Executing Post-Copy Automation Standalone
You execute post-copy automation (PCA) standalone to carry out several configuration steps on a system that was not provisioned by SAP Landscape Management.
Prerequisites
-
You comply with all prerequisites described in SAP Note 1709155 System Provisioning with SAP Landscape Management.
-
You have configured the Initial entities.
-
For ABAP systems, ensure that you have read the following guides on SAP Help Portal at https://help.sap.com/viewer/p/ABAP_POST-COPY_AUTOMATION:
-
For SAP Business Warehouse (SAP BW) systems or systems that are connected to an SAP BW as SAP BW source system, also read the ABAP Post-Copy Automation for SAP BW Configuration Guide.
-
For Java systems, ensure the following:
-
You have read the Java Post-Copy Automation Guide for Enterprise Edition.
For more information, see Java Post-Copy Automation.
-
You have configured Java post-copy automation.
-
-
The system on which you want to execute PCA was not provisioned by SAP Landscape Management.
-
You have to ensure that the copied system does not interfere with your landscape when you start it.
-
You have the required authorizations.
For more information, see Roles and Authorizations
Context
You can use post-copy automation for the following use cases:
Use Case |
Description |
---|---|
Task List Execution |
After the homogeneous or heterogeneous system copy has finished, you have to carry out several cleanup and configuration steps on the target system. The data cleanup is required to delete the content of tables that contain source system information in the target system. This prevents the target system from interfering with the source system and other connected systems. You can use post-copy automation to run the required cleanup and configuration steps automatically. |
Export |
The system refresh is done to overwrite an already existing target system with the latest data from a source system while keeping the configuration. To prevent overwriting the target system configuration, you need to export the target system tables that contain configuration information before you start the system copy. You can use post-copy automation to run the required export steps automatically. |
Import |
The system refresh is done to overwrite an already existing target system with the latest data from a source system while keeping the configuration. To prevent overwriting the target system configuration, you need to export the configuration information before the system copy export and import it again into the target system after the system copy has finished. You can use post-copy automation to run the required import steps automatically. |
Procedure
Results
The monitoring screen appears, where you can view the log of all tasks involved in the process.