Netweaver 7.0 SR3 abap java system copy guide

System Copy GuideSystem Copy for SAP Systems Based on SAP NetWeaver 7.0SR3 ABAP+Java

Target Audience

n System administratorsn Technology consultants

PUBLICDocument version: 1.2 ‒ 03/12/2009

Document History

Caution

Before you start the implementation, make sure you have the latest version of this document. Youcan 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.2 3/12/2009 Update in chapter “Constraints” and “Preparation for Table Splitting”

1.1 1/9/2009 DI-, EPC-, and EP-specific information updated

2/168 PUBLIC 03/12/2009

http://service.sap.com/instguides



Table of Contents

Chapter 1 Homogeneous and Heterogeneous System Copy for SAP Systems Basedon SAP NetWeaver 7.0 SR3 . . . . . . . . . . . . . . . . . . 7

1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 71.2 Online Information from SAP . . . . . . . . . . . . . . . . . . 81.3 System Architecture . . . . . . . . . . . . . . . . . . . . . 81.4 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . 91.5 Constraints . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 3 Preparations . . . . . . . . . . . . . . . . . . . . . . . . 213.1 General Technical Preparations . . . . . . . . . . . . . . . . . 213.2 Installing the Java Development Kit . . . . . . . . . . . . . . . . 24

Chapter 4 Database Independent System Copy . . . . . . . . . . . . . . 274.1 System Copy Procedure . . . . . . . . . . . . . . . . . . . . 284.2 Generating DDL Statements . . . . . . . . . . . . . . . . . . 314.3 Preparation for Table Splitting . . . . . . . . . . . . . . . . . . 324.4 Preparing the Export . . . . . . . . . . . . . . . . . . . . . 364.5 Exporting the Source System Using SAPinst . . . . . . . . . . . . . 374.5.1 Running SAPinst on UNIX or Windows to Perform the Export . . . . . . 374.5.2 Running SAPinst on System i to Perform the Export . . . . . . . . . 444.5.2.1 Preparing the Windows Host for the SAP System Installation . . . . . . 444.5.2.2 Preparing a Windows User Account and System i User Profile . . . . . . 454.5.2.3 Installing TMKSVR and Creating an Installation Share . . . . . . . . 474.5.2.4 Starting SAPinst on System i . . . . . . . . . . . . . . . . . . 504.5.3 Restarting R3load Processes . . . . . . . . . . . . . . . . . . 544.6 Setting Up the Target System . . . . . . . . . . . . . . . . . . 564.6.1 Transferring the Export Files to the Target Host . . . . . . . . . . . 574.6.2 Installing the Target System . . . . . . . . . . . . . . . . . . 58

Chapter 5 Database-Specific System Copy . . . . . . . . . . . . . . . . 615.1 Oracle-Specific Procedure . . . . . . . . . . . . . . . . . . . 635.1.1 Generating the Control File Structure . . . . . . . . . . . . . . . 655.1.2 Creating a Backup . . . . . . . . . . . . . . . . . . . . . . 69

03/12/2009 PUBLIC 3/168

5.1.2.1 Creating an Offline Backup Manually . . . . . . . . . . . . . . . 695.1.2.2 Creating an Offline or Online Backup with BR*Tools . . . . . . . . . 705.1.3 Preparing the Target System . . . . . . . . . . . . . . . . . . 705.1.4 Restoring the Database Files on the Target SystemManually . . . . . . 735.1.5 Restoring the Database Files on the Target System with BR*Tools . . . . . 745.2 SAP MaxDB-Specific Procedure . . . . . . . . . . . . . . . . . 765.3 MS SQL Server-Specific Procedure . . . . . . . . . . . . . . . . 785.4 IBM DB2 for Linux, UNIX, and Windows Specific Procedures . . . . . . 795.5 IBM DB2 for i5/OS Procedure . . . . . . . . . . . . . . . . . . 825.6 IBM DB2 for z/OS Specific Procedure . . . . . . . . . . . . . . . 825.6.1 Step 1: Check Consistency . . . . . . . . . . . . . . . . . . . 845.6.2 Step 2: Stop and Restart the Source System . . . . . . . . . . . . . 855.6.3 Step 3: Run SQL Statements in the Source System . . . . . . . . . . 855.6.3.1 SQL Statement Number 01 . . . . . . . . . . . . . . . . . . . 855.6.3.2 SQL Statement Number 02 . . . . . . . . . . . . . . . . . . . 865.6.3.3 SQL Statement Number 03 . . . . . . . . . . . . . . . . . . . 865.6.3.4 SQL Statement Number 04 . . . . . . . . . . . . . . . . . . . 875.6.3.5 SQL Statement Number 05 . . . . . . . . . . . . . . . . . . . 885.6.3.6 SQL Statement Number 06 . . . . . . . . . . . . . . . . . . . 895.6.3.7 SQL Statement Number 07 . . . . . . . . . . . . . . . . . . . 905.6.3.8 SQL Statement Number 08 . . . . . . . . . . . . . . . . . . . 915.6.3.9 SQL Statement Number 09 . . . . . . . . . . . . . . . . . . . 925.6.4 Step 4: Capturing View Definitions with DB2 V9 (if the Schema Name is to be

Changed) . . . . . . . . . . . . . . . . . . . . . . . . . 935.6.5 Step 5: Stop the Source System . . . . . . . . . . . . . . . . . 935.6.6 Step 6: Making Copies of Source Data Sets . . . . . . . . . . . . . 935.6.7 Step 7: Creating the Target System . . . . . . . . . . . . . . . . 945.6.8 Step 8: Printing the Bootstrap Data Sets . . . . . . . . . . . . . . 945.6.9 Step 9a: Changing the Bootstrap Data Sets (BSDS) . . . . . . . . . . 955.6.10 Step 9b: Start the Target System . . . . . . . . . . . . . . . . . 965.6.11 Step 9c: Creating a New STOGROUP Using the HLQ of the Target System . . 975.6.12 Step 9d: Stopping Index Spaces . . . . . . . . . . . . . . . . . 975.6.13 Step 9e: Changing the User-Defined Indexes in the DB2 Catalog . . . . . 975.6.14 Step 9f: Restart the Index Spaces . . . . . . . . . . . . . . . . . 975.6.15 Step 9g: Creating the Temporary Files for the DB2 Target System . . . . . 985.6.16 Step 9h: Implementing HLQ of the Target System in the Work File Database . 985.6.17 Step 9i: Adjusting the DDF Location Name and Port Number . . . . . . 985.6.18 Step 10 (DB2 V8 and Lower): Changing the VCAT of the Target System . . . 995.6.19 Step 10 (DB2 V9): Changing the VCAT of the Target System . . . . . . . 1005.6.20 Step 11 (DB2 V9): Changing the Schema of the Target System . . . . . . 1005.6.21 Step 12: Adapting WLM Application Environments for DB2 Stored Procedures 102

4/168 PUBLIC 03/12/2009

Chapter 6 Follow-Up Activities . . . . . . . . . . . . . . . . . . . . 1036.1 Performing Follow-Up Activities in the Source System . . . . . . . . . 1036.2 Performing Follow-Up Activities in the Target System . . . . . . . . . 1036.2.1 Installing the License Key . . . . . . . . . . . . . . . . . . . 1036.2.2 Performing Follow-Up Activities for ABAP . . . . . . . . . . . . . 1046.2.3 Performing Follow-Up Activities for Java . . . . . . . . . . . . . . 1086.2.3.1 General Follow-Up Activities . . . . . . . . . . . . . . . . . . 1086.2.3.1.1 Configuration Steps for the SAP Java Connector . . . . . . . . . . . 1086.2.3.1.2 Generating Public-Key Certificates . . . . . . . . . . . . . . . . 1096.2.3.2 Usage Type or Software Unit-Specific Follow-Up Activities . . . . . . . 1096.2.3.2.1 Application Server Java (AS-Java) . . . . . . . . . . . . . . . . . 1096.2.3.2.1.1 AS Java: SAP Knowledge Warehouse . . . . . . . . . . . . . . . 1096.2.3.2.2 EP Core (EPC) . . . . . . . . . . . . . . . . . . . . . . . 1106.2.3.2.2.1 EPC: Portal . . . . . . . . . . . . . . . . . . . . . . . . . 1106.2.3.2.3 Enterprise Portal (EP) . . . . . . . . . . . . . . . . . . . . . 1106.2.3.2.3.1 EP: Knowledge Management and Collaboration . . . . . . . . . . . 1106.2.3.2.4 Business Intelligence Java Components (BI Java) . . . . . . . . . . . 1146.2.3.2.4.1 Business Intelligence (BI Java) . . . . . . . . . . . . . . . . . . 1146.2.3.2.4.2 Basic Configuration for Usage Type BI Java . . . . . . . . . . . . . 1156.2.3.2.5 Process Integration (PI) . . . . . . . . . . . . . . . . . . . . 1156.2.3.2.5.1 PI: System Landscape Directory . . . . . . . . . . . . . . . . . 1166.2.3.2.5.2 PI: Integration Server . . . . . . . . . . . . . . . . . . . . . 1176.2.3.2.5.3 PI: Changes in the Exchange Profile . . . . . . . . . . . . . . . . 1176.2.3.2.5.4 PI: Refresh Caches . . . . . . . . . . . . . . . . . . . . . . 1196.2.3.2.5.5 PI: Switching Addresses . . . . . . . . . . . . . . . . . . . . 1206.2.3.2.5.6 PI: Connection Checks . . . . . . . . . . . . . . . . . . . . 1226.2.3.2.6 Development Infrastructure (DI) . . . . . . . . . . . . . . . . 1226.2.3.2.7 Self Services (XSS) . . . . . . . . . . . . . . . . . . . . . . 1256.2.3.2.7.1 Re-Creating the JCo Destinations . . . . . . . . . . . . . . . . 1256.2.3.2.7.2 ERP-XSS: SAP WebDynpro Applications . . . . . . . . . . . . . . 1256.2.3.2.8 CRM Java Components (JCRM) / Extended E-Selling Components (XECO) . 1266.2.3.2.8.1 Sub-Component Workforce Deployment AS/CS . . . . . . . . . . . 1266.2.3.2.9 MapBox . . . . . . . . . . . . . . . . . . . . . . . . . . 1276.2.3.2.10 SRM Live Auction Cockpit (SRMLAC) . . . . . . . . . . . . . . . 1276.2.3.2.10.1 SRM Live Auction Cockpit (SRMLAC) . . . . . . . . . . . . . . . 1276.2.3.2.10.2 Configuring Single Sign-On . . . . . . . . . . . . . . . . . . 1286.2.3.2.11 SCM Forecasting & Replenishment Processor (SCM FRP) . . . . . . . . 1316.2.4 Performing Jobhead Correction after Homogeneous System Copy . . . . 131

Chapter 7 Additional Information . . . . . . . . . . . . . . . . . . . 1337.1 R3load Procedures Using the Migration Monitor . . . . . . . . . . . 133

03/12/2009 PUBLIC 5/168

7.1.1 Configuration . . . . . . . . . . . . . . . . . . . . . . . 1337.1.2 Assigning DDL Files to Packages . . . . . . . . . . . . . . . . . 1417.1.3 Defining Groups of Packages . . . . . . . . . . . . . . . . . . 1427.1.4 Processing Split Tables . . . . . . . . . . . . . . . . . . . . 1427.1.5 Starting the Migration Monitor . . . . . . . . . . . . . . . . . 1447.1.6 Output Files . . . . . . . . . . . . . . . . . . . . . . . . 1497.1.7 Installing the Target System Using the Migration Monitor . . . . . . . 1497.2 Using SAPinst GUI . . . . . . . . . . . . . . . . . . . . . . 1517.3 Interrupted Installation with SAPinst . . . . . . . . . . . . . . . 1517.4 Performing a Remote Export Using SAPinst . . . . . . . . . . . . . 1547.4.1 Performing a Remote Installation with SAPinst (Optional) . . . . . . . 1557.4.2 Starting SAPinst GUI Separately (Optional) . . . . . . . . . . . . . 156

6/168 PUBLIC 03/12/2009

1Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver7.0 SR3

1 Homogeneous and HeterogeneousSystem Copy for SAP Systems Based onSAP NetWeaver 7.0 SR3

As of SAP NetWeaver 7.0, you can copy ABAP systems, ABAP+Java systems and Java systems in one runusing either database-specific methods or database-independent methods.

1.1 Terminology

n Homogeneous System CopyDuring the system copy you use the same operating system and database platform as the originalsystem.

n Heterogeneous System CopyDuring the system copy, you change either the operating system or the database system, or both.Heterogeneous system copy is a synonym for migration.

n Source System and Target SystemThe SAP system containing the original database is called the source system and the system towhich the database copy is to be imported is called the target system. Their SAP system names areabbreviated to SOURCE_SAPSID and TARGET_SAPSID (System i: source_<SID> and target_<SID>).The terms source database and target database are also used in this description.

n System CopyDuplication of an SAP system. Certain SAP parameters might change in a copy. When youperform a system copy, SAPinst installs all the instances again, but it uses a copy of the sourcesystem database to set up the database.

n Database CopyDatabase-dependent part of the system copy.

n PlaceholdersPlaceholders such as <SAPSID> are used in commands. They are used in the same way as in the SAPsystem installation documentation. You must replace them with the values valid for your site.The following additional placeholders are used:

Placeholder Meaning How to find out

<SAPSID> SAP system ID

<S_HOST> System name of the source host Command hostname

03/12/2009 PUBLIC 7/168


1.2 Online Information from SAP

Placeholder Meaning How to find out

<T_HOST> System name of the target host Command hostname

<S_SAPSID> SAP system ID of the source system <SAPSID> of the original system

<T_SAPSID> SAP system ID of the target system <SAPSID> of the target system

<S_DBSID> Database ID of the source system <DBSID> of the original system

<T_DBSID> Database ID of the target system <DBSID> of the target system

1.2 Online Information from SAP

More information about system copy is online available as follows:

n SAP System Copy & Migration page at http://sdn.sap.com/irj/sdn/systemcopy.n SAP OS/DB Migration page at http://service.sap.com/osdbmigration.

Additionally to the information contained on this page, check the SAP OS/DBMigration Planning Guidethat is available in the Media Library.

n SAP Note 82478

Caution

Only perform a system copy if you have experience in copying systems and good knowledge ofthe operating system, the database, the ABAP Dictionary, and the Java Dictionary. Only perform aheterogeneous system copy if you are a certified system support consultant or a certified SAPTechnical Consultant.

Note

If you encounter problems during the system copy, create a customer message using theapplication area BC-INS-MIG.

1.3 System Architecture

The Java system persists data in both the database and the file system, for example the SoftwareDelivery Manager (SDM) is persisted in the file system. Each server instance has a unique ID and isstored in the database.

8/168 PUBLIC 03/12/2009

http://sdn.sap.com/irj/sdn/systemcopy

http://service.sap.com/osdbmigration

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=82478&_NLANG=en&_NVERS=0


1.4 Restrictions

1.4 Restrictions

Note

See SAP Note 1120872 for Java components based on SAP NetWeaver 7.0 SR3 that have been releasedalready for system copy.

The target system installation consists of both the target database and target instances/applicationservers installations. For the scenarios below, the following holds:

n

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 systemsthat are not based on SAP NetWeaver 7.0 SR3.End of: IBM DB2 for Linux and UNIX and Windows

n Refresh of the database is not supported. A refresh of the database means that only the databaseis loaded with the content of a database of a different system. As in this scenario no migrationcontroller is invoked, this is not supported.

n Copying the database only is not supported.n Copying the central instance only is not supported. The migration controller deletes all dialog

instances in the database, so the system is not complete any longer.n Reinstalling the central instance without the database is not supported. The migration controller

deletes all dialog instances in the database, so the system is not complete any longer.

1.5 Constraints

n As of SAP NetWeaver 7.0, when your system is a double-stack system and you perform a systemcopy, your source system is copied to the target system as a whole. This means, it is neither possibleto exclude a single stack from the system copy nor to copy a separate stack only.

n SAP does not support client transport as a system copy method. Transporting productionclients is not supported at all. You can use client transport for the initial setup of an SAP systeminfrastructure. This documentation does not cover the client copy procedure.

n This documentation does not describe how to export and import a database with the installationtools for reorganization purposes. Use the appropriate tools for database reorganization, as SAPdoes not support this installation option.

n If you have made modifications in your development system and want to copy your qualityassurance or production system onto the development system, see SAP Note 130906.

n This documentation describes how to copy data from one SAP system to another SAP systembased on SAP NetWeaver Application Server. This documentation does not describe how to copydata from non-SAP systems to SAP systems.

n If you want to convert a non-Unicode system to a Unicode system or perform the system copy of aUnicode system, see SAP Note 551344.

03/12/2009 PUBLIC 9/168





1.5 Constraints

n For the development of Java applications, we strongly recommend that you follow the rulesmentioned below. Otherwise, we cannot guarantee that you can copy your Java engine later withthe SAP tools to change your underlying operating system and/or database system.

n SAP does not generally support all Data Archiving operations after a system copy.If you used Data Archiving in the source or in the target system, access to the created archive file(s)from the target system may not always be possible. For more information, see SAP Note 153433and System Landscape Optimization at http://service.sap.com/slo.Access to archived files from the target system without a dedicated archive migration project isonly supported in the following cases:l Your system copy clones a source system for nonproductive purposes, only read-access to the

previously archived data is intended from the target system (no reloading), and you do notstore archive files using ArchiveLink/CMS.You can either copy all archive files to file systems that are not shared between the source andthe target system, or you arrange network access for appropriate archive file sharing.

l The system copy is done to replace a productive system by a new productive system (forexample, hardware migration), assuming that the target system did not exist before and thesource system’s operation is discontinued after the system copy.Youmust not change the system ID during system copy, but arrange for file access and/orArchiveLink/CMS connectivity.

In all other cases, contact SAP SLO at http://service.sap.com/slo or [email protected] When you perform a system copy, all software units or usage types in the source system are copied

to the target system. This means that none of the usage types in the target system can be excludedfrom the system copy, nor can you select usage types.

n Dos and Don’ts for system copy:l Do:uSave configuration data and runtime data in the Java database only. If you absolutely need

to save this data to the file system level, you must use the Software Deployment Manager(SDM) to save the data.

uFollow the Open SQL standard.

uMake sure that all communication runs through the database pool.l Don’t:uSave any system and infrastructure-specific data in business objects. Use a pointer to the

central storage of such information, for example:

t SAP SystemID and SID (SAPSID =SID=system name)

t Host name

t IP addresses

t Services and Ports

t Logical destinations and logical system names

t Other technical infrastructure names

uUse file system persistency.

10/168 PUBLIC 03/12/2009


http://service.sap.com/slo

http://service.sap.com/slo


1.5 Constraints

uSet up dependencies between Java and ABAP.

uTry to copy the Java part of an ABAP+Java system to a Java standalone system or vice versa.n If you have implemented a federated portal network (FPN) across multiple SAP NetWeaver

systems, refer to SAP Note 1080080 before commencing with the system copy.

03/12/2009 PUBLIC 11/168


This page is intentionally left blank.

2 Planning

2 Planning

This section describes how to plan your system copy.You can apply the system copy for:

n Setting up system landscapes (where the SAP systems have different SAPSIDs).n Creating systems for testing, demonstration, training, and standby. Depending on the purpose of

the system, it might be advisable to use the same SAP system ID, even though this prevents youfrom including the system in a system group for transports.

Only valid for: Oracle

Note

You cannot create standby systems with a system copy.

End of: Oracle

Note

You should perform upgrades in a test system first. This way you can identify customer-specificproblems that might result from modifications.

When copying a system that contains production data it is important to choose the right moment forthe copy. This could be a month-end or year-end closing.

Caution

Do not use NFS-mounted file systems because writing to NFS-mounted file systems might causecorrupted dumps.

Required Documentation

n Read the following SAP Note for up-to-date information:SAP Note 1120872 (Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7.0SR3)

n The documentation System Copy for SAP Systems Based on SAP NetWeaver 7.0 SR3 only describes theexport of the source system in detail.

n For the installation of the target system, you also need the installation guide for your SAPapplication:

03/12/2009 PUBLIC 13/168


2 Planning

SAP NetWeaver 7.0: Installation Guide ‒ SAP NetWeaver 7.0 SR3 ABAP+Java on <OS> : <DB> athttp://service.sap.com/installnw70 Installation ‒ SAP NetWeaver Systems .

SAP ERP 6.0: Installation Guide ‒ SAP ERP 6.0 SR3 ABAP+Java on <OS> : <DB> athttp://service.sap.com/erp-inst SAP ERP 6.0 Installation .

SAP CRM 5.0: Installation Guide ‒ SAP CRM 5.0 SR3 ABAP+Java on <OS> : <DB> athttp://service.sap.com/crm-inst SAP CRM 2005 CRM Core and Standalone Components .

SAP SRM 5.0: Installation Guide ‒ SAP SRM 5.0 SR3 ABAP+Java on <OS> : <DB> athttp://service.sap.com/srm-inst Using SAP SRM Server 5.0 .

SAP SCM 5.0: Installation Guide ‒ SAP SCM 5.0 SR3 ABAP+Java on <OS> : <DB> athttp://service.sap.com/instguides SAP Business Suite Applications SAP SCM SAP SCM

Server Using SAP SCM 5.0 Server .

Required DVDs, Tools, and Other Software

Make sure that all required DVDs for the system copy are available:

n Required DVDsl Installation Master DVD

l Java DVD

Note

The DVD names are abbreviated.You can find the full names of all media shipped with SAP NetWeaver 7.0 inMedia Information for SAPNetWeaver 7.0 at http://service.sap.com/installNW70.

n Order the right version of the installation kit before starting the system copy.Make sure that the versions of the SAP system and the installation tools are the same on the targetand source systems. Exceptions are only allowed if they are described in an SAP Note.

Note

You can operate several SAP systems on a single host without encountering any problems.Nevertheless, we recommend that you use a separate host for each system because an SAPsystem upgrade might depend on an OS upgrade. If the SAP systems are on separate hosts, youcan upgrade them at different times.

Caution

The source system must be in a consistent state before you can copy it.

n Check that you have the appropriate tool versions for your SAP kernel.n For a heterogeneous system copy you need to get a migration key by generating it at

http://service.sap.com/migrationkey.

14/168 PUBLIC 03/12/2009

http://service.sap.com/installnw70

http://service.sap.com/erp-inst

http://service.sap.com/crm-inst

http://service.sap.com/srm-inst


http://service.sap.com/installNW70

http://service.sap.com/migrationkey

2 Planning

Creating A System Copy Plan

Create a plan to perform the system copy.

1. Consider the downtime of the source system (for preparations and copying) when planningthe system copy.

2. Perform a test run of the system copy. You can use the time taken by the test run to calculatethe system downtime:n If your target system will replace your source system, try to perform a complete test run. This

means that the entire database is exported from the source system, transferred to the targetsystem and imported there. System downtime is approximately equal to the total test time(that is, time for export, transport, and import).

n If you do not want to replace your source system, a partial test run (export of the entiredatabase or parts of it) can be sufficient to calculate the system downtime. The source system isonly down for the time of the export.Calculating the system downtime is particularly important for very large databases (VLDB)or when tapes are being used. The test run is also to determine the amount of export data.Choose the best data transfer method (for example, FTP or tape). We recommend that youperform read/write actions only on local file systems.

3. Define a schedule for the test migration and the final migration.

Miscellaneous

n In the event of amajor change in hardware configuration (for example, newmachine type, newhard disk configuration, new file system type), consult your SAP-authorized hardware partner.

n Decide which system copy procedure you want to use:l The database-independent procedure using SAP tools.

Use this method if database-specific methods are either not available or not suitable. For moreinformation, see, Database-Independent System Copy [page 27].

Note

For a heterogeneous system copy, only the database-independent method is available.

l The database-specific procedure using tools provided by the database vendorSome database vendors offer specific tools for copying a database. These tools let you:

uRestore a backup of one database (source database) in another one (target database) (backupmethod)

uUnload the source database and load the data into the target databaseFor more information, see Database-Specific System Copy [page 61].

n

Only valid for: Development Infrastructure (DI)

Software Unit Development Infrastructure (DI) only:For the migration of Java Development Infrastructure (JDI) components you can apply either"Copy" or "Move".

03/12/2009 PUBLIC 15/168

2 Planning

l Copy"Copy" is supported only by Design Time Repository (DTR). After a copy, both the source DTRand target DTR can be used productively in parallel. However, Component Build Service (CBS)and Change Management Service (CMS) do not support such a copy.

l Move"Move" is supported by all JDI components ‒ DTR, CBS and CMS. After a move, the sourcesystem can no longer be used ‒ that is, only the target is active after the move has beenperformed.

End of: Development Infrastructure (DI)

n Choosing an SAP system IDYou can choose the new SAP system ID <TARGET_SAPSID> freely during a new installation.

Caution

To meet the requirements of the Workbench Organizer, you must choose different SAP systemIDs for different SAP systems.

n SAP licenseOnce the installation is completed and the SAP system copy has been imported, you willrequire a new license key for the target system. The license key of the source system is notvalid for this system. For more information about ordering and installing the SAP license, seehttp://help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP

NetWeaver by Key Capability Solution Life Cycle Management SAP Licenses .For more information about SAP license keys, see http://service.sap.com/licensekey.

n Archiving filesData that has been archived in the source system (data that does not reside in the database but wasmoved to a different storage location using SAP Archive Management) must be made accessible inthe target system. Adapt the file residence information in the target system. Formore information,see http://help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAPNetWeaver by Key Capability Solution Life Cycle Management Data Archiving .Access to archive files is platform-independent.

n Configuration analysis and hardware analysisYou need to determine the:l Number of application serversl Expected size of the databasel Additional disks or other hardware requiredl Required memory

Note

See the section on hardware and software requirements in the SAP system installationdocumentation to determine the system requirements.

16/168 PUBLIC 03/12/2009

http://help.sap.com/nw70

http://service.sap.com/licensekey


2 Planning

n These methods are not supported for all database systems. See the following table to check whichcopy methods are available for your database system:

Database OS Platform Available Methods

SAP MaxDB UNIX Use one of the following:l System copy procedure on UNIX using R3load for the ABAP

part and Jload for the Java partFor more information, see System Copy Procedure [page 28].

l System copy procedure for a homogeneous system copyonlyFor more information, see SAP MaxDB-specific procedure [page76].

SAP MaxDB Windows Use one of the following:l System copy procedure on Windows using R3load for the

ABAP part and Jload for the Java partFor more information, see System Copy Procedure [page 28].

l System copy procedure for a homogeneous system copyonlyFor more information, see SAP MaxDB-specific procedure [page76].

IBM DB2 fori5/OS

IBM System i Use one of the following:l System copy procedure on System i using R3load for the

ABAP part and Jload for the Java partFor more information, see Starting SAPinst on System i [page 50].

l System i-specific procedure for a homogeneous systemcopy onlyFor more information, see IBM DB2 for I5/OS Procedure [page82].

For more information, see SAP Note 585277.

IBM DB2 forLinux, UNIX,and Windows

UNIX or Windows Use one of the following:

lOnly valid for: UNIX

System copy procedure on UNIX using R3load for the ABAPpart and Jload for the Java partFor more information, see System Copy Procedure [page 28].End of: UNIX

lOnly valid for: Windows

System copy procedure on Windows using R3load for theABAP part and Jload for the Java partFor more information, see System Copy Procedure [page 28].End of: Windows

l The backup method of IBM DB2 for Linux, UNIX, andWindows is supported for SAP systems based on SAPNetWeaver 7.0 SR3.For more information, see IBM DB2 for Linux, UNIX, andWindows Specific Procedures [page 79].

03/12/2009 PUBLIC 17/168


2 Planning


IBM DB2 for z/OS IBM System z Use one of the following:





l Additional Information:u For more information about the IBM DB2 for z/OS

specific procedure for a homogeneous system copyonly, see IBM DB2 for z/OS Specific Procedure [page 82].

uWhen R3ta is used to split tables, DELETE with WHEREis not performed if import errors occur in the targetsystem.For more information, see SAP Note 778729.

Oracle UNIX Use one of the following:



l Oracle-specific procedure for a homogeneous system copyonlyFor more information, see Oracle-Specific Procedure [page 63].

Oracle Windows Use one of the following:



l Homogeneous system copy only: Oracle backup/restoremethodFor more information, see Oracle-Specific Procedure [page 63]and SAP Note 676468.

MS SQL Server Windows Use one of the following:



l Homogeneous system copy only: Backup/Restore orDetach/Attach Method

18/168 PUBLIC 03/12/2009



2 Planning


For more information, seeMS SQL Server-Specific Procedure[page 78] and SAP Notes 193816 and 151603.

03/12/2009 PUBLIC 19/168




3 Preparations

3 Preparations

Before you start the system copy, you must perform the following preparation steps:

3.1 General Technical Preparations

To make a consistent copy of the database, you need to prepare the source system and perform somesubsequent actions on the target system. This is not necessary when performing a test run.The following describes important preparations. For more information about SAP systemadministration, see the SAP Online Documentation.

n Before you start a system copy, check the minimum kernel patch level required by the supportpackage level of the source system. It might be necessary to replace the SAP kernel delivered withthe kernel DVD of the installation kit and installed during the installation of the target system by anewer kernel patch level before starting the target system. If you have to replace the delivered SAPkernel, you can do this after the installation of the central instance.

n Before you start the export on your source system, check that your JAVA_HOME environmentpoints to a valid JDK version.

n No canceled or pending update requests should be in the system. Check this by choosing ToolsAdministration Monitor Update (transaction SM13).If canceled or pending updates exist, you must update these again or delete them from all clients.You can see whether canceled or pending updates exist by checking if table VBDATA containsany entries.Find the canceled or open updates as follows:1. Call transaction SM13.2. Delete the default values for the client, user, and time.3. Choose all update requests.

If canceled or pending records exist, you must update these again or delete them. Checkwhether this action was successful using transaction SE16 for table VBDATA.

n Set all released jobs from Released to Scheduled:Tools CCMS Background Processing Jobs - Overview and Administration (transaction SM37)

You also need to do this for jobs that must run periodically (see SAP Note 16083). Select all jobs(include start after event) as follows:Job Released Scheduled

n Adapt the operation mode timetable to make sure that no switching of operating modes takesplace while a system is being copied as follows:

03/12/2009 PUBLIC 21/168


3 Preparations3.1 General Technical Preparations

Tools CCMS Configuration Operation mode calendar (transaction SM63)n Write down the logical system names of all clients:

1. If you plan to overwrite an existing system with a system copy (for example, the source andtarget systems will both exist after the system copy), make sure you write down the logicalsystem names of all clients in the system that will be overwritten (transaction SCC4).As the logical system names will be overwritten, in the event of differences, you must changethem back to their original names (as they existed in the system that is overwritten) in thefollow-on actions after the system copy.

2. If you create a new system with a system copy (that is, create an upgrade test system), makesure that the logical naming strategy for this new system is consistent with your existing logicalsystem naming convention. If you are still planning your BI (formerly BW) system landscape,see SAP Note 184447.

3. If your system copy is used to replace hardware for the DB server, migrate to a different databasesystem or operating system (that is, source system for the copy is the same as the copy target),no changes to logical system names are required.

n Before the export, delete QCM tables from your system as follows:1. Before deleting you must always checkl That the tables are consistent ‒ no restart log or conversion procedure termination must be

displayedl That the data of the original table can be readl If application programs that use the affected original table do not run correctly, do not

delete the QCM table yet.2. Call transaction SE14.3. Choose Extras Invalid temp. table

All QCM tables that can be deleted are displayed.4. Mark the tables and delete them.

n


Usage Type Development Infrastructure (DI) only:If your SAP system is of usage type Development Infrastructure (DI) then this system can only bemoved, but not be copied. This means that it is possible to migrate such a system from one host toanother but it is not possible to keep both systems active after the migration. If you want to movean SAP system with usage type Development Infrastructure (DI), make sure that the followingprerequisites are met:l The users and passwords created in the source system are valid in the target system (for

example, they use the same UME).l Check in (or revert) all open activities (of all users) in the SAP NetWeaver Developer Studio by

using the Design Time Repository perspective (DTR perspective).l Remove all existing development configurations from the SAP NetWeaver Development

Studio.

22/168 PUBLIC 03/12/2009


3 Preparations3.1 General Technical Preparations

l Verify in the DTRWeb UI that there are no pending entries in the NameReservation queue. Tocheck this, go to http://<dtrhost>:<port>/dtr/sysconfig/support/NameReservationList

and check that there are no entries with the state PRELIMINARY, FINALIZE_PENDING orREVERT_PENDING in the queue.If there are entries with the state FINALIZE_PENDING or REVERT_PENDING you have to wait forthe next run of the name reservation background task in the DTR server that ends theseentries. This background task runs normally every 15 minutes.To check the frequency of this background task you can have a look athttp://<dtrhost>:<port>/dtr/sysconfig/scheduled_tasks.html and check the valuePeriodicity for the task ProcessNameReservationsTask. As precondition for a successfulexecution of this background task, the name server must be configured in the DTR server(http://<dtrhost>:<port>/dtr/system-tools/administration/NameServerConfiguration.There should be no entries with the state PRELIMINARY in the name reservation queue sincethey only occur if there are open activities (which should not be the case if you followed theprevious steps).

l Stop all applications of the Development Infrastructure (DI) on the source system.End of: Development Infrastructure (DI)

n FI customers: You can perform an additional consistency check by running the job SAPF190 beforecopying the source system, as well as after copying the target system, and then compare theresults. Make sure that no customer data is changed in the meantime. You can do this as follows:Accounting Financial Accounting General ledger Periodic Processing Closing Check/count

Comparison

n FI customers: You can further check consistency by running the jobs RFUMSV00 (tax onsales/purchases), RAGITT01 (asset history sheet), RAZUGA01 (asset acquisitions), RAABGA01 (fixed assetretirements) before copying the source system, as well as after copying the target system, and thencompare the results. Make sure that no customer data is changed in the meantime.

n CO customers: You can perform an additional consistency check by running the report group1SIP before copying the source system, as well as after copying the target system, and thencompare the results. Make sure that no customer data is changed in the meantime.

Caution

Prerequisites for an export:Before performing an export, make sure that no incremental conversion is in progress.To test if an incremental conversion is in progress, run transaction ICNV. If there are any tableentries in table TICNV, an incremental conversion is in progress. In this case, you have thefollowing options:1. Defer the migration until the incremental conversion has finished.2. Try to finish the incremental conversion by performing the following steps:

03/12/2009 PUBLIC 23/168

3 Preparations3.2 Installing the Java Development Kit

l If the tables are in state For conversion or in state Done, delete the entries by choosingControl Delete Entry .

l If the tables are in any other state, you have to finish the incremental conversion. ChooseAssistant and proceed according to the online documentation.

Caution

Heterogeneous System Copy only:Before you start the export of your source system, make sure that the tables TATGPC and TATGPCA

are empty. To do so, use your database utility and delete the contents of these tables with thefollowing statements:DELETE from TATGPC

DELETE from TATGPCA

Normally both tables are empty. If you do not delete the contents of these tables you willencounter problems while importing the data to your target system because of non NULL capablefields in these tables.

n Prepare the system for SAPinst. For more information, see Installing the Java Development Kit [page 24].

3.2 Installing the Java Development Kit

You need to prepare the system for the J2EE Engine by installing the Java Development Kit (JDK).The JDK includes the Java Runtime Environment (JRE), which is required both for SAPinst andthe SAPinst GUI.

Only valid for: UNIX;Windows

Note

If required, you can perform a remote installation using a standalone SAPinst GUI on a separateWindows or UNIX host. This lets you perform the installation on a remote host, controlling it withthe SAPinst GUI from a local host.If you want to perform a remote installation, see Performing a Remote Installation with SAPinst [page 155]. Inthis case, you need at least a JRE on the local host to start the SAPinst GUI there.

End of: UNIX;Windows

24/168 PUBLIC 03/12/2009


Only valid for: IBM i5/OS

Note

Since System i has no graphical user interface, the SAPinst executable is running on the Windowsinstallation host. You need to install a valid JDK on Windows only for installation purposes. TheJ2EE Engine of the SAP System uses the IBM JDK as mentioned in the section Hardware and SoftwareRequirements.

End of: IBM i5/OS

Procedure

1. Check the JDK versions that are released for SAP systems in the Product Availability Matrix (PAM):a) Go to http://service.sap.com/pam.

b)

Only valid for: SAP NetWeaver

On the right-hand panel, choose SAP NetWeaver SAP NetWeaver 7.0 (2004S) .End of: SAP NetWeaver

c)

Only valid for: SAP Solution Manager

On the right-hand panel, choose SAP Technology Components SAP SOLUTION MANAGER<Current Release> .End of: SAP Solution Manager

d)

Only valid for: SAP CRM;SAP ERP;SAP SCM;SAP SRM

On the right-hand panel, choose SAP Application Components <your product> .End of: SAP CRM;SAP ERP;SAP SCM;SAP SRM

e) Choose tabstrip JSE Platforms.

Note

For more information about the recommended JDK version for your operating system andabout how to download it, see SAP Note 723909.

2. Make sure a valid JDK version is installed on every host on which you want to install an SAPinstance with the J2EE Engine, as follows:n If the JDK is not already installed, you need to download and install it.n 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.If SAPINST_JRE_HOME is not found, SAPinst also checks JAVA_HOME.

03/12/2009 PUBLIC 25/168

http://service.sap.com/pam



Only valid for: UNIX Linux

Note

If you use a Sun Java VM, you have to edit the conguration file$JAVA_HOME/jre/lib/security/java.security, replacing entrysecurerandom.source=file:/dev/random with securerandom.source=file:/dev/urandom.

End of: UNIX Linux

3. As of SAP NetWeaver 7.0 strong encryption is mandatory for the J2EE Engine and for all usage typesthat are deployed on it. You need to obtain the JCE policy files beforehand so that they can beinstalled by SAPinst:

a)

Only valid for: UNIX;Windows Solaris;HP-UX;Linux;Windows

Download the JCE policy files for your platform at http://java.sun.com/javase/downloads.End of: UNIX;Windows Solaris;HP-UX;Linux;Windows

b)

Only valid for: UNIX;IBM i5/OS AIX;Linux;IBM i5/OS;z/OS

Download the JCE policy files for your platform athttp://www6.software.ibm.com/dl/jcesdk/jcesdk-p.

Only valid for: z/OS

Note

You can also use this link for Linux for System z and Linux for AMD.

End of: z/OS

End of: UNIX;IBM i5/OS AIX;Linux;IBM i5/OS;z/OS

c) SAPinst installs the JCE policy files during the installation process.

d)

Only valid for: UNIX AIX

Copy the JCE policy files to directory /usr/java14_64/jre/lib/security.End of: UNIX AIX

e)

Only valid for: IBM i5/OS IBM i5/OS

Copy the JCE Policy files to directory \QIBM\ProdData\Java400\jdk14\lib\security.End of: IBM i5/OS IBM i5/OS

f)

Only valid for: UNIX z/OS

Copy the JCE Policy files to JAVA_HOME/lib/security.End of: UNIX z/OS

26/168 PUBLIC 03/12/2009

http://java.sun.com/javase/downloads

http://www6.software.ibm.com/dl/jcesdk/jcesdk-p

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, filesystem, and all configuration in a database-independent format. SAPinst uses both the R3loadtool and the Jload tool.R3load generates a database export of all SAP objects that are defined in the ABAP Dictionary andarchives the configuration and components in the file system.Jload generates a database export of all SAP objects that are defined in the Java Dictionary and archivesthe configuration and components in the file system.

Constraints

R3load and Jload Restrictions

n SAPinst generates a database dump of all SAP objects that are defined in the ABAP Dictionary(R3load) or Java Dictionary (Jload). Other objects are not exported by SAPinst.

n For a consistent database the SAP system must be shutdown (excluding the database!). Thedatabase must still be running.

n R3load only: Changes to database objects that cannot be maintained in the ABAP Dictionary(transaction SE14), such as the distribution of tables over several tablespaces or dbspaces, arelost after the system copy.

n R3load only: Indexes longer than 18 characters are not allowed on the database to be exported.

System Copy Tools

n Every installation service (dialog instance installation, for example) must have its own separateinstallation directory whenever you start SAPinst.

n If the target system already exists and if you do not plan to perform an MCOD installation,delete the database on the target system before the import according to the correspondingdescription in section Additional Information of the installation documentation for your SAPcomponent.If the database configuration of your database is stored in the file system, we recommend you toback up these configuration files before deleting the database.

Splitting STR Files

n During the standard system copy process, all tables of the SAP system are grouped into packages,whereby all tables with the same data class belong to the same package. The processing unit forone unload/load process is a package. The packages usually differ in number and size of contained

03/12/2009 PUBLIC 27/168

4 Database Independent System Copy4.1 System Copy Procedure

tables, resulting in varying unload/load runtimes. The overall runtime can be reduced by creatingpackages of the same size, that is, creating packages with a similar processing time. You can achievethis by splitting the default packages (one package per data class) into more and smaller pieces.

n There are several options of how to split packages. For a detailed description of the options, seethe F1 help about the parameters prompted on the screen Split STR Files while running SAPinstto export the database. The options can be used separately or ‒ when using the new Java basedsplitting tool ‒ combined.

n “Splitting of STR Files” is part of the “Advanced Export Parameters” and is disabled by default.If you select the splitting option and unless you did not already perform some tests, using thesplitting tool parameters selected by SAPinst is a good starting point.

Caution

If you want to split STR files, youmust first create the EXT files for the target database system.You can find the EXT files in your export dump directory, subdirectory DB/<DBTYPE>, for exampleDB/ORA.

Process Flow

For UNIX, Windows, or System i, see System Copy Procedure [page 28].

4.1 System Copy Procedure

This section describes the system copy procedure using R3load and Jload.

Process Flow on the Source System (Export)When performing the export you create a MIGRATION EXPORT CD image, which contains the dataof the exported system, and which you use to install the target system.Follow the sequence of steps described in the process flows below for a:

n Central Systemn Distributed System and High-Availability System

Central SystemTo perform the export for a central system, you need to proceed as follows on the central system host:

1. Heterogeneous system copy: Generate the migration key athttp://service.sap.com/migrationkey. Enter the installation number of your source systemwhen prompted.

2. Perform the export on the central system host:

28/168 PUBLIC 03/12/2009



a)


Make sure that the QCM tables are deleted from your system.For more information, see General Technical Preparations [page 21].End of: UNIX;Windows

b)


Prepare the Windows host for the SAP system installation.For more information, see Preparing the Windows Host for the SAP System Installation [page 44].End of: IBM i5/OS

c)


Prepare a Windows user account and a System i user profile.For more information, see Preparing a Windows User Account and System i User Profile [page 45].End of: IBM i5/OS

d)


Install TMKSVR and create an installation share.For more information, see Installing TMKSVR and Create an Installation Share [page 47].End of: IBM i5/OS

e) Generate DDL statements.For more information, see Generating DDL Statements [page 31].

f) Prepare the system for table splitting (optional).For more information, see Preparation for Table Splitting [page 32].

g) Run SAPinst on UNIX, Windows, or System i to prepare the source system for parallel export orparallel import (optional).For more information, see Running SAPinst on UNIX or Windows to Perform the Export [page 37] orRunning SAPinst on System i to Perform the Export [page 44].In SAPinst, choose the installation service Export Preparation.

h) Run SAPinst on UNIX, Windows, or System i to export the database instance and the centralinstance.In SAPinst, choose the installation service Database and Central Instance Export.For more information, see Running SAPinst on UNIX or Windows to Perform the Export [page 37] orRunning SAPinst on System i to Perform the Export [page 44].

Note

If R3load processes fail due to an error, solve the problem and perform a restart.For more information, see Restarting R3load Processes [page 54].

03/12/2009 PUBLIC 29/168


Only valid for: IBM i5/OS;UNIX

Caution

If your database instance is running on HP PA-Risc, you must proceed as described in SAPNote 884452.

End of: IBM i5/OS;UNIX

Result

You have finished this part of the system copy. To complete the system copy, you set up the targetsystem using SAPinst.For more information, see Setting Up the Target System Using SAPinst [page 56].

Distributed System or High-Availability SystemTo perform the export for a distributed system or a high-availability-system, you need to proceedas follows:

1. Heterogeneous system copy only: Generate the migration key athttp://service.sap.com/migrationkey. Enter the installation number of yoursource system when prompted

2. Perform the export on the database instance host:

a)


Make sure that the QCM tables are deleted from your system.For more information, see General Technical Preparations [page 21].End of: UNIX;Windows

b) Generate DDL statements.For more information, see Generating DDL statements [page 31].

c) Prepare the system for table splitting (optional).For more information, see Preparation for Table Splitting [page 32].

d) Run SAPinst on UNIX, Windows, or System i to prepare the source system for parallelexport/import (optional). In SAPinst, choose the installation service Export Preparation.For more information, see Running SAPinst on UNIX or Windows to Perform the Export [page 37] orRunning SAPist on System i to Perform the Export [page 44].

e) Run SAPinst on UNIX, Windows, or System i to export the database instance. In SAPinst,choose the installation service Database Instance Export.For more information, see Running SAPinst on UNIX or Windows to Perform the Export [page 37] orRunning SAPinst on System i to Perform the Export [page 44].

Caution

If your database instance is running on HP PA-Risc, you must proceed as described in SAPNote 884452.

30/168 PUBLIC 03/12/2009




4 Database Independent System Copy4.2 Generating DDL Statements

3. Perform the export on the central instance host:You run SAPinst to export the central instance. For more information, see Exporting the SourceSystem Using SAPinst [page 37].In SAPinst, choose the installation service Central Instance Export.

Result

You finished this part of the system copy. To complete the system copy, you set up the target systemusing SAPinst.For more information, see Setting Up the Target System Using SAPinst [page 56].

Overview on Export Options

Figure 1:

4.2 Generating DDL Statements

To migrate nonstandard database objects, you need to generate DDL statements using the ABAPreport SMIGR_CREATE_DDL.You must perform this procedure before starting SAPinst.

Procedure

1. Log on to the system as a system administrator in a productive client.

03/12/2009 PUBLIC 31/168

4 Database Independent System Copy4.3 Preparation for Table Splitting

2. Call transaction SE38 and run the program SMIGR_CREATE_DDL.3. Select the target database. Depending on the database manufacturer, you might need to select the

database version. The value help supports you in selecting the database version. In general, youonly should enter a database version that is available in the value help .

4. You are able to select Unicode Migration if you also wish to perform a Unicode system copy (fromUnicode to Unicode) or a Unicode conversion (from non-Unicode to Unicode).

5. Specify an empty working directory to which the files generated by the report are to be written.6. If required, you can restrict the generation of DDL statements to specific table types or individual

tables.7. Execute the program.

The DDL statements are generated and are written to the specified directory.

Caution

If no database-specific objects exist in the database, no SQL files will be generated. As long as thereport terminates with status successfully, this is not an error.

8. Before starting the export, the generated SQL files have to be copied from the specified directory tothe <instdir> directory of the export.

For additional database-specific information, see also SAP Note 888210.

4.3 Preparation for Table Splitting

The tool R3ta processes large tables. Instead of exporting/importing one table with one R3loadprocess, the table is processed in, for example, 10 entities. Each entity can be processed by differentR3load processes. The advantages of splitting the tables are:

n Large tables are processed in smaller packages. If the export or import of a table aborts with anerror, only the processing of the package where the error occurred has to be repeated and not forthe complete table.

n The export and import of one table can be performed in parallel by starting several R3loadprocesses to work on some packages in parallel.

Prerequisites

n The export and import has to be performed with the Migration Monitor when the table splittingfeature is used.

n For the following databases, we recommend that you create an index on the column listed in thehints file for the table you want to split before starting R3ta:l DB2 for z/OS (Only create a temporary index if you want to perform an unsorted unload.)

32/168 PUBLIC 03/12/2009



l OracleFor more information, see paragraph Creating a Temporary Index.

Restrictions

n Only tables that are described in the SAP dictionary can be split.n The following tables cannot be split:l DDNTF

l DDNTF_CONV_UCl DDNTT

l DDNTT_CONV_UCl DDLOG (is never copied, but created empty in the target system)

1. Update the R3ta , R3ldctld and the db<dbtype>slib.* in the kernel directory. You can find aversion of these files on the InstallationMaster DVD in the directory IM_<OS>/<DBTYPE>/{UC/NUC}.

2. Create a file that contains lines of the form <table>%<nr of splits> for all tables to be split.

Caution

The tables listed in this file have to appear in alphabetical order!

3. Start SAPinst.4. Choose SAP NetWeaver System Copy Source System ABAP System <Database> <Unicode

or Non-Unicode> Table Splitting Preparation .5. Specify SAPSID, <sidadm> password, the file that contains the split information, the export

directory, and the number of parallel R3ta jobs.

Caution

The specified path to the export directory must not contain blanks!

6. Continue with Next.

Caution

When doing a code page conversion (non-Unicode ® Unicode; 4102 « 4103), make sure not touse a WHERE condition with the column PAGENO included. If the column PAGENO is includedin the WHERE condition, repeat the table splitting - either with different splitting parameters orby defining a suitable column for this table using the R3ta_hints.txt.

7. Check in the export directory <export dump directory>/ABAP/DATA if *.WHR files have beencreated for all tables that are to be split.If no *.WHR files could be produced for some of these tables, create fewer packages for these tables:a) Create a new, empty installation directory.b) Define a new, empty export dump directory <temporary dump directory>.

03/12/2009 PUBLIC 33/168


c) Run the Prepare Table Splitting service again and provide an input file that contains only themissing tables with a lower number of packages for each defined table.

If the *.WHR files have been created for the missing tables, merge these results with the resultsfrom the first Prepare Table Splitting run:a) Copy the *.WHR files from <temporary dump directory>/ABAP/DATA to <export dump

directory>/ABAP/DATA.b) Add the lines from <temporary dump directory>/ABAP/DATA/whr.txt to <export dump

directory>/ABAP/DATA/whr.txt.8. If required, create the temporary index on the source system’s tables to be split. For more

information, see paragraph Creating a Temporary Index.

Parallel data export of a table is supported by all database platforms but not parallel data import.When the target database platform does not support the parallel data import, the Migration Monitorhas to be configured in the way that the data import processes the packages are sequentially. For moreinformation, see Processing Split Tables.

Using HintsWith the file R3ta_hints.txt, you can instruct R3ta to use specific columns of a table to create aWHERE condition. The file has to be located in the directory in which you start R3ta.With one line in the file R3ta_hints.txt, you specify the table name followed by one or more columnnames, separated by a blank. The columns have to be part of the primary key of the table. Thesespecifications are used by R3ta to create the WHERE condition.A file R3ta_hints.txt with column hints for several tables is delivered with the Installation MasterDVD. After the Table Splitting Preparation, make sure you select the Split predefined tables checkbox and addthe R3ta_hints.txt file in the Split STR Files dialog box. If you want to modify this file, copy it fromthe directory <IM_OS>/COMMON/INSTALL to the installation directory and adapt it according yourrequirements as soon as the Parameter Summary dialog appears and before starting the processing phase.

Creating a Temporary Index

Only valid for: IBM DB2 for z/OS

IBMDB2 z/OS only: Create the corresponding temporary index on the database with database tools.Only create a temporary index if you want to perform an unsorted unload. This is the case when youuse a DDLDB2.TPL file with no ORDER_BY_PKEY and the R3load does not overrule this setting. Whichtables cannot be unloaded unsorted is described in SAP Note 954268.End of: IBM DB2 for z/OS

34/168 PUBLIC 03/12/2009




Example

1. Use the DEFER YES parameter to create the index.2. Afterwards, use the REBUILD INDEX job to speed up the index creation process.

End of: IBM DB2 for z/OS


Oracle only: For further information and for alternatives, see SAP Note 960280.End of: Oracle

For each table to be split, R3ta creates the following files to facilitate the creation of the temporaryindex:

File Description

<table>_IDX.STR Contains the description of the temporary index; thedefault index name is <table>~IMG.

<table>_IDX.TSK Contains the task to create the temporary index.

<table>_IDX.cmd R3load command file for creating the temporaryindex.

DRP_<table>_IDX.TSK Contains the task to drop the temporary index.

DRP_<table>_IDX.cmd R3load command file for dropping the temporaryindex.

You can use the R3load cmd, STR and TSK files created by R3ta to create the index.

1.

Only valid for: IBM DB2 for i5/OS;IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server

Make sure that you do not lock the table while creating the temporary index. Dependingon your database platform it might be necessary to modify the create index statement in theDDL<DBTYPE>.TPL file.End of: IBM DB2 for i5/OS;IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server

2.


Make sure that you do not lock the table while creating the temporary index. Dependingon your database platform it might be necessary to modify the create index statement in theDDL<DBTYPE>.TPL file.Edit the file DDLORA.TPL and add the highlighted key words to the creind statement:creind: CREATE &unique&

INDEX &ind name&

ON &tab name&

( /{ &fld name& /-, /} )

03/12/2009 PUBLIC 35/168


4 Database Independent System Copy4.4 Preparing the Export

TABLESPACE &tablespace&

STORAGE (INITIAL &init&

NEXT &next&

MINEXTENTS &minext&

MAXEXTENTS &maxext&

PCTINCREASE &pctinc& )

NOLOGGING

COMPUTE STATISTICS PARALLEL

ONLINE;End of: Oracle

3. Call R3load as user <sapsid>adm with the following parameters:R3load –dbcodepage <source system’s dbcodepage> –i

<table>_IDX.cmd –l <table>_IDX.log

If your source system is a non-Unicode system, the dbcodepage is 1100. If your source system is aUnicode system, the dbcodepage is 4102 (Big Endian) or 4103 (Little Endian).

4.4 Preparing the Export

Optionally you can prepare the source system for the export using R3load and Jload, so as to enableparallel export/import. For this purpose you need to create certain files.The following steps are performed:

n Creating the export directory structuren Creating database structure files (*.STR)n Updating database statistics (…)n Size calculation for the target database (*.EXT,DBSIZE.XML)

These export preparations are required, if:

n You want to build up the target system to the point where the database load starts, before theexport of the source system has finished.

n Export and import processes should run in parallel during the system copy process.

Procedure

1. You run SAPinst to perform the service Export Preparation.For more information, see Running SAPinst on UNIX or Windows to Perform the Export [page 37].

2. As soon as the export preparations have finished successfully, the complete export directory withits structure and the generated files, which are required for building up the target system, have tobe transferred to the target host. You can choose one of the following methods:n Use themigrationmonitor with the FTP Copy Option to transfer the files to the target instance.n Copy the export dump directory manually to the target host.

36/168 PUBLIC 03/12/2009

4 Database Independent System Copy4.5 Exporting the Source System Using SAPinst

n The export dump directory can be shared and thus made accessible on the target host.In any case make sure that the dump directory and its subdirectories and files are accessible foruser <sapsid>adm of the target system.

Note

For more information, see the documentationMigration Monitor ‒ User’s Guide in the MIGMON.SARarchive on the SAP Installation Master DVD.

4.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:

n Running SAPinst on UNIX or Windows to Perform the Export [page 37]n Running SAPinst on System i to Perform the Export [page 50]

4.5.1 Running SAPinst on UNIX or Windows to Perform theExport

This procedure tells you how to run SAPinst to export the database of your SAP system. SAPinstincludes a SAPinst GUI and a GUI server, which both use Java.This section describes a standard export where SAPinst, SAPinst GUI, and the GUI server are runningon the same host. If required, you can instead perform a remote system copy with SAPinst, whereSAPinst GUI is running on a separate host from SAPinst and the GUI server. For more information,see Performing a Remote Installation with SAPinst [page 155].Note the following about SAPinst:

n When you start SAPinst, SAPinst GUI and the GUI server are also started. SAPinst GUI connectsusing a secure SSL connection to the GUI server and the GUI server connects to SAPinst.

Only valid for: UNIX

n SAPinst normally creates the installation directory sapinst_instdir directly below the temporarydirectory. SAPinst finds the temporary directory by checking the value of the environmentvariables TEMP, TMP, or TMPDIR. If no value is set for these variables, SAPinst uses /tmp as defaultinstallation directory.

n The SAPinst Self-Extractor extracts the SAPinst executables to the temporary directory. Theseexecutables are deleted again after SAPinst has stopped running. If required, you can terminateSAPinst and the SAPinst Self-Extractor by pressing Ctrl+C .

End of: UNIX

03/12/2009 PUBLIC 37/168


Only valid for: Windows

n SAPinst normally creates the installation directory sapinst_instdir, where it keeps its logfiles, and which is located directly below the Program Files directory. If SAPinst is not able tocreate sapinst_instdir directly below the Program Files directory, SAPinst tries to createsapinst_instdir in the directory defined by the environment variable TEMP.

n SAPinst creates a subdirectory for each installation service, called<sapinst_instdir>\<installation_service> which is located below%ProgramFiles%\sapinst_instdir.

n The SAPinst Self-Extractor extracts the executables to a temporary directory (TEMP, TMP,

TMPDIR, or SystemRoot). These executables are deleted after SAPinst has stopped running.Directories with the name sapinst_exe.xxxxxx.xxxx sometimes remain in the temporarydirectory. You can safely delete them.In the temporary directory, you can also find the SAPinst Self-Extractor log file dev_selfex.out,which might be useful if an error occurs.

End of: Windows

Caution

If SAPinst cannot find a temporary directory, the installation terminates with the error FCO-00058.


n If you want to terminate SAPinst and the SAPinst Self-Extractor, do one of the following:l Right-click the icon for the SAPinst output window located in theWindows tray and choose Exit.l Click the icon for the SAPinst output window located in the Windows tray and choose File

Exit .

End of: Windows

Prerequisites

Caution

Make sure that you shut down all SAP Application Servers before the export. The database must stillbe running. Otherwise, the target system might be inconsistent.

n


You are logged on to your host as user root.End of: UNIX

38/168 PUBLIC 03/12/2009



You are logged on to your host as user with the required rights and privileges that authorize youto install the SAP system with the SAPinst tool. For more information, see section Required UserAuthorization for the Installation in your installation guide.End of: Windows

n Make available theMaster Installation DVD.

n You need at least 60 MB of free space in the installation directory for each ABAP installation option,and at least 130 MB of free space in the installation directory for each Java installation option. Inaddition, you need 60-200 MB free space for the SAPinst executables.


If you cannot provide 200 MB free space in the temporary directory, you can set one of theenvironment variables TEMP,TMP, or TMPDIR to another directory with 200 MB free space for theSAPinst executables.End of: UNIX

n


Before starting the export steps on the central instance of the source sys-tem, make sure that you have at least the same amount of disk spaceavailable in \\SAPLOC\<SAPSID>\<InstanceName>\SDM\program as is used in\\SAPLOC\<SAPSID>\<InstanceName>\root\origin. During the export some archives are writtento the program subdirectories and SAPinst aborts if there is not enough space.End of: Windows

n

Only valid for: DB2 UDB for UNIX and Windows

Before you start the export of the existing SAP System, you have to download thecurrent version of R3szchk at http://service.sap.com/patches and copy it to directory/usr/sap/<>/SYS/exe/run/.End of: DB2 UDB for UNIX and Windows


n Before starting the export, make sure that you have at least the same amount ofdisk space available in /sapmnt/<SAPSID>/<InstanceName>/SDM/program as is used in/sapmnt/<SAPSID>/<InstanceName>/SDM/root/origin.During the export, some archives are written to the program subdirectories and SAPinst aborts ifthere is not enough space.

n Make sure that the DISPLAY environment variable is set to <host_name>:0.0, where <host_name>is the host where the SAPinst GUI is displayed.

n Make sure that your SAPINST_JRE_HOME environment variable is set to a valid Java RuntimeEnvironment (JRE).

03/12/2009 PUBLIC 39/168

http://service.sap.com/patches


n

Only valid for: AIX

If the operating system is AIX 64-bit, make sure that the PATH variable points to a JDK/JRE forAIX 64-bit.End of: AIX

End of: UNIX

For more information about SAPinst, see Using SAPinst GUI [page 151], Interrupted Installation with SAPinst[page 151], and Performing a Remote Export Using SAPinst [page 154].

1. Start SAPinst from the SAP Installation Master DVD as follows:


Choose one of the following ways:End of: UNIX


n Using the default installation directory (recommended)Enter the following commands:cd <Installation_Master_DVD>/IM_<OS> ./sapinst

SAPinst creates a directory called sapinst_instdir, which is the current working directory foryour installation, below the temporary directory of your operating system.

n Using an alternative installation directoryIf you want to use an alternative installation directory, set the environment variable TEMP,TMP, or TMPDIR.

n 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, TMP, or TMPDIR point, forexample, by using a crontab entry.

n Make sure that your current working directory is not an IM_<OS> directory belonging toanother operating system.

Example

For example, the following causes an error:$ cd /sapcd2/IM_HPUX_IA64$ /sapcd2/IM_HPUX_PARISC/sapinstTo correct this, enter the following:$ cd /sapcd2/IM_HPUX_PARISC$ /sapcd2/IM_HPUX_PARISC/sapinst

End of: UNIX


n Double-click sapinst.exe from the following path:

40/168 PUBLIC 03/12/2009


<DVD_drive>:\DATA_UNITS\IM_WINDOWS_<platform>

SAPinst GUI normally starts automatically by displaying theWelcome screen.End of: Windows

Note

During the installation, the default ports 21200 and 21212 are used for communication betweenSAPinst, GUI server, and SAPinst GUI. SAPinst uses port 21200 to communicate with the GUIserver. The GUI server uses port 21212 to communicate with SAPinst GUI. You get an errormessage if one of these ports is already in use by another service.In this case, 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.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, enter the following command: sapinst —p.

2. On theWelcome screen, choose Software Life-Cycle Options System Copy <database> SourceSystem <Distribution option> Based on <technical stack> .

3. Select the corresponding system copy option from the tree structure according to the sequence ofthe process flow for the database-specific or the database-independent system copy procedure.For more information, see Database-Specific System Copy procedure [page 61] or Database-IndependentSystem Copy [page 27].

Caution

Make sure that you choose the system copy options exactly in the order they appear for eachsystem variant.

The following table provides an overview about the available installation options available forthe export:

Export Services for a Central System

Export Service Remarks

Export Preparation

NoteYou do not perform this step if you use thedatabase-specific method.

Optional step for preparing the export.SAPinst performs the following steps:n Creates the export directory structuren Creates database structure files (*.STR)n Updates database statistics (…)n Calculates the size of the target database

(*.EXT,DBSIZE.XML)

Database and Central Instance Export Mandatory step for system copy procedure.

03/12/2009 PUBLIC 41/168



If you use the database-specific procedure,SAPinst only performs the following steps:

Noten Creates the export directory structure with

label filesn Archives the SDMn Archives application-specific file system

content.

SAPinst performs the following steps:n Creates the export directory structure with label filesn Creates database structure files (*STR)n Updates database statisticsn Calculates the size of the target database

(*EXT,DBSIZE.XML)n Exports the database contentn Archives the SDMn Archives application-specific file system content

4. After you have selected the required option, choose Next.


Caution

If your database instance is running on HP PA-Risc, you must proceed as described in SAP Note884452.

End of: UNIX

Note

If you generated SQL files with DDL statements (see Generating DDL Statements [page 31]), copy thegenerated files into the SAPinst installation directory as soon as it has been created by SAPinst.The installation directory will have been created as soon as the first input screen appears.

5. Follow the instructions in the SAPinst input dialogs and enter the required parameters.

Caution

You must choose Typical when performing a system copy with database tools.

Note

For more information about input parameters in SAPinst, position the cursor on the parameterfield and choose F1 .

6. Database-specific procedures only: On the screen SAP SystemDatabase Export choose option SystemCopy Method Use database specific tools .

After you have entered all required input parameters, SAPinst starts the export and displays theprogress during the processing phase.

42/168 PUBLIC 03/12/2009



TroubleshootingIf an export process aborts due to a hardware failure (for example, file system full, power outage,operating system crash), you have to repeat the export of the complete package. Remove the dumpfiles <package>.<nnn>, the TOC file <package>.TOC, the log file <package>.log and make sure thatall tables in the TSK file <package>.*TSK* have the status flag ’xeq’ or ’err’ set.

n If there is not enough disk space in the export directory, the R3load database export fails. You canthen find error messages in the log files SAP*.log.You can subsequently move the dump files that have been created from the file system in whichthe export directory is located to a different file system during the export. Currently there is nopossibility to automatically distribute the export over different file systems.

n If an error occurs during the dialog phase, SAPinst:l Stops the export.l Displays a dialog that informs you about the error.You can now directly view the log file by choosing View Logs.Finally you must abort the export with OK and try to solve the problem.

n If an error occurs during the processing phase, SAPinst:l Stops the export.l Displays a dialog that informs you about the error.You can now:l Directly view the log file by choosing View Logs.l Try to solve the problem.l Continue the export by choosing Retry.l Abort the export by choosing OK.


n System Copy - 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 installationdirectory.Reason:Only members of sapinst UNIX group can access the installation directory.This group is created first by SAPinst starting from NW 7.0 SR1.Solution:Associate <sid>adm and ora<sid> OS users with sapinst group manually if this associationis missing.Verify /etc/group file and check if sapinst group exists and OS users are members of this group.If sapinst group does not exist yet, start SAPinst. SAPinst will create this group during startupbefore product catalog list will be displayed.Edit /etc/group file and associate OS users with sapinst group.

03/12/2009 PUBLIC 43/168


Continue with the export.

End of: UNIX

For more information, see Using SAPinst GUI [page 151], Interrupted Installation with SAPinst [page 151], andPerforming a Remote Export Using SAPinst [page 154].


4.5.2 Running SAPinst on System i to Perform the Export

4.5.2.1 Preparing the Windows Host for the SAP SystemInstallation

The Java-based SAPinst graphical user interface (SAPinst GUI) requires a Java Development Kit (Java™2 SDK, Standard Edition) with graphical capabilities (AWT, Swing). Since System i does not providea graphical user interface, you must install the JDK on a Windows host to perform the installationwith SAPinst.

PrerequisitesTo prepare the system for SAPinst and SAPinst GUI you need to do the following:

n Necessary operating system versions: Windows NT/2000/2003/XPn Check your Java Runtime Environment (JRE) on the host where SAPinst GUI runs, because the

JRE cannot be integrated into the SAPinst GUI executable for all platforms due to licensing issues.n Set the system path if you install on Windows.

ProcedureThe SAP J2EE Engine requires a Java Development Kit (Java™ 2 SDK, Standard Edition). Therefore,make sure a valid JDK version is installed on every host on which you want to install an SAP instanceincluding the SAP J2EE Engine.For more information about the JDK versions that are released for the SAP WebApplication Server, SAP components based on SAP Web AS and the SAP J2EE Engine, seehttp://service.sap.com/platforms Product Availability Matrix SAP NetWeaver SAP NetWeaver

’04 JSE Platforms

44/168 PUBLIC 03/12/2009

http://service.sap.com/platforms


Note

n JDK is not part of the SAP shipment. If necessary, you need to download and install it.

n To check the version of an already installed JDK, enter:java -version

n If you have more than one Java Virtual Machine (JVM) installed on your system (for example,you have two JDKs with different versions installed), make sure that the JAVA_HOME environmentvariable is set to the valid <JAVA_HOME> directory. Make sure that %JAVA_HOME%\bin is includedin your system path.

Only valid for: IBM i5/OS IBM i5/OS IBM DB2 for i5/OS

4.5.2.2 Preparing a Windows User Account and System iUser Profile

For the installation you need to create a user account on your Windows installation host and auser profile on the System i you want to install.The following requirements apply:

n The System i user profile and the Windows user account must have the same name and password.

n

Only valid for: SAP CRM;SAP ERP;SAP NetWeaver;SAP SRM

The System i user profile must have user class *SECOFR and all special authorities that belongto user QSECOFR.End of: SAP CRM;SAP ERP;SAP NetWeaver;SAP SRM

n

Only valid for: SAP SCM

The System i user profile must be the user QSECOFR.

Note

This is different to other installations on System i. For other installations, we recommended thatyou create user SAPINST or SAPINSTUSR. However for SCM, you need to use the user QSECOFRbecause the liveCache client software has to be installed by this special user.

End of: SAP SCM

n The Windows user account must have administrator rights on the Windows installation host.

03/12/2009 PUBLIC 45/168



Note

The user name SAPINSTUSR and the password SAP are used as examples in the procedures. Informer installation documentation, we used the user SAPINST. However, in future releases SAP hasintroduced a group called SAPINST on System i which conflicts with the previously recommendeduser SAPINST.

End of: SAP CRM;SAP ERP;SAP NetWeaver;SAP SRM

Windows:

1. Create a local user.

2.


In the field User name, enter your installation user name, for example, SAPINSTUSR.End of: SAP CRM;SAP ERP;SAP NetWeaver;SAP SRM

3.


In the field User name, enter your installation user name QSECOFR.End of: SAP SCM

4.


In the fields Password and Confirm password, enter the password SAP.End of: SAP CRM;SAP ERP;SAP NetWeaver;SAP SRM

5.


In the fields Password and Confirm password, enter the password of the user QSECOFR on your System i.End of: SAP SCM

6. Deselect User must change password at next logon.

7.


Assign the new user SAPINSTUSR to the group Administrators.End of: SAP CRM;SAP ERP;SAP NetWeaver;SAP SRM

8.


Assign the new user QSECOFR to the group Administrators.End of: SAP SCM

System i:


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 CRM;SAP ERP;SAP NetWeaver;SAP SRM

46/168 PUBLIC 03/12/2009



To change the user QSECOFR, enter the command CRTUSRPRF USRPRF(QSECOFR) LANGID(ENU)

CNTRYID(US) CCSID(500). After the installation, you can revert the user profile QSECOFR back tothe old values.End of: SAP SCM

Caution

You should not set the system variable QIBM_PASE_CCSID. You should leave this variable empty!

End of: IBM i5/OS IBM i5/OS IBM DB2 for i5/OS


4.5.2.3 Installing TMKSVR and Creating an Installation Share

The TMKSVR is the interface between System i and Windows for the installation with SAPinst. SAPinstis running on Windows, but has to install the product on System i. This means that all actionsrequired for System i are initiated remotely on Windows but executed locally using the TMKSVR. Thecommunication is done using TCP/IP.In addition, an installation share on the System i host needs to be created andmapped to the Windowsinstallation host, which is done automatically by the TMKSVR.The TMKSVR has to be installed and an installation share has to be created on all System i hosts whereinstances of an SAP system should be installed.

Prerequisites

n An FTP server running on System in You must prepare a user. For more information about how users are prepared, see Preparing a

Windows User Account and System i User Profile [page 45].n The Installation Master DVDmust be inserted in the DVD drive of your Windows host.

n Make sure there is no system variable LANG defining a LOCAL. Otherwise, code page problemsmight prevent TMKSVR processes from starting.

Procedure

1. Log on to your Windows host as the installation user. For more information, see Preparing a WindowsUser Account and System i User Profile [page 45].

03/12/2009 PUBLIC 47/168



Note

This user must have the same user ID and password as the user that you are using for theinstallation on System i (a user with administrator rights similar to QSECOFR).



Note

This user must have the same user ID and password as the user that you are using for theinstallation on System i. For SCM, this user must be QSECOFR).

End of: SAP SCM

2. Run SETUP.EXE from the directory IM_OS400_PPC64\TMKSVR on the DVD containing theinstallation package. You can start the setup program by double-clicking on it in the WindowsExplorer.The following dialog box appears:


Figure 2:


48/168 PUBLIC 03/12/2009



Figure 3:

End of: SAP SCM

3. Enter the following values:n System i Hostname:

Enter the name of the System i host where you want to install TMKSVR.

n


System i Administrator (QSECOFR or similar):Enter the System i user. For more information, see Preparing a Windows User Account and System iUser Profile [page 45].End of: SAP CRM;SAP ERP;SAP NetWeaver;SAP SRM

n


System i Administrator (QSECOFR):Enter the System i user. For more information, see Preparing a Windows User Account and System iUser Profile [page 45].End of: SAP SCM

n TMKSVR instance number:Leave the value at 0.

n TMKSVR Instance Port (also referred to as the Dispatcher Port):Leave the value at 59975, if possible. Only change this port number if you encounter problemsduring installation because the port is in use.

ResultThe installation uses FTP to install and starts the TMKSVR on System i. During installation, a librarynamed TMKSVR<nn> is created, with <nn> being the instance number (for example, TMKSVR00).A NetServer share named ROOTBIN is created on the System i host. You can map the share now toyour Windows PC or let SAPinst map it during the installation.

03/12/2009 PUBLIC 49/168


For more information, see the documentation INSTALL.PDF on the DVD in directoryIM_OS400_PPC64\TMKSVR.End of: IBM i5/OS IBM i5/OS IBM DB2 for i5/OS


4.5.2.4 Starting SAPinst on System i

Caution

This section refers to “installation of an instance”, which is a synonym for “export an SAP system”.

This procedure tells you how to run SAPinst to install one or more SAP instances. It describes aninstallation where SAPinst GUI and SAPinst server are running on the same Windows host.SAPinst creates the installation directory \usr\sap\sapinst on System i.

Prerequisites

Caution

Make sure that you shut down all SAP Application Servers before the export. The database must stillbe running. Otherwise, the target system might be inconsistent.

n TMKSVR is up and running: WRKACTJOB SBS (TMKSVR00) (there must be a DISPATCH job). For moreinformation, see Installing TMKSVR and Creating an Installation Share [page 47].

n The Windows host is set up. For more information, see Preparing the Windows Host for the SAP SystemInstallation [page 44].

n The users required for the installation are prepared. For more information, see Preparing a WindowsUser Account and System i User Profile [page 45].

n Make sure that the JAVA_HOME environment variable is set correctly on your Windows host.

1. Log on to the Windows host as the installation user. For more information, see Preparing a WindowsUser Account and System i User Profile [page 45].

2. Start SAPinst from the SAP Installation Master DVD in one of the following ways:n If using the default installation directory (recommended) by double-clicking sapinst.exe

from the following path:<Mapped drive>:<copied ... DVD>\IM_OS400_PPC64

50/168 PUBLIC 03/12/2009


Note

l During the installation, the default ports SAPinst 21212 and 21213 are used forcommunication between SAPinst, GUI server and SAPinst GUI. SAPinst uses port 21200to communicate with the GUI server. You get an error message if one of these ports isalready in use by another service. In this case, open a command prompt and change tothe required directory as follows:<Mapped drive>:<copied ... DVD>\IM_OS400_PPC64

Enter the following command in a single line:sapinst.exe

SAPINST_DIALOG_PORT=<free_port_number_sapinst_gui_to_gui_server>

GUISERVER_DIALOG_PORT=<free_port_number_gui_server_to sapinst_gui>

l For a list of all available SAPinst properties, enter the following command: sapinst -p

3. The SAPinst/TMKSVR ‒ Session Parameters dialog box appears and prompts you for the target System iparameters. Enter your values.

Figure 4:

The SAPinst GUI now starts automatically by displaying theWelcome screen.4. In theWelcome 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> .

03/12/2009 PUBLIC 51/168


5. Select the corresponding installation service from the tree structure according to the sequence ofthe process flow for one of the following precedures:n Database-Specific System Copy [page 61]n Database-Independent System Copy [page 27]

Caution

Make sure that you choose the installation services exactly in the order they appear for eachsystem variant.

6. The following table provides an overview about the available installation services available for a:n Central systemn Distributed system or high-availability system

Export Services for a Central System


Export Preparation


Optional step for preparing the export.SAPinst performs the following steps:n Creates the export directory structuren Creates database structure files (*.STR)n Updates database statistics (…)n Calculates the size of the target database

(*.EXT,DBSIZE.XML)

Database and Central Instance ExportIf you use the database-specific procedure,SAPinst only performs the following steps:

Noten Creates the export directory structure with

label filesn Archives the SDMn Archives application-specific file system

content.

Mandatory step for system copy procedure.SAPinst performs the following steps:n Creates the export directory structure with label filesn Creates database structure files (*STR)n Updates database statisticsn Calculates the size of the target database

(*EXT,DBSIZE.XML)n Exports the database contentn Archives the SDMn Archives application-specific file system content

Export Services for a Distributed System or a High-Availability System


Export Preparation


Optional step for the database-independent system copyprocedure to prepare the export.You need to perform this step on the database instancehost.SAPinst performs the following steps:n Creates the export directory structuren Creates database structure files (*.STR)n Updates database statistics(…)

52/168 PUBLIC 03/12/2009



n Calculates the size of the target database(*.EXT,DBSIZE.XML)

Database Instance Export

Noten You do not perform this step if you use

the database-specific method.n Youmust perform this step before you

perform Central Instance Export.

Mandatory step for the database-independent systemcopy procedure.You need to perform this step on the database instancehost.SAPinst performs the following steps:n Creates the export directory structure with label filesn Creates database structure files (*STR)n Updates database statisticsn Calculates the size of the target database

(*EXT,DBSIZE.XML)n Exports the database content

Central Instance Export

NoteBefore you perform this step, youmust havecompleted the Database Instance Export.

Mandatory step for database-independent system copyprocedure.You need to perform this step on the central instancehost.SAPinst performs the following steps:n Creates the export directory structure with label files.n Archives the SDMn Archives application-specific file system content

7. After you have selected the required installation service, choose Next.8. Choose Next

Note

If you generated SQL files with DDL statements (see Generating DLL Statements [page 31]), copy thegenerated files into the SAPinst installation directory as soon as it has been created by SAPinst:a) Choose Database and Central Instance Exportb) Choose Next.c) The installation directory has been created as soon as the first input screen appears.

9. Follow the instructions in the SAPinst input dialogs and enter the required parameters.

Caution

You must choose Typical when performing a system copy with database tools.

Note

For more information about input parameters in SAPinst, position the cursor on the parameterfield and choose F1 .

03/12/2009 PUBLIC 53/168


After you have entered all required input parameters, SAPinst starts the installation and displaysthe progress of the installation.When the installation has successfully completed, the screen Finished installation is displayed.

Troubleshooting

Caution

If an export process aborts due to a hardware failure (for example, file system full, power outage,operating system crash), you have to repeat the export of the complete package. Remove the dumpfiles <package>.<nnn>, the TOC file <package>.TOC, the log file <package>.log and make sure thatall tables in the TSK file <package>.*TSK* have the status flag ’xeq’ or ’err’ set.

n If an error occurs during the dialog phase, SAPinst:l Stops the installation.l Displays a dialog that informs you about the error.You can now directly view the log file by choosing View Logs.Finally you must abort the installation with OK and try to solve the problem.

n If an error occurs during the processing phase, SAPinst:l Stops the installation.l Displays a dialog that informs you about the error.You can now directly view the log file by choosing View Logs.l Try to solve the problem.l Retry the installation by choosing Retry.l Abort the installation by choosing OK.For more information, see Interrupted Installation with SAPinst [page 151].

End of: IBM i5/OS

End of: IBM i5/OS

4.5.3 Restarting R3load Processes

The state file allows package states to be manually updated to restart failed R3load processes.

Example

For example, if package processing failed and the package state has the value ‒, the state can be setto 0 and processing of the package is restarted.

n To restart package processing, set the package state from – to 0.n To skip package processing, set the package state from 0 or – to +. (This is not recommended,

because it can cause inconsistent data files or database content.)

54/168 PUBLIC 03/12/2009


n If the package is currently being processed (the package state is ?), then any manual modificationsof the package state are ignored.

n Sockets only: You cannot restart processes.

Restarting R3load Processes Using the Socket OptionThere are four possible situations where an R3load restart may be required.First of all, you need to cancel the R3load process. If one of the corresponding R3load processes(export or import) is still running, cancel it as well. Then restart SAPinst to continue with the systemcopy. To continue with the system copy proceed as follows:

n If both the import and the export are completed successfully, there is nothing to do.n If the export was completed successfully, but the import is cancelled with errors, proceed

as follows:l If the export was successful but the import was cancelled when creating the index or the

primary key, set the status for export_state.properties from ’+’ to ’0’.l If the export was completed successfully but the import was cancelled when loading the

table content, set the status

u for export_state.properties from ’+’ to ’0’

u for the TSK file of the export from ’ok’ to ’err’n If both the export and the import are cancelled with errors, proceed as follows:l If the errors in export and import relate to the same table, there is nothing to do.l If the errors relate to different tables, 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’.

Example

Export Import

Table name Status Table name Status

TAB_1 ok TAB_1 ok

TAB_2 err TAB_2 ok

TAB_3 xeq TAB_3 err

TAB_4 xeq TAB_4 xeq

The first object with errors here is TAB_2 (export). That means that in the import TSK filethe status for TAB_2must be set from ’ok’ to ’err’. The entry in the *state* file also must be setfrom ’+’ to ’0’.

n When the import was completed successfully, but the export was cancelled with errors, youcan set the status in the export_state.properties from ’-’ to ’+’.

03/12/2009 PUBLIC 55/168

4 Database Independent System Copy4.6 Setting Up the Target System

More InformationSee also R3load Processes Using the Migration Monitor [page 133].

4.6 Setting Up the Target System

Purpose

You use SAPinst to install the target system and import the database files that you have exportedfrom the source system.

Process Flow

Central System

Perform the following steps on the central system host:

1. You prepare the central system host for the installation of your target system as described in theinstallation guide for your SAP system solution.

2. If you have already prepared the export (for more information, see Preparing the Export [page 36]) onthe source system, you perform the following steps:a) If you use the FTP Exchange option during the export (transfer type FTP, communication type

Exchange Directory on the screen SAP SystemCommunication Parameters for Export), you make surethat you have transferred the files, which have been generated in step Preparing the Export [page36] on the source system.

b) You transfer the Java export files to the central system target host. For more information, seeTransferring the Export Files to the Target Host [page 57].

c) You install the target system. For more information, see Installing the Target System [page 58].If you did not prepare the export on the source system, you perform the following steps:a) You transfer the Java export files to the central system target host. For more information, see

Transferring the Export Files to the Target Host [page 57].b) You install the target system. For more information, see Installing the Target System [page 58].

3. If required, on (the) dialog instance host(s), you install additional dialog instance(s) asdescribed in the installation guide for your SAP system solution.

Distributed System or High-Availability System

Perform the following steps on the relevant installation hosts of your target system:

1. You prepare the central services instance host, the database instance host and the centralinstance host for the installation of the corresponding instances of your target system asdescribed in the installation guide for your SAP system solution.

2. You install the central services instance for the target system as described in the installationguide for your SAP system solution.

3. You perform the following steps on the database instance host:

56/168 PUBLIC 03/12/2009


n If you have already prepared the export (for more information, see Preparing the Export [page 36])on the source system, you perform the following steps:a) If you use the FTP Exchange option during the export (transfer type FTP, communication type

Exchange Directory on the screen SAP SystemCommunication Parameters for Export), you make surethat you have transferred the files, which have been generated in step Preparing the Export [page36] on the source system.

b) You transfer the Java export files to the central system target host. For more information,see Transferring the Export Files to the Target Host [page 57].

c) You install the database instance of the target system. For more information, see Installingthe Target System [page 58].

n If you did not prepare the export (for more information, see Preparing the Export [page 36]) on thesource system, you perform the following steps:a) You transfer the Java export files to the central system target host. For more information,

see Transferring the Export Files to the Target Host [page 57].b) You install the database instance of the target system. For more information, see Installing

the Target System [page 58].4. On the central instance host, you install the central instance of the target system.5. If required, on (the) dialog instance host(s), you install additional dialog instance(s) as

described in the installation guide for your SAP system solution.

4.6.1 Transferring the Export Files to the Target Host

1. On the target host, create a directory <EXPDIR> with sufficient space for the database export filesavailable.

2. Copy all files and directories (recursively) that are located on the source host in the migrationexport directory <EXPDIR> from the source host to the target host.

Note

If you transfer the files with file transfer protocol (ftp), make sure that you use binary mode fortransferring the files.

3. Check the permissions of the transferred files on the target host. All files have to be accessible foruser <sapsid>adm of the target system.

03/12/2009 PUBLIC 57/168


Note

If your source system is a distributed system, the files created by the export of the central instanceand 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.If you have not exported into the same <EXPDIR> already, then you have to merge the two <EXPDIR>

directories from the central instance export and from the database instance export before startingthe target system installation.

4.6.2 Installing the Target System

Prerequisites


Make sure there is enough free space on the target system for the database load. To find out thesize of the export and the sizes of the tablespaces or dbspaces that will be created, look at the fileDBSIZE.XML located in the directory <DRIVE>:\<EXPDIR>\DB\<DATABASE>.End of: Windows


Make sure there is enough free space on the target system for the database load. To find out thesize of the export and the sizes of the tablespaces or dbspaces that will be created, look at the fileDBSIZE.XML located in the directory <EXPDIR>/DB/<DATABASE>.End of: UNIX

Note

As of SAP NetWeaver 7.0, RELOAD is no longer available as an executable installation service, but isperformed automatically by SAPinst. If the database software has already been unpacked or installed,or if the database already exists, SAPinst recognizes this automatically and skips the related steps.

Procedure

1. You prepare the target system host as described in the installation guide of your SAP solution basedon SAP NetWeaver 7.0 SR3.


Note

Make sure that you read the information provided in section Setup of Database Layout in theinstallation documentation.

End of: IBM DB2 for Linux and UNIX and Windows

58/168 PUBLIC 03/12/2009


2. You start SAPinst as described in the installation documentation for your SAP solution basedon SAP NetWeaver 7.0 SR3.

3. On theWelcome screen of the SAP Installation Master DVD, navigate to the following folderaccording to the requirements of your target system: Software Life-Cycle Options System Copy<database> Target System <Distribution option: Central System / Distributed System / High-AvailabilitySystem> Based on <Stack option> AS ABAP and Java / AS Java / AS ABAP> .

4. You run the installation service(s) required for your system copy in the sequence they are listed inthe specific folder and according to process flow in Setting Up the Target System Using SAPinst [page 56].

5. To install the target system, you follow the instructions in the SAPinst input dialogs and enter therequired parameters up to the screen Database - Select the Database Instance Installation Method.On this screen, you 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 isloaded in the newly installed SAP system database.


Caution

n Make sure that you take the information about automatic storage into consideration that isprovided in section Running SAPinst in the appropriate installation guide.

n The option Deferred Table Creation is not supported for load-based system copies for SAPsystems that are not based on SAP NetWeaver 7.0 SR3 or higher.

End of: IBM DB2 for Linux and UNIX and Windows

Caution

n Do not create the installation directory (for example, sapinst_instdir) under the followingdirectories:l UNIX: /usr/sap/<SAPSID>

Windows: \usr\sap\<SAPSID>l UNIX: /sapmnt/<SAPSID>

Windows: \sapmnt\<SAPSID>n If you perform a Unicode conversion, the data import into the target system might abort

because of missing space in the database tablespace or dbspace. Enlarge the database or databasecontainer, in which the table DYNPSOURCE will be created in the target database. The requiredsize for the table will be fifteen times larger than in the non-Unicode source system.

6. When SAPinst displays the DVD / CD browser window and asks for the Export Migration CD,enter the path to the export directory <EXPDIR>.

7. If you perform a heterogeneous system copy, enter the Migration Key on the screen Database Import.If you want to perform export and import in parallel, choose the option Parallel Export / Import.

03/12/2009 PUBLIC 59/168


Note

You must have run the service Prepare the Export on the source system [page 36], if you want to use theoption parallel export/ import for the installation of the target system.

8. Complete the installation as described in the installation documentation for your SAP component.

Note

If you have to restart the import after an error, just restart SAPinst. The import continues withthe table that was not imported successfully.For more information about restarting failed R3load processes, see Restarting R3load Processes[page 54].

Note

The Java engine is not started automatically. After the target system has been installed and thefollow-up activities (see Follow-Up Activities [page 103] have been performed, you have to start theJava engine manually.

60/168 PUBLIC 03/12/2009

5 Database-Specific System Copy


The following sections describe system copy procedures that base on database-specific methods.Database-specific methods are not available for all database systems. For more information aboutmethods available for your database, see Planning [page 13] and the SAP Notes describing thehomogeneous system copy for your database system.

Process

Follow the sequence of steps described in the process flows below for a:

n Central Systemn Distributed Systemn High Availability System

Central System

For performing the export for a central system, you need to proceed as follows on the central systemhost:

Process Flow on the Source System (Export)

When performing the export you create a MIGRATION EXPORT CD image, which contains the dataof the exported system, and which you use to install the target system.

1. You run SAPinst on UNIX or Windows [page 37] to create the export directory structure with labelsand to archive SDM and application-specific file system content.In SAPinst, choose the installation option that corresponds to your database, SAP system andtechnology (ABAP, Java or ABAP+Java).

Example

<your SAP version> Software Life-Cycle Options System Copy your database Source System ExportCentral System Based on AS ABAP and AS Java

If there is more than one option, you must carry out at least the mandatory steps for yourparticular system in the order in which they appear in SAPinst.

2. You generate the control file structure for the target database [page 65].3. If required, you create a backup of the source database [page 69].

03/12/2009 PUBLIC 61/168


Process Flow on the Target System

1.


You install the database software as described in the installation guide of your SAP solution.End of: Windows

2.


You prepare the target system [page 70]:a) Follow the instructions on the SAPinst screens until SAPinst requests you to install the database

software and to perform the database backup/restore.b) You create the database file system (if not yet existing).c) You install the database software.End of: UNIX

3.


Follow the instructions on the SAPinst screens until you are requested to perform the databasebackup/restore.

Note

If required, you have to restart SAPinst as described in the installation guide of your SAP solution.

End of: Windows

4. To complete the system copy, you have to perform the follow-up activities [page 103].

Distributed System or High Availability System

To perform the export for a distributed or high-availability system, proceed as follows:

Process Flow on the Source System (Export)

When performing the export you create a MIGRATION EXPORT CD image, which contains the dataof the exported system, and which you use to install the target system.

1. On the database instance host of the source system, you generate the control file structure for the targetdatabase [page 65].

2. If required, on the database instance host, you create a backup of the source database [page 69].3. On the central instance host, you run SAPinst on UNIX or Windows [page 37] to create the export

directory structure with labels and to archive SDM and application-specific file system content.In SAPinst, choose the installation option that corresponds to your database, SAP system andtechnology (ABAP, Java or ABAP+Java).

Example

<your SAP version> Software Life-Cycle Options System Copy your database Source System ExportCentral System Based on AS ABAP and AS Java

62/168 PUBLIC 03/12/2009

5 Database-Specific System Copy5.1 Oracle-Specific Procedure

If there is more than one option, you must carry out at least the mandatory steps for yourparticular system in the order in which they appear in SAPinst.

Example

a) Export Preparationb) Table Splitting Preparationc) Database and Central Instance Export

Process Flow on the Target System

1.


On the database instance host, you install the database software as described in the installationguide of your SAP solution.End of: Windows

2.


You prepare the target system [page 70]:a) On the database instance host, follow the instructions on the SAPinst screens until SAPinst

requests you to install the database software and to perform the database backup/restore.b) On the database instance host, you create the database file system (if not yet existing).c) On the database instance host, you install the database software.End of: UNIX

3.


On the database instance host, follow the instructions on the SAPinst screens until you arerequested to perform the database backup/restore.

Note

If required, you have to restart SAPinst as described in the installation guide of your SAP solution.

End of: Windows

4. To complete the system copy, you have to perform the follow-up activities [page 103].


5.1 Oracle-Specific Procedure

Purpose

In an SAP system environment, you can create a homogeneous copy of an Oracle database by copyingdatabase files. This method is suitable for creating an exact copy of an existing database. The source of

03/12/2009 PUBLIC 63/168


the copy is a complete data backup of your source database. You can use an offline backup, an onlinebackup, or the file system of your source host.You use SAPinst for the installation on the target system host as described in the installationdocumentation for your SAP component. Only the SAPinst steps for setting up and loading thedatabase content are different.

Advantages

n You can use existing offline or online backupsn This method is faster than the R3load and Jload method.

Disadvantages

n Backup/copy of database files in a heterogeneous environment is not possible because the hardwareof the source and target systems must be binary-compatible.

n Source system host and target system host must be different.n You must shut down the SAP system and the database when you create an offline backup

manually or an offline backup with BR*Tools.n You cannot change the database schema and the table space names.

Prerequisites

n You must use the same Oracle release and patch level for your database in the source and targetsystem.

n You must have prepared your system for SAPinst [page 24].n The ojdbc14.jarmust exist in the /ORACLE/client/10x_64/instantclient (installed using a

standard Oracle installation).n If your source system is an ABAP only system, make sure that JRE version 1.4.1 or higher is

installed on the database instance.n The JAVA_HOME environment variable must point the JRE directory.n The source and target systems must run on different hosts for security reasons.n The source and target systems must be binary compatible.

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.

If your source system uses the US7ASCII character set, you must choose this character set wheninstalling the target system. SAPinst prompts for the character set during the installation (key:Database Character Set). The installation default is WE8DEC or UTF8 for Unicode systems. To findout the character set used by the source system, connect to the source database as user sap<schemaid>or sapr3 with sqlplus and enter: SELECT * FROM V$NLS_PARAMETERS;

64/168 PUBLIC 03/12/2009



5.1.1 Generating the Control File Structure

The OraBRCopy Java tool writes a file CONTROL.SQL to the current working directory, which can beused without further adaptations on the target system.For more information about the OraBRCopy tool, see the documentation ORABRCopy.pdf, which ispart of the OraBRCOPY.SAR archive.

Prerequisites

Recommendation

We recommend that you shut down the SAP system before you perform the following steps. Thedatabase must still be running.

1. Create an installation directory <INSTDIR> (UNIX: with permissions 777) on the source system.2. Copy the ORABRCOPY.SAR archive from the SAP Installation Master DVD to the installation directory

and extract it using SAPCAR.You can find the archive in the following directory on the Installation Master DVD:


<DVD-DIR>:/COMMON/INSTALL/ORA/ORABRCOPY.SAR

End of: UNIX


<DVD-DIR>:\COMMON\INSTALL\ORA\ORABRCOPY.SAR

End of: Windows

3. Make sure that all redo log groups are archived.4. Start the OraBRCopy tool as an OS user with Oracle DBA privileges:

user ora<dbsid>user <sapsid>admn If you perform an offlinemanual copy, enter the following commands:l On UNIX:

./ora_br_copy.sh –generateFiles –forceLogSwitches —targetSid <TARGET_DBSID>

—password <system’s password> —listenerPort <listener port>

l On Windows:ora_br_copy.bat –generateFiles –forceLogSwitches —targetSid <TARGET_DBSID>

—password <system’s password> —listenerPort <listener port>

03/12/2009 PUBLIC 65/168


The tool creates the files CONTROL.SQL, CONTROL.TRC and init<targetSID>.ora in yourinstallation directory, shuts down and restarts the database and performs the required logswitches.

n If you perform an offline or online backup using BR*Tools, enter the following commands:l On UNIX:

./ora_br_copy.sh –generateFiles —targetSid <TARGET_DBSID> —password <system’s

password> —listenerPort <listener port>

l On Windows:ora_br_copy.bat –generateFiles —targetSid <TARGET_DBSID> —password <system’s

password> —listenerPort <listener port>

Note

During the online backup, the database must be up and running. To ensure this, thiscommand must not contain the parameter —forceLogSwitches.

The tool creates the files CONTROL.SQL, CONTROL.TRC and init<targetSID>.ora in yourinstallation directory, and performs the required log switches.

Note

If an error occurs, check the log file:<INSTDIR>/ora.brcopy.log

5. Verify and, if necessary, update the CONTROL.SQL control file using the CONTROL.TRC trace fileas follows.

Example for WindowsIn the following example for Windows, entries of CONTROL.SQL written in bold should be comparedto the trace file:REM

====================================================================

REM CONTROL.SQL

REM

REM SAP AG Walldorf

REM Systeme, 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

66/168 PUBLIC 03/12/2009


REM on

REM Windows 2000 5.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.DBF’,

’D:\ORACLE\NEW\MIRRLOGA\LOG_G11M2.DBF’

) SIZE 50M,

GROUP 2 (

’D:\ORACLE\NEW\ORIGLOGB\LOG_G12M1.DBF’,

’D:\ORACLE\NEW\MIRRLOGB\LOG_G12M2.DBF’

) SIZE 50M,

GROUP 3 (



) SIZE 50M,

GROUP 4 (

’D:\ORACLE\NEW\ORIGLOGB\LOG_G14M1.DBF’,

’D:\ORACLE\NEW\MIRRLOGB\LOG_G14M2.DBF’

) SIZE 50M

DATAFILE

’D:\ORACLE\NEW\SAPDATA1\SYSTEM_1\SYSTEM.DATA1’,

’D:\ORACLE\NEW\SAPDATA3\IMS_1\IMS.DATA1’,








03/12/2009 PUBLIC 67/168



’D:\ORACLE\NEW\SAPDATA1\IMS700_1\IMS700.DATA1’,











’D:\ORACLE\NEW\SAPDATA1\IMSUSR_1\IMSUSR.DATA1’,

’D:\ORACLE\NEW\SAPDATA2\ROLL_1\ROLL.DATA1’

;

ALTER DATABASE OPEN RESETLOGS;

ALTER TABLESPACE PSAPTEMP ADD TEMPFILE

’D:\ORACLE\NEW\SAPDATA3\TEMP_1\TEMP.DATA1’

SIZE 350M REUSE AUTOEXTEND OFF;

Note

In the above example for Windows, entries and values of control.sql written in bold should becompared to the trace file. The changes to be made are valid for UNIX, too.

Changes to be made

1. If you want to upgrade your database from 32-bit to 64-bit, add the following lines at the bottom ofthe control.sql file:shutdown immediate;

startup restrict

spool utlirp.log

@?/rdbms/admin/utlirp.sql

spool off

alter system disable restricted session;

2. MAXLOGFILES 255

...The numbers must be greater than or equal to the corresponding numbers in the trace file.

3. GROUP 1 (



) SIZE 50M,

68/168 PUBLIC 03/12/2009


Group 2 (

…The sizes of the respective groups must be equal to the sizes of the corresponding groups in thetrace file.

4. ’D:\ORACLE\NEW\SAPDATA1\SYSTEM_1\SYSTEM.DATA1’,


…’D:\ORACLE\NEW\SAPDATA1\IMS700_1\IMS700.DATA1’

…The count of the data files must be equal to the count of the corresponding data files in thetrace file.

5. ALTER TABLESPACE PSAPTEMP ADD TEMPFILE

’D:\ORACLE\NEW\SAPDATA3\TEMP_1\TEMP.DATA1’

SIZE 350M REUSE AUTOEXTEND OFF;

…The size must be equal to the corresponding size in the trace file.

6. The number of the rows with ALTER TABLESPACE must be equal to the number of thecorresponding rows in the trace file.

End of: Oracle


5.1.2 Creating a Backup

Create a backup if required. Choose between the following possibilities: Performing an offline backupmanually or an offline or online backup with BR*Tools.

n Offline backup manually [page 69]n Offline backup with BR*Tools [page 70]n Online backup with BR*Tools [page 70]


5.1.2.1 Creating an Offline Backup Manually

There are different possibilities to prepare the actual transfer of the database files:

n If you have an up-to-date offline backup, you can use it (provided that redo logs were cleaned upwith forced log switches).

n If you want to transport the database file (for example, on tape) or if you have to performthe database shutdown at a certain time, stop the database (normal shutdown) and perform

03/12/2009 PUBLIC 69/168


a complete offline backup. You can use the trace file CONTROL.TRC created by OraBrCOPY todetermine the file system trees that have to be saved.

n You stop the database (normal shutdown) and copy the database files when the actual transferto the target system takes place. You do not have to perform any preparations for the actualtransfer now. Proceed with the next step.

Note

If you choose this manual offline backup method, you also have to restore the database files onthe target system manually. For more information, see Restoring the Database Files on the Target SystemManually [page 73].End of: Oracle


5.1.2.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 oronline, with or without BACKINT, with or without RMAN, complete or incremental, and so on. Thebackup strategy must simply be valid for restore and recovery. This means that a complete restore andrecovery of the source database must be possible. For BACKINT and RMAN, the external backup toolsmust also be configured so that a restore is possible on the target host.For more information about BR*Tools, see help.sap.com/nw70 SAP NetWeaver 7.0 Library EnglishSAP NetWeaver Library Administrator’s Guide Technical Operations Manual for SAP NetWeaver General

Administration Tasks Database Administration Database Administration for Oracle BR*Tools for Oracle DBA

Note

If you choose a backup method with BR*Tools, you also have to restore the database files on thetarget system with BR*Tools. For more information, see Restoring the Database Files on the Target Systemwith BR*Tools [page 74].

End of: Oracle

End of: Oracle


5.1.3 Preparing the Target System

PrerequisitesMake sure that sapdata<n> file systems on the target system host are large enough.

70/168 PUBLIC 03/12/2009


Procedure

1. Install the target SAP system with SAPinst as described in the installation documentation foryour SAP solution.

Caution

On theWelcome screen, choose the required installation service:SAP NetWeaver 7.0 Support Release 2 Software Life-Cycle Options System Copy Oracle Target

System <Central System | Distributed System | High-Availability System> .

Caution

When you perform a system copy with the Oracle backup/restore method, you cannot changethe database schema and the table space names of the new target system. When installing thetarget central instance, database instance, or dialog instance make sure that you enter the correctdatabase schema names (which are the database schema name of the source system). The schemanames of the source and target system must be identical.

n When SAPinst prompts for the installation type, choose Homogeneous System Copy (Backup/Restore).n Proceed until SAPinst stops to restore the database files on the target system.

The following message is displayed:SAPinst now stops the installation. Please proceed as follows:...

2. If necessary, extract the Oracle stage archives manually and install the Oracle Software as describedin the installation documentation for your SAP solution.

3. If they do not exist, create the following directories on the target system:

03/12/2009 PUBLIC 71/168


n UNIX:

l /oracle/<TARGET_DBSID>/mirrlog<x>

l /oracle/<TARGET_DBSID>/origlog<x>

l /oracle/<TARGET_DBSID>/sapdata<x>

l /oracle/<TARGET_DBSID>/sapreorg

l /oracle/<TARGET_DBSID>/saparch

l /oracle/<TARGET_DBSID>/oraarch

l /oracle/<TARGET_DBSID>/saptrace

l /oracle/<TARGET_DBSID>/saptrace/background

l /oracle/<TARGET_DBSID>/saptrace/usertrace

l /oracle/<TARGET_DBSID>/origlogA/cntrl

l /oracle/<TARGET_DBSID>/sapdata1/cntrl

l /oracle/<TARGET_DBSID>/saparch/cntrl

l /oracle/<TARGET_DBSID>/sapcheck

n Windows:

l <drive>:\oracle\<TARGET_DBSID>\mirrlog<x>

l <drive>:\oracle\<TARGET_DBSID>\origlog<x>

l <drive>:\oracle\<TARGET_DBSID>\sapdata<x>

l <drive>:\oracle\<TARGET_DBSID>\sapreorg

l <drive>:\oracle\<TARGET_DBSID>\saparch

l <drive>:\oracle\<TARGET_DBSID>\oraarch

l <drive>:\oracle\<TARGET_DBSID>\saptrace

l <drive>:\oracle\<TARGET_DBSID>\saptrace\background

l <drive>:\oracle\<TARGET_DBSID>\saptrace\usertrace

l <drive>:\oracle\<TARGET_DBSID>\origlogA\cntrl

l <drive>:\oracle\<TARGET_DBSID>\sapdata1\cntrl

l <drive>:\oracle\<TARGET_DBSID>\saparch\cntrl

l <drive>:\oracle\<TARGET_DBSID>\sapcheck

4. 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

5.


All directories must be owned by the user ora<target_dbsid>.To achieve this, enter the following command:chown ora<target_dbsid>:dba<directory>

End of: UNIX

6. Set the security settings for the built-in accounts and groups SYSTEM, Administrators,

SAP_<SAPSID>_GlobalAdmin (domain installation), and SAP_<SAPSID>_LocalAdmin (localinstallation) for all directories as follows:a) In the Windows Explorer, right-click the Oracle root directory and choose Properties.b) Under Security, choose Advanced.

72/168 PUBLIC 03/12/2009


c) Uncheck Allow inheritable permissions from the parent....d) In the next dialog, choose Copy to copy the permission entries that were previously applied from

the parent to this object.e) Choose OK.f) Set the permissions for the above-mentioned accounts SYSTEM, Administrators,

SAP_<DBSID>_GlobalAdmin, or SAP_<DBSID>_LocalAdmin to Full Control.g) Delete all other accounts.

7. Restore the database files on the target system either manually (see Restoring the Database Files on theTarget System Manually [page 73]) or with BR*Tools (see Restoring the Database Files on the Target System withBR*Tools [page 74]), then proceed with SAPinst.

End of: Oracle


5.1.4 Restoring the Database Files on the Target SystemManually

Caution

If you do not use a backup but copy the database files directly from the source to the target systemhost, make sure that you shut down the database on the source system before you copy the listedfiles from the source to the target directories.

Procedure

1. Copy the following files from the source to the target system host by copying the listed files fromthe source directories to the target directories. For more information, see Creating an Offline BackupManually [page 69].Directories on UNIX:

Source and Target Directory Files

/oracle/<DBSID>/sapdata<x> All files

/oracle/<DBSID>/origlog<x> All files

/oracle/<DBSID>/mirrlog<x> All files

source: <INSTDIR>target: <SAPINST_INSTDIR>

CONTROL.SQL

source: <INSTDIR>target: /oracle/<DBSID>/<DB_VERSION>_<BIT>/dbs

init<TARGET_DBSID>.ora

Directories on Windows:

03/12/2009 PUBLIC 73/168



<drive>:\oracle\<DBSID>\sapdata<x> All files

<drive>:\oracle\<DBSID>\origlog<x> All files

<drive>:\oracle\<DBSID>\mirrlog<x> All files


CONTROL.SQL

source: <INSTDIR>target: \oracle\<DBSID>\<DB_VERSION>_<BIT>\database


Note

The installation directory of the target system is normally located in the directory:%programfiles%\sapinst_instdir\NW04S\LM\COPY\ORACLE\SYSTEM\<system_variant>

2. After you have copied the database files, make sure that the files on the source and target systemare not located in different directories or drives. If required, make the corresponding changes inthe files control.sql and the init<DBSID>.ora.

3. Verify that the created directories and copied files have the owner ora<target_dbsid>, belong tothe group dba, and have the permissions 740.

4. Make sure that the control files are not restored. If necessary, remove them.The file names are specified by the parameter control_files of the init<TARGET_DBSID>.ora file.

End of: Oracle


5.1.5 Restoring the Database Files on the Target System withBR*Tools

1. Copy the following files from the source system host to the target system host by copying the listedfiles from the source directories to the target directories manually.n On UNIX:



CONTROL.SQL

source: <INSTDIR>target:/oracle/<DBSID>/<DB_VERSION>_<BIT>/dbs


74/168 PUBLIC 03/12/2009

5 Database-Specific System Copy5.2 SAP MaxDB-Specific Procedure

n On Windows:



CONTROL.SQL

source: <INSTDIR>target: \oracle\<DBSID>\<DB_VERSION>_<BIT>\database


2. Create an Oracle spfile from init<TARGET_DBSID>.ora profile as follows:

Syntax

sqlplus /nologconnect / as sysdbacreate spfile from pfile;exit

3. Call the restore and recovery function of BR*Tools.For more information about the required steps and prerequisites, see SAP Note 1003028.The main prerequisite is that the corresponding BR*Tools logs (BRBACKUP detailed and summarylog, BRARCHIVE summary log) are copied manually from the source to the target system. Inaddition, the postprocessing steps mentioned in this SAP Note are performed automatically bySAPinst.SAP Note 1003028 also comprises information about executing restore and recovery under thecontrol of BRRECOVER and the exact syntax of BRRECOVER (see section Homogeneous Database Copy).For more information about BR*Tools, see help.sap.com/nw70 SAP NetWeaver 7.0 Library EnglishSAP NetWeaver Library Administrator’s Guide Technical Operations Manual for SAP NetWeaver

General Administration Tasks Database Administration Database Administration for Oracle BR*Tools forOracle DBA .

4. Shut down the Oracle database instance as follows:

Syntax

sqlplus /nologconnect / as sysdbashutdown immediateexit

End of: Oracle

End of: Oracle

03/12/2009 PUBLIC 75/168




Only valid for: MaxDB

5.2 SAP MaxDB-Specific Procedure

In an SAP system environment, you can create a homogeneous copy of a SAP MaxDB database byusing the backup and restore method. This method is suitable for creating an exact copy of an existingdatabase. The source of the copy is a complete data backup of your source database.The SAPinst tool is used for the installation on the target system host as described in the installationdocumentation for your SAP solution. In SAPinst you select the backup and restore method as thedatabase installation method. SAPinst stops before the database instance initialization and asks you toperform the recovery on the target database. After you have performed recovery and post-recoveryactivities you can continue the installation in SAPinst.This description is not valid for the liveCache system copy.

Advantage

n You can use existing offline backups.n This method is faster than the database-independent method using R3load or Jload [page 27].

Disadvantage

You can only copy between systems with the same byte order. For more information, see below.

Prerequisites

n Byte order ‒ little-endian or big-endianYou can use the backup and restore method to copy systems with the same byte order. That is,you can copy a system based on little-endian to another system based on little-endian. You canalso copy a system based on big-endian to another system based on big-endian. Check SAP Note552464 to find out which processor and operating system combination uses which byte order.

n Data backupYou perform the complete data backup of your source database.

n Recovery toolYou are using the SAP MaxDB Database Manager (DBMGUI) version 7.5.0 Build 12 or above.You can find more information on DBMGUI at either of the following:l http://dev.mysql.com/doc SAP MaxDB by MySQL SAP MaxDB Online Library Tools

l http://help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAPNetWeaver by Key Capability Databases SAP MaxDB Tools Database Manager GUI

n Database SoftwareThe database software on the target host must have the same version as the software on the sourcehost. The build number of the software version on the target host must be greater than or equalto the version on the source host.

76/168 PUBLIC 03/12/2009


http://dev.mysql.com/doc



n Size of the data on the target systemThe size of the target system must be greater than the used space on the source system. You canfind the size of the used pages on the source system as follows:dbmcli —d <database_name> —u <dbm_user>,<password> —n <database_server> —u SQL

sap<sid>,<password> sql_execute ’SELECT USEDPERM FROM SERVERDBSTATISTICS’

The result of this query is the amount of used space, expressed as the number of 8 KB pages. Toget the used space in MB, divide this value by 128. When SAPinst prompts you, configure thedatabase data volumes according to this value.

n JREYou must have installed JRE version 1.5 or higher on your system.The JAVA_HOME environment variable must point to the JRE directory.

Process

1. You do the following on the source system:a) If you do not already have a suitable recent complete SAP MaxDB backup, you create a

complete data backup using the DBMGUI tool:DBMGUI Backup Backup Wizard Complete

b) You make the backup medium available on the target host.

c)


Run SAPinst to perform the export for UNIX or Windows [page 37].End of: UNIX;Windows

2. You do the following on the target system:a) To install the new system you start SAPinst as follows:

SAP NetWeaver 7.0 Lifecyle Management System Copy SAP MaxDB Target System <CentralSystem | Distributed System | High-Availability System> .During the installation of the database instance, SAPinst stops before database initialization inthe screen Perform Database Recovery and asks you to perform the data recovery.

b) You start the data recovery wizard from DBMGUIA) You register your database instance in the DBMGUIB) You check the database instance in the admin state.C) You choose Recovery Recovery with Initialization ...D) In type of recovery you select Restore a medium.E) You specify the backup medium.F) You start the restore procedure.

Note

The recovery wizard does not start the recovery immediately. It initializes the databaseinstance first. It takes some time for the database server to format the database volumes.

03/12/2009 PUBLIC 77/168

5 Database-Specific System Copy5.3 MS SQL Server-Specific Procedure

c) After the restore, you check the state of the target database instance. Change the database stateto online if it is not already in online state.

d) You delete the entries from the following tables to make sure that information about thebackup history for update statistics in the Computing Center Management System (CCMS)from the old system does not appear in the new system:CNHIST, CNREPRT, CNMEDIA, DBSTATHADA, DBSTAIHADA, DBSTATIADA, DBSTATTADA,

SDBAADAUPD

e) You continue with SAPinst or restart it if you stopped it during the recovery.f) After installation is completed you maintain the database connection for CCMS. For more

information, see SAP Note 588515.

End of: MaxDB

Only valid for: Windows MS SQL Server

5.3 MS SQL Server-Specific Procedure

This section describes how to perform a homogeneous system copy of an MS SQL Server databaseby using the backup/restore method, or the detach/attach method in an SAP environment. TheSAPinst installation tool supports both methods.The backup/restore method and the detach/attach method have the following advantages comparedto the R3load method:

n You can use an existing backup.n These methods are much faster than the database-independent method [page 27].

Note

l For more information about the system copy procedure, see also SAP Notes 193816 and 151603.l With SQL Server, you can use backup images across the platforms I386, IA64, x64. That is, you

can make a backup on one type of platform and use it on another type.l You can only attach SQL Server 2000 files to SQL Server 2005 but not vice versa.

Process

1. On the source system, run SAPinst to create an export of the Java central instance [page 37] by choosing thefollowing installation service on theWelcome screen:<Your SAP system> Software Life-Cycle Options System Copy MS SQL Server Source System

<system variant> Based on <technical stack>

n For a central system, choose Database and Central Instance Export.

78/168 PUBLIC 03/12/2009




5 Database-Specific System Copy5.4 IBM DB2 for Linux, UNIX, and Windows Specific Procedures

Note

On the SAPinst screen SAP SystemDatabase Export, make sure to select Use database-specific tools forthe system copy method.

n For a distributed system, you choose Central Instance Export.When performing the export you create a MIGRATION EXPORT CD image, which contains thedata of the exported system, and which you use to install the target system.

2. Detach the database files from the source system database or create a backup and copy the filesto the target system.

3. Attach the database files or restore the backup of the source database on the target database server.4. Run SAPinst to install the target system by choosing the following on theWelcome screen:

<Your SAP system> Software Life-Cycle Options System Copy MS SQL Server Target System<system variant> <technical stack>

Note

n The target system is installed using the exports from the source system.

n Choose the installation services exactly in the order they appear. For moreinformation, see the MS SQL Server installation guide for your SAP system athttp://service.sap.com/installnw70.

n On the SAPinst screen SAP SystemDatabasemake sure to select Homogeneous System Copy (MS SQLServer-specific: Detach/Attach or Backup).

End of: Windows MS SQL Server


5.4 IBM DB2 for Linux, UNIX, and Windows SpecificProcedures

In an SAP system environment, you can create a homogeneous system copy of a DB2 database usingthe backup method or by relocating your database. The relocation of the database is usually used inconjunction with split mirror. For more information, see the documentation Database AdministrationGuide: SAP on IBM DB2 Universal Database for UNIX and Windows, section The db2inidb Tool and the DB2documentation.This section provides information on the backup method.SAPinst is used for the installation on the target system host as described in the installationdocumentation for your SAP component.In a Java or ABAP+Java system, you have to additionally run an export for the Java Engine to archiveSDM and application-specific file system content.

03/12/2009 PUBLIC 79/168

http://service.sap.com/installnw70


Advantages of the Backup Method

n You can use existing offline backups.n Using the backup method is faster than the database-independent method [page 27].

Disadvantages of the Backup Method

n You cannot change the database schema. The database schema will be the same as of the sourcesystem.

n You cannot copy an individual MCOD component to another system. You can only copy thecomplete system.

Prerequisites

n The source and target database systems should be binary compatible.

Note

With DB2, it is possible to use backup images cross platform for AIX, Solaris and HP-UX.

n If errors occur when restoring the backup on the target system, the complete restore must berepeated.

Process

1. You perform an offline backup or restore an existing backup copy.

Note

To export the database content for Java, you can also use the database-specific method(backup/restore).During the dialog phase, SAPinst asks you in the Database Export dialog box to specify the systemcopy method. If you want to use the backup/restore method, choose Use database-specific tools.

2. To create the export directory structure with labels and to archive SDM and application-specificfile system content, you additionally have to run SAPinst.On theWelcome screen, choose <Your SAP system> Software Life-Cycle Options System Copy IBMDB2 for Linux, UNIX, and Windows Source System <system variant> <technical stack> .Perform the installation options in the given sequence and follow the instructions on the SAPinstdialogs.

3. To create a target system, run SAPinst on the target system host by choosing the following on theWelcome screen:<Your SAP system> Software Life-Cycle Options System Copy IBM DB2 for Linux, UNIX, and

Windows Target System <system variant> <technical stack>Perform the installation options in the given sequence and follow the instructions on the SAPinstdialogs. During the installation phase SAPinst prompts you to perform the database restore.

80/168 PUBLIC 03/12/2009


Caution

Be aware of the following constraints when using the backup method for a homogeneous systemcopy:n You cannot change the connect user. 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.n The table space names remain the same during the database restore. However, you can change

them after the installation.n If you want to change the container names on the target system, you have to adapt the

container names in the redirected restore script and then perform a redirected restore. Formore information, see the documentation Database Administration Guide: SAP on IBM DB2 UniversalDatabase for UNIX and Windows, section Usage of Tool brdb6brt.

For the restore of your database, you can choose between one of the following options:n Simple database restore

To perform a database restore, use the DB2 restore command. For more information see theIBM DB2 documentation DB2 Command Reference.

n Redirected restoreTo perform a redirected restore, use the tool brdb6brt that retrieves a database backupand creates a CLP script for the restore of this backup image. For more information abouthow to use the tool brdb6brt, see the documentation Database Administration Guide: SAP onIBM DB2 Universal Database for UNIX and Windows section Usage of Tool brdb6brt and the IBM DB2documentation DB2 Command Reference.

4. Perform the database restore.If you have used an online backup, you have to make sure that you have access to the log filesthat were created during the online backup. You also have to perform a roll forward operationto bring the database into a consistent state.You can now continue with the installation.

5. If required, you can modify the table space names after the installation using the followingcommand:db2 rename tablespace <old name> to <new name>

Example

db2 rename tablespace <SAPSID_SOURCE>#STABD to <SAPSID_TARGET>#STABD

In addition, you have to update the table space names in tables TSDB6, IADB6 and TADB6 usingthe following commands:n For table TSDB6, enter the following SQL command:

update <connect_user_name>.tsdb6 set tabspace =

’<SAPSID_TARGET>#’||substr(tabspace,5,length(tabspace)-4),indspace=’<SAPSID_TARGET>#’||substr(indspace,5,length(indspace)-4)

n For table IADB6, enter the following SQL command:

03/12/2009 PUBLIC 81/168

5 Database-Specific System Copy5.5 IBM DB2 for i5/OS Procedure

update <connect_user_name>.iadb6 set tabspace =

’<SAPSID_TARGET>#’||substr(tabspace,5,length(tabspace)-4)

n For table TADB6, enter the following SQL command:update <connect_user_name>.tabdb6 set tabspace =

’<SAPSID_TARGET>#’||substr(tabspace,5,length(tabspace)-4)

More InformationIBM DB2 documentation DB2 Command ReferenceEnd of: IBM DB2 for Linux and UNIX and Windows

Only valid for: IBM DB2 for i5/OS

5.5 IBM DB2 for i5/OS Procedure

In an SAP system environment, you can create a homogeneous system copy of a DB2 database usingthe SAV/RSTLIB system copy method.

Advantage of the Offline System Copy Method

This method is faster than the database-independent method [page 27].For more information, see SAP Note 585277.

Caution

You can only copy for IBM DB2 for i5/OS.

End of: IBM DB2 for i5/OS


5.6 IBM DB2 for z/OS Specific Procedure

In an SAP system environment, you can create a homogeneous system copy of a DB2 database usingthe offline system copy method.This document assumes that the database schema of your SAP system is SAPR3. If you employ adifferent schema, adapt the references to SAPR3 in the following SQL statements and jobs to reflectthe actual schema name.The following section describes an offline system copy method for SAP systems on IBM DB2 forz/OS.For this example system copy, the high-level qualifier of the source system is assumed to be D8A0 ofthe target system D8B0.

82/168 PUBLIC 03/12/2009


5 Database-Specific System Copy5.6 IBM DB2 for z/OS Specific Procedure

Advantage of the Offline System Copy Method

This method is faster than the database-independent method [page 27].

Restriction of the Offline System Copy Method

At the moment, you cannot copy an individual MCOD component to another system. You can onlycopy the complete system.

Note

The offline system copy must be performed by an experienced database administrator.

You can find an adapted procedure for an online system copy in the IBM documentation HighAvailability for SAP on zSeries Using Autonomic Computing Technologies.

Prerequisites

The following prerequisites must be fulfilled to use this method:

n The permissions of the source and target systems must be completely separate. The source systemmust not be able to use the resources of the target system, and the target system must not beable to use the resources of the source system.

n RACF authorization for the target DB2 subsystem is complete.n Source and target systems must work with DB2 managed objects.n Table spaces are not partitioned.n The system copy is made from a nondata sharing system to a nondata sharing system.n Procedures of the source and the target system are defined in the DB2 PROCLIB.n Source and target systems have their appropriate entries in the APF list.n Volumes of the source and target systems are managed by SMS.n Source and target systems run with the same DB2 service level.

Variables Used in this Procedure

n Source System = D8A0

n Target System = D8B0

n Storage Group = TEMPORA

n High-Level Qualifier = HLQn Boot Strap Data Set = BSDS

Main Steps in this Procedure

The following sections contain the detailed steps involved in the homogeneous system copyprocedure for DB2 for z/OS.In the following steps, storage groups must be modified to apply the new high-level qualifier. Thiscan be achieved by dropping and re-creating the storage groups with the new high-level qualifier(and volumes).

03/12/2009 PUBLIC 83/168


To prepare the DB2 catalog of the target system, you must run JCL jobs created by SQLs runningin the source system.The offline system copy can be divided into the following steps:

1. Check the Source System for Consistency2. Stop and Restart the Source System3. Run SQLs in the Source System4. Capture View Definitions5. Stop the Source System6. Print the Bootstrap Data Sets7. Make Copies of the Source Data Sets8. Create the Target System9. Post-process the Target System10.Changing the VCAT of the Target System11. Changing the Schema of the Target System (DB2 V9 only)12.Adapting WLM Application Environments for DB2 Stored Procedures

JCL jobs and SQL Statements

The JCL jobs and SQL Statements are now located in a compressed file (.zip) that is attached toSAP Note 680746.The path for each file is given in the section that previously contained the code.

5.6.1 Step 1: Check Consistency

The following is a list to help you check the source system for consistency.

n Check if there are threads.

n Check for authorized utilities using the following:DISPLAY DATABASE(*) UTIL(*) and press [ENTER]

Your output should be:No authorized utility found.

If there are running utilities, you must shut them down properly before continuing.n Ensure that all DB2 objects of the source system are started RWmode.

This can be checked withDISPLAY DATABASE(*) SPACENAM(*)

with keywordRESTRICT.For more information, see DB2 UDB for z/OS and OS/390 Command Reference (SC26-9932-05).

n If there are no objects in pending status, the source system must be stopped.

84/168 PUBLIC 03/12/2009



5.6.2 Step 2: Stop and Restart the Source System

Now you must stop and restart the source system with the ACCESS (MAINT) command option toprohibit any authorization IDs other than install SYSADM and install SYSOPR.

5.6.3 Step 3: Run SQL Statements in the Source System

Prerequisites

As described earlier in this section, you must stop and restart the source system with theACCESS(MAINT) command option to prevent changes and to obtain consistent data.

Information for IBM DB2 V9 for z/OS

If you are running your system with DB2 V9, note that SQL Statements 2 through 9, as well as Creatinga New Storage Group Using the HLQ of the Target System are not relevant tasks for this procedure.

Activities

Execute all the following SQL statements in the source system:

5.6.3.1 SQL Statement Number 01

This statement is located atHSCProcedure\Step3\STMT01.SQL

in the .zip file [page 82] attached to SAP Note 680746. For more information, see the section JCLJobs and SQL Statements.With this statement, you identify user-defined indexes that you need to change in the DB2 catalog.For more information, see Step 8e: Changing the User-Defined Indexes in the DB2 Catalog [page 97].

Output

The output of this statement is similar to the following:

Example

---------+---------+---------+---------+---------+-----

NAME DBNAME INDEXSPACE

---------+---------+---------+---------+---------+-----

SYSTBLSP~0 DSNDB06 SYSTBLSP

SYSTABLE~0 DSNDB06 SYSTABLE

SYSIXPART~0 DSNDB06 SYSIXPAR

03/12/2009 PUBLIC 85/168





in the .zip file [page 82] attached to SAP Note 680746. For more information, see the section JCLJobs and SQL Statements.With this statement, you identify all databases that you want to stop at a later point in time in thetarget system:

Note

This task is not relevant for DB2 V9.

Output


Example

-STOP DATABASE (A000XAAA)

-STOP DATABASE (A000XAAB)

-STOP DATABASE (A000XAAC)

-STOP DATABASE (A000XAAD)

-STOP DATABASE (A000XAAE)

-STOP DATABASE (A000XAAF)

-STOP DATABASE (A000XAAG)

-STOP DATABASE (A000XAAH)

-STOP DATABASE (A000XAAI)

-STOP DATABASE (A000XAAJ)

-STOP DATABASE (A000XAAK)

-STOP DATABASE (A000XAAL)

.

.

.

etc.



86/168 PUBLIC 03/12/2009



in the .zip file [page 82] attached to SAP Note 680746. For more information, see the section JCLJobs and SQL Statements.With this statement, you identify all table spaces to be connected at a later point in time to thetemporary storage group TEMPORA:

Note


Output


Example

ALTER TABLESPACE A000XAAA.ABAPTREE USING STOGROUP TEMPORA; COMMIT;

ALTER TABLESPACE A000XAAA.ABAPTREE USING STOGROUP TEMPORA; COMMIT;

ALTER TABLESPACE A000XAAA.ADIRACCE USING STOGROUP TEMPORA; COMMIT;

ALTER TABLESPACE A000XAAA.ADOWNERR USING STOGROUP TEMPORA; COMMIT;

ALTER TABLESPACE A000XAAA.ADRCOMCS USING STOGROUP TEMPORA; COMMIT;

ALTER TABLESPACE A000XAAA.ADRDIFIN USING STOGROUP TEMPORA; COMMIT;

ALTER TABLESPACE A000XAAA.ADRGS2 USING STOGROUP TEMPORA; COMMIT;

ALTER TABLESPACE A000XAAA.ADR10 USING STOGROUP TEMPORA; COMMIT;



in the .zip file [page 82] attached to SAP Note 680746. For more information, see the section JCLJobs and SQL Statements.With this statement, you identify all indexes to be connected with storage group TEMPORA.

Note


Output


03/12/2009 PUBLIC 87/168




Example

ALTER INDEX "DSNACC"."UTLEX01" USING STOGROUP TEMPORA; COMMIT;

ALTER INDEX "DSNACC"."UTLSTX01" USING STOGROUP TEMPORA; COMMIT;

ALTER INDEX "DSNACC"."UTPEBX01" USING STOGROUP TEMPORA; COMMIT;

ALTER INDEX "DSNACC"."UTPETX01" USING STOGROUP TEMPORA; COMMIT;

ALTER INDEX "DSNACC"."UTPEX01" USING STOGROUP TEMPORA; COMMIT;

ALTER INDEX "DSNACC"."UTPRCX01" USING STOGROUP TEMPORA; COMMIT;

ALTER INDEX "DSNACC"."UTRESTARTX" USING STOGROUP TEMPORA; COMMIT;

ALTER INDEX "DSNACC"."UTRESTART2X" USING STOGROUP TEMPORA; COMMIT;

ALTER INDEX "DSNACC"."UTTMDX01" USING STOGROUP TEMPORA; COMMIT;

ALTER INDEX "DSNACC"."UTTMPX01" USING STOGROUP TEMPORA; COMMIT;

.

.

etc.



in the .zip file [page 82] attached to SAP Note 680746. For more information, see the section JCLJobs and SQL Statements.Storage groups in the target system still contain the high-level qualifier of the source system. Withthis statement, you identify storage groups to be dropped at a later point in time with the followingstatement:

Note


Output


88/168 PUBLIC 03/12/2009



Example

DROP STOGROUP SYSDEFLT; COMMIT;

DROP STOGROUP SAPU1I; COMMIT;

DROP STOGROUP SAPU1D; COMMIT;

DROP STOGROUP SAPSOI; COMMIT;

DROP STOGROUP SAPSOD; COMMIT;

DROP STOGROUP SAPESI; COMMIT;

DROP STOGROUP SAPESD; COMMIT;

DROP STOGROUP SAPPRI; COMMIT;

DROP STOGROUP SAPPRD; COMMIT;

DROP STOGROUP SAPLOI; COMMIT;

.

.

etc.



in the .zip file [page 82] attached to SAP Note 680746. For more information, see the section JCLJobs and SQL Statements.

Note


With this statement, you identify storage groups to be created at a later point in time with thehigh-level qualifier of the target system. In this case, we assume that FR01 is the high-level qualifierof the target system.

Storage Group Naming Conventions

Some storage group names may have to be adapted for all storage groups for which the creator is yourSQLID and not SAPR3. The naming convention is as follows:

ABAP Storage Group Naming Convention

Schema Storagegroup Name

SAPR3 SAP<SI><I|D>

other <SID><SI><I|D>

03/12/2009 PUBLIC 89/168



Note

<SI> signifies the two-character STORAGEID of the table type (TABART).

Java Storage Group Naming Convention

Schema Storage Group Name

<schema> <schema>

Caution

For Java, the schema name is also the name of the storage group. You must not change the name ofthe storage group. Be aware that as ofDB2 V9, you can use the CATMAINT utility to globally switcha schema name.

Output


Example

CREATE STOGROUP SYSDEFLT VOLUMES(’*’) VCAT FR01; COMMIT;; COMMIT;

CREATE STOGROUP SAPU1I VOLUMES(’*’) VCAT FR01; COMMIT;; COMMIT;

CREATE STOGROUP SAPU1D VOLUMES(’*’) VCAT FR01; COMMIT;; COMMIT;

CREATE STOGROUP SAPSOI VOLUMES(’*’) VCAT FR01; COMMIT;; COMMIT;

CREATE STOGROUP SAPSOD VOLUMES(’*’) VCAT FR01; COMMIT;; COMMIT;

CREATE STOGROUP SAPESI VOLUMES(’*’) VCAT FR01; COMMIT;; COMMIT;

CREATE STOGROUP SAPESD VOLUMES(’*’) VCAT FR01; COMMIT;; COMMIT;

CREATE STOGROUP SAPPRI VOLUMES(’*’) VCAT FR01; COMMIT;; COMMIT;

CREATE STOGROUP SAPPRD VOLUMES(’*’) VCAT FR01; COMMIT;; COMMIT;

CREATE STOGROUP SAPLOI VOLUMES(’*’) VCAT FR01; COMMIT;; COMMIT;

CREATE STOGROUP SAPLOI VOLUMES(’*’) VCAT FR01; COMMIT;; COMMIT;

CREATE STOGROUP SAPLOD VOLUMES(’*’) VCAT FR01; COMMIT;; COMMIT;

.

.

etc.




90/168 PUBLIC 03/12/2009



With this statement, you connect table spaces with their previous storage groups, which now containthe high-level qualifier of the target system.

Note


Output


Example

ALTER TABLESPACE "DSNRLST"."DSNRLS01" USING STOGROUP SYSDEFLT;COMMIT;

ALTER TABLESPACE "BCXXXC5E"."SYNCLOG" USING STOGROUP SAPD7DDB;COMMIT;

ALTER TABLESPACE "BCXXXC5E"."DDDBRTH" USING STOGROUP SAPD7DDB;COMMIT;

ALTER TABLESPACE "BCXXX3UT"."DDDBTAB" USING STOGROUP SAPD7DDB;COMMIT;

ALTER TABLESPACE "BCXXX3UT"."LDDDBT3U" USING STOGROUP SAPD7DDB;COMMIT;

ALTER TABLESPACE "BCXXX3UT"."DDDBRTX" USING STOGROUP SAPD7DDB;COMMIT;

ALTER TABLESPACE "BCXXXC5E"."JMSDMSG" USING STOGROUP SAPD7DDB;COMMIT;

ALTER TABLESPACE "CC390"."UTTEMPL" USING STOGROUP SYSDEFLT;COMMIT;

ALTER TABLESPACE "CC390"."UTPROC" USING STOGROUP SYSDEFLT;COMMIT;

ALTER TABLESPACE "CC390"."UTRSTRT" USING STOGROUP SYSDEFLT;COMMIT;

.

.

etc.



in the .zip file [page 82] attached to SAP Note 680746. For more information, see the section JCLJobs and SQL Statements.With this statement, you connect indexes with their previous storage groups, which now contain thehigh-level qualifier of the target system.

Note


Output


03/12/2009 PUBLIC 91/168



Example

ALTER INDEX "SAPD5Z"."SYSTBLSPß0" USING STOGROUP SYSDEFLT;COMMIT;

ALTER INDEX "SAPD5Z"."SYSTABLEß0" USING STOGROUP SYSDEFLT;COMMIT;

ALTER INDEX "SAPD5Z"."SYSIXPARTß0" USING STOGROUP SYSDEFLT;COMMIT;

ALTER INDEX "STEM"."DSNARL01" USING STOGROUP SYSDEFLT;COMMIT;

.

.

etc.



in the .zip file [page 82] attached to SAP Note 680746. For more information, see the section JCLJobs and SQL Statements.With this statement, you identify all databases to be started after DB2 catalog manipulations.

Note


Output


Example

-START DATABASE (A000XAAA)

-START DATABASE (A000XAAB)

-START DATABASE (A000XAAC)

-START DATABASE (A000XAAD)

-START DATABASE (A000XAAE)

-START DATABASE (A000XAAF)

-START DATABASE (A000XAAG)

-START DATABASE (A000XAAH)

-START DATABASE (A000XAAI)

-START DATABASE (A000XAAJ)

-START DATABASE (A000XAAK)

-START DATABASE (A000XAAL)

.

.

etc.

92/168 PUBLIC 03/12/2009



5.6.4 Step 4: Capturing View Definitions with DB2 V9 (if theSchema Name is to be Changed)

DB2 V9 adds the capability to change the VCAT name to the CATMAINT utility. This new capabilityfacilitates homogenous system copy. Moreover, the CATMAINT utility can change the schema andcreator of objects.If you intend to also change the schema name as part of the homogeneous system copy, for examplefor SAP Java systems, you need to capture the view definitions in this step. This is necessary sincerenaming the schema using CATMAINT requires that no views exist on the tables for which a VCAT nameis changed. Therefore, the view definitions are exported in this step using R3ldctl.As part of the post-processing steps that are performed in the target system, the saved view definitionsare later used to re-create the views in the target system. The views may also be saved and laterre-created in the target system using alternative tools.

ProcedureTo export the view definitions using R3ldctl:

1. Run R3ldctl without parameters to create the DDLDB2.TPL file, the SAPVIEW.STR file and others2. Store these files

5.6.5 Step 5: Stop the Source System

Stop the source system with the following command option:MODE (QUIESCE)

5.6.6 Step 6: Making Copies of Source Data Sets

With this step, you make copies of the source data sets, which includes:

n DB2 bootstrap data setsn DB2 logcopy data setsn All DB2 VSAM data sets belonging to the source system

With these JCL jobs, you can make copies of the source data sets:

03/12/2009 PUBLIC 93/168


n HSCProcedure\Step6\DUMPA0.JCL



n HSCProcedure\Step6\DUMPLIB.JCL

n HSCProcedure\Step6\DUMPLOG.JCL

n HSCProcedure\Step6\DUMPREST.JCL

All scripts are located in the .zip file [page 82] attached to SAP Note 680746. For more information, seethe section JCL Jobs and SQL Statements.

Note

The source system can be restarted now. It is no longer needed for the following system copy process.

5.6.7 Step 7: Creating the Target System

With the following JCL jobs, you create the target system.In the first step, the dumps of the source system have to be restored. All data sets of the source systemhave to be restored with the high-level qualifier of the target system.All statements are located in the .zip file [page 82] attached to SAP Note 680746. For more information,see the section JCL Jobs and SQL Statements.

n HSCProcedure\Step7\RSTOREA0.JCL



n HSCProcedure\Step7\RSTORELI.JCL

n HSCProcedure\Step7\RSTORELO.JCL

n HSCProcedure\Step7\RSTORERE.JCL

5.6.8 Step 8: Printing the Bootstrap Data Sets

Prerequisites

The source system must be stopped at this point.

Statement

This JCL job is located atHSCProcedure\Step8\PROLOGMAP.JCL

in the .zip file [page 82] attached to SAP Note 680746. For more information, see the section JCLJobs and SQL Statements.With this statement, you print the bootstrap data sets. You can use the output of this statement tomanipulate the bootstrap data sets in the target system.

94/168 PUBLIC 03/12/2009





Output


Syntax

.

.

.GROUP NAME: ........BSDS COPY 1 DATA SET NAME:

............................................BSDS COPY 2 DATA SET NAME:

............................................ENFM START RBA/LRSN: 000000000000

ACTIVE LOG COPY 1 DATA SETSSTART RBA/TIME END RBA/TIME DATE LTIMEDATA SET INFORMATION

-------------------- -------------------- -------- -------------------------0034A0468000 0034AC7DFFFF 2003.106 12:12DSN=D8A0.LOGCOPY1.DS01

2004.163 18:31:44.4 2004.163 20:14:45.7 PASSWORD=(NULL)STATUS=REUSABLE0034AC7E0000 0034B8B57FFF 2003.106 12:12DSN=D8A0.LOGCOPY1.DS02

2004.163 20:14:45.7 2004.163 20:37:23.1 PASSWORD=(NULL)STATUS=REUSABLE0034B8B58000 0034C4ECFFFF 2003.106 12:12DSN=D8A0.LOGCOPY1.DS03

2004.163 20:37:23.1 ........ .......... PASSWORD=(NULL)STATUS=REUSABLEARCHIVE LOG COPY 1 DATA SETSNO ARCHIVE DATA SETS DEFINED FOR THIS COPYACTIVE LOG COPY 2 DATA SETSNO ACTIVE DATA SETS DEFINED FOR THIS COPYARCHIVE LOG COPY 2 DATA SETSNO ARCHIVE DATA SETS DEFINED FOR THIS COPY

.

.

.etc.

5.6.9 Step 9a: Changing the Bootstrap Data Sets (BSDS)

Before starting the target system, the BSDS must be changed.The JCL jobs listed here are located in the .zip file [page 82] attached to SAP Note 680746. For moreinformation, see the section JCL Jobs and SQL Statements.

1. Change the HLQ entry in the BSDS of the target system, using the HLQ D8B0.The corresponding JCL job is located atHSCProcedure\Step9a\CHGBSDS1.JCL

in the .zip file.2. Change the log entries in the BSDS. The START and END RBA information as of utility DSNJU004

have to be used for the target system as follows:The corresponding JCL job is located atHSCProcedure\Step9a\CHGBSDS2.JCL

03/12/2009 PUBLIC 95/168



in the .zip file.

After changing the BSDS with these scripts, you can start the target system.

5.6.10 Step 9b: Start the Target System

When you start the DB2 target system for the very first time, the system is still working with thework file database of the source system. However, access fails with insufficient access authority, asseen in the log.Partial example of a LOG when you start the target system for the first time:

Syntax

.

.

.

.DSNR005I -D8B0 RESTART...COUNTS AFTER FORWARD 604RECOVERYIN COMMIT=0, INDOUBT=0DSNR006I -D8B0 RESTART...COUNTS AFTER BACKWARD 605RECOVERYINFLIGHT=0, IN ABORT=0, POSTPONED ABORT=0DSNP012I -D8B0 DSNPCNP0 - ERROR IN VSAM CATALOG 606LOCATE FUNCTION FOR D8A0.DSNDBC.DSNDB07.DSN4K01.I0001.A001

CTLGRC=AAAAAA08CTLGRSN=AAAAAA08CONNECTION-ID=D8E0, CORRELATION-ID=003.RCRSC 02,LUW-ID=*

IKJ56228I DATA SET D8A0.DSNDBC.DSNDB07.DSN4K01.I0001.A001NOT IN CATALOGOR CATALOG CAN NOT BE ACCESSEDDSNB207I -D8B0 DYNAMIC ALLOCATION OF DATA SET 608FAILED. REASON=17080002.DSNAME=D8A0.DSNDBC.DSNDB07.DSN4K01.I0001.A001DSNT501I -D8B0 DSNITFFS RESOURCE UNAVAILABLE 609

CORRELATION-ID=D8E0CONNECTION-ID=D8E0LUW-ID=D8E0.D8E0.000000000000=0REASON 00D70024

.

.

.

.etc.

We strongly recommend that you maintain different RACF settings for different DB2 subsystems.If not, the target system has access to the data sets of the source system and the data of the sourcesystem could be changed by mistake.The work file database data must be changed later in the clone process.

96/168 PUBLIC 03/12/2009


5.6.11 Step 9c: Creating a New STOGROUP Using the HLQ ofthe Target System

With this JCL job, you create a new STOGROUP using the HLQ of the target system (D8B0).This JCL job is located atHSCProcedure\Step9c\CRTMPSTO.JCL

.zip file [page 82] attached to SAP Note 680746. For more information, see the section JCL Jobs andSQL Statements.

Note


5.6.12 Step 9d: Stopping Index Spaces

With this JCL job, you stop the appropriate index spaces.You find a list of index spaces in the output of SQL statement number 1 [page 85].The JCL job is located atHSCProcedure\Step9d\STOPIDXS.JCL


5.6.13 Step 9e: Changing the User-Defined Indexes in theDB2 Catalog

After starting the target system, the user-defined indexes (the output of SQL statement number 1 [page85]) in the DB2 catalog must be changed, working with the new HLQ of the target system D8B0. Thefollowing example script can be used to carry out this procedure.Change the user-defined DB2 catalog indexes using the new storage group TEMPORA.This JCL job is located atHSCProcedure\Step9e\ALTERIDX.JCL


5.6.14 Step 9f: Restart the Index Spaces

At this point, you must restart the index spaces.

03/12/2009 PUBLIC 97/168





5.6.15 Step 9g: Creating the Temporary Files for the DB2Target System

To create the temporary files for the DB2 target system:

1. Run part of DSNTIJTM to create temporary files for DB2. DSNTIJTM was generated by DSNTINST(optional) or consists of a manually changed copy from another existing DB2 subsystem.The JCL job is located in the .zip file atHSCProcedure\Step9g\CRTTMPFL.JCL.The .zip file [page 82] attached to SAP Note 680746. For more information, see the section JCLJobs and SQL Statements.

2. Stop and restart the DB2 subsystem. The error as described in Step 6: Make Copies of the Sources Data Sets[page 93] should not occur since DB2 is working with the new temporary files.

5.6.16 Step 9h: Implementing HLQ of the Target System inthe Work File Database

In the next step, the work file database is changed to use the new HLQ D8B0.

ProcedureTo change the work file database:

1. Drop work file database DSNDB07 in the target system, delete the clusters for 4K and 32K andcreate them again.

2. Stop and restart the target system.Error message IKJ56228I should not appear because DB2 is now working with its own work filedatabase.

5.6.17 Step 9i: Adjusting the DDF Location Name and PortNumber

To allow communication with the SAP Application Servers of the DB2 target system, you mustadjust the DDF location name and port number.

ProcedureTo adjust the DDF location name and port number, run the DB2 utility DSNJU003with the option DDF

to specify the location name and port number.

98/168 PUBLIC 03/12/2009



5.6.18 Step 10 (DB2 V8 and Lower): Changing the VCAT ofthe Target System

The target system with the new HLQ D8B0 still works with storage groups using VCAT D8A0.In the following steps, the DB2 catalog is manipulated by stopping the databases, altering table-spacesand indexes, dropping and creating storage groups with the new VCAT D8B0, altering table-spaces andindexes using the new storage groups, and starting all databases.The objects to be manipulated are identified by the results of previously described SQL statements.All SQL statements listed here are located in the.zip file [page 82] attached to SAP Note 680746. Formore information, see the section JCL Jobs and SQL Statements.

Procedure

1. Stop all databasesThe corresponding JCL job is located atHSCProcedure\Step10\STOPDBS.JCL.

2. Alter table spaces using storage group TEMPORA

The corresponding JCL job is located atHSCProcedure\Step10\ALTERTBS.JCL.

3. Alter indexes using storage group TEMPORA

The corresponding JCL job is located atHSCProcedure\Step10\ALTERIDX.JCL.

4. Drop the storage groupsThe corresponding JCL job is located atHSCProcedure\Step10\DROPSTG.JCL.

5. Create the storage groupsThe corresponding JCL job is located atHSCProcedure\Step10\CREATSTG.JCL.

6. Alter table spaces using their previous storage groupThe corresponding JCL job is located atHSCProcedure\Step10\ALTERTB2.JCL.

7. Alter indexes using their previous storage groupThe corresponding JCL job is located atHSCProcedure\Step10\ALTERID2.JCL.

8. Start all databasesThis JCL job is located atHSCProcedure\Step10\STARTDBS.JCL.

If necessary, change the user authorizations of the target system. The DB2 catalog still contains theauthorizations of the source system.

03/12/2009 PUBLIC 99/168



5.6.19 Step 10 (DB2 V9): Changing the VCAT of the TargetSystem

To change the VCAT that is used for the storage groups of your SAP tables and indexes, proceedas follows.

Procedure

1. Ensure that the DB2 EMD pool and DB2 EDM DBD cache have at least the following sizes:

n EDMPOOL ≥ 200000 KB

n EDMDBDC ≥ 300000 KB

2. Call the CATMAINT utility with the UPDATE VCAT option to switch the VCAT name3. Reinstate the original sizes of EDMPOOL and EDMDBDC.4. Start the DB2 subsystem in regular mode5. If the schema of the SAP source system is not SAPR3 and if you do not intend to change the schema

name, create a new DB2 stogroup for each existing stogroup. These new stogroups reflect the SAPsystem ID of the new SAP system instead of the SAP system ID of the source SAP system.To create the stogroups, submit the following statement:CREATE STOGROUP <stogroup_name> VOLUMES (*) VCAT <vcat_name>

where <vcat_name> is the VCAT name of the new DB2 subsystem.

Example

If an existing stogroup name is OLDDID and if the SAP system IDs of the source and target systemsare OLD and NEW, respectively, then a new stogroup needs to be created with the name NEWDID.

The existing stogroups in the DB2 target system, which reflect the SAP system ID of the sourcesystem, do not need to be changed and are still used by the existing database objects of the new SAPsystem. As these names are only used internally in DB2, they do not interfere with the stogroups ofthe DB2 source system.For details on the SAP exploitation of DB2 stogroups, see the SAP DBA Guide: DB2 for z/OS, sectionAdditional Information.If necessary, change the user authorizations of the target system. The DB2 catalog still contains theauthorizations of the source system.

5.6.20 Step 11 (DB2 V9): Changing the Schema of the TargetSystem

To change the schema or creator name of your SAP tables and indexes, proceed as follows. Thisapproach requires that you have previously invoked R3ldctl on your source system to capture theview definitions of the SAP system.

100/168 PUBLIC 03/12/2009


Procedure

1. If user-defined materialized query tables or triggers exist, save their definitions in a separate place2. Delete all views, materialized query tables and triggers that exist on the SAP tables3. Ensure that the DB2 EMD pool and DB2 EDM DBD cache have at least the following sizes:

n EDMPOOL ≥ 200000 KB

n EDMDBDC ≥ 300000 KB

4. Call the CATMAINT utility with the SCHEMA SWITCH option to switch the schema name5. Reinstate the original sizes of EDMPOOL and EDMDBDC.6. Start the DB2 subsystem in regular mode7. Create a new DB2 stogroup for each existing stogroup. These new stogroups reflect the SAP system

ID of the new SAP system instead of the SAP system ID of the source SAP system.To create the stogroups, submit the following statement:CREATE STOGROUP <stogroup_name> VOLUMES (*) VCAT <vcat_name>

where <vcat_name> is the VCAT name of the new DB2 subsystem.

Example

If an existing stogroup name is OLDDID and if the SAP system IDs of the source and target systemsare OLD and NEW, respectively, then a new stogroup needs to be created with the name NEWDID.

8. Re-create the views by implementing the following steps:a) Generate the R3load task files by submitting the following command:

R3load -ctf I SAPVIEW.STR DDLDB2.TPL SAPVIEW.TSK DB2 -l SAPVIEW.log

b) Create an SAPVIEW.cmd file to prepare the recreation of the views. This file can contain thefollowing lines for example:

Example

tsk: "SAPVIEW.TSK"

icf: "SAPVIEW.STR"

dcf: "DDLDB2.TPL"

dat: null

dir: null

ext: null

c) Call R3load with the option-i SAPVIEW.cmd -dbcodepage <codepage> -l SAPVIEW.log

to re-create the views.9. If user-defined materialized query tables or triggers exist, re-create them.

03/12/2009 PUBLIC 101/168


5.6.21 Step 12: Adapting WLM Application Environments forDB2 Stored Procedures

The WLM environments of the WLM-established stored procedures need to be changed if the targetsystem is running with other WLM environments.

ProcedureTo change the WLM environments of the WLM-established stored procedures, carry out the followingsteps:

1. Create WLM application environments for the DB2 stored procedures as described in the SAPDBA Guide: DB2 for z/OS.

2. Use the ALTER PROCEDURE statement as described in the IBM documentation DB2 for z/OS SQLReference.

End of: IBM DB2 for z/OS

102/168 PUBLIC 03/12/2009

6 Follow-Up Activities

6 Follow-Up Activities

To finish the system copy of your SAP system:

n Perform follow-up activities in the source system [page 103]n Perform follow-up activities in the target system [page 103]

Note

The Java engine is not started automatically. After the target system has been installed and thefollow-up activities have been performed, you have to start the Java engine manually.

6.1 Performing Follow-Up Activities in the Source System

1. Reschedule your canceled jobs: Tools CCMS Jobs Maintenance (SM37) .2. Using CCMS, adapt your operation mode timetable to the original status: Tools CCMS

Configuration Operation mode calendar (SM63) .

6.2 Performing Follow-Up Activities in the Target System

Note

Before you start the Java engine after the system copy, apply SAP Note 831812 and change the JavaVM parameters, if necessary.

6.2.1 Installing the License Key

Once the installation of the target system is completed and the SAP system copy has been imported,you have to install a new license key. For more information about ordering and installing the SAPlicense, seehttp://help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP

NetWeaver by Key Capability Solution Life Cycle Management SAP Licenses

03/12/2009 PUBLIC 103/168



6 Follow-Up Activities6.2 Performing Follow-Up Activities in the Target System

6.2.2 Performing Follow-Up Activities for ABAP

Actions at Operating System Level

1. Adapt the configuration files at operating system level to meet network and SAP requirements.2. Adapt additional SAP software components (for example, RFC, CPIC, SAP ArchiveLink) if required.3. Adapt additional non-SAP software components (for example, archiving systems, monitoring

tools, job schedulers) if required.4. Adapt backup programs (for example BRBACKUP, BRARCHIVE, BACKINT) if required.5. Adapt non-SAP directories, file systems, NFS mounts, and so on if required.6. Check the SAP parameters of the default and instance profiles.7. Check your UNIX shell files for special entries.8. Check crontab or AT jobs.9. Check operating system files (for example, .netrc, .rhosts).10. Check operating system printers.11. Oracle: Adapt the database profiles init<SAPSID>.ora, init<SAPSID>.dba and

init<SAPSID>.sap.

Actions at Database Level

1. Before starting the SAP system, make sure that the logging mechanism of the database is active.2. Check the parameters in the database profiles.3. Oracle: Delete all entries from the following tables:

DBSTATHORA, DBSTAIHORA, DBSTATIORA, DBSTATTORA.

4. Oracle: Delete the user OPS$<SOURCE_SAPSID>ADM.5. Oracle: If you changed the <DBSID> during the system copy, we recommend that you adapt the

global_name parameter with the following SQL command:alter database rename global_name to <NEW_DBSID>;

If the parameter does not exist on your system, ignore this step.

Actions at SAP System Level

1. Run an installation check: Administration System administration Administration Installation Check(transaction SM28).

2. Configure the Transport Management System (transaction STMS). If you did not change theSAPSID during the system copy, all open transport, repair and customizing requests that have notbeen released in the source system, will not be released automatically.

3. Adapt the transport parameters and transport routes in the Transport Management System(TMS): a.a) Choose transaction STMS Overview Systems .b) Select the system and select the tab Transporttool.To adapt the transport routes:

104/168 PUBLIC 03/12/2009


Choose transaction STMS Overview Transport routes .4. Delete all entries from the following tables: ALCONSEG, ALSYSTEMS, DBSNP, MONI, OSMON, PAHI,

SDBAD, SDBAH, SDBAP, SDBAR.5. Delete canceled and finished jobs.

Execute ABAP program RSBTCDEL, marking the field delete with forced mode: Tools ABAPWorkbench ABAP Editor (transaction SE38).

6. Adapt all jobs needed in the target system:a) Copy the old jobs.b) Modify the new jobs.c) Delete the old jobs.

7. Check the consistency of the Temporary Sequential Objects (TemSe) by searching for files of TemSeobjects for which no TemSe objects exist:Administration CCMS Spool TemSe administration (transaction SP12). For more information,

see SAP Note 16875.8. Adapt the definition of the printers to meet the new system requirements:n Device types and character set definitionsn Spool serversn Output management systems (OMS)

9. Delete entries in table DDLOG for buffer synchronization.10. Synchronize the buffers as described in SAP Note 36283 and adapt the client information for the

logical system.11. Adapt the RFC destination: Tools Administration Administration Network RFC destinations

(transaction SM59).12. If you have performed a system copy with R3load, you must set up the trusted and trusting RFC

relationships again.13. Clean the transactional RFC: Tools Administration Monitor Transactional RFC (transaction

SM58). For more information, see the relevant description in the SAP Online Documentation.14. Start transaction SECSTORE using Check Entries. If you find erroneous entries with message text

System-dependent data for entry … changed , see SAP Note 816861.15. Create new operation modes and remove old ones:

a) Create new operation modes and instance definitions.b) Maintain the timetable using the new operation modes.c) Delete the old operation modes and old instance definitions.

16. Adapt the operation mode time tables (CCMS): Administration CCMS Configuration Operationmode calendar (transaction SM63).

17. Adapt the instances and profiles (CCMS): Administration CCMS Configuration OP modes/instances(transaction RZ04).

18. Define or remove the SAP system users: Tools Administration User maintenance Users(transaction SU01). Also revise the authorizations of the system users.

03/12/2009 PUBLIC 105/168





19. Run transaction SE14 to delete all entries from tables TPFET and TPFHT. These contain informationabout changes made to the profile of your source system.IBM DB2 for i5/OS: Use the commands CLRPFM R3<SID>DATA/TPFET and CLRPFM

R3<SID>DATA/TPFHT.20. Adapt other CCMS settings (for example, alert thresholds, reorganization parameters of CCMS

table MONI) if required.21. Delete all entries from table TLOCK, which holds the repair requests from your source system.22. 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.Adapt the file residence information in the target system. For more information, see the SAPOnline Documentation (SAP Web Application Server System Administration Application Data Archiving andReorganization) .

23. Redefine database actions (backup, update statistics, and so on) if you have used the DBA calendarin the source system (transaction DB13).

24. Check logon groups and assignment of application servers to logon groups (transaction SMLG).25. Check the connection to SAPNet - R/3 Frontend (transaction OSS1).26. Check self-defined external commands (transaction SM69).27. Check entries of the following tables in all relevant systems:n TXCOM (transaction SM54)n THOST (transaction SM55)

28. Check the logical system names. For more information, see Preparations [page 21]. If you need tochange logical system names in the system that results from the copy, change the logical systemnames at this time as described in SAP Notes 103228 and 544509. Follow your corporate namingstrategy for logical systems when making this change.BI customers: If you have copied a BI (formerly BW) system, read SAP Note 325525.

29. For every client in your SAP system check the detail settings (client role, changes and transportsfor client-dependent objects, changes for client-independent objects, protection level, restrictions)(transaction SCC4).

30. Check if you can delete clients that will no longer be used in the target system (transaction SCC5).31. Check the contexts and segments of remote application servers for the SAP Monitoring

Infrastructure if required (transaction RZ21).32. Configure the domain controller in the Transport Management System (TMS) by using

transaction STMS.33. Post-processing for customer objects:

If customer objects are not original in the new system, modify the corresponding entries in tableTADIR.If you encounter problems modifying a customer development class using transaction SMTS orSM31, try to use the option Validate (ENTER) instead of the option Save to save your changes.

34. ABAP Program Loads

106/168 PUBLIC 03/12/2009





The ABAP loads are platform-dependent programs that are generated during runtime and storedin database tables. They are not exported when you use the R3load procedure to copy yourSAP system. The ABAP loads are generated in the target system when they are first used. Thismight, however, reduce production system performance. To avoid this, you can use transactionSGEN to generate the missing loads.Load generation requires a large amount of system resources. Therefore, it makes sense toschedule the generation job to run overnight.For a detailed description of the features, see the online documentation in transaction SGEN bychoosing Information on the SAP Load Generator, or in the Job Monitor by choosing Job Monitor.

35. If you did not change the database when copying the system, you have to start programRS_BW_POST_MIGRATION in the background with variant SAP&POSTMGR. Otherwise, if youchanged the database when copying the system, you have to start program RS_BW_POST_MIGRATION

in the background with variant SAP&POSTMGRDB Program RS_BW_POST_MIGRATION performsnecessary modifications on database-specific objects (mainly BI objects).

Checking the Target SystemThe following actions are suitable for checking the consistency of the target system:

1. Perform initial consistency check (transaction SM28).2. Check the system log on all application servers (transaction SM21).3. Check the consistency of the database (transaction DB02).4. Perform server check (transaction SM51).5. Test transactions frequently used by the customer.6. 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 Generalledger Periodic Processing Closing Check/count Comparison ).

7. FI customers: Run the jobs RFUMSV00 (tax on sales/purchases), RAGITT01 (asset history sheet),RAZUGA01 (asset acquisitions), RAABGA01 (fixed asset retirements) and compare the results to thosegained on the source system before the system copy.

8. CO customers: Run the report group 1SIP and compare the results to those gained on the sourcesystem before the system copy.

Replacing the PSEs in the Target SystemReplace all existing PSEs in the target systems with new ones, which contain the new system’sinformation. Proceed as follows:

1. In your ABAP system, call transaction STRUST.2. Proceed as described in the documentation Creating or Replacing a PSE in the SAP Library at

http://help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAPNetWeaver by Key Capability Security System Security System Security for SAP NetWeaver AS ABAPonly Trust Manager .

03/12/2009 PUBLIC 107/168



Note

n Since replacing a PSE will remove all of the previously used certificates, also import allnecessary trusted certificates into the new PSE’s certificate list. (Check the old PSE’s certificatelist.) Also distribute the new PSE’s public-key certificate to the systems where it will be used.

n Make sure the new PSE contains the new system ID.

n Note the naming conventions to use for each PSE. The naming conventions are usuallyspecified by the Certification Authority (CA) where you obtain the certificate, however, thetype of PSE also has some restrictions, for example, for the SSL server PSE, the CN part of theDistinguished Name must be the host name used to access the server. For the system PSE, werecommend using the SID as the CN part.Therefore, make sure that the Distinguished Name used for the PSE conforms with thenaming convention that applies.

6.2.3 Performing Follow-Up Activities for Java

Depending on the usage types or software units contained in your target system, you have to performgeneral and usage types or software unit-specific configuration steps:

n General follow-up activities [page 108]n Usage Type or Software Unit-specific follow-up activities [page 109]

6.2.3.1 General Follow-Up Activities

You have to perform the following activities for all usage types or software units of the copied SAPsystem.

6.2.3.1.1 Configuration Steps for the SAP Java Connector

You need to perform these post-installation steps for a copied Java system that includes a componentthat has to connect to an ABAP back end using the SAP Java Connector (SAP JCo), for example SAPBusiness Warehouse or SAP Enterprise Portal.

Procedure

1. Log on to the Visual Administrator as an administrator.2. On the launch path on the left, choose Cluster Server <server name> Services JCo RFC Provider .3. On the right, choose Runtime and select the RFC destination that you use for the connection

to the back end.4. Maintain the required parameters for the RFC destination and repository.

108/168 PUBLIC 03/12/2009


5. Remove the old JCo-destination that was copied from the source system.6. Restart the Java server and the component.

6.2.3.1.2 Generating Public-Key Certificates

Reconfiguring the Public-Key CertificatesAfter system copy, the public key certificates are wrong on the target system. You need to reconfigurethem as described at help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAP NetWeaver LibrarySAP 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 LogonTickets Replacing the Key Pair to Use for Logon Tickets .Importing the Public-Key CertificatesYou also need to import this public-key certificate on any systems that are to accept logon ticketsfrom the AS Java system. For more information, see help.sap.com/nw70 SAP NetWeaver 7.0 LibraryEnglish SAP NetWeaver Library SAP NetWeaver by Key Capability Security User Authentication andSingle Sign-On Authentication on the AS Java Configuring Authentication Mechanisms Using Logon Tickets forSingle Sign-On Configuring the Use of Logon Tickets Configuring SAP Web AS ABAP to Accept Logon Ticketsfrom the J2EE .

6.2.3.2 Usage Type or Software Unit-Specific Follow-UpActivities

You have to perform the following activities for specific usage types or software units of the copiedSAP system.

6.2.3.2.1 Application Server Java (AS-Java)

6.2.3.2.1.1 AS Java: SAP Knowledge Warehouse

After the system copy, you have to configure the Internet Knowledge Servlet (IKS) to connect to thenew ABAP back-end as described in Configuring the Access to Knowledge Warehouse Content from SAP InternetKnowledge Servlet in the documentation Installation Guide - SAP NetWeaver 7.0 SR3 on <OS>:<database> athttp://service.sap.com/installNW70 Installation ‒ SAP NetWeaver Systems .

03/12/2009 PUBLIC 109/168



Only valid for: EP Core (EPC)

6.2.3.2.2 EP Core (EPC)

6.2.3.2.2.1 EPC: Portal

If trust between a portal and any other system is required, then you need to replace certificatesand re-establish trust with the newly copied system on which the portal is installed. For moreinformation, see Generating Public-Key Certificates [page 109].If you have more than one portal in your landscape and the portals share content via a federatedportal network (FPN), refer to SAP Note 1080080 for more information about post-system copyconfiguration steps.End of: EP Core (EPC)

Only valid for: Enterprise Portal (EP)

6.2.3.2.3 Enterprise Portal (EP)

6.2.3.2.3.1 EP: Knowledge Management and Collaboration

After the system copy, the Knowledge Management and Collaboration (KMC) target system still hasaccess to the same data as the original source system. If the source and target system have write accessto the same data, this results in serious inconsistencies in both systems. For this reason, it is essentialto prevent both systems from using the same data.Critical items that are accessed by both systems are, for example:

n Indexes for search and classification (TREX)n Data in external repositories, for example, on file system sharesn Data on groupware servers

To prevent source and target system from working with the same data, reconfigure the followingcomponents on the target system:

n TREX

n Repository Managers

110/168 PUBLIC 03/12/2009



n Services

n Collaboration

The tables below summarize the configuration steps for each of the components and specify whereyou can find more information.

TREXAfter the system copy, the target system is still connected to the same TREX installation as the sourcesystem. For this reason you need to install a new instance of TREX and connect it to the target system.

Caution

While KMC is still connected to the old TREX installation, do not delete any indexes, otherwisethey will also be deleted on the source system.

Task Detailed Information

For the target system, install a new instance of TREX. http://service.sap.com/installNW70

Installation Installation - Standalone Engines & ClientsInstallation - Standalone Engine - NW 7.0 SR3 TREX SingleHost

On the target system, set up the connection to thenewly installed TREX system.

http://help.sap.com/nw70 SAP NetWeaver 7.0Library English SAP NetWeaver Library SAP NetWeaverby Key Capability Information Integration Searchand Classification (TREX) TREX ConfigurationPost-Installation Configuration Client Side JavaApplication (HTTP Connection) Specifying the Address of theTREX Name Server

On the target system, delete old indexes that belong tothe source system. Define and generate new indexesfor the target system.

NoteThe prerequisite for this step is that all repositorymanagers are configured correctly for the targetsystem.

http://help.sap.com/nw70 SAP NetWeaver7.0 Library English SAP NetWeaver Library SAPNetWeaver by Key Capability Information IntegrationKnowledge Management Administration Guide SystemAdministration System Configuration ‘Index Administration’iView

Repository ManagersEnsure that the target system does not have write access to the same repositories as the source system.

03/12/2009 PUBLIC 111/168






On the target system, check the configuration of allexternal and internal repository managers that havewrite access to the same data as the source system.Make sure that the source and target system do nothave write access to the same data. For example,check the repository manager settings for:n CM FSDB or CM DBFS repositoriesn Simple File System repositories

http://help.sap.com/nw70 SAP NetWeaver7.0 Library English SAP NetWeaver Library SAPNetWeaver by Key Capability Information IntegrationKnowledge Management Administration Guide SystemConfiguration Content Management ConfigurationRepositories and Repository Managers External Repositories

Services


Content ExchangeIf content exchange is in use, the configuration on thesource and target system is identical. However, it doesnot make sense to have the same content exchangeprocedures configured twice. For this reason, youdelete the configuration on the target system and, ifrequired, set up a new configuration. To remove theexisting configuration on the target system, you runa cleanup file:n Download the cleanup file attached to SAP

Note 1120872. Note that the cleanup procedureautomatically creates a new ID for a syndicatorand subscriber.

n Import the cleanup file into the target portal.To do this, choose System Administration SystemConfiguration Knowledge Management ContentManagement and then, on the right, chooseActions Import .

n If required, configure new content exchangesettings on the target system.

http://help.sap.com/nw70 SAP NetWeaver 7.0Library English SAP NetWeaver Library SAP NetWeaverby Key Capability Information Integration KnowledgeManagement Administration Guide System ConfigurationContent Management Configuration Global Services

Content Exchange Service

URL GeneratorOn the target system, check the settings for the Hostand Alternative Host parameters.

http://help.sap.com/nw70 SAP NetWeaver 7.0Library English SAP NetWeaver Library SAP NetWeaverby Key Capability Information Integration KnowledgeManagement Administration Guide System ConfigurationContent Management Configuration Global Services

URL Generator Service

112/168 PUBLIC 03/12/2009







System Landscape: On the target system, delete theold system IDs that belong to the source system.

Log on to the Portal and choose SystemAdministrationSystem Configuration Knowledge Management ContentManagement Global Services System LandscapeDefinitions Systems Content Management Systems .

Scheduler Service: If the target system is a SAP Javacluster, then you must assign scheduler tasks to thenew system IDs of the target system. After the systemcopy, tasks are still assigned to the IDs of the sourcesystem.

http://help.sap.com/nw70 SAP NetWeaver 7.0Library English SAP NetWeaver Library SAP NetWeaverby Key Capability Information Integration KnowledgeManagement Administration Guide Minimal Configurationfor Knowledge Management Cluster Only: Assigning Tasksto Nodes

Collaboration


On the target system, adapt the room back-endproperties server address, server port and Web

protocol.

http://help.sap.com/nw70 SAP NetWeaver 7.0Library English SAP NetWeaver Library SAP NetWeaverby Key Capability People Integration CollaborationAdministration Guide Basic Configuration DefiningBackend System Properties for Room URLs

On the target system, generate a new index to enablesearch operations in the content of rooms.

http://help.sap.com/nw70 SAP NetWeaver 7.0Library English SAP NetWeaver Library SAP NetWeaverby Key Capability People Integration CollaborationAdministration Guide Virtual Rooms Configuration ofSearch Functions for Rooms Configuration of the Search forRoom Content

On the target system, check the properties of theroomsearch object. Make sure that the parameter UseTREX is set.

http://help.sap.com/nw70 SAP NetWeaver 7.0Library English SAP NetWeaver Library SAP NetWeaverby Key Capability People Integration CollaborationAdministration Guide Virtual Rooms Configuration ofSearch Functions for Rooms Configuration of the Search forRooms

On the target system, configure the connection to therequired groupware server.

http://help.sap.com/nw70 SAP NetWeaver 7.0Library English SAP NetWeaver Library SAP NetWeaverby Key Capability People Integration CollaborationAdministration Guide Basic Configuration ConfiguringE-Mail Connectivity

03/12/2009 PUBLIC 113/168








If the e-mailing service is active on the source system,but is not required on the target system, you needto delete the e-mail transport. After deletion of thetransport, e-mailing is disabled. E-mails will no longerbe automatically sent, for example, when membersare excluded from a room or documents are updatedand deleted.

http://help.sap.com/nw70 SAP NetWeaver 7.0Library English SAP NetWeaver Library SAP NetWeaverby Key Capability People Integration CollaborationAdministration Guide Groupware Groupware FrameworkInstalling and Configuring E-Mail Connectivity ConfigurationSteps Creating an E-Mail Transport

On the target system, reconfigure the ServerName andServerPort for the application sharing server.

http://help.sap.com/nw70 SAP NetWeaver 7.0Library English SAP NetWeaver Library SAP NetWeaverby Key Capability People Integration CollaborationAdministration Guide Real-Time Collaboration ConfiguringReal-Time Collaboration Configuring the Application SharingServer (RTC) Setting Application Sharing Server Parameters(RTC)

End of: Enterprise Portal (EP)

Only valid for: BI Java

6.2.3.2.4 Business Intelligence Java Components (BI Java)

You have to perform the following follow-up activities for usage type BI Java:

6.2.3.2.4.1 Business Intelligence (BI Java)

Follow the instructions in this section if the entries for source system connection have not beencopied to the services file of your target system.

PrerequisitesYou have performed a system copy that includes SAP Business Warehouse (SAP BW).

Adding Entries to the Services FileYou have to do the following to add the entries to the services file:

Your target host runs on a UNIX platform

1. Log on to your target system as user root.

Caution

Make sure that the user root has not set any environment variables for a different SAP system ordatabase.

114/168 PUBLIC 03/12/2009




2. Edit the file /etc/services.3. Add the entries for your source system connection, for example sapgw47 3347.

Your target host runs on a Windows platform or on System i

1. Log on to your target system as a member of the local administration group.2. Edit the file <WindowsDirectory>\system32\drivers\etc\services.3. Add the entries for your source system connection, for example sapgw47 3347.

6.2.3.2.4.2 Basic Configuration for Usage Type BI Java

1. BI-Integrated PlanningCall transaction SPRO and choose SAP NetWeaver Business Intelligence BI-Integrated Planning .Follow the instructions for the following step::Define JCo Destination.

2. Integration into the PortalCall transaction SPRO and choose SAP NetWeaver Business Intelligence Reporting-relevant SettingsBEx Web Integration into the Portal .Follow the instructions for the following steps:a) Create RFC Destination in J2EE Engineb) Import BI Certificate to the Portalc) Maintain Portal Server Settings for the Portald) Create RFC Destination for the Portale) Import Portal Certificate to BI System

End of: BI Java

Only valid for: Process Integration (PI)

6.2.3.2.5 Process Integration (PI)

You have to perform the following follow-up activities for usage type PI:

Note

The following changes reflect exactly the regular configuration steps for usage type PI. For moredetailed instructions about how to change the values, read the configuration information athttp://help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAP NetWeaver Library Technology

Consultant’s Guide Business Process Management Configuration of Usage Type Process Integration .

03/12/2009 PUBLIC 115/168



6.2.3.2.5.1 PI: System Landscape Directory

Note

For more information about how to perform the individual tasks, see the documentation in theSAP Library at http://help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAP NetWeaverLibrary SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Software LifeCycle Management System Landscape Directory Configuring Systems to Connect to SLD . The respectivesections are stated below.

n Maintain the SLD connection parameters:Call transaction SLDAPICUST and change the value for the host name as well as for the port number.For more information, see section Connection Between Web AS ABAP Systems and SLD SLD ApplicationProgramming Interface for ABAP-Based Systems Creating an HTTP Destination for the SLD ABAP API onthe ABAP Side .See

n Maintain the ABAP connection:Call transaction RZ70 and change the value for the host and the gateway service in the group boxTransport Information. This value should be predefined by the value entered before in transactionSLDAPICUST.For more information, see section Connection Between Web AS ABAP Systems and SLD Configuringthe SLD Data Supplier: Default Settings .

n Configure the SLD Data Supplier Service in the Visual Administrator:Change the value for the host as well as for the HTTP port number.For more information, see section Connection Between Web AS Java Systems and SLD Setting Up the SLDData Supplier for J2EE-Based Systems .

Note

For information on how to perform the following tasks, see the Post-Installation Guide SLD of SAPNetWeaver 7.0 at http://service.sap.com/installNW70 Configuration . The respective sectionsare stated below.

n Maintain server settings in the SLD:Change the value for the object server.For more information, see section Configuring Server and Persistence Parameters.

n Configure the SLD Bridge:Change the value for the gateway server as well as for the gateway service.For more information, see section Configuring the SLD Bridge.

116/168 PUBLIC 03/12/2009




6.2.3.2.5.2 PI: Integration Server

1. Maintain the logical system:Call transaction SSC4 to maintain the logical system information.

2. Maintain the technical system and the business system for the Integration Server:In the SLD, maintain a product for the Technical System. Create a Business System for theIntegration Server and maintain the logical system information.

3. Create RFC destinations in the ABAP environment:Call transaction SM59, navigate to destination INTEGRATION_DIRECTORY_HMI, and change the valuefor the target host as well as for the HTTP port number.

4. Maintain RFC destination in the ABAP and Java environment:For the following connections, change the value for the gateway host as well as for the gatewayservice on the ABAP side and in the Visual Administrator. In the Visual Administrator, additionallychange the value for the application host name and the system number. Change the value for thegateway host as well as for the gateway service on the ABAP side and the value for the PI host in theVisual Administrator for the following connections:

Connection Description

AI_RUNTIME_JCOSERVER Used for the connection of the ABAP part to the Javapart of the Integration Server

LCRSAPRFC

SAPSLDAPI

Used for the connection of the Integration Serverto the SLD.

5. Create HTTP destination pmistore in the Java environment:Change the value for the host and port number in the destination URL.

6. Maintain the pipeline to the Integration Server:Change the pipeline to the Integration Server by running transaction SXMB_ADM.

7. Maintain Prefix Numbers for Workflow and Organizational Management.Run transaction SWF_XI_CUSTOMIZING, select Maintain Definition Environment Maintain PrefixNumbers and choose Perform Automatic Workflow Customizing (F9).

6.2.3.2.5.3 PI: Changes in the Exchange Profile

1. Maintain server settings for Exchange Profile connection:Change the value for the host name as well as for the instance number.

2. Change all parameters pointing to the source system:The following parameters contain the host name for the connection of components. Allparameters pointing to the source systemmust be changed in order to reference the target system.

03/12/2009 PUBLIC 117/168


For more information about parameters, see Exchange Profile Parameters in the PI configurationdocumentation at http://help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAPNetWeaver Library Technology Consultant’s Guide Business Process Management Configuration of UsageType Process Integration .

Parameter Description

com.sap.aii.connect.cr.name Contains the host name of the componentrepository server.

com.sap.aii.connect.cr.httpport Contains the HTTP port number of thecomponent repository server.

com.sap.aii.connect.directory.name Contains the host name of the directoryserver.

com.sap.aii.connect.directory.httpport Contains the HTTP port number of thedirectory server.

com.sap.aii.connect.directory.httpsport Contains the HTTPS port number of thedirectory server.

com.sap.aii.connect.directory.rmiport Contains the RMI port number of thedirectory server.

com.sap.aii.connect.integrationserver.name Contains the host name of the IntegrationServer.

com.sap.aii.connect.integrationserver.httpport Contains the HTTP port of the J2EE Engineof the Integration Server. Used by the XIintegration directory to connect to the XIruntime.

com.sap.aii.connect.integrationserver.httpsport Contains the HTTPS port of the J2EE Engineof the Integration Server. Used by the XIintegration directory to connect to the XIruntime.

com.sap.aii.connect.integrationserver.r3.sysnr R3 system number of the NetWeaverApplication Server on which the IntegrationServer runs.

com.sap.aii.connect.integrationserver.r3.httpport Contains the HTTP port number of theIntegration Server.

com.sap.aii.connect.landscape.name Contains the host name of the landscapedirectory server.

com.sap.aii.connect.landscape.httpport Contains the HTTP port number of thelandscape directory server.

com.sap.aii.connect.landscape.httpsport Contains the HTTPS port number of thelandscape directory server.

com.sap.aii.connect.repository.name Contains the host name of the repositoryserver.

118/168 PUBLIC 03/12/2009



Parameter Description

com.sap.aii.connect.repository.httpport Contains the HTTP port number of therepository server.

com.sap.aii.connect.repository.httpsport Contains the HTTPS port number of therepository server.

com.sap.aii.connect.repository.rmiport Contains the RMI port number of therepository server.

com.sap.aii.connect.rwb.name Contains the host name of the RuntimeWorkbench (RWB).

com.sap.aii.connect.rwb.r3.sysnr R3 system number of the NetWeaverApplication Server on which the RuntimeWorkbench runs.

com.sap.aii.connect.rwb.httpport Contains the HTTP port number of theRuntime Workbench.

com.sap.aii.connect.rwb.httpsport Contains the HTTP port number of theRuntime Workbench.

com.sap.aii.ib.server.connect.webas.r3.ashost Connection from Java stack to ABAP stack ofthe NetWeaver Application Server.

com.sap.aii.ib.server.connect.webas.r3.sysnr Connection from Java stack to ABAP stack ofthe NetWeaver Application Server.

com.sap.aii.rwb.server.centralmonitoring.r3.ashost Application server of the NetWeaverApplication Server on which the centralPMI, the central CCMS, and the central alertserver run.

com.sap.aii.rwb.server.centralmonitoring.r3.sysnr System number of the NetWeaverApplication Server on which the centralPMI, CCMS and Alert Server run.

com.sap.aii.rwb.server.centralmonitoring.httpport HTTP port of the NetWeaver ApplicationServer (ABAP part) on which the centralPMI, the CCMS and the Alert Server run.

6.2.3.2.5.4 PI: Refresh Caches

1. Restart the Java engine:In order to initialize caches of Exchange Profile and SLD, restart the Java engine.

2. Refresh the CPACache:Since the restart of the Java server only leads to a delta cache refresh for the CPACache, a fullCPACache refresh is to be forced by executing the following URL:http://<host>:<Java-Port>/CPACache/refresh?mode=full

03/12/2009 PUBLIC 119/168


Note

To call the CPACache refresh URL, you have to enter user PIDIRUSER and the correspondingpassword you entered during the installation.

3. Refresh the XI Cache:Refresh the XI Cache by running transaction SXI_CACHE.

6.2.3.2.5.5 PI: Switching Addresses

The newly installed target IS 7.0 resides at a new network address. In case you want to reconnectbusiness systems, you must make address changes at several locations in order to account for thischange.The following actions are performed automatically:

n Communication from the target IS 7.0 to business systems is set due to copying BI content, whichcontains the communication channels for these business systems.

The following sections contain a detailed description of all necessary manual address changes.

Connecting Business Systems to the SLD of the Target SystemBusiness systems with an Integration Engine require a connection to the SLD server of the targetsystem to obtain their name from the SLD. The business system name is used in the header of themessage sent to the Integration Server. The connection to the SLD is established by creating anRFC destination (as described below) and calling a registered server program, which is defined onthe J2EE JRFC engine of the Integration Server. The server program is called with the HTTP addressas a parameter that is maintained with transaction SLDAPICUST.

Note

For more information about performing the individual tasks, see the configuration information forPI at http://help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAP NetWeaver LibraryTechnology Consultant’s Guide Business Process Management Configuration of Usage Type Process IntegrationConfiguration of Business Systems with an Integration Engine Connecting to the System Landscape Directory .

1. Use transaction SLDAPICUST in the business system to define the SLD access data. This data consistsof the host and port of the SLD as well as a user (PIAPPLUSER) and password. You can use theentries that you maintained on your Integration Server.

2. Change all RFC destinations on your business system. They use the same registered serverprogram, which is defined as part of the JRFC engine settings of the Java engine on the SLD host.This means that all business systems can use the same server program ID (SAPSLDAPI_UNICODE orSAPSLDAPI_NONUNICODE) for their RFC destinations LCRSAPRFC and SAPSLDAPI.

3. You must also change the RFC destinations in:

120/168 PUBLIC 03/12/2009



n all business systems (enter the new Integration Server and, if necessary, adjust the roles)n all technical adaptersn file SLDaccessor.properties in directory /tech_adapter/BaseConfiguration

4. Enter the Gateways in file etc/services.5. For Unicode business systems (program ID SAPSLDAPI_UNICODE), the Unicode indicator is set in the

JRFC engine settings. For non-Unicode business systems (program ID SAPSLDAPI_NONUNICODE),the Unicode indicator is not set.

Maintaining System Connections and DestinationsIf the host name and port of your Integration Server have changed after the system copy, you haveto maintain the destinations and connections if you want to reconnect Integration Engines andadapters. For information on how to perform the individual tasks, see the configuration informationfor PI at http://help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAP NetWeaver LibraryTechnology Consultant’s Guide Business Process Management Configuration of Usage Type Process Integration .The respective sections are stated below.

n Update the HTTP destinations:Update the HTTP destination that points from the Integration Engines (business systems) tothe PI Integration Server. For more information, see section Configuration of Business Systems with anIntegration Engine in the configuration information.

n Optional: Update the destinations to IS 7.0 for receiver preidentification:In the Integration Engine, update RFC destination AI_INTEGRATION_SERVER. For moreinformation, see section Configuration of Business Systems with an Integration Engine in the configurationinformation.

n Optional: Update the destinations to IS 7.0 for maintenance of value mapping table:In the Integration Engine, update RFC destination AI_INTEGRATION_SERVER. For moreinformation, see section Configuration of Business Systems with an Integration Engine in the configurationinformation.

n Reintegrate business systems using the IDoc adapter of the source system:In the sending system, update the RFC destination to the Integration Server. For moreinformation, see section Integration of Business Systems Integration Using the IDoc Adapter in theconfiguration information.

n In case you made configuration settingsMaintain Services for the Integration Server in transactionSICF, make sure these settings are maintained in the newly installed target system, too.

For the following steps, see SAP Library at http://help.sap.com/nw70 SAP NetWeaver 7.0 LibraryEnglish SAP NetWeaver Library SAP NetWeaver by Key Capability Process Integration by Key CapabilitySAP NetWeaver Exchange Infrastructure Runtime Connectivity and then the sections stated below:

n Change the system connections for the RFC adapter:

03/12/2009 PUBLIC 121/168




In all application systems, change the program ID RFC Destination in transaction SM59 to the newprogram ID defined in your sender channels in the section RFC Adapter. For more information,see section Adapters RFC Adapters .

n Integrate business systems using the Plain J2SE Adapter Engine:Update the URL of the HTTP destination to the Integration Server in the sender adapters. Formore information, see section Adapter Engine Plain J2SE Adapter Engine .

6.2.3.2.5.6 PI: Connection Checks

1. Checks in SLDCHECK:On the Integration Server, call transaction SLDCHECK.

2. Checks in SPROXY:Call transaction SPROXY, choose Goto Connection Test and execute all checks.

End of: Process Integration (PI)


6.2.3.2.6 Development Infrastructure (DI)

You have to perform the following manual steps on the target system after the move of an SAP systemwith usage type Development Infrastructure (DI). The assumption here is that all components(DTR, CBS, CMS, SLD and name server) were on a single host before the move and will remain on asingle host after the move.

Procedure

1. If you are using an LDAP server for user management it should be running to ensure that all theusers that were created when the Development Infrastructure (DI) was on the source system willstill be valid after the move to the target system.

2. Check the Java Engine Configuration:n Set MaxHeapSize and other engine parameters to the recommended values.

See Installation Guide for SAP NetWeaver 7.0 SR3 Java on <OS>:>Database> (including usage typeDI) for details.

n


If your database is SAP MaxDB:,a) Upgrade it to at least version 29.b) Set the JOIN_OPERATOR_IMPLEMENTATION parameter to IMPROVED (setting this value is only

possible using the DB-WebUI in SAPMMC).

122/168 PUBLIC 03/12/2009


c) Restart the database.End of: MaxDB

n For general recommendations for the configuration of the Development InfrastructureServers, see SAP Note 889038.

3. Design Time Repository (DTR):n Redeploy the database schema.

This is necessary to re-create the missing metadata for the database views in the dictionary.Otherwise OpenSQL cannot see the database views.The database schema of the DTR server is part of the NWDI SCA. This is the SCA that you havedownloaded from http://service.sap.com/swdc to deploy the NetWeaver DevelopmentInfrastructure (NWDI).In order to only deploy this database schema you have to extract the SCA file. You can do thisby appending .zip to the filename. Then you can use a normal archive tool like WinZip. Underthe subfolder DEPLOYARCHIVES you can find the SDA sap.com~tc~dtr~dbschema.sda for thedatabase schema. This SDAmust be deployed using the Software Deployment Manager (SDM).

Note

During deployment, use the option Update deployed SDAs/SCAs that have any version. This optioncan be set in the Deployment tab on SDM.

n Restart DTR server.

n Change the URL of 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 or if the name serverwas also moved.

n Perform an Update Statistics (30%) on the database.


Note

If your database is SAP MaxDB you can use the Database Manager to update the databasestatistics.

End of: MaxDB

4. System Landscape Directory (SLD):Change the CIM Server URL of the SLD that is defined in the technical landscape to point tothe target host.

Caution

Do not change the ObjectServer attribute.

03/12/2009 PUBLIC 123/168


http://service.sap.com/swdc


5. Component Build Service (CBS):The service properties JDK_HOME_PATHS, BUILD_TOOL_JDK_HOME, rootFolder and threadPoolSize

have to be adjusted according to the hardware and software configuration of the new system.See Installation Guide for SAP NetWeaver 7.0 SR3 Java on <OS>:>Database> (including usage type DI)for details about these parameters.

6. Change Management Service (CMS):The main steps in CMS involve resetting the fields containing URLs to other components (likeDTR, CBS, SLD).n If CMS has not been configured yet, proceed as follows:

a) Copy the folder /usr/sap/trans/EPS/in/CMS<host><SID>, including its content, to thetarget host.

b) Rename the folder to the new host value and new SAPSID (if changed).c) Make sure that the engine user (<SID>adm) has write permissions in the copied folder.

n If CMS has been configured and you have used it already, proceed as follows:a) For the domain (in the Domain Data tab):

A) Change the SLD URL to point to the target host.B) Change the CMS URL to point to the target host.C) Change the transport directory to the appropriate directory on the new CMS (target

host).D) Save the domain. You should see a status message that the data was saved successfully.E) Update CMS (using the button Update CMS). You should see a status message that the

CMS update was successfully.b) Copy the contents of the transport directory of the old CMS (source system) to the

transport directory of the new CMS (target system). The transport directory is configuredin the domain (see Domain Data tab).

c) For each track (in the Track Data tab):A) Change the CBS and DTR URLs.B) For each runtime system that is defined, change the runtime system configuration to

point to the appropriate host (of the target runtime system).If this has not changed, leave the fields unchanged.

C) Save the track definition.You should see a status message that the data was saved successfully.

D) Restore System State (of the DEV system). This will place the Software Components(SCs) into the import queue of this system.

E) Import these SCs. After the import is finished, you should see a status for each SC.7. IDE:n Change the SLD URL in the preference page of the SAP NetWeaver Development Studio (under

Java Development Infrastructure Development Configuration Pool ).This should now point to the new SLD on the target system.

n Import the development configuration you had earlier used for development.

124/168 PUBLIC 03/12/2009


Now you are ready to begin the development with you new (relocated) DevelopmentInfrastructure (DI).

8. Verification Steps (optional)The following steps can optionally be done to verify that the Development Infrastructure (DI)is fully functional after the move:a) Log in to the DTR (using the browser) for all defined users and browse the repository.b) Using IDE, create a new Development Component (DC), check in and activate:n The activation should succeed.

n The name of the Development Component (DC) must be reserved on the name server.c) 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.d) Import the Change Request into the CONS system (from the CMS Transport Studio).e) Assemble a new version of your Software Components (SCs) in one of the tracks.

End of: Development Infrastructure (DI)

Only valid for: SAP ERP Self Services (XSS)

6.2.3.2.7 Self Services (XSS)

6.2.3.2.7.1 Re-Creating the JCo Destinations

You must re-create the JCo destinations as described in the documentation Creating JCo Destinationsin the SAP Library at http://help.sap.com/nw70 SAP NetWeaver Library SAP NetWeaver by KeyCapability Application Platform (SAP Web Application Server) Java Technology in SAP Web Application ServerJava Development Manual Developing User Interfaces Web Dynpro Advanced Web Dynpro Technologies

Web Dynpro Content Administrator .For more information, see SAP Note 899144.

Only valid for: SAP ERP Self Services (XSS)

6.2.3.2.7.2 ERP-XSS: SAP WebDynpro Applications

SAP WebDynpro applications that use “Adaptive RFC” (a Web Dynpro technology based on JCo andAII), require that their “Destinations ”(back-end connections) are configured with the Web DynproContent Administrator “Admin” (a tool specific to Web Dynpro). The configuration data is stored inthe System Landscape Directory (SLD) where it is associated with the Java Cluster that the ContentAdmin runs on. Some additional data is stored in the Secure Storage of the Java Cluster itself. For

03/12/2009 PUBLIC 125/168






both reasons, the destinations have to be configured for each Java Cluster individually and currentlycannot be transported.For more information, see the documentation in the SAP Library at http://help.sap.com/nw70SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform Java Technology JavaDevelopment Manual Core Development Tasks Developing User Interfaces Web Dynpro.

Note

Make sure you use the correct host and port in the portal under System administration Systemconfiguration Systems SAP_Webdynpro .

End of: SAP ERP Self Services (XSS)

End of: SAP ERP Self Services (XSS)

Only valid for: SAP CRM;SAP ERP CRM Java Components (JCRM);Extended E-Selling Components (XECO)

6.2.3.2.8 CRM Java Components (JCRM) / Extended E-SellingComponents (XECO)

Only valid for: SAP ERP;SAP CRM CRM Java Components (JCRM);Extended E-Selling Components (XECO)

6.2.3.2.8.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. The WFD Calculation Services also has an XCMparameter cs.http.port that points to the HTTP port of the Java instance it was installed on.If the system copy involves copying the SAP CRM back-end system, you need to adjust thecs.jco.xxxxx XCM parameters (which point to the SAP CRM back-end system) in the target system.If the system copy involves copying the Java engine, you need to adjust the cs.http.port XCMparameter for WFD Calculation Services in the target system. It should point to the HTTP port ofthe target Java engine.

ProcedureConfigure XCM parameters for WFD Application Services:http://<J2EEHOST>:<>//wfd/admin/xcm/init.do.

Configure XCM parameters for WFD Calculation Services:http://<J2EEHOST>:<J2EEHTTPPORT>//wfdcs/admin/xcm/init.do

End of: SAP ERP;SAP CRM CRM Java Components (JCRM);Extended E-Selling Components (XECO)

End of: SAP CRM;SAP ERP CRM Java Components (JCRM);Extended E-Selling Components (XECO)

126/168 PUBLIC 03/12/2009





Only valid for: SAP CRM MapBox (MBX)

6.2.3.2.9 MapBox

You need to proceed as follows to restore the configuration of the CRM Java component MapBoxon the target system.

Procedure

1. You shut down the Java engine.2. You copy the following files to the relevant directories:

a) Copy the files mapboxmeta.xml, mapboxmeta.xsl and xmlprofiles.xml to the directory<J2EE_root>/cluster/server/.mapboxmeta. You can find these files at the same locationon the source system.

b) Copy the file coordserver.cfg to the <J2EE_root>/cluster/server directory.c) If you want to have the smoketest directory on the target system, then you need to copy the

smoketest directory, too.3. You 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.0 on <OS> <ABAP+Java|Java> athttp://service.sap.com/crm-inst .

ResultYou have restored the configuration for MapBox on the target system.End of: SAP CRM MapBox (MBX)

Only valid for: SAP SRM SRM Live Auction Cockpit (SRMLAC)

6.2.3.2.10 SRM Live Auction Cockpit (SRMLAC)


6.2.3.2.10.1 SRM Live Auction Cockpit (SRMLAC)

To facilitate customization, the resource files for the Live Auction Cockpit applet are packagedseparately from the web application itself. In order for the applet to retrieve its resources, the webserver must make the resource files accessible using HTTP. This is achieved by creating a web alias forthe directory that contains the resources. Without this alias, the applet does not load properly.

03/12/2009 PUBLIC 127/168

http://service.sap.com/crm-inst


PrerequisitesThe J2EE Engine is running.

Procedure

1. Open the Java engine administration tool.

Example

Windows (and System i), go to:<T_INSTDIR>\usr\sap\<sapsid>\<instancenumber>\j2ee\admin\go.bat

UNIX, go to:<T_INSTDIR>/usr/sap/<sapsid>/<instancenumber>/j2ee/admin/go.sh

Port: 5<instance number>04

2. Enter the Java engine administrator password and choose Connect.3. In the navigation pane, choose Server Services HTTP Provider4. Select the Runtime tab.5. Select the Aliases tab.6. In Alias enter srm/lib/resources.7. Enter the Path.

Example

Windows (and System i):<T_INSTDIR>:\usr\sap\<SAPSID>\SYS\global\srmla\resources

UNIX:<T_INSTDIR>:/usr/sap/<SAPSID>/SYS/global/srmla/resources

8. Choose Add.9. Choose Save Properties.10. Choose the Java administration tool.

End of: SAP SRM SRM Live Auction Cockpit (SRMLAC)


6.2.3.2.10.2 Configuring Single Sign-On

To enable Single Sign-On (SSO) you need to configure certain settings in SAP Enterprise Buyer (EBP).

128/168 PUBLIC 03/12/2009


Note

If you are using an external SAP Internet Transaction Server (ITS), you need certain system patchesto make sure that the SSO ticket is properly generated. For more information, see SAP Note 720738.

PrerequisitesYou have access to the following transactions in EBP:

n RZ10 (Edit Profiles)

n STRUST (Trust Manager)

Procedure

1. Create SSO ticket in Profile Maintenance.a) Go to transaction RZ10.b) Choose the Default profile along with the latest version number and select Extended Maintenance.c) Change the following profile parameters:n login/create_sso2_ticket = 1

n login/accept_sso2_ticket = 1

d) Save and Activate the profile.A new profile is automatically generated.

e) Restart the application server.

Caution

Do not forget or skip this step.

2. Export the R3 SSO certificate from the Trust Manager on the target host server.a) Go to transaction STRUST.b) Double-click the text box to the right of Own certif.

The certificate information is displayed.

Note

Make a note of the values displayed in the certificate information because you need to enterthose values below in step 3.

c) Click the icon with the quick info: Export Certificate.d) Save the file as <R3_Name>-<Client>.crt.

Example

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

03/12/2009 PUBLIC 129/168



Caution

Make sure Binary is selected under File Format.

Note

If you export the certificate to a local system, you must copy the file from the local systemto the target host server.

3. Import R3 SSO certificate to the java engine using the administrator tool.

Note

Make sure the Java engine is started.

a) Open the Java administration tool.b) Enter the Java engine administrator password and click Connect.c) Choose Server Services Key Storage .d) Click TicketKeyStore in the View panel.e) Click Load in the Entry group box.f) 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

Make a note of the issuer and subject distinguished names displayed in the certificate of theSAP system. These values must be identical to those you define for the properties in step 4.

4. Configure the Security Provider service in the SAP Java engine using the administrator tool.a) Choose Server Services Security Provider .b) Choose ticket in the component panel and go to the Authentication tab.c) Modify the options of EvaluateTicketLoginModule and add the following properties to each back-end

system on which you want to configure SSO:

Note

For each property below, {n} represents the number of the back-end system on which youwant to configure SSO.

n trustedsys{n}: <R3_Name>, <Client>

Example

trustedsys1: EBS, 300

n trustediss{n}: <the issuer distinguished name>

130/168 PUBLIC 03/12/2009


Note

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

Example

trustediss1: CN=EBS

n trusteddn{n): <the subject distinguished name>

Note

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

Example

trusteddn1: CN=EBS




6.2.3.2.11 SCM Forecasting & Replenishment Processor (SCMFRP)

You must perform follow-up activities after the system copy as described in SAP Note 862955.End of: SAP SCM

6.2.4 Performing Jobhead Correction after HomogeneousSystem 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 tocomplete the homogeneous system copy, the SSID needs to be set to the target system.

03/12/2009 PUBLIC 131/168





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

ProcedureTo set the SSID to the target system:

Only valid for: SAP NetWeaver 7.0;SAP NetWeaver 7.1

1. Call transaction DBACOCKPIT.2. Choose Configuration Homogeneous System Copy: Jobhead Correction3. Modify the necessary data.

End of: SAP NetWeaver 7.0;SAP NetWeaver 7.1

Only valid for: SAP Web AS 6.40

1. Call transaction DB2.2. Choose Checks/Settings Correct Jobheads3. Modify the necessary data.

End of: SAP Web AS 6.40

132/168 PUBLIC 03/12/2009

7 Additional Information

7 Additional Information

7.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 processduring the system copy procedure. The Migration Monitor is integrated into the SAPinst system copytool, but you can also use the monitor for copying older releases by starting it manually.The Migration Monitor will

n create R3load command files

n create R3load task files if requiredn start the R3load processes to unload the datan transfer packages from the source to the target host if requiredn start the R3load processes to load the data as soon as a package is availablen inform the person performing the system copy in case of errors

The Migration Monitor has to be started on the source database host (Export Monitor) and onthe target database host (Import Monitor).

Caution

If you want to convert a non-Unicode system to Unicode using the Socket option, you need an R3loadversion with at least patch level 73 (compile date: 12.01.2008).

Prerequisites

n JRE version 1.5 or highern The JAVA_HOME environment variable must point to the JRE directory.n The correct directory structure for R3load dump files must exist on both the source and target

hosts.

7.1.1 Configuration

Help

The tool will display the available parameters, if you call it with one of the following options:

03/12/2009 PUBLIC 133/168

7 Additional Information7.1 R3load Procedures Using the Migration Monitor

n -help

n -?

Version

The tool will display the version information (release branch and build date), if you call it withthe following option:

n -version

General Options

Name Description Comments

monitorTimeout Monitor timeout in seconds During a timeout, the monitorthread sleeps and does not analyzeany files or analyze its processingstate. The default timeout value is30 seconds.

E-Mail Options


mailServer SMTP server Server name or IP address of thecompany SMTP server

mailFrom “From” e-mail address

mailTo “To” e-mail address Can contain an address listseparated by ‘;’ or blanks.

Trace Option


trace Trace level Possible values:all, off,

1 (error), 2 (warning), 3 (info), 4 (config, default),5,6,7 (trace)

Export Options

Option Description Comments

installDir Installation directory The installation start directory is thedirectory in which the installationtools (SAPinst, R3SETUP) writetheir log files. When the MigrationMonitor is used without theinstallation tools, the installationstart directory is the directory, where

134/168 PUBLIC 03/12/2009



the R3load TSK and log files will becreated.

exportDirs List of export directories Separator on Windows: ‘;’ Separatoron UNIX: ‘:’ The ‘exportDirs’parameter points to the directorywhere the R3load dump files willbe written to. In the ‘exportDirs’directory, the subdirectories DATA,DB and DB/<TARGET_DBTYPE>(forexample, DB/ORA) have to exist.

client Client operating mode Running in client mode means,the Monitor will run parallel withstandard SAPinst export process andtransfer the exported dump files ontothe import server.

server Server operating mode Running in server mode means, theMonitor will create R3load TSK files(if necessary). R3load cmd files andstart the R3load processes.

All options below are for the server mode. The Import Monitor always runs in the server mode. If you want to run the Export Monitor inthe server mode, specify the parameter ‘server’ in the Export Monitors properties file.

orderBy Package order Can be the ‘name’ or path of the filethat contains package names. If theoption value is omitted then packageorder is not determined.

r3loadExe Path of the R3load executable Optional; the default is R3load.If only the name of the R3loadexecutable is available, then JVMlooks for the R3load executable usingOS-specific process search rules.

tskFiles ’yes’ to create task files; ’no’ to skip Before version 4.6 must be set to ‘no’;starting from version 4.7 ‘yes’. If theR3load task files ‘*.TSK’ already existthen the monitor will not overwritethem.

dataCodepage Code page for data files See SAP Note 552464. Possible values:4102, 4103, 1100

taskArgs Additional R3load arguments for theTASK phase

Appended to the R3load commandline. Options already set by themonitor: -ctf; -l; -o (if the omitargument is specified).

03/12/2009 PUBLIC 135/168




loadArgs Additional R3load arguments for theLOAD phase

Appended to the R3load commandline. Options already set by themonitor: -e; -datacodepage; -l;

-p; -r; -socket (if the socket optionis specified); -o (if the omit argumentis specified and task files are not used,that is, the value of the ‘tskFiles’option is ‘no’).

expJobNum Number of parallel export jobs, thedefault is 1.

Any positive number; 0 for anunlimited number of jobs.

Network Exchange Options


net Network operating mode Exported dump files must be visibleon the import host to use thismode.

netExchangeDir Network exchange directory Used for communication betweenthe export and Import Monitors.Must be writable for ExportMonitor and readable for ImportMonitor. The Export Monitor willwrite a file <package>.SGN to thenetwork exchange directory as asignal for the Import Monitor thatthe package is exported successfullyand the import could be started.

FTP Exchange Options


ftp FTP operating mode Exported dump files will betransferred automatically fromthe source host (directory‘exportDirs’) to the target host(directory ‘importDirs’) using FTP.

ftpHost Remote FTP host Name or IP address of the importserver.

ftpUser Name of the remote FTP user The FTP user specified here shouldbe the <sapsid>adm to make surethat the package files can be read byduring the import (which is startedas <sapsid>adm).

136/168 PUBLIC 03/12/2009



ftpPassword Password of the remote FTP userCaution

Security risk!

ftpExportDirs List of remote FTP directories forexport dump

Both ‘;’ or ‘:’ separators are valid.This is the directory on the targethost to which the dump will betransferred. The value will be thesame as for ‘importDirs’ in theImport Monitors property file.

ftpExchangeDir Remote FTP exchange directory Used for communication betweenthe export and Import Monitors.Must be writable for theExport Monitor and readablefor the Import Monitor. TheExport Monitor will write a file<package>.SGN to the FTP exchangedirectory as a signal for theImport Monitor that the packageis exported successfully and theimport could be started.

ftpJobNum Number of parallel FTP jobs; thedefault is 1.

Any positive number; 0 for anunlimited number of jobs.

Export Socket Host

Option Description Comment

socket Socket operating mode R3load will not write dump files tothe file system but the export andimport work through the socketconnection.

host Remote import host Name or IP address of the importhost.

port Host port number Must be the same as the portnumber on the import host. Anyfree port on the import host from1024 to 65535.

03/12/2009 PUBLIC 137/168


FTP Copy Options

Option Description Command

ftpCopy FTP copy operating mode Used as a separate program call formigration with sockets. All filesproduced by R3lctl and R3szchkwill be transferred from the sourceto the target host using FTP.

exportDirs List of export directories Separator on Windows: ‘;’Separator on UNIX: ‘:’ In the‘exportDirs’ directory, thesubdirectories DATA, DB andDB/<TARGET_DBTYPE> (e.g. DB/ORA)have to exist. The R3load STR fileshave to exist in the subdirectoryDATA, the DDL*.TPL files in thesubdirectory DB, and the R3loadEXT files (if required) in thesubdirectory DB/<TARGET_DBTYPE>.

ftpHost Remote FTP host Name or IP address of the importserver.

ftpUser Name of the remote FTP user The FTP user specified here shouldbe the <sapsid>adm to make surethat the package files can be read byduring the import (which is startedas <sapsid>adm).

ftpPassword Password of the remote FTP user CAUTION: Security risk

ftpExportDirs List of remote FTP directories forexport dump

Both ‘;’ or ‘:’ separators are valid.This is the directory on the targethost to which the dump will betransferred. The value will be thesame as for ‘importDirs’ in theImport Monitors property file.

Any other option is ignored by Import Monitor.

Mandatory Options for Export Monitor

n Client mode:installDir, exportDirs,

one of the options ftp, net (and their related parameters)n Server mode:

installDir, exportDirs, tskFiles,

one of the options ftp, net, socket (and their related parameters)n FTP copy:

138/168 PUBLIC 03/12/2009


exportDirs, ftpHost, ftpUser, ftpExportDirs, ftpExchangeDir

Note

The value of the dbType option is determined automatically in the shell script/batch files fromthe dbms_type environment variable.

Import Options


installDir Installation directory The installation start directory is the directory inwhich the installation tools (SAPinst, R3SETUP)write their log files. When the Migration Monitor isused without the installation tools, the installationstart directory is the directory, where the R3loadTSK and log files will be created.

importDirs List of import directories Separator on Windows: ‘;’ Separator on UNIX: ‘:’The ‘importDirs’ parameter points to the directorywhere the R3load dump files will be written to. Inthe ‘importDirs’ directory, the subdirectories DATA,DB and DB/<TARGET_DBTYPE> (for example, DB/ORA)have to exist.

orderBy Package order This option is used only if the Import Monitor workswithout the Export Monitor in stand-alone mode,that is, all export dump files are available on theimport host before the Import Monitor is started.Values can be:name: load packages in alphabetical order,size: load packages starting with the largest one, ora path of the file that contains package names.If the option is omitted then package order is notdefined.

r3loadExe Path of the R3loadexecutable

Optional; the default is R3load. If only the name ofthe R3load executable is available then JVM looksfor the R3load executable using OS-specific processsearch rules.

tskFiles ‘yes’ to create task files;‘no’ to skip

Before version 4.6 must be set to ‘no’; starting fromversion 4.7 ‘yes’. If the R3load task files ‘*.TSK’already exist then the monitor will not overwritethem.

extFiles ‘yes’ to include EXTfiles; ‘no’ to skip them

Add EXT file entries to cmd files; If the EXT filescannot be found in DB/<TARGET_DBTYPE> importdump subdirectory the package processing isaborted.

dbCodepage Database code page forthe target database

See SAP Note 552464. Possible values: 4102, 4103,

1100

03/12/2009 PUBLIC 139/168




migrationKey Migration key

omit R3load omit value Can contain only ’DTPIV’ letters.-o D : omit data; do not load data-o T: omit tables; do not create tables-o P: omit primary keys; do not create primary keys-o I: omit indexes; do not create indexes-o V: omit views; do not create views If you wantto combine several omit options, list these optionswithout blank (for example, ‘-o TV’).

taskArgs Additional R3loadarguments for theTASK phase

Appended to the R3load command line.Options already set by the monitor:-ctf; -l; -o (if the omit argument is specified).

loadArgs Additional R3loadarguments for theLOAD phase

Appended to the R3load command line.Options already used by the monitor:-i; -dbcodepage; -l; -p; -k; -r; -socket (if thesocket option is specified); -o (if the omit argumentis specified and task files are not used, that is, thevalue of ‘tskFiles’ option is ‘no’).

impJobNum Number of parallelimport jobs; the defaultis 1.

Any positive number; 0 for an unlimited numberof jobs

Import Exchange Options


exchangeDir Exchange directory If this option is not set, then themonitor runs in stand-alonemode, that is without the ExportMonitor. All the export dumpfiles or the SAP export CDsfrom the installation kit must beavailable on the import host andbe specified with the parameter‘importDirs’ (for example, in theproperties file). If there is an old fileexport_statistics.properties

(for example, from a previousexport run), remove this file.

Import Socket Options

Option Description Command

socket Socket operating mode

port Server port number Any free port from 1024 to 65535.

140/168 PUBLIC 03/12/2009


Any other option is ignored by Import Monitor.

Mandatory Options for Import Monitor

n Server mode (default):installDir, importDirs, tskFiles, extFiles,

one of the options exchangeDir or socket (and their related parameters)n Stand-alone mode:

installDir, importDirs, tskFiles, extFiles

Note

The value of the dbType option is determined automatically in the shell script/batch files fromthe dbms_type environment variable.

7.1.2 Assigning DDL Files to Packages

It is possible to use several different DDL*.TPL templates during the export respectively during theimport. The assignment of a specific DDL file to a single package is done within a simple text file,which then has to be specified via the ddlMap option within the migration monitor’s properties file.Packages not listed in the DDL mapping file will use the default DDL control file.

ProcedureExample of a DDL mapping file:# DDL mapping file ddl_mapping.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.TPL

# package names

SAPAPPL0

SAPAPPL1

SAPSDIC

[ UNSORTED UNLOAD ]

DDL file for unsorted unload

ddlFile = ./DDLORA_LRG.TPL

# table names

TABLE_A

TABLE_B

TABLE_C

03/12/2009 PUBLIC 141/168


7.1.3 Defining Groups of Packages

The “package group” feature is an enhancement of defining a package order. By defining groupsyou can prevent parallel execution of certain packages and you can define how many large tablesare exported or imported at the same time. In addition, you can specify different values for theparameter jobNum and taskArgs / loadArgs per package. Package groups can be defined in the sametext file in which the package order can be defined (see parameter orderBy). The old package orderformat is also fully supported.If package groups are defined, the maximal number of parallel R3load jobs is the sum of jobNum of allpackages. All packages without package group will be assigned to a “default group” with the numberof jobs, which was defined in the migration monitor’s properties file.

ProcedureExample 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.4 Processing Split Tables

If tables have been split during the export, it has to be ensured before the import starts that thetable exists and that the primary key and the indexes are created before/after (as defined in the DDLtemplate) the table data have been imported. These tasks will be synchronized by the migrationmonitor automatically. WHR files are part of the package and have to be copied to DATA exportsubdirectory to make sure that the same WHR file is used for the export and the import of thecorresponding package.The following database platforms to not support parallel data import:

n IBM DB2 for Linux, UNIX, and Windowsn MS SQL

142/168 PUBLIC 03/12/2009


You can ensure this by using the feature Defining Groups of Packages [page 142].

Example: Target database does not support parallel data importUseDuring the export you have split the table MY_FIRST_TABLE into 3 packages and MY_SECOND_TABLE

into 5 packages. Now you want to run a maximum of 10 R3load processes for parallel data import.ProcedureCreate 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, you can also define the processing order of packages or you can assign DDL files to packages.The inputFile.txt file has to be specified as value for the Migration Monitor parameter orderBy.For every group (MY_FIRST_TABLE and MY_SECOND_TABLE) a R3load job is started. The number ofparallel R3load jobs will be the total of the number of R3load jobs of each group plus the numberof R3load jobs defined for the default group (which is made up of all packages without an explicitgroup name), defined by the parameter jobNum.In this example the parameter jobNum in the import_monitor_cmd.properties file has to be set to 8to ensure that not more than 10 R3load processes will run in parallel.

Re-Starting the Import of a Split-table PackageIf the import of a package fails, the rows. which belong to this package have to be deleted using theWHERE condition assigned to this package before starting the data import again. The deletion witha WHERE clause can be very time consuming so it is faster to delete all rows of the correspondingtable manually and reimport all packages instead.Restart for all other database platforms:

1. Eliminate the reason for the failure of the import of the package(s).2. Delete all rows of the table, for which the import one or more packages failed, manually.3. Remove the TSK files of all packages, which import data into this table (<table

name>-<counter>__TPI.TSK). Do not remove the TSK files, which create the table or which createthe indexes for this table.

03/12/2009 PUBLIC 143/168


4. Adapt the file import_state.properties in the installation directory. Replace the status ’+’ ofall packages for the corresponding table, which had been imported successfully and have to bereimported by ’0’ (see Restarting R3load Processes [page 54]).

5. Restart the import.

7.1.5 Starting the Migration Monitor

The tool can be started using one of the following:

n


The UNIX shell scriptsexport_monitor.sh / import_monitor.sh /

export_monitor_secure.sh

End of: UNIX

n


The Windows batch filesexport_monitor.bat / import_monitor.bat /

export_monitor_secure.bat

End of: Windows

n


IBM i5/OS specific1. Run the command call qp2term.2. export_monitor.sh / import_monitor.sh3. Set the JAVA_HOME environment as follows:

export JAVA_HOME=/QIBM/ProdData/Java400/jdk14

4. 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 133]. The namesof the property files are export_monitor_cmd.properties and import_monitor_cmd.properties.Templates for these files are included in the application archive and must be located in the currentuser’s working directory.Any options specified in the command line take precedence over the corresponding options in theapplication property file. Options are case-sensitive; any options that are not recognized are ignored.To specify an option:

n in the command line,enter -optionName optionValue

n in the application property file,

144/168 PUBLIC 03/12/2009


insert the new line optionName=optionValue


Example of a command line for a UNIX terminal:End of: UNIX


./export_monitor.sh –ftp

End of: UNIX


./export_monitor.sh –ftpCopy

End of: UNIX


./export_monitor.sh –socket –host <import server> –port 5000

End of: UNIX


Example of a command line for Windows cmd.exe:End of: Windows


export_monitor.bat –net

End of: Windows


export_monitor.bat –socket

End of: Windows

If FTP access is used and security is required, start the monitor using the secure version of the shellscript/batch file to prevent seeing FTP password in the command line parameter string / property file.


Example of a command line for a UNIX terminal:End of: UNIX


./export_monitor_secure.sh –ftpPassword <password>

End of: UNIX

1. Start the monitor and close the shell window / command processor. The monitor process willrun in background.

2. Use monitor *.log and *.console.log files to check monitor processing state.

Example of an export_monitor_cmd.properties file with export options:# Export Monitor options

03/12/2009 PUBLIC 145/168


# Operating mode: ftp | net

#net

ftp

#

# Common options

#

# List of export directories, separator on Windows ; 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, separator : or ;

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.de

# "From" email address

[email protected]

# "To" email address

[email protected] [email protected]

Example of an import_monitor_cmd.properties file with import options:

146/168 PUBLIC 03/12/2009


# Import Monitor options

#

# Common options

#

# List of import directories, separator on Windows ; 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.de

# "From" email address

[email protected]

# "To" email address

[email protected] [email protected]

03/12/2009 PUBLIC 147/168


What happens during export / import with the above listed property filesduring a system copy with source and target database Oracle:

n On the export host, the following directories have to exist (see parameter exportDirs):

l c:\temp\export_dump\DATA

l c:\temp\export_dump\DB

l c:\temp\export_dump\DB\ORA

The directory c:\temp\export_dump\DATA has to contain the STR files generated by R3ldctl, thedirectory c:\temp\export_dump\DB the files DDL<DBTYPE>.TPL generated by R3ldctl as well, thedirectory c:\temp\export_dump\DB\ORA the EXT files generated by R3szchk.

n The Export Monitor will write the R3load dump files and the TOC files to the directoryc:\temp\export_dump\DATA.

n The R3load log files, cmd files and TSK files (if required) are located in the directoryc:\install\start (parameter: installDir). The export itself is not done by the Export Monitor,as the monitor is started in client mode (parameter ‘server’ is not set).

n As soon as a package has been exported successfully, the Export Monitor will transfer all filesbelonging to that package (TOC, STR, EXT, 001, ...) 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) identified by password (parameter:ftpPassword) to logon.

n If the package files have been transferred completely to the server, the Export Monitor will write asignal file <package>.SGN to the directory /install_dir/exchange (parameter: ftpExchangeDir)to notify the Import Monitor that it could start the import of this package.

n On the import host, the following directories have to exist (see parameter importDirs):

l /install_dir/export_dump/DATA

l /install_dir/export_dump/DB

l /install_dir/export_dump/DB/ORA

The directory /install_dir/export_dump/DATA has to contain the STR files generated by R3ldctl,the directory /install_dir/export_dump/DB the files DDL<DBTYPE>.TPL generated by R3ldctl, too,the directory /install_dir/export_dump/DB/ORA the EXT files generated by R3szchk.

n The import monitor will start to import a package as soon as the file <package>.SGN is found inthe directory /install_dir/exchange (parameter: exchangeDir).

n The R3load log files, cmd files and TSK files (if required) will be located in the directory/install_dir/start (parameter: installDir).

n The file DDLORA.TPL has to be copied to the directory /install_dir/start (parameter:installDir) before you can start the Import Monitor.

148/168 PUBLIC 03/12/2009


7.1.6 Output Files

Export

n export_monitor.log

n export_state.properties

n ExportMonitor.console.log

Import

n import_monitor.log

n import_state.properties

n 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 Package export not yet started.

? Package export in progress.

- Package export finished with errors.

+0 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

PrerequisitesMake sure there is enough free space in the target system for the database load. To find out the size ofthe export and the sizes of the tablespaces or dbspaces that are created, look at the file DBSIZE.XML

03/12/2009 PUBLIC 149/168


located in the directory <DRIVE>:\<EXPDIR>\DB\<DATABASE> (Windows) or <EXPDIR>/DB/<DATABASE>(UNIX).

Procedure

1. If you want to start the installation of the target host using the migration monitor, make sure thatat least the dump directory with the following files is accessible on the target host and containcorrect data before you start SAPinst:n <dump dir>/LABEL.ASCn <dump dir>/DB/<DBTYPE>/DBSIZE.XMLn <dump dir>/DB/DDLORA.TPLIf the dump directory is not shared on the target host, you can copy the files as soon as theyhave been created on the source host with the (export) migration monitor’s FTP Copy optionsfrom the source system to the target system.

2. You start SAPinst as described in the installation documentation for your SAP component.3. 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 StandardSystem Copy/Migration (R3load-Based).

4. Select the option Use Migration Monitor.

Note

If you need more information about input parameters, position the cursor on the field of therespective parameter and press F1.

5. When SAPinst displays the CD browser-window and asks for the Export Migration CD, enter the pathto the export directory <EXPDIR>.

6. Continue as described in the installation documentation for your SAP component until a dialogbox 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. Check that the prerequisites in the dialog box are fulfilled by your system. If so, you can start theMigration Monitor.

8. 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 continues withthe table that was not imported successfully.

150/168 PUBLIC 03/12/2009

7 Additional Information7.2 Using SAPinst GUI

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 Description

Function key F1 Displays detailed information about each input parameter.

Menu option File Log off Stops the SAPinst GUI, but SAPinst and the GUI server continuerunning.

NoteIf for some reason you need to log off during the installationfrom the host where you control the installation with SAPinstGUI, the installation continues while you are logged off. You canlater reconnect to the same SAPinst installation from the same oranother host. For more information, see Starting SAPinst GUI Separately[page 156].

Menu option File View Log Displays the installation log (sapinst_dev.log)

Menu option File Exit Cancels the installation with the following options:n Stop

For more information, see the description of the message buttonbelow.

n ContinueFor more information, see the description of the message buttonbelow.

Message button Retry Performs the installation step again (if an error has occurred).

Message button View Log Displays the installation log (sapinst_dev.log)

Message button Stop Stops the installation (SAPinst GUI, SAPinst and the GUI server)without further changing the installation files. You can continue theinstallation later from this point.

Message button Continue Continues with the option you have chosen before.

7.3 Interrupted Installation with SAPinst

The SAP system installation might be interrupted for one of the following reasons:

n An error occurred during the dialog or processing phase:SAPinst does not abort the installation in error situations. If an error occurs, the installation pausesand a dialog box appears. The dialog box contains a short description about the choices listed inthe table below as well as a path to a log file that contains detailed information about the error.

n You interrupted the installation by choosing Exit in the SAPinst menu.

03/12/2009 PUBLIC 151/168

7 Additional Information7.3 Interrupted Installation with SAPinst

The following table describes the options in the dialog box:

Option Definition

Retry SAPinst retries the installation from the point of failure without repeatingany of the previous steps.This is possible because SAPinst records the installation progress in thekeydb.xml file.We recommend that you view the entries in the log files, try to solve theproblem and then choose Retry.If the same or a different error occurs again, SAPinst displays the samedialog box again.

Stop SAPinst stops the installation, closing the dialog box, the SAPinst GUI, andthe GUI server.SAPinst records the installation progress in the keydb.xml file. Therefore,you can continue the installation from the point of failure withoutrepeating any of the previous steps. See the procedure below.

Continue SAPinst continues the installation from the current point.


Note

You can also terminate SAPinst by choosing Ctrl + C . However, we do not recommend that youuse Ctrl + C , because this kills the process immediately.

End of: UNIX

ProcedureThis procedure describes the steps to restart an installation, which you stopped by choosing Stop, orto continue an interrupted installation after an error situation.

1.


Log on as a user who is a member of the local administrators group.End of: Windows

2.


Log on to your local UNIX host as user root.

Caution

Make sure that the root user has not set any environment variables for a different SAP system ordatabase.

End of: UNIX

152/168 PUBLIC 03/12/2009

7 Additional Information7.3 Interrupted Installation with SAPinst

3.


Insert the Installation Master DVD in your DVD drive.End of: Windows

4.

Only valid for: Unix

Mount your Installation Master DVD.

Note

Mount the DVD locally. We do not recommend using Network File System (NFS).

End of: Unix

5.


Change to the required directory<DVD drive>:\IM_WINDOWS_<platform>

Double-click sapinst.exe

End of: Windows

6.

Only valid for: Unix

Enter the following commands:cd <Installation_Master_DVD>/IM_<OS>

./sapinst

End of: Unix

7.


Check if a SAPinst GUI Java process is still running.If a process is still running, look for javaw.exe under Processes in your Task Manager and kill it.n If you used the default installation directory (recommended):

cd <Mapped_Drive>:\<Copied Installation Master DVD>\IM_OS400_PPC64

sapinst.exe

n If you used an alternative installation directory:cd <Mapped_Drive>:\<your installation directory>

<Mapped_Drive>:\<Copied Installation Master DVD>\IM_OS400_PPC64\sapinst.exe

End of: IBM i5/OS

8. From the tree structure in theWelcome screen, select the installation service that you want tocontinue and choose Next.

Note

If there is only one component to install, theWelcome screen does not appear.

TheWhat do you want to do? screen appears.9. In theWhat do you want to do? screen, decide between the following alternatives and confirm with OK.

03/12/2009 PUBLIC 153/168

7 Additional Information7.4 Performing a Remote Export Using SAPinst

Alternative Behavior

Run a new Installation SAPinst does not continue the interrupted installation. Instead, it movesthe content of the old installation directory and all installation-specificfiles to the backup directory. Afterwards, you can no longer continuethe old installation.For the backup directory, the following naming convention is used:<log_day_month_year_hours_minutes_seconds> (for example,log_01_Oct_2003_13_47_56).

Continue old installation SAPinst continues the interrupted installation from the point of failure.

7.4 Performing a Remote Export Using SAPinst

Purpose

You can run the SAPinst GUI in standalone mode to perform a remote export.This enables you to perform the export on another host (the remote host) while monitoring theexport with the SAPinst GUI on your local Windows or UNIX computer (the local host).

Prerequisites

n Make sure that you have performed the preparation activities for your local host (SAPinst GUIhost) and your remote host as described in Prerequisites in Exporting the Source System Using SAPinst[page 37].

n Both computers are in the same network and can ping each other.To test this:l Log on to your remote host and enter the command ping <local host>.l Log on to the local host and enter the command ping <remote host>.

Process Flow

1. You start the SAPinst server on your remote host.2. You start the SAPinst GUI on your local host.3. You perform the installation using the SAPinst GUI.

For more information, see:

n Starting SAPinst on the Remote Host [page 155]n Starting SAPinst GUI Separately [page 156]

154/168 PUBLIC 03/12/2009


7.4.1 Performing a Remote Installation with SAPinst(Optional)

You use this procedure to install your SAP system on a remote host. In this case, SAPinst and theGUI server run on the remote host, and SAPinst GUI runs on the local host. The local host is thehost from which you control the installation with SAPinst GUI.

Only valid for: SAP CRM;SAP SCM;SAP SRM SAP CRM 5.2;SAP SCM 5.1;SAP SRM Server 6.0

You can run SAPinst GUI on a PC with 32-bit while SAPinst is running on a 64-bit installation host.End of: SAP CRM;SAP SCM;SAP SRM SAP CRM 5.2;SAP SCM 5.1;SAP SRM Server 6.0


Caution

If you install SAP instances on System i, “local host” in this section refers to the Windows installationhost, not the System i host.


Prerequisites

n Both computers are in the same network and can “ping” each other.To test this:l Log on to your remote host and enter the command ping <local host>.l Log on to the local host and enter the command ping <remote host>.

Procedure

Only valid for: IBM i5/OS;Windows

1. Log on to your remote host as a user who is a member of the local administrators group.2. Insert the Installation Master DVD in the DVD drive on your remote host.3. Open a command prompt and change to the required directory of the installation Master DVD.

Enter the following commands:

Only valid for: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle

<DVD drive:\>cd <DVD drive>:\IM_WINDOWS_<platform>

End of: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle

Only valid for: IBM DB2 for i5/OS (Linux/Windows)

cd <mapped drives>:\IM_OS400_PPC64

End of: IBM DB2 for i5/OS (Linux/Windows)

sapinst.exe -nogui

For more information, see Running SAPinst on UNIX or Windows to Perform the Export [page 37].

03/12/2009 PUBLIC 155/168


SAPinst now starts and waits for the connection to the SAPinst GUI. You see the following atthe command prompt:guiengine: no GUI connected; waiting for a connection on host <host_name>, port

<port_number> to continue with the installation

4. Start SAPinst GUI on your local host as described in Starting SAPinst GUI Separately [page 156].

End of: IBM i5/OS;Windows


1. Log on to your remote host as user root.

Caution


2. Mount the Installation Master DVD.3. Enter the following commands:

cd <Installation_Master_DVD>/IM_<OS>

./sapinst -nogui

For more information, see Running SAPinst on UNIX or Windows to Perform the Export [page 37].SAPinst now starts and waits for the connection to the SAPinst GUI. You see the following atthe command prompt:guiengine: no GUI connected; waiting for a connection on host <host_name>, port

<port_number> to continue with the installation.

4. Start SAPinst GUI on your local host as described in Starting SAPinst GUI Separately [page 156].

End of: UNIX

Only valid for: IBM i5/OS;UNIX;Windows

7.4.2 Starting SAPinst GUI Separately (Optional)

You use this procedure to start SAPinst GUI separately. You might need to start SAPinst GUIseparately in the following cases:

n You have logged off from SAPinst.If you logged off during the installation and you later want to reconnect to the installation while itis still running, you can start SAPinst GUI separately.

n You want to perform a remote installation [page 155].If you want to run SAPinst GUI on a different host from SAPinst and the GUI server, you have tostart SAPinst GUI separately.

156/168 PUBLIC 03/12/2009


Only valid for: SAP CRM;SAP SCM;SAP SRM SAP CRM 5.2;SAP SCM 5.1;SAP SRM Server 6.0

You can run SAPinst GUI on a PC with 32-bit while SAPinst is running on a 64-bit installation host.End of: SAP CRM;SAP SCM;SAP SRM SAP CRM 5.2;SAP SCM 5.1;SAP SRM Server 6.0


Caution

If you install SAP instances on System i, “local host” in this section means the Windows installationhost, not the System i host.


PrerequisitesYou have installed the Java Development Kit [page 24] on the host on which you want to start SAPinstwithout SAPinst GUI.

Starting SAPinst GUI on a Windows Platform

1. Log on as a member of the local administrators group.2. Insert the SAP Installation Master DVD into your DVD drive.3. Open a command prompt and change to the relevant directory:

Only valid for: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle

<DVD drive>:\IM_WINDOWS_<platform>

End of: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle

Only valid for: IBM DB2 for i5/OS;IBM DB2 for i5/OS (Linux/Windows)

cd <mapped drives>:\IM_OS400_PPC64

End of: IBM DB2 for i5/OS;IBM DB2 for i5/OS (Linux/Windows)

4. Start SAPinst GUI in one of the following ways:n 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.n 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.

03/12/2009 PUBLIC 157/168


Note

l If you enter the command without additional parameters, SAPinst GUI uses the local hostas default. SAPinst GUI starts and tries to connect to the GUI server and SAPinst. SinceSAPinst and the GUI server are running on another host, SAPinst GUI cannot connect andthe 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 installationfrom your local host.

l For a list of options to start SAPinst GUI, change to the same directory as your SAPinstexecutable and enter the command startinstgui.bat -h.

Starting SAPinst GUI on a UNIX Platform

1. Log on as user root.

Caution


2. Mount your installation DVD.

Note

Mount the DVD locally. We do not recommend that you use Network File System (NFS).

3. To change to the mount directory enter the following command:cd <Installation_Master_DVD>/IM_<OS>

4. Start the SAPinst GUI in one of the following ways:n If SAPinst GUI runs on the same host as SAPinst and the GUI server, enter the following

command without additional parameters:./startInstGui.sh

SAPinst GUI uses as default the local host.n 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.

158/168 PUBLIC 03/12/2009


Note

l If you enter the command without additional parameters, SAPinst GUI uses the local hostas default. SAPinst GUI starts and tries to connect to the GUI server and SAPinst. SinceSAPinst and GUI server are running on another host, SAPinst GUI cannot connect and theSAP 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 installationfrom your local host.

l For a list of options to start SAPinst GUI, change to the same directory as your SAPinstexecutable and enter the command ./startInstGui.sh -h.

End of: IBM i5/OS;UNIX;Windows

03/12/2009 PUBLIC 159/168

Typographic Conventions

Example Description

<Example> Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system, for example, “Enter your <User Name>”.

ExampleExample

Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

http://www.sap.com Textual cross-references to an internet address

/example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

Example n Words or characters quoted from the screen. These include field labels, screen titles,pushbutton labels, menu names, and menu options.

n Cross-references to other documentation or published works

Example n Output on the screen following a user action, for example, messagesn Source code or syntax quoted directly from a programn File and directory names and their paths, names of variables and parameters, and

names of installation, upgrade, and database tools

EXAMPLE Technical names of system objects. These include report names, program names,transaction codes, database table names, and key concepts of a programming languagewhen they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

160/168 PUBLIC 03/12/2009

http://www.sap.com



SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +49/18 05/34 34 34F +49/18 05/34 34 20

www.sap.com

© Copyright 2009 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors.Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10,z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States and/or other countries.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registeredtrademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium,Massachusetts Institute of Technology.Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implementedby Netscape.SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world. All other product and service names mentioned are thetrademarks of their respective companies. Data contained in this document serves informational purposes only. Nationalproduct specifications may vary.These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies(“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall notbe liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services, if any. Nothing hereinshould be construed as constituting an additional warranty.

This document was created using stylesheet 2007-12-10 (V7.2) / XSL-FO: V5.1 Gamma and XSLT processor SAXON 6.5.2from Michael Kay (http://saxon.sf.net/), XSLT version 1.

03/12/2009 PUBLIC 161/168

DisclaimerSome components of this product are based on Java™. Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited, as is any decompilation of these components.Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified oraltered in any way.

Legal Software Terms

Terms for Included Open Source SoftwareThis SAP software contains also the third party open source software products listed below. Note that for these third partyproducts the following special terms and conditions shall apply.

1. This software was developed using ANTLR.

2. SAP License Agreement for STLportSAP License Agreement for STLPort betweenSAP AktiengesellschaftSystems, Applications, Products in Data ProcessingDietmar-Hopp-Allee 1669190 Walldorf, Germany(hereinafter: SAP)andyou(hereinafter: Customer)

a) Subject Matter of the Agreement

A) SAP grants Customer a non-exclusive, non-transferable, royalty-free license to use the STLport.org C++ library(STLport) and its documentation without fee.

B) By downloading, using, or copying STLport or any portion thereof Customer agrees to abide by the intellectualproperty laws, and to all of the terms and conditions of this Agreement.

C) The Customer may distribute binaries compiled with STLport (whether original or modified) without anyroyalties or restrictions.

D) Customer shall maintain the following copyright and permissions notices on STLport sources and itsdocumentation unchanged: Copyright 2001 SAP AG

E) The Customer may distribute original or modified STLport sources, provided that:n The conditions indicated in the above permissions notice are met;n The following copyright notices are retained when present, and conditions provided in accompanying

permission notices are met:Copyright 1994 Hewlett-Packard CompanyCopyright 1996,97 Silicon Graphics Computer Systems Inc.Copyright 1997 Moscow Center for SPARC Technology.Copyright 1999,2000 Boris FomitchevCopyright 2001 SAP AG

Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes ishereby granted without fee, provided that the above copyright notice appear in all copies and that both thatcopyright notice and this permission notice appear in supporting documentation. Hewlett-Packard Companymakes no representations about the suitability of this software for any purpose. It is provided “as is” withoutexpress or implied warranty.Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose ishereby granted without fee, provided that the above copyright notice appear in all copies and that both that

162/168 PUBLIC 03/12/2009

copyright notice and this permission notice appear in supporting documentation. Silicon Graphics makes norepresentations about the suitability of this software for any purpose. It is provided “as is” without express orimplied warranty.Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes ishereby granted without fee, provided that the above copyright notice appear in all copies and that both thatcopyright notice and this permission notice appear in supporting documentation. Moscow Center for SPARCmakes no representations about the suitability of this software for any purpose. It is provided “as is” withoutexpress or implied warranty.Boris Fomitchev makes no representations about the suitability of this software for any purpose. This material isprovided "as is", with absolutely no warranty expressed or implied. Any use is at your own risk. Permission to useor copy this software for any purpose is hereby granted without fee, provided the above notices are retained on allcopies. Permission to modify the code and to distribute modified code is granted, provided the above notices areretained, and a notice that the code was modified is included with the above copyright notice.Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes ishereby granted without fee, provided that the above copyright notice appear in all copies and that both thatcopyright notice and this permission notice appear in supporting documentation. SAP makes no representationsabout the suitability of this software for any purpose. It is provided with a limited warranty and liability as setforth in the License Agreement distributed with this copy. SAP offers this liability and warranty obligations onlytowards its customers and only referring to its modifications.

b) Support and MaintenanceSAP does not provide software maintenance for the STLport. Software maintenance of the STLport thereforeshall be not included.All other services shall be charged according to the rates for services quoted in the SAP List of Prices and Conditionsand shall be subject to a separate contract.

c) Exclusion of warrantyAs the STLport is transferred to the Customer on a loan basis and free of charge, SAP cannot guarantee that theSTLport is error-free, without material defects or suitable for a specific application under third-party rights.Technical data, sales brochures, advertising text and quality descriptions produced by SAP do not indicate anyassurance of particular attributes.

d) Limited Liability

A) Irrespective of the legal reasons, SAP shall only be liable for damage, including unauthorized operation, 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.

B) If SAP is liable for gross negligence or intent caused by employees who are neither agents or managerialemployees of SAP, the total liability for such damage and a maximum limit on the scope of any such damage shalldepend on the extent to which its occurrence ought to have anticipated by SAP when concluding the contract,due to the circumstances known to it at that point in time representing a typical transfer of the software.

C) In the case of Art. 4.2 above, SAP shall not be liable for indirect damage, consequential damage caused by adefect or lost profit.

D) SAP and the Customer agree that the typical foreseeable extent of damage shall under no circumstances exceedEUR 5,000.

E) The Customer shall take adequate measures for the protection of data and programs, in particular by makingbackup copies at the minimum intervals recommended by SAP. SAP shall not be liable for the loss of data andits recovery, notwithstanding the other limitations of the present Art. 4 if this loss could have been avoided byobserving this obligation.

F) The exclusion or the limitation of claims in accordance with the present Art. 4 includes claims against employeesor agents of SAP.

3. Adobe Document Services

03/12/2009 PUBLIC 163/168

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either registered trademarks or trademarks of Adobe SystemsIncorporated in the United States and / or other countries. For information on Third Party software delivered withAdobe document services and Adobe LiveCycle Designer, see SAP Note 854621.

4.

Only valid for: SAP ERP;SAP CRM

Apache License, Version 2.0

a) Definitions:n "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections

1 through 9 of this document.n "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the

License.n "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or

are under common control with that entity. For the purposes of this definition, "control" means (i) the power,direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii)ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.

n "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.n "Source" form shall mean the preferred form for making modifications, including but not limited to software

source code, documentation source, and configuration files.n "Object" form shall mean any form resulting frommechanical transformation or translation of a Source form,

including but not limited to compiled object code, generated documentation, and conversions to other mediatypes.

n "Work" shall mean the work of authorship, whether in Source or Object form, made available under theLicense, as indicated by a copyright notice that is included in or attached to the work (an example is providedin the Appendix below).

n "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from)the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, asa whole, an original work of authorship. For the purposes of this License, Derivative Works shall not includeworks that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and DerivativeWorks thereof.

n "Contribution" shall mean any work of authorship, including the original version of the Work and anymodifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensorfor inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit onbehalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic,verbal, or written communication sent to the Licensor or its representatives, including but not limited tocommunication on electronic mailing lists, source code control systems, and issue tracking systems that aremanaged by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excludingcommunication that is conspicuously marked or otherwise designated in writing by the copyright owner as"Not a Contribution."

n "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution hasbeen received by Licensor and subsequently incorporated within the Work.

b) Grant of Copyright LicenseSubject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide,non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of,publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source orObject form.

c) Grant of Patent LicenseSubject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide,non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, havemade, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to thosepatent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or bycombination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institutepatent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a

164/168 PUBLIC 03/12/2009


Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patentlicenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.

d) RedistributionYou may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or withoutmodifications, and in Source or Object form, provided that You meet the following conditions:

A) You must give any other recipients of the Work or Derivative Works a copy of this License; and

B) You must cause any modified files to carry prominent notices stating that You changed the files; and

C) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent,trademark, and attribution notices from the Source form of the Work, excluding those notices that do notpertain to any part of the Derivative Works; and

D) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distributemust include a readable copy of the attribution notices contained within such NOTICE file, excluding thosenotices that do not pertain to any part of the Derivative Works, in at least one of the following places: withina NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, ifprovided along with the Derivative Works; or, within a display generated by the Derivative Works, if and whereversuch third-party notices normally appear. The contents of the NOTICE file are for informational purposes onlyand do not modify the License. You may add Your own attribution notices within Derivative Works that Youdistribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additionalattribution notices cannot be construed as modifying the License.

You may add Your own copyright statement to Your modifications and may provide additional or different licenseterms and conditions for use, reproduction, or distribution of Your modifications, or for any such DerivativeWorks as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with theconditions stated in this License.

e) Submission of ContributionsUnless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You tothe Licensor shall be under the terms and conditions of this License, without any additional terms or conditions.Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreementyou may have executed with Licensor regarding such Contributions.

f) TrademarksThis License does not grant permission to use the trade names, trademarks, service marks, or product names of theLicensor, except as required for reasonable and customary use in describing the origin of the Work and reproducingthe content of the NOTICE file.

g) Disclaimer of WarrantyUnless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor providesits Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, eitherexpress or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT,MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determiningthe appropriateness of using or redistributing the Work and assume any risks associated with Your exercise ofpermissions under this License.

h) Limitation of LiabilityIn no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unlessrequired by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall anyContributor be liable to You for damages, including any direct, indirect, special, incidental, or consequentialdamages of any character arising as a result of this License or out of the use or inability to use the Work (includingbut not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and allother commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.

i) Accepting Warranty or Additional Liability

03/12/2009 PUBLIC 165/168

While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptanceof support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, inaccepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf ofany other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for anyliability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty oradditional liability.

End of: SAP ERP;SAP CRM

Documentation in the SAP Service MarketplaceYou can find this document at the following address: https://service.sap.com/instguides

166/168 PUBLIC 03/12/2009

https://service.sap.com/instguides




SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

© Copyright 2009 SAP AG. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may bechanged without prior notice.

Documents

Netweaver 7.0 SR3 abap java system copy guide