Performing the JAVA Post-Copy Automation

Objectives

After completing this lesson, you will be able to:

  • Explain the JAVA post-copy automation
  • Implement and configure JAVA post-copy automation (PCA) for SAP systems based on SAP NetWeaver JAVA

JAVA Post-Copy Automation (PCA)

Post-copy automation includes the following benefits:

Less effort and cost
The number of manual tasks are reduced. You use a wizard instead of searching the configuration documentation, thoroughly reading it, and performing the corresponding steps manually in different UIs, transactions, and tools.
Faster configuration procedures
The required expertise is reduced. You can benefit from SAP expert knowledge, captured in programmatic format.
Greater reliability and standardization of tasks
You can offer services with consistent, predictable quality, regardless of when the task is executed, or by whom.

LM Automation Standalone

  • It offers a lightweight and easy-to-use automation experience.

  • It is a standalone tool. SAP NetWeaver J2EE Engine is not required as runtime. The tool comprises an SAP JVM so that you can completely run it self-contained.

  • It has a short startup time, a small download size, and a small memory footprint.

Why Automation?

  • The challenge is that you have to perform costly configuration steps manually according to the system copy guide.

  • Instead of performing the required tasks for post-copy manually, you can use automation to perform the configuration tasks as follows:

    • Receive guidance through the configuration processes.

    • Benefit from configuration tasks that reflect SAP expert knowledge.

  • Automation results in the following:

    • Less effort and cost.

    • Faster configuration procedures with less expertise required.

    • Greater reliability and standardization of tasks.

Procedures with Automation

The figure, Procedures with Automation, shows the 2 processes, system copy and system refresh, and the required steps for them.

Java Post-Copy Automation (PCA): Overview

The figure, Java Post-Copy Automation (PCA): Overview, gives an overview of the components of the Java Post-Copy Automation (PCA).

In Java post-copy automation, the focus is on the following:

  • Postprocessing after system copy in SAP Basis for JAVA-based systems.

  • Exporting and importing configuration data while refreshing an existing system.

Java System Post-Copy Configuration Template

  • After the homogeneous or heterogeneous system copy finishes, you can perform 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 as follows:

    • Choose System Copy: Java Server – Post-Copy Configuration in the Stand-Alone Task Manager.

    • The template cleans up and configures the RFC destination, SSL key store configuration, ticket key store, System Landscape Directory configuration, and TREX property settings.

    • You can use the same template to import the configuration settings that were exported previously as part of a system refresh procedure.

    • You can also use the same template to perform post-copy configurations on an SAP NetWeaver BI Java system.

    • SAP Landscape Management only handles homogeneous system copies and refreshes. If you want to automate the post-activities of initial heterogeneous system copies, you can execute Java post-copy automation standalone. This is not integrated into end-to-end process of SAP Landscape Management.

Automated Activities for JAVA Initial Copy

Logical TaskTarget SystemExample Subtasks
Cleaning up invalid configuration data on the target systemJava System
  • Deleting RFC engine providers

  • Deleting SSL keystore  

Configuring the target systemJava System
  • Configuring RFC engine providers

  • Configuring SSL keystores

Configuring target systemBI Java System
  • Checking prerequisites for a connection to BI (ABAP) system

  • Updating BI (ABAP) tables

For a detailed list, see Java Post-Copy Automation - Installation and Configuration Guide.

Facts about the Java System Refresh Template:

  • The system refresh overwrites an existing target system with the latest data from a source system, while keeping the configuration.

  • To prevent you from overwriting the target system configuration, 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 export steps automatically by choosing System Copy: Java Server – Prepare System Refresh in the Stand-Alone Task Manager.

Automated activities for Java system refresh

Logical TaskTarget SystemExample Subtasks
Exporting configuration data from the target systemJava System
  • Exporting RFC engine providers

  • Exporting SSL key store

Importing exported configurations back into the target systemJava System
  • Importing RFC engine providers

  • Importing SSL keystores

For a detailed list, see Java Post-Copy Automation - Installation and Configuration Guide.

Minimum Requirements

  • The following are the minimum requirements for SAP NetWeaver:

    • SAP NetWeaver AS Java 7.00 ‒ SP 21

    • SAP NetWeaver AS Java 7.01 – SP 5

    • SAP NetWeaverAS Java 7.02 – SP 4

    • SAP NetWeaver 7.03 SP 0

    • SAP NetWeaver 7.30 SP 0

    • SAP NetWeaver 7.30 SP 08 (for BI JAVA PCA)

    • SAP NetWeaver 7.31

    • SAP NetWeaver 7.31 SP 05 (for BI JAVA PCA)

    • SAP NetWeaver 7.4

  • This is the current state and may be changed by SAP at any time.

JAVA Post-Copy Automation (PCA): Implementation

When implementing Java post-copy automation, download archives as follows:

  1. Download and install SAP Java Virtual Machine on the host that you want to use for JAVA PCA.

  2. Download the SAP JCo driver for your OS.

  3. If needed, download and install Adobe Flash Player.

  4. Download the latest support package of STDALONE TSK MGR FOR LMAUTO 1.0.

  5. Download the archive for JAVA PCA.

  6. Transfer the files to your host that you want to use for JAVA PCA.

Regular exports of SAP Landscape Management configuration data cannot replace a proper backup and restore concept for the SAP Landscape Management system and database.

To install Java post-copy automation, proceed as follows:

  1. Set the JAVA_HOME env variable on your system where you want to start the Standalone Task Manager for JAVA.

  2. Append the PATH env variable with the JAVA_HOME path.

  3. Create a new folder structure, for example, /JAVAPCA/TMLAUTO/TMLAUTO.

  4. Extract the archive of STDALONE TSK MGR FOR LMAUTO 1.0 into /JAVAPCA/TMLAUTO/TMLAUTO.

  5. Extract the archive for JAVA PCA into /JAVAPCA/TMLAUTO.

  6. Depending on your OS, execute LMAuto.bat/LMAuto.sh.

  7. In the command prompt, set the password for user lmauser.

Task Lists

Task Lists support you in post-copy configuration work, preparing a system refresh and also configuring HTTPs for LM Automation Framework as follows:

Available Task Lists

Task ListSummary
System Copy: Java Server – Post-Copy AutomationIt reduces the effort required by automating post-copy activities  like cleanup and reconfiguration of the copied system.
System Copy: Java Server – Refresh (Export) ConfigurationIt backs up your configuration, like RFC destination and SSL keystore before the system refresh.
System Copy: Java Server – Refresh (Import) ConfigurationIt imports the previously exported configuration of the refreshed system.
Configure HTTPS on LM Automation Framework (LMA)

It configures the keystore, SSL port, and so on, which are required to enable HTTPS on a standalone Local LM Automation Framework.

It enables Local LMA to establish secure communication with the HTTPS-configured remote LMA.

Regular exports of SAP Landscape Management configuration data cannot replace a proper backup and restore concept for the SAP Landscape Management system and database.

You can access Standalone Task Manager for Lifecycle Management Automation via

Code snippet
http://<hostname>:50099/lmauto/index.html
Expand
To log on, enter the user lmauser and the previously defined password.

Regular exports of SAP Landscape Management configuration data cannot replace a proper backup and restore concept for the SAP Landscape Management system and database.

Regular exports of SAP Landscape Management configuration data cannot replace a proper backup and restore concept for the SAP Landscape Management system and database.

If you want to use the post-copy automation tasks for various scenarios with a customized set of task properties, you can create and adapt a variant of the available tasks as follows:

  1. Start the application via LMAuto.bat/LMAuto.sh.

  2. Open a Web browser and enter the LM Auto URL.

  3. In the Task Name area, select the task that you want to customize.

  4. Choose the Variant Management tab.

Regular exports of SAP Landscape Management configuration data cannot replace a proper backup and restore concept for the SAP Landscape Management system and database.

Regular exports of SAP Landscape Management configuration data cannot replace a proper backup and restore concept for the SAP Landscape Management system and database.

To finish creating a variant, proceed as follows:

  1. Choose the newly created task variant from the Task Name area.

  2. In the Variant Management tab, choose View Content.

  3. Modify the details as required.
    • The Variant Management UI renders the variant (an XML file) of a scenario in a user-comprehensible format, with a set of attributes or key indicators, such as label, information, secure, required, maximum length, and so on.

    • Mandatory fields that are empty are marked with a red dot in the Valid column.

  4. Choose Save.

  5. On the dialog box, choose OK.

If you want to execute a task variant, choose the Variant Management tab. Select the variant that you want to execute and choose Execute Variant. If you execute a variant Standalone Task Manager for Lifecycle Management Automation, it shows the info of the variant again for your confirmation.

Follow the guidance of the tool and enter further information about the AS Java system on which you want to execute the task. This is necessary if you don't use a variant. For more information about post-copy automation tasks, see the detail figures for every task at the end of this lesson.

Move the mouse over the information symbols to get help text about the required parameters. The progress of the execution is shown in the upper part of the tool. The tool reports any configuration errors. Error message long texts are written to the log file.

Standalone Task Manager for Lifecycle Management Automation - Execution Protocol

After the execution finishes, choose Get Log to view the execution protocol. The protocol provides detailed information about the execution run and performed activities.

After executing the configuration task, deactivate or delete the technical user that calls Remote Function Calls (RFCs), Business Application Programming Interfaces (BAPIs), and Web services in your SAP NetWeaver Java system.

Regular exports of SAP Landscape Management configuration data cannot replace a proper backup and restore concept for the SAP Landscape Management system and database.

Summary

The following is an overview of tasks to perform:

  • Check JAVA post-copy automation guides.
  • Set environment variable JAVA_HOME accordingly.
  • Append env variable PATH with the JAVA_HOME path.
  • Extract JAVA PCA and LMAUTO archives to the same location.
  • Start LMAuto and define a password for user lmauser.
  • Access Standalone Task Manager for Lifecycle Management via
    Code snippet
    http://<hostname>:50099/lmauto/index.html
    Expand
  • Configure task lists in Standalone Task Manager for Lifecycle Management.

If you want to configure technical configuration tasks automatically for a Java system copy or a Java system refresh, configure Java post-copy automation (PCA) as follows:

  1. Choose InfrastructureJava PCA.

  2. Choose Add.

  3. Provide the requested information.

  4. Replace the dummy in the URL field with the real hostname:

    Code snippet
    http://<host>:50099/lmautoconnector/dispatcher
    Expand

  5. Choose Test Configuration.

  6. If the test of the configuration was successful, choose Next.

  7. In Summary screen, choose Save.

Log in to track your progress & complete quizzes