Automated Java System Post-Copy Configuration Using SAP Landscape Management 3.0, Enterprise Edition

Transcription

1 Configuration Guide Document Version: Automated Java System Post-Copy Configuration Using SAP Landscape Management 3.0, Enterprise Edition

2 Document History Before you start the implementation, make sure you have the latest version of this document. Table 1 Version Date Description Final Version Renaming SAP Landscape Virtualization Management 2.0 to SAP Landscape Management All rights reserved. Automated Java System Post Copy Configuration Document History

3 Content 1 Introduction Prerequisites Supported Releases Preparation Detailed Configuration Steps and Automation Information Supportability Content All rights reserved. 3

4 References Document Release Note Link Java Post-Copy Automation 4 All rights reserved.

5 1 Introduction Purpose: System copy is one of the fundamental tasks in the operation of SAP system landscapes. SAP recommends that you perform a system copy if you are planning to set up a test system, demo system, or a training system. You must also perform a system copy if you want to change your operating system or your database. After you perform a system copy, you have to perform several post copy configurations on the target system. This document explains how to use automated configuration templates to automate the post copy configuration tasks. Scope: Table 2 Use Template Description Initial Copy Java System Post-Copy Configuration Template 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. The template cleans up and configures the RFC destination, SSL key store configuration, ticket key store, SLD configuration and Trex property settings. You can also use the same template to perform post copy configurations on BI Java system. Export Java System Refresh Export Template 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 postcopy automation, to run the required export steps automatically Introduction All rights reserved. 5

6 Import Java System Refresh Import Template 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. 6 All rights reserved. Introduction

7 2 Prerequisites You have standalone task manager tool for lifecycle management automation installed on your system. Refer to section Preparation, to know how to install and use it. This tool provides you: Automated configuration templates to automate the configuration tasks Framework to execute the templates For more information on standalone task manager tool for lifecycle management automation, see, SAP Note You have configured Java PCA on SAP Landscape Management tool. If you have not configured it, execute the below steps: Launch the SAP Landscape Management application. Choose Configuration Infrastructure Java PCA Table 3 Choose Add. Enter Java post copy automation properties. Field Names Label User Name Password URL Proxy Host Proxy Port Values A label that identifies this virtual Java PCA configuration within SAP Landscape Management. User name to connect to the Java PCA service. User s password. URL of Java PCA service, using the template URL displayed. Proxy hostname (optional) Enter the proxy port (optional). Test the configurations and Save your entries. Prerequisites All rights reserved. 7

8 3 Supported Releases The automated configuration template supports the following releases: NW AS Java 700 SP 21 onwards NW AS Java 701 SP 5 onwards NW AS Java 702 SP 4 onwards NetWeaver 7.03 SP0 NetWeaver 7.30 SP0 NetWeaver 7:30 SP 08 onwards (for BI JAVA PCA) NetWeaver 7.31 NetWeaver 7.31 SP 05 (for BI JAVA PCA) NetWeaver All rights reserved. Supported Releases

9 4 Preparation Procedure 1. Download and install SAP Java Virtual Machine from SAP Service Marketplace. 2. Download the SAP JCo 3.0 drivers for the required operating system. Access the SAP JCo using the link service.sap.com/connectors. 3. Download and install Adobe Flash player in case it is already not installed. 4. Download the latest support package TMLMAUTO00.zip from service market place at service.sap.com/swdc SAP Support Packages Support Packages and Patches A - Z Index S SL Toolset SL Toolset 1.0 Entry By Components STDALONE TSK MGR FOR LMAUTO Download the archive JAVAPCA2.0.zip from service market place at SAP Support Packages Support Packages and Patches A - Z Index N SAP NW LANDSC VIRT MGT ENT 2.0 Comprised Software Component Versions JAVAPCA 2.0 Note Create a new folder and download both the content and the framework to this new folder. 6. Extract the file TMLMAUTO00.zip to the same location. 7. Set the environment variable JAVA_HOME to point to the Java installation. 8. Double click on LMAuto.bat/LMAuto.sh file to start the application. 9. In the command prompt, configure the password for the user lmauser. The password: Must contain at least 1 upper case letter Must contain at least 1 numeric character Must be more than 6 characters in length Confirm the password by entering it again. You can use this user name and password to connect to standalone task manager tool for lifecycle management automation from a remote system. 10. You can use any of the following two approaches to execute the template: Executing the template using SAP Landscape Management (Background Mode) To use the templates for various scenarios with a customized set of template properties, create a variant of the templates by following the sub-steps below: 1. On the home screen of standalone task manager tool, choose the template System Copy: Java Server Post-Copy Configuration or System Copy: Java Server Prepare System Refresh, as required. 2. Choose Variant Management. 3. Choose New. 4. Click on Generate to obtain a Variant ID 5. Provide details (Variant Name and Variant Description) for the new template variant. 6. Choose Save. 7. Choose Task Name and select the newly created variant. 8. Under Variant Management tab choose View Content Preparation All rights reserved. 9

10 9. Provide details for BI Java copy (BW Host Name, User, Password, etc) 10. For the field Required Execution, set value to True 11. For the field UI Mode Execution, set value to False By creating variants to execute a template, you can avoid entering all required parameters every time you run a process. This improves the execution speed and efficiency. Executing the template using standalone task manager tool (UI Mode) You can use the framework of standalone task manger tool to execute automated configuration templates for Java post copy configurations. To do so, 1. On the home screen of standalone task manager tool, choose the template System Copy: Java Server Post-Copy Configuration or System Copy: Java Server Prepare System Refresh, as required. 2. Choose Start With Log Follow the instructions on the screen and execute each configuration step accordingly. 10 All rights reserved. Preparation

11 5 Detailed Configuration Steps and Automation Information The following table shows the configuration steps that are performed automatically by the configuration template, and the steps that have to be performed manually. JAVA post copy configurations Table 4 Configuration Step Logical Task Target System Description Automated 1 Cleaning up invalid Java system Deleting RFC engine configuration data on providers the target system Deleting SSL keystore 2 Configuring the target Java System Configuring RFC engine system providers Configuring SSL keystores Configuring ticket key stores Configuring SLD data supplier Configuring TREX settings Configuring CIM client settings 3 Configuring target BI Java system Checking prerequisites system for a connection to BI (ABAP) system Creating RFC destinations in ABAP system Updating BI (ABAP) tables Creating RFC destination in Application Server JAVA Detailed Configuration Steps and Automation Information All rights reserved. 11

12 Configuration Step Logical Task Target System Description Automated Setting up BI system in the System Landscape in Portal Configuring repository manager Defining access permissions in the portal Swapping certificates between BI system and the Portal system Activating services in the BI (ABAP) system Establishing connection the portal Establishing connection to BW ABAP system Java system refresh configurations Table 5 Configuration Step Logical Task Target System Description Automated 1 Exporting configuration Java System Exporting RFC engine data from the target providers system Exporting SSL key store Exporting ticket key store 2 Importing exported Java system Importing RFC engine configurations back providers into the target system Importing SSL key store Note If you are using Java System Refresh template to import the user information back into the target Java system, the passwords of all users is reset to an initial password. You can avoid this and keep the original passwords intact, by executing the below two instructions: Manually execute the instructions described in the SAP Note Perform this manual activity before you execute the template. Disable the user export/import phase. You can disable it by deselecting the checkbox for the UME phase. 12 All rights reserved. Detailed Configuration Steps and Automation Information

13 6 Supportability In case of issues, create a message with the CSN component BC-INS-CTC-STD. Supportability All rights reserved. 13

14 Typographic Conventions Table 6 Example <Example> Description Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, Enter your <User Name>. Example Example Arrows separating the parts of a navigation path, for example, menu options Example Example /example Emphasized words or expressions Words or characters that you enter in the system exactly as they appear in the documentation Textual cross-references to an internet address Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web Hyperlink to an SAP Note, for example, SAP Note Example Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options. Cross-references to other documentation or published works Example Output on the screen following a user action, for example, messages Source code or syntax quoted directly from a program File and directory names and their paths, names of variables and parameters, and names of installation, upgrade, and database tools EXAMPLE EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE Keys on the keyboard 14 All rights reserved. Typographic Conventions

15 All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE and its affiliated companies ( SAP Group ) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other countries. Please see index.epx#trademark for additional trademark information and notices. Please see for disclaimer information and notices.