SAP Systems Based on the Application Server

SAP Systems Based on the Application Server
Operations Guide
CUSTOMER
Software Provisioning Manager 1.0
Document Version: 2.5 – 2017-05-22
System Copy for SAP Systems Based on the
Application Server Java of SAP NetWeaver 7.0 to
7.03 on IBM i
Content
1
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.1
Homogeneous and Heterogeneous System Copy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.2
Naming Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3
New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
1.4
Accessing the SAP Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.5
Constraints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2
Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.1
Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
2.2
Before You Start. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.3
Use Cases for System Copy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.4
System Copy Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.5
Creating A System Copy Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
2.6
Various Planning Aspects and Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.7
System Copy and Migration Optimization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Database Tuning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Package Splitting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Table Splitting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Migration Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Database-Specific Central Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3
Preparations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
3.1
Preparations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.2
General Technical Preparations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.3
Preparation for IBM i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Preparing an IBM i User Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Enable the User QSECOFR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.4
Preparing the Media Required for Performing the Export. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Downloading and Extracting the Software Provisioning Manager Archive. . . . . . . . . . . . . . . . . . 27
4
Database Independent System Copy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.1
System Copy Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Exporting the Source System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Setting Up the Target System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
5
Database-Specific System Copy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
5.1
IBM DB2 for i Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
6
Follow-Up Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
2
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Content
7
Performing Follow-Up Activities in the Target System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
7.1
Installing the License Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
7.2
SAP Solution Manager: Connection Between SLD and LMDB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
7.3
Performing Follow-Up Activities for Java. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
7.4
General Follow-Up Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Configuration Steps for the SAP Java Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Generating Public-Key Certificates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
7.5
Usage Type or Software Unit-Specific Follow-Up Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
EP Core (EPC). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Enterprise Portal (EP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Business Intelligence Java Components (BI Java). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87
Development Infrastructure (DI). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Self Services (XSS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
CRM Java Components (JCRM) / Extended E-Selling Components (XECO). . . . . . . . . . . . . . . . 92
MapBox. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
SRM Live Auction Cockpit (SRMLAC). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
SCM Forecasting & Replenishment Processor (SCM FRP). . . . . . . . . . . . . . . . . . . . . . . . . . . . .93
8
Additional Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
8.1
Copying the Installation Media Manually to Your IBM i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
8.2
Jload Procedures Using the Java Migration Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
About the Java Migration Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Configuration for Using the Java Migration Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97
Starting the Java Migration Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Output Files of the Java Migration Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Restarting Jload Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
8.3
Analysis of the Export and Import Times. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
8.4
Package and Table Splitting for Java Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
8.5
Configuration for Using the Java Splitter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
8.6
Starting the Java Splitter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
8.7
Output Files of the Java Splitter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
8.8
Removing the Installation Files of the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
8.9
Verifying and Adjusting the instanceID of an AS Java Instance. . . . . . . . . . . . . . . . . . . . . . . . . . 111
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Content
CUSTOMER
3
Document History
Note
Before you start the implementation, make sure you have the latest version of this document, which is
available at https://support.sap.com/sltoolset
System Provisioning .
The following table provides an overview on the most important document changes:
Table 1:
Version
Date
Description
2.5
2017-05-22
Updated version for software provi­
sioning manager 1.0 SP20 (SL Toolset
1.0 SP20)
2.4
2017-02-06
Updated version for software provi­
sioning manager 1.0 SP19 (SL Toolset
1.0 SP19)
2.3
2016-10-07
Updated version for software provi­
sioning manager 1.0 SP18 (SL Toolset
1.0 SP18)
2.2
2016-06-06
Updated version for software provi­
sioning manager 1.0 SP17 (SL Toolset
1.0 SP17)
2.1
2016-02-15
Updated version for software provi­
sioning manager 1.0 SP10 (SL Toolset
1.0 SP16)
2.01
2015-10-12
Updated version for software provi­
sioning manager 1.0 SP09 (SL Toolset
1.0 SP15)
2.0
2015-10-12
Updated version for software provi­
sioning manager 1.0 SP09 (SL Toolset
1.0 SP15)
1.9
2015-09-14
Updated version for software provi­
sioning manager 1.0 SP09 (SL Toolset
1.0 SP14)
1.8
4
2015-04-27
CUSTOMER
Updated version for software provi­
sioning manager 1.0 SP08 (SL Toolset
1.0 SP13)
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Document History
Version
Date
Description
1.7
2014-11-24
Updated version for software provi­
sioning manager 1.0 SP07 (SL Toolset
1.0 SP12)
1.6
2014-07-07
Updated version for software provi­
sioning manager 1.0 SP06 (SL Toolset
1.0 SP11)
1.5
2014-03-17
Updated version for software provi­
sioning manager 1.0 SP05 (SL Toolset
1.0 SP10 )
1.4
2014-03-05
Updated Version
1.3
2013-11-22
Updated version
1.2
2013-10-28
Updated version
1.1
2013-08-19
Updated version
1.0
2013-07-17
Initial version
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Document History
CUSTOMER
5
1
Introduction
1.1
Homogeneous and Heterogeneous System Copy
This document describes how to perform a homogeneous or heterogeneous system copy of an SAP system
based on SAP NetWeaver 7.0 (including Enhancement Packages) Java with source operating system IBM i,
using Software Provisioning Manager 1.0 SP20.
The following target databases are supported:
● IBM DB2 for i
● IBM DB2 for Linux, UNIX, and Windows
● IBM DB2 for z/OS
● SAP MaxDB
● Oracle
● MS SQL Server
● SAP ASE
You can use either database-specific methods or database-independent methods.
For a detailed list of supported SAP system products and releases, see SAP Note 1738258 . For information
about supported operating system and database platforms, see the Product Availability Matrix at http://
support.sap.com/pam .
Note
Not all SAP NetWeaver releases or SAP Business Suite applications that are available in Software
Provisioning Manager 1.0 and are described in this guide might have been released already. Always check
SAP Note 1680045
to ensure that the system copy options you want to perform are already supported.
1.2
Naming Conventions
● Software Provisioning Manager 1.0
Software provisioning manager is the successor of the product- and release-specific delivery of
provisioning tools, such as SAPinst. Before you perform an installation or system copy, we recommend
that you always download the latest version of the software provisioning manager, which is part of the
Software Logistics Toolset (“SL Toolset” for short). This way, you automatically get the latest SAPinst
version including latest fixes in the tool and supported processes. For more information about software
provisioning manager as well as products and releases supported by it, see SAP Note 1680045 .
SAPinst has therefore been renamed to software provisioning manager 1.0 (“installer” for short)
in this documentation. However, the term “SAPinst” is still used in:
○ Texts and screen elements in the software provisioning manager (“installer”) GUI
6
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Introduction
○ Naming of executables, for example sapinst
○ Naming of command line parameters, for example SAPINST_USE_HOSTNAME
○ Operating system user groups, for example additional group sapinst
In the following, we generally refer to software provisioning manager 1.0 as the “installer”. We
only use the term “software provisioning manager” if this is required for technical reasons.
● System Copy
Duplication of an SAP system. The SAP system ID and certain other SAP parameters might be changed in
a copy. When you perform a system copy, the tool installs all the instances again, but it uses a copy of the
source system database to set up the database.
The following use cases are possible:
○ Initial System Copy
The tool newly installs all the instances of a source system, but it uses a copy of the source system
database to set up the database in the target system.
○ Refresh
Overwriting of an already existing target system with the database content from a source system.
The refresh use case is not supported using the software provisioning manager.
● Homogeneous System Copy
During the system copy, you use the same operating system and database platform as the original
system.
● Heterogeneous System Copy
During the system copy, you change either the operating system or the database system, or both.
Heterogeneous system copy is a synonym for migration.
● Source System and Target System
The SAP system containing the original database is called the source system and the system to which the
database copy is to be imported is called the target system. Their SAP system names are abbreviated to
SOURCE_SAPSID and TARGET_SAPSID. The terms source database and target database are also used in
this description.
● Database Copy
Database-dependent part of the system copy.
● Placeholders
Placeholders such as <SAPSID> are used in commands. They are used in the same way as in the SAP
system installation documentation. You must replace them with the values valid for your site.
The following additional placeholders are used:
Table 2:
Placeholder
Meaning
<SAPSID>
SAP system ID
<S_HOST>
System name of the source host (command hostname)
<T_HOST>
System name of the target host (command hostname)
<S_SAPSID>
SAP system ID <SAPSID> of the source system
<T_SAPSID>
SAP system ID <SAPSID> of the target system
<S_DBSID>
Database ID <DBSID> of the source system
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Introduction
CUSTOMER
7
Placeholder
Meaning
<T_DBSID>
Database ID <DBSID> of the target system
<OS>
Operating system name within a path
<DB>
Database name within a path
<Technology>
ABAP, Java, or ABAP+Java
Note
Database ID <DBSID> identifies the database instance.
<DBSID> and <SAPSID>are always on IBM i the same. These system IDs are often called <SID>.
1.3
New Features
The table below provides an overview of the new features in Software Provisioning Manager.
Make sure that you also read the release notes for your SAP product at http://help.sap.com
<Product>
Area>
<Release>
<Product
What’s New – Release Notes .
Table 3:
Feature
Description
Availability
SL Common GUI with With the new installer framework version SAPINST 7.49, you can now use the
SAPINST 7.49
new SAPUI5-based graphical user interface (GUI) “SL Common GUI”. For
more information, see Useful Information About the Installer [page 40],
Running the Installer [page 35], and SAP Note 2336746
Cleanup of Operating
System Users
.
You can now specify during the Define Parameters phase that the group
SAPINST is to be removed from the operating system users after the execu­
tion of the installer has completed.
Verification of Integ­
rity of Data Units in
Software Provision­
ing Manager
The integrity of data units extracted from the Software Provisioning Manager
archive is verified. For more information, see Downloading and Extracting the
Software Provisioning Manager Archive [page 27].
In addition, check SAP Note 1680045
Software Provi­
sioning Manager
1.0 SP20 (SL Tool­
set 1.0 SP20)
Software Provi­
sioning Manager
1.0 SP20 (SL Tool­
set 1.0 SP20)
Software Provi­
sioning Manager
1.0 SP19 (SL Tool­
set 1.0 SP19)
whether additional information is
available.
8
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Introduction
Feature
Description
Availability
Adjust instanceID of
An inconsistency of the instanceID parameter is caused by using an unsup­
Software Provi­
an SAP Java System
ported procedure to create or maintain the system. When instanceID is not
sioning Manager
consistent, future running of software logistscs scenarios, such as system
1.0 SP10 (SL Tool­
copy, system rename, dual-stack split, upgrade, and so on might fail. The op­
set 1.0 SP16)
tion Adjust instanceID for a Java System helps you to overcome this. It is avail­
able in Software Provisioning Manager as option
Additional Preparation Options
Options
System
Software Life-Cycle
Adjust instanceID for a Java
.
For more information, see Verifying and Adjusting the instanceID of an AS
Java Instance [page 111].
Diagnostics Agent
The Diagnostics Agent is no longer installed automatically with the SAP sys­
Software Provi­
tem. The Install Diagnostics Agent check box on the Install Diagnostics Agent
sioning Manager
screen is no longer available.
1.0 SP10 (SL Tool­
You now have to install the Diagnostics Agent always separately. We recom­
set 1.0 SP16)
mend that you install it prior to the installation of your SAP system(s).
For more information, see the Diagnostics Agent Installation Strategy at­
tached to SAP Note 1365123
1858920
, to SAP Note 1833501
, and to SAP Note
and the attached Diagnostics Agent Setup Guide.
Executing R3szchk
You can now execute R3szchk in parallel. Using this feature you can improve
Software Provi­
in Parallel
the runtime of the export.
sioning Manager
1.0 SP08 (SL Tool­
set 1.0 SP13)
Feedback Evaluation
SAP SE’s aim is to provide fast and efficient procedures. To evaluate the pro­
Software Provi­
Form available in the
cedure you just carried out, we need information generated by the tool during
sioning Manager
Software Provision­
process execution and your experience with the tool itself. A new evaluation
1.0 SP07 (SL Tool­
ing Manager:
form contains a simple questionnaire and XML data generated during the pro­ set 1.0 SP12)
cedure.
Port 4239 is used for displaying the feedback evaluation form. For more infor­
mation, see the Prerequisites section in Running the Installer [page 35].
Automatic user
The installer checks if the user QSECOFR and the IBM i installation user are
check of the
prepared correctly. Only if the installer detects an inconsistency, then a dialog sioning Manager
QSECOFR and the
screen appears.
IBM i installation user
For more information about how to prepare these users, see Preparing an
Software Provi­
1.0 SP20 (SL Tool­
set 1.0 SP20)
IBM i User Profile [page 24] and Enable the User QSECOFR [page 25] .
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Introduction
CUSTOMER
9
1.4
Accessing the SAP Library
The references to the SAP NetWeaver Library documentation in this guide always refer to the following on the
SAP Help Portal:
● SAP NetWeaver 7.0:
http://help.sap.com/nw70
● SAP NetWeaver 7.0 including Enhancement Package 1:
http://help.sap.com/nw701
● SAP NetWeaver 7.0 including Enhancement Package 2:
http://help.sap.com/nw702
● SAP NetWeaver 7.0 including Enhancement Package 3:
http://help.sap.com/nw703
1.5
Constraints
● Only perform a system copy if you have experience in copying systems and thorough knowledge of the
operating system, the database, and the Java Dictionary . Only perform a heterogeneous system copy (of
a production, development, or test (QA) system) if you are a certified system support consultant or a
certified SAP Technical Consultant.
● The target system installation consists of both the target database and target instance/application server
installations. For the scenarios below, the following holds:
○ Refreshing the database is not supported. Refreshing the database means that only the database is
loaded with the content of a database of a different system. Since no migration controller is invoked in
this scenario, this is not supported.
○ Option Generic Installation Options
systems.
Refresh Database Content is not supported for Java
○ Copying only the database is not supported.
○ Copying only the central instance - that means source and target system are identical - is not
supported if the system has dialog instances. The migration controller deletes all dialog instances in
the database, so the system is not complete any longer.
Make sure that the export is consistent with the database. For example, the system must not be online
during the period between when you start exporting the source central instance and when you install
the target central instance.
○ Reinstalling the central instance using option Central Instance in the Target System Installation folder
without the database is not supported if the system has dialog instances. The migration controller
deletes all dialog instances in the database, so the system is not complete any longer.
This might even cause additional problems. For more information, see SAP Note 966752 .
10
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Introduction
●
Caution
SAP is going to restrict maintenance for operating system versions that have been initially released with
SAP kernel 7.2<X> but are no longer supported for SAP kernel 7.40 and higher. The following Software
Provisioning Manager operating system versions are affected:
○ IBM i: < 7.1
With the release of Software Provisioning Manager 1.0 SPS 18, the 70SWPM*.SAR archive will stop
working on the above listed outdated operating system versions.
Instead of using the 70SWPM*.SAR archive, you must use the RMOS70SWPM*.SAR archive for these
outdated operating system versions.
Keep in mind that the RMOS70SWPM*.SAR archive will not receive improvements in the future. SAP
maintenance for RMOS70SWPM*.SAR will be finally stopped by the end of 2017.
SAP recommends upgrading the operating system to a more recent version and using
RMOS70SWPM*.SAR to export from existing SAP systems.
● System copy is not supported for the Diagnostics Agent.
For more information and guidance see the Diagnostics Agent Maintenance Procedures article at http://
wiki.scn.sap.com/wiki/x/n4efFg .
● 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 excluded from the
system copy, nor can you select usage types.
● SAP Solution Manager only:As of Support Release 4, your SAP Solution Manager 7.0 system must be a
dual-stack system if you want to perform a system copy. If required, install a Java Add-In to your existing
ABAP system before you start the export.
● SAP does not support client transport as a system copy method. Transporting production clients is not
supported at all. You can use client transport for the initial setup of an SAP system infrastructure. This
documentation does not cover the client copy procedure.
● This documentation does not describe the following:
○ How to export and import a database with the installation tools for reorganization purposes. Use the
appropriate tools for database reorganization, as SAP does not support this installation option.
○ How to copy data from non-SAP systems to SAP systems based on SAP NetWeaver Application
Server. This documentation only describes how to copy data from one SAP system to another SAP
system.
○ How to perform a duplication of a SAP system on the same host without changing the SAP system ID.
○ How to perform a system refresh using the tool.
● If you have made modifications in your development system and want to copy your quality assurance or
production system onto the development system, see SAP Note 130906 .
● For the development of Java applications, we strongly recommend that you follow the rules mentioned
below. Otherwise, we cannot guarantee that you can copy your Java engine later with the SAP tools to
change your underlying operating system and/or database system.
● SAP does not support all data archiving operations after a system copy.
If you used data archiving in the source or target system, access to the created archive files from the
target system may not always be possible. For more information, see SAP Note 153433
and System
Landscape Optimization at http://service.sap.com/slo .
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Introduction
CUSTOMER
11
Access to archived files from the target system without a dedicated archive migration project is only
supported in the following cases:
○ The system copy is done to provide a source system for nonproductive purposes, for read-only access
to the previously archived data from the target system (no reloading), and you do not store archive
files using ArchiveLink/CMS.
You can either copy all archive files to file systems that are not shared between the source and the
target system, or you arrange network access for appropriate archive file sharing.
○ The system copy is done to replace a productive system with a new productive system (for example,
hardware migration), assuming that the target system did not exist before and the operation of the
source system is discontinued after the system copy.
You must not change the system ID during system copy, but arrange for file access and/or
ArchiveLink/CMS connectivity.
Note
Only valid for SAP NetWeaver Business Warehouse:
If you use ADK-based archiving of request administration data in SAP NetWeaver Business Warehouse,
you have to copy all archive files related to archiving object BWREQARCH to the file system of the
target system. Only then write access (like deletion of requests, deletion of the complete data target
content, further upload of data to other targets, changing the quality status of requests or InfoProvider
rebuild) to requests with archived administration data is possible in the target system of the copy.
In all other cases, contact SAP SLO at http://service.sap.com/slo
slo.consulting@sap.com.
or send an email to
● Dos and Don'ts for system copy:
○ Do:
○ Save configuration data and runtime data in the Java database only. If saving this data to the file
system level is unavoidable, you must use the Software Deployment Manager (SDM) to save the
data.
○ Follow the Open SQL standard.
○ Make sure that all communication runs through the database pool.
○ Don't:
○ Save any system and infrastructure-specific data in business objects. Use a pointer to the central
storage of such information, for example:
○ SAP SystemID and SID (SAPSID=SID=system name)
○ Host name
○ IP addresses
○ Services and ports
○ Logical destinations and logical system names
○ Other technical infrastructure names
○ Use file system persistency.
○ Set up dependencies between Java and ABAP.
○ Try to copy the Java part of an ABAP+Java system to a Java standalone system or vice versa.
● If you have implemented a federated portal network (FPN) across multiple SAP NetWeaver systems, see
SAP Note 1080080
before starting the system copy.
12
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Introduction
2
Planning
2.1
Planning
This section describes how to plan your system copy.
2.2
Before You Start
● The SAP OS/DB Migration Check prepares you in an optimal way for a successful migration and supports
smooth continued operations on the new platform. The OS/DB Migration Check is mandatory, if you are
going to migrate a productive system.
For more information, see https://support.sap.com/support-programs-services/services/os-dbmigration.html . In addition to the information contained on this page, check the SAP OS/DB Migration
Planning Guide that is available in the Media Library.
● Before you start the system copy, you must read the documentation that is referenced in the following:
○ Read the following SAP Notes for up-to-date information on system copy and corrections to the
system copy documentation:
○ SAP Note 1680045
– Release Note for Software Provisioning Manager 1.0
○ SAP Note 1738258
– System Copy of Systems Based on SAP NetWeaver
Make sure that you have the most recent version of the SAP Notes, which you can find at:
http://service.sap.com/notes .
○ Guides for the target system installation
This system copy guide describes only the export of the source system in detail. For the installation of
the target system, you use the installation guide for the database and operating system platform of
your target system. This system copy guide describes only the additional system copy-specific steps
in section Setting Up the Target System [page 53]. You find the target system installation guides at
http://support.sap.com/sltoolset
Provisioning Manager
System Provisioning
System Copy Option of Software
System Copy Guides - Installing the Target System
○ SAP System Copy & Migration at:
http://sdn.sap.com/irj/sdn/systemcopy
.
○ SAP system landscape copy:
○ Best Practice document SAP System Landscape Copy for SAP NetWeaver and SAP Solutions at:
http://service.sap.com/solutionmanagerbp
○ SAP Note 885343
○ SAP Note 1990240
○ SAP Note 82478
– SAP System Landscape Copy
– Support of mixed landscapes (Unicode and Non-Unicode)
SAP System OS/DB Migration
○ If you encounter problems during the system copy, create a customer message using the application
area BC-INS-MIG.
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Planning
CUSTOMER
13
2.3
Use Cases for System Copy
You can apply the system copy for the following:
● Setting up system landscapes (where the SAP systems have different SAPSIDs).
● Providing systems for testing, demonstration, training, and standby.
To create these systems you can either perform an initial system copy or use a database export to
overwrite the database of an already existing target system (refresh use case).
Depending on the purpose of the system, it might be advisable to use the same SAP system ID, even
though this prevents you from including the system in a system group for transports.
Note
You should perform a system copy in a test system first. This way you can identify customer-specific
problems that might result from modifications.
● Changing the operating system, the database, or both.
You can use different operating system releases or database releases for the source and target systems,
but the SAP system release of the source and target systems must be the same.
● Changing the hardware.
2.4
System Copy Methods
You can choose between the following system copy methods:
● The database-independent procedure using SAP tools.
Use this method if database-specific methods are either not available or not suitable. For more
information, see Database-Independent System Copy [page 29].
● The database-specific procedure using tools provided by the database vendor
Some database vendors offer specific tools for copying a database. These tools allow you to:
○ Restore a backup of one database (source database) in another one (target database) (backup
method)
○ Unload the source database and load the data into the target database
For more information, see Database-Specific System Copy [page 57].
14
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Planning
These methods are not supported for all database systems. Refer to the following table to check which copy
methods are available for your database system:
Table 4:
Database
Available Methods
IBM DB2 for i
Use one of the following:
●
System copy procedure on IBM i using Jload
For more information, see Running the Software Provisioning Manager to Perform the
Export [page 35].
●
IBM i-specific procedure for a homogeneous system copy only
For more information, see IBM DB2 for i Procedure [page 58].
For more information, see SAP Note 585277
.
● Development Infrastructure (DI) only:
For the migration of SAP NetWeaver Development Infrastructure (NWDI) components you can apply
either “Copy” or “Move”.
○ Copy
“Copy” is supported only by Design Time Repository (DTR). After a copy, both the source DTR and
target DTR can be used productively in parallel. However, Component Build Service (CBS) and
Change Management Service (CMS) do not support such a copy.
○ Move
“Move” is supported by all NWDI components ‒ DTR, CBS, and CMS. After a move, the source system
can no longer be used ‒ that is, only the target is active after the move has been performed.
2.5
Creating A System Copy Plan
Use
Create a plan to perform the system copy.
Procedure
1. When copying a system that contains production data, choose the moment for the copy carefully. This
could be a month-end or year-end closing.
2. Consider the downtime of the source system (for preparations and copying) when planning the system
copy.
3. Consider a test run.
Perform a test run of the system copy. You can use the time taken by the test run to calculate the system
downtime:
○ If you want your target system to 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 target system,
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Planning
CUSTOMER
15
and imported there. System downtime is approximately equal to the total test time (that is, time for
export, transport, and import).
○ If you do not want to replace your source system, a partial test run (export of the entire database or
parts of it) can be sufficient to calculate the system downtime. The source system is only 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 you only perform read/write
actions on local file systems.
4. Define a schedule for the test migration and the final migration.
2.6
Various Planning Aspects and Parameters
Support of Mixed Landscapes (Unicode and Non-Unicode)
If your system landscape is mixed with Unicode and Non-Unicode systems, or if you have third party software
for potential
in your system landscape which does not support Unicode at all, check SAP Note 1990240
support restrictions.
Using NFS-Mounted File Systems
Note that the overall performance of the system copy depends on all links in the chain, starting from the
performance of the source database to the following:
● Performance of the server on which the export is executed
● File system to which the export data is written
● Target side that reads from the export medium and imports it into the target database
You have to make sure that all aspects are configured for optimal performance. For recommendations on NFS
configuration, see SAP Note 2093132 .
Note
If you want to use NFS for the system copy export, make sure that you create secure file share permissions.
Be aware that the communication protocol for NFS needs to be a safe one, for example SSFS.
Configuration Analysis and Hardware Configuration
● In the event of a major change in hardware configuration (for example, new machine type, new hard disk
configuration, new file system type), consult your SAP-authorized hardware partner.
16
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Planning
● You need to determine the following:
○ Number of application servers
○ Expected size of the database
○ Additional disks or other hardware required
○ Required memory
Note
Refer to the section on hardware and software requirements in the SAP system installation
documentation to determine the system requirements.
Choosing an SAP system ID
You can choose the new SAP system ID <TARGET_SAPSID> freely during a new installation.
Make sure that your SAP system ID:
● Is unique throughout your organization
Do not use an existing <SAPSID> when installing a new SAP system.
● Consists of exactly three alphanumeric characters
● Contains only uppercase letters
● Has a letter for the first character
● Does not include any of the reserved IDs listed in SAP Note 1979280
.
● If you want to install an additional application server instance, make sure that no Gateway instance with
the same SAP System ID (SAPSID) exists in your SAP system landscape.
Caution
To meet the requirements of the Workbench Organizer, you must choose different SAP system IDs for
different SAP systems.
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Planning
CUSTOMER
17
SAP License
Once the installation is completed and the SAP system copy has been imported, you will require a new license
key for the target system. The license key of the source system is not valid for this system. For more
information about ordering and installing the SAP license, see the SAP Library for your release at:
Table 5:
SAP NetWeaver Release
Location
SAP NetWeaver 7.0
http://help.sap.com/nw70
Application Help
Function-Oriented View <Language>
Management by Key Capability
SAP NetWeaver 7.0 including EHP1
SAP Licenses
http://help.sap.com/nw701
SAP NetWeaver 7.0 including EHP2
Solution Life Cycle
SAP Licenses
http://help.sap.com/nw703
.
Application Help
Function-Oriented View <Language>
Management by Key Capability
.
Application Help
Function-Oriented View <Language>
SAP NetWeaver 7.0 including EHP3
Solution Life Cycle
SAP Licenses
http://help.sap.com/nw702
Management by Key Capability
.
Application Help
Function-Oriented View <Language>
Management by Key Capability
Solution Life Cycle
Solution Life Cycle
SAP Licenses
For more information about SAP license keys, see http://support.sap.com/licensekey
.
.
or SAP Note 94998
Archiving files
Data that has been archived in the source system (data that does not reside in the database but was moved to
a different storage location using SAP Archive Management) must be made accessible in the target system.
Adapt the file residence information in the target system. For more information, see the SAP Library for your
release at:
Table 6:
SAP NetWeaver Release
Location
SAP NetWeaver 7.0
http://help.sap.com/nw70
Application Help
Function-Oriented View <Language>
Management by Key Capability
18
CUSTOMER
Solution Life Cycle
Data Archiving
.
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Planning
SAP NetWeaver Release
Location
SAP NetWeaver 7.0 including EHP1
http://help.sap.com/nw701
Application Help
Function-Oriented View <Language>
Management by Key Capability
SAP NetWeaver 7.0 including EHP2
http://help.sap.com/nw702
Data Archiving
SAP NetWeaver 7.0 including EHP3
http://help.sap.com/nw703
Solution Life Cycle
Data Archiving
.
Application Help
Function-Oriented View <Language>
Management by Key Capability
.
Application Help
Function-Oriented View <Language>
Management by Key Capability
Solution Life Cycle
Solution Life Cycle
Data Archiving
.
Access to archive files is platform-independent.
Special Prerequisites for SAP NetWeaver Business Warehouse (SAP
NetWeaver BW) and IBM DB2 for Linux, UNIX, and Windows (DB2 for LUW)
10.5 and higher
For special prerequisites and required procedures for SAP NetWeaver BW and DB2 for LUW, including the
implementation of DB2 BLU acceleration, see the appendix of the database administration guide SAP Business
Warehouse on IBM DB2 for Linux, UNIX, and Windows: Administration Tasks. The guide is available at http://
service.sap.com/instguides
<Your SAP NetWeaver release>
Operations
Database-Specific
Guides .
2.7
System Copy and Migration Optimization
This section lists several methods that you can use to optimize the standard system copy procedure.
Related Information
Database Tuning [page 20]
Package Splitting [page 20]
Table Splitting [page 20]
Migration Monitor [page 20]
Database-Specific Central Notes [page 21]
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Planning
CUSTOMER
19
2.7.1 Database Tuning
This is just a list of database parameters which could help you to tune your database. This list is not meant to
give you detailed recommendations about the parameter settings.
Database Tuning Measures – IBM DB2 for i
Currently there are no recommendations for tuning measures available.
2.7.2 Package Splitting
You can split the default packages EXPORT.XML and IMPORT.XML into several smaller and equal sized
packages using the Java Splitter tool. For more information, see Package and Table Splitting for Java
Tables [page 103].
2.7.3 Table Splitting
For copying large Java tables, you can use the Java Splitter tool.
For more information, see Package and Table Splitting for Java Tables [page 103].
2.7.4 Migration Monitor
Use
The Java Migration Monitor is a tool that helps you to perform and control the unload and load process for the
Java stack during the system copy procedure.
More Information
For more information, see Jload Procedures Using the Java Migration Monitor [page 96]
20
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Planning
2.7.5 Database-Specific Central Notes
For some databases there are central SAP Notes where you can find information about how to optimize
system copy and migration.
● For more information about MS SQL Server-specific migration optimization options, see SAP Note
1054852
(Recommendations for migration to MS SQL Server).
● For more information about SAP ASE-specific migration optimization options, see SAP Note 1680803
(Migration to SAP Sybase ASE - Best Practice).
Related Information
System Copy and Migration Optimization [page 19]
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Planning
CUSTOMER
21
3
Preparations
3.1
Preparations
Before you start the system copy, you must perform the following preparation steps.
3.2
General Technical Preparations
To make a consistent copy of the database, you need to prepare the source system and perform some
subsequent actions on the target system, before you start a system copy. This is not necessary when
performing a test run.
Context
The following describes the required preparations.
For more information about SAP system administration, see the SAP Library for your release at:
Table 7:
SAP NetWeaver Release
Location
SAP NetWeaver 7.0
http://help.sap.com/nw70
and Maintenance Information
System Administration
Technical Operations for
SAP NetWeaver <Language>
SAP NetWeaver 7.0 including enhancement package 1
http://help.sap.com/nw701
and Maintenance Information
System Administration
Technical Operations for
SAP NetWeaver <Language>
SAP NetWeaver 7.0 including enhancement package 2
http://help.sap.com/nw702
and Maintenance Information
System Administration
Technical Operations for
SAP NetWeaver <Language>
22
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Preparations
SAP NetWeaver Release
Location
SAP NetWeaver 7.0 including enhancement package 3
http://help.sap.com/nw703
and Maintenance Information
System Administration
Technical Operations for
SAP NetWeaver <Language>
Procedure
1. Check the minimum kernel patch level required by the support package level of the source system. It
might be necessary to replace the SAP kernel delivered with the installation kit and installed during the
installation of the target system with a newer kernel patch level before starting the target system. If you
have to replace the delivered SAP kernel, you can do this after the installation of the central instance.
2. If your source system is configured against a System Landscape Directory (SLD), check the size of table
BC_SLD_CHANGELOG. The size of this table might be growing very fast because of the reasons described in
SAP Note 1792134
. It is recommended that you clean up table BC_SLD_CHANGELOG as described in
SAP Note 1799613
.
3. SAP NetWeaver Development Infrastructure (DI) only: If your SAP system is of usage type Development
Infrastructure (DI) then this system can only be moved, but not be copied. This means that it is possible to
migrate such a system from one host to another but it is not possible to keep both systems active after the
migration. If you want to move an SAP system with usage type Development Infrastructure (DI), make
sure that the following prerequisites are met:
○ The users and passwords created in the source system are valid in the target system (for example,
they use the same UME).
○ 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).
○ Remove all existing development configurations from the SAP NetWeaver Developer Studio.
○ Verify in the DTR Web UI that there are no pending entries in the NameReservation queue. To check
this, go to http://<dtrhost>:<port>/dtr/sysconfig/support/NameReservationList and
check that there are no entries with the state PRELIMINARY, FINALIZE_PENDING or
REVERT_PENDING in the queue.
If there are entries with the state FINALIZE_PENDING or REVERT_PENDING you have to wait for the
next run of the name reservation background task in the DTR server that ends these entries. This
background task runs normally every 15 minutes.
To check the frequency of this background task you can have a look at http://
<dtrhost>:<port>/dtr/sysconfig/scheduled_tasks.html and check the value Periodicity for
the task ProcessNameReservationsTask. Since precondition for a successful execution 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 since they only occur
if there are open activities (which should not be the case if you followed the previous steps).
○ Stop all applications of the Development Infrastructure (DI) on the source system.
4. SAP NetWeaver 7.0 EHP2 and higher only: If you want to use the Java Migration Monitor, make sure that
the JAVA_MIGMON_ENABLED environment variable is set to “true” on both the source and the target
systems.
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Preparations
CUSTOMER
23
5. BI customers: If you want to perform a system landscape copy for SAP NetWeaver BW, apply SAP Note
886102 .
6. Before you export the Java database on IBM i, apply SAP Note 1724702
.
7. If you use the Integration Repository and Directory, make sure that you apply SAP Note 1345600
avoid any database inconsistencies.
to
8. Make sure that you update the CIM data model in the system landscape directory (SLD) of the source
system as described in SAP Note 669669 . Otherwise you might get an error during the target system
installation (see SAP Note 1840394 ).
3.3
Preparation for IBM i
You have to complete the following preparations for IBM i, which are described in more detail in the linked
sections below.
Related Information
Preparing an IBM i User Profile [page 24]
Enable the User QSECOFR [page 25]
3.3.1 Preparing an IBM i User Profile
Use
For running the installer you need to create a user account on the IBM i host.
The following requirement applies:
● SCM Only:
The IBM i installation user profile must have user class *SECOFR and all special authorities that belong to
user QSECOFR.
Procedure
Note
The user name SAPIUSR and the password SAP are used as examples in the procedures.
24
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Preparations
Enter the following command:
CRTUSRPRF USRPRF(SAPIUSR) PASSWORD(SAP) USRCLS(*SECOFR) TEXT('SAP installation
user') SPCAUT(*USRCLS) OWNER(*USRPRF) LANGID(ENU) CNTRYID(US) CCSID(500)
LOCALE(*NONE)
Caution
You should not set the system variable QIBM_PASE_CCSID. Do not leave this variable empty. Make sure
that QIBM_PASE_CCSID is deleted at least for the time while you are installing your SAP system using the
following command:
RMVENVVAR ENVVAR(QIBM_PASE_CCSID) LEVEL(*SYS)
Note
In previous releases, we recommended that you create the user SAPINST on IBM i to install the SAP
system. In the current release, a group SAPINST is created generically on all platforms and is used for the
installation of the SAP system. If the user SAPINST already exists on your system, you must delete this
user. If you do not want to delete this user for any reason, you must add to the user profile SAPINST the
feature of a group by adding SAPINST to the group of a different user profile such as SAPIUSR. To do this,
use the following command:
CHGUSRPRF USRPRF(SAPIUSR) GRPPRF(SAPINST)
Now the user SAPINST can also be used as a group by the installer.
Note
If you have already an old installation user and you want to make sure this user is configured correctly for
your next SAP system installation, call the following command:
CHGUSRPRF USRPRF(SAPIUSR) USRCLS(*SECOFR) TEXT('SAP installation user')
SPCAUT(*USRCLS) OWNER(*USRPRF) LANGID(ENU) CNTRYID(US) CCSID(500) LOCALE(*NONE)
Note
In a distributed environment, the installation user must have the same name and password on all hosts so
that the required remote access permissions are available. For example, the profile directory on the global
host should be accessible to the installation user of a remote dialog instance.
3.3.2 Enable the User QSECOFR
Use
The user QSECOFR is the standard administrator user on IBM i. This user has the most authority. For running
the installer on IBM i, the user QSECOFR must be enabled. Although for running the installer you only require
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Preparations
CUSTOMER
25
the installation user, the SAP kernel tools on IBM i need some adopted permissions from the QSECOFR. If the
user QSECOFR is disabled this will lead to errors when the SAP kernel tools are called such as CRTR3INST.
Procedure
1. To check the status of the user profile QSECOFR use the following command as your installation user:
DSPUSRPRF USRPRF(QSECOFR)
2. To enable the user QSECOFR use the following command as your installation user:
CHGUSRPRF USRPRF(QSECOFR) STATUS(*ENABLED)
Note
In a distributed environment, the installation user must have the same name and password on all hosts so
that the required remote access permissions are available. For example, the profile directory on the global
host should be accessible to the installation user of a remote dialog instance.
Recommendation
Check also if the password of the user QSECOFR is expired. To do this, login as QSECOFR. When the
password is already expired you will be asked for a new password. Set a new password and the password of
QSECOFR is then no longer expired.
Only when the password of the QSECOFR is not expired the installation procedure will finish successfully.
3.4
Preparing the Media Required for Performing the
Export
For performing the export on the source system, you only need to download and extract the Software
Provisioning Manager 1.0 archive which contains the installer as such.
For the media required for performing the target system installation, refer to section Preparing the
installation Media in the installation guide for your operating system platform and database at https://
help.sap.com/sltoolset
Area System Provisioning
Guide for Installation of Systems Based on SAP
NetWeaver 7.0 / 7.0 EHPs
(see also Installing the Target System [page 54]).
Related Information
Downloading and Extracting the Software Provisioning Manager Archive [page 27]
26
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Preparations
3.4.1 Downloading and Extracting the Software Provisioning
Manager Archive
You must always download and extract the Software Provisioning Manager 1.0 archive
(70SWPM10SP<Support_Package_Number>_<Version_Number>.SAR) from the SAP Software Download
Center because you must use the latest version.
Prerequisites
Make sure the latest version of the SAPCAR archiving tool is available on your Windows PC.
You require the SAPCAR archiving tool to be able to unpack software component archives (*.SAR files), which
is the format of software lifecycle media and tools that you can download from the SAP Software Download
Center.
If required, you can download the latest Windows version of SAPCAR to your Windows PC from:
https://launchpad.support.sap.com/#/softwarecenter
Alphabetical Index (A-Z)
S
SUPPORT PACKAGES & PATCHES
By
SAPCAR .
For more information about SAPCAR, see SAP Note 212876
.
Procedure
1. Download the latest version of the Software Provisioning Manager 1.0 archive
70SWPM10SP<Support_Package_Number>_<Version_Number>.SAR from:
https://launchpad.support.sap.com/#/softwarecenter
Alphabetical Index (A-Z)
S
SUPPORT PACKAGES & PATCHES
By
SOFTWARE PROVISIONING MANAGER
Note
If you have an operating system version that has been initially released with SAP kernel 7.2<X> but is no
longer supported for SAP kernel 7.21 or 7.22, instead of the 70SWPM*.SAR archive you must download
the RMOS70SWPM*.SAR archive for these outdated operating system versions. For more information,
see Constraints [page 10]
2. We recommend that you copy the software provisioning manager 1.0 archive to the IFS of the IBM i host.
3. If you did not do so already, make sure you have configured your TCP/IP as described in SAP Note 92589
. Do not forget afterwards to perform an IPL to make the change effective. Otherwise, the file copying
is very slow from your local Windows optical media drive or Windows file system to the IFS on your IBM i.
4. If you want to verify the signature of the
70SWPM10SP<Support_Package_Number>_<Version_Number>.SAR archive, execute the following
commands on your Windows PC:
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Preparations
CUSTOMER
27
Note
In addition, check SAP Note 1680045
whether additional information is available.
<Path to SAPCAR>\sapcar.exe -tVvf<Path to Download Directory>
\70SWPM10SP<Support_Package_Number>_<Version_Number>.SAR
5. Unpack the Software Provisioning Manager archive to a local directory on your Windows PC using the
following command:
<Path to SAPCAR>\sapcar.exe -xvf <Path to Download Directory>
\70SWPM10SP<Support_Package_Number>_<Version_Number>.SAR <Path to Unpack
Directory>
Note
Make sure that all users have read permissions for the directory where you want to unpack the installer.
Caution
Make sure that you unpack the Software Provisioning Manager archive to a dedicated folder. Do not
unpack it to the same folder as other installation media.
28
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Preparations
4
Database Independent System Copy
You can use the installer to export and import your Java database content, file system, and all configuration in
a database-independent format. It uses the Jload tool.
Jload
Note
Make sure that you have the most recent version of the Jload tool, which you can find at http://
service.sap.com .
Constraints
Jload Restrictions
● The installer generates a database dump of all SAP objects that are defined in the Java Dictionary (Jload).
Other objects are not exported by the installer.
● For a consistent database export, no transactions on export-relevant database objects are allowed during
the export. Otherwise, the export has to be restarted. Therefore, we recommend that you shut down the
SAP system (excluding the database!) for the export. The database must still be running.
Process Flow
Proceed as described in System Copy Procedure [page 29].
4.1
System Copy Procedure
This section describes the system copy procedure using Jload .
Prerequisites
Specify an empty directory with sufficient disk space for the export dump on the host where you want to
perform the export. Make sure that this directory does not contain any files from any previous system copy
exports. If you cancelled a system copy export and want to perform the export again, make sure that you
remove all files from the previously cancelled export before you start the export from scratch.
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Database Independent System Copy
CUSTOMER
29
Process Flow on the Source System (Export)
When performing the export, the installer creates a migration export media which contains the data of the
exported system, and which you use to install the target system.
The following figure shows exemplary the export options and their resulting output files.
Follow the sequence of steps described in the process flows below for a:
● Central system
○ Central system – Performing the Export on the Source System
○ Central system – Setting Up the Target System
● Distributed system or high-availability system
○ Distributed system or high-availability system – Performing the Export on the Source System
○ Distributed system or high-availability system – Setting Up the Target System
Central System – Performing the Export on the Source System
To perform the export for a central system, you need to proceed as follows on the central system host:
1. Perform the export on the central system host:
1. You run the installer [page 35] to export the database instance and the central instance.
On the Welcome screen, choose the option Database and Central Instance Export.
For more information, see Running the Installer to Perform the Export [page 35].
Central System – Setting Up the Target System
Use the installer to set up the target system and import the database files that you have exported from the
source system.
Note
This system copy guide describes only the export of the source system in detail. For the installation of the
target system, you use the installation guide for the database and operating system platform of your target
system. This procedure describes only the additional system copy-specific steps for the target system
installation and refers for the remaining steps to the target system installation guides. You find the target
system installation guides at http://support.sap.com/sltoolset
Option of Software Provisioning Manager
System Provisioning
System Copy
System Copy Guides - Installing the Target System .
In the following, we refer to this guide as “installation guide”.
Perform the following steps on the central system host:
1. Prepare the central system host for the installation of your target system as described in the installation
guide.
2. Transfer the export files [page 53] to the central system target host.
30
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Database Independent System Copy
3. Install the target system [page 54].
4. If required install additional dialog instances on dialog instance hosts as described in the installation
guide.
Distributed System or High-Availability System – Performing the Export on
the Source System
To perform the export for a distributed system or a high-availability-system, you need to proceed as follows:
1. When exporting a distributed system using local export directories, the created export directories need to
be merged, that is copied together. Make sure that the SOURCE.PROPERTIES file is the one created when
exporting the central instance.
2. Perform the export on the database instance host:
1. You run the installer [page 35] to export the database instance. On the Welcome screen, choose the
option Database Instance Export.
For more information, see Running the Installer to Perform the Export [page 35].
3. Perform the export on the central instance host:
You run the installer to export the central instance. For more information, see Running the Installer to
Perform the Export [page 35].
On the Welcome screen, choose the option Central Instance Export.
Distributed System or High-Availability System – Setting Up the Target
System
Use the installer to set up the target system and import the database files that you have exported from the
source system.
Note
This system copy guide describes only the export of the source system in detail. For the installation of the
target system, you use the installation guide for the database and operating system platform of your target
system. This procedure describes only the additional system copy-specific steps for the target system
installation and refers for the remaining steps to the target system installation guides. You find the target
system installation guides at http://support.sap.com/sltoolset
Option of Software Provisioning Manager
System Provisioning
System Copy
System Copy Guides - Installing the Target System .
In the following, we refer to this guide as “installation guide”.
Perform the following steps on the relevant installation hosts of your target system:
1. Prepare the SCS instance host, the central instance host and the database instance host for the
installation of the corresponding instances of your target system as described in the installation guide.
2. Install the SCS instance for the target system as described in the installation guide.
3. Perform the following steps on the database instance host:
1. Transfer the export files to the database instance target host. For more information, see Transferring
the Export Files to the Target Host [page 53].
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Database Independent System Copy
CUSTOMER
31
2. Install the database instance of the target system. For more information, see Installing the Target
System [page 54].
4. On the central instance host, install the central instance of the target system.
5. If required, install additional dialog instances on the dialog instance hosts as described in the installation
guide.
4.1.1 Exporting the Source System
Here you can find information about how to run the installer to perform the export on the source system.
For more information about the overall sequence of steps required for exporting the source system, see
System Copy Procedure [page 29].
Related Information
Copying the Installation Media Manually to Your IBM i [page 94]
Prerequisites for Running the Installer [page 32]
Running the Installer [page 35]
4.1.1.1
Prerequisites for Running the Installer
Make sure you fulfil the following prerequisites before running the installer.
● If you want to use the SL Common GUI, make sure that the following web browser requirements are met:
○ You have one of the following supported browsers on the device where you want to run the SL
Common GUI: Google Chrome, Mozilla Firefox, Microsoft Edge, or Microsoft Internet Explorer 11.
Always use the latest version of these web browsers.
Recommendation
We recommend using Google Chrome.
○ If you copy the SL Common GUI URL manually in the browser window, make sure that you open a new
Web browser window in private browsing mode (Internet Explorer), incognito mode (Chrome) or
private browsing mode (Firefox). This is to prevent Web browser plugins and settings from interfering
with the SL Common GUI.
For more information about the SL Common GUI, see Useful Information About the Installer [page 40].
● Make sure that you have logged on to your host as an installation user with similar authorization rights to
QSECOFR. For more information about how to create an installation user, see Preparing an IBM i User
Profile [page 24].
32
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Database Independent System Copy
● Check the value of the environment variable TEMP, TMP, or TMPDIR:
Table 8: Shells and Commands
Shell Used
Command
Command prompt
WRKENVVAR
Qp2Term
echo $TEMP
○ 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 variable TEMP, TMP, or TMPDIR points – for example, by
using a crontab entry.
○ Each SAP instance requires a separate installation directory.
Recommendation
We recommend that you keep all installation directories until the system is completely and
correctly installed.
○ Make sure that you have at least 60 MB of free space in the installer directory for each installer option.
In addition, you need 200 MB free space for the installer executables. If you cannot provide 200 MB
free space in the temporary directory, you can set one of the environment variables TEMP, TMP, or
TMPDIR to another directory with 200 MB free space for the installer executables.
● The following information is only valid if you use the Java GUI:
Make sure that your DISPLAY environment variable is set to <Host_Name>:0.0, where <Host_Name> is
the host on which you want to display the GUI.
Table 9:
Shell Used
Command
Command prompt
ADDENVVAR ENVVAR(DISPLAY) VALUE('<hostname>:
0.0') REPLACE(*YES)
Qp2Term
export DISPLAY=<host_name>:0.0
Note
When you leave your Qp2Term session, all changes of the environment variables done by the command
export are reverted.
Note
For advanced users only:
PASE, which is similar to AIX, allows you to set the DISPLAY variable. If your X server for Microsoft
Windows or Linux is already configured and running, you can try to direct the graphical output of the
installer to an XWindow by setting the DISPLAY variable. If this works, you do not have to use the
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Database Independent System Copy
CUSTOMER
33
remote installer GUI separately. We do not recommend that you start the installer using the DISPLAY
variable as there is no support available.
Note
For advanced users only:
Besides using an X server and the DISPLAY variable, you can use VNC. For more information about
VNC, see the IBM documentation. VNC also offers a GUI by using IBM i tools. When VNC is prepared as
described in the IBM documentation, the installer GUI is directly started on your Windows PC after
starting the installer on IBM i.
● Make sure that the following ports are not used by other processes:
○ When using the SL Common GUI:
○ Port 4237 is used by default as HTTPS port for communication between the installer and the SL
Common GUI.
If this port cannot be used, you can assign a free port number by executing sapinst with the
following command line parameter:
SAPINST_HTTPS_PORT=<Free Port Number>
Example
CD DIR('<Path_To_Unpack_Directory>')
CALL PGM(QP2TERM) PARM('./sapinst' 'SAPINST_HTTPS_PORT=<Free Port
Number>')
○ Port 4239 is used by default for displaying the feedback evaluation form at the end of the installer
processing.
The filled-out evaluation form is then sent to SAP using HTTPS.
If this port cannot be used, you can assign a free port number by executing sapinst with the
following command line parameter:
SAPINST_HTTP_PORT=<Free Port Number>
○ When using the Java SDT GUI:
○ Port 21212 is used by default for communication between the installer GUI server and the installer
GUI client.
If this port cannot be used, you can assign a free port number by executing sapinst with the
following command line parameter:
SAPINST_DIALOG_PORT=<Free Port Number>
Example
CD DIR('<Path_To_Unpack_Directory>')
CALL PGM(QP2TERM) PARM('./sapinst' 'SAPINST_DIALOG_PORT=<Free Port
Number>')
○ Port 4239 is used by default for displaying the feedback evaluation form at the end of the installer
processing.
The filled-out evaluation form is then sent to SAP using HTTPS.
34
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Database Independent System Copy
If this port cannot be used, you can assign a free port number by executing sapinst with the
following command line parameter:
SAPINST_HTTP_PORT=<Free Port Number>
● Specify an empty directory with sufficient disk space for the export dump on the host where you want to
perform the export. Make sure that this directory does not contain any files from any previous system
copy exports. If you cancelled a system copy export and want to perform the export again, make sure that
you remove all files from the previously cancelled export before you start the export from scratch.
● Make sure that you shut down all SAP Application Servers before the export. The database must still be
running. Otherwise, the target system might be inconsistent.
● IBM DB2 for IBM i only: Before you start the export of the existing SAP system, you have to download the
and copy it to directory /usr/sap/
current version of R3szchk at http://support.sap.com/patches
<SAPSID>/SYS/exe/run/.
● Before you export the Java database on IBM i, apply SAP Note 1724702
4.1.1.2
.
Running the Installer
This section describes how to run the installer to perform the export for system copy.
Prerequisites
For more information, see Prerequisites for Running the Installer [page 32].
Context
Software Provisioning Manager (the “installer” for short) offers two GUIs:
● The new web browser-based “SL Common GUI of the Software Provisioning Manager” - “SL Common
GUI” for short
● The “classic” Java-based GUI with a CUI client and server - “Java SDT GUI” for short
Note
If the SL Common GUI does not meet your requirements you can still use the “classic” Java SDT GUI.
You then have to start the sapinst executable with the command line option
SAPINST_SLP_MODE=false.
In cases where both GUIs behave the same way, we address them as “installer GUI”.
For more information, see Useful Information About the Installer [page 40].
This procedure describes an installation where you use one of the following GUI scenarios:
● You run the installer and use the SL Common GUI. Then you can control the processing of the installer in
the browser running on any device.
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Database Independent System Copy
CUSTOMER
35
● You run the installer and use the Java SDT GUI. The installer is running on the installation host and the
Java SDT GUI on a Windows PC.
The following information is only valid if you use the Java SDT GUI:
● If you need to see the installation on a remote display, we recommend that you perform a remote
installation [page 45], where the installer GUI is running on a separate host from the installer.
● Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote
access to the installer GUI on Windows workstations. For more information, see SAP Note 1170809 .
Recommendation
The following information is only valid if you use the Java SDT GUI:
Since IBM i does not have GUI capabilities, we recommend that you perform a remote installation with the
installer. You first have to start the installer without the installer GUI on the IBM i host using QP2TERM and
then you have to start the installer GUI on the Windows installation host. Afterwards the installer behaves
the same as if started completely on one host. For more information, see Performing a Remote Installation
[page 45] and Starting the Installer GUI Separately [page 47]. The remote installation is the default
installation option on IBM i. The section Running the Installer is used only for information.
However, the remote GUI display (using the DISPLAY environment variable) is possible, but this is
considered an advanced user option.
Procedure
1. Log on to the host where you want to run the installer.
Make sure that you log on as a user with similar authorization rights to QSECOFR. For more information,
see Preparing an IBM i User Profile [page 24].
Caution
Make sure that the installation user has not set any environment variables for a different SAP system or
database by using the command WRKENVVAR.
2. Make the required media available.
For more information, see Preparing the Media Required for Performing the Export [page 26].
Recommendation
Make the installation media available locally . For example, if you use Network File System (NFS),
reading from media mounted with NFS might fail.
3. Start the installer as follows:
Open a command prompt and enter the following command:
CD DIR('<Path_To_Unpack_Directory>')
CALL PGM(QP2TERM) PARM(’./sapinst’)
36
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Database Independent System Copy
Note
If you want to use a virtual host name, start the installer with the installer property
SAPINST_USE_HOSTNAME as follows:
CALL PGM(QP2TERM) PARM(’./sapinst’ ’SAPINST_USE_HOSTNAME=<Virtual_Host_Name>')
Caution
Make sure that the installation directory is not mounted with NFS, or there might be problems when
starting the Java Virtual Machine.
4. The installer is starting up.
Depending on the type of the installer GUI you want to use, do one of the following:
○ If you use the SL Common GUI, the installer now starts and waits for the connection with the SL
Common GUI.
You can find the URL you require to access the SL Common GUI at the bottom of the shell from which
you are running the installer.
Sample Code
...
INFO
2017-02-28 07:08:07.135 (root/sapinst) [/.../ins/SAPINST/
impl/src/guiengine/CSLPCommunicationServer.cpp:157]
CSLPCommunicationServer::doWork()
Access URL for GUI is
https://MyHost:4237/FiUoAQgciBuwWyaf/docs/index.html
Logon users: [MyUser]
...
Open the URL on a device with a supported web browser (see Prerequisites for Running the Installer
[page 32]).
The SL Common GUI opens in the browser by displaying the Welcome screen.
Note
Before you reach the Welcome screen, your browser might warn you that the certificate of the
sapinst process on this computer could not be verified. Accept this warning to inform your
browser that it can trust this site, even if the certificate could not be verified.
○ If you use the Java SDT GUI - that is you started the sapinst executable with command line option
SAPINST_SLP_MODE=false, you still need to start the Java SDT GUI separately on a Windows PC to
get the Welcome screen displayed. For more information, see Starting the Installer GUI Separately
[page 47].
5. On the Welcome screen, choose
<Database>
<Product>
Source System Export
Software Life-cycle Options
<Distribution Option>
System Copy
Based on AS Java .
Select the corresponding system copy option from the tree structure according to the sequence of the
process flow for the database-independent system copy procedure [page 29].
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Database Independent System Copy
CUSTOMER
37
Note
Do not perform these steps if you use a database-specific method (see Database-Specific System
Copy [page 57]).
6. Choose Next.
7. Follow the instructions in the installer input screens and enter the required parameters.
Note
To find more information on each parameter during the Define Parameters phase, position the cursor
on the required parameter input field :
○ If you use the SL Common GUI, choose either F1 or the HELP tab. Then the available help text is
displayed in the HELP tab.
○ If you use the Java SDT GUI, choose F1 . Then a dialog opens with the available help text.
Caution
Whenever you are asked by the installer for the password of the user <SAPSID>ADM on a remote IBM i
host put also the UID number of the <SAPSID>ADM into the input screen when it is not set already. You
can get this number from the global host where the SCS or ASCS instance is already installed using
following command:
DSPUSRPRF USRPRF(<SAPSID>ADM) or
CALL PGM(QP2TERM) PARM('/QOpenSys/usr/bin/id' '<SAPSID>ADM')
The SCS or ASCS installation is the installation which initially determinates the UID of the user
<SAPSID>ADM.
8. After you have entered all requested input parameters, the installer displays the Parameter Summary
screen. This screen shows both the parameters that you entered and those that the installer set by
default.
If required, you can revise the parameters before starting the export procedure.
9. To start the execution, choose Next.
The installer starts the export and displays its progress of the system copy export during the processing
phase.
10. If required, delete directories with the name sapinst_exe.xxxxxx.xxxx after the installer has finished.
Sometimes these remain in the temporary directory.
Note
If there are errors with the installer extraction process, you can find the log file dev_selfex.out in the
temporary directory.
Recommendation
Keep all installer directories until you are sure that the system, including all instances, is completely and
correctly installed. Once the system is completely and correctly installed, make a copy of the installer
38
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Database Independent System Copy
directories with all their contents. Save the copy to a physically separate medium, such as a medium or
a USB drive that is separate from your installation hosts.
This might be useful for analyzing any issues that might occur later when using the system. For security
reasons, do not keep the installer directories on hosts where you processed it, but make sure that you
delete them after saving them separately.
11. If you copied installation media to your hard disk, you can delete these files when the installer has
successfully completed.
Note
For more information about how to remove the installer files on IBM i, see Removing the Installer
Installation Files [page 109].
12. Java GUI only: For security reasons, we recommend that you delete the .sdtgui directory within the
home directory of the user with which you ran the installer:
/home/<Installation_User>/.stdgui
13. For security reasons, we recommend that you remove the group SAPINST from the operating system
users after you have completed the installation.
Note
This step is only required, if you did not specify during the Define Parameters phase that the group
SAPINST is to be removed from the operating system users after the execution of the installer has
completed.
Related Information
Useful Information About the Installer [page 40]
Interrupted Processing of the Installer [page 42]
Performing Remote Processing of the Installer (Java SDT GUI only) [page 45]
Starting the Java SDT GUI Separately [page 47]
Running the Installer in Accessibility Mode [page 50]
Troubleshooting with the Installer [page 51]
4.1.1.3
Additional Information About the Installer
The following sections provide additional information about the installer.
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Database Independent System Copy
CUSTOMER
39
Related Information
Useful Information About the Installer [page 40]
Interrupted Processing of the Installer [page 42]
Performing Remote Processing of the Installer (Java SDT GUI only) [page 45]
Starting the Java SDT GUI Separately [page 47]
Running the Installer in Accessibility Mode [page 50]
Troubleshooting with the Installer [page 51]
Troubleshooting during the Export Process [page 52]
Removing the Installation Files of the Installer [page 109]
4.1.1.3.1
Useful Information About the Installer
This section contains some useful technical background information about the installer and the installer GUI.
● Software Provisioning Manager (the installer) offers two GUIs:
○ The new web browser-based “SL Common GUI of the Software Provisioning Manager” - “SL Common
GUI” for short
○ The “classic” Java-based GUI with a CUI client and server - “Java SDT GUI” for short
The SL Common GUI of the Software Provisioning Manager (or “SL Common GUI” for short) uses the SAP
UI Development Toolkit for HTML5 - also known as SAPUI5 - a client-side HTML5 rendering library based
on JavaScript. The benefits of this new user interface technology for the user are:
○ Zero foot print, since only a web browser is required on the client
○ New controls and functionality, for example, view logs in web browser.
The SL Common GUI connects the web browser on a client with the sapinst executable - which is part of
Software Provisioning Manager - running on the installation host using the standard protocol HTTPS.
For the SL Common GUI the installer provides a pre-generated URL at the bottom of the shell from which
you are running the installer . If you have a supported web browser installed on the host where you run the
installer, you can start the SL Common GUI directly from this URL. Otherwise, open a web browser
supported by the SL Common GUI on any device and run the URL from there.
For more information about supported web browsers see Prerequisites for Running the Installer [page
32].
If the SL Common GUI does not meet your requirements, you can still use the “classic” Java SDT GUI. To
do so, you must start the sapinst executable with the command line option SAPINST_SLP_MODE=false.
You can switch back to the default installer GUI at any time with the following steps:
1. Stop the installer.
2. Restart the installer with command line option SAPINST_SLP_MODE=false.
3. On the What do you want to do? screen choose Continue with the existing run.
● The installer creates the installation directory sapinst_instdir directly below the temporary directory.
The installer finds the temporary directory by checking the value of the following environment variables in
the following sequence: TEMP, TMP, and TMPDIR. If no value is set for these variables, the installer creates
the installation directory sapinst_instdir directly below the /tmp directory by default.
If you want the installer to create the installation directory sapinst_instdir in another directory, set the
environment variable TEMP to this directory before you start the installer.
40
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Database Independent System Copy
Table 10:
Shell Used
Command prompt
Command
ADDENVVAR ENVVAR(TEMP) VALUE('<Directory>')
REPLACE(*YES)
Qp2Term
export TEMP=<Directory>
Note
When you leave your Qp2Term session, all changes of the environment variables done by the command
export are reverted.
Caution
Make sure that the installation directory is not mounted with NFS, or there might be problems when the
Java Virtual Machine is started.
Recommendation
We recommend that you keep all installation directories until the system is completely and correctly
installed.
● For each installation option, the installer creates a subdirectory located in the sapinst_instdir
directory.
● The installer extracts itself to a temporary directory called sapinst_exe.xxxxxx.xxxx, which is located
in the environment variables TEMP, TMP, or TMPDIR. These files are deleted after the installer has stopped
running.
The temporary directory sapinst_exe.xxxxxx.xxxx sometimes remains undeleted. You can safely
delete it.
The temporary directory also contains the log file dev_selfex.out from the extraction process, which
might be useful if an error occurs.
Caution
If the installer cannot find a temporary directory, the installation terminates with the error FCO-00058.
● To see a list of all available installer properties, enter the following commands:
CD DIR('<Path_To_Unpack_Directory>')
CALL PGM(QP2TERM) PARM('./sapinst' '-p')
● This information is only relevant if you use the Java GUI of the installer: If you need to run the installer
in accessibility mode, proceed as described in Running the Installer in Accessibility Mode [page 50].
● If you want to perform the export in unattended mode, see SAP Note 2230669
improved procedure using inifile.params.
which describes an
● Before you start the export of the existing SAP System, you have to download the current version of
R3szchk at http://support.sap.com/patches
and copy it to directory /usr/sap/<SID>/SYS/exe/
run/.
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Database Independent System Copy
CUSTOMER
41
● If required, stop the installer by choosing one of the following, depending on the installer GUI you use:
○ In the SL Common GUI, choose the Cancel button.
○ In the Java SDT GUI, choose
Windows PC..
SAPinst
Exit Process
in the installer Java SDT GUI menu on your
Note
If you need to terminate the installer, press Shift + Esc then 2 on your IBM i host.
4.1.1.3.2
Interrupted Processing of the Installer
Here you find information about how to restart the installer if its processing has been interrupted.
Context
The processing of the installer might be interrupted for one of the following reasons:
● An error occurred during the Define Parameters or Execute phase:
The installer does not abort the installation in error situations. If an error occurs, the installation pauses
and a dialog box appears. The dialog box contains a short description of the choices listed in the table
below as well as a path to a log file that contains detailed information about the error.
● You interrupted the installation by choosing
○ Cancel in the SL Common GUI
○ Exit Process in the SAPinst menu in the Java SDT GUI
Caution
If you stop an option in the Execute phase, any system or component installed by this option is
incomplete and not ready to be used. Any system or component uninstalled by this option is not
completely uninstalled.
42
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Database Independent System Copy
The following table describes the options in the dialog box:
Table 11:
Option
Definition
Retry
The installer retries the installation from the point of failure without repeating any of
the previous steps.
This is possible because the installer records the installation progress in the
keydb.xml file.
We recommend that you view the entries in the log files, try to solve the problem,
and then choose Retry.
If the same or a different error occurs, the installer displays the same dialog box
again.
Stop
The installer stops the installation, closing the dialog box, the installer GUI, and the
GUI server.
The installer records the installation progress in the keydb.xml file. Therefore, you
can continue the installation from the point of failure without repeating any of the
previous steps. See the procedure below.
Continue
The installer continues the installation from the current point.
View Log
Access installation log files.
The following procedure describes the steps to restart an installation, which you stopped by choosing Stop, or
to continue an interrupted installation after an error situation.
Procedure
1. Log on to the installation host as a user with the required permissions as described in Running the Installer
[page 35] .
2. Make sure that the media required for the export are still available.
For more information, see Preparing the Media Required for Performing the Export [page 26].
Recommendation
Make the installation media available locally. For example, if you use remote file shares on other
Windows hosts, CIFS shares on third-party SMB-servers, or Network File System (NFS), reading from
media mounted with NFS might fail.
3. Restart the installer from the installation media directory to which you unpacked the Software
Provisioning Manager archive.
Enter the following commands:
CD DIR('<Path_To_Unpack_Directory>')
CALL PGM(QP2TERM) PARM('./sapinst')
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Database Independent System Copy
CUSTOMER
43
4. The installer is restarting.
Depending on the type of the installer GUI you want to use, do one of the following:
○ If you use the SL Common GUI, the installer now starts and waits for the connection with the SL
Common GUI.
You can find the URL you require to access the SL Common GUI at the bottom of the shell from which
you are running the installer.
Sample Code
...
INFO
2017-02-28 07:08:07.135 (root/sapinst) [/.../ins/SAPINST/
impl/src/guiengine/CSLPCommunicationServer.cpp:157]
CSLPCommunicationServer::doWork()
Access URL for GUI is
https://MyHost:4237/FiUoAQgciBuwWyaf/docs/index.html
Logon users: [MyUser]
...
Open the URL on a device with a supported web browser (see Prerequisites for Running the Installer
[page 32]).
The SL Common GUI opens in the browser by displaying the Welcome screen.
Note
Before you reach the Welcome screen, your browser might warn you that the certificate of the
sapinst process on this computer could not be verified. Accept this warning to inform your
browser that it can trust this site, even if the certificate could not be verified.
○ If you use the Java SDT GUI - that is you started the sapinst executable with command line option
SAPINST_SLP_MODE=false, you still need to start the Java SDT GUI separately on a Windows PC to
get the Welcome screen displayed. For more information, see Starting the Installer GUI Separately
[page 47].
5. From the tree structure on the Welcome screen, select the installation option that you want to continue
and choose Next.
The What do you want to do? screen appears.
6. On the What do you want to do? screen, decide between the following alternatives and continue with Next:
44
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Database Independent System Copy
Table 12:
Alternative
Behavior
Perform a new run
The installer does not continue the interrupted export for system copy option.
Instead, it moves the content of the old installer directory and all installer-spe­
cific files to a backup directory. Afterwards, you can no longer continue the old
option.
The following naming convention is used for the backup directory:
log_<Day>_<Month>_<Year>_<Hours>_<Minutes>_<Seconds>
Example
log_01_Oct_2016_13_47_56
Note
All actions taken by the export for system copy before you stopped it (such
as creating directories or users) are not revoked.
Caution
The installer moves all the files and folders to a new log directory, even if
these files and folders are owned by other users. If there are any processes
currently running on these files and folders, they might no longer function
properly.
Continue with the existing one
The installer continues the interrupted export for system copy from the point
of failure.
4.1.1.3.3
Performing Remote Processing of the Installer
(Java SDT GUI only)
Here you find information about how to process the installer on a remote host.
Note
This section is only valid if you use the Java SDT GUI. That is, you started the sapinst executable with
command line option SAPINST_SLP_MODE=false.
Prerequisites
● The remote host meets the prerequisites for starting the installer as described in Prerequisites for
Running the Installer [page 32].
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Database Independent System Copy
CUSTOMER
45
● Both computers are in the same network and can ping each other.
To test this:
1. Log on to your remote host (IBM i) and enter the command:
PING RMTSYS('<Local_Host>')
2. Log on to the local host (Windows PC) and enter the command:
ping <Remote_Host>
● If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter, make sure that this user exists on the remote host and that this user owns an
existing home directory on IBM i (/home/<User_Name>).
Context
You use this procedure to process the installer on a remote host. In this case, the installer runs on the remote
host, and the installer GUI runs on the local host. The local host is the host from which you control the
installation with the installer GUI. The installer GUI connects using a secure SSL connection to the installer.
If your security policy requires that the person performing the installation by running the installer GUI on the
local host is not allowed to know QSECOFR like credentials on the remote host, you can specify another
operating system user for authentication purposes. You do this using the SAPINST_REMOTE_ACCESS_USER
parameter when starting the sapinst executable from the command line. You have to confirm that the user is
a trusted one. For more information, see SAP Note 1745524
.
Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote access
to the installer GUI on Windows workstations. For more information, see SAP Note 1170809 .
Caution
In this section, “local host” refers to the Windows installation host, and “remote host” refers to the IBM i
host where the SAP system is installed.
Procedure
1. Log on to the remote host.
Make sure that you log on as the installation user with similar authorization rights to QSECOFR. For more
information, see Preparing an IBM i User Profile [page 24].
Caution
Make sure that the installation user has not set any environment variables for a different SAP system or
database by using the command WRKENVVAR.
2. Make the installation media available on your remote host.
For more information, see Preparing the Installation Media [page 26].
46
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Database Independent System Copy
Recommendation
Make the installation media available locally . For example, if you use Network File System (NFS),
reading from media mounted with NFS might fail.
3. Open a command prompt and change to the directory to which you unpacked the Software Provisioning
Manager archive.
4. Check the version of the sapinst executable by entering the following command:
CD DIR('<Path_To_Unpack_Directory>')
CALL PGM(QP2TERM) PARM('./sapinst' '-sfxver')
The version of the sapinst executable must be exactly the same as the version of the sapinstgui
executable on the local host (see also Starting the Installer GUI Separately [page 47]).
5. Start the installer by entering the following command:
CD DIR('<Path_To_Unpack_Directory>')
CALL PGM(QP2TERM) PARM('./sapinst')
Note
If you need to specify another operating system user for authentication purposes, this command is as
follows:
CALL PGM(QP2TERM) PARM('./sapinst'
'SAPINST_REMOTE_ACCESS_USER=<Specified_OS_User>')
The installer now starts and waits for the connection to the installer GUI. You see the following at the
command prompt:
guiengine: no GUI connected; waiting for a connection on host <Host_Name>, port
<Port_Number> to continue with the installation
6. There is no GUI on IBM i, so you do not see the installer Welcome screen. As a default, you must start the
installer GUI separately on a Windows operating system . For more information, see Starting the Installer
GUI Separately [page 47].
4.1.1.3.4
Starting the Java SDT GUI Separately
Here you find information about how to start the Java SDT GUI separately.
Note
This section is only valid if you use the Java SDT GUI. That is, you started the sapinst executable with
command line option SAPINST_SLP_MODE=false.
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Database Independent System Copy
CUSTOMER
47
Prerequisites
Note
If you want to run the installer on a Windows host, make sure that you meet the prerequisites for the
installer listed in the relevant Windows guide.
Context
You need to start the installer GUI separately in the following cases:
● You are running IBM i and did not set a DISPLAY environment variable.
● You closed the installer GUI using
still running.
File
Close GUI only
from the installer menu while the installer is
● You want to perform a remote installation, where the installer GUI runs on a different host from the
installer. For more information, see Performing a Remote Installation [page 45].
● You want to run the installer in accessibility mode. In this case, you have to start the installer GUI
separately on a Windows host as described below with the additional command line parameter accessible. For more information, see Running the Installer in Accessibility Mode [page 50].
Caution
This is the default on IBM i. Since there is no GUI on IBM i, you must start the the installer GUI separately.
In this procedure, the following variables are used: <Remote_Host> is the name of the remote host, and
<Port_Number_Gui_Server_To_Gui_Client> is the port the GUI server uses to communicate with the GUI
client (21212 by default).
Procedure
● Starting the Installer GUI on Windows
a. Make the installer software available on the host on which you want to start the installer GUI.
For more information, see Preparing the Installation Media [page 26].
b. Start the installer GUI by executing <Drive>:\<Path_To_Unpack_Directory>\sapinstgui.exe
with the appropriate command line parameters:
Note
If you start the installer GUI executable on Windows 7 or Windows 2008, you must use the option
Run as administrator. Typically, you first start a command prompt using Run as administrator. Then
in this command prompt, you enter the installer GUI command.
48
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Database Independent System Copy
Note
If you have a share ROOTBIN on your IBM i and you have mapped this share to the drive for example
X, you can start the installer GUI using your copied unpack directory:
X:\tmp\<SAPSID>\<Path_To_Unpack_Directory>\sapinstgui.exe
For more information, see Copying the Installation Media Manually to Your IBM i [page 94].
By default the Windows sapinstgui.exe is part of the software provisioning manager archive for
IBM i. Only when the file sapinstgui.exe is missing, you must download the Software
Provisioning Manager archive for Windows .
○ If you want to perform a remote installation, proceed as follows:
1. Check the version of sapinstgui.exe by entering the following command:
sapinstgui.exe -sfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation [page
45]).
2. Start the installer GUI by entering the following command:
sapinstgui.exe -host <Remote_Host> -port
<Port_Number_Gui_Server_To_Gui_Client>
○ If you closed the installer GUI using
installer, proceed as follows:
File
Close GUI only
and want to reconnect to the
○ If you are performing a local installation with the installer and the installer GUI running on the
same host, execute the following command:
sapinstgui.exe -port <Port_Number_Gui_Server_To_Gui_Client>
○ If you are performing a remote installation with the installer and the installer GUI running on
different hosts, execute the following command:
sapinstgui.exe -host <Remote_Host> -port
<Port_Number_Gui_Server_To_Gui_Client>
c. The installer GUI starts and connects to the installer.
● Starting the Installer GUI on UNIX
a. Make the installer software available on the host on which you want to start the installer GUI.
For more information, see Preparing the Installation Media [page 26].
b. Start the sapinstgui executable with the appropriate command line parameters:
○ If you want to perform a remote installation, proceed as follows:
1. Check the version of the sapinstgui executable by entering the following command:
<Path_To_Unpack_Directory>/sapinstgui -sfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation [page
45]).
2. Start the installer GUI by entering the following command:
<Path_To_Unpack_Directory>/sapinstgui -host <Remote_Host> -port
<Port_Number_Gui_Server_To_Gui_Client>
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Database Independent System Copy
CUSTOMER
49
○ If you closed the installer GUI using
installer, proceed as follows:
File
Close GUI only
and want to reconnect to the
○ If you are performing a local installation with the installer and the installer GUI running on the
same host, execute the following command:
<Path_To_Unpack_Directory>/sapinstgui -port
<Port_Number_Gui_Server_To_Gui_Client>
○ If you are performing a remote installation with the installer and the installer GUI running on
different hosts, execute the following command:
<Path_To_Unpack_Directory>/sapinstgui -host <Remote_Host> -port
<Port_Number_Gui_Server_To_Gui_Client>
c. The installer GUI starts and connects to the installer.
4.1.1.3.5
Running the Installer in Accessibility Mode
You can also run the installer in accessibility mode.
Note
The information contained in this section is only valid if you use the Java SDT GUI. That is, you started the
sapinst executable with command line option SAPINST_SLP_MODE=false.
If you use the SL Common GUI, apply the standard accessibility functions of your web browser.
Context
The following features are available:
● Keyboard access:
This feature is generally available for all operating systems.
● High-contrast color:
This feature is derived from the Windows display properties. Therefore, to enable this feature, perform a
remote installation with the installer GUI running on a Windows host.
● Custom font setting:
This feature is derived from the Windows display properties. Therefore, to enable this feature, perform a
remote installation with the installer GUI running on a Windows host.
Procedure
● Activating and Adjusting Accessibility Settings on Windows
You first have to activate and adjust the relevant settings for the font size and color schemes before you
start the installer or the installer GUI.
50
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Database Independent System Copy
Note
The following procedure applies for Windows Server 2012 and might be different when using another
Windows operating system.
a. Right click on your Windows desktop and choose Personalize.
b. Select Adjust font size (DPI) and choose Larger scale (120 DPI).
To define other font size schemes, choose Custom DPI.
c. In the right-hand pane, select Window Color and Appearance.
Select a color scheme from the Color scheme drop-down box.
To define your own color schemes, choose Advanced.
● Running the Installer in Accessibility Mode
a. Start the installer on the remote host by executing the following command from the command line as
described in Performing Remote Processing of the Installer (Java SDT GUI only) [page 45]:
<Path_To_Unpack_Directory>/sapinst
b. Start the installer GUI on a local Windows host by executing the following command from the
command line as described in Starting the Java SDT GUI Separately [page 47]:
<Path_To_Unpack_Directory>\sapinstgui.exe -accessible -host <Remote_Host> port <Port_Number_Gui_Server_To_Gui_Client>
You perform a remote installation as follows:
a. Start the installer on the remote IBM i host by executing the following command from the command
line as described in Performing Remote Processing of the Installer (Java SDT GUI only) [page 45]:
CD DIR('<Path_To_Unpack_Directory>')
CALL PGM(QP2TERM) PARM('./sapinst')
b. Start the installer GUI on a local Windows host by executing the following command from the
command line as described in Starting the Java SDT GUI Separately [page 47]:
<Path_To_Unpack_Directory>\sapinstgui.exe -accessible -host <Remote_Host> port <Port_Number_Gui_Server_To_Gui_Client>
4.1.1.3.6
Troubleshooting with the Installer
This section tells you how to proceed when errors occur while the installer is running.
Context
If an error occurs, the installer:
● Stops processing
● Displays a dialog informing you about the error
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Database Independent System Copy
CUSTOMER
51
Procedure
1. Check SAP Note 1548438
for known installer issues.
2. If an error occurs during the Define Parameters or the Execute Service phase, do one of the following:
○ Try to solve the problem:
○ To check the installer log files (sapinst.log and sapinst_dev.log) for errors, choose:
○ The LOG FILES tab, if you are using the SL Common GUI.
○ The View Logs menu item, if you are using the Java SDT GUI.
○ To check the log and trace files of the installer GUI for errors:
○ If you use the SL Common GUI, you can find them in the LOG FILES tab.
○ If you use the Java SDT GUI, you can find them in the directory /home/
<Installation_User>/.sdtgui/
○ If the GUI server or the installer GUI does not start, check the file sdtstart.err in the
current /home/<Installation_User> directory.
○ If the installer GUI aborts without an error message, restart the installer GUI as described
in Starting the Installer GUI Separately [page 47].
○ If you use an X Server for Microsoft Windows or other remote desktop tools for the
Remote Access of the Java SDT GUI on Windows workstations and you experience
display problems such as missing repaints or refreshes, contact your X Server vendor.
The vendor can give you information about whether this X Server supports Java Swingbased GUIs and also tell you about further requirements and restrictions. For more
information, see SAP Note 1170809 .
○ Then continue by choosing Retry.
○ If you cannot resolve the problem, abort the installer by choosing one of the following, depending on
the type of installer GUI you use:
○ If you use the SL Common GUI, choose Cancel in the tool menu.
○ If you use the Java SDT GUI, choose Stop from the error message or
in the tool menu.
SAPinst
Exit Process
For more information, see Interrupted Processing of the Installer [page 42].
3. If you cannot resolve the problem, report an incident using component BC-INS.
For more information about using subcomponents of BC-INS, see SAP Note 1669327
4.1.1.3.7
.
Troubleshooting during the Export Process
If the export process aborts during the Execute Service phase (for example, due to a hardware failure, such as
power outage, operating system crash, file system full), you have to repeat the export of the complete
package.
Procedure
● System Copy – export (common issues)
52
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Database Independent System Copy
a. Remove the <Package>.<nnn> dump files, the <Package>.TOC file, and the <Package>.log file.
b. Make sure that all tables in the <Package>.*TSK* file have the status flag xeq or err set.
c. Repeat the export of the complete package.
4.1.2 Setting Up the Target System
Related Information
Transferring the Export Files to the Target Host [page 53]
Installing the Target System [page 54]
4.1.2.1
Transferring the Export Files to the Target Host
This section describes how to transfer the complete export directory with its structure and the generated
DBSIZE.XML file to the target host.
Context
As an alternative, you can also share the complete export directory so that it can be accessed from the target
host.
Procedure
1. On the target host, create a directory <EXPDIR> with sufficient space for the database export files
available.
Caution
Do not create this directory under the installation directory or another directory that contains
installation information (such as the installation media or other export files).
Otherwise, the installer does not ask you to specify the export directory and automatically chooses one
that you may not want to use. In this case, the installer does not display the export directory and you
cannot change it.
2. Transfer all files and directories (recursively) that are located on the source host in the migration export
directory <EXPDIR> from the source host to the target host.
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Database Independent System Copy
CUSTOMER
53
You can choose one of the following methods:
○ Use the migration monitor with the file transfer protocol (FTP) copy option.
Note
Make sure that you use binary mode for transferring the files.
○ Copy the export dump directory manually to the target host.
○ The export dump directory can be shared and thus made accessible on the target host (network
share).
3. Check the permissions of the transferred files on the target host. All files have to be accessible for user
<sapsid>adm of the target system.
Note
If your source system is a distributed system, the files created by the export of the central instance and
the files created by the export of the database instance have to be located in the same <EXPDIR>
directory for the installation of the target system.
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 starting the
target system installation.
Make sure you use the SOURCE.PROPERTIES file from the central instance export when merging the
two export folders.
4.1.2.2
Installing the Target System
This section describes how to set up the target system using the installer.
Prerequisites
There is enough free space on the target system for the database load. To find out the size of the export and
the sizes of the tablespaces or dbspaces that will be created, look at the file DBSIZE.XML, which is located in
the following directory:
Windows: <DRIVE>:\<EXPDIR>\DB\<DATABASE>
UNIX, IBM i: <EXPDIR>/DB/<DATABASE>
SAP MaxDB only: If the database platform of your target system is SAP MaxDB, you must reserve at least two
times the amount of space specified in the DBSIZE.XML file. During the import, monitor the remaining free
space in the database using the SAP MaxDB administration tools Database Manager or Database Studio
and increase it if required.
54
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Database Independent System Copy
Procedure
1. Prepare the target system host as described in the installation guide for the operating system and
database platform intended for the target system. You can find this installation guide at:
http://support.sap.com/sltoolset
Area System Provisioning
Guide for Installation of Systems
Based on SAP NetWeaver 7.0 / 7.0 EHPs
Note
IBM DB2 for Linux, UNIX and Windows only:
Make sure that you read the information provided in section Setup of Database Layout in the installation
documentation.
2. Start the installer as described in the installation guide for the operating system and database platform
intended for the target system.
Caution
If you plan to use Advanced Configuration options during the SAP System Database Import, make sure
you have installed the most current version of the installer to avoid performance problems during the
dialog phase. You can find the latest version of the installer on the SAP Service Marketplace.
3. On the Welcome screen, navigate to the following folder according to the requirements of your target
system:
<Product>
Installation
Software Life-Cycle Options
<System_Variant>
System Copy
<Database>
Target System
Based on <Technical_Stack> .
4. Run the installation options required for your system copy in the sequence they are listed in the specific
folder and according to process flow in Setting Up the Target System Using the Installer [page 53].
5. To install the target system, follow the instructions in the installer input dialogs and enter the required
parameters.
Caution
Heterogeneous system copy: When installing the database instance, you either have to choose
parameter mode Custom or have to check the SAP System > Database Import dialog on the summary
screen and then revise this dialog. Only then appears the dialog screen where you can enter the
migration key, which is required for a heterogeneous system copy. If you forget to revise this dialog
setting during the dialog phase, the installer will abort in the processing phase when checking the
migration key and will ask you for a valid migration key.
○ On the SAP System > Database screen, choose the option Standard System Copy/Migration (loadbased):
The SAP data dump from the migration export media that was created during the export is loaded into
the newly installed SAP system database.
○ When the installer prompts for the migration export, enter the path to the export directory <EXPDIR>.
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Database Independent System Copy
CUSTOMER
55
Caution
IBM DB2 for Linux, UNIX and Windows only:
○ Make sure that you take the information about automatic storage that is provided in the Running
the Installer section in the appropriate installation guide into consideration.
○ The option Deferred Table Creation is not supported for load-based system copies for SAP
systems that are not based on SAP NetWeaver 7.0 or higher.
○ Do not create the installation directory (for example, sapinst_instdir) under the following
directories:
○ UNIX, IBM i: /usr/sap/<SAPSID>
Windows: \usr\sap\<SAPSID>
○ UNIX, IBM i: /sapmnt/<SAPSID>
Windows: \sapmnt\<SAPSID>
6. 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 the installer. The import continues with the
table that has not yet been successfully imported.
56
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Database Independent System Copy
5
Database-Specific System Copy
The following sections describe the database-specific methods for the system copy.
Process
Follow the sequence of steps described in the process flows below for a:
● Central System
● Distributed System
● High Availability System
Central System
To perform the export for a central system, you need to proceed as follows on the central system host:
Process Flow on the Source System (Export)
When performing the export, the installer creates a migration export media which contains the data of the
exported system, and which you use to install the target system.
Run the installer [page 35] to create the export directory structure with labels and to archive SDM and
application-specific file system content.
In the installer, choose the option that corresponds to your database, SAP system, and technology, and then
Database and Central Instance Export.
Example
Choose
Oracle
SAP NetWeaver including Enhancement Package 2
Source System Export
Central System
Software Life-Cycle Options
Based on AS ABAP and AS Java
System Copy
Database and
Central Instance Export
Process Flow on the Source System (Export)
When performing the export, the installer creates a migration export media which contains the data of the
exported system, and which you use to install the target system.
1. In the installer, choose the option that corresponds to your database, SAP system, and technology, and
then Database and Central Instance Export.
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Database-Specific System Copy
CUSTOMER
57
Example
Choose
Copy
SAP NetWeaver including Enhancement Package 2
Oracle
Source System Export
Central System
Software Life-Cycle Options
Based on AS ABAP and AS Java
System
Database
and Central Instance Export
Process Flow on the Target System
1. Follow the instructions on the installer screens.
2. To complete the system copy, you have to perform the follow-up activities [page 60].
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, the installer creates a migration export media which contains the data of the
exported system, and which you use to install the target system.
On the central instance host, run the software [page 35] to create the export directory structure with labels
and to archive SDM and application-specific file system content.
In the installer, choose the option that corresponds to your database, SAP system, and technology, and then
Central Instance Export.
Example
Choose
Oracle
SAP NetWeaver including Enhancement Package 2
Source System Export
Distributed System
Software Life-Cycle Options
Based on AS ABAP and AS Java
System Copy
Central
Instance Export
Process Flow on the Target System
1. On the database instance host, follow the instructions on the installer screens.
2. To complete the system copy, you have to perform the follow-up activities [page 60].
5.1
IBM DB2 for i Procedure
In an SAP system environment, you can create a homogeneous system copy of a DB2 database using the
SAV/RSTLIB system copy method.
Caution
Before you export the Java database, apply SAP Note 1724702
58
CUSTOMER
.
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Database-Specific System Copy
Advantage of the Offline System Copy Method
This method is faster than the database-independent method [page 29].
For more information, see SAP Note 585277
.
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Database-Specific System Copy
CUSTOMER
59
6
Follow-Up Activities
To finish the system copy of your SAP system, perform the follow-up activities described in the following
sections.
Note
The Java engine is not started automatically. After the target system has been installed and the follow-up
activities have been performed, you have to start the Java engine manually.
Related Information
Performing Follow-Up Activities in the Target System [page 61]
60
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Follow-Up Activities
7
Performing Follow-Up Activities in the
Target System
You have to perform the following follow-up activities in the target system.
Note
Before you start the Java engine after the system copy, apply SAP Note 831812
the Java VM parameters as described in SAP Note 723909
and if necessary, change
Related Information
Installing the License Key [page 61]
SAP Solution Manager: Connection Between SLD and LMDB [page 62]
Performing Follow-Up Activities for Java [page 63]
7.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 SAP license key.
You must install a permanent SAP license. When you install your SAP system, a temporary license is
automatically installed.
Caution
● Before the temporary license expires, you must apply for a permanent license key from SAP. We
recommend that you apply for a permanent license key as soon as possible after installing your system.
● Before installing the license key, make sure that SAP Note 831812
is applied.
For more information about ordering and installing the SAP license, see the SAP Library for your release at:
Table 13:
SAP NetWeaver Release
Location
SAP NetWeaver 7.0
http://help.sap.com/nw70
Application Help
NetWeaver by Key Capability
Solution Life Cycle
Management
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Performing Follow-Up Activities in the Target System
SAP
SAP Licenses
CUSTOMER
61
SAP NetWeaver Release
Location
SAP NetWeaver 7.0 including EHP1
http://help.sap.com/nw701
Application Help
NetWeaver by Key Capability
Solution Life Cycle
Management
SAP NetWeaver 7.0 including EHP2
SAP NetWeaver 7.0 including EHP3
SAP Licenses
http://help.sap.com/nw702
Application Help
NetWeaver by Key Capability
Solution Life Cycle
Management
SAP
SAP Licenses
http://help.sap.com/nw703
Application Help
NetWeaver by Key Capability
Solution Life Cycle
Management
SAP
SAP
SAP Licenses
More Information
For more information about SAP license keys, see http://service.sap.com/licensekey
7.2
.
SAP Solution Manager: Connection Between SLD and
LMDB
● Consider the following if you move parts of a system, for example the database, or the complete system to
new hardware:
○ Each change in the host name generates new elements in the system landscape directory (SLD) which
can result in system duplicates.
○ SAP recommends using stable (virtual) host names which remain constant over time, in the system
profiles. SAP Note 1052122
lists the profile parameters evaluated by the SLD Data Suppliers for the
host names.
● If you omitted to use virtual host names at installation time or if you cannot use virtual host names now,
the SLD offers a possibility to prevent the creation of system duplicates. For more information, see SAP
Note 1727294 .
● If you cannot apply SAP Note 1727294
to the SLD, and if you already found a duplicate registration for
the system in the SLD, refer to SAP Note 1694004 for guidance how to clean up such inconsistencies. SAP
describes the cleanup procedure for older SLD releases.
Note 1747926
● If you want to copy an SAP Solution Manager system with a filled Landscape Management Database
(LMDB), see SAP Note 1797014 .
● If you want to create a new synchronization connection between the Landscape Management Database
(LMDB) and the System Landscape Directory (SLD), see SAP Note 1699142 .
● If you want to delete a synchronization connection between two SLD systems or between an SLD system
and LMDB, see SAP Note 1770691 .
62
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Performing Follow-Up Activities in the Target System
7.3
Performing Follow-Up Activities for Java
Depending on the usage types or software units contained in your target system, you have to perform general
and usage type or software unit-specific configuration steps.
Related Information
General Follow-Up Activities [page 63]
Usage Type or Software Unit-Specific Follow-Up Activities [page 66]
7.4
General Follow-Up Activities
You have to perform the following activities for all usage types or software units of the copied SAP system.
Related Information
Configuration Steps for the SAP Java Connector [page 63]
Generating Public-Key Certificates [page 64]
7.4.1 Configuration Steps for the SAP Java Connector
You need to perform these post-installation steps for a copied Java system that includes a component that
has to connect to an ABAP back end using the SAP Java Connector (SAP JCo), for example SAP NetWeaver
Business Warehouse or SAP NetWeaver 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.
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Performing Follow-Up Activities in the Target System
CUSTOMER
63
4. Maintain the required parameters for the RFC destination and repository.
5. Remove the old JCo-destination that was copied from the source system.
6. Restart the Java server and the component.
7.4.2 Generating Public-Key Certificates
Reconfiguring the Public-Key Certificates
After system copy, the public key certificates are wrong on the target system. You need to reconfigure them
as described in the SAP Library for your release at:
Table 14:
SAP NetWeaver Release
Location
SAP NetWeaver 7.0
http://help.sap.com/nw70
NetWeaver by Key Capability
Application Help
Security
Authentication and Single Sign-On
AS Java
User
Authentication on the
Configuring Authentication Mechanisms
Logon Tickets for Single Sign-On
Logon Tickets
SAP
Using
Configuring the Use of
Replacing the Key Pair to Use for Logon
Tickets
SAP NetWeaver 7.0 including EHP1
http://help.sap.com/nw701
NetWeaver by Key Capability
Application Help
Security
Authentication and Single Sign-On
AS Java
User
Authentication on the
Configuring Authentication Mechanisms
Logon Tickets for Single Sign-On
Logon Tickets
SAP
Using
Configuring the Use of
Replacing the Key Pair to Use for Logon
Tickets
SAP NetWeaver 7.0 including EHP2
http://help.sap.com/nw702
NetWeaver by Key Capability
Application Help
Security
Authentication and Single Sign-On
AS Java
User
Authentication on the
Configuring Authentication Mechanisms
Logon Tickets for Single Sign-On
Logon Tickets
SAP
Using
Configuring the Use of
Replacing the Key Pair to Use for Logon
Tickets
64
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Performing Follow-Up Activities in the Target System
SAP NetWeaver Release
Location
SAP NetWeaver 7.0 including EHP3
http://help.sap.com/nw703
NetWeaver by Key Capability
Application Help
Security
Authentication and Single Sign-On
AS Java
SAP
User
Authentication on the
Configuring Authentication Mechanisms
Logon Tickets for Single Sign-On
Logon Tickets
Using
Configuring the Use of
Replacing the Key Pair to Use for Logon
Tickets
Importing the Public-Key Certificates
You also need to import this public-key certificate on any systems that are to accept logon tickets from the AS
Java system. For more information, see the SAP Library for your release at:
Table 15:
SAP NetWeaver Release
Location
SAP NetWeaver 7.0
http://help.sap.com/nw70
NetWeaver by Key Capability
Application Help
Security
Authentication and Single Sign-On
AS Java
SAP
User
Authentication on the
Configuring Authentication Mechanisms
Logon Tickets for Single Sign-On
Logon Tickets
Using
Configuring the Use of
Configuring SAP Web AS ABAP to Accept
Logon Tickets from the J2EE
SAP NetWeaver 7.0 including EHP1
http://help.sap.com/nw701
NetWeaver by Key Capability
Application Help
Security
Authentication and Single Sign-On
AS Java
User
Authentication on the
Configuring Authentication Mechanisms
Logon Tickets for Single Sign-On
Logon Tickets
SAP
Using
Configuring the Use of
Configuring SAP Web AS ABAP to Accept
Logon Tickets from the J2EE
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Performing Follow-Up Activities in the Target System
CUSTOMER
65
SAP NetWeaver Release
Location
SAP NetWeaver 7.0 including EHP2
http://help.sap.com/nw702
NetWeaver by Key Capability
Application Help
Security
Authentication and Single Sign-On
AS Java
User
Authentication on the
Configuring Authentication Mechanisms
Logon Tickets for Single Sign-On
Logon Tickets
SAP
Using
Configuring the Use of
Configuring SAP Web AS ABAP to Accept
Logon Tickets from the J2EE
SAP NetWeaver 7.0 including EHP3
http://help.sap.com/nw703
NetWeaver by Key Capability
Application Help
Security
Authentication and Single Sign-On
AS Java
User
Authentication on the
Configuring Authentication Mechanisms
Logon Tickets for Single Sign-On
Logon Tickets
SAP
Using
Configuring the Use of
Configuring SAP Web AS ABAP to Accept
Logon Tickets from the J2EE
7.5
Usage Type or Software Unit-Specific Follow-Up
Activities
This section includes the steps that you have to perform for specific usage types or software units.
Related Information
EP Core (EPC) [page 67]
Enterprise Portal (EP) [page 70]
Business Intelligence Java Components (BI Java) [page 87]
Development Infrastructure (DI) [page 89]
Self Services (XSS) [page 91]
CRM Java Components (JCRM) / Extended E-Selling Components (XECO) [page 92]
SRM Live Auction Cockpit (SRMLAC) [page 93]
SCM Forecasting & Replenishment Processor (SCM FRP) [page 93]
66
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Performing Follow-Up Activities in the Target System
7.5.1 EP Core (EPC)
Related Information
EPC: Portal [page 67]
Configuring the Portal Content [page 67]
7.5.1.1
EPC: Portal
After system copy, you have to perform some follow-up activities for Enterprise Portal Core.
If trust between a portal and any other system is required, then you need to replace certificates and
reestablish trust with the new system on which the portal is installed. For more information, see Generating
Public-Key Certificates [page 64].
If you have more than one portal in your landscape and the portals share content via a federated portal
network (FPN), see SAP Note 1080080
for more information about follow-up activities.
7.5.1.2
Configuring the Portal Content
Use
After the system copy, the SAP<SAPSID> has changed, but the Logical System ID of the portal system object
in the system landscape still points to the old SAP<SAPSID>. You have to modify it to point to the correct
SAP<SAPSID> by updating the Logical System name.
For more information about the Logical System names, see the SAP Library for your release at:
Table 16:
SAP NetWeaver Release
Location
SAP NetWeaver 7.0
http://help.sap.com/nw70
Application Help
Function-Oriented View <Language>
Integration: Key Areas
Warehousing
Information
Business Intelligence
Data Acquisition
Data
Source System
Connection between Source Systems and BW
Logical
System Names
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Performing Follow-Up Activities in the Target System
CUSTOMER
67
SAP NetWeaver Release
Location
SAP NetWeaver 7.0 including EHP1
http://help.sap.com/nw701
Application Help
Function-Oriented View <Language>
Integration by Key Capability
Warehousing
Information
Business Intelligence
Data Acquisition
Data
Source System
Connection between Source Systems and BW
Logical
System Names
SAP NetWeaver 7.0 including EHP2
http://help.sap.com/nw702
Application Help
Function-Oriented View <Language>
Integration by Key Capability
Warehousing
Data Staging
Information
Business Intelligence
Data
Source System
Logical
Connection between Source Systems and BW
System Names
SAP NetWeaver 7.0 including EHP3
http://help.sap.com/nw702
Application Help
Function-Oriented View <Language>
Integration by Key Capability
Warehousing
System
Modeling
Information
Business Intelligence
Data Acquisition
Data
Source
Connection between Source Systems and BW
Logical System Names
Since the system alias has to be the same as the Logical System name, you have to update it, too.
For more information about the system aliases, see the SAP Library for your release at:
Table 17:
SAP NetWeaver Release
Location
SAP NetWeaver 7.0
http://help.sap.com/nw70
Application Help
Function-Oriented View <Language>
by Key Capability
Administration
Landscape
SAP NetWeaver 7.0 including EHP1
Portal Administration Guide
System Configuration
by Key Capability
Administration
CUSTOMER
System
Application Help
Function-Oriented View <Language>
68
System
System Aliases
http://help.sap.com/nw701
Landscape
People Integration
People Integration
Portal Administration Guide
System Configuration
System
System
System Aliases
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Performing Follow-Up Activities in the Target System
SAP NetWeaver Release
Location
SAP NetWeaver 7.0 including EHP2
http://help.sap.com/nw702
Application Help
Function-Oriented View <Language>
by Key Capability
Administration
Landscape
SAP NetWeaver 7.0 including EHP3
Portal Administration Guide
System Configuration
System
System
System Aliases
http://help.sap.com/nw703
Application Help
Function-Oriented View <Language>
by Key Capability
Administration
Landscape
People Integration
People Integration
Portal Administration Guide
System Configuration
System
System
System Aliases
Procedure
Proceed in one of the following ways:
● Update the information in the existing system.
All parameters that contain information about the old system have to be updated to point to the new
system. That is, if the host name or the port has been changed, the system object has to be updated
accordingly.
1. Update the Logical System name to point to the new system SAP<SAPSID>.
2. Update the system alias to be the same as the new Logical System name.
3. Set the new system alias to be default.
4. Update all relevant properties of the host and the ports values of the old systems.
5. Change the ID/name of the old system.
After the value of the alias has been updated, the old content will not work, because it still points to the old
alias. Moreover, all new role uploads from the new system will be created under a new folder and will not
overwrite the existing one.
Therefore, you also have to change the ID values of the folders of the migrated content and the system
value of the uploaded content.
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Performing Follow-Up Activities in the Target System
CUSTOMER
69
● Create a new system that points to the new environment. For more information, see the SAP Library for
your release at:
Table 18:
SAP NetWeaver Release
Location
SAP NetWeaver 7.0
http://help.sap.com/nw70
Application Help
Function-Oriented View <Language>
by Key Capability
People Integration
Portal Administration Guide
System Administration
Upload of Roles from ABAP-
Based Systems
http://help.sap.com/nw701
SAP NetWeaver 7.0 including EHP1
Application Help
Function-Oriented View <Language>
by Key Capability
People Integration
Portal Administration Guide
System Administration
Upload of Roles from ABAP-
Based Systems
http://help.sap.com/nw702
SAP NetWeaver 7.0 including EHP2
Application Help
Function-Oriented View <Language>
by Key Capability
People Integration
Portal Administration Guide
System Administration
Upload of Roles from ABAP-
Based Systems
http://help.sap.com/nw703
SAP NetWeaver 7.0 including EHP3
Application Help
Function-Oriented View <Language>
by Key Capability
People Integration
Portal Administration Guide
System Administration
Upload of Roles from ABAP-
Based Systems
Make sure that you update the ID values of the folders of the migrated content and the system value of the
uploaded content.
7.5.2 Enterprise Portal (EP)
Related Information
EP: Knowledge Management and Collaboration [page 71]
70
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Performing Follow-Up Activities in the Target System
7.5.2.1
EP: Knowledge Management and Collaboration
Use
After the system copy, the Knowledge Management and Collaboration (KMC) target system still has access to
the same data as the original source system. If the source and target system have write access to the same
data, this results in serious inconsistencies in both systems. For this reason, it is essential to prevent both
systems from using the same data.
Critical items that are accessed by both systems are, for example:
● Indexes for search and classification (TREX)
● Data in external repositories, for example, on file system shares
● Data on groupware servers
Note
SAP NetWeaver 7.0 SR3/EHP1 SR1, Java only: If content exchange is configured on the source system,
the same configuration exists on the target system after the system copy. However, in most cases, it does
not makes sense to have the same configuration on both the source and target system. For this reason, you
need to remove the configuration on the target system with the help of acleanup script and then set up a
new configuration. The cleanup script is available as an attachment to SAP Note 883859 .
Procedure
To prevent source and target system from working with the same data, reconfigure the following components
on the target system:
● TREX
● Repository Managers
● Services
● Collaboration
The tables below summarize the configuration steps for each of the components and specify where you can
find more information.
TREX
After the system copy, the target system is still connected to the same TREX installation as the source system.
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, otherwise they will also
be deleted on the source system.
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Performing Follow-Up Activities in the Target System
CUSTOMER
71
Table 19:
Task
Detailed Information
For the target system, install a new instance of TREX.
http://service.sap.com/installNW70
Standalone Engines
3 – Installation -
SAP NetWeaver Search and
Classification TREX
72
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Performing Follow-Up Activities in the Target System
Task
Detailed Information
On the target system, set up the connection to the newly in­
For more information, see the SAP Library for your release
stalled TREX system.
at:
TREX <version> for SAP NetWeaver 7.0
●
SAP NetWeaver 7.0:
○
TREX 7.0
http://help.sap.com/nw70
Application Help
Function-Oriented View <Language>
Information Integration: Key Areas
Classification TREX
NetWeaver 7.0
Search and
TREX 7.0 for SAP
TREX Configuration
Installation Configuration
Post-
Client Side
Java
Specifying the
Application (HTTP Connection)
Address of the TREX Name Server
○
TREX 7.1
http://help.sap.com/nw70
Application Help
Function-Oriented View <Language>
Information Integration: Key Areas
Classification TREX
7.0
TREX 7.1 for SAP NetWeaver
TREX Configuration
Configuration
Application
Search and
TREX Basic
Connecting TREX with an
Connecting TREX with a Java
Specifying the
Application (HTTP Connection)
Address of the TREX Name Server
●
SAP NetWeaver including EHP1:
○
TREX 7.0
http://help.sap.com/nw701
Application Help
Function-Oriented View <Language>
Information Integration by Key Capability
Search and Classification TREX
SAP NetWeaver 7.0
Search
TREX 7.0 for
TREX Configuration
Installation Configuration
Client Side
PostJava
Specifying the
Application (HTTP Connection)
Address of the TREX Name Server
○
TREX 7.1
http://help.sap.com/nw701
Application Help
Function-Oriented View <Language>
Information Integration by Key Capability
Search and Classification TREX
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Performing Follow-Up Activities in the Target System
Search
TREX 7.1 for
CUSTOMER
73
Task
Detailed Information
SAP NetWeaver 7.0
Basic Configuration
Application
TREX Configuration
TREX
Connecting TREX with an
Connecting TREX with a Java
Application (HTTP Connection)
Specifying the
Address of the TREX Name Server
●
SAP NetWeaver including EHP2:
○
TREX 7.0
http://help.sap.com/nw702
Help
Application
Function-Oriented View <Language>
Information Integration by Key Capability
Search and Classification TREX
SAP NetWeaver 7.0
Search
TREX 7.0 for
TREX Configuration
Client Side
Installation Configuration
Application (HTTP Connection)
PostJava
Specifying the
Address of the TREX Name Server
○
TREX 7.1
http://help.sap.com/nw702
Help
Application
Function-Oriented View <Language>
Information Integration by Key Capability
Search and Classification TREX
SAP NetWeaver 7.0
Basic Configuration
Application
Search
TREX 7.1 for
TREX Configuration
TREX
Connecting TREX with an
Connecting TREX with a Java
Application (HTTP Connection)
Specifying the
Address of the TREX Name Server
●
SAP NetWeaver including EHP3:
○
TREX 7.0
http://help.sap.com/nw703
Help
Application
Function-Oriented View <Language>
Information Integration by Key Capability
and Operational Analytics
Technology
Other Search
Search and Classification TREX
TREX 7.0 for SAP NetWeaver 7.0
Configuration
Client Side
Search
TREX
Post-Installation Configuration
Java Application (HTTP Connection)
Specifying the Address of the TREX Name
Server
74
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Performing Follow-Up Activities in the Target System
Task
Detailed Information
○
TREX 7.1
http://help.sap.com/nw703
Help
Application
Function-Oriented View <Language>
Information Integration by Key Capability
and Operational Analytics
Technology
Other Search
Search and Classification TREX
TREX 7.1 for SAP NetWeaver 7.0
Configuration
Search
TREX
TREX Basic Configuration
Connecting TREX with an Application
Connecting
TREX with a Java Application (HTTP Connection)
Specifying the Address of the TREX Name Server
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Performing Follow-Up Activities in the Target System
CUSTOMER
75
Task
Detailed Information
On the target system, delete old indexes that belong to the
For more information, see the SAP Library for your release
source system. Define and generate new indexes for the tar­ at:
get system.
●
SAP NetWeaver 7.0:
http://help.sap.com/nw70
Note
Application Help
Function-Oriented View <Language>
The prerequisite for this step is that all repository man­
Integration: Key Areas
agers are configured correctly for the target system.
Administration Guide
System Configuration
●
Information
Knowledge Management
System Administration
‘Index Administration’ iView
SAP NetWeaver including EHP1:
http://help.sap.com/nw701
Application Help
Function-Oriented View <Language>
Integration by Key Capability
Management
Administration
Information
Knowledge
Administration Guide
System Configuration
System
‘Index
Administration’ iView
●
SAP NetWeaver including EHP2:
http://help.sap.com/nw702
Application Help
Function-Oriented View <Language>
Integration by Key Capability
Management
Administration
Information
Knowledge
Administration Guide
System Configuration
System
‘Index
Administration’ iView
●
SAP NetWeaver including EHP3:
http://help.sap.com/nw703
Application Help
Function-Oriented View <Language>
Integration by Key Capability
Management
Administration
Information
Knowledge
Administration Guide
System Configuration
System
‘Index
Administration’ iView
Repository Managers
Ensure that the target system does not have write access to the same repositories as the source system.
76
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Performing Follow-Up Activities in the Target System
Table 20:
Task
Detailed Information
On the target system, check the configuration of all external For more information, see the SAP Library for your release
and internal repository managers that have write access to
the same data as the source system. Make sure that the
source and target system do not have write access to the
at:
●
SAP NetWeaver 7.0:
http://help.sap.com/nw70
same data. For example, check the repository manager set­
Application Help
Function-Oriented View <Language>
tings for:
Information
Knowledge Management
●
CM FSDB or CM DBFS repositories
Integration: Key Areas
●
Simple File System repositories
Administration Guide
System Administraton
System Configuration
Content Management
Configuration
Repositories and Repository Managers
External Repositories
●
SAP NetWeaver 7.0 including EHP1:
http://help.sap.com/nw701
Application Help
Function-Oriented View <Language>
Integration by Key Capability
Management
Administraton
Knowledge
Administration Guide
System
System Configuration
Management Configuration
Repository Managers
●
Information
Repositories and
External Repositories
SAP NetWeaver 7.0 including EHP2:
http://help.sap.com/nw702
Application Help
Function-Oriented View <Language>
Integration by Key Capability
Management
Administraton
Information
Knowledge
Administration Guide
System
System Configuration
Management Configuration
Repository Managers
●
Content
Content
Repositories and
External Repositories
SAP NetWeaver 7.0 including EHP3:
http://help.sap.com/nw703
Application Help
Function-Oriented View <Language>
Integration by Key Capability
Management
Administraton
Information
Knowledge
Administration Guide
System
System Configuration
Management Configuration
Repository Managers
Content
Repositories and
External Repositories
Services
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Performing Follow-Up Activities in the Target System
CUSTOMER
77
Table 21:
Task
Detailed Information
Content Exchange
For more information, see the SAP Library for your release
at:
If content exchange is in use, the configuration on the
source and target system is identical. However, it does not
●
make sense to have the same content exchange procedures
SAP NetWeaver 7.0:
http://help.sap.com/nw70
configured twice. For this reason, delete the configuration
Application Help
Function-Oriented View <Language>
on the target system and, if required, set up a new configu­
Information
Knowledge Management
ration. Run a cleanup file to remove the existing configura­
Integration: Key Areas
tion on the target system:
Administration Guide
System Administration
Download the cleanup file attached to SAP Note
System Configuration
Content Management
1238351
Configuration
●
. Note that the cleanup procedure automati­
cally creates a new ID for a syndicator and subscriber.
●
Import the cleanup file into the target portal. To do this,
choose
System Administration
Management
and then, on the right, choose
●
Import
●
SAP NetWeaver 7.0 including EHP1:
http://help.sap.com/nw701
Knowledge Management
Content Exchange
Service
System
Configuration
Actions
Global Services
Content
Application Help
Function-Oriented View <Language>
Integration by Key Capability
.
Management
If required, configure new content exchange settings on
Administration
the target system.
Information
Knowledge
Administration Guide
System
System Configuration
Management Configuration
Content
Global Services
Content Exchange Service
●
SAP NetWeaver 7.0 including EHP2:
http://help.sap.com/nw702
Application Help
Function-Oriented View <Language>
Integration by Key Capability
Management
Administration
Information
Knowledge
Administration Guide
System
System Configuration
Management Configuration
Content
Global Services
Content Exchange Service
●
SAP NetWeaver 7.0 including EHP3:
http://help.sap.com/nw703
Application Help
Function-Oriented View <Language>
Integration by Key Capability
Management
Administration
Information
Knowledge
Administration Guide
System Configuration
Management Configuration
System
Content
Global Services
Content Exchange Service
78
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Performing Follow-Up Activities in the Target System
Task
Detailed Information
URL Generator
For more information, see the SAP Library for your release
On the target system, check the settings for the Host and
Alternative Host parameters.
at:
●
SAP NetWeaver 7.0:
http://help.sap.com/nw70
Application Help
Function-Oriented View <Language>
Integration: Key Areas
Information
Knowledge Management
Administration Guide
System Administration
System Configuration
Content Management
Configuration
Global Services
URL Generator
Service
●
SAP NetWeaver 7.0 including EHP1:
http://help.sap.com/nw701
Application Help
Function-Oriented View: English
Information
Integration by Key Capability
Management
Administration
Knowledge
Administration Guide
System
System Configuration
Management Configuration
Content
Global Services
URL
Generator Service
●
SAP NetWeaver 7.0 including EHP2:
http://help.sap.com/nw702
Application Help
Function-Oriented View <Language>
Integration by Key Capability
Management
Administration
Information
Knowledge
Administration Guide
System
System Configuration
Management Configuration
Content
Global Services
URL
Generator Service
●
SAP NetWeaver 7.0 including EHP3:
http://help.sap.com/nw703
Application Help
Function-Oriented View <Language>
Integration by Key Capability
Management
Administration
Information
Knowledge
Administration Guide
System
System Configuration
Management Configuration
Content
Global Services
URL
Generator Service
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Performing Follow-Up Activities in the Target System
CUSTOMER
79
Task
Detailed Information
System Landscape: On the target system, delete the old
Log on to the Portal and choose
system IDs that belong to the source system.
System Administration
System Configuration
Knowledge Management
Content Management
Global Services
Landscape Definitions
Systems
Systems
System
Content Management
.
Scheduler Service: If the target system is an SAP Java clus­ For more information, see the SAP Library for your release
ter, then you must assign scheduler tasks to the new sys­
at:
tem IDs of the target system. After the system copy, tasks
●
are still assigned to the IDs of the source system.
SAP NetWeaver 7.0:
http://help.sap.com/nw70
Application Help
Function-Oriented View <Language>
Information
Integration: Key Areas
Knowledge Management
Administration Guide
Minimal Configuration for
Knowledge Management
Cluster Only: Assigning
Tasks to Nodes
●
SAP NetWeaver 7.0 including EHP1:
http://help.sap.com/nw701
Application Help
Function-Oriented View <Language>
Integration by Key Capability
Management
Information
Knowledge
Administration Guide
Minimal
Configuration for Knowledge Management
Cluster
Only: Assigning Tasks to Nodes
●
SAP NetWeaver 7.0 including EHP2:
http://help.sap.com/nw702
Application Help
Function-Oriented View <Language>
Integration by Key Capability
Management
Information
Knowledge
Administration Guide
Minimal
Configuration for Knowledge Management
Cluster
Only: Assigning Tasks to Nodes
●
SAP NetWeaver 7.0 including EHP3:
http://help.sap.com/nw703
Application Help
Function-Oriented View <Language>
Integration by Key Capability
Management
Information
Knowledge
Administration Guide
Minimal
Configuration for Knowledge Management
Cluster
Only: Assigning Tasks to Nodes
Collaboration
80
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Performing Follow-Up Activities in the Target System
Table 22:
Task
Detailed Information
On the target system, adapt the room back-end properties
For more information, see the SAP Library for your release
server address, server port, and Web protocol.
at:
●
SAP NetWeaver 7.0:
http://help.sap.com/nw70
Application Help
Function-Oriented View <Language>
Integration by Key Capability
Administration Guide
Portal
People
Collaboration
Making Rooms Available in the
Preparing Rooms for Use
Defining the Web
Address and Automatic E-Mail Dispatch for Rooms
●
SAP NetWeaver 7.0 including EHP1:
http://help.sap.com/nw701
Application Help
Function-Oriented View <Language>
Integration by Key Capability
Administration Guide
Portal
People
Collaboration
Making Rooms Available in the
Preparing Rooms for Use
Defining the Web
Address and Automatic E-Mail Dispatch for Rooms
●
SAP NetWeaver 7.0 including EHP2:
Application Help
http://help.sap.com/nw702
Function-Oriented View <Language>
Integration by Key Capability
Administration Guide
Portal
People
Collaboration
Making Rooms Available in the
Preparing Rooms for Use
Defining the Web
Address and Automatic E-Mail Dispatch for Rooms
●
SAP NetWeaver 7.0 including EHP3:
Application Help
http://help.sap.com/nw703
Function-Oriented View <Language>
Integration by Key Capability
Administration Guide
Portal
People
Collaboration
Making Rooms Available in the
Preparing Rooms for Use
Defining the Web
Address and Automatic E-Mail Dispatch for Rooms
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Performing Follow-Up Activities in the Target System
CUSTOMER
81
Task
Detailed Information
On the target system, generate a new index to enable
●
search operations in the content of rooms.
SAP NetWeaver 7.0:
http://help.sap.com/nw70
Application Help
Function-Oriented View <Language>
Integration by Key Capability
Administration Guide
Portal
People
Collaboration
Making Rooms Available in the
Preparing Rooms for Use
Configuring the
Search for Room Content
●
SAP NetWeaver 7.0 including EHP1:
Application Help
http://help.sap.com/nw701
Function-Oriented View <Language>
Integration by Key Capability
Administration Guide
Portal
People
Collaboration
Making Rooms Available in the
Preparing Rooms for Use
Configuring the
Search for Room Content
●
SAP NetWeaver 7.0 including EHP2:
http://help.sap.com/nw702
Application Help
Function-Oriented View <Language>
Integration by Key Capability
Administration Guide
Portal
People
Collaboration
Making Rooms Available in the
Preparing Rooms for Use
Configuring the
Search for Room Content
●
SAP NetWeaver 7.0 including EHP3:
http://help.sap.com/nw703
Application Help
Function-Oriented View <Language>
Integration by Key Capability
Administration Guide
Portal
People
Collaboration
Making Rooms Available in the
Preparing Rooms for Use
Configuring the
Search for Room Content
82
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Performing Follow-Up Activities in the Target System
Task
On the target system, check the properties of the
Detailed Information
●
roomsearch object. Make sure that the parameter Use
SAP NetWeaver 7.0:
http://help.sap.com/nw70
TREX is set.
Application Help
Function-Oriented View <Language>
Integration by Key Capability
Administration Guide
Portal
People
Collaboration
Making Rooms Available in the
Preparing Rooms for Use
Configuring the
Search for Room Content
●
SAP NetWeaver 7.0 including EHP1:
Application Help
http://help.sap.com/nw701
Function-Oriented View <Language>
Integration by Key Capability
Administration Guide
Portal
People
Collaboration
Making Rooms Available in the
Preparing Rooms for Use
Configuring the
Search for Room Content
●
SAP NetWeaver 7.0 including EHP2:
http://help.sap.com/nw702
Application Help
Function-Oriented View <Language>
Integration by Key Capability
Administration Guide
Portal
People
Collaboration
Making Rooms Available in the
Preparing Rooms for Use
Configuring the
Search for Room Content
●
SAP NetWeaver 7.0 including EHP3:
http://help.sap.com/nw703
Application Help
Function-Oriented View <Language>
Integration by Key Capability
Administration Guide
Portal
People
Collaboration
Making Rooms Available in the
Preparing Rooms for Use
Configuring the
Search for Room Content
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Performing Follow-Up Activities in the Target System
CUSTOMER
83
Task
Detailed Information
On the target system, configure the connection to the re­
For more information, see the SAP Library for your release
quired groupware server.
at:
●
SAP NetWeaver 7.0:
http://help.sap.com/nw70
Application Help
Function-Oriented View <Language>
Integration by Key Capability
Administration Guide
People
Collaboration
Groupware
Installing and
Configuring E-Mail Connectivity
●
SAP NetWeaver 7.0 including EHP1:
http://help.sap.com/nw701
Application Help
Function-Oriented View <Language>
Integration by Key Capability
Administration Guide
People
Collaboration
Groupware
Installing and
Configuring E-Mail Connectivity
●
SAP NetWeaver 7.0 including EHP2:
http://help.sap.com/nw702
Application Help
Function-Oriented View <Language>
Integration by Key Capability
Administration Guide
People
Collaboration
Groupware
Installing and
Configuring E-Mail Connectivity
●
SAP NetWeaver 7.0 including EHP3:
http://help.sap.com/nw703
Application Help
Function-Oriented View <Language>
Integration by Key Capability
Administration Guide
People
Collaboration
Groupware
Installing and
Configuring E-Mail Connectivity
84
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Performing Follow-Up Activities in the Target System
Task
Detailed Information
If the e-mailing service is active on the source system, but is
For more information, see the SAP Library for your release
not required on the target system, you need to delete the e-
at:
mail transport. After deletion of the transport, e-mailing is
disabled. E-mails will no longer be automatically sent, for ex­
●
SAP NetWeaver 7.0:
http://help.sap.com/nw70
ample, when members are excluded from a room or docu­
Application Help
Function-Oriented View <Language>
ments are updated and deleted.
Integration by Key Capability
Administration Guide
Collaboration
Groupware
Configuring E-Mail Connectivity
People
Installing and
Configuration Steps
Creating an E-Mail Transport
●
SAP NetWeaver 7.0 including EHP1:
http://help.sap.com/nw701
Application Help
Function-Oriented View <Language>
Integration by Key Capability
Administration Guide
Collaboration
Groupware
Configuring E-Mail Connectivity
People
Installing and
Configuration Steps
Creating an E-Mail Transport
●
SAP NetWeaver 7.0 including EHP2:
http://help.sap.com/nw702
Application Help
Function-Oriented View <Language>
Integration by Key Capability
Administration Guide
Collaboration
Groupware
Configuring E-Mail Connectivity
People
Installing and
Configuration Steps
Creating an E-Mail Transport
●
SAP NetWeaver 7.0 including EHP3:
http://help.sap.com/nw703
Application Help
Function-Oriented View <Language>
Integration by Key Capability
Administration Guide
Collaboration
Groupware
Configuring E-Mail Connectivity
People
Installing and
Configuration Steps
Creating an E-Mail Transport
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Performing Follow-Up Activities in the Target System
CUSTOMER
85
Task
Detailed Information
On the target system, reconfigure the ServerName and
For more information, see the SAP Library for your release
ServerPort for the application sharing server.
at:
●
SAP NetWeaver 7.0:
http://help.sap.com/nw70
Application Help
Function-Oriented View <Language>
Integration by Key Capability
Administration Guide
People
Collaboration
Real-Time Collaboration
Configuring Real-Time Collaboration
Application Sharing Server (RTC)
Configuring the
Setting Application
Sharing Server Parameters (RTC)
●
SAP NetWeaver 7.0 including EHP1:
http://help.sap.com/nw701
Application Help
Function-Oriented View <Language>
Integration by Key Capability
Administration Guide
People
Collaboration
Real-Time Collaboration
Configuring Real-Time Collaboration
Application Sharing Server (RTC)
Configuring the
Setting Application
Sharing Server Parameters (RTC)
●
SAP NetWeaver 7.0 including EHP2:
http://help.sap.com/nw702
Application Help
Function-Oriented View <Language>
Integration by Key Capability
Administration Guide
People
Collaboration
Real-Time Collaboration
Configuring Real-Time Collaboration
Application Sharing Server (RTC)
Configuring the
Setting Application
Sharing Server Parameters (RTC)
●
SAP NetWeaver 7.0 including EHP3:
http://help.sap.com/nw703
Application Help
Function-Oriented View <Language>
Integration by Key Capability
Administration Guide
People
Collaboration
Real-Time Collaboration
Configuring Real-Time Collaboration
Application Sharing Server (RTC)
Configuring the
Setting Application
Sharing Server Parameters (RTC)
86
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Performing Follow-Up Activities in the Target System
7.5.3 Business Intelligence Java Components (BI Java)
You have to perform the following follow-up activities for usage type BI Java.
Related Information
Business Intelligence (BI Java) [page 87]
Basic Configuration for Usage Type BI Java [page 88]
7.5.3.1
Business Intelligence (BI Java)
Use
Follow the instructions in this section if the entries for source system connection have not been copied to the
services file of your target system.
Prerequisites
You have performed a system copy that includes SAP NetWeaver Business Warehouse (SAP NetWeaver BW).
Procedure
Adding Entries to the Services File
You have to do the following to add the entries to the services file:
If your target host runs on a UNIX platform
1. 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 or
database.
2. Edit the file /etc/services.
3. Add the entries for your source system connection, for example sapgw47 3347.
If your target host runs on a Windows platform or on IBM i
1. Log on to your target system as a member of the local administration group.
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Performing Follow-Up Activities in the Target System
CUSTOMER
87
2. Edit the file <WindowsDirectory>\system32\drivers\etc\services.
3. Add the entries for your source system connection, for example sapgw47 3347.
7.5.3.2
Basic Configuration for Usage Type BI Java
As of SAP NetWeaver 7.0 Support Package 8, you can run the wizard-based configuration task BI-Java /
Technical configuration of BI-Java (repeatable, reproducible) using the configuration wizard to automatically
configure the required settings for portal and BI Java integration.
For more information, see the SAP Library for your release at:
Table 23:
SAP NetWeaver Release
Location
SAP NetWeaver 7.0
http://help.sap.com/nw70
Library: <Language>
Consultant's Guide
Analysis
SAP NetWeaver 7.0 including EHP1
Consultant's Guide
Analysis
Analysis
88
CUSTOMER
Enterprise Reporting, Query, and
.
Application Help
SAP NetWeaver
SAP
Technology
Enterprise Reporting, Query, and
http://help.sap.com/nw703
Consultant's Guide
SAP
Technology
Wizard-Based Configuration of BI Java
Library: <Language>
.
Application Help
SAP NetWeaver
http://help.sap.com/nw702
Consultant's Guide
SAP NetWeaver 7.0 including EHP3
Enterprise Reporting, Query, and
Wizard-Based Configuration of BI Java
Library: <Language>
SAP
Technology
Wizard-Based Configuration of BI Java
Library: <Language>
SAP NetWeaver 7.0 including EHP2
SAP NetWeaver
http://help.sap.com/nw701
Analysis
Application Help
.
Application Help
SAP NetWeaver
SAP
Technology
Enterprise Reporting, Query, and
Wizard-Based Configuration of BI Java
.
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Performing Follow-Up Activities in the Target System
7.5.4 Development Infrastructure (DI)
You have to perform the following manual steps on the target system after moving an SAP system with usage
type Development Infrastructure (DI). 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 a single host after the move.
Procedure
1. If you are using an LDAP server for user management, it should be running to ensure that all the users that
were created when the Development Infrastructure (DI) was on the source system will still be valid after
the move to the target system.
2. Check the Java Engine configuration:
○ Set MaxHeapSize and other engine parameters to the recommended values.
For more information, see your installation guide.
○ If your database is SAP MaxDB, perform the following steps:
1. Upgrade your SAP MaxDB database to at least version 29.
2. Set the JOIN_OPERATOR_IMPLEMENTATION parameter to IMPROVED (setting this value is only
possible using the DB-WebUI in SAPMMC).
3. Restart the database.
○ For general recommendations for the configuration of the Development Infrastructure Servers, see
SAP Note889038 .
3. Design Time Repository (DTR):
○ 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 have
downloaded from SAP Software Distribution Center to deploy the SAP NetWeaver Development
Infrastructure (NWDI).
To only deploy this database schema, you have to extract the SCA file. You can do this by
appending .zip to the filename. Then you can use a normal archive tool like WinZip. Under the
subfolder DEPLOYARCHIVES, you can find the SDA sap.com~tc~dtr~dbschema.sda for the
database schema. This SDA must be deployed using the Software Deployment Manager (SDM).
Note
During deployment, use the option Update deployed SDAs/SCAs that have any version. This option
can be set in the Deployment tab on SDM.
○ Restart DTR server.
○ Change the URL of the name server (in name server configuration page in Web UI: http://
<dtrhost>:<port>/dtr/system-tools/administration/NameServerConfiguration) if you
intend to use a different name server for the moved DTR instance, or if the name server was also
moved.
○ Perform Update Statistics (30%) on the database.
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Performing Follow-Up Activities in the Target System
CUSTOMER
89
Note
If your database is SAP MaxDB, you can use the database manager to update the database
statistics.
4. System Landscape Directory (SLD):
If you used the SLD on the source host as the name server, you need to change the CimomURL to point to
the target host. To do so, proceed as follows:
a. Log on to the SLD as administrator.
b. Choose
Administrator
Directory
Content Maintenance , then under Class, choose
System Landscape
<your local SLD> .
c. Under CimomURL, change the host to target host.
Caution
Do not change the ObjectServer attribute.
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.
For more information about these parameters, see your installation guide.
6. Change Management Service (CMS):
The main steps in CMS involve resetting the fields containing URLs to other components (such as DTR,
CBS, SLD).
○ If CMS has not been configured yet, proceed as follows:
1. Copy the folder /usr/sap/trans/EPS/in/CMS<host><SAPSID>, including its content, to the
target host.
2. Rename the folder to the new host value and new SAP system ID (if changed).
3. Make sure that the engine user (<SAPSID>adm) has write permissions in the copied folder.
○ If CMS has been configured and you have used it already, proceed as follows:
1. For the domain (in the Domain Data tab):
1. Change the SLD URL to point to the target host.
2. Change the CMS URL to point to the target host.
3. Change the transport directory to the appropriate directory on the new CMS (target host).
4. Save the domain. You should see a status message that the data was saved successfully.
5. Update CMS by choosing Update CMS. You should see a status message that the CMS update
was successful.
2. 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 configured in the domain
(see Domain Data tab page).
3. For each track (in the Track Data tab page):
1. Change the CBS and DTR URLs.
2. 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.
90
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Performing Follow-Up Activities in the Target System
3. Save the track definition.
You should see a status message that the data was saved successfully.
4. Restore system state (of the DEV system). This places the software components (SCs) into
the import queue of this system.
5. Import these SCs. After the successful import, you should see a status for each SC.
7. IDE:
○ 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.
○ Import the development configuration that you used earlier for development.
Now you are ready to begin the development with you new (relocated) Development Infrastructure (DI).
8. Verification Steps (optional)
The following steps are optional and verify that the Development Infrastructure (DI) is fully functional after
the move:
1. Log on to the DTR (using the browser) for all defined users and browse the repository.
2. Using IDE, create a new development component (DC), check it in and activate it:
○ The activation should be successful.
○ The name of the development component (DC) must be reserved on the name server.
3. 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.
4. Import the change request into the CONS system (from the CMS Transport Studio).
5. Assemble a new version of your software components (SCs) in one of the tracks.
7.5.5 Self Services (XSS)
Related Information
Re-Creating the JCo Destinations [page 92]
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Performing Follow-Up Activities in the Target System
CUSTOMER
91
7.5.5.1
Re-Creating the JCo Destinations
You must re-create the JCo destinations as described in the SAP Library for your release at:
Table 24:
SAP NetWeaver Release
Location
SAP NetWeaver 7.0
http://help.sap.com/nw70
Development Information
Developers's Guides: English
Java
Core Development Tasks
Interfaces
Destinations
Development Information
Development Information
Development Information
Using
Developing User
Web Dynpro for Java
Dynpro Content Administrator
For more information, see SAP Note 899144
Fundamentals
Core Development Tasks
Destinations
Web
.
Developers's Guides: English
Interfaces
Ensuring Quality
Creating JCo
http://help.sap.com/nw703
Java
Using
Developing User
Web Dynpro for Java
Dynpro Content Administrator
SAP NetWeaver 7.0 including EHP3
Fundamentals
Core Development Tasks
Destinations
Web
.
Developers's Guides: English
Interfaces
Ensuring Quality
Creating JCo
http://help.sap.com/nw702
Java
Using
Developing User
Web Dynpro for Java
Dynpro Content Administrator
SAP NetWeaver 7.0 including EHP2
Fundamentals
Core Development Tasks
Destinations
Web
.
Developers's Guides: English
Interfaces
Ensuring Quality
Creating JCo
http://help.sap.com/nw701
Java
Using
Developing User
Web Dynpro for Java
Dynpro Content Administrator
SAP NetWeaver 7.0 including EHP1
Fundamentals
Ensuring Quality
Web
Creating JCo
.
.
7.5.6 CRM Java Components (JCRM) / Extended E-Selling
Components (XECO)
92
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Performing Follow-Up Activities in the Target System
7.5.7 MapBox
You need to proceed as follows to restore the configuration of the CRM Java component MapBox on the target
system.
Procedure
1. Shut down the Java engine.
2. 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 location on 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. Start the Java engine and MapBox from the URL as described in Post-Installation Steps for MapBox in the
Installation Guide — SAP CRM 7.0 including Enhancement Package 1 on <OS>: <Technical Stack> at
http://service.sap.com/crm-inst .
Results
You have restored the configuration for MapBox on the target system.
7.5.8 SRM Live Auction Cockpit (SRMLAC)
7.5.9 SCM Forecasting & Replenishment Processor (SCM
FRP)
After the system copy, you must perform follow-up activities as described in SAP Note 1033225
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Performing Follow-Up Activities in the Target System
.
CUSTOMER
93
8
Additional Information
Related Information
Jload Procedures Using the Java Migration Monitor [page 95]
Analysis of the Export and Import Times [page 103]
Removing the Installation Files of the Installer [page 109]
8.1
Copying the Installation Media Manually to Your IBM i
Use
This section describes a secure way to copy the required installation media from your Windows PC to your IBM
i. To copy the media, you have to use a binary share ROOTBIN. This guarantees that the content of the media is
copied correctly from the Windows PC to your IBM i. No copied content is corrupted, and no copied files with
longer file names are shortened by a converting share.
Procedure
Creating a Binary Share ROOTBIN on IBM i
If you do not already have a binary share ROOTBIN on your IBM i, and you want to copy manually media from
your Windows PC into the IFS of your IBM i, you have to create this share manually using the IBM Systems
Director Navigator for i. To do so, proceed as follows:
1. Start the IBM Systems Director Navigator for i on your Windows PC.
2. Connect to your IBM i using My Connections.
3. To create or change the share ROOTBIN, choose
File Systems
File Shares .
4. Right-click File Shares Open i5/OS Netserver .
A new screen i5/OS Netserver appears.
5. Click the folder Shared Objects to see the shares.
6. To check the already existing share ROOTBIN or create a new share ROOTBIN, right-click
New
File .
Note
The share ROOTBIN must have the access permission Read/Write and the path name should be /.
94
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Additional Information
7. On the Text Conversion tab, do not select Allow file text conversion.
8. To save the share ROOTBIN, press OK.
Now you have created the share ROOTBIN on your IBM i.
Copying the Installation Media Manually Using the Binary Share ROOTBIN
1. To open the command prompt on Windows, choose
Start
Run .
2. Enter cmd.exe.
3. Press OK.
The command prompt appears.
4. In the command prompt, enter net use.
All network connections to shared resources are displayed.
5. To change to the new network drive, enter X: in the command prompt.
6. Create the subdirectories in your IFS where you want to copy the required media.
For each media, enter:
mkdir /tmp/<SAPSID>/<Media_Name> or
mkdir /tmp/<SAPSID>/<Unpack_Directory>
Note
You must avoid blanks or commas in the media path name.
7. Copy the installation media from your Windows drive (for example D:\) or your download directory to the
IFS of your IBM i host by entering the following command:
xcopy D:\<Media> X:\tmp\<SAPSID>\<Media_Name> /E or
xcopy C:\tmp\download\<Unpack_Directory> X:\tmp\<SAPSID>\<Unpack_Directory> /E
Note
You must copy the root directory of the media respectively of the <Unpack_Directory> and all
required subdirectories to the IFS of your IBM i.
8. For each required media, create a subdirectory and copy the required media.
Note
For advanced users only: Instead of copying the complete media you also can copy only dedicated
subdirectories. For IBM i the following directories have to be copied:
○ K_<Version>_<U or N>_OS400_PPC64
○ JAVA*
○ SL_CONTROLLER_<nnn>
8.2
Jload Procedures Using the Java Migration Monitor
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Additional Information
CUSTOMER
95
Related Information
About the Java Migration Monitor [page 96]
Configuration for Using the Java Migration Monitor [page 97]
Starting the Java Migration Monitor [page 99]
Output Files of the Java Migration Monitor [page 101]
Restarting Jload Processes [page 102]
8.2.1 About the Java Migration Monitor
Note
The Java Migration Monitor tool is available only for systems based on SAP NetWeaver 7.0 EHP2 and
higher,
The Java Migration Monitor is a tool that helps you to perform and control the unload and load process during
the system copy procedure.
The Java Migration Monitor performs the following steps:
● Starting the Jload processes to load or unload the data according to the requirements of the user
● Informing the person performing the system copy in case of errors
Note
Some features described in this documentation might be not available in the JMigmon tool if you do not use
the most current version of the tool
Tool
The tool is part of the CORETOOL*.SCA archive and consists of the following:
● User Guide
○ JMigrationMonitor.pdf
○ Located:
/usr/sap/<SAPSID>/SYS/global/sltools
● Scripts
○ jmigmon_export.sh / jmigmon_export.bat
○ jmigmon_import.sh / jmigmon_import.bat
○ Located:
/usr/sap/<SAPSID>/SYS/global/sltools
● jar archive
○ jmigmon.jar
○ Located:
/usr/sap/<SAPSID>/SYS/global/sltools/sharedlib
● Property files
96
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Additional Information
○ export.jmigmon.properties
○ import.jmigmon.properties
○ Located:
/usr/sap/<SAPSID>/SYS/global/sltools
Prerequisites
● The JRE version must be at least 1.4.1.
● JAVA_HOME environment variable must point to the JRE directory.
● The correct directory structure for Jload dump files must exist on both the source and target hosts
8.2.2 Configuration for Using the Java Migration Monitor
Note
The Java Migration Monitor tool is available only for systems based on SAP NetWeaver 7.0 EHP2 and
higher,
The following options can be provided via the property file or via command line. Command line parameters
take precedence over parameters specified in the property file.
Help
The tool displays the available parameters, if you call it with one of the following command line options:
● -help
● -?
Version Information
With the following command line option, the tool displays version information: -version.
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Additional Information
CUSTOMER
97
General Options
Table 25:
Name
Description
Comment
mode
Java Migration Monitor mode: import
Only available as command line option
or export
sid
SAP system ID
SAP system ID
dsn
Data source name
Specifies the data source name and is regis­
tered in the SecureStore; usually jdbc/pool/
<SAPSID>
ssProps
Path to the SecureStore properties
On Windows: local drive or UNC path
file
ssKey
Path to the SecureStore key file
On Windows: local drive or UNC path
exportDirs
Export directories path
Specifies the path or paths for exported data
and triggers the export functionality.
Separator on Windows: “;”
Separator on UNIX, IBM i: “:”
importDirs
Import directories path
Specifies the path or paths for imported data
and triggers the import functionality.
Separator on Windows: “;”
Separator on UNIX, IBM i: “:”
orderBy
Package order
This can be the name or path of the file that
contains package names. If the option value is
omitted the package order is not determined.
jobNum
Number of parallel export jobs
Default is 3.
monitorTimeout
Monitor time-out in seconds
Default is 30 seconds.
disableStatistics
Disables statistics logging
Disables statistics logging for each Jload proc­
ess: Therefore Jload does not collect statistics
data that could later be displayed by the time
analyzer.
Additional Options (all optional)
98
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Additional Information
Table 26:
Name
Description
Comment
orderBy
Package order
This can be the name or path of the file that
contains package names. If the option value is
omitted the package order is not determined.
jobNum
Number of parallel export jobs
Default is 3.
monitorTimeout
Monitor time-out in seconds
Default is 30 seconds.
8.2.3 Starting the Java Migration Monitor
Use
Note
The Java Migration Monitor tool is available only for systems based on SAP NetWeaver 7.0 EHP2 and
higher,
You can start the tool using one of the following:
● The UNIX shell scripts jexport_monitor.sh / jimport_monitor.sh
● As part of the export / import procedure of the software provisioning manager
The application allows you to specify options in the command line or in the export or import property files. The
names of the property files are export.jmigmon.properties and import.jmigmon.properties.
Any options specified in the command line take precedence over the corresponding options in the application
property file. Options are case-sensitive; any options that are not recognized are ignored. To specify an option:
● In the command line, enter -<optionName> <optionValue>
● In the application property file, insert the new line <optionName>=<optionValue>
Prerequisites
Note
We recommend that you create a certain directory and start the tool from there, because the Java
Migration Monitor produces log and trace files in the current working directory.
Before you run the Java Migration Monitor, set the following environment variables:
● SLTOOLS_HOME
Set this variable to the following directory:
UNIX, IBM i: /<sapmnt>/<SAPSID>/global/sltools/sharedlib
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Additional Information
CUSTOMER
99
● SLTOOLS_SECURITY_HOME
Set this variable to the directory, which contains the iaik_jce.jar file.
The default directory is:
UNIX, IBM i: /<sapmnt>/<SAPSID>/global/security/lib/tools
● SLTOOLS_DBDRIVER_HOME
Set this variable to the directory, which contains the database driver.
Example
For MaxDB on Windows: <Drive>:\sapdb\programs\runtime\jar
Procedure
Start the Java Migration Monitor as user <sapsid>adm by executing one of the following from the command
line:
● ./jmigmon_export.sh -<optionName> <optionValue>
● ./jmigmon_import.sh -<optionName> <optionValue>
Example
./jmigmon_export.sh -sid CE3 -dsn jdbc/pool/CE3 -ssProps /sapmnt/global/security/
data/SecStore.properties -ssKey /sapmnt/global/security/data/SecStore.key exportDirs /JPKGCTL
Start the monitor and then close the shell window or command processor. The monitor process runs in the
background. Use the monitor *.log and *.console.log files to check monitor processing state.
Result
What happens during the export or import:
During the import the tool starts a search in the directories specified by the -importDirs parameter for
packages in XML format and puts them into a working queue.
Next it starts a number (specified by the -jobNum parameter) of parallel Jload importing tasks, taking tasks
from the working queue until the queue is empty.
During the export the tool starts a search in the directories specified by the -exportDirs parameter for
packages in XML format and puts them in a working queue.
Then it starts exporting all the packages containing metadata one after another (not in parallel) while removing
them from the queue. The tool then starts a number (specified by the -jobNum parameter) of parallel Jload
export tasks, taking tasks from the working queue until the queue is empty.
100
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Additional Information
Example
export.jmigmon.properties file with export options
# jmigmon mode: import or export mode = export # number of parallel export jobs,
default is 3 jobNum = 1 # <SAPSID> of the system sid = CE3 # name of datasource
registered in system's SecureStore; usually jdbc/pool/<SAPSID> dsn = jdbc/pool/
CE3 # path of the SecureStore properties file ssProps = D:\usr\sap\CE3\SYS\global
\security\data\SecStore.properties # path of the SecureStore key file ssKey = D:
\usr\sap\CE3\SYS\global\security\data\SecStore.key # list of export directories
exportDirs = D:\JPKGCTL # monitor timeout in seconds, default is 30
monitorTimeout = 30
import_monitor.properties file with import options
# jmigmon mode: import or export mode = export # number of parallel export jobs,
default is 3 jobNum = 1 # <SAPSID> of the system sid = CE3 # name of datasource
registered in system's SecureStore; usually jdbc/pool/<SAPSID> dsn = jdbc/pool/
CE3 # path of the SecureStore properties file ssProps = D:\usr\sap\CE3\SYS\global
\security\data\SecStore.properties # path of the SecureStore key file ssKey = D:
\usr\sap\CE3\SYS\global\security\data\SecStore.key # list of import directories
importDirs = D:\export\unpacked\JAVA\JDMP # monitor timeout in seconds, default
is 30 monitorTimeout = 30
8.2.4 Output Files of the Java Migration Monitor
Note
The Java Migration Monitor tool is available only for systems based on SAP NetWeaver 7.0 EHP2 and
higher,
Export
● export.state.properties
● <PACKAGE>.xml.log
Import
● import.state.properties
● <PACKAGE>.xml.log
Both the export and import state files contain package state lines such as the following:
SAPUSER=+
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Additional Information
CUSTOMER
101
Format of lines is <PACKAGE>=<STATE>. The following table shows the possible values for state:
Table 27:
Value
Description
0
Package export/import not yet started.
?
Package export/import in progress.
-
Package export/import finished with errors.
+
Package export/import finished successfully.
8.2.5 Restarting Jload Processes
Use
Note
The Java Migration Monitor tool is available only for systems based on SAP NetWeaver 7.0 EHP2 and
higher,
The state file allows package states to be manually updated to restart failed Jload processes.
Example
If package processing failed and the package state has the value “–”, the state can be set to “0” and
processing of the package will be started again.
Procedure
● To restart package processing, set the package state from “-” to “0”.
● To skip package processing, set the package state from “0” or “-” to “+”.
Caution
This is not recommended because it can cause inconsistent data files or database content.
● If the package is currently being processed (the package state is “?”) then any manual modifications of the
package state are ignored.
102
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Additional Information
8.3
Analysis of the Export and Import Times
You can reduce the runtimes by splitting the packages in question or extracting long-running tables from the
packages.
If your SAP system is based on SAP NetWeaver 7.0 EHP2 and higher, you can use the jmigtime.jar
archive to analyze the runtimes of the individual packages. The tool is part of the CORETOOL*.SCA archive and
consists of the following:
● User Guide
○ JavaTimeAnalyzer.pdf
○ Located:
/usr/sap/<SAPSID>/SYS/global/sltools
● Scripts
○ jexport_time.sh / jexport_time.bat
○ jimport_time.sh / jimport_time.bat
○ jtime_join.sh / jtime_join.bat
○ Located:
/usr/sap/<SAPSID>/SYS/global/sltools
● jar archive
○ jmigtime.jar
○ Located:
/usr/sap/<SAPSID>/SYS/global/sltools/sharedlib
● Property files
○ export.jmigtime.properties
○ import.jmigtime.properties
○ Located:
/usr/sap/<SAPSID>/SYS/global/sltools
8.4
Package and Table Splitting for Java Tables
This section describes the options of the Java Splitter.
The Java Splitter offers the following options:
● Splitting the default packages EXPORT.XML and IMPORT.XML into several smaller and equal sized
packages
● Extracting large tables into packages of their own
● Splitting large tables into several smaller and equal sized packages (table splitting)
The tool provides the corresponding split packages for export and import. Package splitting and table splitting
can be used combined or separately.
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Additional Information
CUSTOMER
103
Tool
The tool is part of the archives J2EEINSTALL.SDA (jar file) and CORETOOL*.SCA (guide, scripts) and consists
of the following files:
● User Guide
○ JSplitterUserGuide.pdf
○ Located:
/sapmnt/<SAPSID>/global/sltools
● Scripts for starting the tool standalone
○ jsplitter.sh, jsplitter.bat
○ Located:
/sapmnt/<SAPSID>/global/sltools
● jar archive
○ sdt_jcopy_jpkgctl.jar
○ Located:
/sapmnt/<SAPSID>/global/sltools/sharedlib
8.5
Configuration for Using the Java Splitter
The following options can be provided via the property file or via command line. Command line parameters
take precedence over parameters specified in the property file.
Note
To get the complete list of supported options run java com.sap.inst.<tool> -help
Help
With the following command line option, the tool displays all parameters available:
-help
104
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Additional Information
General Options
Table 28: General Splitting Options
Option
Description
Comment
-sec
List of SAP system ID and data source
Note
name[,SecureStore property file, Secure­
Store key file][,SecureStore key phrase]
This option is mandatory.
Separator on Windows: “,”
Separator on UNIX, IBM i: “,”
-dataDir
Output data directory
Note
This option is mandatory.
If this option is missing, the split rules are taken from
the command line arguments.
-log
Log file with program output messages and
errors
Default log file name is JPkgClt.console.log.
In addition, a trace file (JPkgCtl.trc) with detailed
process descriptions, errors, and messages is gener­
ated.
-help
Prints help options for the parameters and
non
their usage
Mandatory General Options
The following splitting options are mandatory for both package and table splitting:
sid, dsn, ssProps, ssKey, dataDir
Package Splitting Options
Table 29: Package Splitting Options
Option
Description
Comment
-split
Size of the splitted package with tables
Size can be a number of bytes (for ex­
ample, 1048576, 200M, 8G, and so on)
Additional Mandatory Option for Package Splitting
Splitting option: split
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Additional Information
CUSTOMER
105
Table Splitting Options
Table 30: Table Splitting Options
Option
Description
Comment
-splitrulesfile
Files that contains key fields for each
Syntax:
table
<TABLE_NAME>:<NUMBER_OF_PACK­
îæ−Áï¢íÄQÄÔ?²¿+c‰x}ÖøÉ'
þ_PÍçg]ŘÖ9>ëÅ9ƒł‡]9tñ¬5žÖ˚Œa¤¶˚cºÕ`’L¡?B=Æ˚ø?p4ÜiWÚÞqæþ
TING]>
-tablesplit
Rules for splitting each table
Syntax:
<TABLE_NAME>:<NUMBER_OF_PACK­
îæ−Áï¢íÄQÄÔ?²¿+c‰x}ÖøÉ'
þ_PÍçg]ŘÖ9>ëÅ9ƒł‡]9tñ¬5žÖ˚Œa¤¶˚cºÕ`’L¡?B=Æ˚ø?p4ÜiWÚÞqæþ
TING]>
-checksplitrules
Checks the syntax of the
Syntax:
splitrulesfile. It expects a file as
an argument.
<TABLE_NAME>:<NUMBER_OF_PACK­
îæ−Áï¢íÄQÄÔ?²¿+c‰x}ÖøÉ'
þ_PÍçg]ŘÖ9>ëÅ9ƒł‡]9tñ¬5žÖ˚Œa¤¶˚cºÕ`’L¡?B=Æ˚ø?p4ÜiWÚÞqæþ
TING]>
Example
J2EE_CONFIG:2:
J2EE_CONFIGENTRY:4:CID
BC_COMPVERS:
2:COMPID;HASHNUMBER;COMPONENTTYPE;SUBS
YSTEM
Caution
When configuring table splitting for a table without primary key (such as J2EE_CONFIGENTRY), you have to
provide a value for parameter <COLUMN_TO_BE_USED_FOR_SPLITTING>. If the table to be split has a
primary key (PK), this parameter is optional.
Additional Mandatory Options for Table Splitting
Splitting options: splitrulefile, tablesplit
Example
JSplitter_cmd.properties :
#
# Table Splitting options
#
106
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Additional Information
# Common options
#
# List of SAPSID, data source name[,SecureStore property file, SecureStore key
file][,SecureStore key phrase]
-sec=CE1, jdbc/pool/CE1,/usr/sap/CE1/SYS/global/security/data/
SecStore.properties, /usr/sap/CE1/SYS/global/security/data/SecStore.key
# Size of the split package with tables
-split=200M
# Output data directory
-dataDir=/jsplitter_export_dir
# File that contains key fields for each table with the following syntax:
<TABLE_NAME>:<NUMBER_OF_PACKAGES_FOR_SPLITTING>:<[TABLE_KEY_FOR_SPLITTING]>
-splitrulesfile=/jsplitter_export_dir/splitrulesfile.txt
# Log file with program output messages and errors
-log=
# Check splitrulesfile syntax
-checksplitrules=/jsplitter_export_dir/splitrulesfile.txt
8.6
Starting the Java Splitter
This section describes how to start the Java splitter.
Prerequisites
Before you run the table splitter, set the following environment variables:
● SLTOOLS_HOME
Set this variable to the following directory:
/sapmnt/<SAPSID>/global/sltools/sharedlib
● SLTOOLS_SECURITY_HOME
Set this variable to the directory, which contains the iaik_jce.jar file.
The default directory is:
/sapmnt/<SAPSID>/global/security/lib/tools
● SLTOOLS_DBDRIVER_HOME
Set this variable to the directory, which contains the database driver.
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Additional Information
CUSTOMER
107
Example
For MaxDB on Windows: <Drive>:\sapdb\programs\runtime\jar
Context
Recommendation
We recommend to create a certain directory for splitting and start the tools from there, because the splitter
produces log and trace files in the current working directory.
The application allows you to specify options in the command line or in the application property file. The name
of the property file is JSplitter_cmd.properties.
Any options specified in the command line take precedence over the corresponding options in the application
property file. Options are case-sensitive; any options that are not recognized are ignored.
Note
To check the splitting processing state, use the splitter *.trc and *.console.log files.
Procedure
1. Start the table splitter as user <sapsid>adm using the following shell script:
jsplitter.sh
2. Specify options as required in one of the following ways-optionName optionValue.
○ Command line:
Specify the option in the format –optionName optionValue
○ Property file:
Add an option as a new line in the format optionName=optionValue
Note
If you use an invalid option or you enter -help, the available options for starting the tool are displayed.
Example
Command line
./jsplitter.sh -tablesplit BC_COMPVERS:2 -tablesplit J2EE_CONFIG:4:CID;PATHHASH tablesplit J2EE_CONFIGENTRY:4:CID
108
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Additional Information
8.7
Output Files of the Java Splitter
Here you find an overview of the log, trace, result, and metadata files of the Java splitter.
● JPkgCtl.console.log
Default log file of splitter tool
● JPkgCtl.trc
Trace file with additional and more detailed information
● IMPORT_<PKG_NUMBER>.XML
Resulting xml files for import after package splitting
● EXPORT_<PKG_NUMBER>.XML
Resulting xml files for export after package splitting
● IMPORT_PKG_METADATA.XML
Metadata for tables
● EXPORT_PKG_METADATA.XML
Metadata for tables
● sizes.xml
File with list of the biggest tables with their expected package size in bytes
8.8
Removing the Installation Files of the Installer
You use this procedure to gain disk space after the installation by deleting the installation files of the installer.
On the IBM i host, you should remove the installation directory, the temporary installer files, and the copied
installation media.
Note
You might want to disconnect from the installation share and remove it from the IBM i. However, you need
for J2EE some Java tools with a GUI running on Windows, for example the VisualAdmin and ConfigTool.
These tools have to use a share such as the installation share. For this you might want to keep the share.
Caution
Do not use this procedure until all instances of the SAP system on the IBM i host have been installed.
Prerequisites
● You have completed the SAP system installation.
● The SAP system is up and running.
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Additional Information
CUSTOMER
109
Procedure
Caution
Only delete the log files if you are sure that you do not need them again. Do not delete log files other than
those in the paths given here.
On IBM i:
1. If you want to remove the installer installation directory, enter the following command:
RMVDIR DIR('<Installation_Directory>') SUBTREE(*ALL)
2. To remove temporary SAPINST files, enter the following command:
RMVDIR DIR('/tmp/sapinst_exe*') SUBTREE(*ALL)
Note
If you have chosen one of the three variables: TEMP, TMP, or TMPDIR for your temporary directory in
section Useful Information About the Installer [page 40], you must use this temporary directory instead
of '/tmp'.
3. To remove the installation media, enter the following command:
RMVDIR DIR('/tmp/<SAPSID>') SUBTREE(*ALL)
4. If you have used a dedicated kernel to export your data, you have to delete the dedicated ILE kernel library
manually afterwards using the following command:
DLTLIB LIB(SAP<SOURCE_SAPSID>TMP<n>), n = 0,..,9
On Windows
Note
You might want to disconnect from the ROOTBIN share and remove it from the IBM i. However, you need for
the Java system some Java tools with a GUI running on Windows, for example the ConfigTool. These tools
have to use this share.
To disconnect the share to the IBM i host on the Windows host, enter the following command:
net use <Mapped_Drive>: /DELETE
110
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Additional Information
8.9
Verifying and Adjusting the instanceID of an AS Java
Instance
Using option Adjust instanceID of an AS Java Instance in Software Provisioning Manager (the“ installer” for
short), you can verify the correctness of the instanceID and box number parameters of an existing AS Java
instance, and adjust them if required.
Prerequisites
● The AS Java instance can be started.
● Caution: The installer performs changes in the database which are related to J2EE Engine configuration.
Therefore it is recommended that you back up the J2EE Engine configuration using the ConfigTool. You
can do this by exporting configurations cluster_data,HttpHosts, apps, jms_provider, and
WebContainer using OfflineConfigEditor and configuration of <SAPSID>/Server <xxx>/
Services/Key Storage using the Visual Administrator.
Context
When to Use Option Adjust instanceID of an AS Java Instance
● Software Update Manager (SUM) fails due to incorrect parameter instanceID.
Example
An error like the following occurs during the upgrade of a Java system based on SAP NetWeaver 7.0x:
The detected instance ID IDXXXXX and the one calculated from the box number
IDXXXXX do not match. A possible reason for this could be that you have
changed the box number in the central instance instance.properties file.
● The installer (70SWPM*.SAR) fails due to incorrect parameter instanceID.
Example
An error like the following occurs during system copy, dual-stack split, or system rename of a Java
system based on SAP NetWeaver 7.0x with Software Provisioning Manager:
The source or target cluster ID is not present on the system! The current
(source) cluster ID is XXXXX and the new (target) cluster ID is XXXXX
● You are in doubt about consistency or correctness of the instanceID parameter of an AS Java instance.
Background Information About How Adjust instanceID of an AS Java Instance Works
Software logistics tools (Software Provisioning Manager (the“ installer”), Software Update Manager) verify if
the instanceID parameter corresponds to the box number of an SAP system based on SAP NetWeaver AS
for Java. If the instanceID parameter is not consistent, Software Provisioning Manager fails.
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Additional Information
CUSTOMER
111
The Box number has the format <SAPSID><instance_name><host_name> and is used as a parameter for
the instanceID generation. instanceID is a unique identifier generated for each instance and is stored in
the SAP system database schema when creating a new Java system.
An inconsistency between instanceID and box number is caused by applying an unsupported procedure to
create or maintain the system. Using Software Provisioning Manager for system copy or system rename
(changing the <SAPSID>, host name, or instance name) guarantees consistency.
Adjust instanceID of an AS Java Instance changes the box number and instanceID in the database and
synchronizes the instance.properties file.
More Information
For more information, such as troubleshooting and FAQ, see SAP Note 2259748
.
Procedure
1. Stop the AS Java instance or dual-stack instance and make sure that the database is running.
2. Start the installer and choose option Adjust instanceID of an AS Java Instance from the following path in
the Welcome screen:
Software Life-Cycle Options
Additional Preparation Options
Adjust instanceID of an AS Java
Instance
Caution
If the AS Java instance uses a virtual host name, start the installer with the installer property
SAPINST_USE_HOSTNAME as follows:
./sapinst SAPINST_USE_HOSTNAME=<Virtual_Host_Name>
3. Follow the instructions given on the screens.
Next Steps
Perform the following activities after applying the correction:
1. Calculate the box number using the SAPLOCALHOST profile parameter in lower case.
2. Calculate the correct instanceID using the tool attached to SAP Note 1987497
.
3. Adapt the /usr/sap/<SAPSID>/<instance_name>/j2ee/cluster/bootstrap/
bootstrap.properties file: Assign the instance.prefix property to the correct instanceID.
4. Examine the instance profile - if j2ee/instance_id exists, change it to the new instanceID.
5. Open the OfflineConfigEditor and expand cluster_data
If the perfomerID property exists, change it to the new instanceID.
112
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Additional Information
6. If you have EP: Knowledge Management and Collaboration installed on your system, you have to do the
following adjustments for the Scheduler Service:
Assign scheduler tasks to the new system IDs of the target system. This is required because after applying
the correction, tasks are still assigned to the IDs of the source system.
For more information, see the SAP Library for your release at:
Table 31:
URL
Path
○
SAP NetWeaver 7.0:
○
SAP NetWeaver 7.0 including EHP1:
○
SAP NetWeaver 7.0 including EHP2:
<Including Enhancement Package>
○
SAP NetWeaver 7.0 including EHP3:
Help
http://help.sap.com/nw
SAP NetWeaver 7.0
SAP NetWeaver by Key Capability
Application
Information
Integration: Key Areas
Knowledge Management
Administration Guide
Minimal Configuration for
Knowledge Management
Cluster Only: Assigning
Tasks to Nodes
Related Information
Running the Installer [page 35]
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Additional Information
CUSTOMER
113
Important Disclaimers and Legal Information
Coding Samples
Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system
environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and
completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP
intentionally or by SAP's gross negligence.
Accessibility
The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be
a binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however,
does not apply in cases of willful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations
of SAP.
Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as
"sales person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun
does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.
Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does
not warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any
damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for
transparency (see: http://help.sap.com/disclaimer).
Open Source Software and Third Party Components
Please refer to https://scn.sap.com/docs/DOC-42044 for information respecting open source software components made available by SAP as part of SAP
NetWeaver and any specific conditions that apply to your use of such open source software components. Please refer to https://scn.sap.com/docs/DOC-42045 for
information relating to SAP’s use of third party software with or within SAP NetWeaver.
114
CUSTOMER
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Important Disclaimers and Legal Information
System Copy for SAP Systems Based on the Application Server Java of SAP NetWeaver 7.0
to 7.03 on IBM i
Important Disclaimers and Legal Information
CUSTOMER
115
go.sap.com/registration/
contact.html
© 2017 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any
form or for any purpose without the express permission of SAP SE
or an SAP affiliate company. The information contained herein may
be changed without prior notice.
Some software products marketed by SAP SE and its distributors
contain proprietary software components of other software
vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company
for informational purposes only, without representation or warranty
of any kind, and SAP or its affiliated companies shall not be liable for
errors or omissions with respect to the materials. The only
warranties for SAP or SAP affiliate company products and services
are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein
should be construed as constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks
of SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the
trademarks of their respective companies.
Please see http://www.sap.com/corporate-en/legal/copyright/
index.epx for additional trademark information and notices.
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising