SAP S/4HANA On Premise Post System Copy Steps

[gilbert_wong]

This document will provide you the required post system copy steps to get your SAP S/4HANA On Premise system up and running. The document will guide you through the steps required after you have successfully performed a SAP system copy of both SAP S/4HANA Backend and Frontend system. This document will not cover the SWPM steps for the target System of a standard System Copy. After completing the post system copy steps, you will have a functioning SAP Fiori Launchpad connecting to the SAP S/4HANA backend system.

High level post system steps include:

• Generate SAP License


• Adopt SAP Instance Profiles


• Reconfigure SSL


• Reconfigure Trusted RFC on both BES and FES


• Reconfigure SAP Web Dispatcher Instance Profile


• Reconfigure SAP Web Dispatcher SSL


• Reconfigure RFC’s


• Reconfigure STMS


• Reconfigure SAML

Optional Steps, if SID rename is performed:

• Update logical system names


• Reconfigure Enterprise Search


• Reconfigure Alias

As a prerequisite for SAP S/4HANA On Premise post system copy document, you will need to perform a homogenous or heterogenous system copy procedure. To perform a SAP system copy, you will need to follow the standard system copy procedures. Please refer to the following SAP System Copy procedure for details steps. Both SAP S/4HANA Backend and Frontend system must be successfully copied and started before use.

We will use the following acronyms in this guide:

BES = SAP S/4HANA Backend System

FES = SAP S/4HANA Frontend System

Please refer to the following document for step by step instructions on the necessary post system copy steps to get you S/4HANA Backend and Fiori Frontend system up and running.

Link to document - https://www.sap.com/documents/2017/12/584b4b05-e47c-0010-82c7-eda71af511fa.html

Thanks,

SAP S/4HANA RIG

[Former Member]

Thanks for this.

We are also licensed for and will be using embedded BPC for S/4HANA, which will be utilising a separate client for BW (same S/4 system) as per SAP recommendations.  Please could you provide any specific post copy steps for embedded BPC?

The fact it requires a configured BW client complicates system refreshes somewhat and I am not sure how many other customers are out there yet (who have done a system copy anyway)

Many thanks,

[former_member182967]

Wonderful job, any update regarding to latest S/4HANA version?

One more thing to be added, I just suggest:

Adjust the RFC destinations for NWBC and WebDynpro apps according to SAP Best Practices for user experience in SAP S/4HANA -> SAP S4HANA Other App Types Deployment (MAL)

[former_member797199]

Hi,

Link to document does not work aynmore – https://www.sap.com/documents/2017/12/584b4b05-e47c-0010-82c7-eda71af511fa.html

 

Can you please provide the "document for step by step instructions on the necessary post system copy steps to get you S/4HANA Backend and Fiori Frontend system up and running."

Thanks a lot

[rajgawai7777]

Contents

• Introduction
• Homogeneous and Heterogeneous System Copy - Target Database: DB2.
  • About Software Provisioning Manager 1.0
  • SAP Products Based on SAP EHP7 ERP 6.0 and SAP Solution Manager 7.2 SR2 Java Supported for System Copy Using Software Provisioning Manager 1.0.
  • New Features
  • Naming Conventions.
  • Constraints
  • Accessing the Installation Guides
  • Accessing the SAP Library
• Planning
  • Before You Start
  • Use Cases for System Copy
  • System Copy Methods
  • Creating a System Copy Plan
  • Basic Planning Aspects and Parameters.
  • System Copy and Migration Optimization

Database Tuning for Source Databases other than SAP HANA

Package Splitting

Table Splitting

Java Migration Monitor

• Migration to SAP DB2 Database

• Preparation

• General Technical Preparations
• Product-Specific Preparations
• Preparing the Migration to SAP HANA Database
• Preparing the Media Required for Performing the Export

Downloading and Extracting the Software Provisioning Manager 1.0 Archive

• Database Independent System Copy
  • System Copy Procedure
  • Preparing Parallel Export and Import
  • Exporting the Source System
  • Setting Up the Target System

6     Database-Specific System Copy

6.1  SAP DB2 Database-Specific Procedure

7     Copying Single Instances Only

7.1 Copying the Primary Application Server Instance Only

7.2 Copying the Database Only – Move Database Instance

7.3 Copying the Database Only – Refresh Database Instance

7.4 Copying the Database Only – Refresh Database Content

8    Follow-Up Activities

8.1 Performing Follow-Up Activities in the Target System

Performing Follow-Up Activities for Java

General Follow-Up Activities

Product-Specific Follow-Up Activities

9    Additional Information

9.1 Jload Procedures Using the Java Migration Monitor

About the Java Migration Monitor

Configuration for Using the Java Migration Monitor

Starting the Java Migration Monitor

Files of the Java Migration Monitor

Restarting Jload Processes

9.2 Analysis of the Export and Import Times

9.3 Package and Table Splitting for Java Tables

Configuration for Using the Java Splitter

Starting the Java Splitter

Output Files of the Java Splitter

9.4  Using PowerShell

9.5  Starting and Stopping the SAP System

Introduction

At several stages in the lifecycle of your SAP EHP7 ERP 6.0, you will face the requirement to perform a system copy or a migration. For example, SAP recommends that you perform a system copy to DEV,QAS & PRD systems. Also, if you need to change your operating system or database, you have to perform a migration of your SAP system. For this, SAP is offering the system copy and migration services of Software Provisioning Manager 1.0 (offering the latest  sapinst version including latest features and fixes for several product versions) that enable you to create consistent copies of your SAP systems, flexibly adapted to your needs - be it an SAP system distributed to several hosts, a high-availability system and Distributive system on a rather exotic operating system/database combination. Also, the procedure is offered for ABAP, Java and dual-stack systems (as supported for the corresponding product version).

Homogeneous and Heterogeneous System Copy - Target Database: DB2

This document describes how to perform a homogeneous or heterogeneous system copy of an SAP system based on the application server of SAP EHP7 ERP 6.0 and SAP Solution Manager 7.2 SR2 Java, with source operating system Linux Suse to DB2 database as target database, using software provisioning manager 1.0 SP38.

The system copy procedures described in this guide consist of two phases:

1. Export of the source system's database content.
2. Installation of the target system using the source system's database content exported in the previous step. The target system installation consists of both the target database and target instance/application server installations

Contents

• Introduction
• Homogeneous and Heterogeneous System Copy - Target Database: DB2.
  • About Software Provisioning Manager 1.0
  • SAP Products Based on SAP EHP7 ERP 6.0 and SAP Solution Manager 7.2 SR2 Java Supported for System Copy Using Software Provisioning Manager 1.0.
  • New Features
  • Naming Conventions.
  • Constraints
  • Accessing the Installation Guides
  • Accessing the SAP Library
• Planning
  • Before You Start
  • Use Cases for System Copy
  • System Copy Methods
  • Creating a System Copy Plan
  • Basic Planning Aspects and Parameters.
  • System Copy and Migration Optimization

Database Tuning for Source Databases other than SAP HANA

Package Splitting

Table Splitting

Java Migration Monitor

• Migration to SAP DB2 Database

• Preparation

• General Technical Preparations
• Product-Specific Preparations
• Preparing the Migration to SAP HANA Database
• Preparing the Media Required for Performing the Export

Downloading and Extracting the Software Provisioning Manager 1.0 Archive

• Database Independent System Copy
  • System Copy Procedure
  • Preparing Parallel Export and Import
  • Exporting the Source System
  • Setting Up the Target System

6     Database-Specific System Copy

6.1  SAP DB2 Database-Specific Procedure

7     Copying Single Instances Only

7.1 Copying the Primary Application Server Instance Only

7.2 Copying the Database Only – Move Database Instance

7.3 Copying the Database Only – Refresh Database Instance

7.4 Copying the Database Only – Refresh Database Content

8    Follow-Up Activities

8.1 Performing Follow-Up Activities in the Target System

Performing Follow-Up Activities for Java

General Follow-Up Activities

Product-Specific Follow-Up Activities

9    Additional Information

9.1 Jload Procedures Using the Java Migration Monitor

About the Java Migration Monitor

Configuration for Using the Java Migration Monitor

Starting the Java Migration Monitor

Files of the Java Migration Monitor

Restarting Jload Processes

9.2 Analysis of the Export and Import Times

9.3 Package and Table Splitting for Java Tables

Configuration for Using the Java Splitter

Starting the Java Splitter

Output Files of the Java Splitter

9.4  Using PowerShell

9.5  Starting and Stopping the SAP System

Introduction

At several stages in the lifecycle of your SAP EHP7 ERP 6.0, you will face the requirement to perform a system copy or a migration. For example, SAP recommends that you perform a system copy to DEV,QAS & PRD systems. Also, if you need to change your operating system or database, you have to perform a migration of your SAP system. For this, SAP is offering the system copy and migration services of Software Provisioning Manager 1.0 (offering the latest  sapinst version including latest features and fixes for several product versions) that enable you to create consistent copies of your SAP systems, flexibly adapted to your needs - be it an SAP system distributed to several hosts, a high-availability system and Distributive system on a rather exotic operating system/database combination. Also, the procedure is offered for ABAP, Java and dual-stack systems (as supported for the corresponding product version).

https://help.sap.com/docs/FIORI_TECHNOLOGY/d71464d9f3204ea8be1144d62acd9ac3/270dd0bc79044592ab225452...

Homogeneous and Heterogeneous System Copy - Target Database: DB2

This document describes how to perform a homogeneous or heterogeneous system copy of an SAP system based on the application server of SAP EHP7 ERP 6.0 and SAP Solution Manager 7.2 SR2 Java, with source operating system Linux Suse to DB2 database as target database, using software provisioning manager 1.0 SP38.

The system copy procedures described in this guide consist of two phases:

1. Export of the source system's database content.
2. Installation of the target system using the source system's database content exported in the previous step. The target system installation consists of both the target database and target instance/application server installations