System Copy Guide System Copy for SAP Systems Based on SAP NetWeaver 7.

0 Including Enhancement Package 1 ABAP+Java
Target Audience ■ System administrators ■ Technology consultants

PUBLIC Document version: 1.5 – 2010-01-25

Document History

CAUTION

Before you start the implementation, make sure you have the latest version of this document. You can find the latest version on SAP Service Marketplace http://service.sap.com/ instguides. The following table provides an overview on the most important document changes:
Version Date Description

1.50 1.40 1.30 1.20 1.10 1.00

2010-01-25 2009-12-08 2009-09-10 2009-03-12 2008-12-09 2008-09-25

Update in Oracle-Specific Procedure Update in Database-Specific System Copy Update in Oracle-Specific Procedure Updates in Constraints and Preparation for Table Splitting Updated version Initial version

2/144

PUBLIC

2010-01-25

Table of Contents

Chapter 1 1.1 1.2 1.3 1.4 1.5 Chapter 2 Chapter 3 3.1 3.2 Chapter 4 4.1 4.2 4.3 4.4 4.5 4.5.1 4.5.2 4.5.2.1 4.5.2.2 4.5.2.3 4.5.2.4 4.5.3 4.6 4.6.1 4.6.2

Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7.0 Including Enhancement Package 1 . . . . . . . . . . . . . Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Online Information from SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7 7 8 8 8 9

Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 General Technical Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Installing the Java Development Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Database Independent System Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Copy Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generating DDL Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparation for Table Splitting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing the Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting the Source System Using SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . Running SAPinst on UNIX or Windows to Perform the Export . . . . . . . . . . . . Running SAPinst on IBM i to Perform the Export . . . . . . . . . . . . . . . . . . . . . . Preparing the Windows Host for the SAP System Installation . . . . . . . . . . . . . Preparing a Windows User Account and IBM i User Profile . . . . . . . . . . . . . . . Installing TMKSVR and Creating an Installation Share . . . . . . . . . . . . . . . . . . Starting SAPinst on IBM i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restarting R3load Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Up the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transferring the Export Files to the Target Host . . . . . . . . . . . . . . . . . . . . . . . Installing the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 26 29 30 33 34 34 41 41 42 43 46 51 52 53 54

2010-01-25

PUBLIC

3/144

. . . . . . . . . . .2 6. . . . . . . . . . .3 Database-Specific System Copy . . . . . . .3. . PI: Integration Server . . . .4 5.1 5.1. . . . . . . . . Business Intelligence Java Components (BI Java) .3. . . . . . . . . . . . . . . . . . .1. .2. . . . . . . . . . . . .2. . . . . . . . . . . . . . . . . . . Creating an Offline or Online Backup with BR*Tools . . . . . . . . . . . . .3. . . . . . . . . . . Generating the Control File Structure . . .1. . . . . . . . . . . . .3. . . . . . . . . . . . . . . . . . . . .2. . . . . . . . . . . . . . . . . . . . . . . . . . Follow-Up Activities . . . . . .6 Chapter 6 6. .1. . . . 57 59 60 64 65 65 66 68 69 70 72 73 78 78 81 81 81 81 82 86 86 87 87 87 88 88 88 88 88 91 91 92 92 93 94 95 4/144 PUBLIC 2010-01-25 . SAP MaxDB-Specific Procedure . . . . . . . . . . . . . . . . . . . . . . . . . General Follow-Up Activities . . . . .2. . . . . . . . . . . . . . . .2. . . Performing Follow-Up Activities for Java . . . . . . . . . . .2. . . . . . . .2. . . . . . . Business Intelligence (BI Java) .2. . . . . .3 5. . .1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3. . .2. . . . . . . Creating an Offline Backup . . . . . . . . . . . . . . . . . . . IBM DB2 for z/OS Specific Procedure .3. . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Backup . . . . . . .3. . . . . . . Basic Configuration for Usage Type BI Java . . .1 5. . . .3. . .3.1. . . . . . . . . . . . . . . .3. . . . . . . . . .3. . . . .Chapter 5 5. . . . . . . . . . . .2. .2. . . . . . Process Integration (PI) . . . . . .3 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.3. . . . . . . . . . . . .2 5. . . .2. . . . . . . . . .2 5. . . . . . . . .3 5.2. . .2. . . . . . . IBM DB2 for Linux. . . . . . . . . .2. . . . . . . . . . . .2. . . . . . .2. . . . . . . . . . . . . . . . . . Oracle-Specific Procedure . . . . . . .2. . . . .1 6.2. . . . . . . . . . . . . . Restoring Database Files on the Target System . . . . . . . . . . . UNIX. . . . . . . . . PI: Changes in the Exchange Profile . . . . . . . . . . . . . . .2 6. .2. . . . . . . .1 5. . . . . . . . . . . . . . . . . . . . .1 6. . . .1 6. . IBM DB2 for i5/OS Procedure . . . . Performing Follow-Up Activities in the Source System . . . . . . .1. . . . . . . . . . . . .2. . . . . . . . . . . . . . . . . . . .4 5. . . . .2.2 6. . . .1 6. . . .2. . . .2 6. . . . .1. . . . . .4. . . . . . . . . . . . . . . AS Java: SAP Knowledge Warehouse . . . . . . . . .5 5. . . . . . . . . . . .2. . EP: Knowledge Management and Collaboration .3.2.2 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enterprise Portal (EP) . . . . . . . .3.1 6. . . . . . . . . . .2. . . . . . . . . . . . . . . . . . . . . . .1. . . . . .2 5. . . . . . Application Server Java (AS-Java) . . . . . PI: System Landscape Directory . . . . . . .3.3. . . . . . . . .1. . . . . . .2. . . . Generating Public-Key Certificates . . . . . . .1 6. . . . . . . . . . . . . . . . . . . . . .4 6. . . . . . . . .2. . . .2 6. . .2. . .5 5. . . . . . . . . . .2. .1 6. . . . . . . . . . . . . . . . . . . . . . . . .3. . . . . . . . . . . . . . . . . . . . . . .3 6.2. . . . . . . . . . .2. . . Installing the License Key . . . . . . . . . Preparing the Target System . . . . . . . . . . . . . . . . . . . . . . . . . .3. . .4. Performing Follow-Up Activities for ABAP . . . . . . . . . . . . . . Configuration Steps for the SAP Java Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 6. . . . .2. . . .4. . . . . . . . . .1 6. and Windows-Specific Procedures . . . . . MS SQL Server-Specific Procedure . . . . . . Usage Type or Software Unit-Specific Follow-Up Activities . . . . . . . . .2 6. . . . . . . EP: Basic Configuration . . . . . . Performing Follow-Up Activities in the Target System . . . . Restoring the Database Files on the Target System with BR*Tools . . . . . . .2. . . . . . . . . . . . . .1 6. . . . .

. . . . . . . . . . . . .4. . . . . . . . .1 6. . .2 6. . . . . . . .2. . . . . . . . . . . . .3. . . . . . . . .2. . . . .3. .3. .2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 6. .2. . .2. . . . . . . .6 6. . . . . . . . . . . . .5 6. . .2. . . . . . .2. . . . . . . . . . . . . . . . . . Assigning DDL Files to Packages . .2.3. . . . . . . . . . . . . . . . . . . . .4. . . . . . . . . . . . . . .2 7. . . . . .3. .2. . . . . . . . . . . . . 105 Configuring Single Sign-On . . . . .2. . . . . . . . . . 103 ERP-XSS: SAP WebDynpro Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 111 111 118 119 119 121 126 126 127 128 131 131 133 2010-01-25 PUBLIC 5/144 . . .2. . . . . . . 103 CRM Java Components (JCRM) / Extended E-Selling Components (XECO) . . . .6 6. .2. . .2 PI: Refresh Caches . . . . . . . . . . . . . . . . . . . .1. . .1 7.7 7. .6. . . . . . .2. . . . . . . . . . . . . . .10 6. . . .3. . . . . . . .3 7. . . . . . . . . . . . . . . .2. . . . . . . . . . . . .8. . . .7 6. . . . . . 108 Performing Jobhead Correction after Homogeneous System Copy . . . . . .2. . . . .2. . . . . . . . . Defining Groups of Packages . . .3. . . . . .2. . . . . . .8 6. . . . . . . . . . . . . . . . . .3. . . . . . . . . . . .1. . . . . . . . . . . . . . .1.2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3. . . R3load Procedures Using the Migration Monitor . . . . . . . .5 6. . . . .2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.1 6. . . . . . . . . . . 102 Self Services (XSS) . . .2. . . . .1 7. . 103 Re-Creating the JCo Destinations . . . . . . . . . . . . .1 6. . . . . . 99 Mobile Infrastructure (MI) . . . . . . . . . . . . . . . . . . . . . .2 7. . .1. . . . . . . . . . . . . . . . . . . . . . . . 97 PI: Connection Checks .2. . . .6. . . . . .1. . . .5 7.4. . . . . . . . . . . 102 MI: Clean Up the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . .3. . . . .4 7. . . . . . . .4 Chapter 7 7. . . . . . . . . . . . . . . .4 6. . Installing the Target System Using the Migration Monitor . . .2 6. . . . . .1. . . Configuration . . .2. .4. . . . . . Output Files . .3. . . . . .4 7. . . . . . . . . . . . . . . . . . . . . . . 99 Development Infrastructure (DI) . . . . . .2. . . . . . . . . . . . . . . . . . . . . . .10. . . . . . . . . . . . .3 7. . . Starting the Migration Monitor . . . . . . .7. . . . . . . . .9 6.3. .2.2. . . . . . . . 104 Sub-Component Workforce Deployment AS/CS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 MapBox . .2. . . . .3.2. . .3. . . . . . . . . . . . . . . 106 SCM Forecasting & Replenishment Processor (SCM FRP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7.10. . .2. . 105 SRM Live Auction Cockpit (SRMLAC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2. . . .1.1 7. .3. . . . . . .2. . . . . . Interrupted Installation with SAPinst . . . . . . . . . . 104 SRM Live Auction Cockpit (SRMLAC) . . . . . . Processing Split Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting SAPinst GUI Separately . . . . . . . . . . 108 Additional Information . . . . . . . . . . . . . . . . . .6 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3. . .1 6. .2. . . . . . . . . . Performing a Remote Installation with SAPinst . . . 97 PI: Switching Addresses . Using SAPinst GUI . . . . . .2. . . . .4. Performing a Remote Export Using SAPinst . . . . . . .

.This page is left blank for documents that are printed on both sides.

They are used in the same way as in the SAP system installation documentation. SAPinst installs all the instances again. ■ System Copy Duplication of an SAP system. Heterogeneous system copy is a synonym for migration. you change either the operating system or the database system. You must replace them with the values valid for your site. or both.0 including Enhancement Package 1 (SAP NetWeaver 7.0 Including Enhancement Package 1 As of SAP NetWeaver 7. When you perform a system copy.1 Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7. 1. This document explains how to perform a system copy for SAP systems based on SAP NetWeaver 7. but it uses a copy of the source system database to set up the database. you can copy ABAP systems. The terms source database and target database are also used in this description.0. ■ Database Copy Database-dependent part of the system copy.0 EHP 1). ■ Heterogeneous System Copy During the system copy.1 Terminology ■ Homogeneous System Copy During the system copy you use the same operating system and database platform as the original system.0 Including Enhancement Package 1 Terminology 1 Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7. The following additional placeholders are used: 2010-01-25 PUBLIC 7/144 . using either database-specific methods or database-independent methods. Certain SAP parameters might change in a copy. ■ Source System and Target System The SAP system containing the original database is called the source system and the system to which the database copy is to be imported is called the target system. ■ Placeholders Placeholders such as <SAPSID> are used in commands. Their SAP system names are abbreviated to SOURCE_SAPSID and TARGET_SAPSID (IBM i: source_<SID> and target_<SID>). ABAP+Java systems and Java systems in one run.1 1.

for example the Software Delivery Manager (SDM) is persisted in the file system.0 Including Enhancement Package 1 Online Information from SAP Meaning How to find out Placeholder <SAPSID> <S_HOST> <T_HOST> <S_SAPSID> <T_SAPSID> <S_DBSID> <T_DBSID> <OS> <DB> <Technology> SAP system ID System name of the source host Command hostname System name of the target host Command hostname SAP system ID of the source system <SAPSID> of the original system SAP system ID of the target system <SAPSID> of the target system Database ID of the source system <DBSID> of the original system Database ID of the target system <DBSID> of the target system Operating system name within a path Database name within a path ABAP. Java.1 1. 1.0 EHP 1 that have been released already for system copy.com/osdbmigration. ■ SAP Note 82478 CAUTION Only perform a system copy if you have experience in copying systems and thorough knowledge of the operating system. ■ SAP OS/DB Migration page at http://service. In addition to the information contained on this page.2 Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7. check the SAP OS/DB Migration Planning Guide that is available in the Media Library.4 Restrictions NOTE Refer to SAP Note 1238351 for Java components based on SAP NetWeaver 7. 8/144 PUBLIC 2010-01-25 . create a customer message using the application area BC-INS-MIG. 1. Only perform a heterogeneous system copy if you are a certified system support consultant or a certified SAP Technical Consultant. and the Java Dictionary.sap. the database.com/irj/sdn/systemcopy. NOTE If you encounter problems during the system copy. Each server instance has a unique ID and is stored in the database.3 System Architecture The Java system persists data in both the database and the file system. or ABAP+Java 1. the ABAP Dictionary.2 Online Information from SAP More information about system copying is available online as follows: ■ SAP System Copy & Migration page at http://sdn.sap.

we strongly recommend that you follow the rules mentioned below. For the scenarios below. ■ If you have made modifications in your development system and want to copy your quality assurance or production system onto the development system. your source system is copied to the target system as a whole. as SAP does not support this installation option.0. ■ Reinstalling the central instance without the database is not supported.1 1. The migration controller deletes all dialog instances in the database. Use the appropriate tools for database reorganization. ■ SAP does not support all data archiving operations after a system copy.5 Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7. so the system is not complete any longer. ■ Only valid for: IBM DB2 for Linux and UNIX and Windows | The option Deferred Table Creation is not supported for load-based system copies for SAP systems that are not based on SAP NetWeaver 7. 2010-01-25 PUBLIC 9/144 . refer to SAP Note 551344. it is neither possible to exclude a single stack from the system copy nor to copy a separate stack only. The migration controller deletes all dialog instances in the database. You can use client transport for the initial setup of an SAP system infrastructure. This documentation does not describe how to copy data from non-SAP systems to SAP systems. ■ Copying only the database is not supported. This means. refer to SAP Note 130906. ■ If you want to convert a non-Unicode system to a Unicode system or perform the system copy of a Unicode system. Since no migration controller is invoked in this scenario. ■ Copying only the central instance is not supported.5 Constraints ■ As of SAP NetWeaver 7. so the system is not complete any longer. ■ SAP does not support client transport as a system copy method. End of: IBM DB2 for Linux and UNIX and Windows | 1. if your system is a double-stack system and you perform a system copy. Otherwise. ■ This documentation describes how to copy data from one SAP system to another SAP system based on SAP NetWeaver Application Server.0 EHP 1. This documentation does not cover the client copy procedure. we cannot guarantee that you can copy your Java engine later with the SAP tools to change your underlying operating system and/or database system. ■ This documentation does not describe how to export and import a database with the installation tools for reorganization purposes.0 Including Enhancement Package 1 Constraints The target system installation consists of both the target database and target instance/application server installations. Refreshing the database means that only the database is loaded with the content of a database of a different system. the following holds: ■ Refreshing the database is not supported. Transporting production clients is not supported at all. this is not supported. ■ For the development of Java applications.

◆ Set up dependencies between Java and ABAP. Access to archived files from the target system without a dedicated archive migration project is only supported in the following cases: ● Your system copy clones a source system for nonproductive purposes. ● The system copy is done to replace a productive system with a new productive system (for example. This means that none of the usage types in the target system can be excluded from the system copy. ■ When you perform a system copy. all software units or usage types in the source system are copied to the target system. for example: ▶ SAP SystemID and SID (SAPSID =SID=system name) ▶ Host name ▶ IP addresses ▶ Services and ports ▶ Logical destinations and logical system names ▶ Other technical infrastructure names ◆ Use file system persistency. contact SAP SLO at http://service.1 1. If saving this data to the file system level is unavoidable. nor can you select usage types.com/slo or slo.com/slo.sap.sap. In all other cases. but arrange for file access and/or ArchiveLink/CMS connectivity.5 Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7. assuming that the target system did not exist before and the source system's operation is discontinued after the system copy. ◆ Make sure that all communication runs through the database pool. or you arrange network access for appropriate archive file sharing. hardware migration). for read-only access to the previously archived data from the target system (no reloading). ◆ Follow the Open SQL standard.0 Including Enhancement Package 1 Constraints If you used data archiving in the source or target system.consulting@sap. and you do not store archive files using ArchiveLink/CMS. 10/144 PUBLIC 2010-01-25 . Use a pointer to the central storage of such information. ● Don't: ◆ Save any system and infrastructure-specific data in business objects. access to the created archive file(s) from the target system may not always be possible. You must not change the system ID during system copy. For more information. see SAP Note 153433 and System Landscape Optimization at http://service. you must use the Software Deployment Manager (SDM) to save the data. ■ Dos and Don'ts for system copy: ● Do: ◆ Save configuration data and runtime data in the Java database only. You can either copy all archive files to file systems that are not shared between the source and the target system.com.

1 1. ■ If you have implemented a federated portal network (FPN) across multiple SAP NetWeaver systems. 2010-01-25 PUBLIC 11/144 . refer to SAP Note 1080080 before commencing with the system copy.0 Including Enhancement Package 1 Constraints ◆ Try to copy the Java part of an ABAP+Java system to a Java standalone system or vice versa.5 Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7.

This page is left blank for documents that are printed on both sides. .

Tools. This could be a month-end or year-end closing.2 Planning 2 Planning This section describes how to plan your system copy. this allows you to identify customerspecific problems that might result from modifications. ■ For the installation of the target system. you also need the installation guide for your SAP application. it might be advisable to use the same SAP system ID. End of: Oracle | NOTE You should perform upgrades in a test system first. training. Installation guides are available at http://service. demonstration.0 Including Enhancement Package 1 only describes the export of the source system in detail. Required Documentation ■ Read the following SAP Note for up-to-date information: SAP Note 1238351 (Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7. Depending on the purpose of the system. When copying a system that contains production data choose the right time for the copy.sap. and standby. Required DVDs.0 including Enhancement Package 1) ■ The documentation System Copy for SAP Systems Based on SAP NetWeaver 7. even though this prevents you from including the system in a system group for transports. ■ Creating systems for testing. and Other Software Make sure that all required DVDs for the system copy are available: ■ Required DVDs ● Installation Master DVD ● Java DVD 2010-01-25 PUBLIC 13/144 .com/instguides . Only valid for: Oracle | NOTE You cannot create standby systems with a system copy. CAUTION Do not use NFS-mounted file systems because writing to NFS-mounted file systems might cause corrupted dumps. You can use the system copy for: ■ Setting up system landscapes (where the SAP systems have different SAPSIDs).

The source system is only down for the time of the export.0 EHP 1 . ■ For a heterogeneous system copy. NOTE You can operate several SAP systems on a single host without encountering any problems. we recommend that you use a separate host for each system because an SAP system upgrade might depend on an OS upgrade. you need to get a migration key by generating it at http:// service. you can upgrade them at different times. You can find the full names of all media shipped with SAP NetWeaver 7. 1. a partial test run (export of the entire database or parts of it) can be sufficient to calculate the system downtime. ■ Check that you have the appropriate tool versions for your SAP kernel. Perform a test run of the system copy. The test run is also to determine the amount of export data. This means that the entire database is exported from the source system. CAUTION The source system must be in a consistent state before you can copy it. Calculating the system downtime is particularly important for very large databases (VLDB) or when tapes are being used.com/installNW70 Installation Installation – SAP NetWeaver Systems Media List – SAP NetWeaver 7. If the SAP systems are on separate hosts. and import). try to perform a complete test run. Exceptions are only allowed if they are described in an SAP Note. ■ Order the right version of the installation kit before starting the system copy. and imported there.sap.sap. 3. Consider the downtime of the source system (for preparations and copying) when planning the system copy.2 Planning NOTE The DVD names are abbreviated. time for export. 14/144 PUBLIC 2010-01-25 . transferred to the target system. We recommend that you only perform read/write actions on local file systems. 2. Define a schedule for the test migration and the final migration. System downtime is approximately equal to the total test time (that is.0 EHP 1 in the appropriate Media List for SAP NetWeaver 7.com/migrationkey. transport. Choose the best data transfer method (for example. Nevertheless. ■ If you do not want to replace your source system. Creating A System Copy Plan Create a plan to perform the system copy. FTP or tape).0 EhP1 at: http://service. You can use the time taken by the test run to calculate the system downtime: ■ If your target system will replace your source system. Make sure that the versions of the SAP system and the installation tools are the same on the target and source systems.

Use one of the following: ● System copy procedure on IBM i using R3load for the ABAP part and Jload for the Java part For more information. These methods are not supported for all database systems. Use one of the following: ● System copy procedure on Windows using R3load for the ABAP part and Jload for the Java part For more information. see Starting SAPinst on IBM i [page 46]. ● IBM i-specific procedure for a homogeneous system copy only For more information. 2010-01-25 PUBLIC 15/144 . For more information. see IBM DB2 i Procedure [page 78]. ● System copy procedure for a homogeneous system copy only For more information. new machine type. see Database-Independent System Copy [page 25]. Refer to the following table to check which copy methods are available for your database system: Database OS Platform Available Methods SAP MaxDB UNIX SAP MaxDB Windows IBM DB2 i IBM i Use one of the following: ● System copy procedure on UNIX using R3load for the ABAP part and Jload for the Java part For more information. ● System copy procedure for a homogeneous system copy only For more information. ● The database-specific procedure using tools provided by the database vendor Some database vendors offer specific tools for copying a database. Use this method if database-specific methods are either not available or not suitable. see System Copy Procedure [page 26]. see SAP MaxDB-specific procedure [page 70]. For more information. new file system type). consult your SAP-authorized hardware partner. new hard disk configuration.2 Planning Miscellaneous ■ In the event of a major change in hardware configuration (for example. see Database-Specific System Copy [page 57]. see SAP MaxDB-specific procedure [page 70]. These tools allow you to: ◆ Restore a backup of one database (source database) in another one (target database) (backup method) ◆ Unload the source database and load the data into the target database For more information. see System Copy Procedure [page 26]. see SAP Note 585277. ■ Decide which system copy procedure you want to use: ● The database-independent procedure using SAP tools.

For more information. For more information. see System Copy Procedure [page 26]. and Windows Specific Procedures [page 73]. ● The backup method of IBM DB2 for Linux. End of: UNIX | Oracle Windows ● Oracle-specific procedure for a homogeneous system copy only For more information.0 EHP 1. Use one of the following: ● Only valid for: UNIX | System copy procedure on UNIX using R3load for the ABAP part and Jload for the Java part For more information. End of: UNIX | ● Only valid for: Windows | System copy procedure on Windows using R3load for the ABAP part and Jload for the Java part For more information.PDF attachmed to SAP Note 680746. and Windows is supported for SAP systems based on SAP NetWeaver 7.2 Planning Database OS Platform Available Methods IBM DB2 for UNIX or Windows Linux. DELETE with WHERE is not performed if import errors occur in the target system. see SAP Note 778729. End of: Windows | MS SQL Server Windows ● Homogeneous system copy only: Oracle backup/restore method For more information. and Windows IBM DB2 for z/OS IBM System z Use one of the following: ● System copy procedure using R3load for the ABAP part and Jload for the Java part For more information. see System Copy Procedure [page 26]. Use one of the following: ● Only valid for: Windows | System copy procedure on Windows using R3load for the ABAP part and Jload for the Java part For more information. see System Copy Procedure [page 26]. Use one of the following: ● Only valid for: UNIX | System copy procedure on UNIX using R3load for the ABAP part and Jload for the Java part For more information. see System Copy Procedure [page 26]. see Oracle-Specific Procedure [page 59]. UNIX. Use one of the following: 16/144 PUBLIC 2010-01-25 . End of: Windows | Oracle UNIX ● Additional Information: ◆ For more information about the IBM DB2 for z/OS specific procedure for a homogeneous system copy only. ◆ When R3ta is used to split tables. see the . UNIX. see Oracle-Specific Procedure [page 59] and SAP Note 676468. see System Copy Procedure [page 26]. UNIX. see IBM DB2 for Linux.

you will require a new license key for the target system. see System Copy Procedure [page 26]. CAUTION To meet the requirements of the Workbench Organizer. ■ Choosing an SAP system ID You can choose the new SAP system ID <TARGET_SAPSID> freely during a new installation. End of: Windows | ● Homogeneous system copy only: Backup/Restore or Detach/Attach Method For more information. 2010-01-25 PUBLIC 17/144 .sap. Access to archive files is platform-independent. For more information about ordering and installing the SAP license. ■ SAP license Once the installation is completed and the SAP system copy has been imported.com/nw70 SAP NetWeaver 7. refer to http://service. you must choose different SAP system IDs for different SAP systems. ■ Archiving files Data that has been archived in the source system (data that does not reside in the database but was moved to a different storage location using SAP Archive Management) must be made accessible in the target system.sap. For more information about SAP license keys. ■ Configuration analysis and hardware analysis You need to determine the: ● Number of application servers ● Expected size of the database ● Additional disks or other hardware required ● Required memory NOTE Refer to the section on hardware and software requirements in the SAP system installation documentation to determine the system requirements.com/licensekey.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management Data Archiving . refer to http:// help. For more information.2 Planning Database OS Platform Available Methods ● Only valid for: Windows | System copy procedure on Windows using R3load for the ABAP part and Jload for the Java part For more information.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management SAP Licenses .com/nw70 SAP NetWeaver 7. see MS SQL Server-Specific Procedure [page 72] and SAP Notes 193816 and 151603. see http://help.sap. The license key of the source system is not valid for this system. Adapt the file residence information in the target system.

.This page is left blank for documents that are printed on both sides.

Call transaction SM13. If canceled or pending updates exist. check that your JAVA_HOME environment points to a valid JDK version. 2. Check whether this action was successful using transaction SE16 for table VBDATA. This is not necessary when performing a test run. Select all jobs (include start after event) as follows: Job Released Scheduled 2010-01-25 PUBLIC 19/144 . you must update these again or delete them.1 Preparations General Technical Preparations 3 Preparations Before you start the system copy. You can find out whether canceled or pending updates exist by checking if table VBDATA contains any entries. you need to prepare the source system and perform some subsequent actions on the target system. you must update these again or delete them from all clients. check the minimum kernel patch level required by the support package level of the source system. The following describes important preparations. If canceled or pending records exist. you can do this after the installation of the central instance.Overview and Administration (transaction SM37) You also need to do this for jobs that must run periodically (refer to SAP Note 16083). ■ Before you start the export on your source system. and time. user. ■ No canceled or pending update requests should be in the system. If you have to replace the delivered SAP kernel. you must perform the following preparation steps: 3. ■ Before you start a system copy. Find the canceled or open updates as follows: 1. It might be necessary to replace the SAP kernel delivered with the kernel DVD of the installation kit and installed during the installation of the target system with a newer kernel patch level before starting the target system. 3. For more information about SAP system administration. ■ Set all released jobs from Released to Scheduled: Tools CCMS Background Processing Jobs . refer to the SAP Online Documentation. Choose all update requests.3 3. Check this by choosing Tools Administration Monitor Update (transaction SM13).1 General Technical Preparations Procedure To make a consistent copy of the database. Delete the default values for the client.

Make sure that no customer data is changed in the meantime. as well as after copying the target system. the source and target systems will both exist after the system copy). If your system copy is used to replace hardware for the DB server. As the logical system names will be overwritten. do not delete the QCM table yet. RAZUGA01 (asset acquisitions). create an upgrade test system). If you plan to overwrite an existing system with a system copy (for example. 3. Make sure that no customer data is changed in the meantime. 2. 20/144 PUBLIC 2010-01-25 . source system for the copy is the same as the copy target).1 Preparations General Technical Preparations ■ Adapt the operation mode timetable to make sure that no switching of operating modes takes place while a system is being copied as follows: Tools CCMS Configuration Operation mode calendar (transaction SM63) ■ Write down the logical system names of all clients: 1. 4. 2.3 3. ■ FI customers: You can perform an additional consistency check by running the job SAPF190 before copying the source system. Call transaction SE14. ■ Before the export. 3. migrate to a different database system or operating system (that is. in the event of differences you must change them back to their original names (as they existed in the system that is overwritten) in the follow-on actions after the system copy. Choose Extras Invalid temp. and then compare the results. no changes to logical system names are required. If you create a new system with a system copy (that is. refer to SAP Note 184447. as well as after copying the target system. If you are still planning your BI (formerly BW) system landscape. Mark the tables and delete them. and then compare the results. table All QCM tables that can be deleted are displayed. You can do this as follows: Accounting Financial Accounting General ledger Periodic Processing Closing Check/count Comparison ■ FI customers: You can further check consistency by running the jobs RFUMSV00 (tax on sales/ purchases). RAGITT01 (asset history sheet). make sure that the logical naming strategy for this new system is consistent with your existing logical system naming convention. Before deleting you must always check ● That the tables are consistent – no restart log or conversion procedure termination must be displayed ● That the data of the original table can be read ● If application programs that use the affected original table do not run correctly. delete QCM tables from your system as follows: 1. RAABGA01 (fixed asset retirements) before copying the source system. make sure you write down the logical system names of all clients in the system that will be overwritten (transaction SCC4).

2. see Installing the Java Development Kit [page 21]. you can perform a remote installation using a standalone SAPinst GUI on a separate Windows or UNIX host. If there are any table entries in table TICNV.2 Preparations Installing the Java Development Kit ■ CO customers: You can perform an additional consistency check by running the report group 1SIP before copying the source system. For more information. Defer the migration until the incremental conversion has finished. run transaction ICNV. Only valid for: UNIX. you have to finish the incremental conversion. as well as after copying the target system. This lets you perform the installation on a remote host. and then compare the results. CAUTION Prerequisites for an export: Before performing an export. In this case. The JDK includes the Java Runtime Environment (JRE). controlling it with the SAPinst GUI from a local host. make sure that no incremental conversion is in progress.2 Installing the Java Development Kit You need to prepare the system for the J2EE Engine by installing the Java Development Kit (JDK). CAUTION Heterogeneous System Copy only: Before you start the export of your source system. use your database utility and delete the contents of these tables with the following statements: DELETE from TATGPC DELETE from TATGPCA Normally both tables are empty. see Performing 2010-01-25 PUBLIC 21/144 . you have the following options: 1. which is required for SAPinst.3 3. delete the entries by choosing Control Delete Entry . you will encounter problems while importing the data to your target system because of non NULL capable fields in these tables. make sure that the tables TATGPC and TATGPCA are empty. Make sure that no customer data is changed in the meantime.Windows | NOTE If required. To do so. ● If the tables are in any other state. Try to finish the incremental conversion by performing the following steps: ● If the tables are in state For conversion or in state Done. ■ Prepare the system for SAPinst. If you want to perform a remote installation. To test if an incremental conversion is in progress. 3. If you do not delete the contents of these tables. Choose Assistant and proceed according to the online documentation. an incremental conversion is in progress.

Make sure a valid JDK version is installed on every host on which you want to install an SAP instance with the J2EE Engine.sap.com/pam. The J2EE Engine of the SAP system uses the IBM JDK as mentioned in the section Hardware and Software Requirements. If SAPINST_JRE_HOME is not found. choose SAP Application Components <your product> . NOTE 2. SAPinst also checks JAVA_HOME. ■ If the JDK is already installed Check the installed version of the JDK by entering the following command: java -version NOTE SAPinst checks environment variable SAPINST_JRE_HOME for a valid Java runtime environment. as follows: ■ If the JDK is not already installed. In this case. 2. choose SAP Technology Components SAP SOLUTION MANAGER <Current Release> . End of: UNIX. Go to http://service. the SAPinst executable is running on the Windows installation host. You need to install a valid JDK on Windows only for installation purposes.SAP SRM | On the right-hand panel.SAP ERP. End of: SAP NetWeaver | 3.0 (2004S) . you need at least a JRE on the local host to start the SAPinst GUI there. Only valid for: SAP CRM. 22/144 PUBLIC 2010-01-25 .Windows | Only valid for: IBM i5/OS | NOTE Since IBM i has no graphical user interface. you need to download and install it. Choose tabstrip J2SE Platforms. see SAP Note 723909.SAP SCM.3 3. For more information about the recommended JDK version for your operating system and about how to download it.2 Preparations Installing the Java Development Kit a Remote Installation with SAPinst [page 131].SAP SRM | 5.SAP ERP. Only valid for: SAP Solution Manager | On the right-hand panel.SAP SCM. End of: SAP CRM. Check the JDK versions that are released for SAP systems in the Product Availability Matrix (PAM): 1. End of: SAP Solution Manager | 4. End of: IBM i5/OS | Procedure 1. choose SAP NetWeaver SAP NetWeaver 7. Only valid for: SAP NetWeaver | On the right-hand panel.

you have to edit the configuration file $JAVA_HOME/jre/lib/ security/java.source=file:/dev/urandom. replacing entry securerandom. End of: UNIX | Linux | 2010-01-25 PUBLIC 23/144 .security.2 Preparations Installing the Java Development Kit Only valid for: UNIX | Linux | NOTE If you use a Sun Java VM.3 3.source=file:/dev/random with securerandom.

.This page is left blank for documents that are printed on both sides.

Constraints R3load and Jload Restrictions ■ SAPinst generates a database dump of all SAP objects that are defined in the ABAP Dictionary (R3load) or Java Dictionary (Jload). ■ For a consistent database the SAP system must be shut down (excluding the database!). such as the distribution of tables over several tablespaces or dbspaces.4 Database Independent System Copy 4 Database Independent System Copy You can use the SAP installation tool SAPinst to export and import your Java database content. System Copy Tools ■ Every installation service (dialog instance installation. whereby all tables with the same data class belong to the same package. we recommend that you back these configuration files up before deleting the database. ■ R3load only: Changes to database objects that cannot be maintained in the ABAP Dictionary (transaction SE14). The database must still be running. ■ R3load only: Indexes longer than 18 characters are not allowed on the database to be exported. are lost after the system copy. resulting in varying unload/load runtimes. Other objects are not exported by SAPinst. for example) must have its own separate installation directory whenever you start SAPinst. If the database configuration of your database is stored in the file system. file system. Splitting STR Files ■ During the standard system copy process. SAPinst uses both the R3load tool and the Jload tool. Jload generates a database export of all SAP objects that are defined in the Java Dictionary and archives the configuration and components in the file system. The packages usually differ in the number and size of contained tables. The processing unit for one unload/load process is a package. all tables of the SAP system are grouped into packages. delete the database on the target system before the import according to the corresponding description in the Additional Information section of the installation documentation for your SAP component. The overall runtime can be reduced 2010-01-25 PUBLIC 25/144 . ■ If the target system already exists and you do not plan to perform an MCOD installation. and all configuration in a database-independent format. R3load generates a database export of all SAP objects that are defined in the ABAP Dictionary and archives the configuration and components in the file system.

subdirectory DB/<DBTYPE>. CAUTION If you want to split STR files by the size based option. 26/144 PUBLIC 2010-01-25 . The options can be used separately or – when using the new Java based splitting tool – together. ■ There are several ways to split packages. you create a MIGRATION EXPORT CD image. you need to proceed as follows on the central system host: 1. creating packages with a similar processing time.1 Database Independent System Copy System Copy Procedure by creating packages of the same size. Follow the sequence of steps described in the process flows below for a: ■ Central System ■ Distributed System and High-Availability System Central System To perform the export for a central system. Only valid for: UNIX. You can find the EXT files in your export dump directory. that is. 2.4 4.sap. Enter the installation number of your source system when prompted. Procedure Process Flow on the Source System (Export) When performing the export. Heterogeneous system copy: Generate the migration key at http://service. 4. you must first create the EXT files for the target database system. refer to System Copy Procedure [page 26]. Windows.1 System Copy Procedure This section describes the system copy procedure using R3load and Jload. then you can only split by providing tables via input file. which contains the data of the exported system. for example DB/ORA.Windows | Make sure that the QCM tables are deleted from your system. ■ “Splitting of STR Files” is part of the “Advanced Export Parameters” and is disabled by default. or IBM i. Using the splitting tool parameters selected by SAPinst is a good starting point if you select the splitting option and you have not performed any tests yet.com/ migrationkey. and which you use to install the target system. refer to the F1 help about the parameters prompted on the screen Split STR Files while running SAPinst to export the database. Perform the export on the central system host: 1. For a detailed description of the options. If you do not have EXT files. Process Flow For UNIX. You can achieve this by splitting the default packages (one package per data class) into more smaller pieces.

solve the problem and perform a restart. choose the installation service Database and Central Instance Export. End of: IBM i5/OS. For more information. In SAPinst. see Preparation for Table Splitting [page 30]. For more information. 8.4 4.1 Database Independent System Copy System Copy Procedure For more information. see Setting Up the Target System Using SAPinst [page 52].UNIX | CAUTION If your database instance is running on HP PA-Risc. see Preparing a Windows User Account and IBM i User Profile [page 42]. End of: IBM i5/OS | 3. or IBM i to prepare the source system for parallel export or parallel import (optional). Prepare the system for table splitting (optional). Run SAPinst on UNIX. Windows. see Preparing the Windows Host for the SAP System Installation [page 41]. For more information. Run SAPinst on UNIX. see Restarting R3load Processes [page 51]. Only valid for: IBM i5/OS | Install TMKSVR and create an installation share. End of: IBM i5/OS | 4. Only valid for: IBM i5/OS | Prepare a Windows user account and an IBM i user profile. End of: IBM i5/OS | 5. Generate DDL statements. For more information. see General Technical Preparations [page 19]. Windows. 6. NOTE If R3load processes fail due to an error. For more information. Only valid for: IBM i5/OS | Prepare the Windows host for the SAP system installation. End of: UNIX. For more information. see Running SAPinst on UNIX or Windows to Perform the Export [page 34] or Running SAPinst on IBM i to Perform the Export [page 41]. Only valid for: IBM i5/OS.Windows | 2. see Generating DDL Statements [page 29]. see Installing TMKSVR and Creating an Installation Share [page 43]. see Running SAPinst on UNIX or Windows to Perform the Export [page 34] or Running SAPinst on IBM i to Perform the Export [page 41]. or IBM i to export the database instance and the central instance. choose the installation service Export Preparation. 2010-01-25 PUBLIC 27/144 . In SAPinst.UNIX | Result You have finished this part of the system copy. For more information. 7. For more information. you must proceed as described in SAP Note 884452. you set up the target system using SAPinst. To complete the system copy. For more information.

In SAPinst. or IBM i to prepare the source system for parallel export/ import (optional). or IBM i to export the database instance. Run SAPinst on UNIX.com/ migrationkey. For more information. see Generating DDL statements [page 29].Windows | Make sure that the QCM tables are deleted from your system. choose the installation service Database Instance Export. In SAPinst.4 4. you need to proceed as follows: 1. Generate DDL statements. For more information. see General Technical Preparations [page 19].sap. Enter the installation number of your source system when prompted 2. If your database instance is running on HP PA-Risc. For more information. you must proceed as described in SAP Note 884452. For more information.1 Database Independent System Copy System Copy Procedure Distributed System or High-Availability System To perform the export for a distributed system or a high-availability-system. Only valid for: UNIX. End of: UNIX. Perform the export on the database instance host: 1. 5. see Preparation for Table Splitting [page 30]. choose the installation service Export Preparation. For more information. see Exporting the Source System Using SAPinst [page 34].Windows | 2. For more information. Run SAPinst on UNIX. To complete the system copy. In SAPinst. 3. 4. see Running SAPinst on UNIX or Windows to Perform the Export [page 34] or Running SAPinst on IBM i to Perform the Export [page 41]. Result You have finished this part of the system copy. Prepare the system for table splitting (optional). see Setting Up the Target System Using SAPinst [page 52]. For more information. 28/144 PUBLIC 2010-01-25 . Windows. Perform the export on the central instance host: You run SAPinst to export the central instance. CAUTION 3. set up the target system using SAPinst. Windows. see Running SAPinst on UNIX or Windows to Perform the Export [page 34] or Running SAPist on IBM i to Perform the Export [page 41]. Heterogeneous system copy only: Generate the migration key at http://service. choose the installation service Central Instance Export.

you might need to select the database version. You must perform this procedure before starting SAPinst. 6. you can restrict the generation of DDL statements to specific table types or individual tables. you need to generate DDL statements using the ABAP report SMIGR_CREATE_DDL. 4. Procedure 1. Specify an empty working directory to which the files generated by the report are to be written. 2.4 4. Execute the program. 5. 3. Call transaction SE38 and run the program SMIGR_CREATE_DDL.2 Generating DDL Statements To migrate nonstandard database objects. Select Unicode Migration if you also wish to perform a Unicode system copy (from Unicode to Unicode) or a Unicode conversion (from non-Unicode to Unicode). Depending on the database manufacturer. The DDL statements are generated and are written to the specified directory. Select the target database. Log on to the system as a system administrator in a productive client.2 Database Independent System Copy Generating DDL Statements Overview of Export Options Figure 1: 4. You should only enter a database version that is available in the value help. The value help supports you in selecting the database version. 2010-01-25 PUBLIC 29/144 . 7. If required.

see SAP Note 888210. only the processing of the package where the error occurred has to be repeated and not for the complete table.3 Database Independent System Copy Preparation for Table Splitting CAUTION If no database-specific objects exist in the database. ■ For the following databases. ■ The export and import of one table can be performed in parallel by starting several R3load processes to work on some packages in parallel. Before starting the export. 4. but created empty in the target system) 30/144 PUBLIC 2010-01-25 . ■ The following tables cannot be split: ● DDNTF ● DDNTF_CONV_UC ● DDNTT ● DDNTT_CONV_UC ● DDLOG (is never copied. we recommend that you create an index on the column listed in the hints file for the table you want to split before starting R3ta: ● DB2 for z/OS (Only create a temporary index if you want to perform an unsorted unload.) ● Oracle For more information. the generated SQL files have to be copied from the specified directory to the <instdir> directory of the export.4 4. this is not an error.3 Preparation for Table Splitting The R3ta tool processes large tables. Prerequisites ■ The export and import have to be performed with the migration monitor when the table splitting feature is used. Instead of exporting/importing one table with one R3load process. The advantages of splitting the tables are: ■ Large tables are processed in smaller packages. the table is processed in. For additional database-specific information. If the export or import of a table aborts with an error. Restrictions ■ Only tables that are described in the SAP dictionary can be split. for example. see the paragraph Creating a Temporary Index. Each entity can be processed by different R3load processes. As long as the report terminates with status successfully. no SQL files will be generated. 8. 10 entities.

4 4. If required. the file that contains the split information. merge these results with the results from the first Prepare Table Splitting run: 1. The tables listed in this file have to appear in alphabetical order! Start SAPinst.WHR files have been created for the missing tables.txt. CAUTION When doing a code page conversion (non-Unicode → Unicode. Define a new. Create a new. 5. Parallel data export of a table is supported by all database platforms but parallel data import is not. empty export dump directory <temporary dump directory>. Add the lines from <temporary dump directory>/ABAP/DATA/whr. Update the R3ta .WHR files could be produced for some of these tables.3 Database Independent System Copy Preparation for Table Splitting Procedure 1. For more information. 2. see the paragraph Creating a Temporary Index.WHR files from <temporary dump directory>/ABAP/DATA to <export dump directory>/ABAP/DATA. create fewer packages for these tables: 1. the export directory. If the column PAGENO is included in the WHERE condition. Run the Prepare Table Splitting service again and provide an input file that contains only the missing tables with a lower number of packages for each defined table. CAUTION 6. Check in the export directory <export dump directory>/ABAP/DATA if *. 8. empty installation directory. R3ldctld. and the db<dbtype>slib. the migration monitor has to 2010-01-25 PUBLIC 31/144 . <sidadm> password. If the target database platform does not support the parallel data import.txt. and the number of parallel R3ta jobs. Choose SAP NetWeaver System Copy Source System ABAP System <Database> <Unicode or NonUnicode> Table Splitting Preparation . 2. Copy the *. 7. Create a file that contains lines of the form <table>%<nr of splits> for all tables to be split.* in the kernel directory. If no *. repeat the table splitting . Specify SAPSID. If the *. 4102 ↔ 4103). You can find a version of these files on the Installation Master DVD in the directory IM_<OS>/<DBTYPE>/{UC/ NUC}. CAUTION 3. 3. 2.WHR files have been created for all tables that are to be split. 4.txt to <export dump directory>/ABAP/DATA/whr. The specified path to the export directory must not contain blanks! Continue with Next. create the temporary index on the source system's tables to be split. make sure not to use a WHERE condition with the column PAGENO included.either with different splitting parameters or by defining a suitable column for this table using the R3ta_hints.

separated by a blank. This is the case when you use a DDLDB2. Afterwards.TPL file with no ORDER_BY_PKEY and the R3load does not overrule this setting. refer to SAP Note 960280. see Processing Split Tables.TSK DRP_<table>_IDX. These specifications are used by R3ta to create the WHERE condition. the default index name is <table>~IMG. End of: IBM DB2 for z/OS | Only valid for: Oracle | Oracle only: For further information and for alternatives. R3load command file for dropping the temporary index.4 4.txt file in the Split STR Files dialog box. 2.txt with column hints for several tables is delivered with the Installation Master DVD. make sure you select the Split predefined tables checkbox and add the R3ta_hints.txt.3 Database Independent System Copy Preparation for Table Splitting be configured so that the data import processes the packages sequentially. Only create a temporary index if you want to perform an unsorted unload. End of: Oracle | For each table to be split. 32/144 PUBLIC 2010-01-25 . The columns have to be part of the primary key of the table.cmd Contains the description of the temporary index. R3ta creates the following files to facilitate the creation of the temporary index: File <table>_IDX. Which tables cannot be unloaded unsorted is described in SAP Note 954268. Contains the task to drop the temporary index. With one line in the file R3ta_hints. and before starting the processing phase.TSK <table>_IDX. you specify the table name followed by one or more column names. After the Table Splitting Preparation.STR Description <table>_IDX. you can instruct R3ta to use specific columns of a table to create a WHERE condition. For more information. Creating a Temporary Index Only valid for: IBM DB2 for z/OS | IBM DB2 z/OS only: Create the corresponding temporary index on the database with database tools. If you want to modify this file. The file has to be located in the directory in which you start R3ta.txt. End of: IBM DB2 for z/OS | Only valid for: IBM DB2 for z/OS | EXAMPLE 1.cmd DRP_<table>_IDX. use the REBUILD INDEX job to speed up the index creation process. copy it from the directory <IM_OS>/COMMON/INSTALL to the installation directory and adapt it according to your requirements as soon as the Parameter Summary dialog appears. Contains the task to create the temporary index. Use the DEFER YES parameter to create the index. Using Hints With the file R3ta_hints. A file R3ta_hints. R3load command file for creating the temporary index.

STR) ■ Updating database statistics (…) 2010-01-25 PUBLIC 33/144 . End of: IBM DB2 for i5/OS.TPL file.4 Preparing the Export You can prepare the source system for the export using R3load and Jload. Depending on your database platform. /} ) TABLESPACE &tablespace& STORAGE (INITIAL &init& NEXT &next& MINEXTENTS &minext& MAXEXTENTS &maxext& PCTINCREASE &pctinc& ) NOLOGGING COMPUTE STATISTICS PARALLEL ONLINE.MaxDB. the dbcodepage is 4102 (Big Endian) or 4103 (Little Endian). 4.IBM DB2 for z/OS. End of: Oracle | 3.TPL and add the highlighted key words to the creind statement: creind: CREATE &unique& INDEX &ind name& ON &tab name& ( /{ &fld name& /-. so as to enable parallel export/ import. Depending on your database platform. it might be necessary to modify the create index statement in the DDL<DBTYPE>.IBM DB2 for Linux and UNIX and Windows. Only valid for: Oracle | Make sure that you do not lock the table while creating the temporary index. Call R3load as user <sapsid>adm with the following parameters: R3load –dbcodepage <source system’s dbcodepage> –i <table>_IDX. If your source system is a Unicode system.MS SQL Server | 2. Only valid for: IBM DB2 for i5/OS.cmd –l <table>_IDX.TPL file. For this purpose you need to create certain files. and TSK files created by R3ta to create the index. STR. the dbcodepage is 1100.MS SQL Server | Make sure that you do not lock the table while creating the temporary index.MaxDB. Edit the file DDLORA.4 Database Independent System Copy Preparing the Export You can use the R3load cmd. it might be necessary to modify the create index statement in the DDL<DBTYPE>.IBM DB2 for z/OS.IBM DB2 for Linux and UNIX and Windows. 1. The following steps are performed: ■ Creating the export directory structure ■ Creating database structure files (*.4 4.log If your source system is a non-Unicode system.

and the GUI server are running on the same host.EXT. where SAPinst GUI is running on a separate host from SAPinst and the GUI server. SAPinst GUI.SAR archive on the SAP Installation Master DVD.5.DBSIZE. ■ The export dump directory can be shared and thus made accessible on the target host. 4. if: ■ You want to build up the target system to the point where the database load starts before the export of the source system has finished. see the documentation Migration Monitor – User’s Guide in the MIGMON. ■ Copy the export dump directory manually to the target host. make sure that the dump directory and its subdirectories and files are accessible for user <sapsid>adm of the target system. In any case. have to be transferred to the target host. the complete export directory with its structure and the generated files. NOTE For more information. Procedure 1. As soon as the export preparations have finished successfully. ■ Export and import processes should run in parallel during the system copy process. You can choose one of the following methods: ■ Use the migration monitor with the FTP Copy option to transfer the files to the target instance.1 Running SAPinst on UNIX or Windows to Perform the Export This procedure tells you how to run SAPinst to export the database of your SAP system. see Running SAPinst on UNIX or Windows to Perform the Export [page 34]. Run SAPinst to perform the Export Preparation service.5 Exporting the Source System Using SAPinst Here you can find information about how to run SAPinst to perform the export on the source system: ■ Running SAPinst on UNIX or Windows to Perform the Export [page 34] ■ Running SAPinst on IBM i to Perform the Export [page 46] 4.XML) These export preparations are required. For more information. This section describes a standard export where SAPinst. If required.5 Database Independent System Copy Exporting the Source System Using SAPinst ■ Size calculation for the target database (*.4 4. SAPinst includes a SAPinst GUI and a GUI server. you can perform a remote system copy with SAPinst instead. which both use Java. which are required for building up the target system. 2. For more information. Note the following about SAPinst: 34/144 PUBLIC 2010-01-25 . see Performing a Remote Installation with SAPinst [page 131].

Only valid for: UNIX | ■ SAPinst normally creates the installation directory sapinst_instdir directly below the temporary directory. End of: UNIX | Only valid for: Windows | ■ SAPinst normally creates the installation directory sapinst_instdir. SAPinst finds the temporary directory by checking the value of the environment variables TEMP.out. These executables are deleted after SAPinst has stopped running. If no value is set for these variables.5 Database Independent System Copy Exporting the Source System Using SAPinst ■ When you start SAPinst. where it keeps its log files.xxxxxx. ■ The SAPinst Self-Extractor extracts the SAPinst executables to the temporary directory. you can terminate SAPinst and the SAPinst Self-Extractor by pressing Ctrl+C . Directories with the name sapinst_exe. You can safely delete them. End of: Windows | 2010-01-25 PUBLIC 35/144 . the installation terminates with the error FCO-00058. SAPinst tries to create sapinst_instdir in the directory defined by the environment variable TEMP. If required. TMP. If SAPinst is not able to create sapinst_instdir directly below the Program Files directory. ■ The SAPinst Self-Extractor extracts the executables to a temporary directory (TEMP. which is located below %ProgramFiles%\sapinst_instdir. SAPinst GUI connects to the GUI server using a secure SSL connection and the GUI server connects to SAPinst. do one of the following: ● Right-click the icon for the SAPinst output window located in the Windows tray and choose Exit. TMPDIR. and which is located directly below the Program Files directory. These executables are deleted again after SAPinst has stopped running. or TMPDIR. which might be useful if an error occurs. called <sapinst_instdir> \<installation_service>.4 4. TMP. SAPinst uses /tmp as default installation directory. Only valid for: Windows | ■ If you want to terminate SAPinst and the SAPinst Self-Extractor. ■ SAPinst creates a subdirectory for each installation service. or SystemRoot). you can also find the SAPinst Self-Extractor log file dev_selfex. In the temporary directory.xxxx sometimes remain in the temporary directory. SAPinst GUI and the GUI server are also started. ● Click the icon for the SAPinst output window located in the Windows tray and choose File Exit . End of: Windows | CAUTION If SAPinst cannot find a temporary directory.

End of: Windows | Only valid for: IBM DB2 for i5/OS (Linux/Windows) | ■ Before you start the export of the existing SAP system. For more information.5 Database Independent System Copy Exporting the Source System Using SAPinst Prerequisites CAUTION Make sure that you shut down all SAP Application Servers before the export. End of: UNIX | ■ Only valid for: Windows | Before starting the export steps on the central instance of the source system. you need 60-200 MB free space for the SAPinst executables.com/patches and copy it to directory /usr/sap/<>/SYS/exe/ run/. the target system might be inconsistent.sap.TMP. During the export some archives are written to the program subdirectories and SAPinst aborts if there is not enough space. make sure that you have at least the same amount of disk space available in \\SAPLOC\<SAPSID>\<InstanceName>\SDM \program as is used in \\SAPLOC\<SAPSID>\<InstanceName>\root\origin. some archives are written to the program subdirectories and SAPinst aborts if there is not enough space. The database must still be running. ■ Only valid for: UNIX | You are logged on to your host as user root. make sure that you have at least the same amount of disk space available in /sapmnt/<SAPSID>/<InstanceName>/SDM/program as is used in /sapmnt/<SAPSID>/ <InstanceName>/SDM/root/origin. In addition. you can set one of the environment variables TEMP.4 4. Otherwise. you have to download the current version of R3szchk at http://service. or TMPDIR to another directory with 200 MB free space for the SAPinst executables. End of: UNIX | Only valid for: Windows | You are logged on to your host as a user with the required rights and privileges that authorize you to install the SAP system with the SAPinst tool. see Required User Authorization for the Installation in your installation guide. During the export. End of: IBM DB2 for i5/OS (Linux/Windows) | Only valid for: UNIX | ■ Before starting the export. Only valid for: UNIX | If you cannot provide 200 MB free space in the temporary directory. 36/144 PUBLIC 2010-01-25 . ■ You need at least 60 MB of free space in the installation directory for each ABAP installation option. End of: Windows | ■ Make the Master Installation DVD available. and at least 130 MB of free space in the installation directory for each Java installation option.

4 4. for example. and Performing a Remote Export Using SAPinst [page 131]. make sure that the PATH variable points to a JDK/JRE for AIX 64-bit. below the temporary directory of your operating system. TMP. ■ Only valid for: AIX | If the operating system is AIX 64-bit. or TMPDIR point. Interrupted Installation with SAPinst [page 128].5 Database Independent System Copy Exporting the Source System Using SAPinst ■ Make sure that the DISPLAY environment variable is set to <host_name>:0. which is the current working directory for your installation. ■ Using an alternative installation directory If you want to use an alternative installation directory. TMP. End of: UNIX | 2010-01-25 PUBLIC 37/144 . End of: AIX | End of: UNIX | For more information about SAPinst. Procedure 1./sapinst SAPinst creates a directory called sapinst_instdir.0. ■ Make sure that your SAPINST_JRE_HOME environment variable is set to a valid Java Runtime Environment (JRE). CAUTION Make sure that your current working directory is not an IM_<OS> directory belonging to another operating system. set the environment variable TEMP. see Using SAPinst GUI [page 127]. by using a crontab entry. where <host_name> is the host where the SAPinst GUI is displayed. enter the following: $ cd /sapcd2/IM_HPUX_PARISC $ /sapcd2/IM_HPUX_PARISC/sapinst CAUTION Make sure that your operating system does not delete the contents of the temporary directory /tmp or the contents of the directories to which the variables TEMP. the following causes an error: $ cd /sapcd2/IM_HPUX_IA64 $ /sapcd2/IM_HPUX_PARISC/sapinst To correct this. or TMPDIR. For example. Start SAPinst from the SAP Installation Master DVD as follows: Only valid for: UNIX | Choose one of the following ways: ■ Using the default installation directory (recommended) Enter the following commands: cd <Installation_Master_DVD>/IM_<OS> .

open a command prompt and change to the required directory as follows: <DVD drive>:\IM_WINDOWS_<platform> Enter the following command in a single line: sapinst. End of: UNIX | Only valid for: Windows | ■ Double-click sapinst. The GUI server uses port 21212 to communicate with SAPinst GUI.xxxx). End of: Windows | 2. NOTE ● During installation. 38/144 PUBLIC 2010-01-25 . SAPinst uses port 21200 to communicate with the GUI server. The GUI server uses port 21212 to communicate with SAPinst GUI./sapinst —p. However.xxxxxx. choose Software Life-Cycle Options System Copy <database> Source System <Distribution option> Based on <technical stack> .exe from the following path: <DVD_drive>:\IM_WINDOWS_<platform> SAPinst GUI normally starts automatically by displaying the Welcome screen. GUI server. GUI server. after you have started SAPinst. You get an error message if one of these ports is already in use by another service. Select the corresponding system copy option from the tree structure. On the Welcome screen. and SAPinst GUI.5 Database Independent System Copy Exporting the Source System Using SAPinst Only valid for: UNIX | NOTE ■ During the installation.4 4. SAPinst directly displays the first input dialog without presenting the Welcome screen. you must execute SAPinst using the following parameters: SAPINST_DIALOG_PORT=<free_port_number_sapinst_to_gui_server> GUISERVER_DIALOG_PORT=<free_port_number_gui_server_to_sapinst_gui> ■ To get a list of all available SAPinst properties. if there is only one component to install. 3. according to the sequence of the process flow for the database-specific or the database-independent system copy procedure. and SAPinst GUI. In this case. In this case. SAPinst uses port 21200 to communicate with the GUI server. You get an error message if one of these ports is already in use by another service. and enter the following command: sapinst —p. start SAPinst as described above with the option –p: . go to the directory (%TEMP% \sapinst_exe. the default ports 21200 and 21212 are used for communication between SAPinst. the default ports 21200 and 21212 are used for communication between SAPinst.exe SAPINST_DIALOG_PORT=<free_port_number_sapinst_gui_to_gui_server> GUISERVER_DIALOG_PORT=<free_port_number_gui_server_to_sapinst_gui> ● To get a list of all available SAPinst properties.

you must proceed as described in SAP Note 884452. Optional step for preparing the export. 2010-01-25 PUBLIC 39/144 .XML) ■ Exports the database content ■ Archives the SDM ■ Archives application-specific file system content 4. Database and Central Instance Export If you use the database-specific procedure. NOTE For more information about input parameters in SAPinst. The installation directory is as soon as the first input screen appears. If you generated SQL files with DDL statements (see Generating DDL Statements [page 29]). End of: UNIX | NOTE 5.5 Database Independent System Copy Exporting the Source System Using SAPinst For more information. After you have selected the required option.DBSIZE.XML) Mandatory step for system copy procedure. SAPinst only performs the following steps: NOTE ■ Creates the export directory structure with label files ■ Archives the SDM ■ Archives application-specific file system content. SAPinst performs the following steps: ■ Creates the export directory structure with label files ■ Creates database structure files (*STR) ■ Updates database statistics ■ Calculates the size of the target database (*EXT.DBSIZE. Only valid for: UNIX | CAUTION If your database instance is running on HP PA-Risc. choose Next.EXT. CAUTION Make sure that you choose the system copy options in exactly the order they appear for each system variant. copy the generated files into the SAPinst installation directory as soon as it has been created by SAPinst. see Database-Specific System Copy procedure [page 57] or Database-Independent System Copy [page 25].STR) ■ Updates database statistics (…) ■ Calculates the size of the target database (*. position the cursor on the parameter field and choose F1 . Follow the instructions in the SAPinst input dialogs and enter the required parameters. SAPinst performs the following steps: ■ Creates the export directory structure ■ Creates database structure files (*.4 4. The following table provides an overview of the installation options available for the export: Export Services for a Central System Export Service Remarks Export Preparation NOTE Do not perform this step if you use the database-specific method. CAUTION You must choose Typical when performing a system copy with database tools.

● Displays a dialog that informs you about the error. Solution: 40/144 PUBLIC 2010-01-25 . Only valid for: UNIX | ■ System Copy . ■ If there is not enough disk space in the export directory. You can then move the dump files that have been created from the file system in which the export directory is located to a different file system during the export. ● Try to solve the problem.<nnn>. It is currently not possible to distribute the export over different file systems automatically. Reason: Only members of sapinst UNIX group can access the installation directory. You can now view the log file directly by choosing View Logs. ● Continue the export by choosing Retry. ■ If an error occurs during the processing phase. you have to abort the export with OK and try to solve the problem. Finally. Troubleshooting If an export process aborts due to a hardware failure (for example.4 4. power outage. ● Displays a dialog that informs you about the error. After you have entered all required input parameters. you have to repeat the export of the complete package.0 SR1.5 Database Independent System Copy Exporting the Source System Using SAPinst 6. ■ If an error occurs during the dialog phase. Database-specific procedures only: On the screen SAP SystemDatabase Export choose System Copy Method Use database specific tools . SAPinst starts the export and displays the progress during the processing phase. the log file <package>. file system full.export on UNIX (especially for upgraded systems) Symptom: Processes started as <sid>adm or ora<sid> OS users cannot create or open files in the installation directory. SAPinst: ● Stops the export. Remove the dump files <package>.log and make sure that all tables in the TSK file <package>. You can now: ● View the log file directly by choosing View Logs. the TOC file <package>. ● Abort the export by choosing OK. SAPinst: ● Stops the export.*TSK* have the status flag 'xeq' or 'err' set. This group is created by SAPinst as of from NW 7.TOC. operating system crash). You can then find error messages in the log files SAP*. the R3load database export fails.log.

SAP components based on SAP Web AS and the SAP J2EE Engine. Swing). Edit /etc/group file and associate OS users with sapinst group.5. Procedure The SAP J2EE Engine requires a Java Development Kit (Java™ 2 SDK.2 Running SAPinst on IBM i to Perform the Export 4. Interrupted Installation with SAPinst [page 128]. ■ Set the system path if you install on Windows. Since IBM i does not provide a graphical user interface.4 4. Verify the /etc/group file and check if the sapinst group exists and OS users are members of this group. Continue with the export. If the sapinst group does not exist yet. End of: UNIX | For more information. Standard Edition). and Performing a Remote Export Using SAPinst [page 131].5. 2010-01-25 PUBLIC 41/144 .1 Preparing the Windows Host for the SAP System Installation The Java-based SAPinst graphical user interface (SAPinst GUI) requires a Java Development Kit (Java™ 2 SDK. because the JRE cannot be integrated into the SAPinst GUI executable for all platforms due to licensing issues. you need to download and install it. start SAPinst. see http://service. see Using SAPinst GUI [page 127]. Prerequisites To prepare the system for SAPinst and SAPinst GUI you need to do the following: ■ Necessary operating system versions: Windows NT/2000/2003/XP ■ Check your Java Runtime Environment (JRE) on the host where SAPinst GUI runs. Standard Edition) with graphical capabilities (AWT. make sure a valid JDK version is installed on every host on which you want to install an SAP instance including the SAP J2EE Engine.sap.5 Database Independent System Copy Exporting the Source System Using SAPinst Manually associate <sid>adm and ora<sid> OS users with sapinst group if this association is missing. you must install the JDK on a Windows host to perform the installation with SAPinst. Only valid for: IBM i5/OS | 4. If necessary. Therefore. For more information about the JDK versions that are released for the SAP Web Application Server.2. SAPinst will create this group during startup before the product catalog list is displayed.com/ platforms Product Availability Matrix SAP NetWeaver SAP NetWeaver '04 JSE Platforms NOTE ■ JDK is not part of the SAP shipment.

42/144 PUBLIC 2010-01-25 . End of: SAP SCM | ■ The Windows user account must have administrator rights on the Windows installation host. you need to use the user QSECOFR because the liveCache client software has to be installed by this special user. which conflicts with the previously recommended user SAPINST.2. enter: java -version ■ If you have more than one Java Virtual Machine (JVM) installed on your system (for example.SAP SRM | NOTE The user name SAPINSTUSR and the password SAP are used as examples in the procedures. you have two JDKs with different versions installed). The following requirements apply: ■ The IBM i user profile and the Windows user account must have the same name and password. Procedure Only valid for: SAP CRM.SAP ERP.SAP SRM | Only valid for: SAP SCM | ■ The IBM i user profile must be the user QSECOFR. End of: SAP CRM.SAP NetWeaver.SAP SRM | The IBM i user profile must have user class *SECOFR and all special authorities that belong to user QSECOFR.SAP NetWeaver. However.SAP NetWeaver. in future releases SAP has introduced a group called SAPINST on IBM i.SAP SRM | Windows: 1. make sure that the JAVA_HOME environment variable is set to the valid <JAVA_HOME> directory. ■ Only valid for: SAP CRM. End of: SAP CRM.5 Database Independent System Copy Exporting the Source System Using SAPinst ■ To check the version of an already installed JDK. we used the user SAPINST. Only valid for: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS | 4. For other installations. Make sure that %JAVA_HOME% \bin is included in your system path. Create a local user.SAP ERP.SAP ERP.SAP NetWeaver.SAP ERP.5. NOTE This is different to other installations on IBM i. we recommended that you create user SAPINST or SAPINSTUSR. In former installation documentation.4 4.2 Preparing a Windows User Account and IBM i User Profile For the installation you need to create a user account on your Windows installation host and a user profile on the IBM i you want to install. However for SCM.

enter your installation user name QSECOFR.SAP ERP.SAP NetWeaver. End of: SAP CRM.SAP ERP. You should leave this variable empty! End of: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS | Only valid for: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS | 4.SAP SRM | Only valid for: SAP SCM | To change the user QSECOFR. SAPinst is running on Windows. End of: SAP CRM. you can revert the user profile QSECOFR back to the old values.SAP NetWeaver. After the installation. which is done automatically by the TMKSVR.2. Only valid for: SAP CRM. 7. End of: SAP SCM | 4. End of: SAP SCM | CAUTION You should not set the system variable QIBM_PASE_CCSID.SAP ERP. Only valid for: SAP SCM | In the fields Password and Confirm password. End of: SAP CRM.SAP ERP. enter the password SAP. End of: SAP SCM | 6.SAP NetWeaver. SAPINSTUSR. enter the password of the user QSECOFR on your IBM i. The communication is done using TCP/IP.SAP SRM | Assign the new user SAPINSTUSR to the group Administrators.SAP SRM | 5.SAP SRM | 2.4 4. for example.SAP NetWeaver.SAP NetWeaver.SAP NetWeaver. 2010-01-25 PUBLIC 43/144 .5.SAP ERP. End of: SAP CRM. enter your installation user name. Only valid for: SAP CRM. an installation share on the IBM i host needs to be created and mapped to the Windows installation host.SAP SRM | 3.SAP SRM | In the fields Password and Confirm password. but has to install the product on IBM i. enter the command CRTUSRPRF USRPRF(QSECOFR) LANGID(ENU) CNTRYID (US) CCSID(500).SAP ERP.SAP ERP. Deselect User must change password at next logon. This means that all actions required for IBM i are initiated remotely on Windows but executed locally using the TMKSVR.SAP NetWeaver. In the field User name.5 Database Independent System Copy Exporting the Source System Using SAPinst Only valid for: SAP CRM.SAP ERP. Only valid for: SAP SCM | Assign the new user QSECOFR to the group Administrators.SAP SRM | 8.3 Installing TMKSVR and Creating an Installation Share The TMKSVR is the interface between IBM i and Windows for the installation with SAPinst. Only valid for: SAP SCM | In the field User name.SAP NetWeaver. In addition.SAP SRM | Enter the command CRTUSRPRF USRPRF(SAPINSTUSR) PASSWORD(SAP) USRCLS(*SECOFR) TEXT('Test User for SAP Installation') SPCAUT(*USRCLS) LANGID(ENU) CNTRYID(US) CCSID(500). End of: SAP SCM | IBM i: Only valid for: SAP CRM.

SAP ERP.SAP SRM | Only valid for: SAP SCM | NOTE This user must have the same user ID and password as the user that you are using for the installation on IBM i. Run SETUP. ■ The Installation Master DVD must be inserted in the DVD drive of your Windows host.SAP SRM | NOTE This user must have the same user ID and password as the user that you are using for the installation on IBM i (a user with administrator rights similar to QSECOFR). Log on to your Windows host as the installation user.SAP ERP. End of: SAP SCM | 2. ■ Make sure there is no system variable LANG defining a LOCAL. see Preparing a Windows User Account and IBM i User Profile [page 42]. For more information. For SCM. Procedure 1.SAP NetWeaver.4 4. Only valid for: SAP CRM.5 Database Independent System Copy Exporting the Source System Using SAPinst The TMKSVR has to be installed and an installation share has to be created on all IBM i hosts where instances of an SAP system should be installed. End of: SAP CRM.EXE from the directory IM_OS400_PPC64\TMKSVR on the DVD containing the installation package. The following dialog box appears: 44/144 PUBLIC 2010-01-25 . For more information about how users are prepared.SAP NetWeaver. code page problems might prevent TMKSVR processes from starting. Otherwise. see Preparing a Windows User Account and IBM i User Profile [page 42]. this user must be QSECOFR). Prerequisites ■ An FTP server running on IBM i ■ You must prepare a user. You can start the setup program by double-clicking on it in the Windows Explorer.

SAP NetWeaver.SAP SRM | IBM i Administrator (QSECOFR or similar): Enter the IBM i user. For more information.5 Database Independent System Copy Exporting the Source System Using SAPinst Only valid for: SAP CRM. ■ Only valid for: SAP CRM.SAP SRM | Figure 2: End of: SAP CRM.4 4. End of: SAP CRM. see Preparing a Windows User Account and IBM i User Profile [page 42]. Enter the following values: ■ IBM i Hostname: Enter the name of the IBM i host where you want to install TMKSVR.SAP NetWeaver.SAP NetWeaver.SAP SRM | Only valid for: SAP SCM | ■ System i Administrator (QSECOFR): 2010-01-25 PUBLIC 45/144 .SAP ERP.SAP ERP.SAP NetWeaver.SAP ERP.SAP SRM | Only valid for: SAP SCM | Figure 3: End of: SAP SCM | 3.SAP ERP.

a library named TMKSVR<nn> is created. ■ The users required for the installation are prepared. Only change this port number if you encounter problems during installation because the port is in use. This procedure tells you how to run SAPinst to install one or more SAP instances. the target system might be inconsistent.2.4 Starting SAPinst on IBM i CAUTION This section refers to “installation of an instance”. For more information. which is a synonym for “export an SAP system”. A NetServer share named ROOTBIN is created on the IBM i host. if possible. The database must still be running. During installation. For more information. For more information. For more information.5. see Installing TMKSVR and Creating an Installation Share [page 43]. End of: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS | Only valid for: IBM i5/OS | 4. ■ Make sure that the JAVA_HOME environment variable is set correctly on your Windows host. For more information. 46/144 PUBLIC 2010-01-25 .5 Database Independent System Copy Exporting the Source System Using SAPinst Enter the IBM i user. ■ TMKSVR Instance Port (also referred to as the Dispatcher Port): Leave the value at 59975. Prerequisites CAUTION Make sure that you shut down all SAP Application Servers before the export. SAPinst creates the installation directory \usr\sap\sapinst on IBM i. ■ The Windows host is set up.4 4. TMKSVR00). see Preparing a Windows User Account and IBM i User Profile [page 42]. You can map the share now to your Windows PC or let SAPinst map it during the installation. ■ TMKSVR is up and running: WRKACTJOB SBS (TMKSVR00) (there must be a DISPATCH job). see Preparing the Windows Host for the SAP System Installation [page 41]. Result The installation uses FTP to install and starts the TMKSVR on IBM i. see Preparing a Windows User Account and IBM i User Profile [page 42]. see the documentation INSTALL. with <nn> being the instance number (for example. It describes an installation where SAPinst GUI and SAPinst server are running on the same Windows host. End of: SAP SCM | ■ TMKSVR instance number: Leave the value at 0.PDF on the DVD in directory IM_OS400_PPC64 \TMKSVR. Otherwise.

see Preparing a Windows User Account and IBM i User Profile [page 42]. the default ports SAPinst 21212 and 21213 are used for communication between SAPinst. For more information.. DVD>\IM_OS400_PPC64 Enter the following command in a single line: sapinst. GUI server. and SAPinst GUI. enter the following command: sapinst -p 3. The SAPinst/TMKSVR – Session Parameters dialog box appears and prompts you for the target IBM i parameters.exe from the following path: <Mapped drive>:<copied . You get an error message if one of these ports is already in use by another service.exe SAPINST_DIALOG_PORT=<free_port_number_sapinst_gui_to_gui_server> GUISERVER_DIALOG_PORT=<free_port_number_gui_server_to sapinst_gui> ● For a list of all available SAPinst properties. In this case. Enter your values. SAPinst uses port 21200 to communicate with the GUI server. open a command prompt and change to the required directory as follows: <Mapped drive>:<copied . 2. by double-clicking sapinst. Log on to the Windows host as the installation user..4 4.. DVD>\IM_OS400_PPC64 NOTE ● During the installation.. 2010-01-25 PUBLIC 47/144 .5 Database Independent System Copy Exporting the Source System Using SAPinst Procedure 1. Start SAPinst from the SAP Installation Master DVD in one of the following ways: ■ If using the default installation directory (recommended).

SAPinst performs the following steps: ■ Creates the export directory structure ■ Creates database structure files (*. The following table provides an overview about the available installation services available for a: ■ Central system ■ Distributed system or high-availability system Export Services for a Central System Export Service Remarks Export Preparation NOTE Do not perform this step if you use the database-specific method.DBSIZE.5 Database Independent System Copy Exporting the Source System Using SAPinst Figure 4: 4.4 4. Make sure that you choose the installation services in exactly the order they appear for each system variant. Optional step for preparing the export.EXT.XML) 48/144 PUBLIC 2010-01-25 . 5. for one of the following procedures: ■ Database-Specific System Copy [page 57] ■ Database-Independent System Copy [page 25] CAUTION 6. In the Welcome screen. choose Software Life-Cycle Options System Copy <your database> Source System <System Variant> Based on <AS ABAP and AS Java | AS Java | AS ABAP> . The SAPinst GUI now starts automatically by displaying the Welcome screen.STR) ■ Updates database statistics (…) ■ Calculates the size of the target database (*. according to the sequence of the process flow. Select the corresponding installation service from the tree structure.

XML) Database Instance Export Mandatory step for the database-independent system copy procedure.EXT. ■ Updates database statistics ■ Calculates the size of the target database (*EXT. NOTE You need to perform this step on the central instance Before you perform this step.4 4. SAPinst performs the following steps: ■ Creates the export directory structure ■ Creates database structure files (*.DBSIZE. ■ Archives the SDM ■ Archives application-specific file system content Export Preparation 7. SAPinst only performs the following steps: NOTE ■ Creates the export directory structure with label files ■ Archives the SDM ■ Archives application-specific file system content.5 Database Independent System Copy Exporting the Source System Using SAPinst Export Service Remarks Database and Central Instance Export If you use the database-specific procedure. NOTE You need to perform this step on the database instance ■ Do not perform this step if you use the database-specific method.DBSIZE.XML) ■ Exports the database content ■ Archives the SDM ■ Archives application-specific file system content Remarks Export Services for a Distributed System or a High-Availability System Export Service Optional step for the database-independent system copy procedure to prepare the export. After you have selected the required installation service.DBSIZE. SAPinst performs the following steps: ■ You must perform this step ■ Creates the export directory structure with label files before you perform Central ■ Creates database structure files (*STR) Instance Export. choose Next. NOTE Do not perform this step if you use the You need to perform this step on the database instance host. host. must have completed the Database SAPinst performs the following steps: Instance Export. 8.XML) ■ Exports the database content Central Instance Export Mandatory step for database-independent system copy procedure.STR) ■ Updates database statistics(…) ■ Calculates the size of the target database (*. SAPinst performs the following steps: ■ Creates the export directory structure with label files ■ Creates database structure files (*STR) ■ Updates database statistics ■ Calculates the size of the target database (*EXT. Choose Next 2010-01-25 PUBLIC 49/144 . ■ Creates the export directory structure with label files. you host. database-specific method. Mandatory step for system copy procedure.

power outage. If you generated SQL files with DDL statements (see Generating DLL Statements [page 29]). ● Abort the installation by choosing OK. SAPinst starts the installation and displays the progress of the installation. When the installation has successfully completed. you must abort the installation with OK and try to solve the problem. After you have entered all required input parameters. CAUTION You must choose Typical when performing a system copy with database tools. the TOC file <package>. ● Displays a dialog that informs you about the error. SAPinst: ● Stops the installation.*TSK* have the status flag 'xeq' or 'err' set. 3. Remove the dump files <package>.TOC. Follow the instructions in the SAPinst input dialogs and enter the required parameters. You can now directly view the log file by choosing View Logs. End of: IBM i5/OS | End of: IBM i5/OS | 50/144 PUBLIC 2010-01-25 . Finally. Troubleshooting CAUTION If an export process aborts due to a hardware failure (for example. NOTE For more information about input parameters in SAPinst. You can now directly view the log file by choosing View Logs. you have to repeat the export of the complete package. SAPinst: ● Stops the installation. ● Try to solve the problem.log and make sure that all tables in the TSK file <package>. ■ If an error occurs during the processing phase. position the cursor on the parameter field and choose F1 . the log file <package>. file system full. copy the generated files into the SAPinst installation directory as soon as it has been created by SAPinst: 1. The installation directory has been created as soon as the first input screen appears. Choose Database and Central Instance Export 2. the screen Finished installation is displayed. ● Displays a dialog that informs you about the error.<nnn>. operating system crash).5 Database Independent System Copy Exporting the Source System Using SAPinst NOTE 9. For more information. see Interrupted Installation with SAPinst [page 128]. ● Retry the installation by choosing Retry. ■ If an error occurs during the dialog phase.4 4. Choose Next.

■ If the export was completed successfully. ● If the export was completed successfully but the import was cancelled when loading the table content.5. cancel it as well. ■ To skip package processing. set the status ◆ for export_state.5 Database Independent System Copy Exporting the Source System Using SAPinst 4. proceed as follows: ● If the errors in export and import relate to the same table. EXAMPLE For example. but the import is cancelled with errors.4 4. if package processing failed and the package state has the value –. Procedure ■ To restart package processing.) ■ If the package is currently being processed (the package state is ?).3 Restarting R3load Processes The state file allows package states to be manually updated to restart failed R3load processes.properties from '+' to '0'. you need to cancel the R3load process. Restarting R3load Processes Using the Socket Option There are four possible situations where an R3load restart may be required.properties from '+' to '0' ◆ for the TSK file of the export from 'ok' to 'err' ■ If both the export and the import are cancelled with errors. set the status for export_state. EXAMPLE Export Import Table name TAB_1 TAB_2 TAB_3 Status ok err xeq Table name TAB_1 TAB_2 TAB_3 Status ok ok err 2010-01-25 PUBLIC 51/144 . ● If the errors relate to different tables. (This is not recommended. proceed as follows: ● If the export was successful but the import was cancelled when creating the index or the primary key. set the package state from – to 0. ■ Sockets only: You cannot restart processes. there is nothing to do. If one of the corresponding R3load processes (export or import) is still running. Then restart SAPinst to continue with the system copy. there is nothing to do. then any manual modifications to the package state are ignored. the state can be set to 0 and processing of the package is restarted. First of all. set the status of the first object with errors (export as well as import) in the TSK file and in the *state* file to 'err'. set the package state from 0 or – to +. To continue with the system copy proceed as follows: ■ If both the import and the export are completed successfully. because it can cause inconsistent data files or database content.

For more information. The entry in the *state* file also must be set from '+' to '0'. see Installing the Target System [page 54]. 3. 2. Transfer the Java export files to the central system target host. communication type Exchange Directory.6 Setting Up the Target System Purpose Use SAPinst to install the target system and import the database files that you have exported from the source system. see Preparing the Export [page 33]) on the source system. perform the following steps: 1. 2. For more information. Install the target system. If you use the FTP Exchange option during the export (transfer type FTP. Prepare the central system host for the installation of your target system as described in the installation guide for your SAP system solution. Install the target system.6 Database Independent System Copy Setting Up the Target System Export Import TAB_4 xeq TAB_4 xeq The first object with errors here is TAB_2 (export). Distributed System or High-Availability System Perform the following steps on the relevant installation hosts of your target system: 52/144 PUBLIC 2010-01-25 . Transfer the Java export files to the central system target host. see Transferring the Export Files to the Target Host [page 53]. perform the following steps: 1. see Transferring the Export Files to the Target Host [page 53]. ■ If the import is completed successfully. If you did not prepare the export on the source system. If you have already prepared the export (for more information. 2. on the screen SAP SystemCommunication Parameters for Export). 3. More Information R3load Processes Using the Migration Monitor [page 111].properties from '-' to '+'. Process Flow Central System Perform the following steps on the central system host: 1.4 4. If required install additional dialog instance(s) on (the) dialog instance host(s) as described in the installation guide for your SAP system solution. 4. For more information. which have been generated in the Preparing the Export [page 33] step on the source system. For more information. make sure that you have transferred the files. That means that in the import TSK file the status for TAB_2 must be set from 'ok' to 'err'. see Installing the Target System [page 54]. but the export was cancelled with errors. you can set the status in the export_state.

see Transferring the Export Files to the Target Host [page 53]. install additional dialog instance(s) on (the) dialog instance host(s) as described in the installation guide for your SAP system solution. NOTE 3. create a directory <EXPDIR> with sufficient space for the database export files available. ■ If you did not prepare the export (for more information.4 4. 3. perform the following steps: 1. 4. For more information. Install the database instance of the target system. Copy all files and directories (recursively) that are located on the source host in the migration export directory <EXPDIR> from the source host to the target host. Check the permissions of the transferred files on the target host. perform the following steps: 1. 2. see Preparing the Export [page 33]) on the source system. All files have to be accessible for user <sapsid>adm of the target system. 2. If you transfer the files with file transfer protocol (ftp). If required. the database instance host. 2. see Preparing the Export [page 33]) on the source system. see Installing the Target System [page 54]. 4. which were generated in the Preparing the Export [page 33] step on the source system. 5. on the screen SAP SystemCommunication Parameters for Export). Transfer the Java export files to the central system target host. see Installing the Target System [page 54]. Install the database instance of the target system. If you use the FTP Exchange option during the export (transfer type FTP. For more information. install the central instance of the target system. see Transferring the Export Files to the Target Host [page 53]. 2. make sure that you have transferred the files.1 Transferring the Export Files to the Target Host Procedure 1. Install the central services instance for the target system as described in the installation guide for your SAP system solution. and the central instance host for the installation of the corresponding instances of your target system as described in the installation guide for your SAP system solution.6. On the central instance host. For more information. Transfer the Java export files to the central system target host. make sure that you use binary mode for transferring the files. You perform the following steps on the database instance host: ■ If you have already prepared the export (for more information. 3. For more information.6 Database Independent System Copy Setting Up the Target System 1. 2010-01-25 PUBLIC 53/144 . On the target host. communication type Exchange Directory. Prepare the central services instance host.

If you have not exported into the same <EXPDIR> already. Start SAPinst as described in the installation documentation for your SAP solution based on SAP NetWeaver 7. End of: Windows | Only valid for: UNIX | Make sure there is enough free space on the target system for the database load. If the database software has already been unpacked or installed. End of: UNIX | NOTE As of SAP NetWeaver 7. Prepare the target system host as described in the installation guide of your SAP solution based on SAP NetWeaver 7. then you have to merge the two <EXPDIR> directories from the central instance export and from the database instance export before starting the target system installation. look at the file DBSIZE. End of: IBM DB2 for Linux and UNIX and Windows | 2.2 Installing the Target System Prerequisites Only valid for: Windows | Make sure there is enough free space on the target system for the database load.6. To find out the size of the export and the sizes of the tablespaces or dbspaces that will be created. or if the database already exists.0. To find out the size of the export and the sizes of the tablespaces or dbspaces that will be created.0 EHP 1.XML located in the directory <DRIVE>:\<EXPDIR>\DB\<DATABASE>. but is performed automatically by SAPinst. 4. Only valid for: IBM DB2 for Linux and UNIX and Windows | NOTE Make sure that you read the information provided in section Setup of Database Layout in the installation documentation.4 4. make sure you have installed the most current version of SAPinst to avoid performance 54/144 PUBLIC 2010-01-25 . Procedure 1.XML located in the directory <EXPDIR>/DB/<DATABASE>. RELOAD is no longer available as an executable installation service. CAUTION If you plan to use Advanced Configuration options during the SAP System Database Import. look at the file DBSIZE.0 EHP 1. the files created by the export of the central instance and the files created by the export of the database instance have to be located in the same <EXPDIR> directory for the installation of the target system.6 Database Independent System Copy Setting Up the Target System NOTE If your source system is a distributed system. SAPinst recognizes this automatically and skips the related steps.

NOTE On the screen SAP System > General Parameters.sap. sapinst_instdir) under the following directories: ● UNIX: /usr/sap/<SAPSID> Windows: \usr\sap\<SAPSID> ● UNIX: /sapmnt/<SAPSID> Windows: \sapmnt\<SAPSID> ■ If you perform a Unicode conversion.Select the Database Instance Installation Method choose the option Standard System Copy/Migration (load-based): The SAP data dump from the MIGRATION EXPORT CD image that you created during the export is loaded in the newly installed SAP system database. On the Welcome screen of the SAP Installation Master DVD.0 EHP1.6 Database Independent System Copy Setting Up the Target System 3. navigate to the following folder according to the requirements of your target system: Software Life-Cycle Options System Copy <database> Target System <Distribution option: Central System / Distributed System / High-Availability System> Based on <Stack option> AS ABAP and Java / AS Java / AS ABAP> . Run the installation service(s) required for your system copy in the sequence they are listed in the specific folder and according to process flow in Setting Up the Target System Using SAPinst [page 52].4 4.0 EHP 1 or higher. Only valid for: IBM DB2 for Linux and UNIX and Windows | CAUTION ■ Make sure that you take the information about automatic storage that is provided in the Running SAPinst section in the appropriate installation guide into consideration. as default. 2010-01-25 PUBLIC 55/144 . 4. On the screen Database . the Unicode System option is selected. problems during the dialog phase. To install the target system. You can find the latest version of SAPinst at http:// service. End of: IBM DB2 for Linux and UNIX and Windows | CAUTION ■ Do not create the installation directory (for example. in which the DYNPSOURCE table will be created in the target database. follow the instructions in the SAPinst input dialogs and enter the required parameters.com. the data import into the target system might abort because of missing space in the database tablespace or dbspace. 5. You can only deselect this option if you perform the system copy for a non-Unicode SAP system that has been upgraded to SAP NetWeaver 7. Enlarge the database or database container. ■ The option Deferred Table Creation is not supported for load-based system copies for SAP systems that are not based on SAP NetWeaver 7. The required size for the table will be fifteen times larger than in the non-Unicode source system.

NOTE The Java engine is not started automatically. 56/144 PUBLIC 2010-01-25 . 7.6 Database Independent System Copy Setting Up the Target System 6. refer to Restarting R3load Processes [page 51]. just restart SAPinst. choose the Parallel Export / Import option.4 4. If you perform a heterogeneous system copy. The import continues with the table that was not imported successfully. NOTE If you have to restart the import after an error. you have to start the Java engine manually. For more information about restarting failed R3load processes. Complete the installation as described in the installation documentation for your SAP component. enter the migration key on the Database Import screen. You must have run the service Prepare the Export on the source system [page 33] if you want to use the parallel export/ import option for the installation of the target system. After the target system has been installed and the follow-up activities (refer to Follow-Up Activities [page 81]) have been performed. enter the path to the export directory <EXPDIR>. NOTE 8. If you want to perform export and import in parallel. When SAPinst displays the DVD / CD browser window and asks for the Export Migration CD.

Follow the instructions on the SAPinst screens until SAPinst requests you to install the database software and to perform the database backup/restore. 3. and technology. Databasespecific methods are not available for all database systems. which contains the data of the exported system. create a MIGRATION EXPORT CD image. For more information about methods available for your database. Process Follow the sequence of steps described in the process flows below for a: ■ Central System ■ Distributed System ■ High Availability System Central System To perform the export for a central system. 1. 2010-01-25 PUBLIC 57/144 . End of: Windows | 2. <your SAP version> Software Life-Cycle Options System Copy Oracle Source System Export Central System Based on AS ABAP and AS Java Database and Central System Export Generate the control file structure for the target database [page 60]. Install the database software as described in the installation guide of your SAP solution. create an offline backup of the source database [page 65]. and which you use to install the target system. Only valid for: Windows | Process Flow on the Target System 1. EXAMPLE 2. Run SAPinst on UNIX or Windows [page 34] to create the export directory structure with labels and to archive SDM and application-specific file system content. Only valid for: UNIX | Prepare the target system [page 66]: 1.5 Database-Specific System Copy 5 Database-Specific System Copy The following sections describe database-specific methods for the homogeneous system copy. In SAPinst. and then Database and Central System Export. SAP system. If required. choose the installation option that corresponds to your database. you need to proceed as follows on the central system host: Process Flow on the Source System (Export) When performing the export. refer to Planning [page 13] and to the SAP Notes describing the homogeneous system copy for your database system.

2. If required. On the database instance host. Only valid for: Windows | On the database instance host. On the database instance host. install the database software. 3. restart SAPinst as described in the installation guide of your SAP solution. SAP system. Create the database file system (if it does not yet exist). follow the instructions on the SAPinst screens until SAPinst requests you to install the database software and to perform the database backup/restore. Distributed System or High Availability System To perform the export for a distributed or high-availability system. End of: UNIX | Only valid for: Windows | Follow the instructions on the SAPinst screens until you are requested to perform the database backup/restore. EXAMPLE <your SAP version> Software Life-Cycle Options System Copy your database Source System Export Distributed System Based on AS ABAP and AS Java Database and Central System Export Process Flow on the Target System 1. proceed as follows: Process Flow on the Source System (Export) When performing the export. On the database instance host of the source system. choose the installation option that corresponds to your database. 2. On the central instance host. NOTE If required. To complete the system copy. 3. create the database file system (if not yet existing). install the database software as described in the installation guide of your SAP solution. 3. End of: Windows | 2. Install the database software. End of: UNIX | 58/144 PUBLIC 2010-01-25 . which contains the data of the exported system. generate the control file structure for the target database [page 60]. and then Database and Central System Export. Only valid for: UNIX | Prepare the target system [page 66]: 1. 3. you create a MIGRATION EXPORT CD image. and which you use to install the target system. On the database instance host. and technology. you have to perform the follow-up activities [page 81]. In SAPinst. 1.5 Database-Specific System Copy 2. End of: Windows | 4. create an offline backup of the source database [page 65]. on the database instance host. run SAPinst on UNIX or Windows [page 34] to create the export directory structure with labels and to archive SDM and application-specific file system content.

jar must exist in the <ORACLE_HOME>/jdbc/lib directory (installed using a standard Oracle installation). End of: Windows | 4. ■ You cannot change the database schema and the table space names. Only valid for: Oracle | 5.4. follow the instructions on the SAPinst screens until you are requested to perform the database backup/restore. ■ Source system host and target system host must be different.1 or higher is installed on the database instance. Prerequisites ■ You must use the same Oracle release and patch level for your database in the source and target system. Disadvantages ■ Backup/copy of database files in a heterogeneous environment is not possible because the hardware of the source and target systems must be binary-compatible. On the database instance host. ■ You must have prepared your system for SAPinst [page 21]. or the file system of your source host. ■ This method is faster than the R3load and Jload method. Use SAPinst for installation on the target system host as described in the installation documentation for your SAP component.5 5. Advantages ■ You can use existing offline or online backups. You can use an offline backup. an online backup. NOTE If required. This method is suitable for creating an exact copy of an existing database. The source of the copy is a complete data backup of your source database. ■ You must shut down the SAP system and the database when you create an offline backup manually or an offline backup with BR*Tools. 2010-01-25 PUBLIC 59/144 . ■ The classes12. To complete the system copy. restart SAPinst as described in the installation guide of your SAP solution.1 Database-Specific System Copy Oracle-Specific Procedure Only valid for: Windows | 3. Only the SAPinst steps for setting up and loading the database steps are different. you have to perform the follow-up activities [page 81]. make sure that JRE version 1. you can create a homogeneous copy of an Oracle database by copying database files.1 Oracle-Specific Procedure Purpose In an SAP system environment. ■ If your source system is an ABAP only system.

Create an installation directory <INSTDIR> (UNIX: with permissions 777) on the source system. If your source system uses the US7ASCII character set. 4. Copy the ORABRCOPY. ■ For security reasons.SAR archive from the SAP Installation Master DVD to the installation directory and extract it using SAPCAR. SAPinst prompts for the character set during the installation (key: Database Character Set). Prerequisites RECOMMENDATION We recommend that you shut down the SAP system before you perform the following steps.5 5.SQL to the current working directory. To find out the character set used by the source system. The installation default is WE8DEC or UTF8 for Unicode systems.SAR archive.SAR End of: Windows | 3. Make sure that all redo log groups are archived Start the OraBRCopy tool as an OS user with Oracle DBA privileges: ■ Log on as one of the following users: 60/144 PUBLIC 2010-01-25 . You can find the archive in the following directory on the Installation Master DVD: Only valid for: UNIX | <DVD-DIR>:/COMMON/INSTALL/ORA/ORABRCOPY. connect to the source database as user sap<schemaid> or sapr3 with sqlplus and enter: SELECT * FROM V$NLS_PARAMETERS.1 Database-Specific System Copy Oracle-Specific Procedure ■ The JAVA_HOME environment variable must point the JRE directory. 2. Procedure 1.1. which can be used without further adaptations on the target system.SAR End of: UNIX | Only valid for: Windows | <DVD-DRIVE>:\COMMON\INSTALL\ORA\ORABRCOPY. For more information about the OraBRCopy tool. 5. ■ The source and target systems must be binary compatible.1 Generating the Control File Structure The OraBRCopy Java tool writes a file CONTROL. NOTE Note that you can also perform a system copy from 32-bit systems to 64-bit systems and vice versa (same operating system assumed) even if source and target system are not binary compatible. the source and target systems must run on different hosts. The database must still be running.pdf. you must choose this character set when installing the target system. refer to the documentation ORABRCopy. which is part of the OraBRCOPY.

SQL written in bold should be compared to the trace file: REM ==================================================================== REM CONTROL.SQL. restarts the database.TRC. the database must be up and running. entries of CONTROL. and performs the required log switches.log 5./ora_br_copy.1 Database-Specific System Copy Oracle-Specific Procedure ● ora<dbsid> ● <sapsid>adm ■ If you perform an offline manual copy.SQL. this command must not contain the parameter —forceLogSwitches. Example for Windows In the following example for Windows.ora in your installation directory.bat –generateFiles —targetSid <TARGET_DBSID> —password <system's password> —listenerPort <listener port> NOTE During the online backup. and performs the required log switches.TRC trace file as follows. Verify and.SQL control file using the CONTROL.ora in your installation directory. enter the following commands: ● On UNIX: . To ensure this.sh –generateFiles –forceLogSwitches —targetSid <TARGET_DBSID> —password <system's password> —listenerPort <listener port> ● On Windows: ora_br_copy. update the CONTROL.sh –generateFiles —targetSid <TARGET_DBSID> —password <system's password> —listenerPort <listener port> ● On Windows: ora_br_copy. ■ If you perform an offline or online backup using BR*Tools. CONTROL. if necessary./ora_br_copy. and init<targetSID>.TRC.bat –generateFiles –forceLogSwitches —targetSid <TARGET_DBSID> —password <system's password> —listenerPort <listener port> The tool creates the files CONTROL.brcopy. and init<targetSID>. enter the following commands: ● On UNIX: .SQL REM REM SAP AG Walldorf 2010-01-25 PUBLIC 61/144 . The tool creates the files CONTROL. check the log file: <INSTDIR>/ora. CONTROL. NOTE If an error occurs.5 5. shuts down.

DBF'.0 x86 CONNECT / AS SYSDBA STARTUP NOMOUNT CREATE CONTROLFILE REUSE SET DATABASE "NEW" RESETLOGS ARCHIVELOG MAXLOGFILES 255 MAXLOGMEMBERS 3 MAXDATAFILES 1022 MAXINSTANCES 50 MAXLOGHISTORY 1134 LOGFILE GROUP 1 ( 'D:\ORACLE\NEW\ORIGLOGA\LOG_G11M1. Anwendungen und Produkte in der Datenverarbeitung REM REM (C) Copyright SAP AG 2004 REM ==================================================================== REM Generated at: REM Fri Sep 17 08:33:25 CEST 2005 REM for target system NEW REM on REM Windows 2000 5.1 Database-Specific System Copy Oracle-Specific Procedure REM Systeme. 'D:\ORACLE\NEW\MIRRLOGA\LOG_G13M2. GROUP 2 ( 'D:\ORACLE\NEW\ORIGLOGB\LOG_G12M1.DBF'. GROUP 4 ( 'D:\ORACLE\NEW\ORIGLOGB\LOG_G14M1.DBF'.5 5. 'D:\ORACLE\NEW\MIRRLOGB\LOG_G12M2. 'D:\ORACLE\NEW\MIRRLOGB\LOG_G14M2. 'D:\ORACLE\NEW\MIRRLOGA\LOG_G11M2. GROUP 3 ( 'D:\ORACLE\NEW\ORIGLOGA\LOG_G13M1.DBF'.DBF' ) SIZE 50M.DBF' ) SIZE 50M 62/144 PUBLIC 2010-01-25 .DBF' ) SIZE 50M.DBF' ) SIZE 50M.

DATA5'. 'D:\ORACLE\NEW\SAPDATA4\IMS700_11\IMS700. 'D:\ORACLE\NEW\SAPDATA3\IMS_4\IMS. 'D:\ORACLE\NEW\SAPDATA3\IMS_1\IMS.DATA10'.DATA8'. too.DATA7'. startup restrict 2010-01-25 PUBLIC 63/144 .DATA5'. 'D:\ORACLE\NEW\SAPDATA1\IMS700_2\IMS700. 'D:\ORACLE\NEW\SAPDATA3\IMS_3\IMS. If you want to upgrade your database from 32-bit to 64-bit. 'D:\ORACLE\NEW\SAPDATA4\IMS_9\IMS.DATA3'. 'D:\ORACLE\NEW\SAPDATA2\IMS700_9\IMS700.DATA1'.DATA4'. 'D:\ORACLE\NEW\SAPDATA4\IMS_8\IMS. 'D:\ORACLE\NEW\SAPDATA2\IMS700_8\IMS700. 'D:\ORACLE\NEW\SAPDATA4\IMS_7\IMS.DATA2'.DATA1'. NOTE In the above example for Windows. ALTER TABLESPACE PSAPTEMP ADD TEMPFILE 'D:\ORACLE\NEW\SAPDATA3\TEMP_1\TEMP. 'D:\ORACLE\NEW\SAPDATA2\IMS700_6\IMS700. 'D:\ORACLE\NEW\SAPDATA1\IMS700_3\IMS700.DATA6'. 'D:\ORACLE\NEW\SAPDATA1\IMS700_4\IMS700.SQL written in bold should be compared to the trace file.DATA9'. entries and values of CONTROL. 'D:\ORACLE\NEW\SAPDATA1\IMS700_1\IMS700.DATA1'. 'D:\ORACLE\NEW\SAPDATA2\ROLL_1\ROLL.DATA4'.DATA1'. ALTER DATABASE OPEN RESETLOGS.DATA8'. Changes to be made 1. add the following lines at the bottom of the CONTROL. 'D:\ORACLE\NEW\SAPDATA4\IMS_5\IMS.DATA2'.5 5. 'D:\ORACLE\NEW\SAPDATA2\IMS700_7\IMS700.SQL file: shutdown immediate.DATA1' . 'D:\ORACLE\NEW\SAPDATA3\IMS_2\IMS. 'D:\ORACLE\NEW\SAPDATA2\IMS700_5\IMS700. The changes to be made are valid for UNIX.DATA7'.DATA11'.DATA6'. 'D:\ORACLE\NEW\SAPDATA1\IMSUSR_1\IMSUSR.1 Database-Specific System Copy Oracle-Specific Procedure DATAFILE 'D:\ORACLE\NEW\SAPDATA1\SYSTEM_1\SYSTEM.DATA9'. 'D:\ORACLE\NEW\SAPDATA4\IMS_6\IMS.DATA1' SIZE 350M REUSE AUTOEXTEND OFF. 'D:\ORACLE\NEW\SAPDATA3\IMS700_10\IMS700.DATA3'.

5. 4..DATA1'.1 Database-Specific System Copy Oracle-Specific Procedure spool utlirp. Choose between the following possibilities: Performing an offline backup manually or an offline or an online backup with BR*Tools.DBF' ) SIZE 50M.DATA1' … The count of the data files must be equal to the count of the corresponding data files in the trace file.DATA1' SIZE 350M REUSE AUTOEXTEND OFF. GROUP 1 ( 'D:\ORACLE\NEW\ORIGLOGA\LOG_G11M1. 5. 3. … 'D:\ORACLE\NEW\SAPDATA1\IMS700_1\IMS700. 'D:\ORACLE\NEW\SAPDATA1\SYSTEM_1\SYSTEM. ALTER TABLESPACE PSAPTEMP ADD TEMPFILE 'D:\ORACLE\NEW\SAPDATA3\TEMP_1\TEMP. 'D:\ORACLE\NEW\MIRRLOGA\LOG_G11M2.5 5. 6. The numbers must be greater than or equal to the corresponding numbers in the trace file.2 Creating a Backup If required.sql spool off alter system disable restricted session.DBF'. ■ Creating an Offline Backup Manually [page 65] ■ Creating an Offline or Online Backup with BR*Tools [page 65] 64/144 PUBLIC 2010-01-25 . 'D:\ORACLE\NEW\SAPDATA3\IMS_1\IMS. The number of rows with ALTER TABLESPACE must be equal to the number of corresponding rows in the trace file.1.DATA1'. Group 2 ( … The sizes of the respective groups must be equal to the sizes of the corresponding groups in the trace file. create a backup.log @?/rdbms/admin/utlirp.. 2. MAXLOGFILES 255 . … The size must be equal to the corresponding size in the trace file.

The backup strategy must simply be valid for restore and recovery. You do not have to perform any preparations for the actual transfer now. NOTE If you choose this manual offline backup method. complete or incremental. with or without RMAN.2 Creating an Offline or Online Backup with BR*Tools You can use any backup strategy supported by BR*Tools as the basis for a system copy: offline or online. Proceed with the next step. Proceed as described in the SAP Library at: help.2. 5.com/nw70 SAP NetWeaver 7.1. see Restoring Database Files on the Target System [page 68]. you also have to restore the database files on the target system manually.2. the external backup tools must be configured so that a restore is possible on the target host. stop the database (normal shutdown) and perform a complete offline backup. and so on. Procedure CAUTION To ensure that no changes are made to the file system during backup. you can use it (provided that redo logs were cleaned up with forced log switches). For more information.TRC created by OraBrCOPY to determine the file system trees that have to be saved.1. 2010-01-25 PUBLIC 65/144 . with or without BACKINT.sap.1 Database-Specific System Copy Oracle-Specific Procedure 5.5 5.0 Library (including Enhancement Package 1) Englishh SAP NetWeaver Library Administrator’s Guide Technical Operations for SAP NetWeaver General Administration Tasks Database Administration Database Administration for Oracle BR*Tools for Oracle DBA BR*Tools in Action Backup and Database Copy with BR*Tools . You can use the trace file CONTROL.1 Creating an Offline Backup Procedure There are different possibilities to prepare the actual transfer of the database files: ■ If you have an up-to-date offline backup. In addition for BACKINT and RMAN.0 including Enhancement Package 1 SAP NetWeaver 7. on tape) or if you have to perform the database shutdown at a certain time. ■ You stop the database (normal shutdown) and copy the database files when the actual transfer to the target system takes place. stop the Software Deployment Manager (SDM). This means that a complete restore and recovery of the source database must be possible. ■ If you want to transport the database file (for example.

1. you cannot change the database schema and the table space names of the new target system. you also have to restore the database files on the target system with BR*Tools. When installing the target central instance. Procedure 1. ■ Proceed until SAPinst stops to restore the database files on the target system.3 Preparing the Target System Prerequisites Make sure that sapdata<n> file systems on the target system host are large enough. CAUTION When you perform a system copy with the Oracle backup/restore method. extract the Oracle stage archives manually and install the Oracle Software as described in the installation documentation for your SAP solution. The following message is displayed: SAPinst now stops the installation. 3. The schema names of the source and target system must be identical.5 5..0 including Enhancement Package 1 Software Life-Cycle Options System Copy Oracle Target System <Central System | Distributed System | High-Availability System> . 5. If they do not exist. If necessary. For more information. CAUTION On the Welcome screen. database instance. Please proceed as follows:. ■ When SAPinst prompts for the installation type.1 Database-Specific System Copy Oracle-Specific Procedure NOTE If you choose a backup method with BR*Tools. choose the required installation service: SAP NetWeaver 7. Install the target SAP system with SAPinst as described in the installation documentation for your SAP solution. choose Homogeneous System Copy (Backup/ Restore).. or dialog instance make sure that you enter the correct database schema names (which are the database schema name of the source system). see Restoring the Database Files on the Target System with BR*Tools [page 69]. create the following directories on the target system: ■ UNIX: ● ● ● ● ● ● /oracle/<TARGET_DBSID>/mirrlog<x> /oracle/<TARGET_DBSID>/origlog<x> /oracle/<TARGET_DBSID>/sapdata<x> /oracle/<TARGET_DBSID>/sapreorg /oracle/<TARGET_DBSID>/saparch /oracle/<TARGET_DBSID>/oraarch 66/144 PUBLIC 2010-01-25 . 2.

. In the next dialog. All directories must be owned by the user ora<target_dbsid>.. In the Windows Explorer. right-click the Oracle root directory and choose Properties. SAP_<SAPSID>_GlobalAdmin (domain installation). 2010-01-25 PUBLIC 67/144 . Under Security. 4.1 Database-Specific System Copy Oracle-Specific Procedure 4.5 5. enter the following command: chown ora<target_dbsid>:dba <directory> End of: UNIX | 6. 2. and SAP_<SAPSID>_LocalAdmin (local installation) for all directories as follows: 1. Uncheck Allow inheritable permissions from the parent. Administrators. ● /oracle/<TARGET_DBSID>/saptrace ● /oracle/<TARGET_DBSID>/saptrace/background ● /oracle/<TARGET_DBSID>/saptrace/usertrace ● /oracle/<TARGET_DBSID>/origlogA/cntrl ● /oracle/<TARGET_DBSID>/sapdata1/cntrl ● /oracle/<TARGET_DBSID>/saparch/cntrl ● /oracle/<TARGET_DBSID>/sapcheck ■ Windows: ● <drive>:\oracle\<TARGET_DBSID>\mirrlog<x> ● <drive>:\oracle\<TARGET_DBSID>\origlog<x> ● <drive>:\oracle\<TARGET_DBSID>\sapdata<x> ● <drive>:\oracle\<TARGET_DBSID>\sapreorg ● <drive>:\oracle\<TARGET_DBSID>\saparch ● <drive>:\oracle\<TARGET_DBSID>\oraarch ● <drive>:\oracle\<TARGET_DBSID>\saptrace ● <drive>:\oracle\<TARGET_DBSID>\saptrace\background ● <drive>:\oracle\<TARGET_DBSID>\saptrace\usertrace ● <drive>:\oracle\<TARGET_DBSID>\origlogA\cntrl ● <drive>:\oracle\<TARGET_DBSID>\sapdata1\cntrl ● <drive>:\oracle\<TARGET_DBSID>\saparch\cntrl ● <drive>:\oracle\<TARGET_DBSID>\sapcheck Make sure that the following directories are empty (except the subdirectory saparch/cntrl): /oracle/<TARGET_DBSID>/saparch and /oracle/<TARGET_DBSID>/oraarch <drive>:\oracle\<TARGET_DBSID>\saparch and <drive>:\oracle\<TARGET_DBSID>\oraarch Only valid for: UNIX | 5. choose Copy to copy the permission entries that were previously applied from the parent to this object.. Only valid for: Windows | Set the security settings for the built-in accounts and groups SYSTEM. choose Advanced. To achieve this. 3.

1 Database-Specific System Copy Oracle-Specific Procedure 5.4 Restoring Database Files on the Target System CAUTION If you do not use an offline backup. 7. Copy the following files from the source to the target system host either by using an offline backup or by copying the listed files from the source directories to the target directories. 68/144 PUBLIC 2010-01-25 . SAP_<DBSID>_GlobalAdmin. 7. make sure that you shut down the database on the source system before you copy the listed files from the source to the target directories. End of: Windows | Restore the database files on the target system either manually (see Restoring Database Files on the Target System Manually [page 68]) or with BR*Tools (see Restoring the Database Files on the Target System with BR*Tools [page 69].1. the source data files and log files are not located in the directories shown in the table. Procedure 1. 5. Choose OK. or SAP_<DBSID>_LocalAdmin to Full Control. but copy the database files directly from the source to the target system host. Directories on UNIX: Source and Target Directory /oracle/<DBSID>/sapdata<x> /oracle/<DBSID>/origlog<x> /oracle/<DBSID>/mirrlog<x> Files All files All files All files CONTROL.ora Directories on Windows: Source and Target Directory <drive>:\oracle\<DBSID>\sapdata<x> <drive>:\oracle\<DBSID>\origlog<x> <drive>:\oracle\<DBSID>\mirrlog<x> Files All files All files All files CONTROL.SQL source: <INSTDIR> target: <SAPINST_INSTDIR> source: <INSTDIR> target: /oracle/<DBSID>/<DB_VERSION>_<BIT>/dbs init<TARGET_DBSID>. Set the permissions for the above-mentioned accounts SYSTEM. Administrators. Delete all other accounts.ora If you use an existing offline backup. 6.SQL source: <INSTDIR> target: <SAPINST_INSTDIR> source: <INSTDIR> target: \oracle\<DBSID>\<DB_VERSION>_<BIT>\database NOTE init<TARGET_DBSID>. then proceed with SAPinst.5 5.

make the corresponding changes in the files control. Make sure that the control files are not restored. For more information about the required steps and prerequisites. BRARCHIVE summary log) are copied from the source to the target system. the postprocessing steps mentioned in this SAP Note are performed automatically by SAPinst. After you have copied the database files.sql and the init<DBSID>. If required. The main prerequisite is that the corresponding BR*Tools logs (BRBACKUP detailed and summary log.ora.ora ■ On Windows: Source and Target Directory Files CONTROL. 4.SQL source: <INSTDIR> target: <SAPINST_INSTDIR> source: <INSTDIR> target: /oracle/<DBSID>/<DB_VERSION>_<BIT>/ dbs init<TARGET_DBSID>. make sure that the files on the source and target system are not located in different directories or drives. Verify that the created directories and copied files have the owner ora<target_dbsid>. see SAP Note 1003028.ora 2. SAP 2010-01-25 PUBLIC 69/144 . and have the permissions 740. Create an Oracle spfile from init<TARGET_DBSID>. 3. The file names are specified by the control_files parameter of the init<TARGET_DBSID>.ora file. Call the restore and recovery function of BR*Tools.5 Restoring the Database Files on the Target System with BR*Tools Procedure 1.5 5.ora profile as follows: SYNTAX sqlplus /nolog connect / as sysdba create spfile from pfile. ■ On UNIX: Source and Target Directory Files CONTROL. remove them.SQL source: <INSTDIR> target: <SAPINST_INSTDIR> source: <INSTDIR> target: \oracle\<DBSID>\<DB_VERSION>_<BIT>\database init<TARGET_DBSID>. exit 3. If necessary. Copy the following files from the source system host to the target system host by copying manually the listed files from the source directories to the target directories.1 Database-Specific System Copy Oracle-Specific Procedure The installation directory of the target system is normally located in the directory: %programfiles%\sapinst_instdir\NW04S\LM\COPY\ORACLE\SYSTEM\<system_variant> 2. In addition.1. belong to the group dba. 5.

In SAPinst. This method is suitable for creating an exact copy of an existing database. see help. After you have performed recovery and post-recovery activities you can continue the installation in SAPinst.0 including Enhancement Package 1 SAP NetWeaver 7. ■ This method is faster than the database-independent method using R3load or Jload [page 25]. Prerequisites ■ Byte order – little-endian or big-endian You can use the backup and restore method to copy systems with the same byte order.2 Database-Specific System Copy SAP MaxDB-Specific Procedure 4. Shut down the Oracle database instance as follows: SYNTAX sqlplus /nolog connect / as sysdba shutdown immediate exit End of: Oracle | Only valid for: MaxDB | 5. You can also copy a system based on big-endian to another system based on big-endian. you can copy a system based on little-endian to another system based on little-endian. Disadvantage You can only copy between systems with the same byte order.sap. The source of the copy is a complete data backup of your source database. The SAPinst tool is used for installation on the target system host as described in the installation documentation for your SAP solution. Check SAP Note 552464 to find out which processor and operating system combination uses which byte order.com/nw70 SAP NetWeaver 7.2 SAP MaxDB-Specific Procedure In an SAP system environment. you can create a homogeneous copy of an SAP MaxDB database by using the backup and restore method.5 5. This description is not valid for the liveCache system copy. Advantages ■ You can use existing offline backups.0 Library (including Enhancement Package 1) Englishh SAP NetWeaver Library Administrator’s Guide Technical Operations for SAP NetWeaver General Administration Tasks Database Administration Database Administration for Oracle BR*Tools for Oracle DBA . you select the backup and restore method as the database installation method. ■ Data backup 70/144 PUBLIC 2010-01-25 . For more information about BR*Tools. SAPinst stops before the database instance initialization and asks you to perform the recovery on the target database. Note 1003028 also comprises information about executing restore and recovery under the control of BRRECOVER and the exact syntax of BRRECOVER (see section Homogeneous Database Copy). That is.

To get the used space in MB. If you do not already have a suitable recent complete SAP MaxDB backup. configure the database data volumes according to this value.com/nw70 SAP NetWeaver 7.<password> —n <database_server> —u SQL sap<sid>. ■ Size of the data on the target system The size of the target system must be greater than the used space on the source system. ■ Recovery tool You are using the SAP MaxDB Database Manager (DBMGUI) version 7. Process 1.2 Database-Specific System Copy SAP MaxDB-Specific Procedure You perform the complete data backup of your source database. To install the new system. The build number of the software version on the target host must be greater than or equal to the version on the source host. SAPinst stops in the screen Perform Database Recovery before database initialization and asks you to perform the data recovery.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Databases SAP MaxDB Tools Database Manager GUI ■ Database Software The database software on the target host must have the same version as the software on the source host. During the installation of the database instance. Make the backup medium available on the target host.Windows | 2. ■ JRE You must have installed JRE version 1.mysql. 3.Windows | Run SAPinst to perform the export for UNIX or Windows [page 34]. When SAPinst prompts you. divide this value by 128. End of: UNIX. Do the following on the source system: 1. You can find the size of the used pages on the source system as follows: dbmcli —d <database_name> —u <dbm_user>.com/doc SAP MaxDB by MySQL SAP MaxDB Online Library Tools ● http://help.sap. start SAPinst as follows: <SAP Product> Software Life-Cyle Options System Copy SAP MaxDB Target System <Central System | Distributed System | High-Availability System> .0 Build 12 or above. expressed as the number of 8 KB pages. 2010-01-25 PUBLIC 71/144 .5 or higher on your system. The JAVA_HOME environment variable must point to the JRE directory. Only valid for: UNIX.<password> sql_execute 'SELECT USEDPERM FROM SERVERDBSTATISTICS' The result of this query is the amount of used space. Do the following on the target system: 1. You can find more information on DBMGUI at either of the following: ● http://dev.5. create a complete data backup using the DBMGUI tool: DBMGUI Backup Backup Wizard Complete 2.5 5.

In type of recovery. you can use backup images across the platforms I386. Specify the backup medium. DBSTATIADA. DBSTATHADA. CNMEDIA. Choose Recovery Recovery with Initialization . check the state of the target database instance. maintain the database connection for CCMS. The recovery wizard does not start the recovery immediately. or the detach/attach method in an SAP environment. see SAP Note 588515. ● You can attach SQL Server 2000 files to SQL Server 2005 but not vice versa. 6. you can make a backup on one type of platform and use it on another type. After the restore. 5. see SAP Notes 193816 and 151603.3 MS SQL Server-Specific Procedure This section describes how to perform a homogeneous system copy of an MS SQL Server database by using the backup/restore method.. 4. ● With SQL Server. NOTE 3. 4. It initializes the database instance first. CNREPRT. DBSTATTADA. For more information. Change the database state to online if it is not already in online state..3 Database-Specific System Copy MS SQL Server-Specific Procedure 2. End of: MaxDB | Only valid for: Windows | MS SQL Server | 5. The backup/restore method and the detach/attach method have the following advantages compared to the R3load method: ■ You can use an existing backup.5 5. ■ These methods are much faster than the database-independent method [page 25]. Start the restore procedure. x64. select Restore a medium. Continue with SAPinst or restart it if you stopped it during the recovery. The SAPinst installation tool supports both methods. DBSTAIHADA. 6. IA64. Register your database instance in the DBMGUI 2. SDBAADAUPD 5. After installation is completed. Delete the entries from the following tables to make sure that information about the backup history for update statistics in the Computing Center Management System (CCMS) from the old system does not appear in the new system: CNHIST. 72/144 PUBLIC 2010-01-25 . 3. Check the database instance in the admin state. Start the data recovery wizard from DBMGUI 1. NOTE ● For more information about the system copy procedure. It takes some time for the database server to format the database volumes. That is.

choose Central Instance Export.sap. 3. NOTE 2. make sure to select Use database-specific tools for the system copy method. Run SAPinst to install the target system by choosing the following on the Welcome screen: <Your SAP system> Software Life-Cycle Options System Copy MS SQL Server Target System <system variant> <technical stack> NOTE ■ The target system is installed using the exports from the source system.com/installnw70.5 5. The database relocation procedure differs significantly from the backup/restore procedure and is not described in this guide. ■ For a distributed system. this method is also referred to as backup/restore procedure. When performing the export. this method is not limited to the homogenous system copy only. create a MIGRATION EXPORT CD image. Since a DB2 backup can be used cross-platform within certain limitations (see below). Attach the database files or restore the backup of the source database on the target database server. Therefore. On the SAPinst screen SAP SystemDatabase Export. make sure to select Homogeneous System Copy (MS SQL Server-specific: Detach/Attach or Backup). On the source system. and Windows-Specific Procedures Process 1. The necessary procedure in this case is called database relocation. ■ On the SAPinst screen SAP SystemDatabase. An SAP system copy with a DB2 database can be also created if more advanced techniques like file system snapshots are available. Detach the database files from the source system database or create a backup and copy the files to the target system. UNIX. and Windows-Specific Procedures The database-specific procedure for the creation of a system copy is based on a restore of an existing online or offline backup. 2010-01-25 PUBLIC 73/144 . UNIX. run SAPinst to create an export of the Java central instance [page 34] by choosing the following installation service on the Welcome screen: <Your SAP system> Software Life-Cycle Options System Copy MS SQL Server Source System <system variant> Based on <technical stack> ■ For a central system. End of: Windows | MS SQL Server | Only valid for: IBM DB2 for Linux and UNIX and Windows | 5.4 IBM DB2 for Linux. which contains the data of the exported system. 4.4 Database-Specific System Copy IBM DB2 for Linux. For more information. ■ Choose the installation services in exactly the order they appear. and which you use to install the target system. choose Database and Central Instance Export. see the MS SQL Server installation guide for your SAP system at http:// service.

■ If errors occur when restoring the backup on the target system. you must follow the additional instructions in SAP Note 628156. see the appropriate installation guide at http://service.sap. see the Database Administration Guide: SAP on IBM DB2 for Linux.ibm. NOTE With DB2. you also have to run an export for the Java Engine to archive SDM and application-specific file system content. If you want to use the backup/restore method between different platforms.ibm. 74/144 PUBLIC 2010-01-25 . and Windows-Specific Procedures For more information. We therefore recommend that you include the necessary log files in the backup image. This implies that the name of the database connect user does not change either. section db2inidb Option: as snapshot. and Windows. also see Backup and restore operations between different operating systems and hardware platforms in the IBM DB2 V9.htm. For more information about cross-platform backups. you can use backup images cross-platform within certain limitations.doc/ doc/c0005960. As a prerequisite. ■ You cannot copy an individual MCOD component to another system. Prerequisites ■ It must be possible to restore the backup of the source system on the platform of the target system. UNIX.admin. The name of the database schema will be the same as that of the source system. UNIX. Especially.udb.4 Database-Specific System Copy IBM DB2 for Linux. Advantages of the Backup Method ■ You can use existing online and offline backups.5 5. For more information.com/ installnw70 Installation – SAP NetWeaver Systems In a Java only or ABAP+Java system. the complete restore must be repeated. a rollforward of your database is required after the database restore on the target system. Process 1. the respective database logs must be accessible.com/infocenter/db2luw/v9/topic/com. SAPinst is used for installation on the target system host as described in the installation documentation for your SAP component. You can only copy the complete system.1Information Center at http:// publib. Disadvantages of the Backup Method ■ You cannot change the name of the database schema. make sure that the relevant file systems are available. Before starting SAPinst on the target system make sure that all prerequisites for the SAP system installation are met.boulder. You perform an online or offline backup. ■ Using the backup method is faster than the database-independent method [page 25].db2. NOTE If you use an online backup to copy your system.

UNIX.doc/doc/t0004896. choose <Your SAP system> Software Life-Cycle Options System Copy IBM DB2 for Linux.htm 5. UNIX. you have to adapt the DB2 container paths or names in the redirected restore script and then perform a redirected restore.ibm. and Windows Source System <system variant> <technical stack> . choose Use database-specific tools. Be aware of the following constraints when using the backup method for a homogeneous system copy: ■ Since you cannot change the name of the database schema. section Usage of Tool brdb6brt.udb. Perform the installation options in the given sequence and follow the instructions on the SAPinst dialogs. 2010-01-25 PUBLIC 75/144 .admin. Note that as of DB2 V9.db2. CAUTION 4. On the Welcome screen. ■ The tablespace names remain the same during the database restore. ■ If you want to change the name or the location of the DB2 container on the target system. you can change them after the installation. To create a target system. To export the database content for Java. NOTE 2. UNIX. SAPinst asks you in the Database Export dialog box to specify the system copy method. the target system must have the same number of partitions as the source system. see the documentation Database Administration Guide: SAP on IBM DB2 Universal Database for UNIX and Windows. If you want to use the backup/restore method. you cannot change the connect user either. However. use the INCLUDE LOGS option of the BACKUP DATABASE command.ibm. 3. To create the export directory structure with labels and to archive SDM and application-specific file system content. Multi-Partition Database Environments only: Add database partitions If you copy a system with multiple database partitions. you can also use the database-specific method (backup/restore).5 5. and Windows Target System Installation <system variant> <technical stack> Perform the installation options in the given sequence and follow the instructions on the SAPinst dialogs. see Enabling database partitioning in a database in the IBM DB2 V9.4 Database-Specific System Copy IBM DB2 for Linux. For more information. During the dialog phase.boulder. you also have to run SAPinst. run SAPinst on the target system host by choosing the following on the Welcome screen: <Your SAP system> Software Life-Cycle Options System Copy IBM DB2 for Linux.com/ infocenter/db2luw/v9/topic/com. and Windows-Specific Procedures To do so. During the dialog phase you have to make sure that you enter the name of the connect user exactly as you did on your source system.5. SAPinst prompts you to perform the database restore during the installation phase. Restore your database. For more information.1 Information Center at http://publib. logs are by default included in an online backup.

see RESTORE DATABASE command in the IBM DB2 V9.htm. you can use the tool brdb6brt that retrieves a database backup and creates a CLP script to restore this backup image. CAUTION Make sure that you use an up-to-date version of the db6util tool. A redirected restore allows you to change the name or the location of the DB2 container. For more information. you have to make sure that you have access to the log files that were created during the online backup.4 Database-Specific System Copy IBM DB2 for Linux.doc/doc/r0001976.udb. use the DB2 RESTORE command. NOTE 6. To check the command options of the db6util tool. To adhere to the SAP standard naming conventions for tablespaces. you cannot change the name or the location of DB2 containers. Since brdb6brt needs to connect to the source system. If you have used an online backup. For more information about how to use the tool brdb6brt.com/infocenter/db2luw/ v9/topic/com. enter the following command: db2 rename tablespace <old name> to <new name> EXAMPLE db2 rename tablespace <SAPSID_SOURCE>#STABD to <SAPSID_TARGET>#STABD If you use the deferred table creation function.ibm. you can choose between one of the following options: ■ Simple database restore To perform a database restore. you also have to execute the following command for each renamed tablespace using the db6util tool: db6util -rtvt <old tbs> <new tbs> For more information. the source system must be available.boulder.1 Information Center at https://publib. see SAP Note 1227165. You require at least a version that supports the option -rtvt. and Windows-Specific Procedures To restore your database.ibm. you use the DB2 RESTORE DATABASE command with the REDIRECT GENERATE SCRIPT option. we recommend that you consider renaming the tablespaces after the installation to reflect the new system name.db2. Alternatively. To perform a redirected restore. see Redirected Restore Using brdb6brt in the Database Administration Guide: SAP on IBM DB2 Universal Database for UNIX and Windows. You can now continue with the installation. see the IBM DB2 documentation DB2 Command Reference. enter the following command: db6util –h 76/144 PUBLIC 2010-01-25 . You also have to perform a roll forward operation to bring the database into a consistent state. UNIX. To rename a single tablespace. ■ Redirected restore This is the recommended method.admin. With a simple restore. For more information.5 5.

For more information.tabdb6 set tabspace = '<SAPSID_TARGET>#'||substr (tabspace. 2. check all settings of the database manager and database configuration parameters.length(indspace)-4) ■ For table IADB6. 5.admin. see SYSTOOLSPACE and SYSTOOLSTMPSPACE tablespaces in the IBM DB2 V9.5. Log on to the database server of the target system as user db2<dbsid>. We recommend that you drop and recreate these tablespaces in the target system as follows: 1. Drop both tablespaces by entering the following command: db2 drop tablespace SYSTOOLSPACE.udb.sql. 4.5.boulder. you perform the following steps: ■ The tablespaces SYSTOOLSPACE and SYSTOOLSTMPSPACE are used by certain DB2 tools and SQL administrative routines to store historical and configuration information. enter the following SQL command: update <connect_user_name>.length(tabspace)-4).length(tabspace)-4) Follow-up Activities After the installation on the target system. To rename all tablespaces in the respective tables according to the standard naming conventions. Execute both statements on the DB2 command line. IADB6 and TADB6.5 5. Generate the DDL statements for the tablespaces of the system by entering the following command on the DB2 command line: db2look -d <DBSID> -l -o <filename>. ■ If you performed a redirected restore. 5.ibm.sql 3.ibm. enter the following SQL command: update <connect_user_name>.tsdb6 set tabspace = '<SAPSID_TARGET>#'||substr (tabspace. use the following commands: ■ For table TSDB6.indspace='<SAPSID_TARGET>#'||substr(indspace.1 Information Center at http://publib.htm. UNIX. and Windows-Specific Procedures In addition.com/infocenter/db2luw/v9/topic/ com.doc/doc/c0023713. Specifically.4 Database-Specific System Copy IBM DB2 for Linux.5. enter the following SQL command: update <connect_user_name>. you have to update the tablespace names in tables TSDB6.length(tabspace)-4) ■ For table TADB6.iadb6 set tabspace = '<SAPSID_TARGET>#'||substr (tabspace. SYSTOOLTMPSPACE Look up the CREATE TABLESPACE statements for SYSTOOLSPACE and SYSTOOLSTMPSPACE in <filename>.db2. make sure that the following configuration parameters point to the correct path: ● DIAGPATH (DBM) ● JDK_PATH (DBM) ● DFTDBPATH (DBM) ● Path to log files (DB) 2010-01-25 PUBLIC 77/144 .

and Windows Knowledge Center Key Topics Administration ■ Database Administration Using the DBA Cockpit in the SAP Community Network at: https:// www.1 at: http://www.com/software/data/db2/udb/support/manualsv9. End of: IBM DB2 for i5/OS | 5.com/infocenter/db2luw/v9r5/ ■ IBM Manuals for DB2 V9.boulder.com/software/data/db2/udb/support/manualsv9.com/irj/sdn/db6 SAP on DB2 for Linux. For more information. OVERFLOWLOGPATH (DB). Advantage of the Offline System Copy Method This method is faster than the database-independent method [page 25].5 at: http://www-1.ibm. you can create a homogeneous system copy of a DB2 database using the offline system copy method. FAILARCHPATH (DB) and MIRRORLOGPATH (DB) More Information ■ Database Administration Guide: SAP on IBM DB2 for Linux.html ■ IBM Manuals for DB2 V9.5 Information Center at: http://publib. NEWLOGPATH (DB). CAUTION You can only copy for IBM DB2 for i5/OS.1 Information Center at: http://www.wss?rs=71&uid=swg27009727 End of: IBM DB2 for Linux and UNIX and Windows | Only valid for: IBM DB2 for i5/OS | 5.ibm.5 Database-Specific System Copy IBM DB2 for i5/OS Procedure ● If set.5 IBM DB2 for i5/OS Procedure In an SAP system environment.sap.6 IBM DB2 for z/OS Specific Procedure In an SAP system environment.5 5.sdn.com/irj/sdn/db6 SAP on DB2 for Linux. UNIX.com/support/docview. UNIX.sdn. 78/144 PUBLIC 2010-01-25 . UNIX. you can create a homogeneous system copy of a DB2 database using the SAV/RSTLIB system copy method.html ■ IBM DB2 V9.sap.ibm. and Windows in the SAP Community Network at: https://www. and Windows Knowledge Center Key Topics Administration ■ IBM DB2 V9.ibm. see SAP Note 585277.

5 5.PDF file that is attached to SAP Note 680746.6 Database-Specific System Copy IBM DB2 for z/OS Specific Procedure More Information For more information on this system copy procedure. see the . The guide contains all the information necessary to carry out a system copy with DB2 tools. 2010-01-25 PUBLIC 79/144 .

This page is left blank for documents that are printed on both sides. .

6. Reschedule your canceled jobs: Tools CCMS Jobs Maintenance (SM37) .2. if necessary.1 Performing Follow-Up Activities in the Source System Procedure 1. see http://help. apply SAP Note 831812 and change the Java VM parameters.6 6.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management SAP Licenses . 6. CAUTION Before installing the license key. For more information about ordering and installing the SAP license.com/nw70 SAP NetWeaver 7. After the target system has been installed and the follow-up activities have been performed. adapt your operation mode timetable to the original status: Tools CCMS Configuration Operation mode calendar (SM63) . make sure that SAP Note 831812 is applied. 2. 2010-01-25 PUBLIC 81/144 .1 Follow-Up Activities Performing Follow-Up Activities in the Source System 6 Follow-Up Activities To finish the system copy of your SAP system: ■ Perform follow-up activities in the source system [page 81] ■ Perform follow-up activities in the target system [page 81] NOTE The Java engine is not started automatically.1 Installing the License Key Once the installation of the target system is completed and the SAP system copy has been imported.2 Performing Follow-Up Activities in the Target System NOTE Before you start the Java engine after the system copy. you have to install a new license key. you have to start the Java engine manually. 6.sap. Using CCMS.

2.sap. 9. 7. Adapt the transport parameters and transport routes in the Transport Management System (TMS): a. Before starting the SAP system. repair. BRARCHIVE. and customizing requests that have not been released in the source system will not be released automatically. Check the SAP parameters of the default and instance profiles. Oracle: Delete the user OPS$<SOURCE_SAPSID>ADM. and so on if required. . DBSTAIHORA. Actions at SAP System Level 1. 11. 1. Check the parameters in the database profiles. 2.netrc. ignore this step. DBSTATIORA. 5. . Adapt non-SAP directories.rhosts). If the parameter does not exist on your system. 3. DBSTATTORA.ora. Oracle: Adapt the database profiles init<SAPSID>. CPIC. all open transport.2. If you did not change the SAPSID during the system copy. SAP ArchiveLink) if required. Adapt additional non-SAP software components (for example. we recommend that you adapt the global_name parameter by using the following SQL command: alter database rename global_name to <NEW_DBSID>.dba and init<SAPSID>. init<SAPSID>. 10. Configure the Transport Management System (transaction STMS). Adapt additional SAP software components (for example. RFC. Actions at Database Level 1. file systems. make sure that the logging mechanism of the database is active. Oracle: If you changed the <DBSID> during the system copy. 3. 8. 6. Adapt backup programs (for example BRBACKUP. 4. Choose transaction STMS Overview Systems . Adapt the configuration files at operating system level to meet network and SAP requirements. job schedulers) if required. 2. Check operating system files (for example.2 Follow-Up Activities Performing Follow-Up Activities in the Target System 6. 82/144 PUBLIC 2010-01-25 . NFS mounts. Check crontab or AT jobs. BACKINT) if required. Run an installation check: Administration System administration Administration Installation Check (transaction SM28). 4. 5.6 6. 2. archiving systems. Check your UNIX shell files for special entries. monitoring tools. Select the system and select the tab Transporttool. 3. Check operating system printers. Oracle: Delete all entries from the following tables: DBSTATHORA.2 Performing Follow-Up Activities for ABAP Procedure Actions at Operating System Level 1.

Delete the old jobs. see SAP Note 16875. Copy the old jobs. To adapt the transport routes: Choose transaction STMS Overview Transport routes . For more information. you must set up the trusted and trusting RFC relationships again. 2010-01-25 PUBLIC 83/144 . 9. ALSYSTEMS. Maintain the time table using the new operation modes. Adapt the definition of the printers to meet the new system requirements: ■ Device types and character set definitions ■ Spool servers ■ Output management systems (OMS) Delete entries in table DDLOG for buffer synchronization. 8. SDBAR. 14. 2. SDBAH. Adapt the operation mode time tables (CCMS): Administration CCMS Configuration Operation mode calendar (transaction SM63). 3.6 6. Delete all entries from the following tables: ALCONSEG. If you find erroneous entries with message text Systemdependent data for entry … changed . Clean the transactional RFC: Tools Administration Monitor Transactional RFC (transaction SM58). 17. Adapt the RFC destination: Tools Administration Administration Network RFC destinations (transaction SM59). 6. 11. Modify the new jobs. If you have performed a system copy with R3load. Create new operation modes and instance definitions. Delete the old operation modes and old instance definitions. PAHI. 12. OSMON. 2. 10. Create new operation modes and remove old ones: 1. Delete canceled and finished jobs. Adapt the instances and profiles (CCMS): Administration CCMS Configuration OP modes/ instances (transaction RZ04). SDBAD. see the relevant description in the SAP Online Documentation. Execute ABAP program RSBTCDEL. DBSNP. 15. For more information. 3. 16. Adapt all jobs needed in the target system: 1. marking the field delete with forced mode: Tools ABAP Workbench ABAP Editor (transaction SE38). Synchronize the buffers as described in SAP Note 36283 and adapt the client information for the logical system. 7. see SAP Note 816861. 13. SDBAP. Check the consistency of the Temporary Sequential Objects (TemSe) by searching for files of TemSe objects for which no TemSe objects exist: Administration CCMS Spool TemSe administration (transaction SP12). Start transaction SECSTORE using Check Entries.2 Follow-Up Activities Performing Follow-Up Activities in the Target System 4. MONI. 5.

For more information. 31. see the SAP Online Documentation (SAP Web Application Server System Administration Application Data Archiving and Reorganization) . Also revise the authorizations of the system users. Post-processing for customer objects: If customer objects are not original in the new system. changes and transports for client-dependent objects. reorganization parameters of CCMS table MONI) if required. Define or remove the SAP system users: Tools Administration User maintenance Users (transaction SU01). BI customers: If you have copied a BI (formerly BW) system. Check the logical system names. see Preparations [page 19].2 Follow-Up Activities Performing Follow-Up Activities in the Target System 18. Configure the domain controller in the Transport Management System (TMS) by using transaction STMS. For more information. which holds the repair requests from your source system. update statistics. Check the connection to SAPNet . 22. alert thresholds. Delete all entries from table TLOCK. 27. Run transaction SE14 to delete all entries from tables TPFET and TPFHT. 25. Check logon groups and assignment of application servers to logon groups (transaction SMLG). 24. These contain information about changes made to the profile of your source system. 23. change the logical system names at this time. IBM DB2 i: Use the commands CLRPFM R3<SID>DATA/TPFET and CLRPFM R3<SID>DATA/TPFHT. Follow your corporate naming strategy for logical systems when making this change. Check if you can delete clients that will no longer be used in the target system (transaction SCC5). 32. Redefine database actions (backup. read SAP Note 325525. Make data archived in the source system (data that does not reside in the database but was moved to a different storage location using SAP Archive Management) accessible in the target system. Check self-defined external commands (transaction SM69). and so on) if you have used the DBA calendar in the source system (transaction DB13). 26. protection level. Check the contexts and segments of remote application servers for the SAP Monitoring Infrastructure if required (transaction RZ21). 20. Check entries of the following tables in all relevant systems: ■ TXCOM (transaction SM54) ■ THOST (transaction SM55) 28. 19. restrictions) (transaction SCC4). Adapt other CCMS settings (for example. 33. 84/144 PUBLIC 2010-01-25 . modify the corresponding entries in table TADIR. If you need to change logical system names in the system that results from the copy. Adapt the file residence information in the target system. changes for client-independent objects. For every client in your SAP system check the detail settings (client role. 30.R/3 Frontend (transaction OSS1). 21. 29.6 6. as described in SAP Notes 103228 and 544509.

Test transactions frequently used by the customer. 7. andRAABGA01 (fixed asset retirements) and compare the results to those gained on the source system before the system copy. For a detailed description of the features. RAGITT01 (asset history sheet). Load generation requires a large amount of system resources. The ABAP loads are generated in the target system when they are first used. Check the system log on all application servers (transaction SM21). IBM i to MaxDB) when copying the system. To avoid this. 2010-01-25 PUBLIC 85/144 . 5. try using the option Validate (ENTER) instead of the option Save to save your changes. you have to start program RS_BW_POST_MIGRATION in the background with variant SAP&POSTMGRDB. 34. RAZUGA01 (asset acquisitions). you have to start program RS_BW_POST_MIGRATION in the background by using variant SAP&POSTMGR. 8.2 Follow-Up Activities Performing Follow-Up Activities in the Target System If you encounter problems modifying a customer development class using transaction SMTS or SM31. ABAP Program Loads The ABAP loads are platform-dependent programs that are generated during runtime and stored in database tables. 3. 4. however. CO customers: Run the report group 1SIP and compare the results to those gained on the source system before the system copy. Perform initial consistency check (transaction SM28). Checking the Target System The following actions are suitable for checking the consistency of the target system: 1. reduce production system performance. you can use transaction SGEN to generate the missing loads.6 6. Therefore. or in the Job Monitor by choosing Job Monitor. FI customers: Run the job SAPF190 (accounting reconciliation) and compare the results to those gained on the source system before the system copy ( Accounting Financial Accounting General ledger Periodic Processing Closing Check/count Comparison ). 6. see the online documentation in transaction SGEN by choosing Information on the SAP Load Generator. They are not exported when you use the R3load procedure to copy your SAP system. NOTE You are required to perform the step independent of whether your target system is a BI or not. If you changed the database management system (for example. it makes sense to schedule the generation job to run overnight. FI customers: Run the jobs RFUMSV00 (tax on sales/purchases). This might. Check the consistency of the database (transaction DB02). 2. 35. Perform server check (transaction SM51). Program RS_BW_POST_MIGRATION performs necessary modifications on databasespecific objects (mainly BI objects). If you did not change the database management system when copying the system.

0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Security System Security System Security for SAP NetWeaver AS ABAP only Trust Manager . NOTE ■ Since replacing a PSE will remove all of the previously used certificates. 2. make sure that the Distinguished Name used for the PSE conforms with the naming convention that applies. Proceed as described in the documentation Creating or Replacing a PSE in the SAP Library at http:// help.sap.3 Performing Follow-Up Activities for Java Depending on the usage types or software units contained in your target system. you have to perform general and usage type or software unit-specific configuration steps: ■ General Follow-Up Activities [page 86] ■ Usage Type or Software Unit-Specific Follow-Up Activities [page 87] 6. the CN part of the Distinguished Name must be the host name used to access the server.6 6. The naming conventions are usually specified by the Certification Authority (CA) where you obtain the certificate.1 General Follow-Up Activities You have to perform the following activities for all usage types or software units of the copied SAP system. For the system PSE.3. however.2. for the SSL server PSE. call transaction STRUST. 6. Proceed as follows: 1. before you use the GUI Config Tool to change Java parameters. also import all necessary trusted certificates into the new PSE's certificate list. 86/144 PUBLIC 2010-01-25 . CAUTION Make sure you applied SAP Note 831812. ■ Note the naming conventions to use for each PSE. for example. the type of PSE also has some restrictions.2. Therefore.) Also distribute the new PSE's public-key certificate to the systems where it will be used. In your ABAP system. ■ Make sure the new PSE contains the new system ID. (Check the old PSE's certificate list. we recommend using the SID as the CN part.com/nw70 SAP NetWeaver 7.2 Follow-Up Activities Performing Follow-Up Activities in the Target System Replacing the PSEs in the Target System Replace all existing PSEs in the target systems with new ones which contain the new system's information.

Maintain the required parameters for the RFC destination and repository.3.sap. 3.1 Configuration Steps for the SAP Java Connector You need to perform these post-installation steps for a copied Java system that includes a component that has to connect to an ABAP back end using the SAP Java Connector (SAP JCo).6 6.sap. 6. 2010-01-25 PUBLIC 87/144 . see help.2. Importing the Public-Key Certificates You also need to import this public-key certificate on any systems that are to accept logon tickets from the AS Java system.2.2.0 Library English SAP NetWeaver Library SAP NetWeaver by Key Capability Security User Authentication and Single Sign-On Authentication on the AS Java Configuring Authentication Mechanisms Using Logon Tickets for Single Sign-On Configuring the Use of Logon Tickets Configuring SAP Web AS ABAP to Accept Logon Tickets from the J2EE . Remove the old JCo-destination that was copied from the source system.3. You need to reconfigure them as described at help.2 Usage Type or Software Unit-Specific Follow-Up Activities You have to perform the following activities for specific usage types or software units of the copied SAP system.2 Follow-Up Activities Performing Follow-Up Activities in the Target System 6. 4.3. 5. 6. 2. the public key certificates are wrong on the target system.com/nw70 SAP NetWeaver 7. choose Runtime and select the RFC destination that you use for the connection to the back end. Procedure 1.0 Library English SAP NetWeaver Library SAP NetWeaver by Key Capability Security User Authentication and Single Sign-On Authentication on the AS Java Configuring Authentication Mechanisms Using Logon Tickets for Single Sign-On Configuring the Use of Logon Tickets Replacing the Key Pair to Use for Logon Tickets .com/nw70 SAP NetWeaver 7. On the launch path on the left.2 Generating Public-Key Certificates Reconfiguring the Public-Key Certificates After system copy. On the right. choose Cluster Server <server name> Services JCo RFC Provider .1. Restart the Java server and the component. For more information. 6. for example SAP Business Warehouse or SAP Enterprise Portal.1. Log on to the Visual Administrator as an administrator.

2.3.3.com/installNW70 Enhancement Package Installation on Existing SAP Systems .2.sap.1 Application Server Java (AS-Java) AS Java: SAP Knowledge Warehouse After the system copy.1 EP: Basic Configuration Configure the portal for your IT scenario variant as described in the SAP Library at http:// help.2. for example.2.0 Including Enhancement Package 1 on <OS>:<database> at http://service. you have to configure the Internet Knowledge Servlet (IKS) to connect to the new ABAP back-end as described in Configuring the Access to Knowledge Warehouse Content from SAP Internet Knowledge Servlet in the documentation Installation Guide .6 6. for example: ■ Indexes for search and classification (TREX) ■ Data in external repositories.2.sap.2.3.2 Enterprise Portal (EP) Only valid for: Enterprise Portal (EP) | 6.2.2. on file system shares ■ Data on groupware servers Procedure To prevent source and target system from working with the same data. If the source and target system have write access to the same data.com/nw70 SAP NetWeaver 7.2 Follow-Up Activities Performing Follow-Up Activities in the Target System 6.2.2.SAP NetWeaver 7. For this reason.3. this results in serious inconsistencies in both systems. Critical items that are accessed by both systems are. Only valid for: Enterprise Portal (EP) | 6. the Knowledge Management and Collaboration (KMC) target system still has access to the same data as the original source system.3. it is essential to prevent both systems from using the same data. End of: Enterprise Portal (EP) | Only valid for: Enterprise Portal (EP) | 6.1 6.2.2 EP: Knowledge Management and Collaboration After the system copy. reconfigure the following components on the target system: ■ TREX ■ Repository Managers 88/144 PUBLIC 2010-01-25 .2.1.0 Library (including Enhancement Package 1) English SAP NetWeaver Library Technology Consultant's Guide Running an Enterprise Portal <your scenario variant> .

Make sure that the source and target system do not have write access to the same data.6 6.sap.sap.NW 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Information Integration Knowledge Management Administration Guide System Configuration Content Management Configuration Repositories and Repository Managers External Repositories http://help. Repository Managers For the target system. install a new instance of TREX. do not delete any indexes.com/nw70 SAP NetWeaver 7. For this reason you need to install a new instance of TREX and connect it to the target system. For example.0 On the target system.0 the source system. Task Detailed Information On the target system. Information Integration Knowledge Management NOTE Administration Guide System Administration System The prerequisite for this step is that all repository Configuration ‘Index Administration’ iView managers are configured correctly for the target system. delete old indexes that belong to http://help.com/nw70 SAP NetWeaver 7. otherwise they will also be deleted on the source system. the target system is still connected to the same TREX installation as the source system. set up the connection to the Library (including Enhancement Package 1) English SAP newly installed TREX system.com/installNW70 Installation Installation .sap. CAUTION While KMC is still connected to the old TREX installation.com/nw70 2010-01-25 PUBLIC 89/144 .Standalone Engines & Clients Installation Standalone Engine . Task Detailed Information http://service. NetWeaver Library SAP NetWeaver by Key Capability Information Integration Search and Classification (TREX) TREX Configuration Post-Installation Configuration Client Side Java Application (HTTP Connection) Specifying the Address of the TREX Name Server On the target system.0 TREX Single Host http://help. Ensure that the target system does not have write access to the same repositories as the source system. Define and generate new indexes for Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability the target system. check the repository manager settings for: ■ CM FSDB or CM DBFS repositories ■ Simple File System repositories SAP NetWeaver 7. TREX After the system copy.2 Follow-Up Activities Performing Follow-Up Activities in the Target System ■ Services ■ Collaboration The tables below summarize the configuration steps for each of the components and specify where you can find more information. check the configuration of all external and internal repository managers that have write access to the same data as the source system.sap.

Import the cleanup file into the target portal. on the right.com/nw70 SAP NetWeaver 7. choose Actions Import . adapt the room back-end properties server address. check the settings for the Host and Alternative Host parameters. generate a new index to enable Library (including Enhancement Package 1) English SAP search operations in the content of rooms. http://help. if required. Nodes Collaboration Task Detailed Information On the target system. tasks are still assigned to the IDs of the source for Knowledge Management Cluster Only: Assigning Tasks to system. and Web protocol.0 Library English SAP NetWeaver Library SAP NetWeaver by Key Capability Information Integration Knowledge Management Administration Guide System Configuration Content Management Configuration Global Services URL Generator Service System Landscape: On the target system.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Information Integration Knowledge Management Administration Guide System Configuration Content Management Configuration Global Services Content Exchange Service Content Exchange If content exchange is in use. http://help.6 6.0 On the target system.sap.com/nw70 SAP NetWeaver 7. ■ If required. set up a new configuration. Note that the cleanup procedure automatically creates a new ID for a syndicator and subscriber. To ■ do this. Scheduler Service: If the target system is an SAP Java http://help.com/nw70 SAP NetWeaver 7. delete the configuration on the target system and. For this reason. NetWeaver Library SAP NetWeaver by Key Capability 90/144 PUBLIC 2010-01-25 . After the system Key Capability Information Integration Knowledge Management Administration Guide Minimal Configuration copy.com/nw70 SAP NetWeaver 7. However.sap. the configuration on the source and target system is identical.com/nw70 SAP NetWeaver 7. Management Global Services System Landscape Definitions Systems Content Management Systems . server port. URL Generator On the target system.0 cluster.sap.sap. configure new content exchange settings on the target system. delete the Log on to the Portal and choose System Administration System Configuration Knowledge Management Content old system IDs that belong to the source system. choose System Administration System Configuration Knowledge Management Content Management and then. then you must assign scheduler tasks to the Library English SAP NetWeaver Library SAP NetWeaver by new system IDs of the target system.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration Collaboration Administration Guide Basic Configuration Defining Back-end System Properties for Room URLs http://help. it does not make sense to have the same content exchange procedures configured twice. Run a cleanup file to remove the existing configuration on the target system: ■ Download the cleanup file attached to SAP Note 1238351.sap.2 Follow-Up Activities Performing Follow-Up Activities in the Target System Services Task Detailed Information http://help.

People Integration Collaboration Administration Guide Virtual Rooms Configuration of Search Functions for Rooms Configuration of the Search for Room Content http://help.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration Collaboration Administration Guide Virtual Rooms Configuration of Search Functions for Rooms Configuration of the Search for Rooms http://help.sap. On the target system. check the properties of the roomsearch object. If the e-mailing service is active on the source system. Make sure that the parameter Use TREX is set. when members are excluded from a room or documents are updated and deleted. but is not required on the target system.3. you need to delete the e-mail transport. reconfigure the ServerName and ServerPort for the application sharing server.2. Prerequisites You have performed a system copy that includes SAP Business Warehouse (SAP BW).1 Business Intelligence (BI Java) Follow the instructions in this section if the entries for source system connection have not been copied to the services file of your target system.sap. After deletion of the transport.sap.6 6. for example.2. configure the connection to the required groupware server.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration Collaboration Administration Guide Real-Time Collaboration Configuring Real-Time Collaboration Configuring the Application Sharing Server (RTC) Setting Application Sharing Server Parameters (RTC) End of: Enterprise Portal (EP) | End of: Enterprise Portal (EP) | Only valid for: BI Java | 6.com/nw70 SAP NetWeaver 7. e-mailing is disabled.com/nw70 SAP NetWeaver 7.3.sap.2 Task Follow-Up Activities Performing Follow-Up Activities in the Target System Detailed Information On the target system.2. 2010-01-25 PUBLIC 91/144 .0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration Collaboration Administration Guide Groupware Groupware Framework Installing and Configuring E-Mail Connectivity Configuration Steps Creating an E-Mail Transport http://help.2. On the target system.3 Business Intelligence Java Components (BI Java) You have to perform the following follow-up activities for usage type BI Java: 6.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration Collaboration Administration Guide Basic Configuration Configuring E-Mail Connectivity http://help.3. E-mails will no longer be automatically sent.com/nw70 SAP NetWeaver 7.

2.2.2 Follow-Up Activities Performing Follow-Up Activities in the Target System Procedure Adding Entries to the Services File You have to do the following to add the entries to the services file: If your target host runs on a UNIX platform 1. If your target host runs on a Windows platform or on IBM i 1.2 Procedure Basic Configuration for Usage Type BI Java 1. 2.2.3. Make sure that the user root has not set any environment variables for a different SAP system or database. Maintain Portal Server Settings for the Portal 4. Import BI Certificate to the Portal 3. BI-Integrated Planning Call transaction SPRO and choose SAP NetWeaver Business Intelligence BI-Integrated Planning . Log on to your target system as user root. for example sapgw47 3347. Edit the file /etc/services. Edit the file <WindowsDirectory>\system32\drivers\etc\services. Import Portal Certificate to BI System End of: BI Java | Only valid for: Process Integration (PI) | 6. Log on to your target system as a member of the local administration group. CAUTION 2. Integration into the Portal Call transaction SPRO and choose SAP NetWeaver Business Intelligence Reporting-Relevant Settings BEx Web Integration into the Portal .4 Process Integration (PI) You have to perform the following follow-up activities for usage type PI: 92/144 PUBLIC 2010-01-25 .3.2. Create RFC Destination for the Portal 5. 3.2. Add the entries for your source system connection. Create RFC Destination in J2EE Engine 2. Follow the instructions for the following steps: 1.6 6. for example sapgw47 3347. 3.3. Add the entries for your source system connection. 6. Follow the instructions for the following step: Define JCo Destination.

4. 6. For more information.com/nw70 SAP NetWeaver 7. see the Post-Installation Guide SLD of SAP NetWeaver 7. For more detailed instructions about how to change the values. see the section Connection Between Web AS Java Systems and SLD Setting Up the SLD Data Supplier for J2EE-Based Systems . For more information.sap.0 at http://service.2 Follow-Up Activities Performing Follow-Up Activities in the Target System NOTE The following changes reflect exactly the regular configuration steps for usage type PI. refer to the configuration information at http://help. ■ Maintain server settings in the SLD: 2010-01-25 PUBLIC 93/144 . see the documentation in the SAP Library at http://help.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Software Life Cycle Management System Landscape Directory Configuring Systems to Connect to SLD .2.1 Procedure NOTE PI: System Landscape Directory For more information about how to perform the individual tasks.3.com/installNW70 Configuration .sap. For more information. This value should be predefined by the value entered before in transaction SLDAPICUST. see the section Connection Between Web AS ABAP Systems and SLD Configuring the SLD Data Supplier: Default Settings .6 6.sap. The respective sections are stated below.0 Library (including Enhancement Package 1) English SAP NetWeaver Library Technology Consultant's Guide Business Process Management Configuration of Usage Type Process Integration . ■ Maintain the SLD connection parameters: Call transaction SLDAPICUST and change the value for the host name as well as for the port number. see the section Connection Between Web AS ABAP Systems and SLD SLD Application Programming Interface for ABAP-Based Systems Creating an HTTP Destination for the SLD ABAP API on the ABAP Side .com/nw70 SAP NetWeaver 7. ■ Maintain the ABAP connection: Call transaction RZ70 and change the value for the host and the gateway service in the group box Transport Information. ■ Configure the SLD Data Supplier Service in the Visual Administrator: Change the value for the host as well as for the HTTP port number. The respective sections are stated below. NOTE For information on how to perform the following tasks.2.

and choose Perform Automatic Workflow Customizing (F9). Create HTTP destination pmistore in the Java environment: Change the value for the host and port number in the destination URL. Create RFC destinations in the ABAP environment: Call transaction SM59. maintain a product for the technical system. Maintain the pipeline to the Integration Server: Change the pipeline to the Integration Server by running transaction SXMB_ADM. also change the value for the application host name and the system number. Call transaction SWF_XI_CUSTOMIZING. Call transaction RZ12 and change the instance name under Group assignment. navigate to destination INTEGRATION_DIRECTORY_HMI. In the Visual Administrator. 2.4. Maintain RFC destination in the ABAP and Java environment: For the following connections. Maintain RFC destination AI_MONITORING_SERVER in the ABAP environment.3. see to the section Configuring the SLD Bridge. Maintain RFC Server Groups. 7. Maintain the technical system and the business system for the Integration Server: In the SLD. 3. Maintain the logical system: Call transaction SCC4 to maintain the logical system information. 6. 5. change the value for the gateway host as well as for the gateway service on the ABAP side and in the Visual Administrator.6 6. Maintain Prefix Numbers for Workflow and Organizational Management. 6. ■ Configure the SLD Bridge: Change the value for the gateway server as well as for the gateway service. as well as for the gateway service on the ABAP side. 8. For more information.2. select Maintain Definition Environment Maintain Prefix Numbers . see the section Configuring Server and Persistence Parameters. Create a business system for the Integration Server and maintain the logical system information. 4. Change the value for the gateway host. 9. For more information.2.2 Procedure PI: Integration Server 1. 94/144 PUBLIC 2010-01-25 .2 Follow-Up Activities Performing Follow-Up Activities in the Target System Change the value for the object server. and change the value for the target host as well as for the HTTP port number. and the value for the PI host in the Visual Administrator for the following connections: Connection AI_RUNTIME_JCOSERVER LCRSAPRFC SAPSLDAPI Description Used to connect the ABAP part to the Java part of the Integration Server Used to connect the Integration Server to the SLD.

sap.aii.6 6.sap. Refresh host name buffer.rmiport com.connect.4.0 Library (including Enhancement Package 1) English SAP NetWeaver Library Technology Consultant's Guide Business Process Management Configuration of Usage Type Process Integration . Note that it is essential that you change the connection for the following steps of this section.httpsport com. refer to Exchange Profile Parameters in the PI configuration documentation at http://help.aii.cr.com/nw70 SAP NetWeaver 7. the host name buffer needs to be reset.sap.aii.httpport Contains the host name of the component repository server. 10. Contains the HTTPS port number of the directory server.sap.connect.sap.name Description com. Contains the HTTP port of the J2EE Engine of the Integration Server.2.connect.aii.integrationserver.httpport com. CAUTION 2.sap.aii.connect.2 Follow-Up Activities Performing Follow-Up Activities in the Target System This destination only needs to be maintained if performance data collected by Process Monitoring Infrastructure is displayed in the Runtime Workbench.name com.cr.aii.3 Procedure PI: Changes in the Exchange Profile 1.sap. Parameter com. Without adjusting the connection parameters. Call transaction SM51 and choose Goto Host Name Buffer Reset Entire System . Contains the RMI port number of the directory server.directory. Contains the host name of the directory server.aii.2.integrationserver.connect.sap. After you have maintained the required RFC destinations.sap. Contains the host name of the Integration Server. Maintain server settings for the exchange profile connection: Change the value for the host name as well as for the instance number. all changes in this section affect the exchange profile of the source system.aii.httpport com.directory. Contains the HTTP port number of the component repository server.connect.connect. For more information about parameters. 2010-01-25 PUBLIC 95/144 . Used by the XI integration directory to connect to the XI runtime. 6.3.directory. Contains the HTTP port number of the directory server.directory.name com. All parameters pointing to the source system must be changed in order to reference the target system. Change all parameters pointing to the source system: The following parameters contain the host name for the connection of components.connect.

sap.connect.connect.sysnr com.sap.aii.rwb.connect.rwb.sap.sap. Contains the HTTP port number of the Integration Server.integrationserver. and the central alert server run.r3.aii.sysnr Contains the HTTPS port of the J2EE Engine of the Integration Server.connect.sap. Connection from Java stack to ABAP stack of the NetWeaver Application Server.rmiport com.centralmonitoring.repository.sap.connect.rwb.sap.sap. Contains the HTTP port number of the Runtime Workbench. Contains the HTTPS port number of the repository server.landscape.sysnr com.server.sap.aii. the central CCMS.connect.integrationserver. System number of the NetWeaver Application Server on which the central PMI.connect.rwb.repository.server.sap.aii.r3. Connection from Java stack to ABAP stack of the NetWeaver Application Server.repository.aii.sap.connect.webas.aii.sysnr com.ib.centralmonitoring.httpport com.r3.name com.connect.httpsport com.connect.ib. and the alert server run.aii.webas. 96/144 PUBLIC 2010-01-25 . the CCMS. Contains the HTTP port number of the landscape directory server.sap. R3 system number of the NetWeaver Application Server on which the Integration Server runs.aii.2 Follow-Up Activities Performing Follow-Up Activities in the Target System Parameter com.r3. Contains the host name of the landscape directory server.aii.sap.connect. Used by the XI integration directory to connect to the XI runtime.sap.aii.landscape.connect.name com. Contains the RMI port number of the repository server. Contains the host name of the Runtime Workbench (RWB).rwb.aii.server.ashost com. Contains the host name of the repository server.rwb.6 6.httpport com.server.aii.connect.aii.httpport com.integrationserver.aii. Contains the HTTPS port number of the landscape directory server.landscape.ashost com.aii.r3. Contains the HTTP port number of the Runtime Workbench.sap. R3 system number of the NetWeaver Application Server on which the Runtime Workbench runs.sap.sap.connect.repository.connect.httpsport com.httpsport com.connect. Contains the HTTP port number of the repository server.sap.r3.aii.r3.httpport com.httpsport Description com.name com. Application server of the NetWeaver Application Server on which the central PMI.aii.aii.

which contains the communication channels for these business systems.3. The server program is called with the HTTP address as a parameter that is maintained with transaction SLDAPICUST.server.2 Follow-Up Activities Performing Follow-Up Activities in the Target System Parameter com.centralmonitoring.6 6. The following actions are performed automatically: ■ Communication from the target IS 7. Restart the Java engine: In order to initialize exchange profile caches and SLD caches.sap. see the configuration information for PI at http://help. a full CPACache refresh must be enforced by executing the following URL: http://<host>:<Java-Port>/CPACache/refresh?mode=full NOTE 3. which is defined on the J2EE JRFC engine of the Integration Server.2. Refresh the CPACache: Since the restart of the Java server only leads to a delta cache refresh for the CPACache.sap.2.0 resides at a new network address. 2. restart the Java engine.4 Procedure PI: Refresh Caches 1.0 Library (including Enhancement Package 1) 2010-01-25 PUBLIC 97/144 .rwb.3.5 Procedure PI: Switching Addresses The newly installed target IS 7. you have to make address changes at several locations in order to account for this change.aii.4. If you want to reconnect business systems. To call the CPACache refresh URL. 6.2. Refresh the XI Cache: Refresh the XI Cache by running transaction SXI_CACHE. The business system name is used in the header of the message sent to the Integration Server.httpport Description HTTP port of the NetWeaver Application Server (ABAP part) on which the central PMI. 6. NOTE For more information about performing the individual tasks. you have to enter user PIDIRUSER and the corresponding password you entered during the installation.0 to business systems is set due to copying BI content. The following sections contain a detailed description of all necessary manual address changes. Connecting Business Systems to the SLD of the Target System Business systems with an Integration Engine require a connection to the SLD server of the target system in order to obtain their name from the SLD.com/nw70 SAP NetWeaver 7.4.2. The connection to the SLD is established by creating an RFC destination (as described below) and calling a registered server program. and the alert server run. the CCMS.

the Unicode indicator is set in the JRFC engine settings.com/nw70 SAP NetWeaver 7. adjust the roles) ■ all technical adapters ■ file SLDaccessor. update RFC destination AI_INTEGRATION_SERVER. The respective sections are stated below. For more information. Maintaining System Connections and Destinations If the host name and port of your Integration Server have changed after the system copy.properties in directory /tech_adapter/BaseConfiguration Enter the gateways in file etc/services. 98/144 PUBLIC 2010-01-25 . update RFC destination AI_INTEGRATION_SERVER. ■ Update the HTTP destinations: Update the HTTP destination that points from the Integration Engines (business systems) to the PI Integration Server. 1. see the configuration information for PI at http://help. Use transaction SLDAPICUST in the business system to define the SLD access data.0 for receiver preidentification: In the Integration Engine.6 6. You can use the entries that you maintained on your Integration Server.sap. the Unicode indicator is not set. 3. see the section Configuration of Business Systems with an Integration Engine in the configuration information. you have to maintain the destinations and connections if you want to reconnect Integration Engines and adapters. They use the same registered server program. You must also change the RFC destinations in: ■ all business systems (enter the new Integration Server and. see the section Configuration of Business Systems with an Integration Engine in the configuration information.0 Library (including Enhancement Package 1) English SAP NetWeaver Library Technology Consultant's Guide Business Process Management Configuration of Usage Type Process Integration . Change all RFC destinations on your business system.2 Follow-Up Activities Performing Follow-Up Activities in the Target System English SAP NetWeaver Library Technology Consultant's Guide Business Process Management Configuration of Usage Type Process Integration Configuration of Business Systems with an Integration Engine Connecting to the System Landscape Directory . For more information. For more information. 2. if necessary. ■ Optional: Update the destinations to IS 7. 5. For non-Unicode business systems (program ID SAPSLDAPI_NONUNICODE). see the section Configuration of Business Systems with an Integration Engine in the configuration information. 4. which is defined as part of the JRFC engine settings of the Java engine on the SLD host. For Unicode business systems (program ID SAPSLDAPI_UNICODE). This means that all business systems can use the same server program ID (SAPSLDAPI_UNICODE or SAPSLDAPI_NONUNICODE) for their RFC destinations LCRSAPRFC and SAPSLDAPI. ■ Optional: Update the destinations to IS 7.0 for maintenance of value mapping table: In the Integration Engine. This data consists of the host and port of the SLD as well as a user (PIAPPLUSER) and password. For information on how to perform the individual tasks.

sap. ■ If you made the configuration settings Maintain Services for the Integration Server in transaction SICF. CBS. Procedure 1. and execute all checks. choose Goto Connection Test . it should be running to ensure that all the users that were created when the Development Infrastructure (DI) was on the source system will still be valid after the move to the target system.2. Checks in SPROXY: Call transaction SPROXY.com/nw70 SAP NetWeaver 7.2 Follow-Up Activities Performing Follow-Up Activities in the Target System ■ Reintegrate business systems using the IDoc adapter of the source system: In the sending system. For the following steps.3.6 6. SLD. change the program ID RFC destination in transaction SM59 to the new program ID defined in your sender channels in the section RFC adapter.2. If you are using an LDAP server for user management. see the section Integration of Business Systems Integration Using the IDoc Adapter in the configuration information.3. The assumption here is that all components (DTR. End of: Process Integration (PI) | Only valid for: Development Infrastructure (DI) | 6. For more information. update the RFC destination to the Integration Server.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Process Integration by Key Capability SAP NetWeaver Exchange Infrastructure Runtime Connectivity and then the sections stated below: ■ Change the system connections for the RFC adapter: In all application systems. ■ Integrate business systems using the Plain J2SE Adapter Engine: Update the URL of the HTTP destination to the Integration Server in the sender adapters. 6. 2010-01-25 PUBLIC 99/144 .4. and name server) were on a single host before the move and will remain on a single host after the move.6 Procedure PI: Connection Checks 1. For more information. see the section Adapters RFC Adapters . make sure these settings are also maintained in the newly installed target system. see the SAP Library at http://help. 2. see the section Adapter Engine Plain J2SE Adapter Engine .2.2. CMS.5 Development Infrastructure (DI) You have to perform the following manual steps on the target system after moving an SAP system with usage type Development Infrastructure (DI). Checks in SLDCHECK: Call transaction SLDCHECK on the Integration Server. For more information.

1. ■ For general recommendations for the configuration of the Development Infrastructure Servers. Design Time Repository (DTR): ■ Redeploy the database schema. This is necessary to re-create the missing metadata for the database views in the dictionary. you can use the database manager to update the database statistics. Under the subfolder DEPLOYARCHIVES. ■ Only valid for: MaxDB | If your database is SAP MaxDB:.0 including Enhancement Package 1 Java on <OS>:>Database> (including usage type DI) for details. This option can be set in the Deployment tab on SDM. Then you can use a normal archive tool like WinZip.2 Follow-Up Activities Performing Follow-Up Activities in the Target System 2. ■ Restart DTR server. You can do this by appending . use the option Update deployed SDAs/SCAs that have any version. End of: MaxDB | 3. you can find the SDA sap. End of: MaxDB | 4. Refer to Installation Guide for SAP NetWeaver 7. 2. NOTE During deployment. This SDA must be deployed using the Software Deployment Manager (SDM). 3.6 6.com~tc~dtr~dbschema. ■ Change the URL of the name server (in name server configuration page in Web UI: http:// <dtrhost>:<port>/dtr/system-tools/administration/NameServerConfiguration) if you intend to use a different name server for the moved DTR instance. Set the JOIN_OPERATOR_IMPLEMENTATION parameter to IMPROVED (setting this value is only possible using the DB-WebUI in SAPMMC). The database schema of the DTR server is part of the NWDI SCA. This is the SCA that you have downloaded from http://service.com/swdc to deploy the NetWeaver Development Infrastructure (NWDI). Upgrade it to at least version 29.sda for the database schema. or if the name server was also moved. Restart the database. Check the Java Engine Configuration: ■ Set MaxHeapSize and other engine parameters to the recommended values. In order to only deploy this database schema you have to extract the SCA file. Only valid for: MaxDB | NOTE If your database is SAP MaxDB. Otherwise OpenSQL cannot see the database views.sap. ■ Perform an Update Statistics (30%) on the database. refer to SAP Note 889038.zip to the filename. System Landscape Directory (SLD): 100/144 PUBLIC 2010-01-25 .

6. Change the CMS URL to point to the target host. 3. rootFolder. CBS. Rename the folder to the new host value and new SAPSID (if changed). 2010-01-25 PUBLIC 101/144 . to the target host. change the runtime system configuration to point to the appropriate host (of the target runtime system). 3. 2. Copy the contents of the transport directory of the old CMS (source system) to the transport directory of the new CMS (target system). Change Management Service (CMS): The main steps in CMS involve resetting the fields containing URLs to other components (like DTR. Change the SLD URL to point to the target host.6 6. leave the fields unchanged. Copy the folder /usr/sap/trans/EPS/in/CMS<host><SID>. 2. 3. 2. 2. 3. Change the CBS and DTR URLs. proceed as follows: 1. For each track (in the Track Data tab): 1. ■ If CMS has not been configured yet. Refer to Installation Guide for SAP NetWeaver 7. You should see a status message that the data was saved successfully. You should see a status message that the data was saved successfully. ■ If CMS has been configured and you have used it already. Update CMS (using the button Update CMS). Do not change the ObjectServer attribute.0 including Enhancement Package 1Java on <OS>:>Database> (including usage type DI) for details about these parameters. BUILD_TOOL_JDK_HOME. Component Build Service (CBS): The service properties JDK_HOME_PATHS.2 Follow-Up Activities Performing Follow-Up Activities in the Target System Change the CIM Server URL of the SLD that is defined in the technical landscape to point to the target host. and threadPoolSize have to be adjusted according to the hardware and software configuration of the new system. Make sure that the engine user (<SID>adm) has write permissions in the copied folder. SLD). For each runtime system that is defined. proceed as follows: 1. If this has not changed. CAUTION 5. 4. Save the domain. 5. Change the transport directory to the appropriate directory on the new CMS (target host). For the domain (in the Domain Data tab): 1. The transport directory is configured in the domain (refer to Domain Data tab). Save the track definition. You should see a status message that the CMS update was successful. including its content.

Import the change request into the CONS system (from the CMS Transport Studio). End of: Development Infrastructure (DI) | 6. Assemble a new version of your software components (SCs) in one of the tracks. After the import is finished. the download links for the mobile component's installation files still point from the target system's ABAP server component to the source system's J2EE server component. check it in and activate it: ■ The activation should be successful. Now you are ready to begin the development with you new (relocated) Development Infrastructure (DI). 8. ■ Change the SLD URL in the preference page of the SAP NetWeaver Development Studio (under Java Development Infrastructure Development Configuration Pool ). ■ Import the development configuration that you used earlier for development. This will place the software components (SCs) into the import queue of this system. 5.2.6.6 6. Verification Steps (optional) The following steps are optional and verify that the Development Infrastructure (DI) is fully functional after the move: 1. Import these SCs. 5. ■ The name of the development component (DC) must be reserved on the name server.2. Log in to the DTR (using the browser) for all defined users and browse the repository.2 Follow-Up Activities Performing Follow-Up Activities in the Target System 4.1 Mobile Infrastructure (MI) MI: Clean Up the Target System After the system copy.2.3. choose Update deployed SDAs/ SCAs that have any version to redeploy all mobile components via the SDM. IDE: Restore system state (of the DEV system). Procedure In the SAP NetWeaver Mobile Administrator. Release the activity created above (from the transport view in the IDE): The activity (change request) should appear in the import queue of the CONS system of the track. 3.6 6.2. 102/144 PUBLIC 2010-01-25 . 7. under Deployment Configuration. you should see a status for each SC. 4. Using IDE. 2.3. This should now point to the new SLD on the target system. create a new development component (DC).

2. For more information.2. For both reasons. The configuration data is stored in the System Landscape Directory (SLD) where it is associated with the Java Cluster that the Content Admin runs on. the destinations have to be configured for each Java Cluster individually and currently cannot be transported.2. see SAP Note 899144.6 6. For more information.2 Follow-Up Activities Performing Follow-Up Activities in the Target System Only valid for: SAP ERP | Self Services (XSS) | 6. Some additional data is stored in the secure storage of the Java Cluster itself.3.7.7 6. require that their “Destinations ”(back-end connections) are configured with the Web Dynpro Content Administrator “Admin” (a tool specific to Web Dynpro).3. End of: SAP ERP | Self Services (XSS) | End of: SAP ERP | Self Services (XSS) | 2010-01-25 PUBLIC 103/144 .2.3.2.7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform (SAP Web Application Server) Java Technology in SAP Web Application Server Java Development Manual Developing User Interfaces Web Dynpro Advanced Web Dynpro Technologies Web Dynpro Content Administrator . see the documentation in the SAP Library at http://help. NOTE Make sure you use the correct host and port in the portal under System administration System configuration Systems SAP_Webdynpro .2 ERP-XSS: SAP WebDynpro Applications SAP WebDynpro applications that use “Adaptive RFC” (a Web Dynpro technology based on JCo and AII).1 Procedure Self Services (XSS) Re-Creating the JCo Destinations You must re-create the JCo destinations as described in the documentation Creating JCo Destinations in the SAP Library at http://help. Only valid for: SAP ERP | Self Services (XSS) | 6.com/nw70 SAP NetWeaver 7.2.sap.sap.com/nw70 SAP NetWeaver Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform Java Technology Java Development Manual Core Development Tasks Developing User Interfaces Web Dynpro.

xml.Extended E-Selling Components (XECO) | 6.SAP ERP | CRM Java Components (JCRM).2 Follow-Up Activities Performing Follow-Up Activities in the Target System Only valid for: SAP CRM.do.SAP ERP | CRM Java Components (JCRM).jco. Copy the following files to the relevant directories: 1.3.2.2.9 MapBox You need to proceed as follows to restore the configuration of the CRM Java component MapBox on the target system. 104/144 PUBLIC 2010-01-25 .2. You can find these files at the same location on the source system.3.SAP ERP | CRM Java Components (JCRM).http.2.3. 2.http. The WFD Calculation Services also has an XCM parameter cs.Extended E-Selling Components (XECO) | End of: SAP CRM.1 Sub-Component Workforce Deployment AS/CS The XCM parameters for Workforce Deployment Application and Calculation Services (WFD AS/CS) point to an SAP CRM or SAP ERP back-end system. and xmlprofiles.xml to the directory <J2EE_root>/cluster/server/.Extended E-Selling Components (XECO) | 6.Extended E-Selling Components (XECO) | Only valid for: SAP CRM | MapBox (MBX) | 6.mapboxmeta. Shut down the Java engine.do End of: SAP CRM. It should point to the HTTP port of the target Java engine. Configure XCM parameters for WFD Calculation Services: http://<J2EEHOST>:<J2EEHTTPPORT>//wfdcs/admin/xcm/init.2.cfg to the <J2EE_root>/cluster/server directory. you need to adjust the cs.port that points to the HTTP port of the Java instance it was installed on.xxxxx XCM parameters (which point to the SAP CRM back-end system) in the target system. Copy the file coordserver. mapboxmeta.8 CRM Java Components (JCRM) / Extended ESelling Components (XECO) Only valid for: SAP CRM. Procedure Configure XCM parameters for WFD Application Services: http://<J2EEHOST>:<>//wfd/admin/xcm/init. 2. you need to adjust the cs. Procedure 1. If the system copy involves copying the Java engine. Copy the files mapboxmeta.6 6.8.xsl.port XCM parameter for WFD Calculation Services in the target system.2.SAP ERP | CRM Java Components (JCRM). If the system copy involves copying the SAP CRM back-end system.

Prerequisites The J2EE Engine is running.3. 4. go to: <T_INSTDIR>\usr\sap\<sapsid>\<instancenumber>\j2ee\admin\go.3. In Alias enter srm/lib/resources. Select the Aliases tab.10. 6. Result You have restored the configuration for MapBox on the target system.bat UNIX. In order for the applet to retrieve its resources. go to: <T_INSTDIR>/usr/sap/<sapsid>/<instancenumber>/j2ee/admin/go.2.2 Follow-Up Activities Performing Follow-Up Activities in the Target System 3.2.2. the resource files for the Live Auction Cockpit applet are packaged separately from the web application itself. EXAMPLE Windows (and IBM i).sh 2. 3. 2010-01-25 PUBLIC 105/144 . the web server must make the resource files accessible using HTTP. then you need to copy the smoketest directory too. choose Server Services HTTP Provider Select the Runtime tab.sap. Open the Java engine administration tool. This is achieved by creating a web alias for the directory that contains the resources. Start the Java engine and MapBox from the URL as described in Post-Installation Steps for MapBox in the documentation Installation Guide — SAP CRM 5. 3. 7. Without this alias. In the navigation pane. 5.1 SRM Live Auction Cockpit (SRMLAC) To facilitate customization.6 6. the applet does not load properly.0 on <OS> <ABAP+Java|Java> at http:// service. Enter the Path. Port: 5<instance number>04 Enter the Java engine administrator password and choose Connect. End of: SAP CRM | MapBox (MBX) | Only valid for: SAP SRM | SRM Live Auction Cockpit (SRMLAC) | 6. If you want to have the smoketest directory on the target system.com/crm-inst . Procedure 1.10 SRM Live Auction Cockpit (SRMLAC) Only valid for: SAP SRM | SRM Live Auction Cockpit (SRMLAC) | 6.2.

2. End of: SAP SRM | SRM Live Auction Cockpit (SRMLAC) | Only valid for: SAP SRM | SRM Live Auction Cockpit (SRMLAC) | 6. 9. Prerequisites You have access to the following transactions in SAP SRM: ■ RZ10 (Edit Profiles) ■ STRUST (Trust Manager) Procedure 1. Double-click the text box to the right of Own certif. Go to transaction STRUST. 1. Create SSO ticket in Profile Maintenance. Choose the Default profile along with the latest version number and select Extended Maintenance. 5.6 6. 3. 1. Choose Add. The certificate information is displayed. Change the following profile parameters: ■ login/create_sso2_ticket = 1 ■ login/accept_sso2_ticket = 1 4.2 Follow-Up Activities Performing Follow-Up Activities in the Target System EXAMPLE Windows (and IBM i): <T_INSTDIR>:\usr\sap\<SAPSID>\SYS\global\srmla\resources UNIX: <T_INSTDIR>:/usr/sap/<SAPSID>/SYS/global/srmla/resources 8. Choose the Java administration tool. Export the R3 SSO certificate from the Trust Manager on the target host server.10.2 Configuring Single Sign-On To enable Single Sign-On (SSO) you need to configure certain settings in SAP Supplier Relationship Management (SAP SRM). CAUTION 2. 2. Choose Save Properties. Save and Activate the profile. Go to transaction RZ10.2.3. 2. Restart the application server. 106/144 PUBLIC 2010-01-25 . 10. A new profile is automatically generated. Do not forget or skip this step.

6 6.2

Follow-Up Activities Performing Follow-Up Activities in the Target System NOTE

3. 4.

Make a note of the values displayed in the certificate information because you need to enter those values below in step 3. Click the icon with the quick info: Export Certificate. Save the file as <R3_Name>-<Client>.crt.
EXAMPLE

For SAP System EBS, client 300, the file name is EBS-300.crt.
CAUTION

Make sure Binary is selected under File Format.
NOTE

3.

If you export the certificate to a local system, you must copy the file from the local system to the target host server. Import R3 SSO certificate to the java engine using the administrator tool.
NOTE

Make sure the Java engine is started. 1. 2. 3. 4. 5. 6. Open the Java administration tool. Enter the Java engine administrator password and click Connect. Choose Server Services Key Storage . Click TicketKeyStore in the View panel. Click Load in the Entry group box. Choose the <R3_Name>-<Client>.crt certificate that was exported from EBP earlier in step 2. The certificate is added to the list in the Entries panel.
NOTE

4.

Make a note of the issuer and subject distinguished names displayed in the certificate of the SAP system. These values must be identical to those you define for the properties in step 4. Configure the Security Provider service in the SAP Java engine using the administrator tool. 1. Choose Server Services Security Provider . 2. Choose ticket in the component panel and go to the Authentication tab. 3. Modify the options of EvaluateTicketLoginModule and add the following properties to each backend system on which you want to configure SSO:
NOTE

For each property below, {n} represents the number of the back-end system on which you want to configure SSO. ■ trustedsys{n}: <R3_Name>, <Client>

2010-01-25

PUBLIC

107/144

6 6.2

Follow-Up Activities Performing Follow-Up Activities in the Target System EXAMPLE

trustedsys1: EBS, 300 ■ trustediss{n}: <the issuer distinguished name>
NOTE

The value you define here must be identical to the issuer distinguished name in the certificate of the SAP system. This certificate was already imported into the keystore when you previously configured SSO for that system. You can find the certificate there and copy the needed data. For more information, see SAP Note 721815.
EXAMPLE

trustediss1: CN=EBS ■ trusteddn{n): <the subject distinguished name>
NOTE

The value you define here must be identical to the subject distinguished name in the certificate of the SAP system. This certificate was already imported into the keystore when you previously configured SSO for that system. You can find the certificate there and copy the needed data. For more information, see SAP Note 721815.
EXAMPLE

trusteddn1: CN=EBS
End of: SAP SRM | SRM Live Auction Cockpit (SRMLAC) | End of: SAP SRM | SRM Live Auction Cockpit (SRMLAC) | Only valid for: SAP SCM |

6.2.3.2.11
Procedure

SCM Forecasting & Replenishment Processor (SCM FRP)

After the system copy, you must perform follow-up activities as described in SAP Note 862955.
End of: SAP SCM |

6.2.4 Performing Jobhead Correction after Homogeneous System Copy
NOTE

This section is only relevant for customers using CCMS to monitor their SAP system(s). After copying your system, the CCMS jobhead still points to the former database SSID. In order to complete the homogeneous system copy, the SSID needs to be set to the target system.

108/144

PUBLIC

2010-01-25

6 6.2

Follow-Up Activities Performing Follow-Up Activities in the Target System CAUTION

Only experienced users should use this utility.
Only valid for: SAP NetWeaver 7.0 |

Prerequisites

You must have SAP NetWeaver 7.0 SP 12 or above to use this function.
End of: SAP NetWeaver 7.0 |

Procedure

To set the SSID to the target system:
Only valid for: SAP NetWeaver 7.0;SAP NetWeaver 7.1 |

1. 2. 3.

Call transaction DBACOCKPIT. Choose Configuration Homogeneous System Copy: Jobhead Correction Modify the necessary data.

End of: SAP NetWeaver 7.0;SAP NetWeaver 7.1 | Only valid for: SAP Web AS 6.40 |

1. 2. 3.

Call transaction DB2. Choose Checks/Settings Correct Jobheads Modify the necessary data.

End of: SAP Web AS 6.40 |

2010-01-25

PUBLIC

109/144

.This page is left blank for documents that are printed on both sides.

■ The correct directory structure for R3load dump files must exist on both the source and target hosts.1 R3load Procedures Using the Migration Monitor Purpose The Migration Monitor is a tool that helps you to perform and control the unload and load process during the system copy procedure.1 Additional Information R3load Procedures Using the Migration Monitor 7 Additional Information 7.1. The Migration Monitor is integrated into the SAPinst system copy tool. 7. you need an R3load version with at least patch level 73 (compile date: 12. Prerequisites ■ JRE version 1.2008).7 7. The Migration Monitor ■ creates R3load command files ■ creates R3load task files if required ■ starts R3load processes to unload the data ■ transfers packages from the source to the target host if required ■ starts R3load processes to load the data as soon as a package is available ■ informs the person performing the system copy in the case of errors The Migration Monitor has to be started on the source database host (Export Monitor) and on the target database host (Import Monitor).01. CAUTION If you want to convert a non-Unicode system to Unicode using the Socket option.1 Configuration Help The tool will display the available parameters. if you call it with one of the following options: ■ ■ -help -? 2010-01-25 PUBLIC 111/144 .5 or higher ■ The JAVA_HOME environment variable must point to the JRE directory. but you can also use the monitor to copy older releases by starting it manually.

3 (info). R3SETUP) write their log files. When the Migration Monitor is used without the installation tools. the monitor thread sleeps and does not analyze any files or its processing state.7 (trace) Export Options Option installDir Description Comments Installation directory exportDirs List of export directories client Client operating mode The installation start directory is the directory in which the installation tools (SAPinst. if you call it with the following option: ■ -version General Options Name monitorTimeout Description Comments Monitor timeout in seconds During a timeout.DB. The subdirectories DATA. 1 (error). off. default).1 Additional Information R3load Procedures Using the Migration Monitor Version The tool will display the version information (release branch and build date).’ Separator on UNIX: ‘:’ The ‘exportDirs’ parameter points to the directory to which the R3load dump files will be written.6. E-Mail Options Name mailServer Description Comments SMTP server “From” e-mail address “To” e-mail address Server name or IP address of the company SMTP server Can contain an address list separated by ‘. Separator on Windows: ‘. Running in client mode means that the Monitor runs parallel with the 112/144 PUBLIC 2010-01-25 . 5. 4 (config. the installation start directory is the directory where the R3load TSK and log files will be created.’ or blanks. 2 (warning).7 7. mailFrom mailTo Trace Option Name trace Description Comments Trace level Possible values: all. and DB/<TARGET_DBTYPE>(for example. DB/ORA) must exist in the exportDirs’ directory. The default timeout value is 30 seconds.

specify the parameter ‘server’ in the Export Monitor's properties file. orderBy Package order Can be the ‘name’ or path of the file that contains package names.TSK’ already exist then the monitor will not overwrite them. If the option value is omitted then package order is not determined. loadArgs Additional R3load arguments for the Appended to the R3load command LOAD phase line. the default is R3load. tskFiles 'yes' to create task files. p. Network Exchange Options Option net Description Comments Network operating mode Network exchange directory netExchangeDir Exported dump files must be visible on the import host to use this mode. expJobNum Number of parallel export jobs. 1100 taskArgs Additional R3load arguments for the Appended to the R3load command TASK phase line. Must be writable for the export 2010-01-25 PUBLIC 113/144 . dataCodepage Code page for data files Refer to SAP Note 552464. Possible values: 4102. If you want to run the Export Monitor in the server mode. server Server operating mode Running in server mode means that the Monitor will create R3load TSK files (if necessary). -datacodepage. that is.7 7. If only the name of the R3load executable is available.7 ‘yes’. -l. -o (if the omit argument is specified and task files are not used. r3loadExe Path of the R3load executable Optional. The Import Monitor always runs in the server mode. -socket (if the socket option is specified). Options already set by the monitor: -ctf. -o (if the omit argument is specified). -r. All options below are for the server mode. 0 for an default is 1. the value of the ‘tskFiles’ option is ‘no’). Used for communication between the export and import monitors. Options already set by the monitor: -e. 4103. R3load cmd files and start the R3load processes. then JVM looks for the R3load executable using OS-specific process search rules. If the R3load task files ‘*.1 Option Additional Information R3load Procedures Using the Migration Monitor Description Comments standard SAPinst export process and transfers the exported dump files onto the import server. -l. as of version 4.6. the Any positive number. this must be set to ‘no’. 'no' to skip Before version 4. unlimited number of jobs.

Export Socket Host Option socket Description Comment Socket operating mode R3load will not write dump files to the file system. Any positive number.7 7. FTP Exchange Options Option ftp Description Comments FTP operating mode ftpHost Remote FTP host Name of the remote FTP user ftpUser Exported dump files will be transferred automatically from the source host (directory ‘exportDirs’) to the target host (directory ‘importDirs’) using FTP. Used for communication between the export and import monitors.’ or ‘:’ separators are valid. Name or IP address of the import server. The FTP user specified here should be the <sapsid>adm to make sure that the package files can be read during the import (which is started as <sapsid>adm). the default is 1.1 Option Additional Information R3load Procedures Using the Migration Monitor Description Comments monitor and readable for the import monitor. Security risk! Both ‘. This is the directory on the target host to which the dump will be transferred.SGN to the FTP exchange directory as a signal for the import monitor that the package has been exported successfully and the import can be started. 0 for an unlimited number of jobs. but the export and 114/144 PUBLIC 2010-01-25 . CAUTION ftpPassword Password of the remote FTP user List of remote FTP directories for export dump ftpExportDirs ftpExchangeDir Remote FTP exchange directory ftpJobNum Number of parallel FTP jobs. The export monitor writes a file <package>.SGN to the network exchange directory as a signal to the import monitor that the package is exported successfully and the import can be started. Must be writable for the export monitor and readable for the import monitor. The export monitor writes a file <package>. The value will be the same as for ‘importDirs’ in the import monitors property file.

The value will be the same as for ‘importDirs’ in the import monitors property file.1 Option Additional Information R3load Procedures Using the Migration Monitor Description Comment host Remote import host Host port number port import work through the socket connection. and DB/ <TARGET_DBTYPE> (e.’ Separator on UNIX: ‘:’ The subdirectories DATA. the DDL*. This is the directory on the target host to which the dump will be transferred. and the R3load EXT files (if required) in the subdirectory DB/ <TARGET_DBTYPE>. Name or IP address of the import host. Separator on Windows: ‘. Name or IP address of the import server.TPL files in the subdirectory DB. CAUTION: Security risk Both ‘. Must be the same as the port number on the import host. The FTP user specified here should be the <sapsid>adm to make sure that the package files can be read during the import (which is started as <sapsid>adm).’ or ‘:’ separators are valid. DB/ORA) must exist in the ‘exportDirs’ directory.7 7. The R3load STR files must exist in the subdirectory DATA. Any other option is ignored by Import Monitor.g. Any free port on the import host from 1024 to 65535. DB. Mandatory Options for Export Monitor ■ Client mode: 2010-01-25 PUBLIC 115/144 . FTP Copy Options Option ftpCopy Description Command FTP copy operating mode exportDirs List of export directories ftpHost Remote FTP host Name of the remote FTP user ftpUser ftpPassword ftpExportDirs Password of the remote FTP user List of remote FTP directories for export dump Used as a separate program call for migration with sockets. All files produced by R3lctl and R3szchk will be transferred from the source to the target host using FTP.

Import Options Option installDir Description Comment Installation directory importDirs orderBy r3loadExe tskFiles The installation start directory is the directory in which the installation tools (SAPinst. ftpExchangeDir NOTE The value of the dbType option is determined automatically in the shell script/batch files from the dbms_type environment variable. one of the options ftp. When the migration monitor is used without the installation tools. ■ Server mode: net (and their related parameters) installDir. The subdirectories DATA. R3SETUP) write their log files.1 Additional Information R3load Procedures Using the Migration Monitor installDir. exportDirs. net.6 this must be set to ‘no’. all export dump files are available on the import host before the import monitor is started. as of version ‘no’ to skip 4. ftpUser.7 it must be set to ‘yes’ If the R3load task files ‘*. size: load packages starting with the largest one. Values can be: name: load packages in alphabetical order. ftpExportDirs.7 7. If only the name of the executable R3load executable is available then JVM looks for the R3load executable using OS-specific process search rules.’ Separator on UNIX: ‘:’ The ‘importDirs’ parameter points to the directory to which the R3load dump files will be written. socket (and their related parameters) ■ FTP copy: exportDirs. one of the options ftp. Path of the R3load Optional. DB and DB/<TARGET_DBTYPE> (for example. where the R3load TSK and log files will be created. Before version 4. 116/144 PUBLIC 2010-01-25 . If the option is omitted then package order is not defined. Package order This option is used only if the import monitor works without the export monitor in stand-alone mode. exportDirs. tskFiles. that is. DB/ORA) must exist in the ‘importDirs’ directory. List of import directories Separator on Windows: ‘. or a path of the file that contains package names. the default is R3load.TSK’ already exist then the monitor will not overwrite them. the installation start directory is the directory. ftpHost. ‘yes’ to create task files.

Add EXT file entries to cmd files.properties (for example. -o (if the omit argument is specified). the default jobs is 1. If the EXT files cannot ‘no’ to skip them be found in the DB/<TARGET_DBTYPE> import dump subdirectory the package processing is aborted. -l. -p. -k. -socket (if the socket option is specified). Import Exchange Options Option exchangeDir Description Comment Exchange directory If this option is not set. 1100 Migration key R3load omit value Can contain only 'DTPIV' letters. do not create views If you want to combine several omit options. the value of ‘tskFiles’ option is ‘no’). ‘-o TV’). -l. then the monitor runs in stand-alone mode. Possible values: 4102. All the export dump files or the SAP export CDs from the installation kit must be available on the import host and be specified with the parameter ‘importDirs’ (for example. -r. do not create primary keys -o I: omit indexes. 0 for an unlimited number of import jobs. -o D : omit data. remove this file. do not load data -o T: omit tables. do not create indexes -o V: omit views. list these options without blanks (for example. Database code page for Refer to SAP Note 552464. from a previous export run). the target database 4103. -dbcodepage. -o (if the omit argument is specified and task files are not used. do not create tables -o P: omit primary keys. in the properties file). that is without the Export Monitor. 2010-01-25 PUBLIC 117/144 . arguments for the LOAD Options already used by the monitor: phase -i. Import Socket Options Option socket port Description Command Socket operating mode Server port number Any free port from 1024 to 65535. Additional R3load Appended to the R3load command line. that is. Additional R3load Appended to the R3load command line. arguments for the TASK Options already set by the monitor: phase -ctf.7 7. Number of parallel Any positive number. If there is an old file export_statistics.1 Option Additional Information R3load Procedures Using the Migration Monitor Description Comment extFiles dbCodepage migrationKey omit taskArgs loadArgs impJobNum ‘yes’ to include EXT files.

Packages not listed in the DDL mapping file use the default DDL control file. importDirs.1 Additional Information R3load Procedures Using the Migration Monitor Any other option is ignored by the import monitor. extFiles NOTE The value of the dbType option is determined automatically in the shell script/batch files from the dbms_type environment variable.txt # !!! line with [GROUP_NAME] can be skipped # used for documentation purposes only [ SORTED UNLOAD ] # DDL file for sorted unload ddlFile = /export_dump/ABAP/DB/ORA/DDLORA. which then has to be specified via the ddlMap option within the migration monitor's properties file.1. tskFiles./DDLORA_LRG. extFiles. 7.TPL # package names SAPAPPL0 SAPAPPL1 SAPSDIC [ UNSORTED UNLOAD ] DDL file for unsorted unload ddlFile = . one of the options exchangeDir or socket (and their related parameters) ■ Stand-alone mode: installDir. The assignment of a specific DDL file to a single package is done within a simple text file.2 Assigning DDL Files to Packages It is possible to use several different DDL*. Mandatory Options for Import Monitor ■ Server mode (default): installDir. Procedure Example of a DDL mapping file: # DDL mapping file ddl_mapping. tskFiles.TPL # table names TABLE_A TABLE_B TABLE_C 118/144 PUBLIC 2010-01-25 .7 7. importDirs.TPL templates during the export or during the import.

you can specify different values for the parameters jobNum and taskArgs / loadArgs per package.1 Additional Information R3load Procedures Using the Migration Monitor 7.1. By defining groups you can prevent parallel execution of certain packages and you can define how many large tables are exported or imported at the same time. These tasks will automatically be synchronized by the migration monitor. Package groups can be defined in the same text file in which the package order can be defined (refer to parameter orderBy). The old package order format is also fully supported.4 Processing Split Tables Before the import starts. and Windows ■ MS SQL You can ensure this by using the feature Defining Groups of Packages [page 119]. If package groups are defined.7 7. Procedure Example of a package order file with group: # custom package order # package names SAPAPPL0 SAPAPPL1 SAPAPPL2 # package group [ SEQUENTIAL GROUP ] jobNum = 1 # table names TABLE_A TABLE_B TABLE_C 7.1. The following database platforms do not support parallel data import: ■ IBM DB2 for Linux. WHR files are part of the package and have to be copied to the DATA export subdirectory to make sure that the same WHR file is used for the export and the import of the corresponding package. if tables have been split during the export it must be ensured that the table exists and that the primary key and the indexes are created before/after (as defined in the DDL template) the table data has been imported. In addition.3 Defining Groups of Packages The “package group” feature is an enhancement of defining a package order. UNIX. 2010-01-25 PUBLIC 119/144 . All packages without a package group will be assigned to a “default group” with the number of jobs which was defined in the migration monitor's properties file. the maximum number of parallel R3load jobs is the sum of jobNum of all packages.

Now you want to run a maximum of 10 R3load processes for parallel data import. The inputFile. For every group (MY_FIRST_TABLE and MY_SECOND_TABLE) a R3load job is started. the parameter jobNum in the import_monitor_cmd. using the WHERE condition assigned to this package. Restart for all other database platforms: 1. Procedure Create the file inputFile.txt with the following content: [ MY_FIRST_TABLE ] jobNum = 1 MY_FIRST_TABLE-1 MY_FIRST_TABLE-2 MY_FIRST_TABLE-3 [ MY_SECOND_TABLE ] jobNum = 1 MY_SECOND_TABLE-1 MY_SECOND_TABLE-2 MY_SECOND_TABLE-3 MY_SECOND_TABLE-4 MY_SECOND_TABLE-5 In this file.7 7.1 Additional Information R3load Procedures Using the Migration Monitor Procedure Example: Target database does not support parallel data import Use During the export you have split the table MY_FIRST_TABLE into 3 packages and MY_SECOND_TABLE into 5 packages. The number of parallel R3load jobs will be the total of the number of R3load jobs of each group plus the number of R3load jobs defined for the default group (which is made up of all packages without an explicit group name). Eliminate the reason for the failure of the import of the package(s). The deletion with a WHERE clause can be very time consuming so it is faster to delete all rows of the corresponding table manually and re-import all packages instead. defined by the parameter jobNum. before starting the data import again. you can also define the processing order of packages or you can assign DDL files to packages. 2.properties file has to be set to 8 to ensure that not more than 10 R3load processes run in parallel. In this example. Manually delete all rows of the table for which the import of one or more packages failed. 120/144 PUBLIC 2010-01-25 . the rows which belong to this package have to be deleted.txt file has to be specified as a value for the migration monitor parameter orderBy. Re-Starting the Import of a Split Table Package If the import of a package fails.

Restart the import. any options that are not recognized are ignored. Remove the TSK files of all packages which import data into this table (<table name><counter>__TPI.bat / import_monitor. Run the command call qp2term. Replace the status '+' of all packages for the corresponding table.sh / import_monitor. To specify an option: ■ in the command line. enter -optionName optionValue 2010-01-25 PUBLIC 121/144 .7 7. 7.sh 3. Templates for these files are included in the application archive and must be located in the current user's working directory.properties.sh / import_monitor.bat End of: Windows | ■ Only valid for: IBM i5/OS | IBM i specific 1. Any options specified in the command line take precedence over the corresponding options in the application property file. 4. Do not remove the TSK files which create the table or which create the indexes for this table. Check that the environment variable PASE_THREAD_ATTACH is set to 'Y': WRKENVVAR PASE_THREAD_ATTACH='Y' End of: IBM i5/OS | You can specify options in the command line or in the export or import property files [page 111]. 2. The names of the property files are export_monitor_cmd.sh / export_monitor_secure. Set the JAVA_HOME environment as follows: export JAVA_HOME=/QIBM/ProdData/Java400/jdk14 4. Adapt the file import_state.5 Starting the Migration Monitor The tool can be started using one of the following: ■ Only valid for: UNIX | The UNIX shell scripts export_monitor.properties in the installation directory.1. export_monitor.TSK). which had been imported successfully and has to be reimported by '0' (refer to Restarting R3load Processes [page 51]).1 Additional Information R3load Procedures Using the Migration Monitor 3.bat / export_monitor_secure.properties and import_monitor_cmd.sh End of: UNIX | ■ Only valid for: Windows | The Windows batch files export_monitor. Options are case-sensitive. 5.

bat –socket End of: Windows | If FTP access is used and security is required.sh –ftp End of: UNIX | Only valid for: UNIX | . Example of an export_monitor_cmd.sh –ftpPassword <password> End of: UNIX | Procedure 1. Start the monitor and close the shell window / command processor. insert the new line optionName=optionValue Only valid for: UNIX | Example of a command line for a UNIX terminal: End of: UNIX | Only valid for: UNIX | ./export_monitor./export_monitor.1 Additional Information R3load Procedures Using the Migration Monitor ■ in the application property file. 2.sh –ftpCopy End of: UNIX | Only valid for: UNIX | .exe: End of: Windows | Only valid for: Windows | export_monitor.log and *. start the monitor using the secure version of the shell script/batch file to prevent seeing the FTP password in the command line parameter string / property file.bat –net End of: Windows | Only valid for: Windows | export_monitor.properties file with export options: # Export Monitor options # Operating mode: ftp | net #net 122/144 PUBLIC 2010-01-25 .7 7. Only valid for: UNIX | Example of a command line for a UNIX terminal: End of: UNIX | Only valid for: UNIX | . The monitor process will run in the background.sh –socket –host <import server> –port 5000 End of: UNIX | Only valid for: Windows | Example of a command line for Windows cmd.console.log files to check monitor processing state. Use monitor *./export_monitor./export_monitor_secure.

7 7. ftpExportDirs=/install_dir/export_dump # Remote FTP exchange directory ftpExchangeDir=/install_dir/exchange # Number of parallel FTP jobs ftpJobNum=3 # # E-mail options # # SMTP server mailServer=sap-ag. separator on Windows .com mail@yahoo.properties file with import options: 2010-01-25 PUBLIC 123/144 .com # "To" email address mailTo=mail@sap.1 ftp # Additional Information R3load Procedures Using the Migration Monitor # Common options # # List of export directories.de # "From" email address mailFrom=mail@sap.com Example of an import_monitor_cmd. separator : or . on UNIX : exportDirs=C:\TEMP\export_dump # SAPinst start directory installDir=C:\install\start # Monitor timeout in seconds monitorTimeout=30 # # FTP options # # Remote FTP host ftpHost=server # Name of remote FTP user ftpUser=sysadm # Password of remote FTP user ftpPassword=password # List of remote FTP directories for export dump.

on UNIX : importDirs=/install_dir/export_dump # SAPinst start directory installDir=/install_dir/start # Exchange directory exchangeDir=/install_dir/exchange # Generation of task files: yes | no tskFiles=yes # Inclusion of extent files: yes | no extFiles=yes # Monitor timeout in seconds monitorTimeout=30 # # R3load options # # DB code page for the target database dbCodepage=1100 # Migration key migrationKey= # Additional R3load arguments for TASK phase taskArgs= # Additional R3load arguments for LOAD phase loadArgs= # Number of parallel import jobs impJobNum=3 # # E-mail options # # SMTP server mailServer=sap-ag.com mail@yahoo.com # "To" email address mailTo=mail@sap.7 7.de # "From" email address mailFrom=mail@sap. separator on Windows .1 Additional Information R3load Procedures Using the Migration Monitor # Import Monitor options # # Common options # # List of import directories.com 124/144 PUBLIC 2010-01-25 .

the /install_dir/export_dump/DB directory the files DDL<DBTYPE>.7 7. cmd files. the export monitor will write a signal file <package>. ■ The R3load log files. the following directories have to exist (refer to parameter exportDirs): ● c:\temp\export_dump\DATA ● c:\temp\export_dump\DB ● c:\temp\export_dump\DB\ORA The c:\temp\export_dump\DATA directory must contain the STR files generated by R3ldctl.SGN is found in the /install_dir/exchange (parameter: exchangeDir) directory. and TSK files (if required) will be located in the directory / install_dir/start (parameter: installDir). the export monitor will transfer all files belonging to that package (TOC. EXT. cmd files.) to the target host (parameter: ftpHost) into the corresponding subdirectories of the directory /install_dir/export_dump (parameter: ftpExportDirs) as user <sapsid>adm (parameter: ftpUser)..TPL generated by R3ldctl. identified by password (parameter: ftpPassword). The export itself is not done by the export monitor. 001. and TSK files (if required) are located in the directory c:\install \start (parameter: installDir). ■ The import monitor will start to import a package as soon as the file <package>. to log on.TPL has to be copied to the directory /install_dir/start (parameter: installDir) before you can start the import monitor. the following directories have to exist (see parameter importDirs): ● /install_dir/export_dump/DATA ● /install_dir/export_dump/DB ● /install_dir/export_dump/DB/ORA The /install_dir/export_dump/DATA directory has to contain the STR files generated by R3ldctl.. and the c:\temp \export_dump\DB\ORA directory the EXT files generated by R3szchk.SGN to the /install_dir/exchange (parameter: ftpExchangeDir) directory to notify the import monitor that it can start importing this package. the c: \temp\export_dump\DB directory the files DDL<DBTYPE>. ■ The export monitor will write the R3load dump files and the TOC files to the directory c:\temp \export_dump\DATA.. ■ On the import host. ■ The R3load log files. the /install_dir/export_dump/DB/ORA directory the EXT files generated by R3szchk. . STR. ■ If the package files have been completely transferred to the server. ■ As soon as a package has been exported successfully. as the monitor is started in client mode (parameter ‘server’ is not set). 2010-01-25 PUBLIC 125/144 .TPL also generated by R3ldctl. ■ The file DDLORA.1 Additional Information R3load Procedures Using the Migration Monitor What happens during export / import with the above listed property files during a system copy with Oracle as source and target database: ■ On the export host.

7 7.1

Additional Information R3load Procedures Using the Migration Monitor

7.1.6 Output Files
Export

■ ■ ■

export_monitor.log export_state.properties ExportMonitor.console.log

Import

■ import_monitor.log ■ import_state.properties ■ ImportMonitor.console.log Both the export and import state files contain package state lines such as the following: SAPUSER=+ Format of lines is <PACKAGE>=<STATE>. Possible values for state are:
0 ? + Package export/import not yet started. Package export/import in progress. Package export/import finished with errors. Package export/import finished successfully.

If any ftp/net exchange options are used, then the export state file may contain a second <STATE> column, which refers to the state of the package transfer. Then the export state file contains package state lines such as the following: SAPUSER=++ Format of lines is <PACKAGE>=<STATE>. Possible values for state are:
0 ? +0 +? +++ Package export not yet started. Package export in progress. Package export finished with errors. Package export finished successfully; package transfer not yet started. Package transfer in progress. Package transfer finished with errors. Package transfer finished successfully.

7.1.7 Installing the Target System Using the Migration Monitor
Prerequisites

Make sure that there is enough free space in the target system for the database load. To find out the size of the export and the sizes of the tablespaces or dbspaces that are created, look at the file DBSIZE.XML located in the directory <DRIVE>:\<EXPDIR>\DB\<DATABASE> (Windows) or <EXPDIR>/DB/ <DATABASE> (UNIX).

126/144

PUBLIC

2010-01-25

7 7.2

Additional Information Using SAPinst GUI

Procedure

1.

2. 3.

4.

If you want to start the installation of the target host using the migration monitor, make sure that at least the dump directory with the following files is accessible on the target host and contains the correct data before you start SAPinst: ■ <dump dir>/LABEL.ASC ■ <dump dir>/DB/<DBTYPE>/DBSIZE.XML ■ <dump dir>/DB/DDLORA.TPL If the dump directory is not shared on the target host, you can copy the files from the source system to the target system as soon as they have been created on the source host, using the (export) migration monitor's FTP Copy options. Start SAPinst as described in the installation documentation for your SAP component. To install the target system, follow the instructions in the SAPinst input dialogs and enter the required parameters up to the screen ABAP System > Database. On this screen, choose Standard System Copy/Migration (R3load-Based). Select the option Use Migration Monitor.
NOTE

5. 6.

If you need more information about input parameters, position the cursor on the field of the respective parameter and press F1. When SAPinst displays the CD browser-window and asks for the Export Migration CD, enter the path to the export directory <EXPDIR>. Continue as described in the installation documentation for your SAP component until a dialog box appears that states:
If the export has been started on the source system and the export monitor is running, you can now start the data load by starting the import monitor.

7. 8.

Check that the prerequisites in the dialog box are fulfilled by your system. If so, you can start the migration monitor. Complete the installation as described in the installation documentation for your SAP solution.
CAUTION

If you have to restart the import after an error, just restart SAPinst. The import is continued with the table that was not imported successfully.

7.2 Using SAPinst GUI
The following table shows the most important functions that are available in SAPinst GUI:
SAPinst GUI Functions Input Type Label
F1

Description

Function key

Displays detailed information about each input parameter

2010-01-25

PUBLIC

127/144

7 7.3

Additional Information Interrupted Installation with SAPinst Label Description

Input Type

Menu option

File

Exit

Stops the SAPinst GUI, but SAPinst and the GUI server continue running
Only valid for: SAP CRM;SAP ERP;SAP NetWeaver;SAP SCM;SAP Solution Manager;SAP SRM |

NOTE

If you need to log off during the installation from the host where you control the installation with SAPinst GUI, the installation continues while you are logged off. You can later reconnect to the same SAPinst installation from the same or another host. For more information, see Starting SAPinst GUI Separately [page 133].
End of: SAP CRM;SAP ERP;SAP NetWeaver;SAP SCM;SAP Solution Manager;SAP SRM |

Menu option

SAPinst

Log Browser

Menu option

SAPinst

Cancel

Message button Message button

Retry Stop

Message button

Continue

Displays the Log Viewer dialog This dialog enables you to access the following log files directly: ■ Installation log (sapinst_dev.log) ■ Log files from the SAPinst GUI server Cancels the installation with the following options: ■ Stop Stops the installation (SAPinst GUI, SAPinst, and the GUI server) without further changing the installation files You can restart and continue the installation later from this point. ■ Continue Continues the installation Performs the installation step again (if an error has occurred) Stops the installation without further changing the installation files You can continue the installation later from this point. Continues with the option you chose previously

7.3 Interrupted Installation with SAPinst
The SAP system installation might be interrupted for one of the following reasons: ■ An error occurred during the Define Parameters or Execute phase: SAPinst does not abort the installation in error situations. If an error occurs, the installation pauses and a dialog box appears. The dialog box contains a short description of the choices listed in the table below as well as a path to a log file that contains detailed information about the error.

128/144

PUBLIC

2010-01-25

closing the dialog box. CAUTION Make sure that the root user has not set any environment variables for a different SAP system or database.7 7. Access installation log files. because this kills the process immediately. Therefore. 1.xml file. 2010-01-25 PUBLIC 129/144 . Only valid for: Unix | Mount your Installation Master DVD. End of: Windows | 2. you can continue the installation from the point of failure without repeating any of the previous steps (see the procedure below). End of: Windows | 4. Only valid for: Windows | Log on as a user who is a member of the local administrators group. This is possible because SAPinst records the installation progress in the keydb. SAPinst displays the same dialog box again. If the same or a different error occurs. the SAPinst GUI. The following table describes the options in the dialog box: Option Definition Retry Stop Continue View Log Only valid for: UNIX | SAPinst retries the installation from the point of failure without repeating any of the previous steps. or to continue an interrupted installation after an error situation. Only valid for: Windows | Insert the Installation Master DVD in your DVD drive. Only valid for: UNIX | Log on to your local UNIX host as user root. and the GUI server. and then choose Retry. SAPinst stops the installation. End of: UNIX | Procedure This procedure describes the steps to restart an installation. we do not recommend that you use Ctrl + C . However. which you stopped by choosing Stop. try to solve the problem. SAPinst continues the installation from the current point.xml file. SAPinst records the installation progress in the keydb. NOTE You can also terminate SAPinst by choosing Ctrl + C . We recommend that you view the entries in the log files.3 Additional Information Interrupted Installation with SAPinst ■ You interrupted the installation by choosing Cancel in the SAPinst menu. End of: UNIX | 3.

130/144 PUBLIC 2010-01-25 . We do not recommend using Network File System (NFS). If a process is still running. From the tree structure in the Welcome screen.3 Additional Information Interrupted Installation with SAPinst NOTE Mount the DVD locally. ■ If you used the default installation directory (recommended): cd <Mapped_Drive>:\<Copied Installation Master DVD>\IM_OS400_PPC64 sapinst. Only valid for: Unix | Enter the following commands: cd <Installation_Master_DVD>/IM_<OS> .exe ■ If you used an alternative installation directory: cd <Mapped_Drive>:\<your installation directory> <Mapped_Drive>:\<Copied Installation Master DVD>\IM_OS400_PPC64\sapinst. End of: Windows | 6.exe. look for javaw. 9. The What Do You Want to Do? screen appears. you can no longer continue the old installation option. NOTE If there is only 1 component to install. EXAMPLE log_01_Oct_2008_13_47_56 Continue with the Old Option SAPinst continues the interrupted installation option from the point of failure. Only valid for: Windows | Change to the required directory: <DVD drive>:\IM_WINDOWS_<platform> Double-click sapinst. the Welcome screen does not appear. Instead. Afterwards. the following naming convention is used: <log_day_month_year_hours_minutes_seconds>.exe End of: IBM i5/OS | 8. it moves the content of the old installation directory and all installationspecific files to a backup directory. select the installation service that you want to continue and choose Next. decide between the following alternatives and confirm with OK: Behavior Alternative Run a New Option SAPinst does not continue the interrupted installation option./sapinst End of: Unix | 7. In the What Do You Want to Do? screen. For the backup directory. End of: Unix | 5. Only valid for: IBM i5/OS | Check if a SAPinst GUI Java process is still running.7 7.exe under Processes in your Task Manager and kill it.

For more information.4 Performing a Remote Export Using SAPinst Purpose You can run the SAPinst GUI in standalone mode to perform a remote export. SAPinst and the GUI server run on the remote host. In this case. The local host is the host from which you control the installation with SAPinst GUI. Only valid for: UNIX.Windows | Linux. SAP no longer delivers any JCE policy archives within the SAP Java Virtual Machine (SAP JVM). Prerequisites ■ You have performed the preparation activities for your local host (SAPinst GUI host) and your remote host as described in Prerequisites in Exporting the Source System Using SAPinst [page 34].4 Additional Information Performing a Remote Export Using SAPinst 7. Start the SAPinst GUI on your local host. 2. 3. We recommend you use the Hummingbird Exceed X Server. End of: UNIX.4.Windows | Linux. and SAPinst GUI runs on the local host. Perform the installation using the SAPinst GUI. see SAP Note 1170809. which we use to validate installations with SAPinst. ● Log on to the local host and enter the command ping <remote host>.Windows | CAUTION The behavior of SAPinst has changed compared to previous versions. Process Flow 1. You have to download the required Java Cryptography Extension (JCE) policy zip file from SAP on the remote host.1 Performing a Remote Installation with SAPinst You use this procedure to install your SAP system on a remote host. This enables you to perform the export on another host (the remote host) while monitoring the export with the SAPinst GUI on your local Windows or UNIX computer (the local host). Start the SAPinst server on your remote host. 2010-01-25 PUBLIC 131/144 . To test this: ● Log on to your remote host and enter the command ping <local host>.7 7. ■ Both computers are in the same network and can ping each other. Alternatively you can use an X server for Microsoft Windows or other remote desktop tools such as VNC Viewer or NX Server / NX Client – offered by various vendors or open source – for remote access to SAPinst GUI on Windows workstations. For more information. For more information. see: ■ Starting SAPinst on the Remote Host [page 131] ■ Starting SAPinst GUI Separately [page 133] 7.Windows | You can run SAPinst GUI on a PC with 32-bit while SAPinst is running on a 64-bit installation host. see SAP Note 1238121.

End of: IBM i5/OS.Windows | Only valid for: UNIX | 1. 132/144 PUBLIC 2010-01-25 . To test this: 1. Enter the following commands: Only valid for: IBM DB2 for Linux and UNIX and Windows. Log on to the local host and enter the command ping <remote host>. Download the JCE policy zip file from SAP as described in SAP Note 1240081. 2.7 7. Insert the Installation Master DVD in the DVD drive on your remote host. Procedure Only valid for: IBM i5/OS. port <port_number> to continue with the installation 6.No Database. End of: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS | Prerequisites ■ Both computers are in the same network and can ping each other. Set the environment variable JCE_POLICY_ZIP to the location of the downloaded policy zip archive by entering the following command: set JCE_POLICY_ZIP=<policy zip archive> 5.MS SQL Server. Start SAPinst GUI on your local host as described in Starting SAPinst GUI Separately [page 133]. Log on to your remote host and enter the command ping <local host>.MS SQL Server. Log on to your remote host as user root.Windows | 1.MaxDB.MaxDB. 2.No Database. see Exporting the Source System Using SAPinst [page 34].IBM DB2 for z/OS.IBM DB2 for z/OS. Log on to your remote host as a user that is a member of the local administrators group.Oracle | cd <DVD drive>:\IM_WINDOWS_<platform> End of: IBM DB2 for Linux and UNIX and Windows. 3. waiting for a connection on host <host_name>.Oracle | Only valid for: IBM DB2 for i5/OS (Linux/Windows) | cd <mapped drives>:\IM_WINDOWS_X86_64 End of: IBM DB2 for i5/OS (Linux/Windows) | sapinst.4 Additional Information Performing a Remote Export Using SAPinst Only valid for: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS | CAUTION If you install SAP instances on IBM i.exe -nogui For more information about how to perform the export. 4. “local host” in this section refers to the Windows installation host. You see the following at the command prompt: guiengine: no GUI connected. not the IBM i host. SAPinst now starts and waits for the connection to the SAPinst GUI.

see Exporting the Source System Using SAPinst [page 34].7 7.Oracle | cd <mountpoint_of_Installation_Master_DVD>/IM_<OS> End of: IBM DB2 for Linux and UNIX and Windows. Make sure that the root user has not set any environment variables for a different SAP system or database. End of: UNIX | Only valid for: IBM i5/OS.2 Starting SAPinst GUI Separately You use this procedure to start SAPinst GUI separately. 2010-01-25 PUBLIC 133/144 . Download the JCE policy zip file from SAP as described in SAP Note 1240081. You might need to start SAPinst GUI separately in the following cases: ■ Only valid for: IBM DB2 for i5/OS | You are running IBM i and did not set a DISPLAY environment variable.No Database.MaxDB.No Database.IBM DB2 for z/OS. waiting for a connection on host <host_name>. Enter the following commands: Only valid for: IBM DB2 for Linux and UNIX and Windows. End of: IBM DB2 for i5/OS | ■ You have logged off from SAPinst. 6.IBM DB2 for z/OS.Windows | 7. Start SAPinst GUI on your local host as described in Starting SAPinst GUI Separately [page 133]. SAPinst now starts and waits for the connection to the SAPinst GUI./sapinst -nogui For more information about how to perform the export.Oracle | Only valid for: UNIX | IBM DB2 for i5/OS (Linux/Windows) | cd <Installation_Master_DVD>/DATA_UNITS/IM_LINUX_PPC64 End of: UNIX | IBM DB2 for i5/OS (Linux/Windows) | . You see the following at the command prompt: guiengine: no GUI connected. 3.4 Additional Information Performing a Remote Export Using SAPinst CAUTION 2.MS SQL Server.4.MaxDB.UNIX. Mount the Installation Master DVD. port <port_number> to continue with the installation. Set the environment variable JCE_POLICY_ZIP to the location of the downloaded policy zip archive as follows: Shell Used Command JCE_POLICY_ZIP=<policy zip archive> export JCE_POLICY_ZIP Bourne shell (sh) C shell (csh) Korn shell (ksh) setenv JCE_POLICY_ZIP <policy zip archive> export JCE_POLICY_ZIP=<policy zip archive> 5.MS SQL Server. 4.

IBM DB2 for z/OS.MS SQL Server. change to the following directory: <Installation_Master_DVD>\IM_WINDOWS_I386 End of: IBM DB2 for Linux and UNIX and Windows.MaxDB.MaxDB. Only valid for: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS | CAUTION This is the default on IBM i. Since there is no GUI on IBM i. see SAP Note 1238121.No Database | <Installation_Master_DVD>\IM_0S400_PPC End of: IBM i5/OS | IBM DB2 for i5/OS. Log on as a member of the local administrators group.MaxDB. 2. ■ You want to perform a remote installation [page 131].MS SQL Server.4 Additional Information Performing a Remote Export Using SAPinst If you logged off during the installation and you later want to reconnect to the installation while it is still running.IBM DB2 for z/OS.IBM DB2 for z/OS. SAP no longer delivers any JCE policy archives within the SAP JVM. 5. you must start the SAPinst GUI separately. For more information.No Database | Only valid for: IBM DB2 for Linux and UNIX and Windows. If SAPinst GUI runs on a different host from SAPinst and the GUI server.No Database. Insert the SAP Installation Master DVD into your DVD drive. Download the JCE policy zip file from SAP as described in SAP Note 1240081. You have to download the required JCE policy zip file from SAP on the local host.Oracle | 134/144 PUBLIC 2010-01-25 .Oracle | NOTE If you want to start SAPinst GUI on a Windows 32-bit operating system. 3.7 7. Set the environment variable JCE_POLICY_ZIP to the location of the downloaded policy zip archive by entering the following command: set JCE_POLICY_ZIP=<policy zip archive> 4. you have to start SAPinst GUI separately on the local host.MS SQL Server. End of: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS | Procedure Starting SAPinst GUI on Windows 1.MS SQL Server.Oracle | <DVD drive>:\IM_WINDOWS_<platform> End of: IBM DB2 for Linux and UNIX and Windows. you can start SAPinst GUI separately. Change to the directory of the sapinst executables: Only valid for: IBM DB2 for Linux and UNIX and Windows.No Database. CAUTION The behavior of SAPinst has changed compared to previous versions.IBM DB2 for z/OS.MaxDB.Oracle | Only valid for: IBM i5/OS | IBM DB2 for i5/OS.

7 7.4

Additional Information Performing a Remote Export Using SAPinst
Only valid for: IBM DB2 for i5/OS;IBM DB2 for i5/OS (Linux/Windows) |

NOTE

If you want to start SAPinst GUI on a Windows 32-bit operating system, you can use the executable available in the DVD or change to the following directory:
<Installation_Master_DVD>\IM_WINDOWS_I386
End of: IBM DB2 for i5/OS;IBM DB2 for i5/OS (Linux/Windows) | Only valid for: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS |

NOTE

If you have a share ROOTBIN on your IBM i and you have mapped this share to the drive X, you can start the SAPinst GUI using your copied Installation Master DVD:
X:\tmp\<SID>\<Installation_Master_DVD>\IM_OS400_PPC_64
End of: IBM i5/OS | IBM i5/OS | IBM DB2 for i5/OS |

6.

Only valid for: AIX;HP-UX;IBM i5/OS;Linux;Solaris;Windows |

Start SAPinst GUI by double-clicking sapinstgui.exe SAPinst GUI starts and tries to connect to the GUI server and SAPinst, using the local host as default. If SAPinst and the GUI server are running on another host, SAPinst GUI cannot connect and the SAP Installation GUI Connection dialog appears. In this case, enter the name of the host on which SAPinst is running and choose Log on. The first dialog of the installation appears and you can perform the remote installation from your local host.
NOTE

Optionally you can start sapinstgui.exe with the following parameters: ■ host=<host name>, where <host name> is the host name of the installation host ■ port=<nr>, where <nr> is the port number for the connection to the GUI server ■ -accessible enables accessibility mode Example:
./sapinstgui.exe host=lsi1209 port=3000 -accessible
End of: AIX;HP-UX;IBM i5/OS;Linux;Solaris;Windows |

7.

Only valid for: z/OS |

Start SAPinst GUI in one of the following ways: ■ If SAPinst GUI runs on the same host as SAPinst and the GUI server, enter the following command:
startinstgui.bat

SAPinst GUI uses the local host as default. ■ If SAPinst and the GUI server runs on a different host from SAPinst GUI (remote installation), enter the following command:
startinstgui.bat -host <host_name> <host_name> is the host name of the installation host.

2010-01-25

PUBLIC

135/144

7 7.4

Additional Information Performing a Remote Export Using SAPinst NOTE

● If you enter the command without additional parameters, SAPinst GUI uses the local host as default. SAPinst GUI starts and tries to connect to the GUI server and SAPinst. Since SAPinst and the GUI server are running on another host, SAPinst GUI cannot connect and the SAP Installation GUI Connection dialog appears. In this case, enter the name of the host on which SAPinst is running and choose Log on. The first dialog of the installation appears and you can perform the remote installation from your local host. ● For a list of options to start SAPinst GUI, change to the same directory as your SAPinst executable and enter the command:
startinstgui.bat -h
End of: z/OS |

Starting SAPinst GUI on UNIX

1.

Log on as user root.
CAUTION

2. 3.

Make sure that the root user has not set any environment variables for a different SAP system or database. Download the JCE policy zip file from SAP as described in SAP Note 1240081. Set the environment variable JCE_POLICY_ZIP to the location of the downloaded policy zip archive as follows:
Shell Used Command
JCE_POLICY_ZIP=<policy zip archive> export JCE_POLICY_ZIP

Bourne shell (sh) C shell (csh) Korn shell (ksh)

setenv JCE_POLICY_ZIP <policy zip archive> export JCE_POLICY_ZIP=<policy zip archive>

4.

Mount your Installation Master DVD.
NOTE

5.

Mount the DVD locally. We do not recommend that you use Network File System (NFS). Change to the directory of the sapinst executables:
<mountpoint_of_Installation_Master_DVD>/IM_<OS> NOTE

If you want to start SAPinst GUI on a Linux 32–bit platform, change to the following directory:
<mountpoint_of_Installation_Master_DVD>/IM_LINUX_I386

6.

Only valid for: AIX;HP-UX;IBM i5/OS;Linux;Solaris;Windows |

Start SAPinst GUI by executing ./sapinstgui SAPinst GUI starts and tries to connect to the GUI server and SAPinst, using the local host as default.

136/144

PUBLIC

2010-01-25

7 7.4

Additional Information Performing a Remote Export Using SAPinst

If SAPinst and the GUI server are running on another host, SAPinst GUI cannot connect and the SAP Installation GUI Connection dialog appears. In this case, enter the name of the host on which SAPinst is running and choose Log on. The first dialog of the installation appears and you can perform the remote installation from your local host.
NOTE

Optionally, you can start sapinstgui with the following parameters: ■ host=<host name>, where <host name> is the host name of the installation host ■ port=<nr>, where <nr> is the port number for the connection to the GUI server ■ - accessible enables accessibility mode Example:
./sapinstgui host=lsi1209 port=3000 -accessible
End of: AIX;HP-UX;IBM i5/OS;Linux;Solaris;Windows |

7.

Only valid for: z/OS |

Start the SAPinst GUI in one of the following ways: ■ If SAPinst GUI runs on the same host as SAPinst and the GUI server, enter the following command without additional parameters:
./startInstGui.sh

By default, SAPinst GUI uses the local host. ■ If SAPinst and the GUI server run on a different host from SAPinst GUI (remote installation), enter the following command with additional parameters:
./startInstGui.sh -host <host_name> <host_name> is the host name of the installation host NOTE

● If you enter the command without additional parameters, SAPinst GUI uses the local host as default. SAPinst GUI starts and tries to connect to the GUI server and SAPinst. Since SAPinst and GUI server are running on another host, SAPinst GUI cannot connect and the SAP Installation GUI Connection dialog appears. In this case, enter the name of host on which SAPinst is running and choose Log on. The first dialog of the installation appears and you can perform the remote installation from your local host. ● For a list of options to start SAPinst GUI, change to the same directory as your SAPinst executable and enter the command:
./startInstGui.sh -h
End of: z/OS | End of: IBM i5/OS;UNIX;Windows |

2010-01-25

PUBLIC

137/144

and menu options.com /example 123456 Example Example EXAMPLE EXAMPLE 138/144 PUBLIC 2010-01-25 . SAP Note 123456 ■ Words or characters quoted from the screen. and names of installation. for example. These include field labels. names of variables and parameters. screen titles.sap. These include report names. messages ■ Source code or syntax quoted directly from a program ■ File and directory names and their paths. and database tools Technical names of system objects. menu options 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. pushbutton labels. SELECT and INCLUDE Keys on the keyboard http://www. ■ Cross-references to other documentation or published works ■ Output on the screen following a user action. menu names.Typographic Conventions Example <Example> Description Example Example Example Example Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system. program names. Arrows separating the parts of a navigation path. for example. upgrade. database table names. for example. for example. for example. transaction codes. “Enter your <User Name>”. and key concepts of a programming language when they are surrounded by body text.

DB2 Universal Database. without representation or warranty of any kind. Massachusetts Institute of Technology. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited. ByDesign. WebSphere. MVS/ESA. Oracle is a registered trademark of Oracle Corporation. iSeries. used under license for technology invented and implemented by Netscape. S/390 Parallel Enterprise Server. XML. Inc. RACF. ICA. RETAIN. Microsoft. AIX. and PowerPoint are registered trademarks of Microsoft Corporation. POWER6+. PowerPC. POWER5. These materials are subject to change without notice. UNIX. The information contained herein may be changed without prior notice. PostScript. and SAP Group shall not be liable for errors or omissions with respect to the materials. Parallel Sysplex. i5/OS. Power Architecture. and MultiWin are trademarks or registered trademarks of Citrix Systems. DB2 Connect. xApps. Duet. Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Excel. Outlook. OpenPower. OS/390. Adobe. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only. BladeCenter. Redbooks. POWER6.S. Data contained in this document serves informational purposes only. GPFS. All rights reserved. and Motif are registered trademarks of the Open Group. System p. OS/2.SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www. and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way. Windows.. System z10. System z9. WinFrame. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. HACMP. POWER. JavaScript is a registered trademark of Sun Microsystems. pSeries. SAP NetWeaver. the Adobe logo. xApp. and other countries. Nothing herein should be construed as constituting an additional warranty. System i. Netfinity. IBM. All other product and service names mentioned are the trademarks of their respective companies. as is any decompilation of these components. AS/400. z9. World Wide Web Consortium. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. MetaFrame. S/390. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. HTML. PowerVM. OSF/1. z/VM. Inc. X/Open. System i5. and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. DB2. z/OS. The information contained herein may be changed without prior notice. Intelligent Miner. PartnerEdge. if any. z10. zSeries. National product specifications may vary. OS/400. System Storage. eServer. System x. Citrix. System p5. VideoFrame. SAP. Disclaimer Some components of this product are based on Java™. POWER5+. xSeries. 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. XHTML and W3C are trademarks or registered trademarks of W3C®. R/3. BatchPipes. Linux is the registered trademark of Linus Torvalds in the U.sap. Java is a registered trademark of Sun Microsystems. Program Neighborhood.com © Copyright 2010 SAP AG. 2010-01-25 PUBLIC 139/144 . Acrobat. System z. SAP Business ByDesign. Inc.

Permission to use. modify. Customer shall maintain the following copyright and permissions notices on STLport sources and its documentation unchanged: Copyright 2001 SAP AG 5.org C++ library (STLport) and its documentation without fee. provided the above notices are retained. Moscow Center for SPARC makes no representations about the suitability of this software for any purpose. Boris Fomitchev makes no representations about the suitability of this software for any purpose. Note that for these third party products the following special terms and conditions shall apply. provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. 1. and a notice that the code was modified is included with the above copyright notice. and to all of the terms and conditions of this Agreement. It is provided “as is” without express or implied warranty. provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. using. SAP grants Customer a non-exclusive. modify. 2. 2. and conditions provided in accompanying permission notices are met: Copyright 1994 Hewlett-Packard Company Copyright 1996.97 Silicon Graphics Computer Systems Inc. Products in Data Processing Dietmar-Hopp-Allee 16 69190 Walldorf. provided the above notices are retained on all copies. non-transferable. Copyright 1997 Moscow Center for SPARC Technology. provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Germany (hereinafter: SAP) and you (hereinafter: Customer) 1. copy. or copying STLport or any portion thereof Customer agrees to abide by the intellectual property laws. 140/144 PUBLIC 2010-01-25 . The Customer may distribute binaries compiled with STLport (whether original or modified) without any royalties or restrictions. Subject Matter of the Agreement 1. provided that: ■ The conditions indicated in the above permissions notice are met. The Customer may distribute original or modified STLport sources. Hewlett-Packard Company makes no representations about the suitability of this software for any purpose. modify. 3. copy. royalty-free license to use the STLport. Applications. It is provided “as is” without express or implied warranty. By downloading. Permission to use. This software was developed using ANTLR. Permission to modify the code and to distribute modified code is granted. This material is provided "as is".Legal Software Terms Terms for Included Open Source Software This SAP software contains also the third party open source software products listed below. Silicon Graphics makes no representations about the suitability of this software for any purpose. distribute and sell this software and its documentation for any purpose is hereby granted without fee. distribute and sell this software and its documentation for any purposes is hereby granted without fee. Permission to use or copy this software for any purpose is hereby granted without fee. SAP License Agreement for STLport SAP License Agreement for STLPort between SAP Aktiengesellschaft Systems. 4. ■ The following copyright notices are retained when present. Copyright 1999. copy. distribute and sell this software and its documentation for any purposes is hereby granted without fee.2000 Boris Fomitchev Copyright 2001 SAP AG Permission to use. Any use is at your own risk. with absolutely no warranty expressed or implied. It is provided “as is” without express or implied warranty.

Adobe Document Services Adobe. SAP offers this liability and warranty obligations only towards its customers and only referring to its modifications. The Customer shall take adequate measures for the protection of data and programs. SAP shall not be liable for the loss of data and its recovery. Definitions: ■ "License" shall mean the terms and conditions for use. whether by contract or otherwise. Support and Maintenance SAP does not provide software maintenance for the STLport. provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. It is provided with a limited warranty and liability as set forth in the License Agreement distributed with this copy. All other services shall be charged according to the rates for services quoted in the SAP List of Prices and Conditions and shall be subject to a separate contract. the total liability for such damage and a maximum limit on the scope of any such damage shall depend on the extent to which its occurrence ought to have anticipated by SAP when concluding the contract. notwithstanding the other limitations of the present Art. Technical data.2 above. see SAP Note 854621. modify. and distribution as defined by Sections 1 through 9 of this document. Permission to use. or (iii) beneficial ownership of such entity. sales brochures. 6. Apache License. 4 includes claims against employees or agents of SAP. For the purposes of this definition. 2. copy. consequential damage caused by a defect or lost profit. to cause the direction or management of such entity. or are under common control with that entity. or (ii) ownership of fifty percent (50%) or more of the outstanding shares. SAP makes no representations about the suitability of this software for any purpose. advertising text and quality descriptions produced by SAP do not indicate any assurance of particular attributes. "control" means (i) the power. For information on Third Party software delivered with Adobe document services and Adobe LiveCycle Designer. due to the circumstances known to it at that point in time representing a typical transfer of the software. SAP shall only be liable for damage. if this (i) can be compensated under the Product Liability Act or (ii) if caused due to gross negligence or intent by SAP or (iii) if based on the failure of a guaranteed attribute. including but not limited to software source code. Acrobat. and configuration files.000. reproduction. ■ "Legal Entity" shall mean the union of the acting entity and all other entities that control. without material defects or suitable for a specific application under third-party rights. Irrespective of the legal reasons. including unauthorized operation. 4. 2010-01-25 PUBLIC 141/144 . and Reader are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and / or other countries. SAP and the Customer agree that the typical foreseeable extent of damage shall under no circumstances exceed EUR 5. 4. 4 if this loss could have been avoided by observing this obligation. are controlled by. Only valid for: SAP ERP. Limited Liability 1.3. the Adobe logo. Software maintenance of the STLport therefore shall be not included. distribute and sell this software and its documentation for any purposes is hereby granted without fee.SAP CRM | 4. in particular by making backup copies at the minimum intervals recommended by SAP. ■ "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. 3. SAP shall not be liable for indirect damage. The exclusion or the limitation of claims in accordance with the present Art. SAP cannot guarantee that the STLport is error-free. Version 2. Exclusion of warranty As the STLport is transferred to the Customer on a loan basis and free of charge. PostScript. documentation source. 3. If SAP is liable for gross negligence or intent caused by employees who are neither agents or managerial employees of SAP. direct or indirect. 2. In the case of Art. 4. ■ "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.0 1. 5. ■ "Source" form shall mean the preferred form for making modifications.

use.2. source code control systems. where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. verbal. excluding those notices that do not pertain to any part of the Derivative Works. and issue tracking systems that are managed by. within the Source form or documentation. if and wherever such third-party notices normally appear. ■ "Derivative Works" shall mean any work. that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. ■ "Contribution" shall mean any work of authorship. patent. publicly display. or on behalf of. no-charge. as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement. Redistribution You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium. no-charge. trademark. in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works. irrevocable copyright license to reproduce. provided that such additional attribution notices cannot be construed as modifying the License. Grant of Patent License Subject to the terms and conditions of this License. worldwide. non-exclusive. and attribution notices from the Source form of the Work." ■ "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. For the purposes of this definition. Derivative Works shall not include works that remain separable from. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form. royalty-free. but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution. import. and 4. and 3. whether in Source or Object form. all copyright. The contents of the NOTICE file are for informational purposes only and do not modify the License. each Contributor hereby grants to You a perpetual. including but not limited to compiled object code. "submitted" means any form of electronic. each Contributor hereby grants to You a perpetual. or distribution of Your modifications. offer to sell. elaborations. and in Source or Object form. You may add Your own attribution notices within Derivative Works that You distribute. have made. then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file. For the purposes of this License. made available under the License. including but not limited to communication on electronic mailing lists. 3. an original work of authorship. including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof. provided that You meet the following conditions: 1. ■ "Work" shall mean the work of authorship. annotations. in the Source form of any Derivative Works that You distribute. that is based on (or derived from) the Work and for which the editorial revisions. if provided along with the Derivative Works. You must give any other recipients of the Work or Derivative Works a copy of this License. sublicense. and otherwise transfer the Work. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use. If the Work includes a "NOTICE" text file as part of its distribution. generated documentation. You must retain. prepare Derivative Works of. publicly perform. within a display generated by the Derivative Works. and conversions to other media types. 4. the Work and Derivative Works thereof. as a whole. sell. You must cause any modified files to carry prominent notices stating that You changed the files. non-exclusive. with or without modifications. or written communication sent to the Licensor or its representatives. and 2. or. or merely link (or bind by name) to the interfaces of. alongside or as an addendum to the NOTICE text from the Work. the Licensor for the purpose of discussing and improving the Work. reproduction. excluding those notices that do not pertain to any part of the Derivative Works. then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. whether in Source or Object form. worldwide. or for any such Derivative Works ■ 142/144 PUBLIC 2010-01-25 . and distribute the Work and such Derivative Works in Source or Object form. or other modifications represent. irrevocable (except as stated in this section) patent license to make. royalty-free. Grant of Copyright License Subject to the terms and conditions of this License.

6. shall any Contributor be liable to You for damages. or other liability obligations and/or rights consistent with this License. or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill. incidental. as a whole. reproduction. End of: SAP ERP. contract. without any additional terms or conditions. even if such Contributor has been advised of the possibility of such damages. any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License. any warranties or conditions of TITLE. However. Notwithstanding the above. service marks. or claims asserted against. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 7. Trademarks This License does not grant permission to use the trade names. work stoppage. and only if You agree to indemnify. acceptance of support. including. trademarks. warranty. Submission of Contributions Unless You explicitly state otherwise. and hold each Contributor harmless for any liability incurred by. except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. such Contributor by reason of your accepting any such warranty or additional liability. in accepting such obligations. and distribution of the Work otherwise complies with the conditions stated in this License. whether in tort (including negligence). provided Your use. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND.SAP CRM | Documentation in the SAP Service Marketplace You can find this document at the following address: https://service. Disclaimer of Warranty Unless required by applicable law or agreed to in writing. nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. or FITNESS FOR A PARTICULAR PURPOSE. You may choose to offer. Limitation of Liability In no event and under no legal theory.5. indirect. not on behalf of any other Contributor. or any and all other commercial damages or losses). 8.sap. and charge a fee for. including any direct. Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS. NON-INFRINGEMENT. special. indemnity.com/instguides 2010-01-25 PUBLIC 143/144 . defend. MERCHANTABILITY. either express or implied. 9. or product names of the Licensor. without limitation. You may act only on Your own behalf and on Your sole responsibility. computer failure or malfunction. unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing. Accepting Warranty or Additional Liability While redistributing the Work or Derivative Works thereof. or otherwise.

All rights reserved. The information contained herein may be changed without prior notice.com © Copyright 2010 SAP AG.sap. . No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www.

Sign up to vote on this title
UsefulNot useful