011000358700001412922011e
TRANSCRIPT
Dual-Stack Split GuideDual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIXUsing the Dual-Stack Split Tool 20
Target Audience System administrators Technology consultants
PUBLICDocument version 14 ndash 2012-04-11
Document History
The following table provides an overview of the most important document changes
Version Date Description
14 2012-04-11 Minor changes
13 2012-04-02 Updates for High-availability with Failover Clustering (MSCS) transport routes support of ABAP NUC and removing the Java stack
12 2012-01-20 Minor changes
11 2012-01-18 Patched version
10 2012-01-19 Initial version
254 PUBLIC 2012-04-11
Table of Contents
Chapter 1 Introduction 5
11 SAP Notes for the Dual-Stack Split 6
12 Accessing the SAP Library 7
13 How to Use this Guide 7
Chapter 2 Split Options Covered by this Guide 9
21 Split Option Move Java Database 9
22 Split Option Keep Database 11
Chapter 3 Planning 13
31 Planning Checklist 13
32 User Management 15
Chapter 4 Preparation 17
41 Preparation Checklist 17
42 Performing a Full System Backup 19
Chapter 5 Splitting 21
51 Splitting Checklist 21
52 Running SAPinst 23
Chapter 6 Follow-Up Activities 33
61 Follow-Up Activities Checklist 33
62 Maintaining the Connection to the System Landscape Directory 36
63 Configuring Transport Routes 38
64 Configuring the CTS Deploy Web Service 39
65 Cleaning Up the System Landscape 40
Chapter 7 Additional Information 41
71 Troubleshooting with SAPinst 41
72 Move Java Database Restarting Instances 42
73 Keep Database Restarting Instances 42
2012-04-11 PUBLIC 354
74 Splitting Within a System Landscape 43
75 Removing the Java Stack 46
Chapter A Appendix 47
A1 Online Information from SAP 47
A2 Online Information from IBM 49
454 PUBLIC 2012-04-11
1 Introduction
This document explains how to use the Dual-Stack Split 20 tool to split a dual-stack (ABAP+Java)
system into one ABAP and one Java stack each with its own system ID This tool is part of the installation
tool SAPinst and it mainly uses the Java system copy functionality It is delivered as part of Support
Package 4 of the Software Logistics Toolset (SL Toolset) 10
The dual-stack split procedure is valid for SAP dual-stack systems based on the following SAP NetWeaver
release levels
SAP NetWeaver 70 SP14 or higher
SAP NetWeaver 70 including Enhancement Package 1
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver 70 including Enhancement Package 3
The procedure described in this guide mainly applies to splitting a single SAP dual-stack system For
more information about splitting systems within a system landscape see Splitting Within a System
Landscape [page 43]
Definitions
Dual-Stack System
A dual-stack system is an SAP system that contains installations of both SAP NetWeaver Application
Server ABAP and SAP NetWeaver Application Server Java It has the following characteristics
Common SAP system ID for its ABAP and Java stacks
Common startup framework
Common database (with different schemes for ABAP and Java)
Dual-Stack Split
While splitting-off the Java part of a dual-stack system into a separate system the dual-stack system is
reduced to an ABAP system To do this the Dual-Stack Split Tool runs a system copy and uses the Java
system copy export to reinstall the Java system separately and with a new SAP system ID The ABAP
stack of the former dual-stack system is not affected by this procedure The separated systems can either
use their own databases (see Split Option Move Java Database [page 9]) or both use the existing database
in the ABAP system (see Split Option Keep Database [page 11])
Use Case
As of SAP NetWeaver 70 including Enhancement Package 3 and SAP Business Suite 7i2011 which
is based on SAP NetWeaver 70 including Enhancement Package 3 the installation of SAP dual-
1 Introduction
2012-04-11 PUBLIC 554
stack systems is no longer supported Furthermore as of SAP Business Suite 7i2011 it will no longer
be possible to upgrade an SAP dual-stack system to a higher release
Since the dual-stack split procedure is only available for SAP NetWeaver 70 systems we recommend
that you split your SAP dual-stack system before you perform an upgrade to one of the following
releases
SAP NetWeaver 73
SAP NetWeaver 73 including Enhancement Package 1
If your system is an SAP Business Suite 7i2011 dual-stack system we strongly recommend that
you perform a dual-stack split as it is no longer possible to upgrade to a higher release
For more information see SAP Note 1655335
If you no longer need the Java stack of your dual-stack system you can remove it as described in
Removing the Java Stack [page 46]
Constraints
You need to consider some constraints before you start splitting your SAP dual-stack system
The dual-stack split procedure does not support the splitting of the following
SAP NetWeaver Process Integration systems
SAP Solution Manager systems
The dual-stack split procedure does not implicate the following
Prerequisites Checker
Host agent
Diagnostics agent
Dialog instances
You can ignore sections in the installation documentation that focus on these options
NOTE
If these options are installed on your SAP dual-stack system and you want to use them on
the Java system after the split you need to install them again on the Java system using the
Installation Master DVD that you used to install your dual-stack system
The migration of the operating system or the database platform during the split is not supported
Naming Conventions
SAP system refers to SAP NetWeaver system or SAP system based on SAP NetWeaver
Dual-stack system refers to SAP NetWeaver ABAP+Java system or SAP ABAP+Java system based on SAP
NetWeaver
11 SAP Notes for the Dual-Stack Split
You must read the following SAP Notes before you start the dual-stack split These SAP Notes contain
the most recent information on the dual-stack split as well as corrections to the dual-stack split
1 Introduction
11 SAP Notes for the Dual-Stack Split
654 PUBLIC 2012-04-11
documentation Make sure that you have the most up-to-date version of each SAP Note which you
can find at httpservicesapcomnotes
SAP Notes for the Dual-Stack Split
SAP Note Number Title Description
1685432 Dual-Stack Split 20 SP1 for Systems Based on SAP NetWeaver
Problems discovered after the publication of the dual-stack split guide
1655335 Use Cases for Splitting Dual-Stack Systems mdash
12 Accessing the SAP Library
The references to the SAP NetWeaver Library documentation in this dual-stack split guide always
refer to the following on SAP Help Portal
SAP NetWeaver 70
httphelpsapcomnw70 Application Help SAP Library English SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 1
httphelpsapcomnw701 Application Help SAP Library English SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 2
httphelpsapcomnw702 Application Help SAP Library English SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 3
httphelpsapcomnw703 Application Help SAP Library English SAP NetWeaver
13 How to Use this Guide
This documentation comprises the description of the dual-stack split procedure and dual-stack-split-
specific steps For general or installation-specific information see the installation documentation
relevant for your release which you can find at httpservicesapcominstguides
Procedure
1 You decide on the split option that you want to use The following split options are available for
central distributed and high-availability systems
ldquoMove Java Databaserdquo (non-MCOD)
ldquoKeep Databaserdquo (MCOD)
For more information see Split Options Covered by this Guide [page 9]
2 You follow the list of steps at the beginning of each phase
Planning [page 13]
Preparation [page 17]
Splitting [page 21]
Follow-up Activities [page 33]
1 Introduction
12 Accessing the SAP Library
2012-04-11 PUBLIC 754
This page is left blank for documents that are printed on both sides
2 Split Options Covered by this Guide
This section shows the split options covered by this guide You have to decide which option you want
to use because the steps you have to perform vary according to the split option that you choose
Move Java Database [page 9]
Keep Database [page 11]
21 Split Option Move Java Database
The split option ldquoMove Java Databaserdquo offers the possibility to split a dual-stack system into one ABAP
system and one Java system each with its own database (non-MCOD)
Move Java Database for Central Systems
When you choose the ldquoMove Java Databaserdquo option for a central system SAPinst exports the Java stack
of the dual-stack system and uses this export to reinstall all main instances on a single host This equates
to an installation of a central system
These are the following instances
Central instance (CI)
Central services instance for Java (SCS)
Database instance (DB)
NOTE
If required you can install the central instance and the central services instance on the ABAP
system host again
Once the installation has finished and after the System Landscape Directory has been reconfigured
SAPinst removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
2012-04-11 PUBLIC 954
Figure 1 Split Option Move Java Database for Central Systems
Move Java Database for Distributed System
When you choose the ldquoMove Java Databaserdquo option for a distributed system SAPinst exports the Java
stack of the dual-stack system and uses this export to reinstall the main instances on several hosts
Every instance can run on a separate host This equates to an installation of a distributed system
These are the following instances
Central instance (CI)
Central services instance for Java (SCS)
Database instance (DB)
NOTE
If required you can reinstall the central instance and the central services instance on the ABAP
system hosts
After the installation has finished and the System Landscape Directory has been reconfigured SAPinst
removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
1054 PUBLIC 2012-04-11
Figure 2 Split Option Move Java Database for Distributed System
22 Split Option Keep Database
The split option ldquoKeep Databaserdquo offers the possibility for the Java system to reuse the existing database
of the dual-stack system using MCOD (multiple components ndash one database)
Keep Database for Central and Distributed Systems
When you choose the ldquoKeep Databaserdquo option SAPinst exports the Java file system on the dual-stack
system It uses this export to reinstall a central services instance (SCS) and a central instance (CI) for
Java They can be installed on one host on different hosts or on the source system hosts again
Additionally SAPinst adapts the Java schema of the database of the dual-stack system to the target Java
system
After the installation has finished and the System Landscape Directory has been reconfigured SAPinst
removes all Java parts from the dual-stack system except the Java database schema
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-04-11 PUBLIC 1154
Figure 3 Split Option Keep Database for Central Systems
Figure 4 Split Option Keep Database for Distributed Systems
2 Split Options Covered by this Guide
22 Split Option Keep Database
1254 PUBLIC 2012-04-11
3 Planning
31 Planning Checklist
This section includes the planning steps that you have to perform when you want to install the new
Java system on one or more hosts Perform the planning steps according to the split option and your
system variant
NOTE
Most of the required planning steps listed in this section are not described in this documentation
You can find the detailed description in the SAP NetWeaver Application Server Java installation
documentation relevant for your release at httpservicesapcominstguides
Prerequisites
You have decided on your split option [page 9]
Split Option ldquoMove Java Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
1 You check the hardware and software requirements for the Java installation host
For more information see Hardware and Software Requirements in the installation documentation of
your release
2 You read about user management [page 15]
3 You identify basic SAP system installation parameters
For more information see Basic SAP System Parameters in the installation documentation of your
release
Be aware of the following dual-stack-split-specific deviations
SAP System Parameters
User management
We do not recommend that you make modifications in the user management settings
For more information see User Management [page 15]
System Landscape Directory (SLD)
You can ignore SLD parameters
Only valid for Oracle |
SAP System Database Parameters Java database schema
We recommend that you choose a schema ID that is different from your SAP system ID
It might cause problems when you copy a system if ltSCHEMA_IDgt is the same as ltSAPSIDgt and
the database-specific method used for the copy does not allow you to rename the database
3 Planning
31 Planning Checklist
2012-04-11 PUBLIC 1354
schemes In certain situations you might create a system copy with a new ltSAPSIDgt but where
the database schema has the old ltSAPSIDgt This is not a technical problem but might be
confusing to the system administratorEnd of Oracle |
4 Only valid for MaxDB |
You plan your system configuration
For more information see System Configuration in the installation documentation of your releaseEnd of MaxDB |
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
You plan the setup of your database carefully
For more information see Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
7 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 43]
8 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
9 Only valid for IBM DB2 for zOS |
If you want to execute a Software Life-Cycle Option with SAPinst in an SAP system with thick client
connectivity see Special Considerations Regarding Connectivity for Software Life-Cycle Options in the installation
documentation of your releaseEnd of IBM DB2 for zOS |
10 Only valid for IBM DB2 for i5OS |
Optionally you decide whether you want to install multiple SAP systems on a single host
For more information see Multiple SAP Systems on a Single Host in the installation documentation of
your releaseEnd of IBM DB2 for i5OS |
11 You can continue with Preparation [page 17]
Split Option ldquoKeep Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
1 You check the hardware and software requirements for the Java installation host
For more information see Hardware and Software Requirements in the installation documentation of
your release
2 You read about user management [page 15]
3 You identify basic SAP system installation parameters
For more information see Basic SAP System Parameters in the installation documentation of your
release
3 Planning
31 Planning Checklist
1454 PUBLIC 2012-04-11
Be aware of the following dual-stack-split-specific deviation for SAP System Parameters
User management
We do not recommend that you make modifications in the user management settings For
more information see User Management [page 15]
System Landscape Directory (SLD)
You can ignore SLD parameters
4 Only valid for IBM DB2 for zOSMaxDB |
You plan your system configuration
For more information see System Configuration in the installation documentation of your releaseEnd of IBM DB2 for zOSMaxDB |
5 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
6 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 43]
7 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
8 Only valid for IBM DB2 for zOS |
If you want to execute a Software Life-Cycle Option with SAPinst in an SAP system with thick client
connectivity see Special Considerations Regarding Connectivity for Software Life-Cycle Options in the installation
documentation of your releaseEnd of IBM DB2 for zOS |
9 Only valid for IBM DB2 for i5OS |
Optionally you decide whether you want to install multiple SAP systems on a single host
For more information see Multiple SAP Systems on a Single Host in the installation documentation of
your releaseEnd of IBM DB2 for i5OS |
10 You can continue with Preparation [page 17]
32 User Management
The dual-stack split procedure does not change the user management and you cannot choose which
kind of user management you want to use for the target AS Java system That is the separated Java
system and the ABAP system both use the user management of the former dual-stack system The
following is possible
If the dual-stack system uses AS ABAP as data source for the User Management Engine (UME)
after the split the separated Java stack will also use the ABAP UME
If the dual-stack system uses an LDAP directory as source for user data this is also valid for the Java
stack
3 Planning
32 User Management
2012-04-11 PUBLIC 1554
In both cases manual configuration is not required
We do not recommend that you make modifications to the user management settings
For more information see SAP Note 718383
3 Planning
32 User Management
1654 PUBLIC 2012-04-11
4 Preparation
41 Preparation Checklist
This section includes the preparation steps that you have to perform when you want to install the new
Java system on one or more hosts
NOTE
Most of the required preparation steps listed in this section are not described in this
documentation You can find the detailed description in the SAP NetWeaver Application Server
Java installation documentation relevant for your release at httpservicesapcom
instguides
1 Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
You make sure that the required operating system users and groups are created
To create the groups and users automatically run the Dual-Stack Split Tool on the host where
the SAP Java system is to be installed and choose Dual-Stack Split Operating System Users and
Groups
For more information see Creating Operating System Users and Groups in the installation documentation
of your releaseEnd of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
2 You set up file systems and make sure that the required disk space is available for the directories
to be created during the installation
For more information see Setting Up File Systems for a High-Availability System in the installation
documentation of your release
3 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
4 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
If you want to install a high-availability system you perform switchover preparations
For more information see Performing Switchover Preparations for High-Availability in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
5 If you want to share the transport directory trans from another system you export this directory
to your installation hosts
For more information see Exporting and Mounting the Global Transport Directory in the installation
documentation of your release
4 Preparation
41 Preparation Checklist
2012-04-11 PUBLIC 1754
6 You install the Java Development Kit This step is not required if you have installed the SAP JVM
4 on your source system
For more information see Installing the Java Development Kit in the installation documentation of your
release
7 You make sure that the required installation media are available on each host
You can download the Dual-Stack Split Tool at httpservicesapcomsltoolset
Software Logistics Toolset 10 Dual-Stack Split
You can download the Java stack and database installation media from SAP Service
Marketplace as described in Preparing the Installation Media in the installation documentation of
your release
NOTE
The release level required for the installation corresponds to the release level of your dual-
stack system
The following table shows the required installation media for the dual-stack split
SAP Instance Installation Required Media
Central services instance central instance
Dual-Stack Split Tool Java DVD RDBMS Client DVD
Move Java Database only Database instance
Dual-Stack Split Tool Java DVD Only valid for MS SQL ServerOracle |
RDBMS DVDEnd of MS SQL ServerOracle |
Only valid for MS SQL ServerOracle |
RDBMS Patch DVD (if available)End of MS SQL ServerOracle |
8 Only valid for HA (MSCS) |
To install a high-availability system with Microsoft Cluster Service (MSCS) you also perform the
MSCS-specific preparation tasks as described in the installation documentation of your releaseEnd of HA (MSCS) |
9 Only valid for HA (MSCS) |
If you choose the split option ldquoKeep Databaserdquo with the scenario ldquoKeep SCS on the Source Cluster
Systemrdquo you perform the following steps
You provide additional disk storage on the target cluster system
For more information see Distribution of SAP System Components to Disks for MSCS Directories in an
MSCS Configuration and IP Addresses in an MSCS Configuration in the installation documentation of
your release
You provide an additional IP address and an additional virtual host name for the Java system
For more information see Mapping Host Names to IP Addresses for MSCS in the installation
documentation of your releaseEnd of HA (MSCS) |
4 Preparation
41 Preparation Checklist
1854 PUBLIC 2012-04-11
10 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 19] of
the dual-stack system
11 You can continue with Splitting [page 21]
42 Performing a Full System Backup
If you decided to use the split option ldquoKeep Databaserdquo you must perform a full system backup of the
dual-stack system or at least a backup of the Java database schema before you start the split procedure
If you decided to use the split option ldquoMove Java Databaserdquo you do not need to perform a backup before
you start the split procedure
For more information about backing up your database see the database-specific backup and recovery
documentation in the SAP Library [page 7] at
SAP MaxDB
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for SAP
MaxDB
Oracle
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Oracle
IBM DB2 for i5OS
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 UDB for iSeries
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for i
4 Preparation
42 Performing a Full System Backup
2012-04-11 PUBLIC 1954
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
i
IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX
and Windows
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
Linux UNIX and Windows
IBM DB2 for zOS
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 UDB for zOS
SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for DB2 for z
OS
Microsoft SQL Server
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Microsoft SQL
Server
4 Preparation
42 Performing a Full System Backup
2054 PUBLIC 2012-04-11
5 Splitting
51 Splitting Checklist
This section includes the splitting steps that you have to perform for the following split options
ldquoMove Java Databaserdquo
ldquoKeep Databaserdquo
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Only valid for Oracle |
You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 You export the Java stack using SAPinst [page 23]
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
4 You restart the source system
5 You run SAPinst [page 23] to install a Java only system using the export from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2012-04-11 PUBLIC 2154
Distributed System
1 Only valid for Oracle |
On the database instance host of the dual-stack system you install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes on the database instance host
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 On the database instance host of the dual-stack system you run SAPinst [page 23] to export the
Java database schema
4 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the Java
parts of the file system of the central instance
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
5 You restart the source system
6 You run SAPinst [page 23] to install a central services instance for the Java target system
7 You run SAPinst [page 23] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
9 You continue with Follow-Up Activities [page 33]
Keep Database
1 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the
file system of the central instance
5 Splitting
51 Splitting Checklist
2254 PUBLIC 2012-04-11
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you wont use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
2 You restart the source system
3 You run SAPinst [page 23] to install a central services instance for the Java target system
4 On the database instance host of the dual-stack system you run SAPinst [page 23] to adapt the
database for the Java target system
NOTE
Make sure that you enter the profile directory of the Java target system in the SAP System gt
General Parameters screen
5 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
52 Running SAPinst
This section describes how to run the installation tool SAPinst SAPinst includes a GUI client and a GUI
server which both use Java
The procedure describes an installation where SAPinst GUI client and GUI server are running on the
same host In the following GUI client and GUI server are addressed as ldquoSAPinst GUIrdquo
If you need to see the installation on a remote display we recommend that you perform a remote
installation with SAPinst where the SAPinst GUI is running on a separate host from SAPinst For more
information see Performing a Remote Installation with SAPinst in the installation documentation of your
release
Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote
access to SAPinst GUI on Windows workstations For more information see SAP Note 1170809
Useful Information About SAPinst
When you start SAPinst it automatically starts the SAPinst GUI
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2354
SAPinst creates the installation directory sapinst_instdir directly below the temporary directory
SAPinst 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 SAPinst
creates the installation directory sapinst_instdir directly below the tmp directory by default
If you want SAPinst to create the installation directory sapinst_instdir in another directory set
the environment variable TEMP to this directory before you start SAPinst
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
Only valid for IBM DB2 for i5OS |
NOTE
When you leave your Qp2Term session all changes of the environment variables done by the
command export are reverted
End of IBM DB2 for i5OS |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
SAPinst creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt
SAPinst extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is located
in the environment variables TEMP TMP or TMPDIR These files are deleted after SAPinst has stopped
running
The temporary directory sapinst_exexxxxxxxxxx sometimes remains undeleted You can safely
delete it
The temporary directory also contains the log file dev_selfexout from the extraction process
which might be useful if an error occurs
CAUTION
If SAPinst cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default ports 21200 21212 and 4239 are used for communication
between SAPinst GUI server GUI and HTTP server as follows
SAPinst uses port 21200 to communicate with the GUI server
The GUI server uses port 21212 to communicate with the GUI client
5 Splitting
52 Running SAPinst
2454 PUBLIC 2012-04-11
4239 is the port of the HTTP server which is part of the GUI server
If the ports for SAPinst and the GUI server are already in use SAPinst automatically searches for
free port numbers If the search fails SAPinst exits
In this case or if you want SAPinst to use specific ports you can assign them by executing the
sapinst executable with the following command line parameters
SAPINST_DIALOG_PORT=ltport_number_sapinst_to_gui_servergt
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
GUISERVER_HTTP_PORT=ltport_number_http_servergt
To see a list of all available SAPinst properties start SAPinst as described above with command line
parameter -p
sapinst -p
If you need to run SAPinst in accessibility mode proceed as described in Running SAPinst in Accessibility
Mode in the installation documentation of your release
If required you can stop SAPinst by choosing SAPinst Cancel in the SAPinst GUI menu
Prerequisites
We recommend that you use the csh shell for the installation with SAPinst If you want to use
another shell make sure that you have first read SAP Note 202227
SAPinst uses csh scripts during the installation to obtain the environment for user ltsapsidgtadm
This is also true if user ltsapsidgtadm already exists from an earlier SAP system installation and the
shell of this user is not csh Before you start SAPinst execute the following command as user
ltsapsidgtadm to make sure that the csh scripts are up-to-date
bincsh -c source lthome directory of ltsapsidgtadmgtcshrcenv
Make sure that you have specified the most important SAP system parameters as described in Basic
SAP System Installation Parameters in the installation documentation of your release before you start
SAPinst
Only valid for IBM DB2 for zOS |
Check that your installation hosts meet the requirements for the installation options that you
want to installEnd of IBM DB2 for zOS |
Only valid for Non-Standalone Engines and Clients |
If you want to perform a distributed or a high-availability installation make sure that you have
exported and mounted global directories For more information see Exporting and Mounting Global
Directories in the installation documentation of your releaseEnd of Non-Standalone Engines and Clients |
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you have carefully planned your database layout in particular the tablespace layout
as described in Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2554
Only valid for AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for Solaris |
Solaris SPARC onlyEnd of Solaris |
If you want to set up DB2s high-availability cluster solution SA MP make sure that you have read
the document IBM DB2 High Availability Solution IBM Tivoli System Automation for Multiplatforms at
httpservicesapcominstguidesnw70 Installation Installation ndash SAP NetWeaver SystemsEnd of AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for zOS |
First make sure that you have installed DB2 for zOS For information on that installation see
SAP DBA Guide DB2 for zOS DB2 Setup especially the section Stored Procedures EnablementEnd of IBM DB2 for zOS |
Check the value of the environment variable TEMP TMP or TMPDIR
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
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 ndash for example by using a crontab entry
Make sure that you have at least 60 MB of free space in the installation directory for each
installation option In addition you need 200 MB free space for the SAPinst executables If you
cannot provide 200 MB free space in the temporary directory you can set one of the
environment variables TEMP TMP or TMPDIR to another directory with 200 MB free space for
the SAPinst executables
Make sure that the temporary directory has the permissions 777
Only valid for IBM DB2 for zOS |
Make sure that your database is up and runningEnd of IBM DB2 for zOS |
Make sure that your DISPLAY environment variable is set to lthost_namegt00 where
lthost_namegt is the host on which you want to display the GUI
Shell Used Command
Bourne shell (sh) DISPLAY=lthost_namegt00
export DISPLAY
C shell (csh) setenv DISPLAY lthost_namegt00
Korn shell (ksh) export DISPLAY=lthost_namegt00
Make sure that umask is set to 022 for user root
As user root enter the following command umask 022
Check the following values for user root
5 Splitting
52 Running SAPinst
2654 PUBLIC 2012-04-11
In csh execute limit
Output Properties
cputime unlimited
filesize unlimited
datasize unlimited
stacksize 8192 KB
coredumpsize unlimited
descriptors 8192
memorysize unlimited
In sh or ksh execute ulimit -a
Output Properties
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192
coredump(blocks) unlimited
nofiles(descriptors) 8192
memory(KBytes) unlimited
If your parameter settings differ from those above change these values accordingly
EXAMPLE
If you have to change the value for descriptors to 8192 proceed as follows
In csh execute
limit descriptors 8192
In sh or ksh execute
ulimit -n 8192
Before you start SAPinst read SAP Note 1697164 for more information about which user to choose
for running the SAPinst SDT GUI server
Procedure
1 Log on to the installation host as user root
CAUTION
Do not use an existing ltsapsidgtadm user
Only valid for Non-Standalone Engines and Clients |
CAUTION
Make sure that the root user has not set any environment variables for a different SAP system
or database
End of Non-Standalone Engines and Clients |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2754
2 Make the Dual-Stack Split Tool available on the installation host Make sure that it is available
locally We do not recommend that you use Network File System (NFS) because reading from
media mounted with NFS might fail
For more information see Preparation Checklist [page 17] and Preparing the Installation Media in the
installation documentation of your release
3 Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
Only valid for Non-Standalone Engines and Clients |
Change to the directory with the sapinst executable for your operating system by entering the
following command cd ltMountpoint of Installation Master mediumgtDATA_UNITS
ltproductgt_IM_ltOSgtEnd of Non-Standalone Engines and Clients |
End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
4 Start SAPinst by executing the following command sapinst
NOTE
If you want to use a virtual host name start SAPinst with the SAPinst property
SAPINST_USE_HOSTNAME as follows
Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
sapinst SAPINST_USE_HOSTNAME=ltvirtual host namegt
End of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
5 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
In addition if you want to use the split option ldquoMove Java Databaserdquo choose ltYour System
Variantgt
Perform the export and installation steps exactly in the order in which they appear
6 Only valid for Non-Standalone Engines and Clients |
Choose NextEnd of Non-Standalone Engines and Clients |
7 Follow the instructions in the SAPinst input screens and enter the required parameters
NOTE
If SAPinst asks for the Java DVD make sure that you provide a Java DVD with the same
release level as your dual-stack system
For more information about the input parameters position the cursor on the parameter
and press F1
After you have entered all requested input parameters SAPinst displays the Parameter Summary screen
This screen shows both the parameters that you entered and those that SAPinst set by default If
required you can revise the parameters before starting the split procedure
5 Splitting
52 Running SAPinst
2854 PUBLIC 2012-04-11
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you check the following parameters depending on the installation type that you
have chosenEnd of IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for Linux and UNIX and Windows |
If you are performing a typical installation SAPinst creates four sapdata directories by
default If you require more or fewer sapdata directories depending on the storage devices
you are using you must change this parameter before you start the installation By selecting
this parameter on the Summary screen and choosing Revise SAPinst returns to the IBM DB2 for
Linux UNIX and Windows ndashgt Sapdata Directories screen
On this screen you can also decide if you want SAPinst to create the regular table and index
tablespaces with DB2s automatic storage management enabled By default the option for
automatic storage management is preselected
NOTE
As of DB2 V91 and higher the database and the SYSCATSPACE tablespace are always created
with automatic storage management enabled even if you deselect this option on the
dialog IBM DB2 for Linux UNIX and Windows gt Sapdata Directories
For more information about DB2s automatic storage management see section DB2
Tablespaces in the installation documentation of your SAP product
If you are performing a custom installation you set these parameters during the Define
Parameters phase of SAPinst
NOTE
If the tablespace layout used by SAPinst does not meet your requirements you can create
the tablespaces manually by deselecting the option Create Tablespaces with SAPinst on the
IBM DB2 for Linux and UNIX and Windows Sapdata Directories screen
During the installation phase SAPinst then displays the following message
You must create the tablespaces now To do so use the
createTablespacessql script that is located in your installation
directory
To continue the installation choose OK Alternatively you can cancel
SAPinst here and restart it again
SAPinst does not check the page size of tablespaces that have either been created manually
or that already exist If you create the tablespaces manually you must make sure that
you use a page size of 16 KBEnd of IBM DB2 for Linux and UNIX and Windows |
8 To start the dual-stack split choose Start
SAPinst starts and displays the progress of the split procedure
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2954
When the split option has finished successfully SAPinst displays the message Execution of
ltOption_Namegt has completed
Only valid for Oracle |
NOTE
When installing the Oracle database instance SAPinst stops the installation and prompts
you to install the Oracle database software For more information see Installing the Oracle
Database Software in the installation documentation of your release
After you have finished the installation of the Oracle database you continue the database
instance installation by choosing OK in the GUI of the database instance installation
Check SAP Note 1431800 for technical information about Oracle Release 112 in SAP
environments
End of Oracle |
Only valid for Enterprise Portal (EP) |
NOTE
During the final restart of Application Server Java performed by SAPinst the portal starts the
processing and uploading of the new portal archives It takes approximately 15 to 90 minutes
before the deployment is completed and the portal is launched
Do not stop SAPinst or Application Server Java during this phase
End of Enterprise Portal (EP) |
9 If required delete directories with the name sapinst_exexxxxxxxxxx after SAPinst has finished
Sometimes these remain in the temporary directory
NOTE
If there are errors with the SAPinst extraction process you can find the log file
dev_selfexout in the temporary directory
Only valid for Non-Standalone Engines and Clients |
RECOMMENDATION
Keep all installation 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 installation 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 installation directories on installation hosts but make sure
that you delete them after saving them separately
End of Non-Standalone Engines and Clients |
10 We recommend that you delete the directory ltuser_homegtsdtgui
11 Only valid for IBM DB2 for Linux and UNIX and Windows |
If not already done install the DB2 license
5 Splitting
52 Running SAPinst
3054 PUBLIC 2012-04-11
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
End of IBM DB2 for Linux and UNIX and Windows |
12 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 3154
This page is left blank for documents that are printed on both sides
6 Follow-Up Activities
61 Follow-Up Activities Checklist
This section includes the follow-up activities that you have to perform for the following split options
ldquoMove Java Databaserdquo for a central system
ldquoMove Java Databaserdquo for a distributed system or a high-availability system
ldquoKeep Databaserdquo for a central distributed or high-availability system
NOTE
Some of the follow-up activities listed in this section are not described in this documentation You
can find the detailed description in the SAP NetWeaver Application Server Java system copy
documentation relevant for your release at
httpservicesapcominstguides
Move Java Database
Central System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3354
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
7 We recommend that you perform regression testing
8 On the source system you run SAPinst [page 23] to remove the Java parts in the file system and in
the database
9 On the source system you call transaction RZ10 to reimport the profiles from the file system
10 In the Transport Management System (TMS) you configure the transport routes [page 38]
11 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
12 You clean up the system landscape data [page 40]
Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3454 PUBLIC 2012-04-11
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the database host of the source system you run SAPinst [page 23] to remove the Java database
schema
12 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
13 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
14 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
15 You clean up the system landscape data [page 40]
Keep Database
Central Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3554
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
12 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
13 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
14 You clean up the system landscape data [page 40]
62 Maintaining the Connection to the System Landscape Directory
After installing the Java system you need to reconfigure the connection between the System Landscape
Directory (SLD) the source system and the target system The steps required differ depending on
whether you use a local or a central SLD To maintain the connection to the SLD you can either run
the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split or perform the required steps manually as described below
NOTE
This step is only required if the connection to the SLD was established on the source system before
the split
Prerequisites
If you want to use the configuration wizard you need an SAP NetWeaver Java system 70 Support
Package 14 or higher in your landscape
SLDAPIUSER credentials are available in the ABAP system
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3654 PUBLIC 2012-04-11
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
Document History
The following table provides an overview of the most important document changes
Version Date Description
14 2012-04-11 Minor changes
13 2012-04-02 Updates for High-availability with Failover Clustering (MSCS) transport routes support of ABAP NUC and removing the Java stack
12 2012-01-20 Minor changes
11 2012-01-18 Patched version
10 2012-01-19 Initial version
254 PUBLIC 2012-04-11
Table of Contents
Chapter 1 Introduction 5
11 SAP Notes for the Dual-Stack Split 6
12 Accessing the SAP Library 7
13 How to Use this Guide 7
Chapter 2 Split Options Covered by this Guide 9
21 Split Option Move Java Database 9
22 Split Option Keep Database 11
Chapter 3 Planning 13
31 Planning Checklist 13
32 User Management 15
Chapter 4 Preparation 17
41 Preparation Checklist 17
42 Performing a Full System Backup 19
Chapter 5 Splitting 21
51 Splitting Checklist 21
52 Running SAPinst 23
Chapter 6 Follow-Up Activities 33
61 Follow-Up Activities Checklist 33
62 Maintaining the Connection to the System Landscape Directory 36
63 Configuring Transport Routes 38
64 Configuring the CTS Deploy Web Service 39
65 Cleaning Up the System Landscape 40
Chapter 7 Additional Information 41
71 Troubleshooting with SAPinst 41
72 Move Java Database Restarting Instances 42
73 Keep Database Restarting Instances 42
2012-04-11 PUBLIC 354
74 Splitting Within a System Landscape 43
75 Removing the Java Stack 46
Chapter A Appendix 47
A1 Online Information from SAP 47
A2 Online Information from IBM 49
454 PUBLIC 2012-04-11
1 Introduction
This document explains how to use the Dual-Stack Split 20 tool to split a dual-stack (ABAP+Java)
system into one ABAP and one Java stack each with its own system ID This tool is part of the installation
tool SAPinst and it mainly uses the Java system copy functionality It is delivered as part of Support
Package 4 of the Software Logistics Toolset (SL Toolset) 10
The dual-stack split procedure is valid for SAP dual-stack systems based on the following SAP NetWeaver
release levels
SAP NetWeaver 70 SP14 or higher
SAP NetWeaver 70 including Enhancement Package 1
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver 70 including Enhancement Package 3
The procedure described in this guide mainly applies to splitting a single SAP dual-stack system For
more information about splitting systems within a system landscape see Splitting Within a System
Landscape [page 43]
Definitions
Dual-Stack System
A dual-stack system is an SAP system that contains installations of both SAP NetWeaver Application
Server ABAP and SAP NetWeaver Application Server Java It has the following characteristics
Common SAP system ID for its ABAP and Java stacks
Common startup framework
Common database (with different schemes for ABAP and Java)
Dual-Stack Split
While splitting-off the Java part of a dual-stack system into a separate system the dual-stack system is
reduced to an ABAP system To do this the Dual-Stack Split Tool runs a system copy and uses the Java
system copy export to reinstall the Java system separately and with a new SAP system ID The ABAP
stack of the former dual-stack system is not affected by this procedure The separated systems can either
use their own databases (see Split Option Move Java Database [page 9]) or both use the existing database
in the ABAP system (see Split Option Keep Database [page 11])
Use Case
As of SAP NetWeaver 70 including Enhancement Package 3 and SAP Business Suite 7i2011 which
is based on SAP NetWeaver 70 including Enhancement Package 3 the installation of SAP dual-
1 Introduction
2012-04-11 PUBLIC 554
stack systems is no longer supported Furthermore as of SAP Business Suite 7i2011 it will no longer
be possible to upgrade an SAP dual-stack system to a higher release
Since the dual-stack split procedure is only available for SAP NetWeaver 70 systems we recommend
that you split your SAP dual-stack system before you perform an upgrade to one of the following
releases
SAP NetWeaver 73
SAP NetWeaver 73 including Enhancement Package 1
If your system is an SAP Business Suite 7i2011 dual-stack system we strongly recommend that
you perform a dual-stack split as it is no longer possible to upgrade to a higher release
For more information see SAP Note 1655335
If you no longer need the Java stack of your dual-stack system you can remove it as described in
Removing the Java Stack [page 46]
Constraints
You need to consider some constraints before you start splitting your SAP dual-stack system
The dual-stack split procedure does not support the splitting of the following
SAP NetWeaver Process Integration systems
SAP Solution Manager systems
The dual-stack split procedure does not implicate the following
Prerequisites Checker
Host agent
Diagnostics agent
Dialog instances
You can ignore sections in the installation documentation that focus on these options
NOTE
If these options are installed on your SAP dual-stack system and you want to use them on
the Java system after the split you need to install them again on the Java system using the
Installation Master DVD that you used to install your dual-stack system
The migration of the operating system or the database platform during the split is not supported
Naming Conventions
SAP system refers to SAP NetWeaver system or SAP system based on SAP NetWeaver
Dual-stack system refers to SAP NetWeaver ABAP+Java system or SAP ABAP+Java system based on SAP
NetWeaver
11 SAP Notes for the Dual-Stack Split
You must read the following SAP Notes before you start the dual-stack split These SAP Notes contain
the most recent information on the dual-stack split as well as corrections to the dual-stack split
1 Introduction
11 SAP Notes for the Dual-Stack Split
654 PUBLIC 2012-04-11
documentation Make sure that you have the most up-to-date version of each SAP Note which you
can find at httpservicesapcomnotes
SAP Notes for the Dual-Stack Split
SAP Note Number Title Description
1685432 Dual-Stack Split 20 SP1 for Systems Based on SAP NetWeaver
Problems discovered after the publication of the dual-stack split guide
1655335 Use Cases for Splitting Dual-Stack Systems mdash
12 Accessing the SAP Library
The references to the SAP NetWeaver Library documentation in this dual-stack split guide always
refer to the following on SAP Help Portal
SAP NetWeaver 70
httphelpsapcomnw70 Application Help SAP Library English SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 1
httphelpsapcomnw701 Application Help SAP Library English SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 2
httphelpsapcomnw702 Application Help SAP Library English SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 3
httphelpsapcomnw703 Application Help SAP Library English SAP NetWeaver
13 How to Use this Guide
This documentation comprises the description of the dual-stack split procedure and dual-stack-split-
specific steps For general or installation-specific information see the installation documentation
relevant for your release which you can find at httpservicesapcominstguides
Procedure
1 You decide on the split option that you want to use The following split options are available for
central distributed and high-availability systems
ldquoMove Java Databaserdquo (non-MCOD)
ldquoKeep Databaserdquo (MCOD)
For more information see Split Options Covered by this Guide [page 9]
2 You follow the list of steps at the beginning of each phase
Planning [page 13]
Preparation [page 17]
Splitting [page 21]
Follow-up Activities [page 33]
1 Introduction
12 Accessing the SAP Library
2012-04-11 PUBLIC 754
This page is left blank for documents that are printed on both sides
2 Split Options Covered by this Guide
This section shows the split options covered by this guide You have to decide which option you want
to use because the steps you have to perform vary according to the split option that you choose
Move Java Database [page 9]
Keep Database [page 11]
21 Split Option Move Java Database
The split option ldquoMove Java Databaserdquo offers the possibility to split a dual-stack system into one ABAP
system and one Java system each with its own database (non-MCOD)
Move Java Database for Central Systems
When you choose the ldquoMove Java Databaserdquo option for a central system SAPinst exports the Java stack
of the dual-stack system and uses this export to reinstall all main instances on a single host This equates
to an installation of a central system
These are the following instances
Central instance (CI)
Central services instance for Java (SCS)
Database instance (DB)
NOTE
If required you can install the central instance and the central services instance on the ABAP
system host again
Once the installation has finished and after the System Landscape Directory has been reconfigured
SAPinst removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
2012-04-11 PUBLIC 954
Figure 1 Split Option Move Java Database for Central Systems
Move Java Database for Distributed System
When you choose the ldquoMove Java Databaserdquo option for a distributed system SAPinst exports the Java
stack of the dual-stack system and uses this export to reinstall the main instances on several hosts
Every instance can run on a separate host This equates to an installation of a distributed system
These are the following instances
Central instance (CI)
Central services instance for Java (SCS)
Database instance (DB)
NOTE
If required you can reinstall the central instance and the central services instance on the ABAP
system hosts
After the installation has finished and the System Landscape Directory has been reconfigured SAPinst
removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
1054 PUBLIC 2012-04-11
Figure 2 Split Option Move Java Database for Distributed System
22 Split Option Keep Database
The split option ldquoKeep Databaserdquo offers the possibility for the Java system to reuse the existing database
of the dual-stack system using MCOD (multiple components ndash one database)
Keep Database for Central and Distributed Systems
When you choose the ldquoKeep Databaserdquo option SAPinst exports the Java file system on the dual-stack
system It uses this export to reinstall a central services instance (SCS) and a central instance (CI) for
Java They can be installed on one host on different hosts or on the source system hosts again
Additionally SAPinst adapts the Java schema of the database of the dual-stack system to the target Java
system
After the installation has finished and the System Landscape Directory has been reconfigured SAPinst
removes all Java parts from the dual-stack system except the Java database schema
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-04-11 PUBLIC 1154
Figure 3 Split Option Keep Database for Central Systems
Figure 4 Split Option Keep Database for Distributed Systems
2 Split Options Covered by this Guide
22 Split Option Keep Database
1254 PUBLIC 2012-04-11
3 Planning
31 Planning Checklist
This section includes the planning steps that you have to perform when you want to install the new
Java system on one or more hosts Perform the planning steps according to the split option and your
system variant
NOTE
Most of the required planning steps listed in this section are not described in this documentation
You can find the detailed description in the SAP NetWeaver Application Server Java installation
documentation relevant for your release at httpservicesapcominstguides
Prerequisites
You have decided on your split option [page 9]
Split Option ldquoMove Java Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
1 You check the hardware and software requirements for the Java installation host
For more information see Hardware and Software Requirements in the installation documentation of
your release
2 You read about user management [page 15]
3 You identify basic SAP system installation parameters
For more information see Basic SAP System Parameters in the installation documentation of your
release
Be aware of the following dual-stack-split-specific deviations
SAP System Parameters
User management
We do not recommend that you make modifications in the user management settings
For more information see User Management [page 15]
System Landscape Directory (SLD)
You can ignore SLD parameters
Only valid for Oracle |
SAP System Database Parameters Java database schema
We recommend that you choose a schema ID that is different from your SAP system ID
It might cause problems when you copy a system if ltSCHEMA_IDgt is the same as ltSAPSIDgt and
the database-specific method used for the copy does not allow you to rename the database
3 Planning
31 Planning Checklist
2012-04-11 PUBLIC 1354
schemes In certain situations you might create a system copy with a new ltSAPSIDgt but where
the database schema has the old ltSAPSIDgt This is not a technical problem but might be
confusing to the system administratorEnd of Oracle |
4 Only valid for MaxDB |
You plan your system configuration
For more information see System Configuration in the installation documentation of your releaseEnd of MaxDB |
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
You plan the setup of your database carefully
For more information see Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
7 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 43]
8 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
9 Only valid for IBM DB2 for zOS |
If you want to execute a Software Life-Cycle Option with SAPinst in an SAP system with thick client
connectivity see Special Considerations Regarding Connectivity for Software Life-Cycle Options in the installation
documentation of your releaseEnd of IBM DB2 for zOS |
10 Only valid for IBM DB2 for i5OS |
Optionally you decide whether you want to install multiple SAP systems on a single host
For more information see Multiple SAP Systems on a Single Host in the installation documentation of
your releaseEnd of IBM DB2 for i5OS |
11 You can continue with Preparation [page 17]
Split Option ldquoKeep Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
1 You check the hardware and software requirements for the Java installation host
For more information see Hardware and Software Requirements in the installation documentation of
your release
2 You read about user management [page 15]
3 You identify basic SAP system installation parameters
For more information see Basic SAP System Parameters in the installation documentation of your
release
3 Planning
31 Planning Checklist
1454 PUBLIC 2012-04-11
Be aware of the following dual-stack-split-specific deviation for SAP System Parameters
User management
We do not recommend that you make modifications in the user management settings For
more information see User Management [page 15]
System Landscape Directory (SLD)
You can ignore SLD parameters
4 Only valid for IBM DB2 for zOSMaxDB |
You plan your system configuration
For more information see System Configuration in the installation documentation of your releaseEnd of IBM DB2 for zOSMaxDB |
5 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
6 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 43]
7 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
8 Only valid for IBM DB2 for zOS |
If you want to execute a Software Life-Cycle Option with SAPinst in an SAP system with thick client
connectivity see Special Considerations Regarding Connectivity for Software Life-Cycle Options in the installation
documentation of your releaseEnd of IBM DB2 for zOS |
9 Only valid for IBM DB2 for i5OS |
Optionally you decide whether you want to install multiple SAP systems on a single host
For more information see Multiple SAP Systems on a Single Host in the installation documentation of
your releaseEnd of IBM DB2 for i5OS |
10 You can continue with Preparation [page 17]
32 User Management
The dual-stack split procedure does not change the user management and you cannot choose which
kind of user management you want to use for the target AS Java system That is the separated Java
system and the ABAP system both use the user management of the former dual-stack system The
following is possible
If the dual-stack system uses AS ABAP as data source for the User Management Engine (UME)
after the split the separated Java stack will also use the ABAP UME
If the dual-stack system uses an LDAP directory as source for user data this is also valid for the Java
stack
3 Planning
32 User Management
2012-04-11 PUBLIC 1554
In both cases manual configuration is not required
We do not recommend that you make modifications to the user management settings
For more information see SAP Note 718383
3 Planning
32 User Management
1654 PUBLIC 2012-04-11
4 Preparation
41 Preparation Checklist
This section includes the preparation steps that you have to perform when you want to install the new
Java system on one or more hosts
NOTE
Most of the required preparation steps listed in this section are not described in this
documentation You can find the detailed description in the SAP NetWeaver Application Server
Java installation documentation relevant for your release at httpservicesapcom
instguides
1 Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
You make sure that the required operating system users and groups are created
To create the groups and users automatically run the Dual-Stack Split Tool on the host where
the SAP Java system is to be installed and choose Dual-Stack Split Operating System Users and
Groups
For more information see Creating Operating System Users and Groups in the installation documentation
of your releaseEnd of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
2 You set up file systems and make sure that the required disk space is available for the directories
to be created during the installation
For more information see Setting Up File Systems for a High-Availability System in the installation
documentation of your release
3 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
4 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
If you want to install a high-availability system you perform switchover preparations
For more information see Performing Switchover Preparations for High-Availability in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
5 If you want to share the transport directory trans from another system you export this directory
to your installation hosts
For more information see Exporting and Mounting the Global Transport Directory in the installation
documentation of your release
4 Preparation
41 Preparation Checklist
2012-04-11 PUBLIC 1754
6 You install the Java Development Kit This step is not required if you have installed the SAP JVM
4 on your source system
For more information see Installing the Java Development Kit in the installation documentation of your
release
7 You make sure that the required installation media are available on each host
You can download the Dual-Stack Split Tool at httpservicesapcomsltoolset
Software Logistics Toolset 10 Dual-Stack Split
You can download the Java stack and database installation media from SAP Service
Marketplace as described in Preparing the Installation Media in the installation documentation of
your release
NOTE
The release level required for the installation corresponds to the release level of your dual-
stack system
The following table shows the required installation media for the dual-stack split
SAP Instance Installation Required Media
Central services instance central instance
Dual-Stack Split Tool Java DVD RDBMS Client DVD
Move Java Database only Database instance
Dual-Stack Split Tool Java DVD Only valid for MS SQL ServerOracle |
RDBMS DVDEnd of MS SQL ServerOracle |
Only valid for MS SQL ServerOracle |
RDBMS Patch DVD (if available)End of MS SQL ServerOracle |
8 Only valid for HA (MSCS) |
To install a high-availability system with Microsoft Cluster Service (MSCS) you also perform the
MSCS-specific preparation tasks as described in the installation documentation of your releaseEnd of HA (MSCS) |
9 Only valid for HA (MSCS) |
If you choose the split option ldquoKeep Databaserdquo with the scenario ldquoKeep SCS on the Source Cluster
Systemrdquo you perform the following steps
You provide additional disk storage on the target cluster system
For more information see Distribution of SAP System Components to Disks for MSCS Directories in an
MSCS Configuration and IP Addresses in an MSCS Configuration in the installation documentation of
your release
You provide an additional IP address and an additional virtual host name for the Java system
For more information see Mapping Host Names to IP Addresses for MSCS in the installation
documentation of your releaseEnd of HA (MSCS) |
4 Preparation
41 Preparation Checklist
1854 PUBLIC 2012-04-11
10 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 19] of
the dual-stack system
11 You can continue with Splitting [page 21]
42 Performing a Full System Backup
If you decided to use the split option ldquoKeep Databaserdquo you must perform a full system backup of the
dual-stack system or at least a backup of the Java database schema before you start the split procedure
If you decided to use the split option ldquoMove Java Databaserdquo you do not need to perform a backup before
you start the split procedure
For more information about backing up your database see the database-specific backup and recovery
documentation in the SAP Library [page 7] at
SAP MaxDB
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for SAP
MaxDB
Oracle
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Oracle
IBM DB2 for i5OS
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 UDB for iSeries
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for i
4 Preparation
42 Performing a Full System Backup
2012-04-11 PUBLIC 1954
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
i
IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX
and Windows
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
Linux UNIX and Windows
IBM DB2 for zOS
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 UDB for zOS
SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for DB2 for z
OS
Microsoft SQL Server
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Microsoft SQL
Server
4 Preparation
42 Performing a Full System Backup
2054 PUBLIC 2012-04-11
5 Splitting
51 Splitting Checklist
This section includes the splitting steps that you have to perform for the following split options
ldquoMove Java Databaserdquo
ldquoKeep Databaserdquo
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Only valid for Oracle |
You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 You export the Java stack using SAPinst [page 23]
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
4 You restart the source system
5 You run SAPinst [page 23] to install a Java only system using the export from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2012-04-11 PUBLIC 2154
Distributed System
1 Only valid for Oracle |
On the database instance host of the dual-stack system you install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes on the database instance host
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 On the database instance host of the dual-stack system you run SAPinst [page 23] to export the
Java database schema
4 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the Java
parts of the file system of the central instance
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
5 You restart the source system
6 You run SAPinst [page 23] to install a central services instance for the Java target system
7 You run SAPinst [page 23] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
9 You continue with Follow-Up Activities [page 33]
Keep Database
1 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the
file system of the central instance
5 Splitting
51 Splitting Checklist
2254 PUBLIC 2012-04-11
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you wont use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
2 You restart the source system
3 You run SAPinst [page 23] to install a central services instance for the Java target system
4 On the database instance host of the dual-stack system you run SAPinst [page 23] to adapt the
database for the Java target system
NOTE
Make sure that you enter the profile directory of the Java target system in the SAP System gt
General Parameters screen
5 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
52 Running SAPinst
This section describes how to run the installation tool SAPinst SAPinst includes a GUI client and a GUI
server which both use Java
The procedure describes an installation where SAPinst GUI client and GUI server are running on the
same host In the following GUI client and GUI server are addressed as ldquoSAPinst GUIrdquo
If you need to see the installation on a remote display we recommend that you perform a remote
installation with SAPinst where the SAPinst GUI is running on a separate host from SAPinst For more
information see Performing a Remote Installation with SAPinst in the installation documentation of your
release
Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote
access to SAPinst GUI on Windows workstations For more information see SAP Note 1170809
Useful Information About SAPinst
When you start SAPinst it automatically starts the SAPinst GUI
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2354
SAPinst creates the installation directory sapinst_instdir directly below the temporary directory
SAPinst 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 SAPinst
creates the installation directory sapinst_instdir directly below the tmp directory by default
If you want SAPinst to create the installation directory sapinst_instdir in another directory set
the environment variable TEMP to this directory before you start SAPinst
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
Only valid for IBM DB2 for i5OS |
NOTE
When you leave your Qp2Term session all changes of the environment variables done by the
command export are reverted
End of IBM DB2 for i5OS |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
SAPinst creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt
SAPinst extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is located
in the environment variables TEMP TMP or TMPDIR These files are deleted after SAPinst has stopped
running
The temporary directory sapinst_exexxxxxxxxxx sometimes remains undeleted You can safely
delete it
The temporary directory also contains the log file dev_selfexout from the extraction process
which might be useful if an error occurs
CAUTION
If SAPinst cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default ports 21200 21212 and 4239 are used for communication
between SAPinst GUI server GUI and HTTP server as follows
SAPinst uses port 21200 to communicate with the GUI server
The GUI server uses port 21212 to communicate with the GUI client
5 Splitting
52 Running SAPinst
2454 PUBLIC 2012-04-11
4239 is the port of the HTTP server which is part of the GUI server
If the ports for SAPinst and the GUI server are already in use SAPinst automatically searches for
free port numbers If the search fails SAPinst exits
In this case or if you want SAPinst to use specific ports you can assign them by executing the
sapinst executable with the following command line parameters
SAPINST_DIALOG_PORT=ltport_number_sapinst_to_gui_servergt
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
GUISERVER_HTTP_PORT=ltport_number_http_servergt
To see a list of all available SAPinst properties start SAPinst as described above with command line
parameter -p
sapinst -p
If you need to run SAPinst in accessibility mode proceed as described in Running SAPinst in Accessibility
Mode in the installation documentation of your release
If required you can stop SAPinst by choosing SAPinst Cancel in the SAPinst GUI menu
Prerequisites
We recommend that you use the csh shell for the installation with SAPinst If you want to use
another shell make sure that you have first read SAP Note 202227
SAPinst uses csh scripts during the installation to obtain the environment for user ltsapsidgtadm
This is also true if user ltsapsidgtadm already exists from an earlier SAP system installation and the
shell of this user is not csh Before you start SAPinst execute the following command as user
ltsapsidgtadm to make sure that the csh scripts are up-to-date
bincsh -c source lthome directory of ltsapsidgtadmgtcshrcenv
Make sure that you have specified the most important SAP system parameters as described in Basic
SAP System Installation Parameters in the installation documentation of your release before you start
SAPinst
Only valid for IBM DB2 for zOS |
Check that your installation hosts meet the requirements for the installation options that you
want to installEnd of IBM DB2 for zOS |
Only valid for Non-Standalone Engines and Clients |
If you want to perform a distributed or a high-availability installation make sure that you have
exported and mounted global directories For more information see Exporting and Mounting Global
Directories in the installation documentation of your releaseEnd of Non-Standalone Engines and Clients |
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you have carefully planned your database layout in particular the tablespace layout
as described in Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2554
Only valid for AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for Solaris |
Solaris SPARC onlyEnd of Solaris |
If you want to set up DB2s high-availability cluster solution SA MP make sure that you have read
the document IBM DB2 High Availability Solution IBM Tivoli System Automation for Multiplatforms at
httpservicesapcominstguidesnw70 Installation Installation ndash SAP NetWeaver SystemsEnd of AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for zOS |
First make sure that you have installed DB2 for zOS For information on that installation see
SAP DBA Guide DB2 for zOS DB2 Setup especially the section Stored Procedures EnablementEnd of IBM DB2 for zOS |
Check the value of the environment variable TEMP TMP or TMPDIR
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
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 ndash for example by using a crontab entry
Make sure that you have at least 60 MB of free space in the installation directory for each
installation option In addition you need 200 MB free space for the SAPinst executables If you
cannot provide 200 MB free space in the temporary directory you can set one of the
environment variables TEMP TMP or TMPDIR to another directory with 200 MB free space for
the SAPinst executables
Make sure that the temporary directory has the permissions 777
Only valid for IBM DB2 for zOS |
Make sure that your database is up and runningEnd of IBM DB2 for zOS |
Make sure that your DISPLAY environment variable is set to lthost_namegt00 where
lthost_namegt is the host on which you want to display the GUI
Shell Used Command
Bourne shell (sh) DISPLAY=lthost_namegt00
export DISPLAY
C shell (csh) setenv DISPLAY lthost_namegt00
Korn shell (ksh) export DISPLAY=lthost_namegt00
Make sure that umask is set to 022 for user root
As user root enter the following command umask 022
Check the following values for user root
5 Splitting
52 Running SAPinst
2654 PUBLIC 2012-04-11
In csh execute limit
Output Properties
cputime unlimited
filesize unlimited
datasize unlimited
stacksize 8192 KB
coredumpsize unlimited
descriptors 8192
memorysize unlimited
In sh or ksh execute ulimit -a
Output Properties
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192
coredump(blocks) unlimited
nofiles(descriptors) 8192
memory(KBytes) unlimited
If your parameter settings differ from those above change these values accordingly
EXAMPLE
If you have to change the value for descriptors to 8192 proceed as follows
In csh execute
limit descriptors 8192
In sh or ksh execute
ulimit -n 8192
Before you start SAPinst read SAP Note 1697164 for more information about which user to choose
for running the SAPinst SDT GUI server
Procedure
1 Log on to the installation host as user root
CAUTION
Do not use an existing ltsapsidgtadm user
Only valid for Non-Standalone Engines and Clients |
CAUTION
Make sure that the root user has not set any environment variables for a different SAP system
or database
End of Non-Standalone Engines and Clients |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2754
2 Make the Dual-Stack Split Tool available on the installation host Make sure that it is available
locally We do not recommend that you use Network File System (NFS) because reading from
media mounted with NFS might fail
For more information see Preparation Checklist [page 17] and Preparing the Installation Media in the
installation documentation of your release
3 Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
Only valid for Non-Standalone Engines and Clients |
Change to the directory with the sapinst executable for your operating system by entering the
following command cd ltMountpoint of Installation Master mediumgtDATA_UNITS
ltproductgt_IM_ltOSgtEnd of Non-Standalone Engines and Clients |
End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
4 Start SAPinst by executing the following command sapinst
NOTE
If you want to use a virtual host name start SAPinst with the SAPinst property
SAPINST_USE_HOSTNAME as follows
Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
sapinst SAPINST_USE_HOSTNAME=ltvirtual host namegt
End of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
5 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
In addition if you want to use the split option ldquoMove Java Databaserdquo choose ltYour System
Variantgt
Perform the export and installation steps exactly in the order in which they appear
6 Only valid for Non-Standalone Engines and Clients |
Choose NextEnd of Non-Standalone Engines and Clients |
7 Follow the instructions in the SAPinst input screens and enter the required parameters
NOTE
If SAPinst asks for the Java DVD make sure that you provide a Java DVD with the same
release level as your dual-stack system
For more information about the input parameters position the cursor on the parameter
and press F1
After you have entered all requested input parameters SAPinst displays the Parameter Summary screen
This screen shows both the parameters that you entered and those that SAPinst set by default If
required you can revise the parameters before starting the split procedure
5 Splitting
52 Running SAPinst
2854 PUBLIC 2012-04-11
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you check the following parameters depending on the installation type that you
have chosenEnd of IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for Linux and UNIX and Windows |
If you are performing a typical installation SAPinst creates four sapdata directories by
default If you require more or fewer sapdata directories depending on the storage devices
you are using you must change this parameter before you start the installation By selecting
this parameter on the Summary screen and choosing Revise SAPinst returns to the IBM DB2 for
Linux UNIX and Windows ndashgt Sapdata Directories screen
On this screen you can also decide if you want SAPinst to create the regular table and index
tablespaces with DB2s automatic storage management enabled By default the option for
automatic storage management is preselected
NOTE
As of DB2 V91 and higher the database and the SYSCATSPACE tablespace are always created
with automatic storage management enabled even if you deselect this option on the
dialog IBM DB2 for Linux UNIX and Windows gt Sapdata Directories
For more information about DB2s automatic storage management see section DB2
Tablespaces in the installation documentation of your SAP product
If you are performing a custom installation you set these parameters during the Define
Parameters phase of SAPinst
NOTE
If the tablespace layout used by SAPinst does not meet your requirements you can create
the tablespaces manually by deselecting the option Create Tablespaces with SAPinst on the
IBM DB2 for Linux and UNIX and Windows Sapdata Directories screen
During the installation phase SAPinst then displays the following message
You must create the tablespaces now To do so use the
createTablespacessql script that is located in your installation
directory
To continue the installation choose OK Alternatively you can cancel
SAPinst here and restart it again
SAPinst does not check the page size of tablespaces that have either been created manually
or that already exist If you create the tablespaces manually you must make sure that
you use a page size of 16 KBEnd of IBM DB2 for Linux and UNIX and Windows |
8 To start the dual-stack split choose Start
SAPinst starts and displays the progress of the split procedure
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2954
When the split option has finished successfully SAPinst displays the message Execution of
ltOption_Namegt has completed
Only valid for Oracle |
NOTE
When installing the Oracle database instance SAPinst stops the installation and prompts
you to install the Oracle database software For more information see Installing the Oracle
Database Software in the installation documentation of your release
After you have finished the installation of the Oracle database you continue the database
instance installation by choosing OK in the GUI of the database instance installation
Check SAP Note 1431800 for technical information about Oracle Release 112 in SAP
environments
End of Oracle |
Only valid for Enterprise Portal (EP) |
NOTE
During the final restart of Application Server Java performed by SAPinst the portal starts the
processing and uploading of the new portal archives It takes approximately 15 to 90 minutes
before the deployment is completed and the portal is launched
Do not stop SAPinst or Application Server Java during this phase
End of Enterprise Portal (EP) |
9 If required delete directories with the name sapinst_exexxxxxxxxxx after SAPinst has finished
Sometimes these remain in the temporary directory
NOTE
If there are errors with the SAPinst extraction process you can find the log file
dev_selfexout in the temporary directory
Only valid for Non-Standalone Engines and Clients |
RECOMMENDATION
Keep all installation 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 installation 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 installation directories on installation hosts but make sure
that you delete them after saving them separately
End of Non-Standalone Engines and Clients |
10 We recommend that you delete the directory ltuser_homegtsdtgui
11 Only valid for IBM DB2 for Linux and UNIX and Windows |
If not already done install the DB2 license
5 Splitting
52 Running SAPinst
3054 PUBLIC 2012-04-11
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
End of IBM DB2 for Linux and UNIX and Windows |
12 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 3154
This page is left blank for documents that are printed on both sides
6 Follow-Up Activities
61 Follow-Up Activities Checklist
This section includes the follow-up activities that you have to perform for the following split options
ldquoMove Java Databaserdquo for a central system
ldquoMove Java Databaserdquo for a distributed system or a high-availability system
ldquoKeep Databaserdquo for a central distributed or high-availability system
NOTE
Some of the follow-up activities listed in this section are not described in this documentation You
can find the detailed description in the SAP NetWeaver Application Server Java system copy
documentation relevant for your release at
httpservicesapcominstguides
Move Java Database
Central System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3354
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
7 We recommend that you perform regression testing
8 On the source system you run SAPinst [page 23] to remove the Java parts in the file system and in
the database
9 On the source system you call transaction RZ10 to reimport the profiles from the file system
10 In the Transport Management System (TMS) you configure the transport routes [page 38]
11 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
12 You clean up the system landscape data [page 40]
Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3454 PUBLIC 2012-04-11
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the database host of the source system you run SAPinst [page 23] to remove the Java database
schema
12 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
13 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
14 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
15 You clean up the system landscape data [page 40]
Keep Database
Central Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3554
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
12 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
13 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
14 You clean up the system landscape data [page 40]
62 Maintaining the Connection to the System Landscape Directory
After installing the Java system you need to reconfigure the connection between the System Landscape
Directory (SLD) the source system and the target system The steps required differ depending on
whether you use a local or a central SLD To maintain the connection to the SLD you can either run
the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split or perform the required steps manually as described below
NOTE
This step is only required if the connection to the SLD was established on the source system before
the split
Prerequisites
If you want to use the configuration wizard you need an SAP NetWeaver Java system 70 Support
Package 14 or higher in your landscape
SLDAPIUSER credentials are available in the ABAP system
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3654 PUBLIC 2012-04-11
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
Table of Contents
Chapter 1 Introduction 5
11 SAP Notes for the Dual-Stack Split 6
12 Accessing the SAP Library 7
13 How to Use this Guide 7
Chapter 2 Split Options Covered by this Guide 9
21 Split Option Move Java Database 9
22 Split Option Keep Database 11
Chapter 3 Planning 13
31 Planning Checklist 13
32 User Management 15
Chapter 4 Preparation 17
41 Preparation Checklist 17
42 Performing a Full System Backup 19
Chapter 5 Splitting 21
51 Splitting Checklist 21
52 Running SAPinst 23
Chapter 6 Follow-Up Activities 33
61 Follow-Up Activities Checklist 33
62 Maintaining the Connection to the System Landscape Directory 36
63 Configuring Transport Routes 38
64 Configuring the CTS Deploy Web Service 39
65 Cleaning Up the System Landscape 40
Chapter 7 Additional Information 41
71 Troubleshooting with SAPinst 41
72 Move Java Database Restarting Instances 42
73 Keep Database Restarting Instances 42
2012-04-11 PUBLIC 354
74 Splitting Within a System Landscape 43
75 Removing the Java Stack 46
Chapter A Appendix 47
A1 Online Information from SAP 47
A2 Online Information from IBM 49
454 PUBLIC 2012-04-11
1 Introduction
This document explains how to use the Dual-Stack Split 20 tool to split a dual-stack (ABAP+Java)
system into one ABAP and one Java stack each with its own system ID This tool is part of the installation
tool SAPinst and it mainly uses the Java system copy functionality It is delivered as part of Support
Package 4 of the Software Logistics Toolset (SL Toolset) 10
The dual-stack split procedure is valid for SAP dual-stack systems based on the following SAP NetWeaver
release levels
SAP NetWeaver 70 SP14 or higher
SAP NetWeaver 70 including Enhancement Package 1
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver 70 including Enhancement Package 3
The procedure described in this guide mainly applies to splitting a single SAP dual-stack system For
more information about splitting systems within a system landscape see Splitting Within a System
Landscape [page 43]
Definitions
Dual-Stack System
A dual-stack system is an SAP system that contains installations of both SAP NetWeaver Application
Server ABAP and SAP NetWeaver Application Server Java It has the following characteristics
Common SAP system ID for its ABAP and Java stacks
Common startup framework
Common database (with different schemes for ABAP and Java)
Dual-Stack Split
While splitting-off the Java part of a dual-stack system into a separate system the dual-stack system is
reduced to an ABAP system To do this the Dual-Stack Split Tool runs a system copy and uses the Java
system copy export to reinstall the Java system separately and with a new SAP system ID The ABAP
stack of the former dual-stack system is not affected by this procedure The separated systems can either
use their own databases (see Split Option Move Java Database [page 9]) or both use the existing database
in the ABAP system (see Split Option Keep Database [page 11])
Use Case
As of SAP NetWeaver 70 including Enhancement Package 3 and SAP Business Suite 7i2011 which
is based on SAP NetWeaver 70 including Enhancement Package 3 the installation of SAP dual-
1 Introduction
2012-04-11 PUBLIC 554
stack systems is no longer supported Furthermore as of SAP Business Suite 7i2011 it will no longer
be possible to upgrade an SAP dual-stack system to a higher release
Since the dual-stack split procedure is only available for SAP NetWeaver 70 systems we recommend
that you split your SAP dual-stack system before you perform an upgrade to one of the following
releases
SAP NetWeaver 73
SAP NetWeaver 73 including Enhancement Package 1
If your system is an SAP Business Suite 7i2011 dual-stack system we strongly recommend that
you perform a dual-stack split as it is no longer possible to upgrade to a higher release
For more information see SAP Note 1655335
If you no longer need the Java stack of your dual-stack system you can remove it as described in
Removing the Java Stack [page 46]
Constraints
You need to consider some constraints before you start splitting your SAP dual-stack system
The dual-stack split procedure does not support the splitting of the following
SAP NetWeaver Process Integration systems
SAP Solution Manager systems
The dual-stack split procedure does not implicate the following
Prerequisites Checker
Host agent
Diagnostics agent
Dialog instances
You can ignore sections in the installation documentation that focus on these options
NOTE
If these options are installed on your SAP dual-stack system and you want to use them on
the Java system after the split you need to install them again on the Java system using the
Installation Master DVD that you used to install your dual-stack system
The migration of the operating system or the database platform during the split is not supported
Naming Conventions
SAP system refers to SAP NetWeaver system or SAP system based on SAP NetWeaver
Dual-stack system refers to SAP NetWeaver ABAP+Java system or SAP ABAP+Java system based on SAP
NetWeaver
11 SAP Notes for the Dual-Stack Split
You must read the following SAP Notes before you start the dual-stack split These SAP Notes contain
the most recent information on the dual-stack split as well as corrections to the dual-stack split
1 Introduction
11 SAP Notes for the Dual-Stack Split
654 PUBLIC 2012-04-11
documentation Make sure that you have the most up-to-date version of each SAP Note which you
can find at httpservicesapcomnotes
SAP Notes for the Dual-Stack Split
SAP Note Number Title Description
1685432 Dual-Stack Split 20 SP1 for Systems Based on SAP NetWeaver
Problems discovered after the publication of the dual-stack split guide
1655335 Use Cases for Splitting Dual-Stack Systems mdash
12 Accessing the SAP Library
The references to the SAP NetWeaver Library documentation in this dual-stack split guide always
refer to the following on SAP Help Portal
SAP NetWeaver 70
httphelpsapcomnw70 Application Help SAP Library English SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 1
httphelpsapcomnw701 Application Help SAP Library English SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 2
httphelpsapcomnw702 Application Help SAP Library English SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 3
httphelpsapcomnw703 Application Help SAP Library English SAP NetWeaver
13 How to Use this Guide
This documentation comprises the description of the dual-stack split procedure and dual-stack-split-
specific steps For general or installation-specific information see the installation documentation
relevant for your release which you can find at httpservicesapcominstguides
Procedure
1 You decide on the split option that you want to use The following split options are available for
central distributed and high-availability systems
ldquoMove Java Databaserdquo (non-MCOD)
ldquoKeep Databaserdquo (MCOD)
For more information see Split Options Covered by this Guide [page 9]
2 You follow the list of steps at the beginning of each phase
Planning [page 13]
Preparation [page 17]
Splitting [page 21]
Follow-up Activities [page 33]
1 Introduction
12 Accessing the SAP Library
2012-04-11 PUBLIC 754
This page is left blank for documents that are printed on both sides
2 Split Options Covered by this Guide
This section shows the split options covered by this guide You have to decide which option you want
to use because the steps you have to perform vary according to the split option that you choose
Move Java Database [page 9]
Keep Database [page 11]
21 Split Option Move Java Database
The split option ldquoMove Java Databaserdquo offers the possibility to split a dual-stack system into one ABAP
system and one Java system each with its own database (non-MCOD)
Move Java Database for Central Systems
When you choose the ldquoMove Java Databaserdquo option for a central system SAPinst exports the Java stack
of the dual-stack system and uses this export to reinstall all main instances on a single host This equates
to an installation of a central system
These are the following instances
Central instance (CI)
Central services instance for Java (SCS)
Database instance (DB)
NOTE
If required you can install the central instance and the central services instance on the ABAP
system host again
Once the installation has finished and after the System Landscape Directory has been reconfigured
SAPinst removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
2012-04-11 PUBLIC 954
Figure 1 Split Option Move Java Database for Central Systems
Move Java Database for Distributed System
When you choose the ldquoMove Java Databaserdquo option for a distributed system SAPinst exports the Java
stack of the dual-stack system and uses this export to reinstall the main instances on several hosts
Every instance can run on a separate host This equates to an installation of a distributed system
These are the following instances
Central instance (CI)
Central services instance for Java (SCS)
Database instance (DB)
NOTE
If required you can reinstall the central instance and the central services instance on the ABAP
system hosts
After the installation has finished and the System Landscape Directory has been reconfigured SAPinst
removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
1054 PUBLIC 2012-04-11
Figure 2 Split Option Move Java Database for Distributed System
22 Split Option Keep Database
The split option ldquoKeep Databaserdquo offers the possibility for the Java system to reuse the existing database
of the dual-stack system using MCOD (multiple components ndash one database)
Keep Database for Central and Distributed Systems
When you choose the ldquoKeep Databaserdquo option SAPinst exports the Java file system on the dual-stack
system It uses this export to reinstall a central services instance (SCS) and a central instance (CI) for
Java They can be installed on one host on different hosts or on the source system hosts again
Additionally SAPinst adapts the Java schema of the database of the dual-stack system to the target Java
system
After the installation has finished and the System Landscape Directory has been reconfigured SAPinst
removes all Java parts from the dual-stack system except the Java database schema
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-04-11 PUBLIC 1154
Figure 3 Split Option Keep Database for Central Systems
Figure 4 Split Option Keep Database for Distributed Systems
2 Split Options Covered by this Guide
22 Split Option Keep Database
1254 PUBLIC 2012-04-11
3 Planning
31 Planning Checklist
This section includes the planning steps that you have to perform when you want to install the new
Java system on one or more hosts Perform the planning steps according to the split option and your
system variant
NOTE
Most of the required planning steps listed in this section are not described in this documentation
You can find the detailed description in the SAP NetWeaver Application Server Java installation
documentation relevant for your release at httpservicesapcominstguides
Prerequisites
You have decided on your split option [page 9]
Split Option ldquoMove Java Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
1 You check the hardware and software requirements for the Java installation host
For more information see Hardware and Software Requirements in the installation documentation of
your release
2 You read about user management [page 15]
3 You identify basic SAP system installation parameters
For more information see Basic SAP System Parameters in the installation documentation of your
release
Be aware of the following dual-stack-split-specific deviations
SAP System Parameters
User management
We do not recommend that you make modifications in the user management settings
For more information see User Management [page 15]
System Landscape Directory (SLD)
You can ignore SLD parameters
Only valid for Oracle |
SAP System Database Parameters Java database schema
We recommend that you choose a schema ID that is different from your SAP system ID
It might cause problems when you copy a system if ltSCHEMA_IDgt is the same as ltSAPSIDgt and
the database-specific method used for the copy does not allow you to rename the database
3 Planning
31 Planning Checklist
2012-04-11 PUBLIC 1354
schemes In certain situations you might create a system copy with a new ltSAPSIDgt but where
the database schema has the old ltSAPSIDgt This is not a technical problem but might be
confusing to the system administratorEnd of Oracle |
4 Only valid for MaxDB |
You plan your system configuration
For more information see System Configuration in the installation documentation of your releaseEnd of MaxDB |
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
You plan the setup of your database carefully
For more information see Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
7 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 43]
8 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
9 Only valid for IBM DB2 for zOS |
If you want to execute a Software Life-Cycle Option with SAPinst in an SAP system with thick client
connectivity see Special Considerations Regarding Connectivity for Software Life-Cycle Options in the installation
documentation of your releaseEnd of IBM DB2 for zOS |
10 Only valid for IBM DB2 for i5OS |
Optionally you decide whether you want to install multiple SAP systems on a single host
For more information see Multiple SAP Systems on a Single Host in the installation documentation of
your releaseEnd of IBM DB2 for i5OS |
11 You can continue with Preparation [page 17]
Split Option ldquoKeep Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
1 You check the hardware and software requirements for the Java installation host
For more information see Hardware and Software Requirements in the installation documentation of
your release
2 You read about user management [page 15]
3 You identify basic SAP system installation parameters
For more information see Basic SAP System Parameters in the installation documentation of your
release
3 Planning
31 Planning Checklist
1454 PUBLIC 2012-04-11
Be aware of the following dual-stack-split-specific deviation for SAP System Parameters
User management
We do not recommend that you make modifications in the user management settings For
more information see User Management [page 15]
System Landscape Directory (SLD)
You can ignore SLD parameters
4 Only valid for IBM DB2 for zOSMaxDB |
You plan your system configuration
For more information see System Configuration in the installation documentation of your releaseEnd of IBM DB2 for zOSMaxDB |
5 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
6 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 43]
7 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
8 Only valid for IBM DB2 for zOS |
If you want to execute a Software Life-Cycle Option with SAPinst in an SAP system with thick client
connectivity see Special Considerations Regarding Connectivity for Software Life-Cycle Options in the installation
documentation of your releaseEnd of IBM DB2 for zOS |
9 Only valid for IBM DB2 for i5OS |
Optionally you decide whether you want to install multiple SAP systems on a single host
For more information see Multiple SAP Systems on a Single Host in the installation documentation of
your releaseEnd of IBM DB2 for i5OS |
10 You can continue with Preparation [page 17]
32 User Management
The dual-stack split procedure does not change the user management and you cannot choose which
kind of user management you want to use for the target AS Java system That is the separated Java
system and the ABAP system both use the user management of the former dual-stack system The
following is possible
If the dual-stack system uses AS ABAP as data source for the User Management Engine (UME)
after the split the separated Java stack will also use the ABAP UME
If the dual-stack system uses an LDAP directory as source for user data this is also valid for the Java
stack
3 Planning
32 User Management
2012-04-11 PUBLIC 1554
In both cases manual configuration is not required
We do not recommend that you make modifications to the user management settings
For more information see SAP Note 718383
3 Planning
32 User Management
1654 PUBLIC 2012-04-11
4 Preparation
41 Preparation Checklist
This section includes the preparation steps that you have to perform when you want to install the new
Java system on one or more hosts
NOTE
Most of the required preparation steps listed in this section are not described in this
documentation You can find the detailed description in the SAP NetWeaver Application Server
Java installation documentation relevant for your release at httpservicesapcom
instguides
1 Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
You make sure that the required operating system users and groups are created
To create the groups and users automatically run the Dual-Stack Split Tool on the host where
the SAP Java system is to be installed and choose Dual-Stack Split Operating System Users and
Groups
For more information see Creating Operating System Users and Groups in the installation documentation
of your releaseEnd of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
2 You set up file systems and make sure that the required disk space is available for the directories
to be created during the installation
For more information see Setting Up File Systems for a High-Availability System in the installation
documentation of your release
3 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
4 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
If you want to install a high-availability system you perform switchover preparations
For more information see Performing Switchover Preparations for High-Availability in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
5 If you want to share the transport directory trans from another system you export this directory
to your installation hosts
For more information see Exporting and Mounting the Global Transport Directory in the installation
documentation of your release
4 Preparation
41 Preparation Checklist
2012-04-11 PUBLIC 1754
6 You install the Java Development Kit This step is not required if you have installed the SAP JVM
4 on your source system
For more information see Installing the Java Development Kit in the installation documentation of your
release
7 You make sure that the required installation media are available on each host
You can download the Dual-Stack Split Tool at httpservicesapcomsltoolset
Software Logistics Toolset 10 Dual-Stack Split
You can download the Java stack and database installation media from SAP Service
Marketplace as described in Preparing the Installation Media in the installation documentation of
your release
NOTE
The release level required for the installation corresponds to the release level of your dual-
stack system
The following table shows the required installation media for the dual-stack split
SAP Instance Installation Required Media
Central services instance central instance
Dual-Stack Split Tool Java DVD RDBMS Client DVD
Move Java Database only Database instance
Dual-Stack Split Tool Java DVD Only valid for MS SQL ServerOracle |
RDBMS DVDEnd of MS SQL ServerOracle |
Only valid for MS SQL ServerOracle |
RDBMS Patch DVD (if available)End of MS SQL ServerOracle |
8 Only valid for HA (MSCS) |
To install a high-availability system with Microsoft Cluster Service (MSCS) you also perform the
MSCS-specific preparation tasks as described in the installation documentation of your releaseEnd of HA (MSCS) |
9 Only valid for HA (MSCS) |
If you choose the split option ldquoKeep Databaserdquo with the scenario ldquoKeep SCS on the Source Cluster
Systemrdquo you perform the following steps
You provide additional disk storage on the target cluster system
For more information see Distribution of SAP System Components to Disks for MSCS Directories in an
MSCS Configuration and IP Addresses in an MSCS Configuration in the installation documentation of
your release
You provide an additional IP address and an additional virtual host name for the Java system
For more information see Mapping Host Names to IP Addresses for MSCS in the installation
documentation of your releaseEnd of HA (MSCS) |
4 Preparation
41 Preparation Checklist
1854 PUBLIC 2012-04-11
10 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 19] of
the dual-stack system
11 You can continue with Splitting [page 21]
42 Performing a Full System Backup
If you decided to use the split option ldquoKeep Databaserdquo you must perform a full system backup of the
dual-stack system or at least a backup of the Java database schema before you start the split procedure
If you decided to use the split option ldquoMove Java Databaserdquo you do not need to perform a backup before
you start the split procedure
For more information about backing up your database see the database-specific backup and recovery
documentation in the SAP Library [page 7] at
SAP MaxDB
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for SAP
MaxDB
Oracle
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Oracle
IBM DB2 for i5OS
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 UDB for iSeries
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for i
4 Preparation
42 Performing a Full System Backup
2012-04-11 PUBLIC 1954
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
i
IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX
and Windows
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
Linux UNIX and Windows
IBM DB2 for zOS
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 UDB for zOS
SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for DB2 for z
OS
Microsoft SQL Server
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Microsoft SQL
Server
4 Preparation
42 Performing a Full System Backup
2054 PUBLIC 2012-04-11
5 Splitting
51 Splitting Checklist
This section includes the splitting steps that you have to perform for the following split options
ldquoMove Java Databaserdquo
ldquoKeep Databaserdquo
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Only valid for Oracle |
You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 You export the Java stack using SAPinst [page 23]
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
4 You restart the source system
5 You run SAPinst [page 23] to install a Java only system using the export from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2012-04-11 PUBLIC 2154
Distributed System
1 Only valid for Oracle |
On the database instance host of the dual-stack system you install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes on the database instance host
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 On the database instance host of the dual-stack system you run SAPinst [page 23] to export the
Java database schema
4 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the Java
parts of the file system of the central instance
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
5 You restart the source system
6 You run SAPinst [page 23] to install a central services instance for the Java target system
7 You run SAPinst [page 23] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
9 You continue with Follow-Up Activities [page 33]
Keep Database
1 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the
file system of the central instance
5 Splitting
51 Splitting Checklist
2254 PUBLIC 2012-04-11
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you wont use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
2 You restart the source system
3 You run SAPinst [page 23] to install a central services instance for the Java target system
4 On the database instance host of the dual-stack system you run SAPinst [page 23] to adapt the
database for the Java target system
NOTE
Make sure that you enter the profile directory of the Java target system in the SAP System gt
General Parameters screen
5 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
52 Running SAPinst
This section describes how to run the installation tool SAPinst SAPinst includes a GUI client and a GUI
server which both use Java
The procedure describes an installation where SAPinst GUI client and GUI server are running on the
same host In the following GUI client and GUI server are addressed as ldquoSAPinst GUIrdquo
If you need to see the installation on a remote display we recommend that you perform a remote
installation with SAPinst where the SAPinst GUI is running on a separate host from SAPinst For more
information see Performing a Remote Installation with SAPinst in the installation documentation of your
release
Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote
access to SAPinst GUI on Windows workstations For more information see SAP Note 1170809
Useful Information About SAPinst
When you start SAPinst it automatically starts the SAPinst GUI
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2354
SAPinst creates the installation directory sapinst_instdir directly below the temporary directory
SAPinst 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 SAPinst
creates the installation directory sapinst_instdir directly below the tmp directory by default
If you want SAPinst to create the installation directory sapinst_instdir in another directory set
the environment variable TEMP to this directory before you start SAPinst
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
Only valid for IBM DB2 for i5OS |
NOTE
When you leave your Qp2Term session all changes of the environment variables done by the
command export are reverted
End of IBM DB2 for i5OS |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
SAPinst creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt
SAPinst extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is located
in the environment variables TEMP TMP or TMPDIR These files are deleted after SAPinst has stopped
running
The temporary directory sapinst_exexxxxxxxxxx sometimes remains undeleted You can safely
delete it
The temporary directory also contains the log file dev_selfexout from the extraction process
which might be useful if an error occurs
CAUTION
If SAPinst cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default ports 21200 21212 and 4239 are used for communication
between SAPinst GUI server GUI and HTTP server as follows
SAPinst uses port 21200 to communicate with the GUI server
The GUI server uses port 21212 to communicate with the GUI client
5 Splitting
52 Running SAPinst
2454 PUBLIC 2012-04-11
4239 is the port of the HTTP server which is part of the GUI server
If the ports for SAPinst and the GUI server are already in use SAPinst automatically searches for
free port numbers If the search fails SAPinst exits
In this case or if you want SAPinst to use specific ports you can assign them by executing the
sapinst executable with the following command line parameters
SAPINST_DIALOG_PORT=ltport_number_sapinst_to_gui_servergt
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
GUISERVER_HTTP_PORT=ltport_number_http_servergt
To see a list of all available SAPinst properties start SAPinst as described above with command line
parameter -p
sapinst -p
If you need to run SAPinst in accessibility mode proceed as described in Running SAPinst in Accessibility
Mode in the installation documentation of your release
If required you can stop SAPinst by choosing SAPinst Cancel in the SAPinst GUI menu
Prerequisites
We recommend that you use the csh shell for the installation with SAPinst If you want to use
another shell make sure that you have first read SAP Note 202227
SAPinst uses csh scripts during the installation to obtain the environment for user ltsapsidgtadm
This is also true if user ltsapsidgtadm already exists from an earlier SAP system installation and the
shell of this user is not csh Before you start SAPinst execute the following command as user
ltsapsidgtadm to make sure that the csh scripts are up-to-date
bincsh -c source lthome directory of ltsapsidgtadmgtcshrcenv
Make sure that you have specified the most important SAP system parameters as described in Basic
SAP System Installation Parameters in the installation documentation of your release before you start
SAPinst
Only valid for IBM DB2 for zOS |
Check that your installation hosts meet the requirements for the installation options that you
want to installEnd of IBM DB2 for zOS |
Only valid for Non-Standalone Engines and Clients |
If you want to perform a distributed or a high-availability installation make sure that you have
exported and mounted global directories For more information see Exporting and Mounting Global
Directories in the installation documentation of your releaseEnd of Non-Standalone Engines and Clients |
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you have carefully planned your database layout in particular the tablespace layout
as described in Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2554
Only valid for AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for Solaris |
Solaris SPARC onlyEnd of Solaris |
If you want to set up DB2s high-availability cluster solution SA MP make sure that you have read
the document IBM DB2 High Availability Solution IBM Tivoli System Automation for Multiplatforms at
httpservicesapcominstguidesnw70 Installation Installation ndash SAP NetWeaver SystemsEnd of AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for zOS |
First make sure that you have installed DB2 for zOS For information on that installation see
SAP DBA Guide DB2 for zOS DB2 Setup especially the section Stored Procedures EnablementEnd of IBM DB2 for zOS |
Check the value of the environment variable TEMP TMP or TMPDIR
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
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 ndash for example by using a crontab entry
Make sure that you have at least 60 MB of free space in the installation directory for each
installation option In addition you need 200 MB free space for the SAPinst executables If you
cannot provide 200 MB free space in the temporary directory you can set one of the
environment variables TEMP TMP or TMPDIR to another directory with 200 MB free space for
the SAPinst executables
Make sure that the temporary directory has the permissions 777
Only valid for IBM DB2 for zOS |
Make sure that your database is up and runningEnd of IBM DB2 for zOS |
Make sure that your DISPLAY environment variable is set to lthost_namegt00 where
lthost_namegt is the host on which you want to display the GUI
Shell Used Command
Bourne shell (sh) DISPLAY=lthost_namegt00
export DISPLAY
C shell (csh) setenv DISPLAY lthost_namegt00
Korn shell (ksh) export DISPLAY=lthost_namegt00
Make sure that umask is set to 022 for user root
As user root enter the following command umask 022
Check the following values for user root
5 Splitting
52 Running SAPinst
2654 PUBLIC 2012-04-11
In csh execute limit
Output Properties
cputime unlimited
filesize unlimited
datasize unlimited
stacksize 8192 KB
coredumpsize unlimited
descriptors 8192
memorysize unlimited
In sh or ksh execute ulimit -a
Output Properties
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192
coredump(blocks) unlimited
nofiles(descriptors) 8192
memory(KBytes) unlimited
If your parameter settings differ from those above change these values accordingly
EXAMPLE
If you have to change the value for descriptors to 8192 proceed as follows
In csh execute
limit descriptors 8192
In sh or ksh execute
ulimit -n 8192
Before you start SAPinst read SAP Note 1697164 for more information about which user to choose
for running the SAPinst SDT GUI server
Procedure
1 Log on to the installation host as user root
CAUTION
Do not use an existing ltsapsidgtadm user
Only valid for Non-Standalone Engines and Clients |
CAUTION
Make sure that the root user has not set any environment variables for a different SAP system
or database
End of Non-Standalone Engines and Clients |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2754
2 Make the Dual-Stack Split Tool available on the installation host Make sure that it is available
locally We do not recommend that you use Network File System (NFS) because reading from
media mounted with NFS might fail
For more information see Preparation Checklist [page 17] and Preparing the Installation Media in the
installation documentation of your release
3 Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
Only valid for Non-Standalone Engines and Clients |
Change to the directory with the sapinst executable for your operating system by entering the
following command cd ltMountpoint of Installation Master mediumgtDATA_UNITS
ltproductgt_IM_ltOSgtEnd of Non-Standalone Engines and Clients |
End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
4 Start SAPinst by executing the following command sapinst
NOTE
If you want to use a virtual host name start SAPinst with the SAPinst property
SAPINST_USE_HOSTNAME as follows
Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
sapinst SAPINST_USE_HOSTNAME=ltvirtual host namegt
End of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
5 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
In addition if you want to use the split option ldquoMove Java Databaserdquo choose ltYour System
Variantgt
Perform the export and installation steps exactly in the order in which they appear
6 Only valid for Non-Standalone Engines and Clients |
Choose NextEnd of Non-Standalone Engines and Clients |
7 Follow the instructions in the SAPinst input screens and enter the required parameters
NOTE
If SAPinst asks for the Java DVD make sure that you provide a Java DVD with the same
release level as your dual-stack system
For more information about the input parameters position the cursor on the parameter
and press F1
After you have entered all requested input parameters SAPinst displays the Parameter Summary screen
This screen shows both the parameters that you entered and those that SAPinst set by default If
required you can revise the parameters before starting the split procedure
5 Splitting
52 Running SAPinst
2854 PUBLIC 2012-04-11
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you check the following parameters depending on the installation type that you
have chosenEnd of IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for Linux and UNIX and Windows |
If you are performing a typical installation SAPinst creates four sapdata directories by
default If you require more or fewer sapdata directories depending on the storage devices
you are using you must change this parameter before you start the installation By selecting
this parameter on the Summary screen and choosing Revise SAPinst returns to the IBM DB2 for
Linux UNIX and Windows ndashgt Sapdata Directories screen
On this screen you can also decide if you want SAPinst to create the regular table and index
tablespaces with DB2s automatic storage management enabled By default the option for
automatic storage management is preselected
NOTE
As of DB2 V91 and higher the database and the SYSCATSPACE tablespace are always created
with automatic storage management enabled even if you deselect this option on the
dialog IBM DB2 for Linux UNIX and Windows gt Sapdata Directories
For more information about DB2s automatic storage management see section DB2
Tablespaces in the installation documentation of your SAP product
If you are performing a custom installation you set these parameters during the Define
Parameters phase of SAPinst
NOTE
If the tablespace layout used by SAPinst does not meet your requirements you can create
the tablespaces manually by deselecting the option Create Tablespaces with SAPinst on the
IBM DB2 for Linux and UNIX and Windows Sapdata Directories screen
During the installation phase SAPinst then displays the following message
You must create the tablespaces now To do so use the
createTablespacessql script that is located in your installation
directory
To continue the installation choose OK Alternatively you can cancel
SAPinst here and restart it again
SAPinst does not check the page size of tablespaces that have either been created manually
or that already exist If you create the tablespaces manually you must make sure that
you use a page size of 16 KBEnd of IBM DB2 for Linux and UNIX and Windows |
8 To start the dual-stack split choose Start
SAPinst starts and displays the progress of the split procedure
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2954
When the split option has finished successfully SAPinst displays the message Execution of
ltOption_Namegt has completed
Only valid for Oracle |
NOTE
When installing the Oracle database instance SAPinst stops the installation and prompts
you to install the Oracle database software For more information see Installing the Oracle
Database Software in the installation documentation of your release
After you have finished the installation of the Oracle database you continue the database
instance installation by choosing OK in the GUI of the database instance installation
Check SAP Note 1431800 for technical information about Oracle Release 112 in SAP
environments
End of Oracle |
Only valid for Enterprise Portal (EP) |
NOTE
During the final restart of Application Server Java performed by SAPinst the portal starts the
processing and uploading of the new portal archives It takes approximately 15 to 90 minutes
before the deployment is completed and the portal is launched
Do not stop SAPinst or Application Server Java during this phase
End of Enterprise Portal (EP) |
9 If required delete directories with the name sapinst_exexxxxxxxxxx after SAPinst has finished
Sometimes these remain in the temporary directory
NOTE
If there are errors with the SAPinst extraction process you can find the log file
dev_selfexout in the temporary directory
Only valid for Non-Standalone Engines and Clients |
RECOMMENDATION
Keep all installation 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 installation 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 installation directories on installation hosts but make sure
that you delete them after saving them separately
End of Non-Standalone Engines and Clients |
10 We recommend that you delete the directory ltuser_homegtsdtgui
11 Only valid for IBM DB2 for Linux and UNIX and Windows |
If not already done install the DB2 license
5 Splitting
52 Running SAPinst
3054 PUBLIC 2012-04-11
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
End of IBM DB2 for Linux and UNIX and Windows |
12 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 3154
This page is left blank for documents that are printed on both sides
6 Follow-Up Activities
61 Follow-Up Activities Checklist
This section includes the follow-up activities that you have to perform for the following split options
ldquoMove Java Databaserdquo for a central system
ldquoMove Java Databaserdquo for a distributed system or a high-availability system
ldquoKeep Databaserdquo for a central distributed or high-availability system
NOTE
Some of the follow-up activities listed in this section are not described in this documentation You
can find the detailed description in the SAP NetWeaver Application Server Java system copy
documentation relevant for your release at
httpservicesapcominstguides
Move Java Database
Central System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3354
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
7 We recommend that you perform regression testing
8 On the source system you run SAPinst [page 23] to remove the Java parts in the file system and in
the database
9 On the source system you call transaction RZ10 to reimport the profiles from the file system
10 In the Transport Management System (TMS) you configure the transport routes [page 38]
11 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
12 You clean up the system landscape data [page 40]
Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3454 PUBLIC 2012-04-11
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the database host of the source system you run SAPinst [page 23] to remove the Java database
schema
12 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
13 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
14 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
15 You clean up the system landscape data [page 40]
Keep Database
Central Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3554
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
12 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
13 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
14 You clean up the system landscape data [page 40]
62 Maintaining the Connection to the System Landscape Directory
After installing the Java system you need to reconfigure the connection between the System Landscape
Directory (SLD) the source system and the target system The steps required differ depending on
whether you use a local or a central SLD To maintain the connection to the SLD you can either run
the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split or perform the required steps manually as described below
NOTE
This step is only required if the connection to the SLD was established on the source system before
the split
Prerequisites
If you want to use the configuration wizard you need an SAP NetWeaver Java system 70 Support
Package 14 or higher in your landscape
SLDAPIUSER credentials are available in the ABAP system
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3654 PUBLIC 2012-04-11
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
74 Splitting Within a System Landscape 43
75 Removing the Java Stack 46
Chapter A Appendix 47
A1 Online Information from SAP 47
A2 Online Information from IBM 49
454 PUBLIC 2012-04-11
1 Introduction
This document explains how to use the Dual-Stack Split 20 tool to split a dual-stack (ABAP+Java)
system into one ABAP and one Java stack each with its own system ID This tool is part of the installation
tool SAPinst and it mainly uses the Java system copy functionality It is delivered as part of Support
Package 4 of the Software Logistics Toolset (SL Toolset) 10
The dual-stack split procedure is valid for SAP dual-stack systems based on the following SAP NetWeaver
release levels
SAP NetWeaver 70 SP14 or higher
SAP NetWeaver 70 including Enhancement Package 1
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver 70 including Enhancement Package 3
The procedure described in this guide mainly applies to splitting a single SAP dual-stack system For
more information about splitting systems within a system landscape see Splitting Within a System
Landscape [page 43]
Definitions
Dual-Stack System
A dual-stack system is an SAP system that contains installations of both SAP NetWeaver Application
Server ABAP and SAP NetWeaver Application Server Java It has the following characteristics
Common SAP system ID for its ABAP and Java stacks
Common startup framework
Common database (with different schemes for ABAP and Java)
Dual-Stack Split
While splitting-off the Java part of a dual-stack system into a separate system the dual-stack system is
reduced to an ABAP system To do this the Dual-Stack Split Tool runs a system copy and uses the Java
system copy export to reinstall the Java system separately and with a new SAP system ID The ABAP
stack of the former dual-stack system is not affected by this procedure The separated systems can either
use their own databases (see Split Option Move Java Database [page 9]) or both use the existing database
in the ABAP system (see Split Option Keep Database [page 11])
Use Case
As of SAP NetWeaver 70 including Enhancement Package 3 and SAP Business Suite 7i2011 which
is based on SAP NetWeaver 70 including Enhancement Package 3 the installation of SAP dual-
1 Introduction
2012-04-11 PUBLIC 554
stack systems is no longer supported Furthermore as of SAP Business Suite 7i2011 it will no longer
be possible to upgrade an SAP dual-stack system to a higher release
Since the dual-stack split procedure is only available for SAP NetWeaver 70 systems we recommend
that you split your SAP dual-stack system before you perform an upgrade to one of the following
releases
SAP NetWeaver 73
SAP NetWeaver 73 including Enhancement Package 1
If your system is an SAP Business Suite 7i2011 dual-stack system we strongly recommend that
you perform a dual-stack split as it is no longer possible to upgrade to a higher release
For more information see SAP Note 1655335
If you no longer need the Java stack of your dual-stack system you can remove it as described in
Removing the Java Stack [page 46]
Constraints
You need to consider some constraints before you start splitting your SAP dual-stack system
The dual-stack split procedure does not support the splitting of the following
SAP NetWeaver Process Integration systems
SAP Solution Manager systems
The dual-stack split procedure does not implicate the following
Prerequisites Checker
Host agent
Diagnostics agent
Dialog instances
You can ignore sections in the installation documentation that focus on these options
NOTE
If these options are installed on your SAP dual-stack system and you want to use them on
the Java system after the split you need to install them again on the Java system using the
Installation Master DVD that you used to install your dual-stack system
The migration of the operating system or the database platform during the split is not supported
Naming Conventions
SAP system refers to SAP NetWeaver system or SAP system based on SAP NetWeaver
Dual-stack system refers to SAP NetWeaver ABAP+Java system or SAP ABAP+Java system based on SAP
NetWeaver
11 SAP Notes for the Dual-Stack Split
You must read the following SAP Notes before you start the dual-stack split These SAP Notes contain
the most recent information on the dual-stack split as well as corrections to the dual-stack split
1 Introduction
11 SAP Notes for the Dual-Stack Split
654 PUBLIC 2012-04-11
documentation Make sure that you have the most up-to-date version of each SAP Note which you
can find at httpservicesapcomnotes
SAP Notes for the Dual-Stack Split
SAP Note Number Title Description
1685432 Dual-Stack Split 20 SP1 for Systems Based on SAP NetWeaver
Problems discovered after the publication of the dual-stack split guide
1655335 Use Cases for Splitting Dual-Stack Systems mdash
12 Accessing the SAP Library
The references to the SAP NetWeaver Library documentation in this dual-stack split guide always
refer to the following on SAP Help Portal
SAP NetWeaver 70
httphelpsapcomnw70 Application Help SAP Library English SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 1
httphelpsapcomnw701 Application Help SAP Library English SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 2
httphelpsapcomnw702 Application Help SAP Library English SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 3
httphelpsapcomnw703 Application Help SAP Library English SAP NetWeaver
13 How to Use this Guide
This documentation comprises the description of the dual-stack split procedure and dual-stack-split-
specific steps For general or installation-specific information see the installation documentation
relevant for your release which you can find at httpservicesapcominstguides
Procedure
1 You decide on the split option that you want to use The following split options are available for
central distributed and high-availability systems
ldquoMove Java Databaserdquo (non-MCOD)
ldquoKeep Databaserdquo (MCOD)
For more information see Split Options Covered by this Guide [page 9]
2 You follow the list of steps at the beginning of each phase
Planning [page 13]
Preparation [page 17]
Splitting [page 21]
Follow-up Activities [page 33]
1 Introduction
12 Accessing the SAP Library
2012-04-11 PUBLIC 754
This page is left blank for documents that are printed on both sides
2 Split Options Covered by this Guide
This section shows the split options covered by this guide You have to decide which option you want
to use because the steps you have to perform vary according to the split option that you choose
Move Java Database [page 9]
Keep Database [page 11]
21 Split Option Move Java Database
The split option ldquoMove Java Databaserdquo offers the possibility to split a dual-stack system into one ABAP
system and one Java system each with its own database (non-MCOD)
Move Java Database for Central Systems
When you choose the ldquoMove Java Databaserdquo option for a central system SAPinst exports the Java stack
of the dual-stack system and uses this export to reinstall all main instances on a single host This equates
to an installation of a central system
These are the following instances
Central instance (CI)
Central services instance for Java (SCS)
Database instance (DB)
NOTE
If required you can install the central instance and the central services instance on the ABAP
system host again
Once the installation has finished and after the System Landscape Directory has been reconfigured
SAPinst removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
2012-04-11 PUBLIC 954
Figure 1 Split Option Move Java Database for Central Systems
Move Java Database for Distributed System
When you choose the ldquoMove Java Databaserdquo option for a distributed system SAPinst exports the Java
stack of the dual-stack system and uses this export to reinstall the main instances on several hosts
Every instance can run on a separate host This equates to an installation of a distributed system
These are the following instances
Central instance (CI)
Central services instance for Java (SCS)
Database instance (DB)
NOTE
If required you can reinstall the central instance and the central services instance on the ABAP
system hosts
After the installation has finished and the System Landscape Directory has been reconfigured SAPinst
removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
1054 PUBLIC 2012-04-11
Figure 2 Split Option Move Java Database for Distributed System
22 Split Option Keep Database
The split option ldquoKeep Databaserdquo offers the possibility for the Java system to reuse the existing database
of the dual-stack system using MCOD (multiple components ndash one database)
Keep Database for Central and Distributed Systems
When you choose the ldquoKeep Databaserdquo option SAPinst exports the Java file system on the dual-stack
system It uses this export to reinstall a central services instance (SCS) and a central instance (CI) for
Java They can be installed on one host on different hosts or on the source system hosts again
Additionally SAPinst adapts the Java schema of the database of the dual-stack system to the target Java
system
After the installation has finished and the System Landscape Directory has been reconfigured SAPinst
removes all Java parts from the dual-stack system except the Java database schema
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-04-11 PUBLIC 1154
Figure 3 Split Option Keep Database for Central Systems
Figure 4 Split Option Keep Database for Distributed Systems
2 Split Options Covered by this Guide
22 Split Option Keep Database
1254 PUBLIC 2012-04-11
3 Planning
31 Planning Checklist
This section includes the planning steps that you have to perform when you want to install the new
Java system on one or more hosts Perform the planning steps according to the split option and your
system variant
NOTE
Most of the required planning steps listed in this section are not described in this documentation
You can find the detailed description in the SAP NetWeaver Application Server Java installation
documentation relevant for your release at httpservicesapcominstguides
Prerequisites
You have decided on your split option [page 9]
Split Option ldquoMove Java Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
1 You check the hardware and software requirements for the Java installation host
For more information see Hardware and Software Requirements in the installation documentation of
your release
2 You read about user management [page 15]
3 You identify basic SAP system installation parameters
For more information see Basic SAP System Parameters in the installation documentation of your
release
Be aware of the following dual-stack-split-specific deviations
SAP System Parameters
User management
We do not recommend that you make modifications in the user management settings
For more information see User Management [page 15]
System Landscape Directory (SLD)
You can ignore SLD parameters
Only valid for Oracle |
SAP System Database Parameters Java database schema
We recommend that you choose a schema ID that is different from your SAP system ID
It might cause problems when you copy a system if ltSCHEMA_IDgt is the same as ltSAPSIDgt and
the database-specific method used for the copy does not allow you to rename the database
3 Planning
31 Planning Checklist
2012-04-11 PUBLIC 1354
schemes In certain situations you might create a system copy with a new ltSAPSIDgt but where
the database schema has the old ltSAPSIDgt This is not a technical problem but might be
confusing to the system administratorEnd of Oracle |
4 Only valid for MaxDB |
You plan your system configuration
For more information see System Configuration in the installation documentation of your releaseEnd of MaxDB |
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
You plan the setup of your database carefully
For more information see Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
7 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 43]
8 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
9 Only valid for IBM DB2 for zOS |
If you want to execute a Software Life-Cycle Option with SAPinst in an SAP system with thick client
connectivity see Special Considerations Regarding Connectivity for Software Life-Cycle Options in the installation
documentation of your releaseEnd of IBM DB2 for zOS |
10 Only valid for IBM DB2 for i5OS |
Optionally you decide whether you want to install multiple SAP systems on a single host
For more information see Multiple SAP Systems on a Single Host in the installation documentation of
your releaseEnd of IBM DB2 for i5OS |
11 You can continue with Preparation [page 17]
Split Option ldquoKeep Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
1 You check the hardware and software requirements for the Java installation host
For more information see Hardware and Software Requirements in the installation documentation of
your release
2 You read about user management [page 15]
3 You identify basic SAP system installation parameters
For more information see Basic SAP System Parameters in the installation documentation of your
release
3 Planning
31 Planning Checklist
1454 PUBLIC 2012-04-11
Be aware of the following dual-stack-split-specific deviation for SAP System Parameters
User management
We do not recommend that you make modifications in the user management settings For
more information see User Management [page 15]
System Landscape Directory (SLD)
You can ignore SLD parameters
4 Only valid for IBM DB2 for zOSMaxDB |
You plan your system configuration
For more information see System Configuration in the installation documentation of your releaseEnd of IBM DB2 for zOSMaxDB |
5 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
6 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 43]
7 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
8 Only valid for IBM DB2 for zOS |
If you want to execute a Software Life-Cycle Option with SAPinst in an SAP system with thick client
connectivity see Special Considerations Regarding Connectivity for Software Life-Cycle Options in the installation
documentation of your releaseEnd of IBM DB2 for zOS |
9 Only valid for IBM DB2 for i5OS |
Optionally you decide whether you want to install multiple SAP systems on a single host
For more information see Multiple SAP Systems on a Single Host in the installation documentation of
your releaseEnd of IBM DB2 for i5OS |
10 You can continue with Preparation [page 17]
32 User Management
The dual-stack split procedure does not change the user management and you cannot choose which
kind of user management you want to use for the target AS Java system That is the separated Java
system and the ABAP system both use the user management of the former dual-stack system The
following is possible
If the dual-stack system uses AS ABAP as data source for the User Management Engine (UME)
after the split the separated Java stack will also use the ABAP UME
If the dual-stack system uses an LDAP directory as source for user data this is also valid for the Java
stack
3 Planning
32 User Management
2012-04-11 PUBLIC 1554
In both cases manual configuration is not required
We do not recommend that you make modifications to the user management settings
For more information see SAP Note 718383
3 Planning
32 User Management
1654 PUBLIC 2012-04-11
4 Preparation
41 Preparation Checklist
This section includes the preparation steps that you have to perform when you want to install the new
Java system on one or more hosts
NOTE
Most of the required preparation steps listed in this section are not described in this
documentation You can find the detailed description in the SAP NetWeaver Application Server
Java installation documentation relevant for your release at httpservicesapcom
instguides
1 Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
You make sure that the required operating system users and groups are created
To create the groups and users automatically run the Dual-Stack Split Tool on the host where
the SAP Java system is to be installed and choose Dual-Stack Split Operating System Users and
Groups
For more information see Creating Operating System Users and Groups in the installation documentation
of your releaseEnd of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
2 You set up file systems and make sure that the required disk space is available for the directories
to be created during the installation
For more information see Setting Up File Systems for a High-Availability System in the installation
documentation of your release
3 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
4 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
If you want to install a high-availability system you perform switchover preparations
For more information see Performing Switchover Preparations for High-Availability in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
5 If you want to share the transport directory trans from another system you export this directory
to your installation hosts
For more information see Exporting and Mounting the Global Transport Directory in the installation
documentation of your release
4 Preparation
41 Preparation Checklist
2012-04-11 PUBLIC 1754
6 You install the Java Development Kit This step is not required if you have installed the SAP JVM
4 on your source system
For more information see Installing the Java Development Kit in the installation documentation of your
release
7 You make sure that the required installation media are available on each host
You can download the Dual-Stack Split Tool at httpservicesapcomsltoolset
Software Logistics Toolset 10 Dual-Stack Split
You can download the Java stack and database installation media from SAP Service
Marketplace as described in Preparing the Installation Media in the installation documentation of
your release
NOTE
The release level required for the installation corresponds to the release level of your dual-
stack system
The following table shows the required installation media for the dual-stack split
SAP Instance Installation Required Media
Central services instance central instance
Dual-Stack Split Tool Java DVD RDBMS Client DVD
Move Java Database only Database instance
Dual-Stack Split Tool Java DVD Only valid for MS SQL ServerOracle |
RDBMS DVDEnd of MS SQL ServerOracle |
Only valid for MS SQL ServerOracle |
RDBMS Patch DVD (if available)End of MS SQL ServerOracle |
8 Only valid for HA (MSCS) |
To install a high-availability system with Microsoft Cluster Service (MSCS) you also perform the
MSCS-specific preparation tasks as described in the installation documentation of your releaseEnd of HA (MSCS) |
9 Only valid for HA (MSCS) |
If you choose the split option ldquoKeep Databaserdquo with the scenario ldquoKeep SCS on the Source Cluster
Systemrdquo you perform the following steps
You provide additional disk storage on the target cluster system
For more information see Distribution of SAP System Components to Disks for MSCS Directories in an
MSCS Configuration and IP Addresses in an MSCS Configuration in the installation documentation of
your release
You provide an additional IP address and an additional virtual host name for the Java system
For more information see Mapping Host Names to IP Addresses for MSCS in the installation
documentation of your releaseEnd of HA (MSCS) |
4 Preparation
41 Preparation Checklist
1854 PUBLIC 2012-04-11
10 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 19] of
the dual-stack system
11 You can continue with Splitting [page 21]
42 Performing a Full System Backup
If you decided to use the split option ldquoKeep Databaserdquo you must perform a full system backup of the
dual-stack system or at least a backup of the Java database schema before you start the split procedure
If you decided to use the split option ldquoMove Java Databaserdquo you do not need to perform a backup before
you start the split procedure
For more information about backing up your database see the database-specific backup and recovery
documentation in the SAP Library [page 7] at
SAP MaxDB
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for SAP
MaxDB
Oracle
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Oracle
IBM DB2 for i5OS
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 UDB for iSeries
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for i
4 Preparation
42 Performing a Full System Backup
2012-04-11 PUBLIC 1954
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
i
IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX
and Windows
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
Linux UNIX and Windows
IBM DB2 for zOS
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 UDB for zOS
SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for DB2 for z
OS
Microsoft SQL Server
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Microsoft SQL
Server
4 Preparation
42 Performing a Full System Backup
2054 PUBLIC 2012-04-11
5 Splitting
51 Splitting Checklist
This section includes the splitting steps that you have to perform for the following split options
ldquoMove Java Databaserdquo
ldquoKeep Databaserdquo
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Only valid for Oracle |
You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 You export the Java stack using SAPinst [page 23]
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
4 You restart the source system
5 You run SAPinst [page 23] to install a Java only system using the export from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2012-04-11 PUBLIC 2154
Distributed System
1 Only valid for Oracle |
On the database instance host of the dual-stack system you install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes on the database instance host
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 On the database instance host of the dual-stack system you run SAPinst [page 23] to export the
Java database schema
4 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the Java
parts of the file system of the central instance
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
5 You restart the source system
6 You run SAPinst [page 23] to install a central services instance for the Java target system
7 You run SAPinst [page 23] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
9 You continue with Follow-Up Activities [page 33]
Keep Database
1 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the
file system of the central instance
5 Splitting
51 Splitting Checklist
2254 PUBLIC 2012-04-11
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you wont use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
2 You restart the source system
3 You run SAPinst [page 23] to install a central services instance for the Java target system
4 On the database instance host of the dual-stack system you run SAPinst [page 23] to adapt the
database for the Java target system
NOTE
Make sure that you enter the profile directory of the Java target system in the SAP System gt
General Parameters screen
5 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
52 Running SAPinst
This section describes how to run the installation tool SAPinst SAPinst includes a GUI client and a GUI
server which both use Java
The procedure describes an installation where SAPinst GUI client and GUI server are running on the
same host In the following GUI client and GUI server are addressed as ldquoSAPinst GUIrdquo
If you need to see the installation on a remote display we recommend that you perform a remote
installation with SAPinst where the SAPinst GUI is running on a separate host from SAPinst For more
information see Performing a Remote Installation with SAPinst in the installation documentation of your
release
Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote
access to SAPinst GUI on Windows workstations For more information see SAP Note 1170809
Useful Information About SAPinst
When you start SAPinst it automatically starts the SAPinst GUI
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2354
SAPinst creates the installation directory sapinst_instdir directly below the temporary directory
SAPinst 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 SAPinst
creates the installation directory sapinst_instdir directly below the tmp directory by default
If you want SAPinst to create the installation directory sapinst_instdir in another directory set
the environment variable TEMP to this directory before you start SAPinst
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
Only valid for IBM DB2 for i5OS |
NOTE
When you leave your Qp2Term session all changes of the environment variables done by the
command export are reverted
End of IBM DB2 for i5OS |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
SAPinst creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt
SAPinst extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is located
in the environment variables TEMP TMP or TMPDIR These files are deleted after SAPinst has stopped
running
The temporary directory sapinst_exexxxxxxxxxx sometimes remains undeleted You can safely
delete it
The temporary directory also contains the log file dev_selfexout from the extraction process
which might be useful if an error occurs
CAUTION
If SAPinst cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default ports 21200 21212 and 4239 are used for communication
between SAPinst GUI server GUI and HTTP server as follows
SAPinst uses port 21200 to communicate with the GUI server
The GUI server uses port 21212 to communicate with the GUI client
5 Splitting
52 Running SAPinst
2454 PUBLIC 2012-04-11
4239 is the port of the HTTP server which is part of the GUI server
If the ports for SAPinst and the GUI server are already in use SAPinst automatically searches for
free port numbers If the search fails SAPinst exits
In this case or if you want SAPinst to use specific ports you can assign them by executing the
sapinst executable with the following command line parameters
SAPINST_DIALOG_PORT=ltport_number_sapinst_to_gui_servergt
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
GUISERVER_HTTP_PORT=ltport_number_http_servergt
To see a list of all available SAPinst properties start SAPinst as described above with command line
parameter -p
sapinst -p
If you need to run SAPinst in accessibility mode proceed as described in Running SAPinst in Accessibility
Mode in the installation documentation of your release
If required you can stop SAPinst by choosing SAPinst Cancel in the SAPinst GUI menu
Prerequisites
We recommend that you use the csh shell for the installation with SAPinst If you want to use
another shell make sure that you have first read SAP Note 202227
SAPinst uses csh scripts during the installation to obtain the environment for user ltsapsidgtadm
This is also true if user ltsapsidgtadm already exists from an earlier SAP system installation and the
shell of this user is not csh Before you start SAPinst execute the following command as user
ltsapsidgtadm to make sure that the csh scripts are up-to-date
bincsh -c source lthome directory of ltsapsidgtadmgtcshrcenv
Make sure that you have specified the most important SAP system parameters as described in Basic
SAP System Installation Parameters in the installation documentation of your release before you start
SAPinst
Only valid for IBM DB2 for zOS |
Check that your installation hosts meet the requirements for the installation options that you
want to installEnd of IBM DB2 for zOS |
Only valid for Non-Standalone Engines and Clients |
If you want to perform a distributed or a high-availability installation make sure that you have
exported and mounted global directories For more information see Exporting and Mounting Global
Directories in the installation documentation of your releaseEnd of Non-Standalone Engines and Clients |
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you have carefully planned your database layout in particular the tablespace layout
as described in Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2554
Only valid for AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for Solaris |
Solaris SPARC onlyEnd of Solaris |
If you want to set up DB2s high-availability cluster solution SA MP make sure that you have read
the document IBM DB2 High Availability Solution IBM Tivoli System Automation for Multiplatforms at
httpservicesapcominstguidesnw70 Installation Installation ndash SAP NetWeaver SystemsEnd of AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for zOS |
First make sure that you have installed DB2 for zOS For information on that installation see
SAP DBA Guide DB2 for zOS DB2 Setup especially the section Stored Procedures EnablementEnd of IBM DB2 for zOS |
Check the value of the environment variable TEMP TMP or TMPDIR
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
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 ndash for example by using a crontab entry
Make sure that you have at least 60 MB of free space in the installation directory for each
installation option In addition you need 200 MB free space for the SAPinst executables If you
cannot provide 200 MB free space in the temporary directory you can set one of the
environment variables TEMP TMP or TMPDIR to another directory with 200 MB free space for
the SAPinst executables
Make sure that the temporary directory has the permissions 777
Only valid for IBM DB2 for zOS |
Make sure that your database is up and runningEnd of IBM DB2 for zOS |
Make sure that your DISPLAY environment variable is set to lthost_namegt00 where
lthost_namegt is the host on which you want to display the GUI
Shell Used Command
Bourne shell (sh) DISPLAY=lthost_namegt00
export DISPLAY
C shell (csh) setenv DISPLAY lthost_namegt00
Korn shell (ksh) export DISPLAY=lthost_namegt00
Make sure that umask is set to 022 for user root
As user root enter the following command umask 022
Check the following values for user root
5 Splitting
52 Running SAPinst
2654 PUBLIC 2012-04-11
In csh execute limit
Output Properties
cputime unlimited
filesize unlimited
datasize unlimited
stacksize 8192 KB
coredumpsize unlimited
descriptors 8192
memorysize unlimited
In sh or ksh execute ulimit -a
Output Properties
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192
coredump(blocks) unlimited
nofiles(descriptors) 8192
memory(KBytes) unlimited
If your parameter settings differ from those above change these values accordingly
EXAMPLE
If you have to change the value for descriptors to 8192 proceed as follows
In csh execute
limit descriptors 8192
In sh or ksh execute
ulimit -n 8192
Before you start SAPinst read SAP Note 1697164 for more information about which user to choose
for running the SAPinst SDT GUI server
Procedure
1 Log on to the installation host as user root
CAUTION
Do not use an existing ltsapsidgtadm user
Only valid for Non-Standalone Engines and Clients |
CAUTION
Make sure that the root user has not set any environment variables for a different SAP system
or database
End of Non-Standalone Engines and Clients |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2754
2 Make the Dual-Stack Split Tool available on the installation host Make sure that it is available
locally We do not recommend that you use Network File System (NFS) because reading from
media mounted with NFS might fail
For more information see Preparation Checklist [page 17] and Preparing the Installation Media in the
installation documentation of your release
3 Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
Only valid for Non-Standalone Engines and Clients |
Change to the directory with the sapinst executable for your operating system by entering the
following command cd ltMountpoint of Installation Master mediumgtDATA_UNITS
ltproductgt_IM_ltOSgtEnd of Non-Standalone Engines and Clients |
End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
4 Start SAPinst by executing the following command sapinst
NOTE
If you want to use a virtual host name start SAPinst with the SAPinst property
SAPINST_USE_HOSTNAME as follows
Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
sapinst SAPINST_USE_HOSTNAME=ltvirtual host namegt
End of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
5 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
In addition if you want to use the split option ldquoMove Java Databaserdquo choose ltYour System
Variantgt
Perform the export and installation steps exactly in the order in which they appear
6 Only valid for Non-Standalone Engines and Clients |
Choose NextEnd of Non-Standalone Engines and Clients |
7 Follow the instructions in the SAPinst input screens and enter the required parameters
NOTE
If SAPinst asks for the Java DVD make sure that you provide a Java DVD with the same
release level as your dual-stack system
For more information about the input parameters position the cursor on the parameter
and press F1
After you have entered all requested input parameters SAPinst displays the Parameter Summary screen
This screen shows both the parameters that you entered and those that SAPinst set by default If
required you can revise the parameters before starting the split procedure
5 Splitting
52 Running SAPinst
2854 PUBLIC 2012-04-11
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you check the following parameters depending on the installation type that you
have chosenEnd of IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for Linux and UNIX and Windows |
If you are performing a typical installation SAPinst creates four sapdata directories by
default If you require more or fewer sapdata directories depending on the storage devices
you are using you must change this parameter before you start the installation By selecting
this parameter on the Summary screen and choosing Revise SAPinst returns to the IBM DB2 for
Linux UNIX and Windows ndashgt Sapdata Directories screen
On this screen you can also decide if you want SAPinst to create the regular table and index
tablespaces with DB2s automatic storage management enabled By default the option for
automatic storage management is preselected
NOTE
As of DB2 V91 and higher the database and the SYSCATSPACE tablespace are always created
with automatic storage management enabled even if you deselect this option on the
dialog IBM DB2 for Linux UNIX and Windows gt Sapdata Directories
For more information about DB2s automatic storage management see section DB2
Tablespaces in the installation documentation of your SAP product
If you are performing a custom installation you set these parameters during the Define
Parameters phase of SAPinst
NOTE
If the tablespace layout used by SAPinst does not meet your requirements you can create
the tablespaces manually by deselecting the option Create Tablespaces with SAPinst on the
IBM DB2 for Linux and UNIX and Windows Sapdata Directories screen
During the installation phase SAPinst then displays the following message
You must create the tablespaces now To do so use the
createTablespacessql script that is located in your installation
directory
To continue the installation choose OK Alternatively you can cancel
SAPinst here and restart it again
SAPinst does not check the page size of tablespaces that have either been created manually
or that already exist If you create the tablespaces manually you must make sure that
you use a page size of 16 KBEnd of IBM DB2 for Linux and UNIX and Windows |
8 To start the dual-stack split choose Start
SAPinst starts and displays the progress of the split procedure
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2954
When the split option has finished successfully SAPinst displays the message Execution of
ltOption_Namegt has completed
Only valid for Oracle |
NOTE
When installing the Oracle database instance SAPinst stops the installation and prompts
you to install the Oracle database software For more information see Installing the Oracle
Database Software in the installation documentation of your release
After you have finished the installation of the Oracle database you continue the database
instance installation by choosing OK in the GUI of the database instance installation
Check SAP Note 1431800 for technical information about Oracle Release 112 in SAP
environments
End of Oracle |
Only valid for Enterprise Portal (EP) |
NOTE
During the final restart of Application Server Java performed by SAPinst the portal starts the
processing and uploading of the new portal archives It takes approximately 15 to 90 minutes
before the deployment is completed and the portal is launched
Do not stop SAPinst or Application Server Java during this phase
End of Enterprise Portal (EP) |
9 If required delete directories with the name sapinst_exexxxxxxxxxx after SAPinst has finished
Sometimes these remain in the temporary directory
NOTE
If there are errors with the SAPinst extraction process you can find the log file
dev_selfexout in the temporary directory
Only valid for Non-Standalone Engines and Clients |
RECOMMENDATION
Keep all installation 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 installation 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 installation directories on installation hosts but make sure
that you delete them after saving them separately
End of Non-Standalone Engines and Clients |
10 We recommend that you delete the directory ltuser_homegtsdtgui
11 Only valid for IBM DB2 for Linux and UNIX and Windows |
If not already done install the DB2 license
5 Splitting
52 Running SAPinst
3054 PUBLIC 2012-04-11
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
End of IBM DB2 for Linux and UNIX and Windows |
12 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 3154
This page is left blank for documents that are printed on both sides
6 Follow-Up Activities
61 Follow-Up Activities Checklist
This section includes the follow-up activities that you have to perform for the following split options
ldquoMove Java Databaserdquo for a central system
ldquoMove Java Databaserdquo for a distributed system or a high-availability system
ldquoKeep Databaserdquo for a central distributed or high-availability system
NOTE
Some of the follow-up activities listed in this section are not described in this documentation You
can find the detailed description in the SAP NetWeaver Application Server Java system copy
documentation relevant for your release at
httpservicesapcominstguides
Move Java Database
Central System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3354
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
7 We recommend that you perform regression testing
8 On the source system you run SAPinst [page 23] to remove the Java parts in the file system and in
the database
9 On the source system you call transaction RZ10 to reimport the profiles from the file system
10 In the Transport Management System (TMS) you configure the transport routes [page 38]
11 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
12 You clean up the system landscape data [page 40]
Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3454 PUBLIC 2012-04-11
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the database host of the source system you run SAPinst [page 23] to remove the Java database
schema
12 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
13 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
14 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
15 You clean up the system landscape data [page 40]
Keep Database
Central Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3554
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
12 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
13 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
14 You clean up the system landscape data [page 40]
62 Maintaining the Connection to the System Landscape Directory
After installing the Java system you need to reconfigure the connection between the System Landscape
Directory (SLD) the source system and the target system The steps required differ depending on
whether you use a local or a central SLD To maintain the connection to the SLD you can either run
the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split or perform the required steps manually as described below
NOTE
This step is only required if the connection to the SLD was established on the source system before
the split
Prerequisites
If you want to use the configuration wizard you need an SAP NetWeaver Java system 70 Support
Package 14 or higher in your landscape
SLDAPIUSER credentials are available in the ABAP system
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3654 PUBLIC 2012-04-11
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
1 Introduction
This document explains how to use the Dual-Stack Split 20 tool to split a dual-stack (ABAP+Java)
system into one ABAP and one Java stack each with its own system ID This tool is part of the installation
tool SAPinst and it mainly uses the Java system copy functionality It is delivered as part of Support
Package 4 of the Software Logistics Toolset (SL Toolset) 10
The dual-stack split procedure is valid for SAP dual-stack systems based on the following SAP NetWeaver
release levels
SAP NetWeaver 70 SP14 or higher
SAP NetWeaver 70 including Enhancement Package 1
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver 70 including Enhancement Package 3
The procedure described in this guide mainly applies to splitting a single SAP dual-stack system For
more information about splitting systems within a system landscape see Splitting Within a System
Landscape [page 43]
Definitions
Dual-Stack System
A dual-stack system is an SAP system that contains installations of both SAP NetWeaver Application
Server ABAP and SAP NetWeaver Application Server Java It has the following characteristics
Common SAP system ID for its ABAP and Java stacks
Common startup framework
Common database (with different schemes for ABAP and Java)
Dual-Stack Split
While splitting-off the Java part of a dual-stack system into a separate system the dual-stack system is
reduced to an ABAP system To do this the Dual-Stack Split Tool runs a system copy and uses the Java
system copy export to reinstall the Java system separately and with a new SAP system ID The ABAP
stack of the former dual-stack system is not affected by this procedure The separated systems can either
use their own databases (see Split Option Move Java Database [page 9]) or both use the existing database
in the ABAP system (see Split Option Keep Database [page 11])
Use Case
As of SAP NetWeaver 70 including Enhancement Package 3 and SAP Business Suite 7i2011 which
is based on SAP NetWeaver 70 including Enhancement Package 3 the installation of SAP dual-
1 Introduction
2012-04-11 PUBLIC 554
stack systems is no longer supported Furthermore as of SAP Business Suite 7i2011 it will no longer
be possible to upgrade an SAP dual-stack system to a higher release
Since the dual-stack split procedure is only available for SAP NetWeaver 70 systems we recommend
that you split your SAP dual-stack system before you perform an upgrade to one of the following
releases
SAP NetWeaver 73
SAP NetWeaver 73 including Enhancement Package 1
If your system is an SAP Business Suite 7i2011 dual-stack system we strongly recommend that
you perform a dual-stack split as it is no longer possible to upgrade to a higher release
For more information see SAP Note 1655335
If you no longer need the Java stack of your dual-stack system you can remove it as described in
Removing the Java Stack [page 46]
Constraints
You need to consider some constraints before you start splitting your SAP dual-stack system
The dual-stack split procedure does not support the splitting of the following
SAP NetWeaver Process Integration systems
SAP Solution Manager systems
The dual-stack split procedure does not implicate the following
Prerequisites Checker
Host agent
Diagnostics agent
Dialog instances
You can ignore sections in the installation documentation that focus on these options
NOTE
If these options are installed on your SAP dual-stack system and you want to use them on
the Java system after the split you need to install them again on the Java system using the
Installation Master DVD that you used to install your dual-stack system
The migration of the operating system or the database platform during the split is not supported
Naming Conventions
SAP system refers to SAP NetWeaver system or SAP system based on SAP NetWeaver
Dual-stack system refers to SAP NetWeaver ABAP+Java system or SAP ABAP+Java system based on SAP
NetWeaver
11 SAP Notes for the Dual-Stack Split
You must read the following SAP Notes before you start the dual-stack split These SAP Notes contain
the most recent information on the dual-stack split as well as corrections to the dual-stack split
1 Introduction
11 SAP Notes for the Dual-Stack Split
654 PUBLIC 2012-04-11
documentation Make sure that you have the most up-to-date version of each SAP Note which you
can find at httpservicesapcomnotes
SAP Notes for the Dual-Stack Split
SAP Note Number Title Description
1685432 Dual-Stack Split 20 SP1 for Systems Based on SAP NetWeaver
Problems discovered after the publication of the dual-stack split guide
1655335 Use Cases for Splitting Dual-Stack Systems mdash
12 Accessing the SAP Library
The references to the SAP NetWeaver Library documentation in this dual-stack split guide always
refer to the following on SAP Help Portal
SAP NetWeaver 70
httphelpsapcomnw70 Application Help SAP Library English SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 1
httphelpsapcomnw701 Application Help SAP Library English SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 2
httphelpsapcomnw702 Application Help SAP Library English SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 3
httphelpsapcomnw703 Application Help SAP Library English SAP NetWeaver
13 How to Use this Guide
This documentation comprises the description of the dual-stack split procedure and dual-stack-split-
specific steps For general or installation-specific information see the installation documentation
relevant for your release which you can find at httpservicesapcominstguides
Procedure
1 You decide on the split option that you want to use The following split options are available for
central distributed and high-availability systems
ldquoMove Java Databaserdquo (non-MCOD)
ldquoKeep Databaserdquo (MCOD)
For more information see Split Options Covered by this Guide [page 9]
2 You follow the list of steps at the beginning of each phase
Planning [page 13]
Preparation [page 17]
Splitting [page 21]
Follow-up Activities [page 33]
1 Introduction
12 Accessing the SAP Library
2012-04-11 PUBLIC 754
This page is left blank for documents that are printed on both sides
2 Split Options Covered by this Guide
This section shows the split options covered by this guide You have to decide which option you want
to use because the steps you have to perform vary according to the split option that you choose
Move Java Database [page 9]
Keep Database [page 11]
21 Split Option Move Java Database
The split option ldquoMove Java Databaserdquo offers the possibility to split a dual-stack system into one ABAP
system and one Java system each with its own database (non-MCOD)
Move Java Database for Central Systems
When you choose the ldquoMove Java Databaserdquo option for a central system SAPinst exports the Java stack
of the dual-stack system and uses this export to reinstall all main instances on a single host This equates
to an installation of a central system
These are the following instances
Central instance (CI)
Central services instance for Java (SCS)
Database instance (DB)
NOTE
If required you can install the central instance and the central services instance on the ABAP
system host again
Once the installation has finished and after the System Landscape Directory has been reconfigured
SAPinst removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
2012-04-11 PUBLIC 954
Figure 1 Split Option Move Java Database for Central Systems
Move Java Database for Distributed System
When you choose the ldquoMove Java Databaserdquo option for a distributed system SAPinst exports the Java
stack of the dual-stack system and uses this export to reinstall the main instances on several hosts
Every instance can run on a separate host This equates to an installation of a distributed system
These are the following instances
Central instance (CI)
Central services instance for Java (SCS)
Database instance (DB)
NOTE
If required you can reinstall the central instance and the central services instance on the ABAP
system hosts
After the installation has finished and the System Landscape Directory has been reconfigured SAPinst
removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
1054 PUBLIC 2012-04-11
Figure 2 Split Option Move Java Database for Distributed System
22 Split Option Keep Database
The split option ldquoKeep Databaserdquo offers the possibility for the Java system to reuse the existing database
of the dual-stack system using MCOD (multiple components ndash one database)
Keep Database for Central and Distributed Systems
When you choose the ldquoKeep Databaserdquo option SAPinst exports the Java file system on the dual-stack
system It uses this export to reinstall a central services instance (SCS) and a central instance (CI) for
Java They can be installed on one host on different hosts or on the source system hosts again
Additionally SAPinst adapts the Java schema of the database of the dual-stack system to the target Java
system
After the installation has finished and the System Landscape Directory has been reconfigured SAPinst
removes all Java parts from the dual-stack system except the Java database schema
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-04-11 PUBLIC 1154
Figure 3 Split Option Keep Database for Central Systems
Figure 4 Split Option Keep Database for Distributed Systems
2 Split Options Covered by this Guide
22 Split Option Keep Database
1254 PUBLIC 2012-04-11
3 Planning
31 Planning Checklist
This section includes the planning steps that you have to perform when you want to install the new
Java system on one or more hosts Perform the planning steps according to the split option and your
system variant
NOTE
Most of the required planning steps listed in this section are not described in this documentation
You can find the detailed description in the SAP NetWeaver Application Server Java installation
documentation relevant for your release at httpservicesapcominstguides
Prerequisites
You have decided on your split option [page 9]
Split Option ldquoMove Java Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
1 You check the hardware and software requirements for the Java installation host
For more information see Hardware and Software Requirements in the installation documentation of
your release
2 You read about user management [page 15]
3 You identify basic SAP system installation parameters
For more information see Basic SAP System Parameters in the installation documentation of your
release
Be aware of the following dual-stack-split-specific deviations
SAP System Parameters
User management
We do not recommend that you make modifications in the user management settings
For more information see User Management [page 15]
System Landscape Directory (SLD)
You can ignore SLD parameters
Only valid for Oracle |
SAP System Database Parameters Java database schema
We recommend that you choose a schema ID that is different from your SAP system ID
It might cause problems when you copy a system if ltSCHEMA_IDgt is the same as ltSAPSIDgt and
the database-specific method used for the copy does not allow you to rename the database
3 Planning
31 Planning Checklist
2012-04-11 PUBLIC 1354
schemes In certain situations you might create a system copy with a new ltSAPSIDgt but where
the database schema has the old ltSAPSIDgt This is not a technical problem but might be
confusing to the system administratorEnd of Oracle |
4 Only valid for MaxDB |
You plan your system configuration
For more information see System Configuration in the installation documentation of your releaseEnd of MaxDB |
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
You plan the setup of your database carefully
For more information see Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
7 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 43]
8 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
9 Only valid for IBM DB2 for zOS |
If you want to execute a Software Life-Cycle Option with SAPinst in an SAP system with thick client
connectivity see Special Considerations Regarding Connectivity for Software Life-Cycle Options in the installation
documentation of your releaseEnd of IBM DB2 for zOS |
10 Only valid for IBM DB2 for i5OS |
Optionally you decide whether you want to install multiple SAP systems on a single host
For more information see Multiple SAP Systems on a Single Host in the installation documentation of
your releaseEnd of IBM DB2 for i5OS |
11 You can continue with Preparation [page 17]
Split Option ldquoKeep Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
1 You check the hardware and software requirements for the Java installation host
For more information see Hardware and Software Requirements in the installation documentation of
your release
2 You read about user management [page 15]
3 You identify basic SAP system installation parameters
For more information see Basic SAP System Parameters in the installation documentation of your
release
3 Planning
31 Planning Checklist
1454 PUBLIC 2012-04-11
Be aware of the following dual-stack-split-specific deviation for SAP System Parameters
User management
We do not recommend that you make modifications in the user management settings For
more information see User Management [page 15]
System Landscape Directory (SLD)
You can ignore SLD parameters
4 Only valid for IBM DB2 for zOSMaxDB |
You plan your system configuration
For more information see System Configuration in the installation documentation of your releaseEnd of IBM DB2 for zOSMaxDB |
5 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
6 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 43]
7 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
8 Only valid for IBM DB2 for zOS |
If you want to execute a Software Life-Cycle Option with SAPinst in an SAP system with thick client
connectivity see Special Considerations Regarding Connectivity for Software Life-Cycle Options in the installation
documentation of your releaseEnd of IBM DB2 for zOS |
9 Only valid for IBM DB2 for i5OS |
Optionally you decide whether you want to install multiple SAP systems on a single host
For more information see Multiple SAP Systems on a Single Host in the installation documentation of
your releaseEnd of IBM DB2 for i5OS |
10 You can continue with Preparation [page 17]
32 User Management
The dual-stack split procedure does not change the user management and you cannot choose which
kind of user management you want to use for the target AS Java system That is the separated Java
system and the ABAP system both use the user management of the former dual-stack system The
following is possible
If the dual-stack system uses AS ABAP as data source for the User Management Engine (UME)
after the split the separated Java stack will also use the ABAP UME
If the dual-stack system uses an LDAP directory as source for user data this is also valid for the Java
stack
3 Planning
32 User Management
2012-04-11 PUBLIC 1554
In both cases manual configuration is not required
We do not recommend that you make modifications to the user management settings
For more information see SAP Note 718383
3 Planning
32 User Management
1654 PUBLIC 2012-04-11
4 Preparation
41 Preparation Checklist
This section includes the preparation steps that you have to perform when you want to install the new
Java system on one or more hosts
NOTE
Most of the required preparation steps listed in this section are not described in this
documentation You can find the detailed description in the SAP NetWeaver Application Server
Java installation documentation relevant for your release at httpservicesapcom
instguides
1 Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
You make sure that the required operating system users and groups are created
To create the groups and users automatically run the Dual-Stack Split Tool on the host where
the SAP Java system is to be installed and choose Dual-Stack Split Operating System Users and
Groups
For more information see Creating Operating System Users and Groups in the installation documentation
of your releaseEnd of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
2 You set up file systems and make sure that the required disk space is available for the directories
to be created during the installation
For more information see Setting Up File Systems for a High-Availability System in the installation
documentation of your release
3 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
4 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
If you want to install a high-availability system you perform switchover preparations
For more information see Performing Switchover Preparations for High-Availability in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
5 If you want to share the transport directory trans from another system you export this directory
to your installation hosts
For more information see Exporting and Mounting the Global Transport Directory in the installation
documentation of your release
4 Preparation
41 Preparation Checklist
2012-04-11 PUBLIC 1754
6 You install the Java Development Kit This step is not required if you have installed the SAP JVM
4 on your source system
For more information see Installing the Java Development Kit in the installation documentation of your
release
7 You make sure that the required installation media are available on each host
You can download the Dual-Stack Split Tool at httpservicesapcomsltoolset
Software Logistics Toolset 10 Dual-Stack Split
You can download the Java stack and database installation media from SAP Service
Marketplace as described in Preparing the Installation Media in the installation documentation of
your release
NOTE
The release level required for the installation corresponds to the release level of your dual-
stack system
The following table shows the required installation media for the dual-stack split
SAP Instance Installation Required Media
Central services instance central instance
Dual-Stack Split Tool Java DVD RDBMS Client DVD
Move Java Database only Database instance
Dual-Stack Split Tool Java DVD Only valid for MS SQL ServerOracle |
RDBMS DVDEnd of MS SQL ServerOracle |
Only valid for MS SQL ServerOracle |
RDBMS Patch DVD (if available)End of MS SQL ServerOracle |
8 Only valid for HA (MSCS) |
To install a high-availability system with Microsoft Cluster Service (MSCS) you also perform the
MSCS-specific preparation tasks as described in the installation documentation of your releaseEnd of HA (MSCS) |
9 Only valid for HA (MSCS) |
If you choose the split option ldquoKeep Databaserdquo with the scenario ldquoKeep SCS on the Source Cluster
Systemrdquo you perform the following steps
You provide additional disk storage on the target cluster system
For more information see Distribution of SAP System Components to Disks for MSCS Directories in an
MSCS Configuration and IP Addresses in an MSCS Configuration in the installation documentation of
your release
You provide an additional IP address and an additional virtual host name for the Java system
For more information see Mapping Host Names to IP Addresses for MSCS in the installation
documentation of your releaseEnd of HA (MSCS) |
4 Preparation
41 Preparation Checklist
1854 PUBLIC 2012-04-11
10 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 19] of
the dual-stack system
11 You can continue with Splitting [page 21]
42 Performing a Full System Backup
If you decided to use the split option ldquoKeep Databaserdquo you must perform a full system backup of the
dual-stack system or at least a backup of the Java database schema before you start the split procedure
If you decided to use the split option ldquoMove Java Databaserdquo you do not need to perform a backup before
you start the split procedure
For more information about backing up your database see the database-specific backup and recovery
documentation in the SAP Library [page 7] at
SAP MaxDB
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for SAP
MaxDB
Oracle
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Oracle
IBM DB2 for i5OS
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 UDB for iSeries
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for i
4 Preparation
42 Performing a Full System Backup
2012-04-11 PUBLIC 1954
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
i
IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX
and Windows
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
Linux UNIX and Windows
IBM DB2 for zOS
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 UDB for zOS
SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for DB2 for z
OS
Microsoft SQL Server
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Microsoft SQL
Server
4 Preparation
42 Performing a Full System Backup
2054 PUBLIC 2012-04-11
5 Splitting
51 Splitting Checklist
This section includes the splitting steps that you have to perform for the following split options
ldquoMove Java Databaserdquo
ldquoKeep Databaserdquo
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Only valid for Oracle |
You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 You export the Java stack using SAPinst [page 23]
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
4 You restart the source system
5 You run SAPinst [page 23] to install a Java only system using the export from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2012-04-11 PUBLIC 2154
Distributed System
1 Only valid for Oracle |
On the database instance host of the dual-stack system you install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes on the database instance host
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 On the database instance host of the dual-stack system you run SAPinst [page 23] to export the
Java database schema
4 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the Java
parts of the file system of the central instance
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
5 You restart the source system
6 You run SAPinst [page 23] to install a central services instance for the Java target system
7 You run SAPinst [page 23] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
9 You continue with Follow-Up Activities [page 33]
Keep Database
1 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the
file system of the central instance
5 Splitting
51 Splitting Checklist
2254 PUBLIC 2012-04-11
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you wont use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
2 You restart the source system
3 You run SAPinst [page 23] to install a central services instance for the Java target system
4 On the database instance host of the dual-stack system you run SAPinst [page 23] to adapt the
database for the Java target system
NOTE
Make sure that you enter the profile directory of the Java target system in the SAP System gt
General Parameters screen
5 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
52 Running SAPinst
This section describes how to run the installation tool SAPinst SAPinst includes a GUI client and a GUI
server which both use Java
The procedure describes an installation where SAPinst GUI client and GUI server are running on the
same host In the following GUI client and GUI server are addressed as ldquoSAPinst GUIrdquo
If you need to see the installation on a remote display we recommend that you perform a remote
installation with SAPinst where the SAPinst GUI is running on a separate host from SAPinst For more
information see Performing a Remote Installation with SAPinst in the installation documentation of your
release
Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote
access to SAPinst GUI on Windows workstations For more information see SAP Note 1170809
Useful Information About SAPinst
When you start SAPinst it automatically starts the SAPinst GUI
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2354
SAPinst creates the installation directory sapinst_instdir directly below the temporary directory
SAPinst 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 SAPinst
creates the installation directory sapinst_instdir directly below the tmp directory by default
If you want SAPinst to create the installation directory sapinst_instdir in another directory set
the environment variable TEMP to this directory before you start SAPinst
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
Only valid for IBM DB2 for i5OS |
NOTE
When you leave your Qp2Term session all changes of the environment variables done by the
command export are reverted
End of IBM DB2 for i5OS |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
SAPinst creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt
SAPinst extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is located
in the environment variables TEMP TMP or TMPDIR These files are deleted after SAPinst has stopped
running
The temporary directory sapinst_exexxxxxxxxxx sometimes remains undeleted You can safely
delete it
The temporary directory also contains the log file dev_selfexout from the extraction process
which might be useful if an error occurs
CAUTION
If SAPinst cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default ports 21200 21212 and 4239 are used for communication
between SAPinst GUI server GUI and HTTP server as follows
SAPinst uses port 21200 to communicate with the GUI server
The GUI server uses port 21212 to communicate with the GUI client
5 Splitting
52 Running SAPinst
2454 PUBLIC 2012-04-11
4239 is the port of the HTTP server which is part of the GUI server
If the ports for SAPinst and the GUI server are already in use SAPinst automatically searches for
free port numbers If the search fails SAPinst exits
In this case or if you want SAPinst to use specific ports you can assign them by executing the
sapinst executable with the following command line parameters
SAPINST_DIALOG_PORT=ltport_number_sapinst_to_gui_servergt
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
GUISERVER_HTTP_PORT=ltport_number_http_servergt
To see a list of all available SAPinst properties start SAPinst as described above with command line
parameter -p
sapinst -p
If you need to run SAPinst in accessibility mode proceed as described in Running SAPinst in Accessibility
Mode in the installation documentation of your release
If required you can stop SAPinst by choosing SAPinst Cancel in the SAPinst GUI menu
Prerequisites
We recommend that you use the csh shell for the installation with SAPinst If you want to use
another shell make sure that you have first read SAP Note 202227
SAPinst uses csh scripts during the installation to obtain the environment for user ltsapsidgtadm
This is also true if user ltsapsidgtadm already exists from an earlier SAP system installation and the
shell of this user is not csh Before you start SAPinst execute the following command as user
ltsapsidgtadm to make sure that the csh scripts are up-to-date
bincsh -c source lthome directory of ltsapsidgtadmgtcshrcenv
Make sure that you have specified the most important SAP system parameters as described in Basic
SAP System Installation Parameters in the installation documentation of your release before you start
SAPinst
Only valid for IBM DB2 for zOS |
Check that your installation hosts meet the requirements for the installation options that you
want to installEnd of IBM DB2 for zOS |
Only valid for Non-Standalone Engines and Clients |
If you want to perform a distributed or a high-availability installation make sure that you have
exported and mounted global directories For more information see Exporting and Mounting Global
Directories in the installation documentation of your releaseEnd of Non-Standalone Engines and Clients |
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you have carefully planned your database layout in particular the tablespace layout
as described in Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2554
Only valid for AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for Solaris |
Solaris SPARC onlyEnd of Solaris |
If you want to set up DB2s high-availability cluster solution SA MP make sure that you have read
the document IBM DB2 High Availability Solution IBM Tivoli System Automation for Multiplatforms at
httpservicesapcominstguidesnw70 Installation Installation ndash SAP NetWeaver SystemsEnd of AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for zOS |
First make sure that you have installed DB2 for zOS For information on that installation see
SAP DBA Guide DB2 for zOS DB2 Setup especially the section Stored Procedures EnablementEnd of IBM DB2 for zOS |
Check the value of the environment variable TEMP TMP or TMPDIR
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
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 ndash for example by using a crontab entry
Make sure that you have at least 60 MB of free space in the installation directory for each
installation option In addition you need 200 MB free space for the SAPinst executables If you
cannot provide 200 MB free space in the temporary directory you can set one of the
environment variables TEMP TMP or TMPDIR to another directory with 200 MB free space for
the SAPinst executables
Make sure that the temporary directory has the permissions 777
Only valid for IBM DB2 for zOS |
Make sure that your database is up and runningEnd of IBM DB2 for zOS |
Make sure that your DISPLAY environment variable is set to lthost_namegt00 where
lthost_namegt is the host on which you want to display the GUI
Shell Used Command
Bourne shell (sh) DISPLAY=lthost_namegt00
export DISPLAY
C shell (csh) setenv DISPLAY lthost_namegt00
Korn shell (ksh) export DISPLAY=lthost_namegt00
Make sure that umask is set to 022 for user root
As user root enter the following command umask 022
Check the following values for user root
5 Splitting
52 Running SAPinst
2654 PUBLIC 2012-04-11
In csh execute limit
Output Properties
cputime unlimited
filesize unlimited
datasize unlimited
stacksize 8192 KB
coredumpsize unlimited
descriptors 8192
memorysize unlimited
In sh or ksh execute ulimit -a
Output Properties
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192
coredump(blocks) unlimited
nofiles(descriptors) 8192
memory(KBytes) unlimited
If your parameter settings differ from those above change these values accordingly
EXAMPLE
If you have to change the value for descriptors to 8192 proceed as follows
In csh execute
limit descriptors 8192
In sh or ksh execute
ulimit -n 8192
Before you start SAPinst read SAP Note 1697164 for more information about which user to choose
for running the SAPinst SDT GUI server
Procedure
1 Log on to the installation host as user root
CAUTION
Do not use an existing ltsapsidgtadm user
Only valid for Non-Standalone Engines and Clients |
CAUTION
Make sure that the root user has not set any environment variables for a different SAP system
or database
End of Non-Standalone Engines and Clients |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2754
2 Make the Dual-Stack Split Tool available on the installation host Make sure that it is available
locally We do not recommend that you use Network File System (NFS) because reading from
media mounted with NFS might fail
For more information see Preparation Checklist [page 17] and Preparing the Installation Media in the
installation documentation of your release
3 Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
Only valid for Non-Standalone Engines and Clients |
Change to the directory with the sapinst executable for your operating system by entering the
following command cd ltMountpoint of Installation Master mediumgtDATA_UNITS
ltproductgt_IM_ltOSgtEnd of Non-Standalone Engines and Clients |
End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
4 Start SAPinst by executing the following command sapinst
NOTE
If you want to use a virtual host name start SAPinst with the SAPinst property
SAPINST_USE_HOSTNAME as follows
Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
sapinst SAPINST_USE_HOSTNAME=ltvirtual host namegt
End of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
5 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
In addition if you want to use the split option ldquoMove Java Databaserdquo choose ltYour System
Variantgt
Perform the export and installation steps exactly in the order in which they appear
6 Only valid for Non-Standalone Engines and Clients |
Choose NextEnd of Non-Standalone Engines and Clients |
7 Follow the instructions in the SAPinst input screens and enter the required parameters
NOTE
If SAPinst asks for the Java DVD make sure that you provide a Java DVD with the same
release level as your dual-stack system
For more information about the input parameters position the cursor on the parameter
and press F1
After you have entered all requested input parameters SAPinst displays the Parameter Summary screen
This screen shows both the parameters that you entered and those that SAPinst set by default If
required you can revise the parameters before starting the split procedure
5 Splitting
52 Running SAPinst
2854 PUBLIC 2012-04-11
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you check the following parameters depending on the installation type that you
have chosenEnd of IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for Linux and UNIX and Windows |
If you are performing a typical installation SAPinst creates four sapdata directories by
default If you require more or fewer sapdata directories depending on the storage devices
you are using you must change this parameter before you start the installation By selecting
this parameter on the Summary screen and choosing Revise SAPinst returns to the IBM DB2 for
Linux UNIX and Windows ndashgt Sapdata Directories screen
On this screen you can also decide if you want SAPinst to create the regular table and index
tablespaces with DB2s automatic storage management enabled By default the option for
automatic storage management is preselected
NOTE
As of DB2 V91 and higher the database and the SYSCATSPACE tablespace are always created
with automatic storage management enabled even if you deselect this option on the
dialog IBM DB2 for Linux UNIX and Windows gt Sapdata Directories
For more information about DB2s automatic storage management see section DB2
Tablespaces in the installation documentation of your SAP product
If you are performing a custom installation you set these parameters during the Define
Parameters phase of SAPinst
NOTE
If the tablespace layout used by SAPinst does not meet your requirements you can create
the tablespaces manually by deselecting the option Create Tablespaces with SAPinst on the
IBM DB2 for Linux and UNIX and Windows Sapdata Directories screen
During the installation phase SAPinst then displays the following message
You must create the tablespaces now To do so use the
createTablespacessql script that is located in your installation
directory
To continue the installation choose OK Alternatively you can cancel
SAPinst here and restart it again
SAPinst does not check the page size of tablespaces that have either been created manually
or that already exist If you create the tablespaces manually you must make sure that
you use a page size of 16 KBEnd of IBM DB2 for Linux and UNIX and Windows |
8 To start the dual-stack split choose Start
SAPinst starts and displays the progress of the split procedure
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2954
When the split option has finished successfully SAPinst displays the message Execution of
ltOption_Namegt has completed
Only valid for Oracle |
NOTE
When installing the Oracle database instance SAPinst stops the installation and prompts
you to install the Oracle database software For more information see Installing the Oracle
Database Software in the installation documentation of your release
After you have finished the installation of the Oracle database you continue the database
instance installation by choosing OK in the GUI of the database instance installation
Check SAP Note 1431800 for technical information about Oracle Release 112 in SAP
environments
End of Oracle |
Only valid for Enterprise Portal (EP) |
NOTE
During the final restart of Application Server Java performed by SAPinst the portal starts the
processing and uploading of the new portal archives It takes approximately 15 to 90 minutes
before the deployment is completed and the portal is launched
Do not stop SAPinst or Application Server Java during this phase
End of Enterprise Portal (EP) |
9 If required delete directories with the name sapinst_exexxxxxxxxxx after SAPinst has finished
Sometimes these remain in the temporary directory
NOTE
If there are errors with the SAPinst extraction process you can find the log file
dev_selfexout in the temporary directory
Only valid for Non-Standalone Engines and Clients |
RECOMMENDATION
Keep all installation 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 installation 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 installation directories on installation hosts but make sure
that you delete them after saving them separately
End of Non-Standalone Engines and Clients |
10 We recommend that you delete the directory ltuser_homegtsdtgui
11 Only valid for IBM DB2 for Linux and UNIX and Windows |
If not already done install the DB2 license
5 Splitting
52 Running SAPinst
3054 PUBLIC 2012-04-11
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
End of IBM DB2 for Linux and UNIX and Windows |
12 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 3154
This page is left blank for documents that are printed on both sides
6 Follow-Up Activities
61 Follow-Up Activities Checklist
This section includes the follow-up activities that you have to perform for the following split options
ldquoMove Java Databaserdquo for a central system
ldquoMove Java Databaserdquo for a distributed system or a high-availability system
ldquoKeep Databaserdquo for a central distributed or high-availability system
NOTE
Some of the follow-up activities listed in this section are not described in this documentation You
can find the detailed description in the SAP NetWeaver Application Server Java system copy
documentation relevant for your release at
httpservicesapcominstguides
Move Java Database
Central System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3354
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
7 We recommend that you perform regression testing
8 On the source system you run SAPinst [page 23] to remove the Java parts in the file system and in
the database
9 On the source system you call transaction RZ10 to reimport the profiles from the file system
10 In the Transport Management System (TMS) you configure the transport routes [page 38]
11 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
12 You clean up the system landscape data [page 40]
Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3454 PUBLIC 2012-04-11
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the database host of the source system you run SAPinst [page 23] to remove the Java database
schema
12 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
13 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
14 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
15 You clean up the system landscape data [page 40]
Keep Database
Central Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3554
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
12 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
13 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
14 You clean up the system landscape data [page 40]
62 Maintaining the Connection to the System Landscape Directory
After installing the Java system you need to reconfigure the connection between the System Landscape
Directory (SLD) the source system and the target system The steps required differ depending on
whether you use a local or a central SLD To maintain the connection to the SLD you can either run
the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split or perform the required steps manually as described below
NOTE
This step is only required if the connection to the SLD was established on the source system before
the split
Prerequisites
If you want to use the configuration wizard you need an SAP NetWeaver Java system 70 Support
Package 14 or higher in your landscape
SLDAPIUSER credentials are available in the ABAP system
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3654 PUBLIC 2012-04-11
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
stack systems is no longer supported Furthermore as of SAP Business Suite 7i2011 it will no longer
be possible to upgrade an SAP dual-stack system to a higher release
Since the dual-stack split procedure is only available for SAP NetWeaver 70 systems we recommend
that you split your SAP dual-stack system before you perform an upgrade to one of the following
releases
SAP NetWeaver 73
SAP NetWeaver 73 including Enhancement Package 1
If your system is an SAP Business Suite 7i2011 dual-stack system we strongly recommend that
you perform a dual-stack split as it is no longer possible to upgrade to a higher release
For more information see SAP Note 1655335
If you no longer need the Java stack of your dual-stack system you can remove it as described in
Removing the Java Stack [page 46]
Constraints
You need to consider some constraints before you start splitting your SAP dual-stack system
The dual-stack split procedure does not support the splitting of the following
SAP NetWeaver Process Integration systems
SAP Solution Manager systems
The dual-stack split procedure does not implicate the following
Prerequisites Checker
Host agent
Diagnostics agent
Dialog instances
You can ignore sections in the installation documentation that focus on these options
NOTE
If these options are installed on your SAP dual-stack system and you want to use them on
the Java system after the split you need to install them again on the Java system using the
Installation Master DVD that you used to install your dual-stack system
The migration of the operating system or the database platform during the split is not supported
Naming Conventions
SAP system refers to SAP NetWeaver system or SAP system based on SAP NetWeaver
Dual-stack system refers to SAP NetWeaver ABAP+Java system or SAP ABAP+Java system based on SAP
NetWeaver
11 SAP Notes for the Dual-Stack Split
You must read the following SAP Notes before you start the dual-stack split These SAP Notes contain
the most recent information on the dual-stack split as well as corrections to the dual-stack split
1 Introduction
11 SAP Notes for the Dual-Stack Split
654 PUBLIC 2012-04-11
documentation Make sure that you have the most up-to-date version of each SAP Note which you
can find at httpservicesapcomnotes
SAP Notes for the Dual-Stack Split
SAP Note Number Title Description
1685432 Dual-Stack Split 20 SP1 for Systems Based on SAP NetWeaver
Problems discovered after the publication of the dual-stack split guide
1655335 Use Cases for Splitting Dual-Stack Systems mdash
12 Accessing the SAP Library
The references to the SAP NetWeaver Library documentation in this dual-stack split guide always
refer to the following on SAP Help Portal
SAP NetWeaver 70
httphelpsapcomnw70 Application Help SAP Library English SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 1
httphelpsapcomnw701 Application Help SAP Library English SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 2
httphelpsapcomnw702 Application Help SAP Library English SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 3
httphelpsapcomnw703 Application Help SAP Library English SAP NetWeaver
13 How to Use this Guide
This documentation comprises the description of the dual-stack split procedure and dual-stack-split-
specific steps For general or installation-specific information see the installation documentation
relevant for your release which you can find at httpservicesapcominstguides
Procedure
1 You decide on the split option that you want to use The following split options are available for
central distributed and high-availability systems
ldquoMove Java Databaserdquo (non-MCOD)
ldquoKeep Databaserdquo (MCOD)
For more information see Split Options Covered by this Guide [page 9]
2 You follow the list of steps at the beginning of each phase
Planning [page 13]
Preparation [page 17]
Splitting [page 21]
Follow-up Activities [page 33]
1 Introduction
12 Accessing the SAP Library
2012-04-11 PUBLIC 754
This page is left blank for documents that are printed on both sides
2 Split Options Covered by this Guide
This section shows the split options covered by this guide You have to decide which option you want
to use because the steps you have to perform vary according to the split option that you choose
Move Java Database [page 9]
Keep Database [page 11]
21 Split Option Move Java Database
The split option ldquoMove Java Databaserdquo offers the possibility to split a dual-stack system into one ABAP
system and one Java system each with its own database (non-MCOD)
Move Java Database for Central Systems
When you choose the ldquoMove Java Databaserdquo option for a central system SAPinst exports the Java stack
of the dual-stack system and uses this export to reinstall all main instances on a single host This equates
to an installation of a central system
These are the following instances
Central instance (CI)
Central services instance for Java (SCS)
Database instance (DB)
NOTE
If required you can install the central instance and the central services instance on the ABAP
system host again
Once the installation has finished and after the System Landscape Directory has been reconfigured
SAPinst removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
2012-04-11 PUBLIC 954
Figure 1 Split Option Move Java Database for Central Systems
Move Java Database for Distributed System
When you choose the ldquoMove Java Databaserdquo option for a distributed system SAPinst exports the Java
stack of the dual-stack system and uses this export to reinstall the main instances on several hosts
Every instance can run on a separate host This equates to an installation of a distributed system
These are the following instances
Central instance (CI)
Central services instance for Java (SCS)
Database instance (DB)
NOTE
If required you can reinstall the central instance and the central services instance on the ABAP
system hosts
After the installation has finished and the System Landscape Directory has been reconfigured SAPinst
removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
1054 PUBLIC 2012-04-11
Figure 2 Split Option Move Java Database for Distributed System
22 Split Option Keep Database
The split option ldquoKeep Databaserdquo offers the possibility for the Java system to reuse the existing database
of the dual-stack system using MCOD (multiple components ndash one database)
Keep Database for Central and Distributed Systems
When you choose the ldquoKeep Databaserdquo option SAPinst exports the Java file system on the dual-stack
system It uses this export to reinstall a central services instance (SCS) and a central instance (CI) for
Java They can be installed on one host on different hosts or on the source system hosts again
Additionally SAPinst adapts the Java schema of the database of the dual-stack system to the target Java
system
After the installation has finished and the System Landscape Directory has been reconfigured SAPinst
removes all Java parts from the dual-stack system except the Java database schema
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-04-11 PUBLIC 1154
Figure 3 Split Option Keep Database for Central Systems
Figure 4 Split Option Keep Database for Distributed Systems
2 Split Options Covered by this Guide
22 Split Option Keep Database
1254 PUBLIC 2012-04-11
3 Planning
31 Planning Checklist
This section includes the planning steps that you have to perform when you want to install the new
Java system on one or more hosts Perform the planning steps according to the split option and your
system variant
NOTE
Most of the required planning steps listed in this section are not described in this documentation
You can find the detailed description in the SAP NetWeaver Application Server Java installation
documentation relevant for your release at httpservicesapcominstguides
Prerequisites
You have decided on your split option [page 9]
Split Option ldquoMove Java Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
1 You check the hardware and software requirements for the Java installation host
For more information see Hardware and Software Requirements in the installation documentation of
your release
2 You read about user management [page 15]
3 You identify basic SAP system installation parameters
For more information see Basic SAP System Parameters in the installation documentation of your
release
Be aware of the following dual-stack-split-specific deviations
SAP System Parameters
User management
We do not recommend that you make modifications in the user management settings
For more information see User Management [page 15]
System Landscape Directory (SLD)
You can ignore SLD parameters
Only valid for Oracle |
SAP System Database Parameters Java database schema
We recommend that you choose a schema ID that is different from your SAP system ID
It might cause problems when you copy a system if ltSCHEMA_IDgt is the same as ltSAPSIDgt and
the database-specific method used for the copy does not allow you to rename the database
3 Planning
31 Planning Checklist
2012-04-11 PUBLIC 1354
schemes In certain situations you might create a system copy with a new ltSAPSIDgt but where
the database schema has the old ltSAPSIDgt This is not a technical problem but might be
confusing to the system administratorEnd of Oracle |
4 Only valid for MaxDB |
You plan your system configuration
For more information see System Configuration in the installation documentation of your releaseEnd of MaxDB |
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
You plan the setup of your database carefully
For more information see Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
7 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 43]
8 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
9 Only valid for IBM DB2 for zOS |
If you want to execute a Software Life-Cycle Option with SAPinst in an SAP system with thick client
connectivity see Special Considerations Regarding Connectivity for Software Life-Cycle Options in the installation
documentation of your releaseEnd of IBM DB2 for zOS |
10 Only valid for IBM DB2 for i5OS |
Optionally you decide whether you want to install multiple SAP systems on a single host
For more information see Multiple SAP Systems on a Single Host in the installation documentation of
your releaseEnd of IBM DB2 for i5OS |
11 You can continue with Preparation [page 17]
Split Option ldquoKeep Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
1 You check the hardware and software requirements for the Java installation host
For more information see Hardware and Software Requirements in the installation documentation of
your release
2 You read about user management [page 15]
3 You identify basic SAP system installation parameters
For more information see Basic SAP System Parameters in the installation documentation of your
release
3 Planning
31 Planning Checklist
1454 PUBLIC 2012-04-11
Be aware of the following dual-stack-split-specific deviation for SAP System Parameters
User management
We do not recommend that you make modifications in the user management settings For
more information see User Management [page 15]
System Landscape Directory (SLD)
You can ignore SLD parameters
4 Only valid for IBM DB2 for zOSMaxDB |
You plan your system configuration
For more information see System Configuration in the installation documentation of your releaseEnd of IBM DB2 for zOSMaxDB |
5 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
6 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 43]
7 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
8 Only valid for IBM DB2 for zOS |
If you want to execute a Software Life-Cycle Option with SAPinst in an SAP system with thick client
connectivity see Special Considerations Regarding Connectivity for Software Life-Cycle Options in the installation
documentation of your releaseEnd of IBM DB2 for zOS |
9 Only valid for IBM DB2 for i5OS |
Optionally you decide whether you want to install multiple SAP systems on a single host
For more information see Multiple SAP Systems on a Single Host in the installation documentation of
your releaseEnd of IBM DB2 for i5OS |
10 You can continue with Preparation [page 17]
32 User Management
The dual-stack split procedure does not change the user management and you cannot choose which
kind of user management you want to use for the target AS Java system That is the separated Java
system and the ABAP system both use the user management of the former dual-stack system The
following is possible
If the dual-stack system uses AS ABAP as data source for the User Management Engine (UME)
after the split the separated Java stack will also use the ABAP UME
If the dual-stack system uses an LDAP directory as source for user data this is also valid for the Java
stack
3 Planning
32 User Management
2012-04-11 PUBLIC 1554
In both cases manual configuration is not required
We do not recommend that you make modifications to the user management settings
For more information see SAP Note 718383
3 Planning
32 User Management
1654 PUBLIC 2012-04-11
4 Preparation
41 Preparation Checklist
This section includes the preparation steps that you have to perform when you want to install the new
Java system on one or more hosts
NOTE
Most of the required preparation steps listed in this section are not described in this
documentation You can find the detailed description in the SAP NetWeaver Application Server
Java installation documentation relevant for your release at httpservicesapcom
instguides
1 Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
You make sure that the required operating system users and groups are created
To create the groups and users automatically run the Dual-Stack Split Tool on the host where
the SAP Java system is to be installed and choose Dual-Stack Split Operating System Users and
Groups
For more information see Creating Operating System Users and Groups in the installation documentation
of your releaseEnd of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
2 You set up file systems and make sure that the required disk space is available for the directories
to be created during the installation
For more information see Setting Up File Systems for a High-Availability System in the installation
documentation of your release
3 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
4 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
If you want to install a high-availability system you perform switchover preparations
For more information see Performing Switchover Preparations for High-Availability in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
5 If you want to share the transport directory trans from another system you export this directory
to your installation hosts
For more information see Exporting and Mounting the Global Transport Directory in the installation
documentation of your release
4 Preparation
41 Preparation Checklist
2012-04-11 PUBLIC 1754
6 You install the Java Development Kit This step is not required if you have installed the SAP JVM
4 on your source system
For more information see Installing the Java Development Kit in the installation documentation of your
release
7 You make sure that the required installation media are available on each host
You can download the Dual-Stack Split Tool at httpservicesapcomsltoolset
Software Logistics Toolset 10 Dual-Stack Split
You can download the Java stack and database installation media from SAP Service
Marketplace as described in Preparing the Installation Media in the installation documentation of
your release
NOTE
The release level required for the installation corresponds to the release level of your dual-
stack system
The following table shows the required installation media for the dual-stack split
SAP Instance Installation Required Media
Central services instance central instance
Dual-Stack Split Tool Java DVD RDBMS Client DVD
Move Java Database only Database instance
Dual-Stack Split Tool Java DVD Only valid for MS SQL ServerOracle |
RDBMS DVDEnd of MS SQL ServerOracle |
Only valid for MS SQL ServerOracle |
RDBMS Patch DVD (if available)End of MS SQL ServerOracle |
8 Only valid for HA (MSCS) |
To install a high-availability system with Microsoft Cluster Service (MSCS) you also perform the
MSCS-specific preparation tasks as described in the installation documentation of your releaseEnd of HA (MSCS) |
9 Only valid for HA (MSCS) |
If you choose the split option ldquoKeep Databaserdquo with the scenario ldquoKeep SCS on the Source Cluster
Systemrdquo you perform the following steps
You provide additional disk storage on the target cluster system
For more information see Distribution of SAP System Components to Disks for MSCS Directories in an
MSCS Configuration and IP Addresses in an MSCS Configuration in the installation documentation of
your release
You provide an additional IP address and an additional virtual host name for the Java system
For more information see Mapping Host Names to IP Addresses for MSCS in the installation
documentation of your releaseEnd of HA (MSCS) |
4 Preparation
41 Preparation Checklist
1854 PUBLIC 2012-04-11
10 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 19] of
the dual-stack system
11 You can continue with Splitting [page 21]
42 Performing a Full System Backup
If you decided to use the split option ldquoKeep Databaserdquo you must perform a full system backup of the
dual-stack system or at least a backup of the Java database schema before you start the split procedure
If you decided to use the split option ldquoMove Java Databaserdquo you do not need to perform a backup before
you start the split procedure
For more information about backing up your database see the database-specific backup and recovery
documentation in the SAP Library [page 7] at
SAP MaxDB
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for SAP
MaxDB
Oracle
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Oracle
IBM DB2 for i5OS
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 UDB for iSeries
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for i
4 Preparation
42 Performing a Full System Backup
2012-04-11 PUBLIC 1954
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
i
IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX
and Windows
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
Linux UNIX and Windows
IBM DB2 for zOS
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 UDB for zOS
SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for DB2 for z
OS
Microsoft SQL Server
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Microsoft SQL
Server
4 Preparation
42 Performing a Full System Backup
2054 PUBLIC 2012-04-11
5 Splitting
51 Splitting Checklist
This section includes the splitting steps that you have to perform for the following split options
ldquoMove Java Databaserdquo
ldquoKeep Databaserdquo
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Only valid for Oracle |
You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 You export the Java stack using SAPinst [page 23]
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
4 You restart the source system
5 You run SAPinst [page 23] to install a Java only system using the export from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2012-04-11 PUBLIC 2154
Distributed System
1 Only valid for Oracle |
On the database instance host of the dual-stack system you install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes on the database instance host
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 On the database instance host of the dual-stack system you run SAPinst [page 23] to export the
Java database schema
4 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the Java
parts of the file system of the central instance
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
5 You restart the source system
6 You run SAPinst [page 23] to install a central services instance for the Java target system
7 You run SAPinst [page 23] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
9 You continue with Follow-Up Activities [page 33]
Keep Database
1 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the
file system of the central instance
5 Splitting
51 Splitting Checklist
2254 PUBLIC 2012-04-11
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you wont use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
2 You restart the source system
3 You run SAPinst [page 23] to install a central services instance for the Java target system
4 On the database instance host of the dual-stack system you run SAPinst [page 23] to adapt the
database for the Java target system
NOTE
Make sure that you enter the profile directory of the Java target system in the SAP System gt
General Parameters screen
5 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
52 Running SAPinst
This section describes how to run the installation tool SAPinst SAPinst includes a GUI client and a GUI
server which both use Java
The procedure describes an installation where SAPinst GUI client and GUI server are running on the
same host In the following GUI client and GUI server are addressed as ldquoSAPinst GUIrdquo
If you need to see the installation on a remote display we recommend that you perform a remote
installation with SAPinst where the SAPinst GUI is running on a separate host from SAPinst For more
information see Performing a Remote Installation with SAPinst in the installation documentation of your
release
Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote
access to SAPinst GUI on Windows workstations For more information see SAP Note 1170809
Useful Information About SAPinst
When you start SAPinst it automatically starts the SAPinst GUI
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2354
SAPinst creates the installation directory sapinst_instdir directly below the temporary directory
SAPinst 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 SAPinst
creates the installation directory sapinst_instdir directly below the tmp directory by default
If you want SAPinst to create the installation directory sapinst_instdir in another directory set
the environment variable TEMP to this directory before you start SAPinst
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
Only valid for IBM DB2 for i5OS |
NOTE
When you leave your Qp2Term session all changes of the environment variables done by the
command export are reverted
End of IBM DB2 for i5OS |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
SAPinst creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt
SAPinst extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is located
in the environment variables TEMP TMP or TMPDIR These files are deleted after SAPinst has stopped
running
The temporary directory sapinst_exexxxxxxxxxx sometimes remains undeleted You can safely
delete it
The temporary directory also contains the log file dev_selfexout from the extraction process
which might be useful if an error occurs
CAUTION
If SAPinst cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default ports 21200 21212 and 4239 are used for communication
between SAPinst GUI server GUI and HTTP server as follows
SAPinst uses port 21200 to communicate with the GUI server
The GUI server uses port 21212 to communicate with the GUI client
5 Splitting
52 Running SAPinst
2454 PUBLIC 2012-04-11
4239 is the port of the HTTP server which is part of the GUI server
If the ports for SAPinst and the GUI server are already in use SAPinst automatically searches for
free port numbers If the search fails SAPinst exits
In this case or if you want SAPinst to use specific ports you can assign them by executing the
sapinst executable with the following command line parameters
SAPINST_DIALOG_PORT=ltport_number_sapinst_to_gui_servergt
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
GUISERVER_HTTP_PORT=ltport_number_http_servergt
To see a list of all available SAPinst properties start SAPinst as described above with command line
parameter -p
sapinst -p
If you need to run SAPinst in accessibility mode proceed as described in Running SAPinst in Accessibility
Mode in the installation documentation of your release
If required you can stop SAPinst by choosing SAPinst Cancel in the SAPinst GUI menu
Prerequisites
We recommend that you use the csh shell for the installation with SAPinst If you want to use
another shell make sure that you have first read SAP Note 202227
SAPinst uses csh scripts during the installation to obtain the environment for user ltsapsidgtadm
This is also true if user ltsapsidgtadm already exists from an earlier SAP system installation and the
shell of this user is not csh Before you start SAPinst execute the following command as user
ltsapsidgtadm to make sure that the csh scripts are up-to-date
bincsh -c source lthome directory of ltsapsidgtadmgtcshrcenv
Make sure that you have specified the most important SAP system parameters as described in Basic
SAP System Installation Parameters in the installation documentation of your release before you start
SAPinst
Only valid for IBM DB2 for zOS |
Check that your installation hosts meet the requirements for the installation options that you
want to installEnd of IBM DB2 for zOS |
Only valid for Non-Standalone Engines and Clients |
If you want to perform a distributed or a high-availability installation make sure that you have
exported and mounted global directories For more information see Exporting and Mounting Global
Directories in the installation documentation of your releaseEnd of Non-Standalone Engines and Clients |
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you have carefully planned your database layout in particular the tablespace layout
as described in Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2554
Only valid for AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for Solaris |
Solaris SPARC onlyEnd of Solaris |
If you want to set up DB2s high-availability cluster solution SA MP make sure that you have read
the document IBM DB2 High Availability Solution IBM Tivoli System Automation for Multiplatforms at
httpservicesapcominstguidesnw70 Installation Installation ndash SAP NetWeaver SystemsEnd of AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for zOS |
First make sure that you have installed DB2 for zOS For information on that installation see
SAP DBA Guide DB2 for zOS DB2 Setup especially the section Stored Procedures EnablementEnd of IBM DB2 for zOS |
Check the value of the environment variable TEMP TMP or TMPDIR
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
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 ndash for example by using a crontab entry
Make sure that you have at least 60 MB of free space in the installation directory for each
installation option In addition you need 200 MB free space for the SAPinst executables If you
cannot provide 200 MB free space in the temporary directory you can set one of the
environment variables TEMP TMP or TMPDIR to another directory with 200 MB free space for
the SAPinst executables
Make sure that the temporary directory has the permissions 777
Only valid for IBM DB2 for zOS |
Make sure that your database is up and runningEnd of IBM DB2 for zOS |
Make sure that your DISPLAY environment variable is set to lthost_namegt00 where
lthost_namegt is the host on which you want to display the GUI
Shell Used Command
Bourne shell (sh) DISPLAY=lthost_namegt00
export DISPLAY
C shell (csh) setenv DISPLAY lthost_namegt00
Korn shell (ksh) export DISPLAY=lthost_namegt00
Make sure that umask is set to 022 for user root
As user root enter the following command umask 022
Check the following values for user root
5 Splitting
52 Running SAPinst
2654 PUBLIC 2012-04-11
In csh execute limit
Output Properties
cputime unlimited
filesize unlimited
datasize unlimited
stacksize 8192 KB
coredumpsize unlimited
descriptors 8192
memorysize unlimited
In sh or ksh execute ulimit -a
Output Properties
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192
coredump(blocks) unlimited
nofiles(descriptors) 8192
memory(KBytes) unlimited
If your parameter settings differ from those above change these values accordingly
EXAMPLE
If you have to change the value for descriptors to 8192 proceed as follows
In csh execute
limit descriptors 8192
In sh or ksh execute
ulimit -n 8192
Before you start SAPinst read SAP Note 1697164 for more information about which user to choose
for running the SAPinst SDT GUI server
Procedure
1 Log on to the installation host as user root
CAUTION
Do not use an existing ltsapsidgtadm user
Only valid for Non-Standalone Engines and Clients |
CAUTION
Make sure that the root user has not set any environment variables for a different SAP system
or database
End of Non-Standalone Engines and Clients |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2754
2 Make the Dual-Stack Split Tool available on the installation host Make sure that it is available
locally We do not recommend that you use Network File System (NFS) because reading from
media mounted with NFS might fail
For more information see Preparation Checklist [page 17] and Preparing the Installation Media in the
installation documentation of your release
3 Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
Only valid for Non-Standalone Engines and Clients |
Change to the directory with the sapinst executable for your operating system by entering the
following command cd ltMountpoint of Installation Master mediumgtDATA_UNITS
ltproductgt_IM_ltOSgtEnd of Non-Standalone Engines and Clients |
End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
4 Start SAPinst by executing the following command sapinst
NOTE
If you want to use a virtual host name start SAPinst with the SAPinst property
SAPINST_USE_HOSTNAME as follows
Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
sapinst SAPINST_USE_HOSTNAME=ltvirtual host namegt
End of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
5 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
In addition if you want to use the split option ldquoMove Java Databaserdquo choose ltYour System
Variantgt
Perform the export and installation steps exactly in the order in which they appear
6 Only valid for Non-Standalone Engines and Clients |
Choose NextEnd of Non-Standalone Engines and Clients |
7 Follow the instructions in the SAPinst input screens and enter the required parameters
NOTE
If SAPinst asks for the Java DVD make sure that you provide a Java DVD with the same
release level as your dual-stack system
For more information about the input parameters position the cursor on the parameter
and press F1
After you have entered all requested input parameters SAPinst displays the Parameter Summary screen
This screen shows both the parameters that you entered and those that SAPinst set by default If
required you can revise the parameters before starting the split procedure
5 Splitting
52 Running SAPinst
2854 PUBLIC 2012-04-11
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you check the following parameters depending on the installation type that you
have chosenEnd of IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for Linux and UNIX and Windows |
If you are performing a typical installation SAPinst creates four sapdata directories by
default If you require more or fewer sapdata directories depending on the storage devices
you are using you must change this parameter before you start the installation By selecting
this parameter on the Summary screen and choosing Revise SAPinst returns to the IBM DB2 for
Linux UNIX and Windows ndashgt Sapdata Directories screen
On this screen you can also decide if you want SAPinst to create the regular table and index
tablespaces with DB2s automatic storage management enabled By default the option for
automatic storage management is preselected
NOTE
As of DB2 V91 and higher the database and the SYSCATSPACE tablespace are always created
with automatic storage management enabled even if you deselect this option on the
dialog IBM DB2 for Linux UNIX and Windows gt Sapdata Directories
For more information about DB2s automatic storage management see section DB2
Tablespaces in the installation documentation of your SAP product
If you are performing a custom installation you set these parameters during the Define
Parameters phase of SAPinst
NOTE
If the tablespace layout used by SAPinst does not meet your requirements you can create
the tablespaces manually by deselecting the option Create Tablespaces with SAPinst on the
IBM DB2 for Linux and UNIX and Windows Sapdata Directories screen
During the installation phase SAPinst then displays the following message
You must create the tablespaces now To do so use the
createTablespacessql script that is located in your installation
directory
To continue the installation choose OK Alternatively you can cancel
SAPinst here and restart it again
SAPinst does not check the page size of tablespaces that have either been created manually
or that already exist If you create the tablespaces manually you must make sure that
you use a page size of 16 KBEnd of IBM DB2 for Linux and UNIX and Windows |
8 To start the dual-stack split choose Start
SAPinst starts and displays the progress of the split procedure
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2954
When the split option has finished successfully SAPinst displays the message Execution of
ltOption_Namegt has completed
Only valid for Oracle |
NOTE
When installing the Oracle database instance SAPinst stops the installation and prompts
you to install the Oracle database software For more information see Installing the Oracle
Database Software in the installation documentation of your release
After you have finished the installation of the Oracle database you continue the database
instance installation by choosing OK in the GUI of the database instance installation
Check SAP Note 1431800 for technical information about Oracle Release 112 in SAP
environments
End of Oracle |
Only valid for Enterprise Portal (EP) |
NOTE
During the final restart of Application Server Java performed by SAPinst the portal starts the
processing and uploading of the new portal archives It takes approximately 15 to 90 minutes
before the deployment is completed and the portal is launched
Do not stop SAPinst or Application Server Java during this phase
End of Enterprise Portal (EP) |
9 If required delete directories with the name sapinst_exexxxxxxxxxx after SAPinst has finished
Sometimes these remain in the temporary directory
NOTE
If there are errors with the SAPinst extraction process you can find the log file
dev_selfexout in the temporary directory
Only valid for Non-Standalone Engines and Clients |
RECOMMENDATION
Keep all installation 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 installation 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 installation directories on installation hosts but make sure
that you delete them after saving them separately
End of Non-Standalone Engines and Clients |
10 We recommend that you delete the directory ltuser_homegtsdtgui
11 Only valid for IBM DB2 for Linux and UNIX and Windows |
If not already done install the DB2 license
5 Splitting
52 Running SAPinst
3054 PUBLIC 2012-04-11
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
End of IBM DB2 for Linux and UNIX and Windows |
12 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 3154
This page is left blank for documents that are printed on both sides
6 Follow-Up Activities
61 Follow-Up Activities Checklist
This section includes the follow-up activities that you have to perform for the following split options
ldquoMove Java Databaserdquo for a central system
ldquoMove Java Databaserdquo for a distributed system or a high-availability system
ldquoKeep Databaserdquo for a central distributed or high-availability system
NOTE
Some of the follow-up activities listed in this section are not described in this documentation You
can find the detailed description in the SAP NetWeaver Application Server Java system copy
documentation relevant for your release at
httpservicesapcominstguides
Move Java Database
Central System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3354
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
7 We recommend that you perform regression testing
8 On the source system you run SAPinst [page 23] to remove the Java parts in the file system and in
the database
9 On the source system you call transaction RZ10 to reimport the profiles from the file system
10 In the Transport Management System (TMS) you configure the transport routes [page 38]
11 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
12 You clean up the system landscape data [page 40]
Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3454 PUBLIC 2012-04-11
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the database host of the source system you run SAPinst [page 23] to remove the Java database
schema
12 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
13 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
14 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
15 You clean up the system landscape data [page 40]
Keep Database
Central Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3554
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
12 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
13 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
14 You clean up the system landscape data [page 40]
62 Maintaining the Connection to the System Landscape Directory
After installing the Java system you need to reconfigure the connection between the System Landscape
Directory (SLD) the source system and the target system The steps required differ depending on
whether you use a local or a central SLD To maintain the connection to the SLD you can either run
the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split or perform the required steps manually as described below
NOTE
This step is only required if the connection to the SLD was established on the source system before
the split
Prerequisites
If you want to use the configuration wizard you need an SAP NetWeaver Java system 70 Support
Package 14 or higher in your landscape
SLDAPIUSER credentials are available in the ABAP system
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3654 PUBLIC 2012-04-11
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
documentation Make sure that you have the most up-to-date version of each SAP Note which you
can find at httpservicesapcomnotes
SAP Notes for the Dual-Stack Split
SAP Note Number Title Description
1685432 Dual-Stack Split 20 SP1 for Systems Based on SAP NetWeaver
Problems discovered after the publication of the dual-stack split guide
1655335 Use Cases for Splitting Dual-Stack Systems mdash
12 Accessing the SAP Library
The references to the SAP NetWeaver Library documentation in this dual-stack split guide always
refer to the following on SAP Help Portal
SAP NetWeaver 70
httphelpsapcomnw70 Application Help SAP Library English SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 1
httphelpsapcomnw701 Application Help SAP Library English SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 2
httphelpsapcomnw702 Application Help SAP Library English SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 3
httphelpsapcomnw703 Application Help SAP Library English SAP NetWeaver
13 How to Use this Guide
This documentation comprises the description of the dual-stack split procedure and dual-stack-split-
specific steps For general or installation-specific information see the installation documentation
relevant for your release which you can find at httpservicesapcominstguides
Procedure
1 You decide on the split option that you want to use The following split options are available for
central distributed and high-availability systems
ldquoMove Java Databaserdquo (non-MCOD)
ldquoKeep Databaserdquo (MCOD)
For more information see Split Options Covered by this Guide [page 9]
2 You follow the list of steps at the beginning of each phase
Planning [page 13]
Preparation [page 17]
Splitting [page 21]
Follow-up Activities [page 33]
1 Introduction
12 Accessing the SAP Library
2012-04-11 PUBLIC 754
This page is left blank for documents that are printed on both sides
2 Split Options Covered by this Guide
This section shows the split options covered by this guide You have to decide which option you want
to use because the steps you have to perform vary according to the split option that you choose
Move Java Database [page 9]
Keep Database [page 11]
21 Split Option Move Java Database
The split option ldquoMove Java Databaserdquo offers the possibility to split a dual-stack system into one ABAP
system and one Java system each with its own database (non-MCOD)
Move Java Database for Central Systems
When you choose the ldquoMove Java Databaserdquo option for a central system SAPinst exports the Java stack
of the dual-stack system and uses this export to reinstall all main instances on a single host This equates
to an installation of a central system
These are the following instances
Central instance (CI)
Central services instance for Java (SCS)
Database instance (DB)
NOTE
If required you can install the central instance and the central services instance on the ABAP
system host again
Once the installation has finished and after the System Landscape Directory has been reconfigured
SAPinst removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
2012-04-11 PUBLIC 954
Figure 1 Split Option Move Java Database for Central Systems
Move Java Database for Distributed System
When you choose the ldquoMove Java Databaserdquo option for a distributed system SAPinst exports the Java
stack of the dual-stack system and uses this export to reinstall the main instances on several hosts
Every instance can run on a separate host This equates to an installation of a distributed system
These are the following instances
Central instance (CI)
Central services instance for Java (SCS)
Database instance (DB)
NOTE
If required you can reinstall the central instance and the central services instance on the ABAP
system hosts
After the installation has finished and the System Landscape Directory has been reconfigured SAPinst
removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
1054 PUBLIC 2012-04-11
Figure 2 Split Option Move Java Database for Distributed System
22 Split Option Keep Database
The split option ldquoKeep Databaserdquo offers the possibility for the Java system to reuse the existing database
of the dual-stack system using MCOD (multiple components ndash one database)
Keep Database for Central and Distributed Systems
When you choose the ldquoKeep Databaserdquo option SAPinst exports the Java file system on the dual-stack
system It uses this export to reinstall a central services instance (SCS) and a central instance (CI) for
Java They can be installed on one host on different hosts or on the source system hosts again
Additionally SAPinst adapts the Java schema of the database of the dual-stack system to the target Java
system
After the installation has finished and the System Landscape Directory has been reconfigured SAPinst
removes all Java parts from the dual-stack system except the Java database schema
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-04-11 PUBLIC 1154
Figure 3 Split Option Keep Database for Central Systems
Figure 4 Split Option Keep Database for Distributed Systems
2 Split Options Covered by this Guide
22 Split Option Keep Database
1254 PUBLIC 2012-04-11
3 Planning
31 Planning Checklist
This section includes the planning steps that you have to perform when you want to install the new
Java system on one or more hosts Perform the planning steps according to the split option and your
system variant
NOTE
Most of the required planning steps listed in this section are not described in this documentation
You can find the detailed description in the SAP NetWeaver Application Server Java installation
documentation relevant for your release at httpservicesapcominstguides
Prerequisites
You have decided on your split option [page 9]
Split Option ldquoMove Java Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
1 You check the hardware and software requirements for the Java installation host
For more information see Hardware and Software Requirements in the installation documentation of
your release
2 You read about user management [page 15]
3 You identify basic SAP system installation parameters
For more information see Basic SAP System Parameters in the installation documentation of your
release
Be aware of the following dual-stack-split-specific deviations
SAP System Parameters
User management
We do not recommend that you make modifications in the user management settings
For more information see User Management [page 15]
System Landscape Directory (SLD)
You can ignore SLD parameters
Only valid for Oracle |
SAP System Database Parameters Java database schema
We recommend that you choose a schema ID that is different from your SAP system ID
It might cause problems when you copy a system if ltSCHEMA_IDgt is the same as ltSAPSIDgt and
the database-specific method used for the copy does not allow you to rename the database
3 Planning
31 Planning Checklist
2012-04-11 PUBLIC 1354
schemes In certain situations you might create a system copy with a new ltSAPSIDgt but where
the database schema has the old ltSAPSIDgt This is not a technical problem but might be
confusing to the system administratorEnd of Oracle |
4 Only valid for MaxDB |
You plan your system configuration
For more information see System Configuration in the installation documentation of your releaseEnd of MaxDB |
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
You plan the setup of your database carefully
For more information see Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
7 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 43]
8 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
9 Only valid for IBM DB2 for zOS |
If you want to execute a Software Life-Cycle Option with SAPinst in an SAP system with thick client
connectivity see Special Considerations Regarding Connectivity for Software Life-Cycle Options in the installation
documentation of your releaseEnd of IBM DB2 for zOS |
10 Only valid for IBM DB2 for i5OS |
Optionally you decide whether you want to install multiple SAP systems on a single host
For more information see Multiple SAP Systems on a Single Host in the installation documentation of
your releaseEnd of IBM DB2 for i5OS |
11 You can continue with Preparation [page 17]
Split Option ldquoKeep Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
1 You check the hardware and software requirements for the Java installation host
For more information see Hardware and Software Requirements in the installation documentation of
your release
2 You read about user management [page 15]
3 You identify basic SAP system installation parameters
For more information see Basic SAP System Parameters in the installation documentation of your
release
3 Planning
31 Planning Checklist
1454 PUBLIC 2012-04-11
Be aware of the following dual-stack-split-specific deviation for SAP System Parameters
User management
We do not recommend that you make modifications in the user management settings For
more information see User Management [page 15]
System Landscape Directory (SLD)
You can ignore SLD parameters
4 Only valid for IBM DB2 for zOSMaxDB |
You plan your system configuration
For more information see System Configuration in the installation documentation of your releaseEnd of IBM DB2 for zOSMaxDB |
5 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
6 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 43]
7 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
8 Only valid for IBM DB2 for zOS |
If you want to execute a Software Life-Cycle Option with SAPinst in an SAP system with thick client
connectivity see Special Considerations Regarding Connectivity for Software Life-Cycle Options in the installation
documentation of your releaseEnd of IBM DB2 for zOS |
9 Only valid for IBM DB2 for i5OS |
Optionally you decide whether you want to install multiple SAP systems on a single host
For more information see Multiple SAP Systems on a Single Host in the installation documentation of
your releaseEnd of IBM DB2 for i5OS |
10 You can continue with Preparation [page 17]
32 User Management
The dual-stack split procedure does not change the user management and you cannot choose which
kind of user management you want to use for the target AS Java system That is the separated Java
system and the ABAP system both use the user management of the former dual-stack system The
following is possible
If the dual-stack system uses AS ABAP as data source for the User Management Engine (UME)
after the split the separated Java stack will also use the ABAP UME
If the dual-stack system uses an LDAP directory as source for user data this is also valid for the Java
stack
3 Planning
32 User Management
2012-04-11 PUBLIC 1554
In both cases manual configuration is not required
We do not recommend that you make modifications to the user management settings
For more information see SAP Note 718383
3 Planning
32 User Management
1654 PUBLIC 2012-04-11
4 Preparation
41 Preparation Checklist
This section includes the preparation steps that you have to perform when you want to install the new
Java system on one or more hosts
NOTE
Most of the required preparation steps listed in this section are not described in this
documentation You can find the detailed description in the SAP NetWeaver Application Server
Java installation documentation relevant for your release at httpservicesapcom
instguides
1 Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
You make sure that the required operating system users and groups are created
To create the groups and users automatically run the Dual-Stack Split Tool on the host where
the SAP Java system is to be installed and choose Dual-Stack Split Operating System Users and
Groups
For more information see Creating Operating System Users and Groups in the installation documentation
of your releaseEnd of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
2 You set up file systems and make sure that the required disk space is available for the directories
to be created during the installation
For more information see Setting Up File Systems for a High-Availability System in the installation
documentation of your release
3 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
4 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
If you want to install a high-availability system you perform switchover preparations
For more information see Performing Switchover Preparations for High-Availability in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
5 If you want to share the transport directory trans from another system you export this directory
to your installation hosts
For more information see Exporting and Mounting the Global Transport Directory in the installation
documentation of your release
4 Preparation
41 Preparation Checklist
2012-04-11 PUBLIC 1754
6 You install the Java Development Kit This step is not required if you have installed the SAP JVM
4 on your source system
For more information see Installing the Java Development Kit in the installation documentation of your
release
7 You make sure that the required installation media are available on each host
You can download the Dual-Stack Split Tool at httpservicesapcomsltoolset
Software Logistics Toolset 10 Dual-Stack Split
You can download the Java stack and database installation media from SAP Service
Marketplace as described in Preparing the Installation Media in the installation documentation of
your release
NOTE
The release level required for the installation corresponds to the release level of your dual-
stack system
The following table shows the required installation media for the dual-stack split
SAP Instance Installation Required Media
Central services instance central instance
Dual-Stack Split Tool Java DVD RDBMS Client DVD
Move Java Database only Database instance
Dual-Stack Split Tool Java DVD Only valid for MS SQL ServerOracle |
RDBMS DVDEnd of MS SQL ServerOracle |
Only valid for MS SQL ServerOracle |
RDBMS Patch DVD (if available)End of MS SQL ServerOracle |
8 Only valid for HA (MSCS) |
To install a high-availability system with Microsoft Cluster Service (MSCS) you also perform the
MSCS-specific preparation tasks as described in the installation documentation of your releaseEnd of HA (MSCS) |
9 Only valid for HA (MSCS) |
If you choose the split option ldquoKeep Databaserdquo with the scenario ldquoKeep SCS on the Source Cluster
Systemrdquo you perform the following steps
You provide additional disk storage on the target cluster system
For more information see Distribution of SAP System Components to Disks for MSCS Directories in an
MSCS Configuration and IP Addresses in an MSCS Configuration in the installation documentation of
your release
You provide an additional IP address and an additional virtual host name for the Java system
For more information see Mapping Host Names to IP Addresses for MSCS in the installation
documentation of your releaseEnd of HA (MSCS) |
4 Preparation
41 Preparation Checklist
1854 PUBLIC 2012-04-11
10 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 19] of
the dual-stack system
11 You can continue with Splitting [page 21]
42 Performing a Full System Backup
If you decided to use the split option ldquoKeep Databaserdquo you must perform a full system backup of the
dual-stack system or at least a backup of the Java database schema before you start the split procedure
If you decided to use the split option ldquoMove Java Databaserdquo you do not need to perform a backup before
you start the split procedure
For more information about backing up your database see the database-specific backup and recovery
documentation in the SAP Library [page 7] at
SAP MaxDB
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for SAP
MaxDB
Oracle
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Oracle
IBM DB2 for i5OS
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 UDB for iSeries
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for i
4 Preparation
42 Performing a Full System Backup
2012-04-11 PUBLIC 1954
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
i
IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX
and Windows
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
Linux UNIX and Windows
IBM DB2 for zOS
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 UDB for zOS
SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for DB2 for z
OS
Microsoft SQL Server
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Microsoft SQL
Server
4 Preparation
42 Performing a Full System Backup
2054 PUBLIC 2012-04-11
5 Splitting
51 Splitting Checklist
This section includes the splitting steps that you have to perform for the following split options
ldquoMove Java Databaserdquo
ldquoKeep Databaserdquo
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Only valid for Oracle |
You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 You export the Java stack using SAPinst [page 23]
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
4 You restart the source system
5 You run SAPinst [page 23] to install a Java only system using the export from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2012-04-11 PUBLIC 2154
Distributed System
1 Only valid for Oracle |
On the database instance host of the dual-stack system you install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes on the database instance host
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 On the database instance host of the dual-stack system you run SAPinst [page 23] to export the
Java database schema
4 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the Java
parts of the file system of the central instance
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
5 You restart the source system
6 You run SAPinst [page 23] to install a central services instance for the Java target system
7 You run SAPinst [page 23] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
9 You continue with Follow-Up Activities [page 33]
Keep Database
1 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the
file system of the central instance
5 Splitting
51 Splitting Checklist
2254 PUBLIC 2012-04-11
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you wont use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
2 You restart the source system
3 You run SAPinst [page 23] to install a central services instance for the Java target system
4 On the database instance host of the dual-stack system you run SAPinst [page 23] to adapt the
database for the Java target system
NOTE
Make sure that you enter the profile directory of the Java target system in the SAP System gt
General Parameters screen
5 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
52 Running SAPinst
This section describes how to run the installation tool SAPinst SAPinst includes a GUI client and a GUI
server which both use Java
The procedure describes an installation where SAPinst GUI client and GUI server are running on the
same host In the following GUI client and GUI server are addressed as ldquoSAPinst GUIrdquo
If you need to see the installation on a remote display we recommend that you perform a remote
installation with SAPinst where the SAPinst GUI is running on a separate host from SAPinst For more
information see Performing a Remote Installation with SAPinst in the installation documentation of your
release
Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote
access to SAPinst GUI on Windows workstations For more information see SAP Note 1170809
Useful Information About SAPinst
When you start SAPinst it automatically starts the SAPinst GUI
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2354
SAPinst creates the installation directory sapinst_instdir directly below the temporary directory
SAPinst 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 SAPinst
creates the installation directory sapinst_instdir directly below the tmp directory by default
If you want SAPinst to create the installation directory sapinst_instdir in another directory set
the environment variable TEMP to this directory before you start SAPinst
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
Only valid for IBM DB2 for i5OS |
NOTE
When you leave your Qp2Term session all changes of the environment variables done by the
command export are reverted
End of IBM DB2 for i5OS |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
SAPinst creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt
SAPinst extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is located
in the environment variables TEMP TMP or TMPDIR These files are deleted after SAPinst has stopped
running
The temporary directory sapinst_exexxxxxxxxxx sometimes remains undeleted You can safely
delete it
The temporary directory also contains the log file dev_selfexout from the extraction process
which might be useful if an error occurs
CAUTION
If SAPinst cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default ports 21200 21212 and 4239 are used for communication
between SAPinst GUI server GUI and HTTP server as follows
SAPinst uses port 21200 to communicate with the GUI server
The GUI server uses port 21212 to communicate with the GUI client
5 Splitting
52 Running SAPinst
2454 PUBLIC 2012-04-11
4239 is the port of the HTTP server which is part of the GUI server
If the ports for SAPinst and the GUI server are already in use SAPinst automatically searches for
free port numbers If the search fails SAPinst exits
In this case or if you want SAPinst to use specific ports you can assign them by executing the
sapinst executable with the following command line parameters
SAPINST_DIALOG_PORT=ltport_number_sapinst_to_gui_servergt
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
GUISERVER_HTTP_PORT=ltport_number_http_servergt
To see a list of all available SAPinst properties start SAPinst as described above with command line
parameter -p
sapinst -p
If you need to run SAPinst in accessibility mode proceed as described in Running SAPinst in Accessibility
Mode in the installation documentation of your release
If required you can stop SAPinst by choosing SAPinst Cancel in the SAPinst GUI menu
Prerequisites
We recommend that you use the csh shell for the installation with SAPinst If you want to use
another shell make sure that you have first read SAP Note 202227
SAPinst uses csh scripts during the installation to obtain the environment for user ltsapsidgtadm
This is also true if user ltsapsidgtadm already exists from an earlier SAP system installation and the
shell of this user is not csh Before you start SAPinst execute the following command as user
ltsapsidgtadm to make sure that the csh scripts are up-to-date
bincsh -c source lthome directory of ltsapsidgtadmgtcshrcenv
Make sure that you have specified the most important SAP system parameters as described in Basic
SAP System Installation Parameters in the installation documentation of your release before you start
SAPinst
Only valid for IBM DB2 for zOS |
Check that your installation hosts meet the requirements for the installation options that you
want to installEnd of IBM DB2 for zOS |
Only valid for Non-Standalone Engines and Clients |
If you want to perform a distributed or a high-availability installation make sure that you have
exported and mounted global directories For more information see Exporting and Mounting Global
Directories in the installation documentation of your releaseEnd of Non-Standalone Engines and Clients |
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you have carefully planned your database layout in particular the tablespace layout
as described in Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2554
Only valid for AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for Solaris |
Solaris SPARC onlyEnd of Solaris |
If you want to set up DB2s high-availability cluster solution SA MP make sure that you have read
the document IBM DB2 High Availability Solution IBM Tivoli System Automation for Multiplatforms at
httpservicesapcominstguidesnw70 Installation Installation ndash SAP NetWeaver SystemsEnd of AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for zOS |
First make sure that you have installed DB2 for zOS For information on that installation see
SAP DBA Guide DB2 for zOS DB2 Setup especially the section Stored Procedures EnablementEnd of IBM DB2 for zOS |
Check the value of the environment variable TEMP TMP or TMPDIR
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
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 ndash for example by using a crontab entry
Make sure that you have at least 60 MB of free space in the installation directory for each
installation option In addition you need 200 MB free space for the SAPinst executables If you
cannot provide 200 MB free space in the temporary directory you can set one of the
environment variables TEMP TMP or TMPDIR to another directory with 200 MB free space for
the SAPinst executables
Make sure that the temporary directory has the permissions 777
Only valid for IBM DB2 for zOS |
Make sure that your database is up and runningEnd of IBM DB2 for zOS |
Make sure that your DISPLAY environment variable is set to lthost_namegt00 where
lthost_namegt is the host on which you want to display the GUI
Shell Used Command
Bourne shell (sh) DISPLAY=lthost_namegt00
export DISPLAY
C shell (csh) setenv DISPLAY lthost_namegt00
Korn shell (ksh) export DISPLAY=lthost_namegt00
Make sure that umask is set to 022 for user root
As user root enter the following command umask 022
Check the following values for user root
5 Splitting
52 Running SAPinst
2654 PUBLIC 2012-04-11
In csh execute limit
Output Properties
cputime unlimited
filesize unlimited
datasize unlimited
stacksize 8192 KB
coredumpsize unlimited
descriptors 8192
memorysize unlimited
In sh or ksh execute ulimit -a
Output Properties
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192
coredump(blocks) unlimited
nofiles(descriptors) 8192
memory(KBytes) unlimited
If your parameter settings differ from those above change these values accordingly
EXAMPLE
If you have to change the value for descriptors to 8192 proceed as follows
In csh execute
limit descriptors 8192
In sh or ksh execute
ulimit -n 8192
Before you start SAPinst read SAP Note 1697164 for more information about which user to choose
for running the SAPinst SDT GUI server
Procedure
1 Log on to the installation host as user root
CAUTION
Do not use an existing ltsapsidgtadm user
Only valid for Non-Standalone Engines and Clients |
CAUTION
Make sure that the root user has not set any environment variables for a different SAP system
or database
End of Non-Standalone Engines and Clients |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2754
2 Make the Dual-Stack Split Tool available on the installation host Make sure that it is available
locally We do not recommend that you use Network File System (NFS) because reading from
media mounted with NFS might fail
For more information see Preparation Checklist [page 17] and Preparing the Installation Media in the
installation documentation of your release
3 Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
Only valid for Non-Standalone Engines and Clients |
Change to the directory with the sapinst executable for your operating system by entering the
following command cd ltMountpoint of Installation Master mediumgtDATA_UNITS
ltproductgt_IM_ltOSgtEnd of Non-Standalone Engines and Clients |
End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
4 Start SAPinst by executing the following command sapinst
NOTE
If you want to use a virtual host name start SAPinst with the SAPinst property
SAPINST_USE_HOSTNAME as follows
Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
sapinst SAPINST_USE_HOSTNAME=ltvirtual host namegt
End of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
5 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
In addition if you want to use the split option ldquoMove Java Databaserdquo choose ltYour System
Variantgt
Perform the export and installation steps exactly in the order in which they appear
6 Only valid for Non-Standalone Engines and Clients |
Choose NextEnd of Non-Standalone Engines and Clients |
7 Follow the instructions in the SAPinst input screens and enter the required parameters
NOTE
If SAPinst asks for the Java DVD make sure that you provide a Java DVD with the same
release level as your dual-stack system
For more information about the input parameters position the cursor on the parameter
and press F1
After you have entered all requested input parameters SAPinst displays the Parameter Summary screen
This screen shows both the parameters that you entered and those that SAPinst set by default If
required you can revise the parameters before starting the split procedure
5 Splitting
52 Running SAPinst
2854 PUBLIC 2012-04-11
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you check the following parameters depending on the installation type that you
have chosenEnd of IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for Linux and UNIX and Windows |
If you are performing a typical installation SAPinst creates four sapdata directories by
default If you require more or fewer sapdata directories depending on the storage devices
you are using you must change this parameter before you start the installation By selecting
this parameter on the Summary screen and choosing Revise SAPinst returns to the IBM DB2 for
Linux UNIX and Windows ndashgt Sapdata Directories screen
On this screen you can also decide if you want SAPinst to create the regular table and index
tablespaces with DB2s automatic storage management enabled By default the option for
automatic storage management is preselected
NOTE
As of DB2 V91 and higher the database and the SYSCATSPACE tablespace are always created
with automatic storage management enabled even if you deselect this option on the
dialog IBM DB2 for Linux UNIX and Windows gt Sapdata Directories
For more information about DB2s automatic storage management see section DB2
Tablespaces in the installation documentation of your SAP product
If you are performing a custom installation you set these parameters during the Define
Parameters phase of SAPinst
NOTE
If the tablespace layout used by SAPinst does not meet your requirements you can create
the tablespaces manually by deselecting the option Create Tablespaces with SAPinst on the
IBM DB2 for Linux and UNIX and Windows Sapdata Directories screen
During the installation phase SAPinst then displays the following message
You must create the tablespaces now To do so use the
createTablespacessql script that is located in your installation
directory
To continue the installation choose OK Alternatively you can cancel
SAPinst here and restart it again
SAPinst does not check the page size of tablespaces that have either been created manually
or that already exist If you create the tablespaces manually you must make sure that
you use a page size of 16 KBEnd of IBM DB2 for Linux and UNIX and Windows |
8 To start the dual-stack split choose Start
SAPinst starts and displays the progress of the split procedure
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2954
When the split option has finished successfully SAPinst displays the message Execution of
ltOption_Namegt has completed
Only valid for Oracle |
NOTE
When installing the Oracle database instance SAPinst stops the installation and prompts
you to install the Oracle database software For more information see Installing the Oracle
Database Software in the installation documentation of your release
After you have finished the installation of the Oracle database you continue the database
instance installation by choosing OK in the GUI of the database instance installation
Check SAP Note 1431800 for technical information about Oracle Release 112 in SAP
environments
End of Oracle |
Only valid for Enterprise Portal (EP) |
NOTE
During the final restart of Application Server Java performed by SAPinst the portal starts the
processing and uploading of the new portal archives It takes approximately 15 to 90 minutes
before the deployment is completed and the portal is launched
Do not stop SAPinst or Application Server Java during this phase
End of Enterprise Portal (EP) |
9 If required delete directories with the name sapinst_exexxxxxxxxxx after SAPinst has finished
Sometimes these remain in the temporary directory
NOTE
If there are errors with the SAPinst extraction process you can find the log file
dev_selfexout in the temporary directory
Only valid for Non-Standalone Engines and Clients |
RECOMMENDATION
Keep all installation 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 installation 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 installation directories on installation hosts but make sure
that you delete them after saving them separately
End of Non-Standalone Engines and Clients |
10 We recommend that you delete the directory ltuser_homegtsdtgui
11 Only valid for IBM DB2 for Linux and UNIX and Windows |
If not already done install the DB2 license
5 Splitting
52 Running SAPinst
3054 PUBLIC 2012-04-11
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
End of IBM DB2 for Linux and UNIX and Windows |
12 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 3154
This page is left blank for documents that are printed on both sides
6 Follow-Up Activities
61 Follow-Up Activities Checklist
This section includes the follow-up activities that you have to perform for the following split options
ldquoMove Java Databaserdquo for a central system
ldquoMove Java Databaserdquo for a distributed system or a high-availability system
ldquoKeep Databaserdquo for a central distributed or high-availability system
NOTE
Some of the follow-up activities listed in this section are not described in this documentation You
can find the detailed description in the SAP NetWeaver Application Server Java system copy
documentation relevant for your release at
httpservicesapcominstguides
Move Java Database
Central System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3354
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
7 We recommend that you perform regression testing
8 On the source system you run SAPinst [page 23] to remove the Java parts in the file system and in
the database
9 On the source system you call transaction RZ10 to reimport the profiles from the file system
10 In the Transport Management System (TMS) you configure the transport routes [page 38]
11 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
12 You clean up the system landscape data [page 40]
Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3454 PUBLIC 2012-04-11
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the database host of the source system you run SAPinst [page 23] to remove the Java database
schema
12 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
13 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
14 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
15 You clean up the system landscape data [page 40]
Keep Database
Central Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3554
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
12 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
13 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
14 You clean up the system landscape data [page 40]
62 Maintaining the Connection to the System Landscape Directory
After installing the Java system you need to reconfigure the connection between the System Landscape
Directory (SLD) the source system and the target system The steps required differ depending on
whether you use a local or a central SLD To maintain the connection to the SLD you can either run
the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split or perform the required steps manually as described below
NOTE
This step is only required if the connection to the SLD was established on the source system before
the split
Prerequisites
If you want to use the configuration wizard you need an SAP NetWeaver Java system 70 Support
Package 14 or higher in your landscape
SLDAPIUSER credentials are available in the ABAP system
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3654 PUBLIC 2012-04-11
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
This page is left blank for documents that are printed on both sides
2 Split Options Covered by this Guide
This section shows the split options covered by this guide You have to decide which option you want
to use because the steps you have to perform vary according to the split option that you choose
Move Java Database [page 9]
Keep Database [page 11]
21 Split Option Move Java Database
The split option ldquoMove Java Databaserdquo offers the possibility to split a dual-stack system into one ABAP
system and one Java system each with its own database (non-MCOD)
Move Java Database for Central Systems
When you choose the ldquoMove Java Databaserdquo option for a central system SAPinst exports the Java stack
of the dual-stack system and uses this export to reinstall all main instances on a single host This equates
to an installation of a central system
These are the following instances
Central instance (CI)
Central services instance for Java (SCS)
Database instance (DB)
NOTE
If required you can install the central instance and the central services instance on the ABAP
system host again
Once the installation has finished and after the System Landscape Directory has been reconfigured
SAPinst removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
2012-04-11 PUBLIC 954
Figure 1 Split Option Move Java Database for Central Systems
Move Java Database for Distributed System
When you choose the ldquoMove Java Databaserdquo option for a distributed system SAPinst exports the Java
stack of the dual-stack system and uses this export to reinstall the main instances on several hosts
Every instance can run on a separate host This equates to an installation of a distributed system
These are the following instances
Central instance (CI)
Central services instance for Java (SCS)
Database instance (DB)
NOTE
If required you can reinstall the central instance and the central services instance on the ABAP
system hosts
After the installation has finished and the System Landscape Directory has been reconfigured SAPinst
removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
1054 PUBLIC 2012-04-11
Figure 2 Split Option Move Java Database for Distributed System
22 Split Option Keep Database
The split option ldquoKeep Databaserdquo offers the possibility for the Java system to reuse the existing database
of the dual-stack system using MCOD (multiple components ndash one database)
Keep Database for Central and Distributed Systems
When you choose the ldquoKeep Databaserdquo option SAPinst exports the Java file system on the dual-stack
system It uses this export to reinstall a central services instance (SCS) and a central instance (CI) for
Java They can be installed on one host on different hosts or on the source system hosts again
Additionally SAPinst adapts the Java schema of the database of the dual-stack system to the target Java
system
After the installation has finished and the System Landscape Directory has been reconfigured SAPinst
removes all Java parts from the dual-stack system except the Java database schema
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-04-11 PUBLIC 1154
Figure 3 Split Option Keep Database for Central Systems
Figure 4 Split Option Keep Database for Distributed Systems
2 Split Options Covered by this Guide
22 Split Option Keep Database
1254 PUBLIC 2012-04-11
3 Planning
31 Planning Checklist
This section includes the planning steps that you have to perform when you want to install the new
Java system on one or more hosts Perform the planning steps according to the split option and your
system variant
NOTE
Most of the required planning steps listed in this section are not described in this documentation
You can find the detailed description in the SAP NetWeaver Application Server Java installation
documentation relevant for your release at httpservicesapcominstguides
Prerequisites
You have decided on your split option [page 9]
Split Option ldquoMove Java Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
1 You check the hardware and software requirements for the Java installation host
For more information see Hardware and Software Requirements in the installation documentation of
your release
2 You read about user management [page 15]
3 You identify basic SAP system installation parameters
For more information see Basic SAP System Parameters in the installation documentation of your
release
Be aware of the following dual-stack-split-specific deviations
SAP System Parameters
User management
We do not recommend that you make modifications in the user management settings
For more information see User Management [page 15]
System Landscape Directory (SLD)
You can ignore SLD parameters
Only valid for Oracle |
SAP System Database Parameters Java database schema
We recommend that you choose a schema ID that is different from your SAP system ID
It might cause problems when you copy a system if ltSCHEMA_IDgt is the same as ltSAPSIDgt and
the database-specific method used for the copy does not allow you to rename the database
3 Planning
31 Planning Checklist
2012-04-11 PUBLIC 1354
schemes In certain situations you might create a system copy with a new ltSAPSIDgt but where
the database schema has the old ltSAPSIDgt This is not a technical problem but might be
confusing to the system administratorEnd of Oracle |
4 Only valid for MaxDB |
You plan your system configuration
For more information see System Configuration in the installation documentation of your releaseEnd of MaxDB |
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
You plan the setup of your database carefully
For more information see Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
7 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 43]
8 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
9 Only valid for IBM DB2 for zOS |
If you want to execute a Software Life-Cycle Option with SAPinst in an SAP system with thick client
connectivity see Special Considerations Regarding Connectivity for Software Life-Cycle Options in the installation
documentation of your releaseEnd of IBM DB2 for zOS |
10 Only valid for IBM DB2 for i5OS |
Optionally you decide whether you want to install multiple SAP systems on a single host
For more information see Multiple SAP Systems on a Single Host in the installation documentation of
your releaseEnd of IBM DB2 for i5OS |
11 You can continue with Preparation [page 17]
Split Option ldquoKeep Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
1 You check the hardware and software requirements for the Java installation host
For more information see Hardware and Software Requirements in the installation documentation of
your release
2 You read about user management [page 15]
3 You identify basic SAP system installation parameters
For more information see Basic SAP System Parameters in the installation documentation of your
release
3 Planning
31 Planning Checklist
1454 PUBLIC 2012-04-11
Be aware of the following dual-stack-split-specific deviation for SAP System Parameters
User management
We do not recommend that you make modifications in the user management settings For
more information see User Management [page 15]
System Landscape Directory (SLD)
You can ignore SLD parameters
4 Only valid for IBM DB2 for zOSMaxDB |
You plan your system configuration
For more information see System Configuration in the installation documentation of your releaseEnd of IBM DB2 for zOSMaxDB |
5 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
6 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 43]
7 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
8 Only valid for IBM DB2 for zOS |
If you want to execute a Software Life-Cycle Option with SAPinst in an SAP system with thick client
connectivity see Special Considerations Regarding Connectivity for Software Life-Cycle Options in the installation
documentation of your releaseEnd of IBM DB2 for zOS |
9 Only valid for IBM DB2 for i5OS |
Optionally you decide whether you want to install multiple SAP systems on a single host
For more information see Multiple SAP Systems on a Single Host in the installation documentation of
your releaseEnd of IBM DB2 for i5OS |
10 You can continue with Preparation [page 17]
32 User Management
The dual-stack split procedure does not change the user management and you cannot choose which
kind of user management you want to use for the target AS Java system That is the separated Java
system and the ABAP system both use the user management of the former dual-stack system The
following is possible
If the dual-stack system uses AS ABAP as data source for the User Management Engine (UME)
after the split the separated Java stack will also use the ABAP UME
If the dual-stack system uses an LDAP directory as source for user data this is also valid for the Java
stack
3 Planning
32 User Management
2012-04-11 PUBLIC 1554
In both cases manual configuration is not required
We do not recommend that you make modifications to the user management settings
For more information see SAP Note 718383
3 Planning
32 User Management
1654 PUBLIC 2012-04-11
4 Preparation
41 Preparation Checklist
This section includes the preparation steps that you have to perform when you want to install the new
Java system on one or more hosts
NOTE
Most of the required preparation steps listed in this section are not described in this
documentation You can find the detailed description in the SAP NetWeaver Application Server
Java installation documentation relevant for your release at httpservicesapcom
instguides
1 Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
You make sure that the required operating system users and groups are created
To create the groups and users automatically run the Dual-Stack Split Tool on the host where
the SAP Java system is to be installed and choose Dual-Stack Split Operating System Users and
Groups
For more information see Creating Operating System Users and Groups in the installation documentation
of your releaseEnd of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
2 You set up file systems and make sure that the required disk space is available for the directories
to be created during the installation
For more information see Setting Up File Systems for a High-Availability System in the installation
documentation of your release
3 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
4 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
If you want to install a high-availability system you perform switchover preparations
For more information see Performing Switchover Preparations for High-Availability in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
5 If you want to share the transport directory trans from another system you export this directory
to your installation hosts
For more information see Exporting and Mounting the Global Transport Directory in the installation
documentation of your release
4 Preparation
41 Preparation Checklist
2012-04-11 PUBLIC 1754
6 You install the Java Development Kit This step is not required if you have installed the SAP JVM
4 on your source system
For more information see Installing the Java Development Kit in the installation documentation of your
release
7 You make sure that the required installation media are available on each host
You can download the Dual-Stack Split Tool at httpservicesapcomsltoolset
Software Logistics Toolset 10 Dual-Stack Split
You can download the Java stack and database installation media from SAP Service
Marketplace as described in Preparing the Installation Media in the installation documentation of
your release
NOTE
The release level required for the installation corresponds to the release level of your dual-
stack system
The following table shows the required installation media for the dual-stack split
SAP Instance Installation Required Media
Central services instance central instance
Dual-Stack Split Tool Java DVD RDBMS Client DVD
Move Java Database only Database instance
Dual-Stack Split Tool Java DVD Only valid for MS SQL ServerOracle |
RDBMS DVDEnd of MS SQL ServerOracle |
Only valid for MS SQL ServerOracle |
RDBMS Patch DVD (if available)End of MS SQL ServerOracle |
8 Only valid for HA (MSCS) |
To install a high-availability system with Microsoft Cluster Service (MSCS) you also perform the
MSCS-specific preparation tasks as described in the installation documentation of your releaseEnd of HA (MSCS) |
9 Only valid for HA (MSCS) |
If you choose the split option ldquoKeep Databaserdquo with the scenario ldquoKeep SCS on the Source Cluster
Systemrdquo you perform the following steps
You provide additional disk storage on the target cluster system
For more information see Distribution of SAP System Components to Disks for MSCS Directories in an
MSCS Configuration and IP Addresses in an MSCS Configuration in the installation documentation of
your release
You provide an additional IP address and an additional virtual host name for the Java system
For more information see Mapping Host Names to IP Addresses for MSCS in the installation
documentation of your releaseEnd of HA (MSCS) |
4 Preparation
41 Preparation Checklist
1854 PUBLIC 2012-04-11
10 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 19] of
the dual-stack system
11 You can continue with Splitting [page 21]
42 Performing a Full System Backup
If you decided to use the split option ldquoKeep Databaserdquo you must perform a full system backup of the
dual-stack system or at least a backup of the Java database schema before you start the split procedure
If you decided to use the split option ldquoMove Java Databaserdquo you do not need to perform a backup before
you start the split procedure
For more information about backing up your database see the database-specific backup and recovery
documentation in the SAP Library [page 7] at
SAP MaxDB
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for SAP
MaxDB
Oracle
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Oracle
IBM DB2 for i5OS
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 UDB for iSeries
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for i
4 Preparation
42 Performing a Full System Backup
2012-04-11 PUBLIC 1954
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
i
IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX
and Windows
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
Linux UNIX and Windows
IBM DB2 for zOS
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 UDB for zOS
SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for DB2 for z
OS
Microsoft SQL Server
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Microsoft SQL
Server
4 Preparation
42 Performing a Full System Backup
2054 PUBLIC 2012-04-11
5 Splitting
51 Splitting Checklist
This section includes the splitting steps that you have to perform for the following split options
ldquoMove Java Databaserdquo
ldquoKeep Databaserdquo
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Only valid for Oracle |
You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 You export the Java stack using SAPinst [page 23]
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
4 You restart the source system
5 You run SAPinst [page 23] to install a Java only system using the export from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2012-04-11 PUBLIC 2154
Distributed System
1 Only valid for Oracle |
On the database instance host of the dual-stack system you install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes on the database instance host
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 On the database instance host of the dual-stack system you run SAPinst [page 23] to export the
Java database schema
4 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the Java
parts of the file system of the central instance
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
5 You restart the source system
6 You run SAPinst [page 23] to install a central services instance for the Java target system
7 You run SAPinst [page 23] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
9 You continue with Follow-Up Activities [page 33]
Keep Database
1 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the
file system of the central instance
5 Splitting
51 Splitting Checklist
2254 PUBLIC 2012-04-11
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you wont use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
2 You restart the source system
3 You run SAPinst [page 23] to install a central services instance for the Java target system
4 On the database instance host of the dual-stack system you run SAPinst [page 23] to adapt the
database for the Java target system
NOTE
Make sure that you enter the profile directory of the Java target system in the SAP System gt
General Parameters screen
5 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
52 Running SAPinst
This section describes how to run the installation tool SAPinst SAPinst includes a GUI client and a GUI
server which both use Java
The procedure describes an installation where SAPinst GUI client and GUI server are running on the
same host In the following GUI client and GUI server are addressed as ldquoSAPinst GUIrdquo
If you need to see the installation on a remote display we recommend that you perform a remote
installation with SAPinst where the SAPinst GUI is running on a separate host from SAPinst For more
information see Performing a Remote Installation with SAPinst in the installation documentation of your
release
Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote
access to SAPinst GUI on Windows workstations For more information see SAP Note 1170809
Useful Information About SAPinst
When you start SAPinst it automatically starts the SAPinst GUI
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2354
SAPinst creates the installation directory sapinst_instdir directly below the temporary directory
SAPinst 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 SAPinst
creates the installation directory sapinst_instdir directly below the tmp directory by default
If you want SAPinst to create the installation directory sapinst_instdir in another directory set
the environment variable TEMP to this directory before you start SAPinst
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
Only valid for IBM DB2 for i5OS |
NOTE
When you leave your Qp2Term session all changes of the environment variables done by the
command export are reverted
End of IBM DB2 for i5OS |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
SAPinst creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt
SAPinst extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is located
in the environment variables TEMP TMP or TMPDIR These files are deleted after SAPinst has stopped
running
The temporary directory sapinst_exexxxxxxxxxx sometimes remains undeleted You can safely
delete it
The temporary directory also contains the log file dev_selfexout from the extraction process
which might be useful if an error occurs
CAUTION
If SAPinst cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default ports 21200 21212 and 4239 are used for communication
between SAPinst GUI server GUI and HTTP server as follows
SAPinst uses port 21200 to communicate with the GUI server
The GUI server uses port 21212 to communicate with the GUI client
5 Splitting
52 Running SAPinst
2454 PUBLIC 2012-04-11
4239 is the port of the HTTP server which is part of the GUI server
If the ports for SAPinst and the GUI server are already in use SAPinst automatically searches for
free port numbers If the search fails SAPinst exits
In this case or if you want SAPinst to use specific ports you can assign them by executing the
sapinst executable with the following command line parameters
SAPINST_DIALOG_PORT=ltport_number_sapinst_to_gui_servergt
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
GUISERVER_HTTP_PORT=ltport_number_http_servergt
To see a list of all available SAPinst properties start SAPinst as described above with command line
parameter -p
sapinst -p
If you need to run SAPinst in accessibility mode proceed as described in Running SAPinst in Accessibility
Mode in the installation documentation of your release
If required you can stop SAPinst by choosing SAPinst Cancel in the SAPinst GUI menu
Prerequisites
We recommend that you use the csh shell for the installation with SAPinst If you want to use
another shell make sure that you have first read SAP Note 202227
SAPinst uses csh scripts during the installation to obtain the environment for user ltsapsidgtadm
This is also true if user ltsapsidgtadm already exists from an earlier SAP system installation and the
shell of this user is not csh Before you start SAPinst execute the following command as user
ltsapsidgtadm to make sure that the csh scripts are up-to-date
bincsh -c source lthome directory of ltsapsidgtadmgtcshrcenv
Make sure that you have specified the most important SAP system parameters as described in Basic
SAP System Installation Parameters in the installation documentation of your release before you start
SAPinst
Only valid for IBM DB2 for zOS |
Check that your installation hosts meet the requirements for the installation options that you
want to installEnd of IBM DB2 for zOS |
Only valid for Non-Standalone Engines and Clients |
If you want to perform a distributed or a high-availability installation make sure that you have
exported and mounted global directories For more information see Exporting and Mounting Global
Directories in the installation documentation of your releaseEnd of Non-Standalone Engines and Clients |
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you have carefully planned your database layout in particular the tablespace layout
as described in Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2554
Only valid for AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for Solaris |
Solaris SPARC onlyEnd of Solaris |
If you want to set up DB2s high-availability cluster solution SA MP make sure that you have read
the document IBM DB2 High Availability Solution IBM Tivoli System Automation for Multiplatforms at
httpservicesapcominstguidesnw70 Installation Installation ndash SAP NetWeaver SystemsEnd of AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for zOS |
First make sure that you have installed DB2 for zOS For information on that installation see
SAP DBA Guide DB2 for zOS DB2 Setup especially the section Stored Procedures EnablementEnd of IBM DB2 for zOS |
Check the value of the environment variable TEMP TMP or TMPDIR
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
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 ndash for example by using a crontab entry
Make sure that you have at least 60 MB of free space in the installation directory for each
installation option In addition you need 200 MB free space for the SAPinst executables If you
cannot provide 200 MB free space in the temporary directory you can set one of the
environment variables TEMP TMP or TMPDIR to another directory with 200 MB free space for
the SAPinst executables
Make sure that the temporary directory has the permissions 777
Only valid for IBM DB2 for zOS |
Make sure that your database is up and runningEnd of IBM DB2 for zOS |
Make sure that your DISPLAY environment variable is set to lthost_namegt00 where
lthost_namegt is the host on which you want to display the GUI
Shell Used Command
Bourne shell (sh) DISPLAY=lthost_namegt00
export DISPLAY
C shell (csh) setenv DISPLAY lthost_namegt00
Korn shell (ksh) export DISPLAY=lthost_namegt00
Make sure that umask is set to 022 for user root
As user root enter the following command umask 022
Check the following values for user root
5 Splitting
52 Running SAPinst
2654 PUBLIC 2012-04-11
In csh execute limit
Output Properties
cputime unlimited
filesize unlimited
datasize unlimited
stacksize 8192 KB
coredumpsize unlimited
descriptors 8192
memorysize unlimited
In sh or ksh execute ulimit -a
Output Properties
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192
coredump(blocks) unlimited
nofiles(descriptors) 8192
memory(KBytes) unlimited
If your parameter settings differ from those above change these values accordingly
EXAMPLE
If you have to change the value for descriptors to 8192 proceed as follows
In csh execute
limit descriptors 8192
In sh or ksh execute
ulimit -n 8192
Before you start SAPinst read SAP Note 1697164 for more information about which user to choose
for running the SAPinst SDT GUI server
Procedure
1 Log on to the installation host as user root
CAUTION
Do not use an existing ltsapsidgtadm user
Only valid for Non-Standalone Engines and Clients |
CAUTION
Make sure that the root user has not set any environment variables for a different SAP system
or database
End of Non-Standalone Engines and Clients |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2754
2 Make the Dual-Stack Split Tool available on the installation host Make sure that it is available
locally We do not recommend that you use Network File System (NFS) because reading from
media mounted with NFS might fail
For more information see Preparation Checklist [page 17] and Preparing the Installation Media in the
installation documentation of your release
3 Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
Only valid for Non-Standalone Engines and Clients |
Change to the directory with the sapinst executable for your operating system by entering the
following command cd ltMountpoint of Installation Master mediumgtDATA_UNITS
ltproductgt_IM_ltOSgtEnd of Non-Standalone Engines and Clients |
End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
4 Start SAPinst by executing the following command sapinst
NOTE
If you want to use a virtual host name start SAPinst with the SAPinst property
SAPINST_USE_HOSTNAME as follows
Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
sapinst SAPINST_USE_HOSTNAME=ltvirtual host namegt
End of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
5 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
In addition if you want to use the split option ldquoMove Java Databaserdquo choose ltYour System
Variantgt
Perform the export and installation steps exactly in the order in which they appear
6 Only valid for Non-Standalone Engines and Clients |
Choose NextEnd of Non-Standalone Engines and Clients |
7 Follow the instructions in the SAPinst input screens and enter the required parameters
NOTE
If SAPinst asks for the Java DVD make sure that you provide a Java DVD with the same
release level as your dual-stack system
For more information about the input parameters position the cursor on the parameter
and press F1
After you have entered all requested input parameters SAPinst displays the Parameter Summary screen
This screen shows both the parameters that you entered and those that SAPinst set by default If
required you can revise the parameters before starting the split procedure
5 Splitting
52 Running SAPinst
2854 PUBLIC 2012-04-11
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you check the following parameters depending on the installation type that you
have chosenEnd of IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for Linux and UNIX and Windows |
If you are performing a typical installation SAPinst creates four sapdata directories by
default If you require more or fewer sapdata directories depending on the storage devices
you are using you must change this parameter before you start the installation By selecting
this parameter on the Summary screen and choosing Revise SAPinst returns to the IBM DB2 for
Linux UNIX and Windows ndashgt Sapdata Directories screen
On this screen you can also decide if you want SAPinst to create the regular table and index
tablespaces with DB2s automatic storage management enabled By default the option for
automatic storage management is preselected
NOTE
As of DB2 V91 and higher the database and the SYSCATSPACE tablespace are always created
with automatic storage management enabled even if you deselect this option on the
dialog IBM DB2 for Linux UNIX and Windows gt Sapdata Directories
For more information about DB2s automatic storage management see section DB2
Tablespaces in the installation documentation of your SAP product
If you are performing a custom installation you set these parameters during the Define
Parameters phase of SAPinst
NOTE
If the tablespace layout used by SAPinst does not meet your requirements you can create
the tablespaces manually by deselecting the option Create Tablespaces with SAPinst on the
IBM DB2 for Linux and UNIX and Windows Sapdata Directories screen
During the installation phase SAPinst then displays the following message
You must create the tablespaces now To do so use the
createTablespacessql script that is located in your installation
directory
To continue the installation choose OK Alternatively you can cancel
SAPinst here and restart it again
SAPinst does not check the page size of tablespaces that have either been created manually
or that already exist If you create the tablespaces manually you must make sure that
you use a page size of 16 KBEnd of IBM DB2 for Linux and UNIX and Windows |
8 To start the dual-stack split choose Start
SAPinst starts and displays the progress of the split procedure
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2954
When the split option has finished successfully SAPinst displays the message Execution of
ltOption_Namegt has completed
Only valid for Oracle |
NOTE
When installing the Oracle database instance SAPinst stops the installation and prompts
you to install the Oracle database software For more information see Installing the Oracle
Database Software in the installation documentation of your release
After you have finished the installation of the Oracle database you continue the database
instance installation by choosing OK in the GUI of the database instance installation
Check SAP Note 1431800 for technical information about Oracle Release 112 in SAP
environments
End of Oracle |
Only valid for Enterprise Portal (EP) |
NOTE
During the final restart of Application Server Java performed by SAPinst the portal starts the
processing and uploading of the new portal archives It takes approximately 15 to 90 minutes
before the deployment is completed and the portal is launched
Do not stop SAPinst or Application Server Java during this phase
End of Enterprise Portal (EP) |
9 If required delete directories with the name sapinst_exexxxxxxxxxx after SAPinst has finished
Sometimes these remain in the temporary directory
NOTE
If there are errors with the SAPinst extraction process you can find the log file
dev_selfexout in the temporary directory
Only valid for Non-Standalone Engines and Clients |
RECOMMENDATION
Keep all installation 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 installation 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 installation directories on installation hosts but make sure
that you delete them after saving them separately
End of Non-Standalone Engines and Clients |
10 We recommend that you delete the directory ltuser_homegtsdtgui
11 Only valid for IBM DB2 for Linux and UNIX and Windows |
If not already done install the DB2 license
5 Splitting
52 Running SAPinst
3054 PUBLIC 2012-04-11
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
End of IBM DB2 for Linux and UNIX and Windows |
12 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 3154
This page is left blank for documents that are printed on both sides
6 Follow-Up Activities
61 Follow-Up Activities Checklist
This section includes the follow-up activities that you have to perform for the following split options
ldquoMove Java Databaserdquo for a central system
ldquoMove Java Databaserdquo for a distributed system or a high-availability system
ldquoKeep Databaserdquo for a central distributed or high-availability system
NOTE
Some of the follow-up activities listed in this section are not described in this documentation You
can find the detailed description in the SAP NetWeaver Application Server Java system copy
documentation relevant for your release at
httpservicesapcominstguides
Move Java Database
Central System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3354
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
7 We recommend that you perform regression testing
8 On the source system you run SAPinst [page 23] to remove the Java parts in the file system and in
the database
9 On the source system you call transaction RZ10 to reimport the profiles from the file system
10 In the Transport Management System (TMS) you configure the transport routes [page 38]
11 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
12 You clean up the system landscape data [page 40]
Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3454 PUBLIC 2012-04-11
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the database host of the source system you run SAPinst [page 23] to remove the Java database
schema
12 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
13 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
14 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
15 You clean up the system landscape data [page 40]
Keep Database
Central Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3554
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
12 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
13 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
14 You clean up the system landscape data [page 40]
62 Maintaining the Connection to the System Landscape Directory
After installing the Java system you need to reconfigure the connection between the System Landscape
Directory (SLD) the source system and the target system The steps required differ depending on
whether you use a local or a central SLD To maintain the connection to the SLD you can either run
the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split or perform the required steps manually as described below
NOTE
This step is only required if the connection to the SLD was established on the source system before
the split
Prerequisites
If you want to use the configuration wizard you need an SAP NetWeaver Java system 70 Support
Package 14 or higher in your landscape
SLDAPIUSER credentials are available in the ABAP system
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3654 PUBLIC 2012-04-11
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
2 Split Options Covered by this Guide
This section shows the split options covered by this guide You have to decide which option you want
to use because the steps you have to perform vary according to the split option that you choose
Move Java Database [page 9]
Keep Database [page 11]
21 Split Option Move Java Database
The split option ldquoMove Java Databaserdquo offers the possibility to split a dual-stack system into one ABAP
system and one Java system each with its own database (non-MCOD)
Move Java Database for Central Systems
When you choose the ldquoMove Java Databaserdquo option for a central system SAPinst exports the Java stack
of the dual-stack system and uses this export to reinstall all main instances on a single host This equates
to an installation of a central system
These are the following instances
Central instance (CI)
Central services instance for Java (SCS)
Database instance (DB)
NOTE
If required you can install the central instance and the central services instance on the ABAP
system host again
Once the installation has finished and after the System Landscape Directory has been reconfigured
SAPinst removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
2012-04-11 PUBLIC 954
Figure 1 Split Option Move Java Database for Central Systems
Move Java Database for Distributed System
When you choose the ldquoMove Java Databaserdquo option for a distributed system SAPinst exports the Java
stack of the dual-stack system and uses this export to reinstall the main instances on several hosts
Every instance can run on a separate host This equates to an installation of a distributed system
These are the following instances
Central instance (CI)
Central services instance for Java (SCS)
Database instance (DB)
NOTE
If required you can reinstall the central instance and the central services instance on the ABAP
system hosts
After the installation has finished and the System Landscape Directory has been reconfigured SAPinst
removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
1054 PUBLIC 2012-04-11
Figure 2 Split Option Move Java Database for Distributed System
22 Split Option Keep Database
The split option ldquoKeep Databaserdquo offers the possibility for the Java system to reuse the existing database
of the dual-stack system using MCOD (multiple components ndash one database)
Keep Database for Central and Distributed Systems
When you choose the ldquoKeep Databaserdquo option SAPinst exports the Java file system on the dual-stack
system It uses this export to reinstall a central services instance (SCS) and a central instance (CI) for
Java They can be installed on one host on different hosts or on the source system hosts again
Additionally SAPinst adapts the Java schema of the database of the dual-stack system to the target Java
system
After the installation has finished and the System Landscape Directory has been reconfigured SAPinst
removes all Java parts from the dual-stack system except the Java database schema
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-04-11 PUBLIC 1154
Figure 3 Split Option Keep Database for Central Systems
Figure 4 Split Option Keep Database for Distributed Systems
2 Split Options Covered by this Guide
22 Split Option Keep Database
1254 PUBLIC 2012-04-11
3 Planning
31 Planning Checklist
This section includes the planning steps that you have to perform when you want to install the new
Java system on one or more hosts Perform the planning steps according to the split option and your
system variant
NOTE
Most of the required planning steps listed in this section are not described in this documentation
You can find the detailed description in the SAP NetWeaver Application Server Java installation
documentation relevant for your release at httpservicesapcominstguides
Prerequisites
You have decided on your split option [page 9]
Split Option ldquoMove Java Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
1 You check the hardware and software requirements for the Java installation host
For more information see Hardware and Software Requirements in the installation documentation of
your release
2 You read about user management [page 15]
3 You identify basic SAP system installation parameters
For more information see Basic SAP System Parameters in the installation documentation of your
release
Be aware of the following dual-stack-split-specific deviations
SAP System Parameters
User management
We do not recommend that you make modifications in the user management settings
For more information see User Management [page 15]
System Landscape Directory (SLD)
You can ignore SLD parameters
Only valid for Oracle |
SAP System Database Parameters Java database schema
We recommend that you choose a schema ID that is different from your SAP system ID
It might cause problems when you copy a system if ltSCHEMA_IDgt is the same as ltSAPSIDgt and
the database-specific method used for the copy does not allow you to rename the database
3 Planning
31 Planning Checklist
2012-04-11 PUBLIC 1354
schemes In certain situations you might create a system copy with a new ltSAPSIDgt but where
the database schema has the old ltSAPSIDgt This is not a technical problem but might be
confusing to the system administratorEnd of Oracle |
4 Only valid for MaxDB |
You plan your system configuration
For more information see System Configuration in the installation documentation of your releaseEnd of MaxDB |
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
You plan the setup of your database carefully
For more information see Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
7 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 43]
8 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
9 Only valid for IBM DB2 for zOS |
If you want to execute a Software Life-Cycle Option with SAPinst in an SAP system with thick client
connectivity see Special Considerations Regarding Connectivity for Software Life-Cycle Options in the installation
documentation of your releaseEnd of IBM DB2 for zOS |
10 Only valid for IBM DB2 for i5OS |
Optionally you decide whether you want to install multiple SAP systems on a single host
For more information see Multiple SAP Systems on a Single Host in the installation documentation of
your releaseEnd of IBM DB2 for i5OS |
11 You can continue with Preparation [page 17]
Split Option ldquoKeep Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
1 You check the hardware and software requirements for the Java installation host
For more information see Hardware and Software Requirements in the installation documentation of
your release
2 You read about user management [page 15]
3 You identify basic SAP system installation parameters
For more information see Basic SAP System Parameters in the installation documentation of your
release
3 Planning
31 Planning Checklist
1454 PUBLIC 2012-04-11
Be aware of the following dual-stack-split-specific deviation for SAP System Parameters
User management
We do not recommend that you make modifications in the user management settings For
more information see User Management [page 15]
System Landscape Directory (SLD)
You can ignore SLD parameters
4 Only valid for IBM DB2 for zOSMaxDB |
You plan your system configuration
For more information see System Configuration in the installation documentation of your releaseEnd of IBM DB2 for zOSMaxDB |
5 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
6 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 43]
7 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
8 Only valid for IBM DB2 for zOS |
If you want to execute a Software Life-Cycle Option with SAPinst in an SAP system with thick client
connectivity see Special Considerations Regarding Connectivity for Software Life-Cycle Options in the installation
documentation of your releaseEnd of IBM DB2 for zOS |
9 Only valid for IBM DB2 for i5OS |
Optionally you decide whether you want to install multiple SAP systems on a single host
For more information see Multiple SAP Systems on a Single Host in the installation documentation of
your releaseEnd of IBM DB2 for i5OS |
10 You can continue with Preparation [page 17]
32 User Management
The dual-stack split procedure does not change the user management and you cannot choose which
kind of user management you want to use for the target AS Java system That is the separated Java
system and the ABAP system both use the user management of the former dual-stack system The
following is possible
If the dual-stack system uses AS ABAP as data source for the User Management Engine (UME)
after the split the separated Java stack will also use the ABAP UME
If the dual-stack system uses an LDAP directory as source for user data this is also valid for the Java
stack
3 Planning
32 User Management
2012-04-11 PUBLIC 1554
In both cases manual configuration is not required
We do not recommend that you make modifications to the user management settings
For more information see SAP Note 718383
3 Planning
32 User Management
1654 PUBLIC 2012-04-11
4 Preparation
41 Preparation Checklist
This section includes the preparation steps that you have to perform when you want to install the new
Java system on one or more hosts
NOTE
Most of the required preparation steps listed in this section are not described in this
documentation You can find the detailed description in the SAP NetWeaver Application Server
Java installation documentation relevant for your release at httpservicesapcom
instguides
1 Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
You make sure that the required operating system users and groups are created
To create the groups and users automatically run the Dual-Stack Split Tool on the host where
the SAP Java system is to be installed and choose Dual-Stack Split Operating System Users and
Groups
For more information see Creating Operating System Users and Groups in the installation documentation
of your releaseEnd of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
2 You set up file systems and make sure that the required disk space is available for the directories
to be created during the installation
For more information see Setting Up File Systems for a High-Availability System in the installation
documentation of your release
3 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
4 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
If you want to install a high-availability system you perform switchover preparations
For more information see Performing Switchover Preparations for High-Availability in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
5 If you want to share the transport directory trans from another system you export this directory
to your installation hosts
For more information see Exporting and Mounting the Global Transport Directory in the installation
documentation of your release
4 Preparation
41 Preparation Checklist
2012-04-11 PUBLIC 1754
6 You install the Java Development Kit This step is not required if you have installed the SAP JVM
4 on your source system
For more information see Installing the Java Development Kit in the installation documentation of your
release
7 You make sure that the required installation media are available on each host
You can download the Dual-Stack Split Tool at httpservicesapcomsltoolset
Software Logistics Toolset 10 Dual-Stack Split
You can download the Java stack and database installation media from SAP Service
Marketplace as described in Preparing the Installation Media in the installation documentation of
your release
NOTE
The release level required for the installation corresponds to the release level of your dual-
stack system
The following table shows the required installation media for the dual-stack split
SAP Instance Installation Required Media
Central services instance central instance
Dual-Stack Split Tool Java DVD RDBMS Client DVD
Move Java Database only Database instance
Dual-Stack Split Tool Java DVD Only valid for MS SQL ServerOracle |
RDBMS DVDEnd of MS SQL ServerOracle |
Only valid for MS SQL ServerOracle |
RDBMS Patch DVD (if available)End of MS SQL ServerOracle |
8 Only valid for HA (MSCS) |
To install a high-availability system with Microsoft Cluster Service (MSCS) you also perform the
MSCS-specific preparation tasks as described in the installation documentation of your releaseEnd of HA (MSCS) |
9 Only valid for HA (MSCS) |
If you choose the split option ldquoKeep Databaserdquo with the scenario ldquoKeep SCS on the Source Cluster
Systemrdquo you perform the following steps
You provide additional disk storage on the target cluster system
For more information see Distribution of SAP System Components to Disks for MSCS Directories in an
MSCS Configuration and IP Addresses in an MSCS Configuration in the installation documentation of
your release
You provide an additional IP address and an additional virtual host name for the Java system
For more information see Mapping Host Names to IP Addresses for MSCS in the installation
documentation of your releaseEnd of HA (MSCS) |
4 Preparation
41 Preparation Checklist
1854 PUBLIC 2012-04-11
10 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 19] of
the dual-stack system
11 You can continue with Splitting [page 21]
42 Performing a Full System Backup
If you decided to use the split option ldquoKeep Databaserdquo you must perform a full system backup of the
dual-stack system or at least a backup of the Java database schema before you start the split procedure
If you decided to use the split option ldquoMove Java Databaserdquo you do not need to perform a backup before
you start the split procedure
For more information about backing up your database see the database-specific backup and recovery
documentation in the SAP Library [page 7] at
SAP MaxDB
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for SAP
MaxDB
Oracle
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Oracle
IBM DB2 for i5OS
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 UDB for iSeries
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for i
4 Preparation
42 Performing a Full System Backup
2012-04-11 PUBLIC 1954
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
i
IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX
and Windows
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
Linux UNIX and Windows
IBM DB2 for zOS
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 UDB for zOS
SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for DB2 for z
OS
Microsoft SQL Server
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Microsoft SQL
Server
4 Preparation
42 Performing a Full System Backup
2054 PUBLIC 2012-04-11
5 Splitting
51 Splitting Checklist
This section includes the splitting steps that you have to perform for the following split options
ldquoMove Java Databaserdquo
ldquoKeep Databaserdquo
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Only valid for Oracle |
You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 You export the Java stack using SAPinst [page 23]
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
4 You restart the source system
5 You run SAPinst [page 23] to install a Java only system using the export from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2012-04-11 PUBLIC 2154
Distributed System
1 Only valid for Oracle |
On the database instance host of the dual-stack system you install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes on the database instance host
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 On the database instance host of the dual-stack system you run SAPinst [page 23] to export the
Java database schema
4 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the Java
parts of the file system of the central instance
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
5 You restart the source system
6 You run SAPinst [page 23] to install a central services instance for the Java target system
7 You run SAPinst [page 23] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
9 You continue with Follow-Up Activities [page 33]
Keep Database
1 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the
file system of the central instance
5 Splitting
51 Splitting Checklist
2254 PUBLIC 2012-04-11
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you wont use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
2 You restart the source system
3 You run SAPinst [page 23] to install a central services instance for the Java target system
4 On the database instance host of the dual-stack system you run SAPinst [page 23] to adapt the
database for the Java target system
NOTE
Make sure that you enter the profile directory of the Java target system in the SAP System gt
General Parameters screen
5 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
52 Running SAPinst
This section describes how to run the installation tool SAPinst SAPinst includes a GUI client and a GUI
server which both use Java
The procedure describes an installation where SAPinst GUI client and GUI server are running on the
same host In the following GUI client and GUI server are addressed as ldquoSAPinst GUIrdquo
If you need to see the installation on a remote display we recommend that you perform a remote
installation with SAPinst where the SAPinst GUI is running on a separate host from SAPinst For more
information see Performing a Remote Installation with SAPinst in the installation documentation of your
release
Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote
access to SAPinst GUI on Windows workstations For more information see SAP Note 1170809
Useful Information About SAPinst
When you start SAPinst it automatically starts the SAPinst GUI
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2354
SAPinst creates the installation directory sapinst_instdir directly below the temporary directory
SAPinst 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 SAPinst
creates the installation directory sapinst_instdir directly below the tmp directory by default
If you want SAPinst to create the installation directory sapinst_instdir in another directory set
the environment variable TEMP to this directory before you start SAPinst
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
Only valid for IBM DB2 for i5OS |
NOTE
When you leave your Qp2Term session all changes of the environment variables done by the
command export are reverted
End of IBM DB2 for i5OS |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
SAPinst creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt
SAPinst extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is located
in the environment variables TEMP TMP or TMPDIR These files are deleted after SAPinst has stopped
running
The temporary directory sapinst_exexxxxxxxxxx sometimes remains undeleted You can safely
delete it
The temporary directory also contains the log file dev_selfexout from the extraction process
which might be useful if an error occurs
CAUTION
If SAPinst cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default ports 21200 21212 and 4239 are used for communication
between SAPinst GUI server GUI and HTTP server as follows
SAPinst uses port 21200 to communicate with the GUI server
The GUI server uses port 21212 to communicate with the GUI client
5 Splitting
52 Running SAPinst
2454 PUBLIC 2012-04-11
4239 is the port of the HTTP server which is part of the GUI server
If the ports for SAPinst and the GUI server are already in use SAPinst automatically searches for
free port numbers If the search fails SAPinst exits
In this case or if you want SAPinst to use specific ports you can assign them by executing the
sapinst executable with the following command line parameters
SAPINST_DIALOG_PORT=ltport_number_sapinst_to_gui_servergt
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
GUISERVER_HTTP_PORT=ltport_number_http_servergt
To see a list of all available SAPinst properties start SAPinst as described above with command line
parameter -p
sapinst -p
If you need to run SAPinst in accessibility mode proceed as described in Running SAPinst in Accessibility
Mode in the installation documentation of your release
If required you can stop SAPinst by choosing SAPinst Cancel in the SAPinst GUI menu
Prerequisites
We recommend that you use the csh shell for the installation with SAPinst If you want to use
another shell make sure that you have first read SAP Note 202227
SAPinst uses csh scripts during the installation to obtain the environment for user ltsapsidgtadm
This is also true if user ltsapsidgtadm already exists from an earlier SAP system installation and the
shell of this user is not csh Before you start SAPinst execute the following command as user
ltsapsidgtadm to make sure that the csh scripts are up-to-date
bincsh -c source lthome directory of ltsapsidgtadmgtcshrcenv
Make sure that you have specified the most important SAP system parameters as described in Basic
SAP System Installation Parameters in the installation documentation of your release before you start
SAPinst
Only valid for IBM DB2 for zOS |
Check that your installation hosts meet the requirements for the installation options that you
want to installEnd of IBM DB2 for zOS |
Only valid for Non-Standalone Engines and Clients |
If you want to perform a distributed or a high-availability installation make sure that you have
exported and mounted global directories For more information see Exporting and Mounting Global
Directories in the installation documentation of your releaseEnd of Non-Standalone Engines and Clients |
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you have carefully planned your database layout in particular the tablespace layout
as described in Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2554
Only valid for AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for Solaris |
Solaris SPARC onlyEnd of Solaris |
If you want to set up DB2s high-availability cluster solution SA MP make sure that you have read
the document IBM DB2 High Availability Solution IBM Tivoli System Automation for Multiplatforms at
httpservicesapcominstguidesnw70 Installation Installation ndash SAP NetWeaver SystemsEnd of AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for zOS |
First make sure that you have installed DB2 for zOS For information on that installation see
SAP DBA Guide DB2 for zOS DB2 Setup especially the section Stored Procedures EnablementEnd of IBM DB2 for zOS |
Check the value of the environment variable TEMP TMP or TMPDIR
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
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 ndash for example by using a crontab entry
Make sure that you have at least 60 MB of free space in the installation directory for each
installation option In addition you need 200 MB free space for the SAPinst executables If you
cannot provide 200 MB free space in the temporary directory you can set one of the
environment variables TEMP TMP or TMPDIR to another directory with 200 MB free space for
the SAPinst executables
Make sure that the temporary directory has the permissions 777
Only valid for IBM DB2 for zOS |
Make sure that your database is up and runningEnd of IBM DB2 for zOS |
Make sure that your DISPLAY environment variable is set to lthost_namegt00 where
lthost_namegt is the host on which you want to display the GUI
Shell Used Command
Bourne shell (sh) DISPLAY=lthost_namegt00
export DISPLAY
C shell (csh) setenv DISPLAY lthost_namegt00
Korn shell (ksh) export DISPLAY=lthost_namegt00
Make sure that umask is set to 022 for user root
As user root enter the following command umask 022
Check the following values for user root
5 Splitting
52 Running SAPinst
2654 PUBLIC 2012-04-11
In csh execute limit
Output Properties
cputime unlimited
filesize unlimited
datasize unlimited
stacksize 8192 KB
coredumpsize unlimited
descriptors 8192
memorysize unlimited
In sh or ksh execute ulimit -a
Output Properties
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192
coredump(blocks) unlimited
nofiles(descriptors) 8192
memory(KBytes) unlimited
If your parameter settings differ from those above change these values accordingly
EXAMPLE
If you have to change the value for descriptors to 8192 proceed as follows
In csh execute
limit descriptors 8192
In sh or ksh execute
ulimit -n 8192
Before you start SAPinst read SAP Note 1697164 for more information about which user to choose
for running the SAPinst SDT GUI server
Procedure
1 Log on to the installation host as user root
CAUTION
Do not use an existing ltsapsidgtadm user
Only valid for Non-Standalone Engines and Clients |
CAUTION
Make sure that the root user has not set any environment variables for a different SAP system
or database
End of Non-Standalone Engines and Clients |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2754
2 Make the Dual-Stack Split Tool available on the installation host Make sure that it is available
locally We do not recommend that you use Network File System (NFS) because reading from
media mounted with NFS might fail
For more information see Preparation Checklist [page 17] and Preparing the Installation Media in the
installation documentation of your release
3 Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
Only valid for Non-Standalone Engines and Clients |
Change to the directory with the sapinst executable for your operating system by entering the
following command cd ltMountpoint of Installation Master mediumgtDATA_UNITS
ltproductgt_IM_ltOSgtEnd of Non-Standalone Engines and Clients |
End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
4 Start SAPinst by executing the following command sapinst
NOTE
If you want to use a virtual host name start SAPinst with the SAPinst property
SAPINST_USE_HOSTNAME as follows
Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
sapinst SAPINST_USE_HOSTNAME=ltvirtual host namegt
End of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
5 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
In addition if you want to use the split option ldquoMove Java Databaserdquo choose ltYour System
Variantgt
Perform the export and installation steps exactly in the order in which they appear
6 Only valid for Non-Standalone Engines and Clients |
Choose NextEnd of Non-Standalone Engines and Clients |
7 Follow the instructions in the SAPinst input screens and enter the required parameters
NOTE
If SAPinst asks for the Java DVD make sure that you provide a Java DVD with the same
release level as your dual-stack system
For more information about the input parameters position the cursor on the parameter
and press F1
After you have entered all requested input parameters SAPinst displays the Parameter Summary screen
This screen shows both the parameters that you entered and those that SAPinst set by default If
required you can revise the parameters before starting the split procedure
5 Splitting
52 Running SAPinst
2854 PUBLIC 2012-04-11
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you check the following parameters depending on the installation type that you
have chosenEnd of IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for Linux and UNIX and Windows |
If you are performing a typical installation SAPinst creates four sapdata directories by
default If you require more or fewer sapdata directories depending on the storage devices
you are using you must change this parameter before you start the installation By selecting
this parameter on the Summary screen and choosing Revise SAPinst returns to the IBM DB2 for
Linux UNIX and Windows ndashgt Sapdata Directories screen
On this screen you can also decide if you want SAPinst to create the regular table and index
tablespaces with DB2s automatic storage management enabled By default the option for
automatic storage management is preselected
NOTE
As of DB2 V91 and higher the database and the SYSCATSPACE tablespace are always created
with automatic storage management enabled even if you deselect this option on the
dialog IBM DB2 for Linux UNIX and Windows gt Sapdata Directories
For more information about DB2s automatic storage management see section DB2
Tablespaces in the installation documentation of your SAP product
If you are performing a custom installation you set these parameters during the Define
Parameters phase of SAPinst
NOTE
If the tablespace layout used by SAPinst does not meet your requirements you can create
the tablespaces manually by deselecting the option Create Tablespaces with SAPinst on the
IBM DB2 for Linux and UNIX and Windows Sapdata Directories screen
During the installation phase SAPinst then displays the following message
You must create the tablespaces now To do so use the
createTablespacessql script that is located in your installation
directory
To continue the installation choose OK Alternatively you can cancel
SAPinst here and restart it again
SAPinst does not check the page size of tablespaces that have either been created manually
or that already exist If you create the tablespaces manually you must make sure that
you use a page size of 16 KBEnd of IBM DB2 for Linux and UNIX and Windows |
8 To start the dual-stack split choose Start
SAPinst starts and displays the progress of the split procedure
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2954
When the split option has finished successfully SAPinst displays the message Execution of
ltOption_Namegt has completed
Only valid for Oracle |
NOTE
When installing the Oracle database instance SAPinst stops the installation and prompts
you to install the Oracle database software For more information see Installing the Oracle
Database Software in the installation documentation of your release
After you have finished the installation of the Oracle database you continue the database
instance installation by choosing OK in the GUI of the database instance installation
Check SAP Note 1431800 for technical information about Oracle Release 112 in SAP
environments
End of Oracle |
Only valid for Enterprise Portal (EP) |
NOTE
During the final restart of Application Server Java performed by SAPinst the portal starts the
processing and uploading of the new portal archives It takes approximately 15 to 90 minutes
before the deployment is completed and the portal is launched
Do not stop SAPinst or Application Server Java during this phase
End of Enterprise Portal (EP) |
9 If required delete directories with the name sapinst_exexxxxxxxxxx after SAPinst has finished
Sometimes these remain in the temporary directory
NOTE
If there are errors with the SAPinst extraction process you can find the log file
dev_selfexout in the temporary directory
Only valid for Non-Standalone Engines and Clients |
RECOMMENDATION
Keep all installation 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 installation 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 installation directories on installation hosts but make sure
that you delete them after saving them separately
End of Non-Standalone Engines and Clients |
10 We recommend that you delete the directory ltuser_homegtsdtgui
11 Only valid for IBM DB2 for Linux and UNIX and Windows |
If not already done install the DB2 license
5 Splitting
52 Running SAPinst
3054 PUBLIC 2012-04-11
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
End of IBM DB2 for Linux and UNIX and Windows |
12 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 3154
This page is left blank for documents that are printed on both sides
6 Follow-Up Activities
61 Follow-Up Activities Checklist
This section includes the follow-up activities that you have to perform for the following split options
ldquoMove Java Databaserdquo for a central system
ldquoMove Java Databaserdquo for a distributed system or a high-availability system
ldquoKeep Databaserdquo for a central distributed or high-availability system
NOTE
Some of the follow-up activities listed in this section are not described in this documentation You
can find the detailed description in the SAP NetWeaver Application Server Java system copy
documentation relevant for your release at
httpservicesapcominstguides
Move Java Database
Central System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3354
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
7 We recommend that you perform regression testing
8 On the source system you run SAPinst [page 23] to remove the Java parts in the file system and in
the database
9 On the source system you call transaction RZ10 to reimport the profiles from the file system
10 In the Transport Management System (TMS) you configure the transport routes [page 38]
11 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
12 You clean up the system landscape data [page 40]
Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3454 PUBLIC 2012-04-11
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the database host of the source system you run SAPinst [page 23] to remove the Java database
schema
12 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
13 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
14 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
15 You clean up the system landscape data [page 40]
Keep Database
Central Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3554
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
12 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
13 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
14 You clean up the system landscape data [page 40]
62 Maintaining the Connection to the System Landscape Directory
After installing the Java system you need to reconfigure the connection between the System Landscape
Directory (SLD) the source system and the target system The steps required differ depending on
whether you use a local or a central SLD To maintain the connection to the SLD you can either run
the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split or perform the required steps manually as described below
NOTE
This step is only required if the connection to the SLD was established on the source system before
the split
Prerequisites
If you want to use the configuration wizard you need an SAP NetWeaver Java system 70 Support
Package 14 or higher in your landscape
SLDAPIUSER credentials are available in the ABAP system
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3654 PUBLIC 2012-04-11
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
Figure 1 Split Option Move Java Database for Central Systems
Move Java Database for Distributed System
When you choose the ldquoMove Java Databaserdquo option for a distributed system SAPinst exports the Java
stack of the dual-stack system and uses this export to reinstall the main instances on several hosts
Every instance can run on a separate host This equates to an installation of a distributed system
These are the following instances
Central instance (CI)
Central services instance for Java (SCS)
Database instance (DB)
NOTE
If required you can reinstall the central instance and the central services instance on the ABAP
system hosts
After the installation has finished and the System Landscape Directory has been reconfigured SAPinst
removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
1054 PUBLIC 2012-04-11
Figure 2 Split Option Move Java Database for Distributed System
22 Split Option Keep Database
The split option ldquoKeep Databaserdquo offers the possibility for the Java system to reuse the existing database
of the dual-stack system using MCOD (multiple components ndash one database)
Keep Database for Central and Distributed Systems
When you choose the ldquoKeep Databaserdquo option SAPinst exports the Java file system on the dual-stack
system It uses this export to reinstall a central services instance (SCS) and a central instance (CI) for
Java They can be installed on one host on different hosts or on the source system hosts again
Additionally SAPinst adapts the Java schema of the database of the dual-stack system to the target Java
system
After the installation has finished and the System Landscape Directory has been reconfigured SAPinst
removes all Java parts from the dual-stack system except the Java database schema
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-04-11 PUBLIC 1154
Figure 3 Split Option Keep Database for Central Systems
Figure 4 Split Option Keep Database for Distributed Systems
2 Split Options Covered by this Guide
22 Split Option Keep Database
1254 PUBLIC 2012-04-11
3 Planning
31 Planning Checklist
This section includes the planning steps that you have to perform when you want to install the new
Java system on one or more hosts Perform the planning steps according to the split option and your
system variant
NOTE
Most of the required planning steps listed in this section are not described in this documentation
You can find the detailed description in the SAP NetWeaver Application Server Java installation
documentation relevant for your release at httpservicesapcominstguides
Prerequisites
You have decided on your split option [page 9]
Split Option ldquoMove Java Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
1 You check the hardware and software requirements for the Java installation host
For more information see Hardware and Software Requirements in the installation documentation of
your release
2 You read about user management [page 15]
3 You identify basic SAP system installation parameters
For more information see Basic SAP System Parameters in the installation documentation of your
release
Be aware of the following dual-stack-split-specific deviations
SAP System Parameters
User management
We do not recommend that you make modifications in the user management settings
For more information see User Management [page 15]
System Landscape Directory (SLD)
You can ignore SLD parameters
Only valid for Oracle |
SAP System Database Parameters Java database schema
We recommend that you choose a schema ID that is different from your SAP system ID
It might cause problems when you copy a system if ltSCHEMA_IDgt is the same as ltSAPSIDgt and
the database-specific method used for the copy does not allow you to rename the database
3 Planning
31 Planning Checklist
2012-04-11 PUBLIC 1354
schemes In certain situations you might create a system copy with a new ltSAPSIDgt but where
the database schema has the old ltSAPSIDgt This is not a technical problem but might be
confusing to the system administratorEnd of Oracle |
4 Only valid for MaxDB |
You plan your system configuration
For more information see System Configuration in the installation documentation of your releaseEnd of MaxDB |
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
You plan the setup of your database carefully
For more information see Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
7 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 43]
8 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
9 Only valid for IBM DB2 for zOS |
If you want to execute a Software Life-Cycle Option with SAPinst in an SAP system with thick client
connectivity see Special Considerations Regarding Connectivity for Software Life-Cycle Options in the installation
documentation of your releaseEnd of IBM DB2 for zOS |
10 Only valid for IBM DB2 for i5OS |
Optionally you decide whether you want to install multiple SAP systems on a single host
For more information see Multiple SAP Systems on a Single Host in the installation documentation of
your releaseEnd of IBM DB2 for i5OS |
11 You can continue with Preparation [page 17]
Split Option ldquoKeep Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
1 You check the hardware and software requirements for the Java installation host
For more information see Hardware and Software Requirements in the installation documentation of
your release
2 You read about user management [page 15]
3 You identify basic SAP system installation parameters
For more information see Basic SAP System Parameters in the installation documentation of your
release
3 Planning
31 Planning Checklist
1454 PUBLIC 2012-04-11
Be aware of the following dual-stack-split-specific deviation for SAP System Parameters
User management
We do not recommend that you make modifications in the user management settings For
more information see User Management [page 15]
System Landscape Directory (SLD)
You can ignore SLD parameters
4 Only valid for IBM DB2 for zOSMaxDB |
You plan your system configuration
For more information see System Configuration in the installation documentation of your releaseEnd of IBM DB2 for zOSMaxDB |
5 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
6 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 43]
7 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
8 Only valid for IBM DB2 for zOS |
If you want to execute a Software Life-Cycle Option with SAPinst in an SAP system with thick client
connectivity see Special Considerations Regarding Connectivity for Software Life-Cycle Options in the installation
documentation of your releaseEnd of IBM DB2 for zOS |
9 Only valid for IBM DB2 for i5OS |
Optionally you decide whether you want to install multiple SAP systems on a single host
For more information see Multiple SAP Systems on a Single Host in the installation documentation of
your releaseEnd of IBM DB2 for i5OS |
10 You can continue with Preparation [page 17]
32 User Management
The dual-stack split procedure does not change the user management and you cannot choose which
kind of user management you want to use for the target AS Java system That is the separated Java
system and the ABAP system both use the user management of the former dual-stack system The
following is possible
If the dual-stack system uses AS ABAP as data source for the User Management Engine (UME)
after the split the separated Java stack will also use the ABAP UME
If the dual-stack system uses an LDAP directory as source for user data this is also valid for the Java
stack
3 Planning
32 User Management
2012-04-11 PUBLIC 1554
In both cases manual configuration is not required
We do not recommend that you make modifications to the user management settings
For more information see SAP Note 718383
3 Planning
32 User Management
1654 PUBLIC 2012-04-11
4 Preparation
41 Preparation Checklist
This section includes the preparation steps that you have to perform when you want to install the new
Java system on one or more hosts
NOTE
Most of the required preparation steps listed in this section are not described in this
documentation You can find the detailed description in the SAP NetWeaver Application Server
Java installation documentation relevant for your release at httpservicesapcom
instguides
1 Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
You make sure that the required operating system users and groups are created
To create the groups and users automatically run the Dual-Stack Split Tool on the host where
the SAP Java system is to be installed and choose Dual-Stack Split Operating System Users and
Groups
For more information see Creating Operating System Users and Groups in the installation documentation
of your releaseEnd of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
2 You set up file systems and make sure that the required disk space is available for the directories
to be created during the installation
For more information see Setting Up File Systems for a High-Availability System in the installation
documentation of your release
3 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
4 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
If you want to install a high-availability system you perform switchover preparations
For more information see Performing Switchover Preparations for High-Availability in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
5 If you want to share the transport directory trans from another system you export this directory
to your installation hosts
For more information see Exporting and Mounting the Global Transport Directory in the installation
documentation of your release
4 Preparation
41 Preparation Checklist
2012-04-11 PUBLIC 1754
6 You install the Java Development Kit This step is not required if you have installed the SAP JVM
4 on your source system
For more information see Installing the Java Development Kit in the installation documentation of your
release
7 You make sure that the required installation media are available on each host
You can download the Dual-Stack Split Tool at httpservicesapcomsltoolset
Software Logistics Toolset 10 Dual-Stack Split
You can download the Java stack and database installation media from SAP Service
Marketplace as described in Preparing the Installation Media in the installation documentation of
your release
NOTE
The release level required for the installation corresponds to the release level of your dual-
stack system
The following table shows the required installation media for the dual-stack split
SAP Instance Installation Required Media
Central services instance central instance
Dual-Stack Split Tool Java DVD RDBMS Client DVD
Move Java Database only Database instance
Dual-Stack Split Tool Java DVD Only valid for MS SQL ServerOracle |
RDBMS DVDEnd of MS SQL ServerOracle |
Only valid for MS SQL ServerOracle |
RDBMS Patch DVD (if available)End of MS SQL ServerOracle |
8 Only valid for HA (MSCS) |
To install a high-availability system with Microsoft Cluster Service (MSCS) you also perform the
MSCS-specific preparation tasks as described in the installation documentation of your releaseEnd of HA (MSCS) |
9 Only valid for HA (MSCS) |
If you choose the split option ldquoKeep Databaserdquo with the scenario ldquoKeep SCS on the Source Cluster
Systemrdquo you perform the following steps
You provide additional disk storage on the target cluster system
For more information see Distribution of SAP System Components to Disks for MSCS Directories in an
MSCS Configuration and IP Addresses in an MSCS Configuration in the installation documentation of
your release
You provide an additional IP address and an additional virtual host name for the Java system
For more information see Mapping Host Names to IP Addresses for MSCS in the installation
documentation of your releaseEnd of HA (MSCS) |
4 Preparation
41 Preparation Checklist
1854 PUBLIC 2012-04-11
10 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 19] of
the dual-stack system
11 You can continue with Splitting [page 21]
42 Performing a Full System Backup
If you decided to use the split option ldquoKeep Databaserdquo you must perform a full system backup of the
dual-stack system or at least a backup of the Java database schema before you start the split procedure
If you decided to use the split option ldquoMove Java Databaserdquo you do not need to perform a backup before
you start the split procedure
For more information about backing up your database see the database-specific backup and recovery
documentation in the SAP Library [page 7] at
SAP MaxDB
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for SAP
MaxDB
Oracle
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Oracle
IBM DB2 for i5OS
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 UDB for iSeries
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for i
4 Preparation
42 Performing a Full System Backup
2012-04-11 PUBLIC 1954
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
i
IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX
and Windows
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
Linux UNIX and Windows
IBM DB2 for zOS
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 UDB for zOS
SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for DB2 for z
OS
Microsoft SQL Server
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Microsoft SQL
Server
4 Preparation
42 Performing a Full System Backup
2054 PUBLIC 2012-04-11
5 Splitting
51 Splitting Checklist
This section includes the splitting steps that you have to perform for the following split options
ldquoMove Java Databaserdquo
ldquoKeep Databaserdquo
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Only valid for Oracle |
You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 You export the Java stack using SAPinst [page 23]
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
4 You restart the source system
5 You run SAPinst [page 23] to install a Java only system using the export from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2012-04-11 PUBLIC 2154
Distributed System
1 Only valid for Oracle |
On the database instance host of the dual-stack system you install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes on the database instance host
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 On the database instance host of the dual-stack system you run SAPinst [page 23] to export the
Java database schema
4 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the Java
parts of the file system of the central instance
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
5 You restart the source system
6 You run SAPinst [page 23] to install a central services instance for the Java target system
7 You run SAPinst [page 23] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
9 You continue with Follow-Up Activities [page 33]
Keep Database
1 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the
file system of the central instance
5 Splitting
51 Splitting Checklist
2254 PUBLIC 2012-04-11
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you wont use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
2 You restart the source system
3 You run SAPinst [page 23] to install a central services instance for the Java target system
4 On the database instance host of the dual-stack system you run SAPinst [page 23] to adapt the
database for the Java target system
NOTE
Make sure that you enter the profile directory of the Java target system in the SAP System gt
General Parameters screen
5 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
52 Running SAPinst
This section describes how to run the installation tool SAPinst SAPinst includes a GUI client and a GUI
server which both use Java
The procedure describes an installation where SAPinst GUI client and GUI server are running on the
same host In the following GUI client and GUI server are addressed as ldquoSAPinst GUIrdquo
If you need to see the installation on a remote display we recommend that you perform a remote
installation with SAPinst where the SAPinst GUI is running on a separate host from SAPinst For more
information see Performing a Remote Installation with SAPinst in the installation documentation of your
release
Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote
access to SAPinst GUI on Windows workstations For more information see SAP Note 1170809
Useful Information About SAPinst
When you start SAPinst it automatically starts the SAPinst GUI
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2354
SAPinst creates the installation directory sapinst_instdir directly below the temporary directory
SAPinst 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 SAPinst
creates the installation directory sapinst_instdir directly below the tmp directory by default
If you want SAPinst to create the installation directory sapinst_instdir in another directory set
the environment variable TEMP to this directory before you start SAPinst
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
Only valid for IBM DB2 for i5OS |
NOTE
When you leave your Qp2Term session all changes of the environment variables done by the
command export are reverted
End of IBM DB2 for i5OS |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
SAPinst creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt
SAPinst extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is located
in the environment variables TEMP TMP or TMPDIR These files are deleted after SAPinst has stopped
running
The temporary directory sapinst_exexxxxxxxxxx sometimes remains undeleted You can safely
delete it
The temporary directory also contains the log file dev_selfexout from the extraction process
which might be useful if an error occurs
CAUTION
If SAPinst cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default ports 21200 21212 and 4239 are used for communication
between SAPinst GUI server GUI and HTTP server as follows
SAPinst uses port 21200 to communicate with the GUI server
The GUI server uses port 21212 to communicate with the GUI client
5 Splitting
52 Running SAPinst
2454 PUBLIC 2012-04-11
4239 is the port of the HTTP server which is part of the GUI server
If the ports for SAPinst and the GUI server are already in use SAPinst automatically searches for
free port numbers If the search fails SAPinst exits
In this case or if you want SAPinst to use specific ports you can assign them by executing the
sapinst executable with the following command line parameters
SAPINST_DIALOG_PORT=ltport_number_sapinst_to_gui_servergt
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
GUISERVER_HTTP_PORT=ltport_number_http_servergt
To see a list of all available SAPinst properties start SAPinst as described above with command line
parameter -p
sapinst -p
If you need to run SAPinst in accessibility mode proceed as described in Running SAPinst in Accessibility
Mode in the installation documentation of your release
If required you can stop SAPinst by choosing SAPinst Cancel in the SAPinst GUI menu
Prerequisites
We recommend that you use the csh shell for the installation with SAPinst If you want to use
another shell make sure that you have first read SAP Note 202227
SAPinst uses csh scripts during the installation to obtain the environment for user ltsapsidgtadm
This is also true if user ltsapsidgtadm already exists from an earlier SAP system installation and the
shell of this user is not csh Before you start SAPinst execute the following command as user
ltsapsidgtadm to make sure that the csh scripts are up-to-date
bincsh -c source lthome directory of ltsapsidgtadmgtcshrcenv
Make sure that you have specified the most important SAP system parameters as described in Basic
SAP System Installation Parameters in the installation documentation of your release before you start
SAPinst
Only valid for IBM DB2 for zOS |
Check that your installation hosts meet the requirements for the installation options that you
want to installEnd of IBM DB2 for zOS |
Only valid for Non-Standalone Engines and Clients |
If you want to perform a distributed or a high-availability installation make sure that you have
exported and mounted global directories For more information see Exporting and Mounting Global
Directories in the installation documentation of your releaseEnd of Non-Standalone Engines and Clients |
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you have carefully planned your database layout in particular the tablespace layout
as described in Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2554
Only valid for AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for Solaris |
Solaris SPARC onlyEnd of Solaris |
If you want to set up DB2s high-availability cluster solution SA MP make sure that you have read
the document IBM DB2 High Availability Solution IBM Tivoli System Automation for Multiplatforms at
httpservicesapcominstguidesnw70 Installation Installation ndash SAP NetWeaver SystemsEnd of AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for zOS |
First make sure that you have installed DB2 for zOS For information on that installation see
SAP DBA Guide DB2 for zOS DB2 Setup especially the section Stored Procedures EnablementEnd of IBM DB2 for zOS |
Check the value of the environment variable TEMP TMP or TMPDIR
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
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 ndash for example by using a crontab entry
Make sure that you have at least 60 MB of free space in the installation directory for each
installation option In addition you need 200 MB free space for the SAPinst executables If you
cannot provide 200 MB free space in the temporary directory you can set one of the
environment variables TEMP TMP or TMPDIR to another directory with 200 MB free space for
the SAPinst executables
Make sure that the temporary directory has the permissions 777
Only valid for IBM DB2 for zOS |
Make sure that your database is up and runningEnd of IBM DB2 for zOS |
Make sure that your DISPLAY environment variable is set to lthost_namegt00 where
lthost_namegt is the host on which you want to display the GUI
Shell Used Command
Bourne shell (sh) DISPLAY=lthost_namegt00
export DISPLAY
C shell (csh) setenv DISPLAY lthost_namegt00
Korn shell (ksh) export DISPLAY=lthost_namegt00
Make sure that umask is set to 022 for user root
As user root enter the following command umask 022
Check the following values for user root
5 Splitting
52 Running SAPinst
2654 PUBLIC 2012-04-11
In csh execute limit
Output Properties
cputime unlimited
filesize unlimited
datasize unlimited
stacksize 8192 KB
coredumpsize unlimited
descriptors 8192
memorysize unlimited
In sh or ksh execute ulimit -a
Output Properties
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192
coredump(blocks) unlimited
nofiles(descriptors) 8192
memory(KBytes) unlimited
If your parameter settings differ from those above change these values accordingly
EXAMPLE
If you have to change the value for descriptors to 8192 proceed as follows
In csh execute
limit descriptors 8192
In sh or ksh execute
ulimit -n 8192
Before you start SAPinst read SAP Note 1697164 for more information about which user to choose
for running the SAPinst SDT GUI server
Procedure
1 Log on to the installation host as user root
CAUTION
Do not use an existing ltsapsidgtadm user
Only valid for Non-Standalone Engines and Clients |
CAUTION
Make sure that the root user has not set any environment variables for a different SAP system
or database
End of Non-Standalone Engines and Clients |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2754
2 Make the Dual-Stack Split Tool available on the installation host Make sure that it is available
locally We do not recommend that you use Network File System (NFS) because reading from
media mounted with NFS might fail
For more information see Preparation Checklist [page 17] and Preparing the Installation Media in the
installation documentation of your release
3 Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
Only valid for Non-Standalone Engines and Clients |
Change to the directory with the sapinst executable for your operating system by entering the
following command cd ltMountpoint of Installation Master mediumgtDATA_UNITS
ltproductgt_IM_ltOSgtEnd of Non-Standalone Engines and Clients |
End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
4 Start SAPinst by executing the following command sapinst
NOTE
If you want to use a virtual host name start SAPinst with the SAPinst property
SAPINST_USE_HOSTNAME as follows
Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
sapinst SAPINST_USE_HOSTNAME=ltvirtual host namegt
End of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
5 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
In addition if you want to use the split option ldquoMove Java Databaserdquo choose ltYour System
Variantgt
Perform the export and installation steps exactly in the order in which they appear
6 Only valid for Non-Standalone Engines and Clients |
Choose NextEnd of Non-Standalone Engines and Clients |
7 Follow the instructions in the SAPinst input screens and enter the required parameters
NOTE
If SAPinst asks for the Java DVD make sure that you provide a Java DVD with the same
release level as your dual-stack system
For more information about the input parameters position the cursor on the parameter
and press F1
After you have entered all requested input parameters SAPinst displays the Parameter Summary screen
This screen shows both the parameters that you entered and those that SAPinst set by default If
required you can revise the parameters before starting the split procedure
5 Splitting
52 Running SAPinst
2854 PUBLIC 2012-04-11
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you check the following parameters depending on the installation type that you
have chosenEnd of IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for Linux and UNIX and Windows |
If you are performing a typical installation SAPinst creates four sapdata directories by
default If you require more or fewer sapdata directories depending on the storage devices
you are using you must change this parameter before you start the installation By selecting
this parameter on the Summary screen and choosing Revise SAPinst returns to the IBM DB2 for
Linux UNIX and Windows ndashgt Sapdata Directories screen
On this screen you can also decide if you want SAPinst to create the regular table and index
tablespaces with DB2s automatic storage management enabled By default the option for
automatic storage management is preselected
NOTE
As of DB2 V91 and higher the database and the SYSCATSPACE tablespace are always created
with automatic storage management enabled even if you deselect this option on the
dialog IBM DB2 for Linux UNIX and Windows gt Sapdata Directories
For more information about DB2s automatic storage management see section DB2
Tablespaces in the installation documentation of your SAP product
If you are performing a custom installation you set these parameters during the Define
Parameters phase of SAPinst
NOTE
If the tablespace layout used by SAPinst does not meet your requirements you can create
the tablespaces manually by deselecting the option Create Tablespaces with SAPinst on the
IBM DB2 for Linux and UNIX and Windows Sapdata Directories screen
During the installation phase SAPinst then displays the following message
You must create the tablespaces now To do so use the
createTablespacessql script that is located in your installation
directory
To continue the installation choose OK Alternatively you can cancel
SAPinst here and restart it again
SAPinst does not check the page size of tablespaces that have either been created manually
or that already exist If you create the tablespaces manually you must make sure that
you use a page size of 16 KBEnd of IBM DB2 for Linux and UNIX and Windows |
8 To start the dual-stack split choose Start
SAPinst starts and displays the progress of the split procedure
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2954
When the split option has finished successfully SAPinst displays the message Execution of
ltOption_Namegt has completed
Only valid for Oracle |
NOTE
When installing the Oracle database instance SAPinst stops the installation and prompts
you to install the Oracle database software For more information see Installing the Oracle
Database Software in the installation documentation of your release
After you have finished the installation of the Oracle database you continue the database
instance installation by choosing OK in the GUI of the database instance installation
Check SAP Note 1431800 for technical information about Oracle Release 112 in SAP
environments
End of Oracle |
Only valid for Enterprise Portal (EP) |
NOTE
During the final restart of Application Server Java performed by SAPinst the portal starts the
processing and uploading of the new portal archives It takes approximately 15 to 90 minutes
before the deployment is completed and the portal is launched
Do not stop SAPinst or Application Server Java during this phase
End of Enterprise Portal (EP) |
9 If required delete directories with the name sapinst_exexxxxxxxxxx after SAPinst has finished
Sometimes these remain in the temporary directory
NOTE
If there are errors with the SAPinst extraction process you can find the log file
dev_selfexout in the temporary directory
Only valid for Non-Standalone Engines and Clients |
RECOMMENDATION
Keep all installation 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 installation 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 installation directories on installation hosts but make sure
that you delete them after saving them separately
End of Non-Standalone Engines and Clients |
10 We recommend that you delete the directory ltuser_homegtsdtgui
11 Only valid for IBM DB2 for Linux and UNIX and Windows |
If not already done install the DB2 license
5 Splitting
52 Running SAPinst
3054 PUBLIC 2012-04-11
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
End of IBM DB2 for Linux and UNIX and Windows |
12 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 3154
This page is left blank for documents that are printed on both sides
6 Follow-Up Activities
61 Follow-Up Activities Checklist
This section includes the follow-up activities that you have to perform for the following split options
ldquoMove Java Databaserdquo for a central system
ldquoMove Java Databaserdquo for a distributed system or a high-availability system
ldquoKeep Databaserdquo for a central distributed or high-availability system
NOTE
Some of the follow-up activities listed in this section are not described in this documentation You
can find the detailed description in the SAP NetWeaver Application Server Java system copy
documentation relevant for your release at
httpservicesapcominstguides
Move Java Database
Central System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3354
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
7 We recommend that you perform regression testing
8 On the source system you run SAPinst [page 23] to remove the Java parts in the file system and in
the database
9 On the source system you call transaction RZ10 to reimport the profiles from the file system
10 In the Transport Management System (TMS) you configure the transport routes [page 38]
11 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
12 You clean up the system landscape data [page 40]
Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3454 PUBLIC 2012-04-11
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the database host of the source system you run SAPinst [page 23] to remove the Java database
schema
12 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
13 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
14 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
15 You clean up the system landscape data [page 40]
Keep Database
Central Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3554
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
12 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
13 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
14 You clean up the system landscape data [page 40]
62 Maintaining the Connection to the System Landscape Directory
After installing the Java system you need to reconfigure the connection between the System Landscape
Directory (SLD) the source system and the target system The steps required differ depending on
whether you use a local or a central SLD To maintain the connection to the SLD you can either run
the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split or perform the required steps manually as described below
NOTE
This step is only required if the connection to the SLD was established on the source system before
the split
Prerequisites
If you want to use the configuration wizard you need an SAP NetWeaver Java system 70 Support
Package 14 or higher in your landscape
SLDAPIUSER credentials are available in the ABAP system
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3654 PUBLIC 2012-04-11
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
Figure 2 Split Option Move Java Database for Distributed System
22 Split Option Keep Database
The split option ldquoKeep Databaserdquo offers the possibility for the Java system to reuse the existing database
of the dual-stack system using MCOD (multiple components ndash one database)
Keep Database for Central and Distributed Systems
When you choose the ldquoKeep Databaserdquo option SAPinst exports the Java file system on the dual-stack
system It uses this export to reinstall a central services instance (SCS) and a central instance (CI) for
Java They can be installed on one host on different hosts or on the source system hosts again
Additionally SAPinst adapts the Java schema of the database of the dual-stack system to the target Java
system
After the installation has finished and the System Landscape Directory has been reconfigured SAPinst
removes all Java parts from the dual-stack system except the Java database schema
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-04-11 PUBLIC 1154
Figure 3 Split Option Keep Database for Central Systems
Figure 4 Split Option Keep Database for Distributed Systems
2 Split Options Covered by this Guide
22 Split Option Keep Database
1254 PUBLIC 2012-04-11
3 Planning
31 Planning Checklist
This section includes the planning steps that you have to perform when you want to install the new
Java system on one or more hosts Perform the planning steps according to the split option and your
system variant
NOTE
Most of the required planning steps listed in this section are not described in this documentation
You can find the detailed description in the SAP NetWeaver Application Server Java installation
documentation relevant for your release at httpservicesapcominstguides
Prerequisites
You have decided on your split option [page 9]
Split Option ldquoMove Java Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
1 You check the hardware and software requirements for the Java installation host
For more information see Hardware and Software Requirements in the installation documentation of
your release
2 You read about user management [page 15]
3 You identify basic SAP system installation parameters
For more information see Basic SAP System Parameters in the installation documentation of your
release
Be aware of the following dual-stack-split-specific deviations
SAP System Parameters
User management
We do not recommend that you make modifications in the user management settings
For more information see User Management [page 15]
System Landscape Directory (SLD)
You can ignore SLD parameters
Only valid for Oracle |
SAP System Database Parameters Java database schema
We recommend that you choose a schema ID that is different from your SAP system ID
It might cause problems when you copy a system if ltSCHEMA_IDgt is the same as ltSAPSIDgt and
the database-specific method used for the copy does not allow you to rename the database
3 Planning
31 Planning Checklist
2012-04-11 PUBLIC 1354
schemes In certain situations you might create a system copy with a new ltSAPSIDgt but where
the database schema has the old ltSAPSIDgt This is not a technical problem but might be
confusing to the system administratorEnd of Oracle |
4 Only valid for MaxDB |
You plan your system configuration
For more information see System Configuration in the installation documentation of your releaseEnd of MaxDB |
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
You plan the setup of your database carefully
For more information see Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
7 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 43]
8 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
9 Only valid for IBM DB2 for zOS |
If you want to execute a Software Life-Cycle Option with SAPinst in an SAP system with thick client
connectivity see Special Considerations Regarding Connectivity for Software Life-Cycle Options in the installation
documentation of your releaseEnd of IBM DB2 for zOS |
10 Only valid for IBM DB2 for i5OS |
Optionally you decide whether you want to install multiple SAP systems on a single host
For more information see Multiple SAP Systems on a Single Host in the installation documentation of
your releaseEnd of IBM DB2 for i5OS |
11 You can continue with Preparation [page 17]
Split Option ldquoKeep Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
1 You check the hardware and software requirements for the Java installation host
For more information see Hardware and Software Requirements in the installation documentation of
your release
2 You read about user management [page 15]
3 You identify basic SAP system installation parameters
For more information see Basic SAP System Parameters in the installation documentation of your
release
3 Planning
31 Planning Checklist
1454 PUBLIC 2012-04-11
Be aware of the following dual-stack-split-specific deviation for SAP System Parameters
User management
We do not recommend that you make modifications in the user management settings For
more information see User Management [page 15]
System Landscape Directory (SLD)
You can ignore SLD parameters
4 Only valid for IBM DB2 for zOSMaxDB |
You plan your system configuration
For more information see System Configuration in the installation documentation of your releaseEnd of IBM DB2 for zOSMaxDB |
5 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
6 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 43]
7 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
8 Only valid for IBM DB2 for zOS |
If you want to execute a Software Life-Cycle Option with SAPinst in an SAP system with thick client
connectivity see Special Considerations Regarding Connectivity for Software Life-Cycle Options in the installation
documentation of your releaseEnd of IBM DB2 for zOS |
9 Only valid for IBM DB2 for i5OS |
Optionally you decide whether you want to install multiple SAP systems on a single host
For more information see Multiple SAP Systems on a Single Host in the installation documentation of
your releaseEnd of IBM DB2 for i5OS |
10 You can continue with Preparation [page 17]
32 User Management
The dual-stack split procedure does not change the user management and you cannot choose which
kind of user management you want to use for the target AS Java system That is the separated Java
system and the ABAP system both use the user management of the former dual-stack system The
following is possible
If the dual-stack system uses AS ABAP as data source for the User Management Engine (UME)
after the split the separated Java stack will also use the ABAP UME
If the dual-stack system uses an LDAP directory as source for user data this is also valid for the Java
stack
3 Planning
32 User Management
2012-04-11 PUBLIC 1554
In both cases manual configuration is not required
We do not recommend that you make modifications to the user management settings
For more information see SAP Note 718383
3 Planning
32 User Management
1654 PUBLIC 2012-04-11
4 Preparation
41 Preparation Checklist
This section includes the preparation steps that you have to perform when you want to install the new
Java system on one or more hosts
NOTE
Most of the required preparation steps listed in this section are not described in this
documentation You can find the detailed description in the SAP NetWeaver Application Server
Java installation documentation relevant for your release at httpservicesapcom
instguides
1 Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
You make sure that the required operating system users and groups are created
To create the groups and users automatically run the Dual-Stack Split Tool on the host where
the SAP Java system is to be installed and choose Dual-Stack Split Operating System Users and
Groups
For more information see Creating Operating System Users and Groups in the installation documentation
of your releaseEnd of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
2 You set up file systems and make sure that the required disk space is available for the directories
to be created during the installation
For more information see Setting Up File Systems for a High-Availability System in the installation
documentation of your release
3 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
4 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
If you want to install a high-availability system you perform switchover preparations
For more information see Performing Switchover Preparations for High-Availability in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
5 If you want to share the transport directory trans from another system you export this directory
to your installation hosts
For more information see Exporting and Mounting the Global Transport Directory in the installation
documentation of your release
4 Preparation
41 Preparation Checklist
2012-04-11 PUBLIC 1754
6 You install the Java Development Kit This step is not required if you have installed the SAP JVM
4 on your source system
For more information see Installing the Java Development Kit in the installation documentation of your
release
7 You make sure that the required installation media are available on each host
You can download the Dual-Stack Split Tool at httpservicesapcomsltoolset
Software Logistics Toolset 10 Dual-Stack Split
You can download the Java stack and database installation media from SAP Service
Marketplace as described in Preparing the Installation Media in the installation documentation of
your release
NOTE
The release level required for the installation corresponds to the release level of your dual-
stack system
The following table shows the required installation media for the dual-stack split
SAP Instance Installation Required Media
Central services instance central instance
Dual-Stack Split Tool Java DVD RDBMS Client DVD
Move Java Database only Database instance
Dual-Stack Split Tool Java DVD Only valid for MS SQL ServerOracle |
RDBMS DVDEnd of MS SQL ServerOracle |
Only valid for MS SQL ServerOracle |
RDBMS Patch DVD (if available)End of MS SQL ServerOracle |
8 Only valid for HA (MSCS) |
To install a high-availability system with Microsoft Cluster Service (MSCS) you also perform the
MSCS-specific preparation tasks as described in the installation documentation of your releaseEnd of HA (MSCS) |
9 Only valid for HA (MSCS) |
If you choose the split option ldquoKeep Databaserdquo with the scenario ldquoKeep SCS on the Source Cluster
Systemrdquo you perform the following steps
You provide additional disk storage on the target cluster system
For more information see Distribution of SAP System Components to Disks for MSCS Directories in an
MSCS Configuration and IP Addresses in an MSCS Configuration in the installation documentation of
your release
You provide an additional IP address and an additional virtual host name for the Java system
For more information see Mapping Host Names to IP Addresses for MSCS in the installation
documentation of your releaseEnd of HA (MSCS) |
4 Preparation
41 Preparation Checklist
1854 PUBLIC 2012-04-11
10 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 19] of
the dual-stack system
11 You can continue with Splitting [page 21]
42 Performing a Full System Backup
If you decided to use the split option ldquoKeep Databaserdquo you must perform a full system backup of the
dual-stack system or at least a backup of the Java database schema before you start the split procedure
If you decided to use the split option ldquoMove Java Databaserdquo you do not need to perform a backup before
you start the split procedure
For more information about backing up your database see the database-specific backup and recovery
documentation in the SAP Library [page 7] at
SAP MaxDB
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for SAP
MaxDB
Oracle
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Oracle
IBM DB2 for i5OS
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 UDB for iSeries
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for i
4 Preparation
42 Performing a Full System Backup
2012-04-11 PUBLIC 1954
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
i
IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX
and Windows
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
Linux UNIX and Windows
IBM DB2 for zOS
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 UDB for zOS
SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for DB2 for z
OS
Microsoft SQL Server
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Microsoft SQL
Server
4 Preparation
42 Performing a Full System Backup
2054 PUBLIC 2012-04-11
5 Splitting
51 Splitting Checklist
This section includes the splitting steps that you have to perform for the following split options
ldquoMove Java Databaserdquo
ldquoKeep Databaserdquo
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Only valid for Oracle |
You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 You export the Java stack using SAPinst [page 23]
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
4 You restart the source system
5 You run SAPinst [page 23] to install a Java only system using the export from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2012-04-11 PUBLIC 2154
Distributed System
1 Only valid for Oracle |
On the database instance host of the dual-stack system you install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes on the database instance host
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 On the database instance host of the dual-stack system you run SAPinst [page 23] to export the
Java database schema
4 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the Java
parts of the file system of the central instance
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
5 You restart the source system
6 You run SAPinst [page 23] to install a central services instance for the Java target system
7 You run SAPinst [page 23] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
9 You continue with Follow-Up Activities [page 33]
Keep Database
1 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the
file system of the central instance
5 Splitting
51 Splitting Checklist
2254 PUBLIC 2012-04-11
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you wont use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
2 You restart the source system
3 You run SAPinst [page 23] to install a central services instance for the Java target system
4 On the database instance host of the dual-stack system you run SAPinst [page 23] to adapt the
database for the Java target system
NOTE
Make sure that you enter the profile directory of the Java target system in the SAP System gt
General Parameters screen
5 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
52 Running SAPinst
This section describes how to run the installation tool SAPinst SAPinst includes a GUI client and a GUI
server which both use Java
The procedure describes an installation where SAPinst GUI client and GUI server are running on the
same host In the following GUI client and GUI server are addressed as ldquoSAPinst GUIrdquo
If you need to see the installation on a remote display we recommend that you perform a remote
installation with SAPinst where the SAPinst GUI is running on a separate host from SAPinst For more
information see Performing a Remote Installation with SAPinst in the installation documentation of your
release
Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote
access to SAPinst GUI on Windows workstations For more information see SAP Note 1170809
Useful Information About SAPinst
When you start SAPinst it automatically starts the SAPinst GUI
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2354
SAPinst creates the installation directory sapinst_instdir directly below the temporary directory
SAPinst 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 SAPinst
creates the installation directory sapinst_instdir directly below the tmp directory by default
If you want SAPinst to create the installation directory sapinst_instdir in another directory set
the environment variable TEMP to this directory before you start SAPinst
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
Only valid for IBM DB2 for i5OS |
NOTE
When you leave your Qp2Term session all changes of the environment variables done by the
command export are reverted
End of IBM DB2 for i5OS |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
SAPinst creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt
SAPinst extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is located
in the environment variables TEMP TMP or TMPDIR These files are deleted after SAPinst has stopped
running
The temporary directory sapinst_exexxxxxxxxxx sometimes remains undeleted You can safely
delete it
The temporary directory also contains the log file dev_selfexout from the extraction process
which might be useful if an error occurs
CAUTION
If SAPinst cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default ports 21200 21212 and 4239 are used for communication
between SAPinst GUI server GUI and HTTP server as follows
SAPinst uses port 21200 to communicate with the GUI server
The GUI server uses port 21212 to communicate with the GUI client
5 Splitting
52 Running SAPinst
2454 PUBLIC 2012-04-11
4239 is the port of the HTTP server which is part of the GUI server
If the ports for SAPinst and the GUI server are already in use SAPinst automatically searches for
free port numbers If the search fails SAPinst exits
In this case or if you want SAPinst to use specific ports you can assign them by executing the
sapinst executable with the following command line parameters
SAPINST_DIALOG_PORT=ltport_number_sapinst_to_gui_servergt
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
GUISERVER_HTTP_PORT=ltport_number_http_servergt
To see a list of all available SAPinst properties start SAPinst as described above with command line
parameter -p
sapinst -p
If you need to run SAPinst in accessibility mode proceed as described in Running SAPinst in Accessibility
Mode in the installation documentation of your release
If required you can stop SAPinst by choosing SAPinst Cancel in the SAPinst GUI menu
Prerequisites
We recommend that you use the csh shell for the installation with SAPinst If you want to use
another shell make sure that you have first read SAP Note 202227
SAPinst uses csh scripts during the installation to obtain the environment for user ltsapsidgtadm
This is also true if user ltsapsidgtadm already exists from an earlier SAP system installation and the
shell of this user is not csh Before you start SAPinst execute the following command as user
ltsapsidgtadm to make sure that the csh scripts are up-to-date
bincsh -c source lthome directory of ltsapsidgtadmgtcshrcenv
Make sure that you have specified the most important SAP system parameters as described in Basic
SAP System Installation Parameters in the installation documentation of your release before you start
SAPinst
Only valid for IBM DB2 for zOS |
Check that your installation hosts meet the requirements for the installation options that you
want to installEnd of IBM DB2 for zOS |
Only valid for Non-Standalone Engines and Clients |
If you want to perform a distributed or a high-availability installation make sure that you have
exported and mounted global directories For more information see Exporting and Mounting Global
Directories in the installation documentation of your releaseEnd of Non-Standalone Engines and Clients |
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you have carefully planned your database layout in particular the tablespace layout
as described in Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2554
Only valid for AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for Solaris |
Solaris SPARC onlyEnd of Solaris |
If you want to set up DB2s high-availability cluster solution SA MP make sure that you have read
the document IBM DB2 High Availability Solution IBM Tivoli System Automation for Multiplatforms at
httpservicesapcominstguidesnw70 Installation Installation ndash SAP NetWeaver SystemsEnd of AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for zOS |
First make sure that you have installed DB2 for zOS For information on that installation see
SAP DBA Guide DB2 for zOS DB2 Setup especially the section Stored Procedures EnablementEnd of IBM DB2 for zOS |
Check the value of the environment variable TEMP TMP or TMPDIR
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
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 ndash for example by using a crontab entry
Make sure that you have at least 60 MB of free space in the installation directory for each
installation option In addition you need 200 MB free space for the SAPinst executables If you
cannot provide 200 MB free space in the temporary directory you can set one of the
environment variables TEMP TMP or TMPDIR to another directory with 200 MB free space for
the SAPinst executables
Make sure that the temporary directory has the permissions 777
Only valid for IBM DB2 for zOS |
Make sure that your database is up and runningEnd of IBM DB2 for zOS |
Make sure that your DISPLAY environment variable is set to lthost_namegt00 where
lthost_namegt is the host on which you want to display the GUI
Shell Used Command
Bourne shell (sh) DISPLAY=lthost_namegt00
export DISPLAY
C shell (csh) setenv DISPLAY lthost_namegt00
Korn shell (ksh) export DISPLAY=lthost_namegt00
Make sure that umask is set to 022 for user root
As user root enter the following command umask 022
Check the following values for user root
5 Splitting
52 Running SAPinst
2654 PUBLIC 2012-04-11
In csh execute limit
Output Properties
cputime unlimited
filesize unlimited
datasize unlimited
stacksize 8192 KB
coredumpsize unlimited
descriptors 8192
memorysize unlimited
In sh or ksh execute ulimit -a
Output Properties
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192
coredump(blocks) unlimited
nofiles(descriptors) 8192
memory(KBytes) unlimited
If your parameter settings differ from those above change these values accordingly
EXAMPLE
If you have to change the value for descriptors to 8192 proceed as follows
In csh execute
limit descriptors 8192
In sh or ksh execute
ulimit -n 8192
Before you start SAPinst read SAP Note 1697164 for more information about which user to choose
for running the SAPinst SDT GUI server
Procedure
1 Log on to the installation host as user root
CAUTION
Do not use an existing ltsapsidgtadm user
Only valid for Non-Standalone Engines and Clients |
CAUTION
Make sure that the root user has not set any environment variables for a different SAP system
or database
End of Non-Standalone Engines and Clients |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2754
2 Make the Dual-Stack Split Tool available on the installation host Make sure that it is available
locally We do not recommend that you use Network File System (NFS) because reading from
media mounted with NFS might fail
For more information see Preparation Checklist [page 17] and Preparing the Installation Media in the
installation documentation of your release
3 Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
Only valid for Non-Standalone Engines and Clients |
Change to the directory with the sapinst executable for your operating system by entering the
following command cd ltMountpoint of Installation Master mediumgtDATA_UNITS
ltproductgt_IM_ltOSgtEnd of Non-Standalone Engines and Clients |
End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
4 Start SAPinst by executing the following command sapinst
NOTE
If you want to use a virtual host name start SAPinst with the SAPinst property
SAPINST_USE_HOSTNAME as follows
Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
sapinst SAPINST_USE_HOSTNAME=ltvirtual host namegt
End of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
5 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
In addition if you want to use the split option ldquoMove Java Databaserdquo choose ltYour System
Variantgt
Perform the export and installation steps exactly in the order in which they appear
6 Only valid for Non-Standalone Engines and Clients |
Choose NextEnd of Non-Standalone Engines and Clients |
7 Follow the instructions in the SAPinst input screens and enter the required parameters
NOTE
If SAPinst asks for the Java DVD make sure that you provide a Java DVD with the same
release level as your dual-stack system
For more information about the input parameters position the cursor on the parameter
and press F1
After you have entered all requested input parameters SAPinst displays the Parameter Summary screen
This screen shows both the parameters that you entered and those that SAPinst set by default If
required you can revise the parameters before starting the split procedure
5 Splitting
52 Running SAPinst
2854 PUBLIC 2012-04-11
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you check the following parameters depending on the installation type that you
have chosenEnd of IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for Linux and UNIX and Windows |
If you are performing a typical installation SAPinst creates four sapdata directories by
default If you require more or fewer sapdata directories depending on the storage devices
you are using you must change this parameter before you start the installation By selecting
this parameter on the Summary screen and choosing Revise SAPinst returns to the IBM DB2 for
Linux UNIX and Windows ndashgt Sapdata Directories screen
On this screen you can also decide if you want SAPinst to create the regular table and index
tablespaces with DB2s automatic storage management enabled By default the option for
automatic storage management is preselected
NOTE
As of DB2 V91 and higher the database and the SYSCATSPACE tablespace are always created
with automatic storage management enabled even if you deselect this option on the
dialog IBM DB2 for Linux UNIX and Windows gt Sapdata Directories
For more information about DB2s automatic storage management see section DB2
Tablespaces in the installation documentation of your SAP product
If you are performing a custom installation you set these parameters during the Define
Parameters phase of SAPinst
NOTE
If the tablespace layout used by SAPinst does not meet your requirements you can create
the tablespaces manually by deselecting the option Create Tablespaces with SAPinst on the
IBM DB2 for Linux and UNIX and Windows Sapdata Directories screen
During the installation phase SAPinst then displays the following message
You must create the tablespaces now To do so use the
createTablespacessql script that is located in your installation
directory
To continue the installation choose OK Alternatively you can cancel
SAPinst here and restart it again
SAPinst does not check the page size of tablespaces that have either been created manually
or that already exist If you create the tablespaces manually you must make sure that
you use a page size of 16 KBEnd of IBM DB2 for Linux and UNIX and Windows |
8 To start the dual-stack split choose Start
SAPinst starts and displays the progress of the split procedure
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2954
When the split option has finished successfully SAPinst displays the message Execution of
ltOption_Namegt has completed
Only valid for Oracle |
NOTE
When installing the Oracle database instance SAPinst stops the installation and prompts
you to install the Oracle database software For more information see Installing the Oracle
Database Software in the installation documentation of your release
After you have finished the installation of the Oracle database you continue the database
instance installation by choosing OK in the GUI of the database instance installation
Check SAP Note 1431800 for technical information about Oracle Release 112 in SAP
environments
End of Oracle |
Only valid for Enterprise Portal (EP) |
NOTE
During the final restart of Application Server Java performed by SAPinst the portal starts the
processing and uploading of the new portal archives It takes approximately 15 to 90 minutes
before the deployment is completed and the portal is launched
Do not stop SAPinst or Application Server Java during this phase
End of Enterprise Portal (EP) |
9 If required delete directories with the name sapinst_exexxxxxxxxxx after SAPinst has finished
Sometimes these remain in the temporary directory
NOTE
If there are errors with the SAPinst extraction process you can find the log file
dev_selfexout in the temporary directory
Only valid for Non-Standalone Engines and Clients |
RECOMMENDATION
Keep all installation 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 installation 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 installation directories on installation hosts but make sure
that you delete them after saving them separately
End of Non-Standalone Engines and Clients |
10 We recommend that you delete the directory ltuser_homegtsdtgui
11 Only valid for IBM DB2 for Linux and UNIX and Windows |
If not already done install the DB2 license
5 Splitting
52 Running SAPinst
3054 PUBLIC 2012-04-11
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
End of IBM DB2 for Linux and UNIX and Windows |
12 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 3154
This page is left blank for documents that are printed on both sides
6 Follow-Up Activities
61 Follow-Up Activities Checklist
This section includes the follow-up activities that you have to perform for the following split options
ldquoMove Java Databaserdquo for a central system
ldquoMove Java Databaserdquo for a distributed system or a high-availability system
ldquoKeep Databaserdquo for a central distributed or high-availability system
NOTE
Some of the follow-up activities listed in this section are not described in this documentation You
can find the detailed description in the SAP NetWeaver Application Server Java system copy
documentation relevant for your release at
httpservicesapcominstguides
Move Java Database
Central System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3354
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
7 We recommend that you perform regression testing
8 On the source system you run SAPinst [page 23] to remove the Java parts in the file system and in
the database
9 On the source system you call transaction RZ10 to reimport the profiles from the file system
10 In the Transport Management System (TMS) you configure the transport routes [page 38]
11 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
12 You clean up the system landscape data [page 40]
Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3454 PUBLIC 2012-04-11
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the database host of the source system you run SAPinst [page 23] to remove the Java database
schema
12 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
13 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
14 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
15 You clean up the system landscape data [page 40]
Keep Database
Central Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3554
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
12 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
13 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
14 You clean up the system landscape data [page 40]
62 Maintaining the Connection to the System Landscape Directory
After installing the Java system you need to reconfigure the connection between the System Landscape
Directory (SLD) the source system and the target system The steps required differ depending on
whether you use a local or a central SLD To maintain the connection to the SLD you can either run
the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split or perform the required steps manually as described below
NOTE
This step is only required if the connection to the SLD was established on the source system before
the split
Prerequisites
If you want to use the configuration wizard you need an SAP NetWeaver Java system 70 Support
Package 14 or higher in your landscape
SLDAPIUSER credentials are available in the ABAP system
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3654 PUBLIC 2012-04-11
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
Figure 3 Split Option Keep Database for Central Systems
Figure 4 Split Option Keep Database for Distributed Systems
2 Split Options Covered by this Guide
22 Split Option Keep Database
1254 PUBLIC 2012-04-11
3 Planning
31 Planning Checklist
This section includes the planning steps that you have to perform when you want to install the new
Java system on one or more hosts Perform the planning steps according to the split option and your
system variant
NOTE
Most of the required planning steps listed in this section are not described in this documentation
You can find the detailed description in the SAP NetWeaver Application Server Java installation
documentation relevant for your release at httpservicesapcominstguides
Prerequisites
You have decided on your split option [page 9]
Split Option ldquoMove Java Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
1 You check the hardware and software requirements for the Java installation host
For more information see Hardware and Software Requirements in the installation documentation of
your release
2 You read about user management [page 15]
3 You identify basic SAP system installation parameters
For more information see Basic SAP System Parameters in the installation documentation of your
release
Be aware of the following dual-stack-split-specific deviations
SAP System Parameters
User management
We do not recommend that you make modifications in the user management settings
For more information see User Management [page 15]
System Landscape Directory (SLD)
You can ignore SLD parameters
Only valid for Oracle |
SAP System Database Parameters Java database schema
We recommend that you choose a schema ID that is different from your SAP system ID
It might cause problems when you copy a system if ltSCHEMA_IDgt is the same as ltSAPSIDgt and
the database-specific method used for the copy does not allow you to rename the database
3 Planning
31 Planning Checklist
2012-04-11 PUBLIC 1354
schemes In certain situations you might create a system copy with a new ltSAPSIDgt but where
the database schema has the old ltSAPSIDgt This is not a technical problem but might be
confusing to the system administratorEnd of Oracle |
4 Only valid for MaxDB |
You plan your system configuration
For more information see System Configuration in the installation documentation of your releaseEnd of MaxDB |
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
You plan the setup of your database carefully
For more information see Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
7 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 43]
8 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
9 Only valid for IBM DB2 for zOS |
If you want to execute a Software Life-Cycle Option with SAPinst in an SAP system with thick client
connectivity see Special Considerations Regarding Connectivity for Software Life-Cycle Options in the installation
documentation of your releaseEnd of IBM DB2 for zOS |
10 Only valid for IBM DB2 for i5OS |
Optionally you decide whether you want to install multiple SAP systems on a single host
For more information see Multiple SAP Systems on a Single Host in the installation documentation of
your releaseEnd of IBM DB2 for i5OS |
11 You can continue with Preparation [page 17]
Split Option ldquoKeep Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
1 You check the hardware and software requirements for the Java installation host
For more information see Hardware and Software Requirements in the installation documentation of
your release
2 You read about user management [page 15]
3 You identify basic SAP system installation parameters
For more information see Basic SAP System Parameters in the installation documentation of your
release
3 Planning
31 Planning Checklist
1454 PUBLIC 2012-04-11
Be aware of the following dual-stack-split-specific deviation for SAP System Parameters
User management
We do not recommend that you make modifications in the user management settings For
more information see User Management [page 15]
System Landscape Directory (SLD)
You can ignore SLD parameters
4 Only valid for IBM DB2 for zOSMaxDB |
You plan your system configuration
For more information see System Configuration in the installation documentation of your releaseEnd of IBM DB2 for zOSMaxDB |
5 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
6 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 43]
7 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
8 Only valid for IBM DB2 for zOS |
If you want to execute a Software Life-Cycle Option with SAPinst in an SAP system with thick client
connectivity see Special Considerations Regarding Connectivity for Software Life-Cycle Options in the installation
documentation of your releaseEnd of IBM DB2 for zOS |
9 Only valid for IBM DB2 for i5OS |
Optionally you decide whether you want to install multiple SAP systems on a single host
For more information see Multiple SAP Systems on a Single Host in the installation documentation of
your releaseEnd of IBM DB2 for i5OS |
10 You can continue with Preparation [page 17]
32 User Management
The dual-stack split procedure does not change the user management and you cannot choose which
kind of user management you want to use for the target AS Java system That is the separated Java
system and the ABAP system both use the user management of the former dual-stack system The
following is possible
If the dual-stack system uses AS ABAP as data source for the User Management Engine (UME)
after the split the separated Java stack will also use the ABAP UME
If the dual-stack system uses an LDAP directory as source for user data this is also valid for the Java
stack
3 Planning
32 User Management
2012-04-11 PUBLIC 1554
In both cases manual configuration is not required
We do not recommend that you make modifications to the user management settings
For more information see SAP Note 718383
3 Planning
32 User Management
1654 PUBLIC 2012-04-11
4 Preparation
41 Preparation Checklist
This section includes the preparation steps that you have to perform when you want to install the new
Java system on one or more hosts
NOTE
Most of the required preparation steps listed in this section are not described in this
documentation You can find the detailed description in the SAP NetWeaver Application Server
Java installation documentation relevant for your release at httpservicesapcom
instguides
1 Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
You make sure that the required operating system users and groups are created
To create the groups and users automatically run the Dual-Stack Split Tool on the host where
the SAP Java system is to be installed and choose Dual-Stack Split Operating System Users and
Groups
For more information see Creating Operating System Users and Groups in the installation documentation
of your releaseEnd of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
2 You set up file systems and make sure that the required disk space is available for the directories
to be created during the installation
For more information see Setting Up File Systems for a High-Availability System in the installation
documentation of your release
3 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
4 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
If you want to install a high-availability system you perform switchover preparations
For more information see Performing Switchover Preparations for High-Availability in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
5 If you want to share the transport directory trans from another system you export this directory
to your installation hosts
For more information see Exporting and Mounting the Global Transport Directory in the installation
documentation of your release
4 Preparation
41 Preparation Checklist
2012-04-11 PUBLIC 1754
6 You install the Java Development Kit This step is not required if you have installed the SAP JVM
4 on your source system
For more information see Installing the Java Development Kit in the installation documentation of your
release
7 You make sure that the required installation media are available on each host
You can download the Dual-Stack Split Tool at httpservicesapcomsltoolset
Software Logistics Toolset 10 Dual-Stack Split
You can download the Java stack and database installation media from SAP Service
Marketplace as described in Preparing the Installation Media in the installation documentation of
your release
NOTE
The release level required for the installation corresponds to the release level of your dual-
stack system
The following table shows the required installation media for the dual-stack split
SAP Instance Installation Required Media
Central services instance central instance
Dual-Stack Split Tool Java DVD RDBMS Client DVD
Move Java Database only Database instance
Dual-Stack Split Tool Java DVD Only valid for MS SQL ServerOracle |
RDBMS DVDEnd of MS SQL ServerOracle |
Only valid for MS SQL ServerOracle |
RDBMS Patch DVD (if available)End of MS SQL ServerOracle |
8 Only valid for HA (MSCS) |
To install a high-availability system with Microsoft Cluster Service (MSCS) you also perform the
MSCS-specific preparation tasks as described in the installation documentation of your releaseEnd of HA (MSCS) |
9 Only valid for HA (MSCS) |
If you choose the split option ldquoKeep Databaserdquo with the scenario ldquoKeep SCS on the Source Cluster
Systemrdquo you perform the following steps
You provide additional disk storage on the target cluster system
For more information see Distribution of SAP System Components to Disks for MSCS Directories in an
MSCS Configuration and IP Addresses in an MSCS Configuration in the installation documentation of
your release
You provide an additional IP address and an additional virtual host name for the Java system
For more information see Mapping Host Names to IP Addresses for MSCS in the installation
documentation of your releaseEnd of HA (MSCS) |
4 Preparation
41 Preparation Checklist
1854 PUBLIC 2012-04-11
10 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 19] of
the dual-stack system
11 You can continue with Splitting [page 21]
42 Performing a Full System Backup
If you decided to use the split option ldquoKeep Databaserdquo you must perform a full system backup of the
dual-stack system or at least a backup of the Java database schema before you start the split procedure
If you decided to use the split option ldquoMove Java Databaserdquo you do not need to perform a backup before
you start the split procedure
For more information about backing up your database see the database-specific backup and recovery
documentation in the SAP Library [page 7] at
SAP MaxDB
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for SAP
MaxDB
Oracle
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Oracle
IBM DB2 for i5OS
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 UDB for iSeries
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for i
4 Preparation
42 Performing a Full System Backup
2012-04-11 PUBLIC 1954
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
i
IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX
and Windows
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
Linux UNIX and Windows
IBM DB2 for zOS
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 UDB for zOS
SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for DB2 for z
OS
Microsoft SQL Server
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Microsoft SQL
Server
4 Preparation
42 Performing a Full System Backup
2054 PUBLIC 2012-04-11
5 Splitting
51 Splitting Checklist
This section includes the splitting steps that you have to perform for the following split options
ldquoMove Java Databaserdquo
ldquoKeep Databaserdquo
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Only valid for Oracle |
You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 You export the Java stack using SAPinst [page 23]
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
4 You restart the source system
5 You run SAPinst [page 23] to install a Java only system using the export from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2012-04-11 PUBLIC 2154
Distributed System
1 Only valid for Oracle |
On the database instance host of the dual-stack system you install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes on the database instance host
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 On the database instance host of the dual-stack system you run SAPinst [page 23] to export the
Java database schema
4 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the Java
parts of the file system of the central instance
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
5 You restart the source system
6 You run SAPinst [page 23] to install a central services instance for the Java target system
7 You run SAPinst [page 23] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
9 You continue with Follow-Up Activities [page 33]
Keep Database
1 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the
file system of the central instance
5 Splitting
51 Splitting Checklist
2254 PUBLIC 2012-04-11
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you wont use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
2 You restart the source system
3 You run SAPinst [page 23] to install a central services instance for the Java target system
4 On the database instance host of the dual-stack system you run SAPinst [page 23] to adapt the
database for the Java target system
NOTE
Make sure that you enter the profile directory of the Java target system in the SAP System gt
General Parameters screen
5 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
52 Running SAPinst
This section describes how to run the installation tool SAPinst SAPinst includes a GUI client and a GUI
server which both use Java
The procedure describes an installation where SAPinst GUI client and GUI server are running on the
same host In the following GUI client and GUI server are addressed as ldquoSAPinst GUIrdquo
If you need to see the installation on a remote display we recommend that you perform a remote
installation with SAPinst where the SAPinst GUI is running on a separate host from SAPinst For more
information see Performing a Remote Installation with SAPinst in the installation documentation of your
release
Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote
access to SAPinst GUI on Windows workstations For more information see SAP Note 1170809
Useful Information About SAPinst
When you start SAPinst it automatically starts the SAPinst GUI
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2354
SAPinst creates the installation directory sapinst_instdir directly below the temporary directory
SAPinst 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 SAPinst
creates the installation directory sapinst_instdir directly below the tmp directory by default
If you want SAPinst to create the installation directory sapinst_instdir in another directory set
the environment variable TEMP to this directory before you start SAPinst
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
Only valid for IBM DB2 for i5OS |
NOTE
When you leave your Qp2Term session all changes of the environment variables done by the
command export are reverted
End of IBM DB2 for i5OS |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
SAPinst creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt
SAPinst extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is located
in the environment variables TEMP TMP or TMPDIR These files are deleted after SAPinst has stopped
running
The temporary directory sapinst_exexxxxxxxxxx sometimes remains undeleted You can safely
delete it
The temporary directory also contains the log file dev_selfexout from the extraction process
which might be useful if an error occurs
CAUTION
If SAPinst cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default ports 21200 21212 and 4239 are used for communication
between SAPinst GUI server GUI and HTTP server as follows
SAPinst uses port 21200 to communicate with the GUI server
The GUI server uses port 21212 to communicate with the GUI client
5 Splitting
52 Running SAPinst
2454 PUBLIC 2012-04-11
4239 is the port of the HTTP server which is part of the GUI server
If the ports for SAPinst and the GUI server are already in use SAPinst automatically searches for
free port numbers If the search fails SAPinst exits
In this case or if you want SAPinst to use specific ports you can assign them by executing the
sapinst executable with the following command line parameters
SAPINST_DIALOG_PORT=ltport_number_sapinst_to_gui_servergt
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
GUISERVER_HTTP_PORT=ltport_number_http_servergt
To see a list of all available SAPinst properties start SAPinst as described above with command line
parameter -p
sapinst -p
If you need to run SAPinst in accessibility mode proceed as described in Running SAPinst in Accessibility
Mode in the installation documentation of your release
If required you can stop SAPinst by choosing SAPinst Cancel in the SAPinst GUI menu
Prerequisites
We recommend that you use the csh shell for the installation with SAPinst If you want to use
another shell make sure that you have first read SAP Note 202227
SAPinst uses csh scripts during the installation to obtain the environment for user ltsapsidgtadm
This is also true if user ltsapsidgtadm already exists from an earlier SAP system installation and the
shell of this user is not csh Before you start SAPinst execute the following command as user
ltsapsidgtadm to make sure that the csh scripts are up-to-date
bincsh -c source lthome directory of ltsapsidgtadmgtcshrcenv
Make sure that you have specified the most important SAP system parameters as described in Basic
SAP System Installation Parameters in the installation documentation of your release before you start
SAPinst
Only valid for IBM DB2 for zOS |
Check that your installation hosts meet the requirements for the installation options that you
want to installEnd of IBM DB2 for zOS |
Only valid for Non-Standalone Engines and Clients |
If you want to perform a distributed or a high-availability installation make sure that you have
exported and mounted global directories For more information see Exporting and Mounting Global
Directories in the installation documentation of your releaseEnd of Non-Standalone Engines and Clients |
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you have carefully planned your database layout in particular the tablespace layout
as described in Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2554
Only valid for AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for Solaris |
Solaris SPARC onlyEnd of Solaris |
If you want to set up DB2s high-availability cluster solution SA MP make sure that you have read
the document IBM DB2 High Availability Solution IBM Tivoli System Automation for Multiplatforms at
httpservicesapcominstguidesnw70 Installation Installation ndash SAP NetWeaver SystemsEnd of AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for zOS |
First make sure that you have installed DB2 for zOS For information on that installation see
SAP DBA Guide DB2 for zOS DB2 Setup especially the section Stored Procedures EnablementEnd of IBM DB2 for zOS |
Check the value of the environment variable TEMP TMP or TMPDIR
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
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 ndash for example by using a crontab entry
Make sure that you have at least 60 MB of free space in the installation directory for each
installation option In addition you need 200 MB free space for the SAPinst executables If you
cannot provide 200 MB free space in the temporary directory you can set one of the
environment variables TEMP TMP or TMPDIR to another directory with 200 MB free space for
the SAPinst executables
Make sure that the temporary directory has the permissions 777
Only valid for IBM DB2 for zOS |
Make sure that your database is up and runningEnd of IBM DB2 for zOS |
Make sure that your DISPLAY environment variable is set to lthost_namegt00 where
lthost_namegt is the host on which you want to display the GUI
Shell Used Command
Bourne shell (sh) DISPLAY=lthost_namegt00
export DISPLAY
C shell (csh) setenv DISPLAY lthost_namegt00
Korn shell (ksh) export DISPLAY=lthost_namegt00
Make sure that umask is set to 022 for user root
As user root enter the following command umask 022
Check the following values for user root
5 Splitting
52 Running SAPinst
2654 PUBLIC 2012-04-11
In csh execute limit
Output Properties
cputime unlimited
filesize unlimited
datasize unlimited
stacksize 8192 KB
coredumpsize unlimited
descriptors 8192
memorysize unlimited
In sh or ksh execute ulimit -a
Output Properties
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192
coredump(blocks) unlimited
nofiles(descriptors) 8192
memory(KBytes) unlimited
If your parameter settings differ from those above change these values accordingly
EXAMPLE
If you have to change the value for descriptors to 8192 proceed as follows
In csh execute
limit descriptors 8192
In sh or ksh execute
ulimit -n 8192
Before you start SAPinst read SAP Note 1697164 for more information about which user to choose
for running the SAPinst SDT GUI server
Procedure
1 Log on to the installation host as user root
CAUTION
Do not use an existing ltsapsidgtadm user
Only valid for Non-Standalone Engines and Clients |
CAUTION
Make sure that the root user has not set any environment variables for a different SAP system
or database
End of Non-Standalone Engines and Clients |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2754
2 Make the Dual-Stack Split Tool available on the installation host Make sure that it is available
locally We do not recommend that you use Network File System (NFS) because reading from
media mounted with NFS might fail
For more information see Preparation Checklist [page 17] and Preparing the Installation Media in the
installation documentation of your release
3 Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
Only valid for Non-Standalone Engines and Clients |
Change to the directory with the sapinst executable for your operating system by entering the
following command cd ltMountpoint of Installation Master mediumgtDATA_UNITS
ltproductgt_IM_ltOSgtEnd of Non-Standalone Engines and Clients |
End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
4 Start SAPinst by executing the following command sapinst
NOTE
If you want to use a virtual host name start SAPinst with the SAPinst property
SAPINST_USE_HOSTNAME as follows
Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
sapinst SAPINST_USE_HOSTNAME=ltvirtual host namegt
End of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
5 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
In addition if you want to use the split option ldquoMove Java Databaserdquo choose ltYour System
Variantgt
Perform the export and installation steps exactly in the order in which they appear
6 Only valid for Non-Standalone Engines and Clients |
Choose NextEnd of Non-Standalone Engines and Clients |
7 Follow the instructions in the SAPinst input screens and enter the required parameters
NOTE
If SAPinst asks for the Java DVD make sure that you provide a Java DVD with the same
release level as your dual-stack system
For more information about the input parameters position the cursor on the parameter
and press F1
After you have entered all requested input parameters SAPinst displays the Parameter Summary screen
This screen shows both the parameters that you entered and those that SAPinst set by default If
required you can revise the parameters before starting the split procedure
5 Splitting
52 Running SAPinst
2854 PUBLIC 2012-04-11
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you check the following parameters depending on the installation type that you
have chosenEnd of IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for Linux and UNIX and Windows |
If you are performing a typical installation SAPinst creates four sapdata directories by
default If you require more or fewer sapdata directories depending on the storage devices
you are using you must change this parameter before you start the installation By selecting
this parameter on the Summary screen and choosing Revise SAPinst returns to the IBM DB2 for
Linux UNIX and Windows ndashgt Sapdata Directories screen
On this screen you can also decide if you want SAPinst to create the regular table and index
tablespaces with DB2s automatic storage management enabled By default the option for
automatic storage management is preselected
NOTE
As of DB2 V91 and higher the database and the SYSCATSPACE tablespace are always created
with automatic storage management enabled even if you deselect this option on the
dialog IBM DB2 for Linux UNIX and Windows gt Sapdata Directories
For more information about DB2s automatic storage management see section DB2
Tablespaces in the installation documentation of your SAP product
If you are performing a custom installation you set these parameters during the Define
Parameters phase of SAPinst
NOTE
If the tablespace layout used by SAPinst does not meet your requirements you can create
the tablespaces manually by deselecting the option Create Tablespaces with SAPinst on the
IBM DB2 for Linux and UNIX and Windows Sapdata Directories screen
During the installation phase SAPinst then displays the following message
You must create the tablespaces now To do so use the
createTablespacessql script that is located in your installation
directory
To continue the installation choose OK Alternatively you can cancel
SAPinst here and restart it again
SAPinst does not check the page size of tablespaces that have either been created manually
or that already exist If you create the tablespaces manually you must make sure that
you use a page size of 16 KBEnd of IBM DB2 for Linux and UNIX and Windows |
8 To start the dual-stack split choose Start
SAPinst starts and displays the progress of the split procedure
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2954
When the split option has finished successfully SAPinst displays the message Execution of
ltOption_Namegt has completed
Only valid for Oracle |
NOTE
When installing the Oracle database instance SAPinst stops the installation and prompts
you to install the Oracle database software For more information see Installing the Oracle
Database Software in the installation documentation of your release
After you have finished the installation of the Oracle database you continue the database
instance installation by choosing OK in the GUI of the database instance installation
Check SAP Note 1431800 for technical information about Oracle Release 112 in SAP
environments
End of Oracle |
Only valid for Enterprise Portal (EP) |
NOTE
During the final restart of Application Server Java performed by SAPinst the portal starts the
processing and uploading of the new portal archives It takes approximately 15 to 90 minutes
before the deployment is completed and the portal is launched
Do not stop SAPinst or Application Server Java during this phase
End of Enterprise Portal (EP) |
9 If required delete directories with the name sapinst_exexxxxxxxxxx after SAPinst has finished
Sometimes these remain in the temporary directory
NOTE
If there are errors with the SAPinst extraction process you can find the log file
dev_selfexout in the temporary directory
Only valid for Non-Standalone Engines and Clients |
RECOMMENDATION
Keep all installation 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 installation 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 installation directories on installation hosts but make sure
that you delete them after saving them separately
End of Non-Standalone Engines and Clients |
10 We recommend that you delete the directory ltuser_homegtsdtgui
11 Only valid for IBM DB2 for Linux and UNIX and Windows |
If not already done install the DB2 license
5 Splitting
52 Running SAPinst
3054 PUBLIC 2012-04-11
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
End of IBM DB2 for Linux and UNIX and Windows |
12 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 3154
This page is left blank for documents that are printed on both sides
6 Follow-Up Activities
61 Follow-Up Activities Checklist
This section includes the follow-up activities that you have to perform for the following split options
ldquoMove Java Databaserdquo for a central system
ldquoMove Java Databaserdquo for a distributed system or a high-availability system
ldquoKeep Databaserdquo for a central distributed or high-availability system
NOTE
Some of the follow-up activities listed in this section are not described in this documentation You
can find the detailed description in the SAP NetWeaver Application Server Java system copy
documentation relevant for your release at
httpservicesapcominstguides
Move Java Database
Central System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3354
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
7 We recommend that you perform regression testing
8 On the source system you run SAPinst [page 23] to remove the Java parts in the file system and in
the database
9 On the source system you call transaction RZ10 to reimport the profiles from the file system
10 In the Transport Management System (TMS) you configure the transport routes [page 38]
11 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
12 You clean up the system landscape data [page 40]
Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3454 PUBLIC 2012-04-11
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the database host of the source system you run SAPinst [page 23] to remove the Java database
schema
12 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
13 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
14 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
15 You clean up the system landscape data [page 40]
Keep Database
Central Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3554
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
12 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
13 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
14 You clean up the system landscape data [page 40]
62 Maintaining the Connection to the System Landscape Directory
After installing the Java system you need to reconfigure the connection between the System Landscape
Directory (SLD) the source system and the target system The steps required differ depending on
whether you use a local or a central SLD To maintain the connection to the SLD you can either run
the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split or perform the required steps manually as described below
NOTE
This step is only required if the connection to the SLD was established on the source system before
the split
Prerequisites
If you want to use the configuration wizard you need an SAP NetWeaver Java system 70 Support
Package 14 or higher in your landscape
SLDAPIUSER credentials are available in the ABAP system
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3654 PUBLIC 2012-04-11
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
3 Planning
31 Planning Checklist
This section includes the planning steps that you have to perform when you want to install the new
Java system on one or more hosts Perform the planning steps according to the split option and your
system variant
NOTE
Most of the required planning steps listed in this section are not described in this documentation
You can find the detailed description in the SAP NetWeaver Application Server Java installation
documentation relevant for your release at httpservicesapcominstguides
Prerequisites
You have decided on your split option [page 9]
Split Option ldquoMove Java Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
1 You check the hardware and software requirements for the Java installation host
For more information see Hardware and Software Requirements in the installation documentation of
your release
2 You read about user management [page 15]
3 You identify basic SAP system installation parameters
For more information see Basic SAP System Parameters in the installation documentation of your
release
Be aware of the following dual-stack-split-specific deviations
SAP System Parameters
User management
We do not recommend that you make modifications in the user management settings
For more information see User Management [page 15]
System Landscape Directory (SLD)
You can ignore SLD parameters
Only valid for Oracle |
SAP System Database Parameters Java database schema
We recommend that you choose a schema ID that is different from your SAP system ID
It might cause problems when you copy a system if ltSCHEMA_IDgt is the same as ltSAPSIDgt and
the database-specific method used for the copy does not allow you to rename the database
3 Planning
31 Planning Checklist
2012-04-11 PUBLIC 1354
schemes In certain situations you might create a system copy with a new ltSAPSIDgt but where
the database schema has the old ltSAPSIDgt This is not a technical problem but might be
confusing to the system administratorEnd of Oracle |
4 Only valid for MaxDB |
You plan your system configuration
For more information see System Configuration in the installation documentation of your releaseEnd of MaxDB |
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
You plan the setup of your database carefully
For more information see Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
7 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 43]
8 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
9 Only valid for IBM DB2 for zOS |
If you want to execute a Software Life-Cycle Option with SAPinst in an SAP system with thick client
connectivity see Special Considerations Regarding Connectivity for Software Life-Cycle Options in the installation
documentation of your releaseEnd of IBM DB2 for zOS |
10 Only valid for IBM DB2 for i5OS |
Optionally you decide whether you want to install multiple SAP systems on a single host
For more information see Multiple SAP Systems on a Single Host in the installation documentation of
your releaseEnd of IBM DB2 for i5OS |
11 You can continue with Preparation [page 17]
Split Option ldquoKeep Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
1 You check the hardware and software requirements for the Java installation host
For more information see Hardware and Software Requirements in the installation documentation of
your release
2 You read about user management [page 15]
3 You identify basic SAP system installation parameters
For more information see Basic SAP System Parameters in the installation documentation of your
release
3 Planning
31 Planning Checklist
1454 PUBLIC 2012-04-11
Be aware of the following dual-stack-split-specific deviation for SAP System Parameters
User management
We do not recommend that you make modifications in the user management settings For
more information see User Management [page 15]
System Landscape Directory (SLD)
You can ignore SLD parameters
4 Only valid for IBM DB2 for zOSMaxDB |
You plan your system configuration
For more information see System Configuration in the installation documentation of your releaseEnd of IBM DB2 for zOSMaxDB |
5 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
6 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 43]
7 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
8 Only valid for IBM DB2 for zOS |
If you want to execute a Software Life-Cycle Option with SAPinst in an SAP system with thick client
connectivity see Special Considerations Regarding Connectivity for Software Life-Cycle Options in the installation
documentation of your releaseEnd of IBM DB2 for zOS |
9 Only valid for IBM DB2 for i5OS |
Optionally you decide whether you want to install multiple SAP systems on a single host
For more information see Multiple SAP Systems on a Single Host in the installation documentation of
your releaseEnd of IBM DB2 for i5OS |
10 You can continue with Preparation [page 17]
32 User Management
The dual-stack split procedure does not change the user management and you cannot choose which
kind of user management you want to use for the target AS Java system That is the separated Java
system and the ABAP system both use the user management of the former dual-stack system The
following is possible
If the dual-stack system uses AS ABAP as data source for the User Management Engine (UME)
after the split the separated Java stack will also use the ABAP UME
If the dual-stack system uses an LDAP directory as source for user data this is also valid for the Java
stack
3 Planning
32 User Management
2012-04-11 PUBLIC 1554
In both cases manual configuration is not required
We do not recommend that you make modifications to the user management settings
For more information see SAP Note 718383
3 Planning
32 User Management
1654 PUBLIC 2012-04-11
4 Preparation
41 Preparation Checklist
This section includes the preparation steps that you have to perform when you want to install the new
Java system on one or more hosts
NOTE
Most of the required preparation steps listed in this section are not described in this
documentation You can find the detailed description in the SAP NetWeaver Application Server
Java installation documentation relevant for your release at httpservicesapcom
instguides
1 Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
You make sure that the required operating system users and groups are created
To create the groups and users automatically run the Dual-Stack Split Tool on the host where
the SAP Java system is to be installed and choose Dual-Stack Split Operating System Users and
Groups
For more information see Creating Operating System Users and Groups in the installation documentation
of your releaseEnd of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
2 You set up file systems and make sure that the required disk space is available for the directories
to be created during the installation
For more information see Setting Up File Systems for a High-Availability System in the installation
documentation of your release
3 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
4 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
If you want to install a high-availability system you perform switchover preparations
For more information see Performing Switchover Preparations for High-Availability in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
5 If you want to share the transport directory trans from another system you export this directory
to your installation hosts
For more information see Exporting and Mounting the Global Transport Directory in the installation
documentation of your release
4 Preparation
41 Preparation Checklist
2012-04-11 PUBLIC 1754
6 You install the Java Development Kit This step is not required if you have installed the SAP JVM
4 on your source system
For more information see Installing the Java Development Kit in the installation documentation of your
release
7 You make sure that the required installation media are available on each host
You can download the Dual-Stack Split Tool at httpservicesapcomsltoolset
Software Logistics Toolset 10 Dual-Stack Split
You can download the Java stack and database installation media from SAP Service
Marketplace as described in Preparing the Installation Media in the installation documentation of
your release
NOTE
The release level required for the installation corresponds to the release level of your dual-
stack system
The following table shows the required installation media for the dual-stack split
SAP Instance Installation Required Media
Central services instance central instance
Dual-Stack Split Tool Java DVD RDBMS Client DVD
Move Java Database only Database instance
Dual-Stack Split Tool Java DVD Only valid for MS SQL ServerOracle |
RDBMS DVDEnd of MS SQL ServerOracle |
Only valid for MS SQL ServerOracle |
RDBMS Patch DVD (if available)End of MS SQL ServerOracle |
8 Only valid for HA (MSCS) |
To install a high-availability system with Microsoft Cluster Service (MSCS) you also perform the
MSCS-specific preparation tasks as described in the installation documentation of your releaseEnd of HA (MSCS) |
9 Only valid for HA (MSCS) |
If you choose the split option ldquoKeep Databaserdquo with the scenario ldquoKeep SCS on the Source Cluster
Systemrdquo you perform the following steps
You provide additional disk storage on the target cluster system
For more information see Distribution of SAP System Components to Disks for MSCS Directories in an
MSCS Configuration and IP Addresses in an MSCS Configuration in the installation documentation of
your release
You provide an additional IP address and an additional virtual host name for the Java system
For more information see Mapping Host Names to IP Addresses for MSCS in the installation
documentation of your releaseEnd of HA (MSCS) |
4 Preparation
41 Preparation Checklist
1854 PUBLIC 2012-04-11
10 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 19] of
the dual-stack system
11 You can continue with Splitting [page 21]
42 Performing a Full System Backup
If you decided to use the split option ldquoKeep Databaserdquo you must perform a full system backup of the
dual-stack system or at least a backup of the Java database schema before you start the split procedure
If you decided to use the split option ldquoMove Java Databaserdquo you do not need to perform a backup before
you start the split procedure
For more information about backing up your database see the database-specific backup and recovery
documentation in the SAP Library [page 7] at
SAP MaxDB
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for SAP
MaxDB
Oracle
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Oracle
IBM DB2 for i5OS
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 UDB for iSeries
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for i
4 Preparation
42 Performing a Full System Backup
2012-04-11 PUBLIC 1954
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
i
IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX
and Windows
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
Linux UNIX and Windows
IBM DB2 for zOS
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 UDB for zOS
SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for DB2 for z
OS
Microsoft SQL Server
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Microsoft SQL
Server
4 Preparation
42 Performing a Full System Backup
2054 PUBLIC 2012-04-11
5 Splitting
51 Splitting Checklist
This section includes the splitting steps that you have to perform for the following split options
ldquoMove Java Databaserdquo
ldquoKeep Databaserdquo
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Only valid for Oracle |
You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 You export the Java stack using SAPinst [page 23]
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
4 You restart the source system
5 You run SAPinst [page 23] to install a Java only system using the export from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2012-04-11 PUBLIC 2154
Distributed System
1 Only valid for Oracle |
On the database instance host of the dual-stack system you install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes on the database instance host
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 On the database instance host of the dual-stack system you run SAPinst [page 23] to export the
Java database schema
4 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the Java
parts of the file system of the central instance
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
5 You restart the source system
6 You run SAPinst [page 23] to install a central services instance for the Java target system
7 You run SAPinst [page 23] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
9 You continue with Follow-Up Activities [page 33]
Keep Database
1 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the
file system of the central instance
5 Splitting
51 Splitting Checklist
2254 PUBLIC 2012-04-11
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you wont use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
2 You restart the source system
3 You run SAPinst [page 23] to install a central services instance for the Java target system
4 On the database instance host of the dual-stack system you run SAPinst [page 23] to adapt the
database for the Java target system
NOTE
Make sure that you enter the profile directory of the Java target system in the SAP System gt
General Parameters screen
5 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
52 Running SAPinst
This section describes how to run the installation tool SAPinst SAPinst includes a GUI client and a GUI
server which both use Java
The procedure describes an installation where SAPinst GUI client and GUI server are running on the
same host In the following GUI client and GUI server are addressed as ldquoSAPinst GUIrdquo
If you need to see the installation on a remote display we recommend that you perform a remote
installation with SAPinst where the SAPinst GUI is running on a separate host from SAPinst For more
information see Performing a Remote Installation with SAPinst in the installation documentation of your
release
Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote
access to SAPinst GUI on Windows workstations For more information see SAP Note 1170809
Useful Information About SAPinst
When you start SAPinst it automatically starts the SAPinst GUI
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2354
SAPinst creates the installation directory sapinst_instdir directly below the temporary directory
SAPinst 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 SAPinst
creates the installation directory sapinst_instdir directly below the tmp directory by default
If you want SAPinst to create the installation directory sapinst_instdir in another directory set
the environment variable TEMP to this directory before you start SAPinst
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
Only valid for IBM DB2 for i5OS |
NOTE
When you leave your Qp2Term session all changes of the environment variables done by the
command export are reverted
End of IBM DB2 for i5OS |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
SAPinst creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt
SAPinst extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is located
in the environment variables TEMP TMP or TMPDIR These files are deleted after SAPinst has stopped
running
The temporary directory sapinst_exexxxxxxxxxx sometimes remains undeleted You can safely
delete it
The temporary directory also contains the log file dev_selfexout from the extraction process
which might be useful if an error occurs
CAUTION
If SAPinst cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default ports 21200 21212 and 4239 are used for communication
between SAPinst GUI server GUI and HTTP server as follows
SAPinst uses port 21200 to communicate with the GUI server
The GUI server uses port 21212 to communicate with the GUI client
5 Splitting
52 Running SAPinst
2454 PUBLIC 2012-04-11
4239 is the port of the HTTP server which is part of the GUI server
If the ports for SAPinst and the GUI server are already in use SAPinst automatically searches for
free port numbers If the search fails SAPinst exits
In this case or if you want SAPinst to use specific ports you can assign them by executing the
sapinst executable with the following command line parameters
SAPINST_DIALOG_PORT=ltport_number_sapinst_to_gui_servergt
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
GUISERVER_HTTP_PORT=ltport_number_http_servergt
To see a list of all available SAPinst properties start SAPinst as described above with command line
parameter -p
sapinst -p
If you need to run SAPinst in accessibility mode proceed as described in Running SAPinst in Accessibility
Mode in the installation documentation of your release
If required you can stop SAPinst by choosing SAPinst Cancel in the SAPinst GUI menu
Prerequisites
We recommend that you use the csh shell for the installation with SAPinst If you want to use
another shell make sure that you have first read SAP Note 202227
SAPinst uses csh scripts during the installation to obtain the environment for user ltsapsidgtadm
This is also true if user ltsapsidgtadm already exists from an earlier SAP system installation and the
shell of this user is not csh Before you start SAPinst execute the following command as user
ltsapsidgtadm to make sure that the csh scripts are up-to-date
bincsh -c source lthome directory of ltsapsidgtadmgtcshrcenv
Make sure that you have specified the most important SAP system parameters as described in Basic
SAP System Installation Parameters in the installation documentation of your release before you start
SAPinst
Only valid for IBM DB2 for zOS |
Check that your installation hosts meet the requirements for the installation options that you
want to installEnd of IBM DB2 for zOS |
Only valid for Non-Standalone Engines and Clients |
If you want to perform a distributed or a high-availability installation make sure that you have
exported and mounted global directories For more information see Exporting and Mounting Global
Directories in the installation documentation of your releaseEnd of Non-Standalone Engines and Clients |
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you have carefully planned your database layout in particular the tablespace layout
as described in Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2554
Only valid for AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for Solaris |
Solaris SPARC onlyEnd of Solaris |
If you want to set up DB2s high-availability cluster solution SA MP make sure that you have read
the document IBM DB2 High Availability Solution IBM Tivoli System Automation for Multiplatforms at
httpservicesapcominstguidesnw70 Installation Installation ndash SAP NetWeaver SystemsEnd of AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for zOS |
First make sure that you have installed DB2 for zOS For information on that installation see
SAP DBA Guide DB2 for zOS DB2 Setup especially the section Stored Procedures EnablementEnd of IBM DB2 for zOS |
Check the value of the environment variable TEMP TMP or TMPDIR
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
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 ndash for example by using a crontab entry
Make sure that you have at least 60 MB of free space in the installation directory for each
installation option In addition you need 200 MB free space for the SAPinst executables If you
cannot provide 200 MB free space in the temporary directory you can set one of the
environment variables TEMP TMP or TMPDIR to another directory with 200 MB free space for
the SAPinst executables
Make sure that the temporary directory has the permissions 777
Only valid for IBM DB2 for zOS |
Make sure that your database is up and runningEnd of IBM DB2 for zOS |
Make sure that your DISPLAY environment variable is set to lthost_namegt00 where
lthost_namegt is the host on which you want to display the GUI
Shell Used Command
Bourne shell (sh) DISPLAY=lthost_namegt00
export DISPLAY
C shell (csh) setenv DISPLAY lthost_namegt00
Korn shell (ksh) export DISPLAY=lthost_namegt00
Make sure that umask is set to 022 for user root
As user root enter the following command umask 022
Check the following values for user root
5 Splitting
52 Running SAPinst
2654 PUBLIC 2012-04-11
In csh execute limit
Output Properties
cputime unlimited
filesize unlimited
datasize unlimited
stacksize 8192 KB
coredumpsize unlimited
descriptors 8192
memorysize unlimited
In sh or ksh execute ulimit -a
Output Properties
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192
coredump(blocks) unlimited
nofiles(descriptors) 8192
memory(KBytes) unlimited
If your parameter settings differ from those above change these values accordingly
EXAMPLE
If you have to change the value for descriptors to 8192 proceed as follows
In csh execute
limit descriptors 8192
In sh or ksh execute
ulimit -n 8192
Before you start SAPinst read SAP Note 1697164 for more information about which user to choose
for running the SAPinst SDT GUI server
Procedure
1 Log on to the installation host as user root
CAUTION
Do not use an existing ltsapsidgtadm user
Only valid for Non-Standalone Engines and Clients |
CAUTION
Make sure that the root user has not set any environment variables for a different SAP system
or database
End of Non-Standalone Engines and Clients |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2754
2 Make the Dual-Stack Split Tool available on the installation host Make sure that it is available
locally We do not recommend that you use Network File System (NFS) because reading from
media mounted with NFS might fail
For more information see Preparation Checklist [page 17] and Preparing the Installation Media in the
installation documentation of your release
3 Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
Only valid for Non-Standalone Engines and Clients |
Change to the directory with the sapinst executable for your operating system by entering the
following command cd ltMountpoint of Installation Master mediumgtDATA_UNITS
ltproductgt_IM_ltOSgtEnd of Non-Standalone Engines and Clients |
End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
4 Start SAPinst by executing the following command sapinst
NOTE
If you want to use a virtual host name start SAPinst with the SAPinst property
SAPINST_USE_HOSTNAME as follows
Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
sapinst SAPINST_USE_HOSTNAME=ltvirtual host namegt
End of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
5 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
In addition if you want to use the split option ldquoMove Java Databaserdquo choose ltYour System
Variantgt
Perform the export and installation steps exactly in the order in which they appear
6 Only valid for Non-Standalone Engines and Clients |
Choose NextEnd of Non-Standalone Engines and Clients |
7 Follow the instructions in the SAPinst input screens and enter the required parameters
NOTE
If SAPinst asks for the Java DVD make sure that you provide a Java DVD with the same
release level as your dual-stack system
For more information about the input parameters position the cursor on the parameter
and press F1
After you have entered all requested input parameters SAPinst displays the Parameter Summary screen
This screen shows both the parameters that you entered and those that SAPinst set by default If
required you can revise the parameters before starting the split procedure
5 Splitting
52 Running SAPinst
2854 PUBLIC 2012-04-11
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you check the following parameters depending on the installation type that you
have chosenEnd of IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for Linux and UNIX and Windows |
If you are performing a typical installation SAPinst creates four sapdata directories by
default If you require more or fewer sapdata directories depending on the storage devices
you are using you must change this parameter before you start the installation By selecting
this parameter on the Summary screen and choosing Revise SAPinst returns to the IBM DB2 for
Linux UNIX and Windows ndashgt Sapdata Directories screen
On this screen you can also decide if you want SAPinst to create the regular table and index
tablespaces with DB2s automatic storage management enabled By default the option for
automatic storage management is preselected
NOTE
As of DB2 V91 and higher the database and the SYSCATSPACE tablespace are always created
with automatic storage management enabled even if you deselect this option on the
dialog IBM DB2 for Linux UNIX and Windows gt Sapdata Directories
For more information about DB2s automatic storage management see section DB2
Tablespaces in the installation documentation of your SAP product
If you are performing a custom installation you set these parameters during the Define
Parameters phase of SAPinst
NOTE
If the tablespace layout used by SAPinst does not meet your requirements you can create
the tablespaces manually by deselecting the option Create Tablespaces with SAPinst on the
IBM DB2 for Linux and UNIX and Windows Sapdata Directories screen
During the installation phase SAPinst then displays the following message
You must create the tablespaces now To do so use the
createTablespacessql script that is located in your installation
directory
To continue the installation choose OK Alternatively you can cancel
SAPinst here and restart it again
SAPinst does not check the page size of tablespaces that have either been created manually
or that already exist If you create the tablespaces manually you must make sure that
you use a page size of 16 KBEnd of IBM DB2 for Linux and UNIX and Windows |
8 To start the dual-stack split choose Start
SAPinst starts and displays the progress of the split procedure
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2954
When the split option has finished successfully SAPinst displays the message Execution of
ltOption_Namegt has completed
Only valid for Oracle |
NOTE
When installing the Oracle database instance SAPinst stops the installation and prompts
you to install the Oracle database software For more information see Installing the Oracle
Database Software in the installation documentation of your release
After you have finished the installation of the Oracle database you continue the database
instance installation by choosing OK in the GUI of the database instance installation
Check SAP Note 1431800 for technical information about Oracle Release 112 in SAP
environments
End of Oracle |
Only valid for Enterprise Portal (EP) |
NOTE
During the final restart of Application Server Java performed by SAPinst the portal starts the
processing and uploading of the new portal archives It takes approximately 15 to 90 minutes
before the deployment is completed and the portal is launched
Do not stop SAPinst or Application Server Java during this phase
End of Enterprise Portal (EP) |
9 If required delete directories with the name sapinst_exexxxxxxxxxx after SAPinst has finished
Sometimes these remain in the temporary directory
NOTE
If there are errors with the SAPinst extraction process you can find the log file
dev_selfexout in the temporary directory
Only valid for Non-Standalone Engines and Clients |
RECOMMENDATION
Keep all installation 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 installation 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 installation directories on installation hosts but make sure
that you delete them after saving them separately
End of Non-Standalone Engines and Clients |
10 We recommend that you delete the directory ltuser_homegtsdtgui
11 Only valid for IBM DB2 for Linux and UNIX and Windows |
If not already done install the DB2 license
5 Splitting
52 Running SAPinst
3054 PUBLIC 2012-04-11
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
End of IBM DB2 for Linux and UNIX and Windows |
12 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 3154
This page is left blank for documents that are printed on both sides
6 Follow-Up Activities
61 Follow-Up Activities Checklist
This section includes the follow-up activities that you have to perform for the following split options
ldquoMove Java Databaserdquo for a central system
ldquoMove Java Databaserdquo for a distributed system or a high-availability system
ldquoKeep Databaserdquo for a central distributed or high-availability system
NOTE
Some of the follow-up activities listed in this section are not described in this documentation You
can find the detailed description in the SAP NetWeaver Application Server Java system copy
documentation relevant for your release at
httpservicesapcominstguides
Move Java Database
Central System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3354
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
7 We recommend that you perform regression testing
8 On the source system you run SAPinst [page 23] to remove the Java parts in the file system and in
the database
9 On the source system you call transaction RZ10 to reimport the profiles from the file system
10 In the Transport Management System (TMS) you configure the transport routes [page 38]
11 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
12 You clean up the system landscape data [page 40]
Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3454 PUBLIC 2012-04-11
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the database host of the source system you run SAPinst [page 23] to remove the Java database
schema
12 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
13 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
14 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
15 You clean up the system landscape data [page 40]
Keep Database
Central Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3554
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
12 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
13 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
14 You clean up the system landscape data [page 40]
62 Maintaining the Connection to the System Landscape Directory
After installing the Java system you need to reconfigure the connection between the System Landscape
Directory (SLD) the source system and the target system The steps required differ depending on
whether you use a local or a central SLD To maintain the connection to the SLD you can either run
the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split or perform the required steps manually as described below
NOTE
This step is only required if the connection to the SLD was established on the source system before
the split
Prerequisites
If you want to use the configuration wizard you need an SAP NetWeaver Java system 70 Support
Package 14 or higher in your landscape
SLDAPIUSER credentials are available in the ABAP system
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3654 PUBLIC 2012-04-11
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
schemes In certain situations you might create a system copy with a new ltSAPSIDgt but where
the database schema has the old ltSAPSIDgt This is not a technical problem but might be
confusing to the system administratorEnd of Oracle |
4 Only valid for MaxDB |
You plan your system configuration
For more information see System Configuration in the installation documentation of your releaseEnd of MaxDB |
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
You plan the setup of your database carefully
For more information see Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
7 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 43]
8 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
9 Only valid for IBM DB2 for zOS |
If you want to execute a Software Life-Cycle Option with SAPinst in an SAP system with thick client
connectivity see Special Considerations Regarding Connectivity for Software Life-Cycle Options in the installation
documentation of your releaseEnd of IBM DB2 for zOS |
10 Only valid for IBM DB2 for i5OS |
Optionally you decide whether you want to install multiple SAP systems on a single host
For more information see Multiple SAP Systems on a Single Host in the installation documentation of
your releaseEnd of IBM DB2 for i5OS |
11 You can continue with Preparation [page 17]
Split Option ldquoKeep Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
1 You check the hardware and software requirements for the Java installation host
For more information see Hardware and Software Requirements in the installation documentation of
your release
2 You read about user management [page 15]
3 You identify basic SAP system installation parameters
For more information see Basic SAP System Parameters in the installation documentation of your
release
3 Planning
31 Planning Checklist
1454 PUBLIC 2012-04-11
Be aware of the following dual-stack-split-specific deviation for SAP System Parameters
User management
We do not recommend that you make modifications in the user management settings For
more information see User Management [page 15]
System Landscape Directory (SLD)
You can ignore SLD parameters
4 Only valid for IBM DB2 for zOSMaxDB |
You plan your system configuration
For more information see System Configuration in the installation documentation of your releaseEnd of IBM DB2 for zOSMaxDB |
5 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
6 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 43]
7 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
8 Only valid for IBM DB2 for zOS |
If you want to execute a Software Life-Cycle Option with SAPinst in an SAP system with thick client
connectivity see Special Considerations Regarding Connectivity for Software Life-Cycle Options in the installation
documentation of your releaseEnd of IBM DB2 for zOS |
9 Only valid for IBM DB2 for i5OS |
Optionally you decide whether you want to install multiple SAP systems on a single host
For more information see Multiple SAP Systems on a Single Host in the installation documentation of
your releaseEnd of IBM DB2 for i5OS |
10 You can continue with Preparation [page 17]
32 User Management
The dual-stack split procedure does not change the user management and you cannot choose which
kind of user management you want to use for the target AS Java system That is the separated Java
system and the ABAP system both use the user management of the former dual-stack system The
following is possible
If the dual-stack system uses AS ABAP as data source for the User Management Engine (UME)
after the split the separated Java stack will also use the ABAP UME
If the dual-stack system uses an LDAP directory as source for user data this is also valid for the Java
stack
3 Planning
32 User Management
2012-04-11 PUBLIC 1554
In both cases manual configuration is not required
We do not recommend that you make modifications to the user management settings
For more information see SAP Note 718383
3 Planning
32 User Management
1654 PUBLIC 2012-04-11
4 Preparation
41 Preparation Checklist
This section includes the preparation steps that you have to perform when you want to install the new
Java system on one or more hosts
NOTE
Most of the required preparation steps listed in this section are not described in this
documentation You can find the detailed description in the SAP NetWeaver Application Server
Java installation documentation relevant for your release at httpservicesapcom
instguides
1 Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
You make sure that the required operating system users and groups are created
To create the groups and users automatically run the Dual-Stack Split Tool on the host where
the SAP Java system is to be installed and choose Dual-Stack Split Operating System Users and
Groups
For more information see Creating Operating System Users and Groups in the installation documentation
of your releaseEnd of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
2 You set up file systems and make sure that the required disk space is available for the directories
to be created during the installation
For more information see Setting Up File Systems for a High-Availability System in the installation
documentation of your release
3 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
4 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
If you want to install a high-availability system you perform switchover preparations
For more information see Performing Switchover Preparations for High-Availability in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
5 If you want to share the transport directory trans from another system you export this directory
to your installation hosts
For more information see Exporting and Mounting the Global Transport Directory in the installation
documentation of your release
4 Preparation
41 Preparation Checklist
2012-04-11 PUBLIC 1754
6 You install the Java Development Kit This step is not required if you have installed the SAP JVM
4 on your source system
For more information see Installing the Java Development Kit in the installation documentation of your
release
7 You make sure that the required installation media are available on each host
You can download the Dual-Stack Split Tool at httpservicesapcomsltoolset
Software Logistics Toolset 10 Dual-Stack Split
You can download the Java stack and database installation media from SAP Service
Marketplace as described in Preparing the Installation Media in the installation documentation of
your release
NOTE
The release level required for the installation corresponds to the release level of your dual-
stack system
The following table shows the required installation media for the dual-stack split
SAP Instance Installation Required Media
Central services instance central instance
Dual-Stack Split Tool Java DVD RDBMS Client DVD
Move Java Database only Database instance
Dual-Stack Split Tool Java DVD Only valid for MS SQL ServerOracle |
RDBMS DVDEnd of MS SQL ServerOracle |
Only valid for MS SQL ServerOracle |
RDBMS Patch DVD (if available)End of MS SQL ServerOracle |
8 Only valid for HA (MSCS) |
To install a high-availability system with Microsoft Cluster Service (MSCS) you also perform the
MSCS-specific preparation tasks as described in the installation documentation of your releaseEnd of HA (MSCS) |
9 Only valid for HA (MSCS) |
If you choose the split option ldquoKeep Databaserdquo with the scenario ldquoKeep SCS on the Source Cluster
Systemrdquo you perform the following steps
You provide additional disk storage on the target cluster system
For more information see Distribution of SAP System Components to Disks for MSCS Directories in an
MSCS Configuration and IP Addresses in an MSCS Configuration in the installation documentation of
your release
You provide an additional IP address and an additional virtual host name for the Java system
For more information see Mapping Host Names to IP Addresses for MSCS in the installation
documentation of your releaseEnd of HA (MSCS) |
4 Preparation
41 Preparation Checklist
1854 PUBLIC 2012-04-11
10 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 19] of
the dual-stack system
11 You can continue with Splitting [page 21]
42 Performing a Full System Backup
If you decided to use the split option ldquoKeep Databaserdquo you must perform a full system backup of the
dual-stack system or at least a backup of the Java database schema before you start the split procedure
If you decided to use the split option ldquoMove Java Databaserdquo you do not need to perform a backup before
you start the split procedure
For more information about backing up your database see the database-specific backup and recovery
documentation in the SAP Library [page 7] at
SAP MaxDB
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for SAP
MaxDB
Oracle
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Oracle
IBM DB2 for i5OS
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 UDB for iSeries
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for i
4 Preparation
42 Performing a Full System Backup
2012-04-11 PUBLIC 1954
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
i
IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX
and Windows
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
Linux UNIX and Windows
IBM DB2 for zOS
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 UDB for zOS
SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for DB2 for z
OS
Microsoft SQL Server
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Microsoft SQL
Server
4 Preparation
42 Performing a Full System Backup
2054 PUBLIC 2012-04-11
5 Splitting
51 Splitting Checklist
This section includes the splitting steps that you have to perform for the following split options
ldquoMove Java Databaserdquo
ldquoKeep Databaserdquo
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Only valid for Oracle |
You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 You export the Java stack using SAPinst [page 23]
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
4 You restart the source system
5 You run SAPinst [page 23] to install a Java only system using the export from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2012-04-11 PUBLIC 2154
Distributed System
1 Only valid for Oracle |
On the database instance host of the dual-stack system you install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes on the database instance host
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 On the database instance host of the dual-stack system you run SAPinst [page 23] to export the
Java database schema
4 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the Java
parts of the file system of the central instance
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
5 You restart the source system
6 You run SAPinst [page 23] to install a central services instance for the Java target system
7 You run SAPinst [page 23] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
9 You continue with Follow-Up Activities [page 33]
Keep Database
1 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the
file system of the central instance
5 Splitting
51 Splitting Checklist
2254 PUBLIC 2012-04-11
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you wont use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
2 You restart the source system
3 You run SAPinst [page 23] to install a central services instance for the Java target system
4 On the database instance host of the dual-stack system you run SAPinst [page 23] to adapt the
database for the Java target system
NOTE
Make sure that you enter the profile directory of the Java target system in the SAP System gt
General Parameters screen
5 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
52 Running SAPinst
This section describes how to run the installation tool SAPinst SAPinst includes a GUI client and a GUI
server which both use Java
The procedure describes an installation where SAPinst GUI client and GUI server are running on the
same host In the following GUI client and GUI server are addressed as ldquoSAPinst GUIrdquo
If you need to see the installation on a remote display we recommend that you perform a remote
installation with SAPinst where the SAPinst GUI is running on a separate host from SAPinst For more
information see Performing a Remote Installation with SAPinst in the installation documentation of your
release
Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote
access to SAPinst GUI on Windows workstations For more information see SAP Note 1170809
Useful Information About SAPinst
When you start SAPinst it automatically starts the SAPinst GUI
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2354
SAPinst creates the installation directory sapinst_instdir directly below the temporary directory
SAPinst 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 SAPinst
creates the installation directory sapinst_instdir directly below the tmp directory by default
If you want SAPinst to create the installation directory sapinst_instdir in another directory set
the environment variable TEMP to this directory before you start SAPinst
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
Only valid for IBM DB2 for i5OS |
NOTE
When you leave your Qp2Term session all changes of the environment variables done by the
command export are reverted
End of IBM DB2 for i5OS |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
SAPinst creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt
SAPinst extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is located
in the environment variables TEMP TMP or TMPDIR These files are deleted after SAPinst has stopped
running
The temporary directory sapinst_exexxxxxxxxxx sometimes remains undeleted You can safely
delete it
The temporary directory also contains the log file dev_selfexout from the extraction process
which might be useful if an error occurs
CAUTION
If SAPinst cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default ports 21200 21212 and 4239 are used for communication
between SAPinst GUI server GUI and HTTP server as follows
SAPinst uses port 21200 to communicate with the GUI server
The GUI server uses port 21212 to communicate with the GUI client
5 Splitting
52 Running SAPinst
2454 PUBLIC 2012-04-11
4239 is the port of the HTTP server which is part of the GUI server
If the ports for SAPinst and the GUI server are already in use SAPinst automatically searches for
free port numbers If the search fails SAPinst exits
In this case or if you want SAPinst to use specific ports you can assign them by executing the
sapinst executable with the following command line parameters
SAPINST_DIALOG_PORT=ltport_number_sapinst_to_gui_servergt
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
GUISERVER_HTTP_PORT=ltport_number_http_servergt
To see a list of all available SAPinst properties start SAPinst as described above with command line
parameter -p
sapinst -p
If you need to run SAPinst in accessibility mode proceed as described in Running SAPinst in Accessibility
Mode in the installation documentation of your release
If required you can stop SAPinst by choosing SAPinst Cancel in the SAPinst GUI menu
Prerequisites
We recommend that you use the csh shell for the installation with SAPinst If you want to use
another shell make sure that you have first read SAP Note 202227
SAPinst uses csh scripts during the installation to obtain the environment for user ltsapsidgtadm
This is also true if user ltsapsidgtadm already exists from an earlier SAP system installation and the
shell of this user is not csh Before you start SAPinst execute the following command as user
ltsapsidgtadm to make sure that the csh scripts are up-to-date
bincsh -c source lthome directory of ltsapsidgtadmgtcshrcenv
Make sure that you have specified the most important SAP system parameters as described in Basic
SAP System Installation Parameters in the installation documentation of your release before you start
SAPinst
Only valid for IBM DB2 for zOS |
Check that your installation hosts meet the requirements for the installation options that you
want to installEnd of IBM DB2 for zOS |
Only valid for Non-Standalone Engines and Clients |
If you want to perform a distributed or a high-availability installation make sure that you have
exported and mounted global directories For more information see Exporting and Mounting Global
Directories in the installation documentation of your releaseEnd of Non-Standalone Engines and Clients |
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you have carefully planned your database layout in particular the tablespace layout
as described in Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2554
Only valid for AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for Solaris |
Solaris SPARC onlyEnd of Solaris |
If you want to set up DB2s high-availability cluster solution SA MP make sure that you have read
the document IBM DB2 High Availability Solution IBM Tivoli System Automation for Multiplatforms at
httpservicesapcominstguidesnw70 Installation Installation ndash SAP NetWeaver SystemsEnd of AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for zOS |
First make sure that you have installed DB2 for zOS For information on that installation see
SAP DBA Guide DB2 for zOS DB2 Setup especially the section Stored Procedures EnablementEnd of IBM DB2 for zOS |
Check the value of the environment variable TEMP TMP or TMPDIR
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
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 ndash for example by using a crontab entry
Make sure that you have at least 60 MB of free space in the installation directory for each
installation option In addition you need 200 MB free space for the SAPinst executables If you
cannot provide 200 MB free space in the temporary directory you can set one of the
environment variables TEMP TMP or TMPDIR to another directory with 200 MB free space for
the SAPinst executables
Make sure that the temporary directory has the permissions 777
Only valid for IBM DB2 for zOS |
Make sure that your database is up and runningEnd of IBM DB2 for zOS |
Make sure that your DISPLAY environment variable is set to lthost_namegt00 where
lthost_namegt is the host on which you want to display the GUI
Shell Used Command
Bourne shell (sh) DISPLAY=lthost_namegt00
export DISPLAY
C shell (csh) setenv DISPLAY lthost_namegt00
Korn shell (ksh) export DISPLAY=lthost_namegt00
Make sure that umask is set to 022 for user root
As user root enter the following command umask 022
Check the following values for user root
5 Splitting
52 Running SAPinst
2654 PUBLIC 2012-04-11
In csh execute limit
Output Properties
cputime unlimited
filesize unlimited
datasize unlimited
stacksize 8192 KB
coredumpsize unlimited
descriptors 8192
memorysize unlimited
In sh or ksh execute ulimit -a
Output Properties
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192
coredump(blocks) unlimited
nofiles(descriptors) 8192
memory(KBytes) unlimited
If your parameter settings differ from those above change these values accordingly
EXAMPLE
If you have to change the value for descriptors to 8192 proceed as follows
In csh execute
limit descriptors 8192
In sh or ksh execute
ulimit -n 8192
Before you start SAPinst read SAP Note 1697164 for more information about which user to choose
for running the SAPinst SDT GUI server
Procedure
1 Log on to the installation host as user root
CAUTION
Do not use an existing ltsapsidgtadm user
Only valid for Non-Standalone Engines and Clients |
CAUTION
Make sure that the root user has not set any environment variables for a different SAP system
or database
End of Non-Standalone Engines and Clients |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2754
2 Make the Dual-Stack Split Tool available on the installation host Make sure that it is available
locally We do not recommend that you use Network File System (NFS) because reading from
media mounted with NFS might fail
For more information see Preparation Checklist [page 17] and Preparing the Installation Media in the
installation documentation of your release
3 Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
Only valid for Non-Standalone Engines and Clients |
Change to the directory with the sapinst executable for your operating system by entering the
following command cd ltMountpoint of Installation Master mediumgtDATA_UNITS
ltproductgt_IM_ltOSgtEnd of Non-Standalone Engines and Clients |
End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
4 Start SAPinst by executing the following command sapinst
NOTE
If you want to use a virtual host name start SAPinst with the SAPinst property
SAPINST_USE_HOSTNAME as follows
Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
sapinst SAPINST_USE_HOSTNAME=ltvirtual host namegt
End of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
5 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
In addition if you want to use the split option ldquoMove Java Databaserdquo choose ltYour System
Variantgt
Perform the export and installation steps exactly in the order in which they appear
6 Only valid for Non-Standalone Engines and Clients |
Choose NextEnd of Non-Standalone Engines and Clients |
7 Follow the instructions in the SAPinst input screens and enter the required parameters
NOTE
If SAPinst asks for the Java DVD make sure that you provide a Java DVD with the same
release level as your dual-stack system
For more information about the input parameters position the cursor on the parameter
and press F1
After you have entered all requested input parameters SAPinst displays the Parameter Summary screen
This screen shows both the parameters that you entered and those that SAPinst set by default If
required you can revise the parameters before starting the split procedure
5 Splitting
52 Running SAPinst
2854 PUBLIC 2012-04-11
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you check the following parameters depending on the installation type that you
have chosenEnd of IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for Linux and UNIX and Windows |
If you are performing a typical installation SAPinst creates four sapdata directories by
default If you require more or fewer sapdata directories depending on the storage devices
you are using you must change this parameter before you start the installation By selecting
this parameter on the Summary screen and choosing Revise SAPinst returns to the IBM DB2 for
Linux UNIX and Windows ndashgt Sapdata Directories screen
On this screen you can also decide if you want SAPinst to create the regular table and index
tablespaces with DB2s automatic storage management enabled By default the option for
automatic storage management is preselected
NOTE
As of DB2 V91 and higher the database and the SYSCATSPACE tablespace are always created
with automatic storage management enabled even if you deselect this option on the
dialog IBM DB2 for Linux UNIX and Windows gt Sapdata Directories
For more information about DB2s automatic storage management see section DB2
Tablespaces in the installation documentation of your SAP product
If you are performing a custom installation you set these parameters during the Define
Parameters phase of SAPinst
NOTE
If the tablespace layout used by SAPinst does not meet your requirements you can create
the tablespaces manually by deselecting the option Create Tablespaces with SAPinst on the
IBM DB2 for Linux and UNIX and Windows Sapdata Directories screen
During the installation phase SAPinst then displays the following message
You must create the tablespaces now To do so use the
createTablespacessql script that is located in your installation
directory
To continue the installation choose OK Alternatively you can cancel
SAPinst here and restart it again
SAPinst does not check the page size of tablespaces that have either been created manually
or that already exist If you create the tablespaces manually you must make sure that
you use a page size of 16 KBEnd of IBM DB2 for Linux and UNIX and Windows |
8 To start the dual-stack split choose Start
SAPinst starts and displays the progress of the split procedure
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2954
When the split option has finished successfully SAPinst displays the message Execution of
ltOption_Namegt has completed
Only valid for Oracle |
NOTE
When installing the Oracle database instance SAPinst stops the installation and prompts
you to install the Oracle database software For more information see Installing the Oracle
Database Software in the installation documentation of your release
After you have finished the installation of the Oracle database you continue the database
instance installation by choosing OK in the GUI of the database instance installation
Check SAP Note 1431800 for technical information about Oracle Release 112 in SAP
environments
End of Oracle |
Only valid for Enterprise Portal (EP) |
NOTE
During the final restart of Application Server Java performed by SAPinst the portal starts the
processing and uploading of the new portal archives It takes approximately 15 to 90 minutes
before the deployment is completed and the portal is launched
Do not stop SAPinst or Application Server Java during this phase
End of Enterprise Portal (EP) |
9 If required delete directories with the name sapinst_exexxxxxxxxxx after SAPinst has finished
Sometimes these remain in the temporary directory
NOTE
If there are errors with the SAPinst extraction process you can find the log file
dev_selfexout in the temporary directory
Only valid for Non-Standalone Engines and Clients |
RECOMMENDATION
Keep all installation 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 installation 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 installation directories on installation hosts but make sure
that you delete them after saving them separately
End of Non-Standalone Engines and Clients |
10 We recommend that you delete the directory ltuser_homegtsdtgui
11 Only valid for IBM DB2 for Linux and UNIX and Windows |
If not already done install the DB2 license
5 Splitting
52 Running SAPinst
3054 PUBLIC 2012-04-11
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
End of IBM DB2 for Linux and UNIX and Windows |
12 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 3154
This page is left blank for documents that are printed on both sides
6 Follow-Up Activities
61 Follow-Up Activities Checklist
This section includes the follow-up activities that you have to perform for the following split options
ldquoMove Java Databaserdquo for a central system
ldquoMove Java Databaserdquo for a distributed system or a high-availability system
ldquoKeep Databaserdquo for a central distributed or high-availability system
NOTE
Some of the follow-up activities listed in this section are not described in this documentation You
can find the detailed description in the SAP NetWeaver Application Server Java system copy
documentation relevant for your release at
httpservicesapcominstguides
Move Java Database
Central System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3354
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
7 We recommend that you perform regression testing
8 On the source system you run SAPinst [page 23] to remove the Java parts in the file system and in
the database
9 On the source system you call transaction RZ10 to reimport the profiles from the file system
10 In the Transport Management System (TMS) you configure the transport routes [page 38]
11 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
12 You clean up the system landscape data [page 40]
Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3454 PUBLIC 2012-04-11
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the database host of the source system you run SAPinst [page 23] to remove the Java database
schema
12 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
13 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
14 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
15 You clean up the system landscape data [page 40]
Keep Database
Central Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3554
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
12 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
13 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
14 You clean up the system landscape data [page 40]
62 Maintaining the Connection to the System Landscape Directory
After installing the Java system you need to reconfigure the connection between the System Landscape
Directory (SLD) the source system and the target system The steps required differ depending on
whether you use a local or a central SLD To maintain the connection to the SLD you can either run
the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split or perform the required steps manually as described below
NOTE
This step is only required if the connection to the SLD was established on the source system before
the split
Prerequisites
If you want to use the configuration wizard you need an SAP NetWeaver Java system 70 Support
Package 14 or higher in your landscape
SLDAPIUSER credentials are available in the ABAP system
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3654 PUBLIC 2012-04-11
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
Be aware of the following dual-stack-split-specific deviation for SAP System Parameters
User management
We do not recommend that you make modifications in the user management settings For
more information see User Management [page 15]
System Landscape Directory (SLD)
You can ignore SLD parameters
4 Only valid for IBM DB2 for zOSMaxDB |
You plan your system configuration
For more information see System Configuration in the installation documentation of your releaseEnd of IBM DB2 for zOSMaxDB |
5 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
6 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 43]
7 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
8 Only valid for IBM DB2 for zOS |
If you want to execute a Software Life-Cycle Option with SAPinst in an SAP system with thick client
connectivity see Special Considerations Regarding Connectivity for Software Life-Cycle Options in the installation
documentation of your releaseEnd of IBM DB2 for zOS |
9 Only valid for IBM DB2 for i5OS |
Optionally you decide whether you want to install multiple SAP systems on a single host
For more information see Multiple SAP Systems on a Single Host in the installation documentation of
your releaseEnd of IBM DB2 for i5OS |
10 You can continue with Preparation [page 17]
32 User Management
The dual-stack split procedure does not change the user management and you cannot choose which
kind of user management you want to use for the target AS Java system That is the separated Java
system and the ABAP system both use the user management of the former dual-stack system The
following is possible
If the dual-stack system uses AS ABAP as data source for the User Management Engine (UME)
after the split the separated Java stack will also use the ABAP UME
If the dual-stack system uses an LDAP directory as source for user data this is also valid for the Java
stack
3 Planning
32 User Management
2012-04-11 PUBLIC 1554
In both cases manual configuration is not required
We do not recommend that you make modifications to the user management settings
For more information see SAP Note 718383
3 Planning
32 User Management
1654 PUBLIC 2012-04-11
4 Preparation
41 Preparation Checklist
This section includes the preparation steps that you have to perform when you want to install the new
Java system on one or more hosts
NOTE
Most of the required preparation steps listed in this section are not described in this
documentation You can find the detailed description in the SAP NetWeaver Application Server
Java installation documentation relevant for your release at httpservicesapcom
instguides
1 Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
You make sure that the required operating system users and groups are created
To create the groups and users automatically run the Dual-Stack Split Tool on the host where
the SAP Java system is to be installed and choose Dual-Stack Split Operating System Users and
Groups
For more information see Creating Operating System Users and Groups in the installation documentation
of your releaseEnd of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
2 You set up file systems and make sure that the required disk space is available for the directories
to be created during the installation
For more information see Setting Up File Systems for a High-Availability System in the installation
documentation of your release
3 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
4 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
If you want to install a high-availability system you perform switchover preparations
For more information see Performing Switchover Preparations for High-Availability in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
5 If you want to share the transport directory trans from another system you export this directory
to your installation hosts
For more information see Exporting and Mounting the Global Transport Directory in the installation
documentation of your release
4 Preparation
41 Preparation Checklist
2012-04-11 PUBLIC 1754
6 You install the Java Development Kit This step is not required if you have installed the SAP JVM
4 on your source system
For more information see Installing the Java Development Kit in the installation documentation of your
release
7 You make sure that the required installation media are available on each host
You can download the Dual-Stack Split Tool at httpservicesapcomsltoolset
Software Logistics Toolset 10 Dual-Stack Split
You can download the Java stack and database installation media from SAP Service
Marketplace as described in Preparing the Installation Media in the installation documentation of
your release
NOTE
The release level required for the installation corresponds to the release level of your dual-
stack system
The following table shows the required installation media for the dual-stack split
SAP Instance Installation Required Media
Central services instance central instance
Dual-Stack Split Tool Java DVD RDBMS Client DVD
Move Java Database only Database instance
Dual-Stack Split Tool Java DVD Only valid for MS SQL ServerOracle |
RDBMS DVDEnd of MS SQL ServerOracle |
Only valid for MS SQL ServerOracle |
RDBMS Patch DVD (if available)End of MS SQL ServerOracle |
8 Only valid for HA (MSCS) |
To install a high-availability system with Microsoft Cluster Service (MSCS) you also perform the
MSCS-specific preparation tasks as described in the installation documentation of your releaseEnd of HA (MSCS) |
9 Only valid for HA (MSCS) |
If you choose the split option ldquoKeep Databaserdquo with the scenario ldquoKeep SCS on the Source Cluster
Systemrdquo you perform the following steps
You provide additional disk storage on the target cluster system
For more information see Distribution of SAP System Components to Disks for MSCS Directories in an
MSCS Configuration and IP Addresses in an MSCS Configuration in the installation documentation of
your release
You provide an additional IP address and an additional virtual host name for the Java system
For more information see Mapping Host Names to IP Addresses for MSCS in the installation
documentation of your releaseEnd of HA (MSCS) |
4 Preparation
41 Preparation Checklist
1854 PUBLIC 2012-04-11
10 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 19] of
the dual-stack system
11 You can continue with Splitting [page 21]
42 Performing a Full System Backup
If you decided to use the split option ldquoKeep Databaserdquo you must perform a full system backup of the
dual-stack system or at least a backup of the Java database schema before you start the split procedure
If you decided to use the split option ldquoMove Java Databaserdquo you do not need to perform a backup before
you start the split procedure
For more information about backing up your database see the database-specific backup and recovery
documentation in the SAP Library [page 7] at
SAP MaxDB
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for SAP
MaxDB
Oracle
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Oracle
IBM DB2 for i5OS
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 UDB for iSeries
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for i
4 Preparation
42 Performing a Full System Backup
2012-04-11 PUBLIC 1954
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
i
IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX
and Windows
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
Linux UNIX and Windows
IBM DB2 for zOS
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 UDB for zOS
SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for DB2 for z
OS
Microsoft SQL Server
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Microsoft SQL
Server
4 Preparation
42 Performing a Full System Backup
2054 PUBLIC 2012-04-11
5 Splitting
51 Splitting Checklist
This section includes the splitting steps that you have to perform for the following split options
ldquoMove Java Databaserdquo
ldquoKeep Databaserdquo
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Only valid for Oracle |
You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 You export the Java stack using SAPinst [page 23]
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
4 You restart the source system
5 You run SAPinst [page 23] to install a Java only system using the export from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2012-04-11 PUBLIC 2154
Distributed System
1 Only valid for Oracle |
On the database instance host of the dual-stack system you install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes on the database instance host
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 On the database instance host of the dual-stack system you run SAPinst [page 23] to export the
Java database schema
4 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the Java
parts of the file system of the central instance
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
5 You restart the source system
6 You run SAPinst [page 23] to install a central services instance for the Java target system
7 You run SAPinst [page 23] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
9 You continue with Follow-Up Activities [page 33]
Keep Database
1 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the
file system of the central instance
5 Splitting
51 Splitting Checklist
2254 PUBLIC 2012-04-11
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you wont use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
2 You restart the source system
3 You run SAPinst [page 23] to install a central services instance for the Java target system
4 On the database instance host of the dual-stack system you run SAPinst [page 23] to adapt the
database for the Java target system
NOTE
Make sure that you enter the profile directory of the Java target system in the SAP System gt
General Parameters screen
5 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
52 Running SAPinst
This section describes how to run the installation tool SAPinst SAPinst includes a GUI client and a GUI
server which both use Java
The procedure describes an installation where SAPinst GUI client and GUI server are running on the
same host In the following GUI client and GUI server are addressed as ldquoSAPinst GUIrdquo
If you need to see the installation on a remote display we recommend that you perform a remote
installation with SAPinst where the SAPinst GUI is running on a separate host from SAPinst For more
information see Performing a Remote Installation with SAPinst in the installation documentation of your
release
Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote
access to SAPinst GUI on Windows workstations For more information see SAP Note 1170809
Useful Information About SAPinst
When you start SAPinst it automatically starts the SAPinst GUI
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2354
SAPinst creates the installation directory sapinst_instdir directly below the temporary directory
SAPinst 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 SAPinst
creates the installation directory sapinst_instdir directly below the tmp directory by default
If you want SAPinst to create the installation directory sapinst_instdir in another directory set
the environment variable TEMP to this directory before you start SAPinst
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
Only valid for IBM DB2 for i5OS |
NOTE
When you leave your Qp2Term session all changes of the environment variables done by the
command export are reverted
End of IBM DB2 for i5OS |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
SAPinst creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt
SAPinst extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is located
in the environment variables TEMP TMP or TMPDIR These files are deleted after SAPinst has stopped
running
The temporary directory sapinst_exexxxxxxxxxx sometimes remains undeleted You can safely
delete it
The temporary directory also contains the log file dev_selfexout from the extraction process
which might be useful if an error occurs
CAUTION
If SAPinst cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default ports 21200 21212 and 4239 are used for communication
between SAPinst GUI server GUI and HTTP server as follows
SAPinst uses port 21200 to communicate with the GUI server
The GUI server uses port 21212 to communicate with the GUI client
5 Splitting
52 Running SAPinst
2454 PUBLIC 2012-04-11
4239 is the port of the HTTP server which is part of the GUI server
If the ports for SAPinst and the GUI server are already in use SAPinst automatically searches for
free port numbers If the search fails SAPinst exits
In this case or if you want SAPinst to use specific ports you can assign them by executing the
sapinst executable with the following command line parameters
SAPINST_DIALOG_PORT=ltport_number_sapinst_to_gui_servergt
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
GUISERVER_HTTP_PORT=ltport_number_http_servergt
To see a list of all available SAPinst properties start SAPinst as described above with command line
parameter -p
sapinst -p
If you need to run SAPinst in accessibility mode proceed as described in Running SAPinst in Accessibility
Mode in the installation documentation of your release
If required you can stop SAPinst by choosing SAPinst Cancel in the SAPinst GUI menu
Prerequisites
We recommend that you use the csh shell for the installation with SAPinst If you want to use
another shell make sure that you have first read SAP Note 202227
SAPinst uses csh scripts during the installation to obtain the environment for user ltsapsidgtadm
This is also true if user ltsapsidgtadm already exists from an earlier SAP system installation and the
shell of this user is not csh Before you start SAPinst execute the following command as user
ltsapsidgtadm to make sure that the csh scripts are up-to-date
bincsh -c source lthome directory of ltsapsidgtadmgtcshrcenv
Make sure that you have specified the most important SAP system parameters as described in Basic
SAP System Installation Parameters in the installation documentation of your release before you start
SAPinst
Only valid for IBM DB2 for zOS |
Check that your installation hosts meet the requirements for the installation options that you
want to installEnd of IBM DB2 for zOS |
Only valid for Non-Standalone Engines and Clients |
If you want to perform a distributed or a high-availability installation make sure that you have
exported and mounted global directories For more information see Exporting and Mounting Global
Directories in the installation documentation of your releaseEnd of Non-Standalone Engines and Clients |
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you have carefully planned your database layout in particular the tablespace layout
as described in Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2554
Only valid for AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for Solaris |
Solaris SPARC onlyEnd of Solaris |
If you want to set up DB2s high-availability cluster solution SA MP make sure that you have read
the document IBM DB2 High Availability Solution IBM Tivoli System Automation for Multiplatforms at
httpservicesapcominstguidesnw70 Installation Installation ndash SAP NetWeaver SystemsEnd of AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for zOS |
First make sure that you have installed DB2 for zOS For information on that installation see
SAP DBA Guide DB2 for zOS DB2 Setup especially the section Stored Procedures EnablementEnd of IBM DB2 for zOS |
Check the value of the environment variable TEMP TMP or TMPDIR
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
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 ndash for example by using a crontab entry
Make sure that you have at least 60 MB of free space in the installation directory for each
installation option In addition you need 200 MB free space for the SAPinst executables If you
cannot provide 200 MB free space in the temporary directory you can set one of the
environment variables TEMP TMP or TMPDIR to another directory with 200 MB free space for
the SAPinst executables
Make sure that the temporary directory has the permissions 777
Only valid for IBM DB2 for zOS |
Make sure that your database is up and runningEnd of IBM DB2 for zOS |
Make sure that your DISPLAY environment variable is set to lthost_namegt00 where
lthost_namegt is the host on which you want to display the GUI
Shell Used Command
Bourne shell (sh) DISPLAY=lthost_namegt00
export DISPLAY
C shell (csh) setenv DISPLAY lthost_namegt00
Korn shell (ksh) export DISPLAY=lthost_namegt00
Make sure that umask is set to 022 for user root
As user root enter the following command umask 022
Check the following values for user root
5 Splitting
52 Running SAPinst
2654 PUBLIC 2012-04-11
In csh execute limit
Output Properties
cputime unlimited
filesize unlimited
datasize unlimited
stacksize 8192 KB
coredumpsize unlimited
descriptors 8192
memorysize unlimited
In sh or ksh execute ulimit -a
Output Properties
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192
coredump(blocks) unlimited
nofiles(descriptors) 8192
memory(KBytes) unlimited
If your parameter settings differ from those above change these values accordingly
EXAMPLE
If you have to change the value for descriptors to 8192 proceed as follows
In csh execute
limit descriptors 8192
In sh or ksh execute
ulimit -n 8192
Before you start SAPinst read SAP Note 1697164 for more information about which user to choose
for running the SAPinst SDT GUI server
Procedure
1 Log on to the installation host as user root
CAUTION
Do not use an existing ltsapsidgtadm user
Only valid for Non-Standalone Engines and Clients |
CAUTION
Make sure that the root user has not set any environment variables for a different SAP system
or database
End of Non-Standalone Engines and Clients |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2754
2 Make the Dual-Stack Split Tool available on the installation host Make sure that it is available
locally We do not recommend that you use Network File System (NFS) because reading from
media mounted with NFS might fail
For more information see Preparation Checklist [page 17] and Preparing the Installation Media in the
installation documentation of your release
3 Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
Only valid for Non-Standalone Engines and Clients |
Change to the directory with the sapinst executable for your operating system by entering the
following command cd ltMountpoint of Installation Master mediumgtDATA_UNITS
ltproductgt_IM_ltOSgtEnd of Non-Standalone Engines and Clients |
End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
4 Start SAPinst by executing the following command sapinst
NOTE
If you want to use a virtual host name start SAPinst with the SAPinst property
SAPINST_USE_HOSTNAME as follows
Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
sapinst SAPINST_USE_HOSTNAME=ltvirtual host namegt
End of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
5 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
In addition if you want to use the split option ldquoMove Java Databaserdquo choose ltYour System
Variantgt
Perform the export and installation steps exactly in the order in which they appear
6 Only valid for Non-Standalone Engines and Clients |
Choose NextEnd of Non-Standalone Engines and Clients |
7 Follow the instructions in the SAPinst input screens and enter the required parameters
NOTE
If SAPinst asks for the Java DVD make sure that you provide a Java DVD with the same
release level as your dual-stack system
For more information about the input parameters position the cursor on the parameter
and press F1
After you have entered all requested input parameters SAPinst displays the Parameter Summary screen
This screen shows both the parameters that you entered and those that SAPinst set by default If
required you can revise the parameters before starting the split procedure
5 Splitting
52 Running SAPinst
2854 PUBLIC 2012-04-11
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you check the following parameters depending on the installation type that you
have chosenEnd of IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for Linux and UNIX and Windows |
If you are performing a typical installation SAPinst creates four sapdata directories by
default If you require more or fewer sapdata directories depending on the storage devices
you are using you must change this parameter before you start the installation By selecting
this parameter on the Summary screen and choosing Revise SAPinst returns to the IBM DB2 for
Linux UNIX and Windows ndashgt Sapdata Directories screen
On this screen you can also decide if you want SAPinst to create the regular table and index
tablespaces with DB2s automatic storage management enabled By default the option for
automatic storage management is preselected
NOTE
As of DB2 V91 and higher the database and the SYSCATSPACE tablespace are always created
with automatic storage management enabled even if you deselect this option on the
dialog IBM DB2 for Linux UNIX and Windows gt Sapdata Directories
For more information about DB2s automatic storage management see section DB2
Tablespaces in the installation documentation of your SAP product
If you are performing a custom installation you set these parameters during the Define
Parameters phase of SAPinst
NOTE
If the tablespace layout used by SAPinst does not meet your requirements you can create
the tablespaces manually by deselecting the option Create Tablespaces with SAPinst on the
IBM DB2 for Linux and UNIX and Windows Sapdata Directories screen
During the installation phase SAPinst then displays the following message
You must create the tablespaces now To do so use the
createTablespacessql script that is located in your installation
directory
To continue the installation choose OK Alternatively you can cancel
SAPinst here and restart it again
SAPinst does not check the page size of tablespaces that have either been created manually
or that already exist If you create the tablespaces manually you must make sure that
you use a page size of 16 KBEnd of IBM DB2 for Linux and UNIX and Windows |
8 To start the dual-stack split choose Start
SAPinst starts and displays the progress of the split procedure
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2954
When the split option has finished successfully SAPinst displays the message Execution of
ltOption_Namegt has completed
Only valid for Oracle |
NOTE
When installing the Oracle database instance SAPinst stops the installation and prompts
you to install the Oracle database software For more information see Installing the Oracle
Database Software in the installation documentation of your release
After you have finished the installation of the Oracle database you continue the database
instance installation by choosing OK in the GUI of the database instance installation
Check SAP Note 1431800 for technical information about Oracle Release 112 in SAP
environments
End of Oracle |
Only valid for Enterprise Portal (EP) |
NOTE
During the final restart of Application Server Java performed by SAPinst the portal starts the
processing and uploading of the new portal archives It takes approximately 15 to 90 minutes
before the deployment is completed and the portal is launched
Do not stop SAPinst or Application Server Java during this phase
End of Enterprise Portal (EP) |
9 If required delete directories with the name sapinst_exexxxxxxxxxx after SAPinst has finished
Sometimes these remain in the temporary directory
NOTE
If there are errors with the SAPinst extraction process you can find the log file
dev_selfexout in the temporary directory
Only valid for Non-Standalone Engines and Clients |
RECOMMENDATION
Keep all installation 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 installation 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 installation directories on installation hosts but make sure
that you delete them after saving them separately
End of Non-Standalone Engines and Clients |
10 We recommend that you delete the directory ltuser_homegtsdtgui
11 Only valid for IBM DB2 for Linux and UNIX and Windows |
If not already done install the DB2 license
5 Splitting
52 Running SAPinst
3054 PUBLIC 2012-04-11
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
End of IBM DB2 for Linux and UNIX and Windows |
12 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 3154
This page is left blank for documents that are printed on both sides
6 Follow-Up Activities
61 Follow-Up Activities Checklist
This section includes the follow-up activities that you have to perform for the following split options
ldquoMove Java Databaserdquo for a central system
ldquoMove Java Databaserdquo for a distributed system or a high-availability system
ldquoKeep Databaserdquo for a central distributed or high-availability system
NOTE
Some of the follow-up activities listed in this section are not described in this documentation You
can find the detailed description in the SAP NetWeaver Application Server Java system copy
documentation relevant for your release at
httpservicesapcominstguides
Move Java Database
Central System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3354
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
7 We recommend that you perform regression testing
8 On the source system you run SAPinst [page 23] to remove the Java parts in the file system and in
the database
9 On the source system you call transaction RZ10 to reimport the profiles from the file system
10 In the Transport Management System (TMS) you configure the transport routes [page 38]
11 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
12 You clean up the system landscape data [page 40]
Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3454 PUBLIC 2012-04-11
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the database host of the source system you run SAPinst [page 23] to remove the Java database
schema
12 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
13 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
14 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
15 You clean up the system landscape data [page 40]
Keep Database
Central Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3554
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
12 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
13 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
14 You clean up the system landscape data [page 40]
62 Maintaining the Connection to the System Landscape Directory
After installing the Java system you need to reconfigure the connection between the System Landscape
Directory (SLD) the source system and the target system The steps required differ depending on
whether you use a local or a central SLD To maintain the connection to the SLD you can either run
the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split or perform the required steps manually as described below
NOTE
This step is only required if the connection to the SLD was established on the source system before
the split
Prerequisites
If you want to use the configuration wizard you need an SAP NetWeaver Java system 70 Support
Package 14 or higher in your landscape
SLDAPIUSER credentials are available in the ABAP system
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3654 PUBLIC 2012-04-11
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
In both cases manual configuration is not required
We do not recommend that you make modifications to the user management settings
For more information see SAP Note 718383
3 Planning
32 User Management
1654 PUBLIC 2012-04-11
4 Preparation
41 Preparation Checklist
This section includes the preparation steps that you have to perform when you want to install the new
Java system on one or more hosts
NOTE
Most of the required preparation steps listed in this section are not described in this
documentation You can find the detailed description in the SAP NetWeaver Application Server
Java installation documentation relevant for your release at httpservicesapcom
instguides
1 Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
You make sure that the required operating system users and groups are created
To create the groups and users automatically run the Dual-Stack Split Tool on the host where
the SAP Java system is to be installed and choose Dual-Stack Split Operating System Users and
Groups
For more information see Creating Operating System Users and Groups in the installation documentation
of your releaseEnd of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
2 You set up file systems and make sure that the required disk space is available for the directories
to be created during the installation
For more information see Setting Up File Systems for a High-Availability System in the installation
documentation of your release
3 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
4 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
If you want to install a high-availability system you perform switchover preparations
For more information see Performing Switchover Preparations for High-Availability in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
5 If you want to share the transport directory trans from another system you export this directory
to your installation hosts
For more information see Exporting and Mounting the Global Transport Directory in the installation
documentation of your release
4 Preparation
41 Preparation Checklist
2012-04-11 PUBLIC 1754
6 You install the Java Development Kit This step is not required if you have installed the SAP JVM
4 on your source system
For more information see Installing the Java Development Kit in the installation documentation of your
release
7 You make sure that the required installation media are available on each host
You can download the Dual-Stack Split Tool at httpservicesapcomsltoolset
Software Logistics Toolset 10 Dual-Stack Split
You can download the Java stack and database installation media from SAP Service
Marketplace as described in Preparing the Installation Media in the installation documentation of
your release
NOTE
The release level required for the installation corresponds to the release level of your dual-
stack system
The following table shows the required installation media for the dual-stack split
SAP Instance Installation Required Media
Central services instance central instance
Dual-Stack Split Tool Java DVD RDBMS Client DVD
Move Java Database only Database instance
Dual-Stack Split Tool Java DVD Only valid for MS SQL ServerOracle |
RDBMS DVDEnd of MS SQL ServerOracle |
Only valid for MS SQL ServerOracle |
RDBMS Patch DVD (if available)End of MS SQL ServerOracle |
8 Only valid for HA (MSCS) |
To install a high-availability system with Microsoft Cluster Service (MSCS) you also perform the
MSCS-specific preparation tasks as described in the installation documentation of your releaseEnd of HA (MSCS) |
9 Only valid for HA (MSCS) |
If you choose the split option ldquoKeep Databaserdquo with the scenario ldquoKeep SCS on the Source Cluster
Systemrdquo you perform the following steps
You provide additional disk storage on the target cluster system
For more information see Distribution of SAP System Components to Disks for MSCS Directories in an
MSCS Configuration and IP Addresses in an MSCS Configuration in the installation documentation of
your release
You provide an additional IP address and an additional virtual host name for the Java system
For more information see Mapping Host Names to IP Addresses for MSCS in the installation
documentation of your releaseEnd of HA (MSCS) |
4 Preparation
41 Preparation Checklist
1854 PUBLIC 2012-04-11
10 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 19] of
the dual-stack system
11 You can continue with Splitting [page 21]
42 Performing a Full System Backup
If you decided to use the split option ldquoKeep Databaserdquo you must perform a full system backup of the
dual-stack system or at least a backup of the Java database schema before you start the split procedure
If you decided to use the split option ldquoMove Java Databaserdquo you do not need to perform a backup before
you start the split procedure
For more information about backing up your database see the database-specific backup and recovery
documentation in the SAP Library [page 7] at
SAP MaxDB
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for SAP
MaxDB
Oracle
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Oracle
IBM DB2 for i5OS
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 UDB for iSeries
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for i
4 Preparation
42 Performing a Full System Backup
2012-04-11 PUBLIC 1954
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
i
IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX
and Windows
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
Linux UNIX and Windows
IBM DB2 for zOS
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 UDB for zOS
SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for DB2 for z
OS
Microsoft SQL Server
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Microsoft SQL
Server
4 Preparation
42 Performing a Full System Backup
2054 PUBLIC 2012-04-11
5 Splitting
51 Splitting Checklist
This section includes the splitting steps that you have to perform for the following split options
ldquoMove Java Databaserdquo
ldquoKeep Databaserdquo
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Only valid for Oracle |
You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 You export the Java stack using SAPinst [page 23]
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
4 You restart the source system
5 You run SAPinst [page 23] to install a Java only system using the export from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2012-04-11 PUBLIC 2154
Distributed System
1 Only valid for Oracle |
On the database instance host of the dual-stack system you install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes on the database instance host
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 On the database instance host of the dual-stack system you run SAPinst [page 23] to export the
Java database schema
4 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the Java
parts of the file system of the central instance
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
5 You restart the source system
6 You run SAPinst [page 23] to install a central services instance for the Java target system
7 You run SAPinst [page 23] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
9 You continue with Follow-Up Activities [page 33]
Keep Database
1 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the
file system of the central instance
5 Splitting
51 Splitting Checklist
2254 PUBLIC 2012-04-11
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you wont use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
2 You restart the source system
3 You run SAPinst [page 23] to install a central services instance for the Java target system
4 On the database instance host of the dual-stack system you run SAPinst [page 23] to adapt the
database for the Java target system
NOTE
Make sure that you enter the profile directory of the Java target system in the SAP System gt
General Parameters screen
5 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
52 Running SAPinst
This section describes how to run the installation tool SAPinst SAPinst includes a GUI client and a GUI
server which both use Java
The procedure describes an installation where SAPinst GUI client and GUI server are running on the
same host In the following GUI client and GUI server are addressed as ldquoSAPinst GUIrdquo
If you need to see the installation on a remote display we recommend that you perform a remote
installation with SAPinst where the SAPinst GUI is running on a separate host from SAPinst For more
information see Performing a Remote Installation with SAPinst in the installation documentation of your
release
Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote
access to SAPinst GUI on Windows workstations For more information see SAP Note 1170809
Useful Information About SAPinst
When you start SAPinst it automatically starts the SAPinst GUI
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2354
SAPinst creates the installation directory sapinst_instdir directly below the temporary directory
SAPinst 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 SAPinst
creates the installation directory sapinst_instdir directly below the tmp directory by default
If you want SAPinst to create the installation directory sapinst_instdir in another directory set
the environment variable TEMP to this directory before you start SAPinst
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
Only valid for IBM DB2 for i5OS |
NOTE
When you leave your Qp2Term session all changes of the environment variables done by the
command export are reverted
End of IBM DB2 for i5OS |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
SAPinst creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt
SAPinst extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is located
in the environment variables TEMP TMP or TMPDIR These files are deleted after SAPinst has stopped
running
The temporary directory sapinst_exexxxxxxxxxx sometimes remains undeleted You can safely
delete it
The temporary directory also contains the log file dev_selfexout from the extraction process
which might be useful if an error occurs
CAUTION
If SAPinst cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default ports 21200 21212 and 4239 are used for communication
between SAPinst GUI server GUI and HTTP server as follows
SAPinst uses port 21200 to communicate with the GUI server
The GUI server uses port 21212 to communicate with the GUI client
5 Splitting
52 Running SAPinst
2454 PUBLIC 2012-04-11
4239 is the port of the HTTP server which is part of the GUI server
If the ports for SAPinst and the GUI server are already in use SAPinst automatically searches for
free port numbers If the search fails SAPinst exits
In this case or if you want SAPinst to use specific ports you can assign them by executing the
sapinst executable with the following command line parameters
SAPINST_DIALOG_PORT=ltport_number_sapinst_to_gui_servergt
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
GUISERVER_HTTP_PORT=ltport_number_http_servergt
To see a list of all available SAPinst properties start SAPinst as described above with command line
parameter -p
sapinst -p
If you need to run SAPinst in accessibility mode proceed as described in Running SAPinst in Accessibility
Mode in the installation documentation of your release
If required you can stop SAPinst by choosing SAPinst Cancel in the SAPinst GUI menu
Prerequisites
We recommend that you use the csh shell for the installation with SAPinst If you want to use
another shell make sure that you have first read SAP Note 202227
SAPinst uses csh scripts during the installation to obtain the environment for user ltsapsidgtadm
This is also true if user ltsapsidgtadm already exists from an earlier SAP system installation and the
shell of this user is not csh Before you start SAPinst execute the following command as user
ltsapsidgtadm to make sure that the csh scripts are up-to-date
bincsh -c source lthome directory of ltsapsidgtadmgtcshrcenv
Make sure that you have specified the most important SAP system parameters as described in Basic
SAP System Installation Parameters in the installation documentation of your release before you start
SAPinst
Only valid for IBM DB2 for zOS |
Check that your installation hosts meet the requirements for the installation options that you
want to installEnd of IBM DB2 for zOS |
Only valid for Non-Standalone Engines and Clients |
If you want to perform a distributed or a high-availability installation make sure that you have
exported and mounted global directories For more information see Exporting and Mounting Global
Directories in the installation documentation of your releaseEnd of Non-Standalone Engines and Clients |
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you have carefully planned your database layout in particular the tablespace layout
as described in Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2554
Only valid for AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for Solaris |
Solaris SPARC onlyEnd of Solaris |
If you want to set up DB2s high-availability cluster solution SA MP make sure that you have read
the document IBM DB2 High Availability Solution IBM Tivoli System Automation for Multiplatforms at
httpservicesapcominstguidesnw70 Installation Installation ndash SAP NetWeaver SystemsEnd of AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for zOS |
First make sure that you have installed DB2 for zOS For information on that installation see
SAP DBA Guide DB2 for zOS DB2 Setup especially the section Stored Procedures EnablementEnd of IBM DB2 for zOS |
Check the value of the environment variable TEMP TMP or TMPDIR
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
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 ndash for example by using a crontab entry
Make sure that you have at least 60 MB of free space in the installation directory for each
installation option In addition you need 200 MB free space for the SAPinst executables If you
cannot provide 200 MB free space in the temporary directory you can set one of the
environment variables TEMP TMP or TMPDIR to another directory with 200 MB free space for
the SAPinst executables
Make sure that the temporary directory has the permissions 777
Only valid for IBM DB2 for zOS |
Make sure that your database is up and runningEnd of IBM DB2 for zOS |
Make sure that your DISPLAY environment variable is set to lthost_namegt00 where
lthost_namegt is the host on which you want to display the GUI
Shell Used Command
Bourne shell (sh) DISPLAY=lthost_namegt00
export DISPLAY
C shell (csh) setenv DISPLAY lthost_namegt00
Korn shell (ksh) export DISPLAY=lthost_namegt00
Make sure that umask is set to 022 for user root
As user root enter the following command umask 022
Check the following values for user root
5 Splitting
52 Running SAPinst
2654 PUBLIC 2012-04-11
In csh execute limit
Output Properties
cputime unlimited
filesize unlimited
datasize unlimited
stacksize 8192 KB
coredumpsize unlimited
descriptors 8192
memorysize unlimited
In sh or ksh execute ulimit -a
Output Properties
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192
coredump(blocks) unlimited
nofiles(descriptors) 8192
memory(KBytes) unlimited
If your parameter settings differ from those above change these values accordingly
EXAMPLE
If you have to change the value for descriptors to 8192 proceed as follows
In csh execute
limit descriptors 8192
In sh or ksh execute
ulimit -n 8192
Before you start SAPinst read SAP Note 1697164 for more information about which user to choose
for running the SAPinst SDT GUI server
Procedure
1 Log on to the installation host as user root
CAUTION
Do not use an existing ltsapsidgtadm user
Only valid for Non-Standalone Engines and Clients |
CAUTION
Make sure that the root user has not set any environment variables for a different SAP system
or database
End of Non-Standalone Engines and Clients |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2754
2 Make the Dual-Stack Split Tool available on the installation host Make sure that it is available
locally We do not recommend that you use Network File System (NFS) because reading from
media mounted with NFS might fail
For more information see Preparation Checklist [page 17] and Preparing the Installation Media in the
installation documentation of your release
3 Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
Only valid for Non-Standalone Engines and Clients |
Change to the directory with the sapinst executable for your operating system by entering the
following command cd ltMountpoint of Installation Master mediumgtDATA_UNITS
ltproductgt_IM_ltOSgtEnd of Non-Standalone Engines and Clients |
End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
4 Start SAPinst by executing the following command sapinst
NOTE
If you want to use a virtual host name start SAPinst with the SAPinst property
SAPINST_USE_HOSTNAME as follows
Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
sapinst SAPINST_USE_HOSTNAME=ltvirtual host namegt
End of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
5 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
In addition if you want to use the split option ldquoMove Java Databaserdquo choose ltYour System
Variantgt
Perform the export and installation steps exactly in the order in which they appear
6 Only valid for Non-Standalone Engines and Clients |
Choose NextEnd of Non-Standalone Engines and Clients |
7 Follow the instructions in the SAPinst input screens and enter the required parameters
NOTE
If SAPinst asks for the Java DVD make sure that you provide a Java DVD with the same
release level as your dual-stack system
For more information about the input parameters position the cursor on the parameter
and press F1
After you have entered all requested input parameters SAPinst displays the Parameter Summary screen
This screen shows both the parameters that you entered and those that SAPinst set by default If
required you can revise the parameters before starting the split procedure
5 Splitting
52 Running SAPinst
2854 PUBLIC 2012-04-11
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you check the following parameters depending on the installation type that you
have chosenEnd of IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for Linux and UNIX and Windows |
If you are performing a typical installation SAPinst creates four sapdata directories by
default If you require more or fewer sapdata directories depending on the storage devices
you are using you must change this parameter before you start the installation By selecting
this parameter on the Summary screen and choosing Revise SAPinst returns to the IBM DB2 for
Linux UNIX and Windows ndashgt Sapdata Directories screen
On this screen you can also decide if you want SAPinst to create the regular table and index
tablespaces with DB2s automatic storage management enabled By default the option for
automatic storage management is preselected
NOTE
As of DB2 V91 and higher the database and the SYSCATSPACE tablespace are always created
with automatic storage management enabled even if you deselect this option on the
dialog IBM DB2 for Linux UNIX and Windows gt Sapdata Directories
For more information about DB2s automatic storage management see section DB2
Tablespaces in the installation documentation of your SAP product
If you are performing a custom installation you set these parameters during the Define
Parameters phase of SAPinst
NOTE
If the tablespace layout used by SAPinst does not meet your requirements you can create
the tablespaces manually by deselecting the option Create Tablespaces with SAPinst on the
IBM DB2 for Linux and UNIX and Windows Sapdata Directories screen
During the installation phase SAPinst then displays the following message
You must create the tablespaces now To do so use the
createTablespacessql script that is located in your installation
directory
To continue the installation choose OK Alternatively you can cancel
SAPinst here and restart it again
SAPinst does not check the page size of tablespaces that have either been created manually
or that already exist If you create the tablespaces manually you must make sure that
you use a page size of 16 KBEnd of IBM DB2 for Linux and UNIX and Windows |
8 To start the dual-stack split choose Start
SAPinst starts and displays the progress of the split procedure
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2954
When the split option has finished successfully SAPinst displays the message Execution of
ltOption_Namegt has completed
Only valid for Oracle |
NOTE
When installing the Oracle database instance SAPinst stops the installation and prompts
you to install the Oracle database software For more information see Installing the Oracle
Database Software in the installation documentation of your release
After you have finished the installation of the Oracle database you continue the database
instance installation by choosing OK in the GUI of the database instance installation
Check SAP Note 1431800 for technical information about Oracle Release 112 in SAP
environments
End of Oracle |
Only valid for Enterprise Portal (EP) |
NOTE
During the final restart of Application Server Java performed by SAPinst the portal starts the
processing and uploading of the new portal archives It takes approximately 15 to 90 minutes
before the deployment is completed and the portal is launched
Do not stop SAPinst or Application Server Java during this phase
End of Enterprise Portal (EP) |
9 If required delete directories with the name sapinst_exexxxxxxxxxx after SAPinst has finished
Sometimes these remain in the temporary directory
NOTE
If there are errors with the SAPinst extraction process you can find the log file
dev_selfexout in the temporary directory
Only valid for Non-Standalone Engines and Clients |
RECOMMENDATION
Keep all installation 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 installation 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 installation directories on installation hosts but make sure
that you delete them after saving them separately
End of Non-Standalone Engines and Clients |
10 We recommend that you delete the directory ltuser_homegtsdtgui
11 Only valid for IBM DB2 for Linux and UNIX and Windows |
If not already done install the DB2 license
5 Splitting
52 Running SAPinst
3054 PUBLIC 2012-04-11
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
End of IBM DB2 for Linux and UNIX and Windows |
12 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 3154
This page is left blank for documents that are printed on both sides
6 Follow-Up Activities
61 Follow-Up Activities Checklist
This section includes the follow-up activities that you have to perform for the following split options
ldquoMove Java Databaserdquo for a central system
ldquoMove Java Databaserdquo for a distributed system or a high-availability system
ldquoKeep Databaserdquo for a central distributed or high-availability system
NOTE
Some of the follow-up activities listed in this section are not described in this documentation You
can find the detailed description in the SAP NetWeaver Application Server Java system copy
documentation relevant for your release at
httpservicesapcominstguides
Move Java Database
Central System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3354
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
7 We recommend that you perform regression testing
8 On the source system you run SAPinst [page 23] to remove the Java parts in the file system and in
the database
9 On the source system you call transaction RZ10 to reimport the profiles from the file system
10 In the Transport Management System (TMS) you configure the transport routes [page 38]
11 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
12 You clean up the system landscape data [page 40]
Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3454 PUBLIC 2012-04-11
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the database host of the source system you run SAPinst [page 23] to remove the Java database
schema
12 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
13 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
14 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
15 You clean up the system landscape data [page 40]
Keep Database
Central Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3554
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
12 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
13 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
14 You clean up the system landscape data [page 40]
62 Maintaining the Connection to the System Landscape Directory
After installing the Java system you need to reconfigure the connection between the System Landscape
Directory (SLD) the source system and the target system The steps required differ depending on
whether you use a local or a central SLD To maintain the connection to the SLD you can either run
the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split or perform the required steps manually as described below
NOTE
This step is only required if the connection to the SLD was established on the source system before
the split
Prerequisites
If you want to use the configuration wizard you need an SAP NetWeaver Java system 70 Support
Package 14 or higher in your landscape
SLDAPIUSER credentials are available in the ABAP system
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3654 PUBLIC 2012-04-11
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
4 Preparation
41 Preparation Checklist
This section includes the preparation steps that you have to perform when you want to install the new
Java system on one or more hosts
NOTE
Most of the required preparation steps listed in this section are not described in this
documentation You can find the detailed description in the SAP NetWeaver Application Server
Java installation documentation relevant for your release at httpservicesapcom
instguides
1 Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
You make sure that the required operating system users and groups are created
To create the groups and users automatically run the Dual-Stack Split Tool on the host where
the SAP Java system is to be installed and choose Dual-Stack Split Operating System Users and
Groups
For more information see Creating Operating System Users and Groups in the installation documentation
of your releaseEnd of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
2 You set up file systems and make sure that the required disk space is available for the directories
to be created during the installation
For more information see Setting Up File Systems for a High-Availability System in the installation
documentation of your release
3 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
4 Only valid for HA (UNIX) | Non-Standalone Engines and Clients |
If you want to install a high-availability system you perform switchover preparations
For more information see Performing Switchover Preparations for High-Availability in the installation
documentation of your releaseEnd of HA (UNIX) | Non-Standalone Engines and Clients |
5 If you want to share the transport directory trans from another system you export this directory
to your installation hosts
For more information see Exporting and Mounting the Global Transport Directory in the installation
documentation of your release
4 Preparation
41 Preparation Checklist
2012-04-11 PUBLIC 1754
6 You install the Java Development Kit This step is not required if you have installed the SAP JVM
4 on your source system
For more information see Installing the Java Development Kit in the installation documentation of your
release
7 You make sure that the required installation media are available on each host
You can download the Dual-Stack Split Tool at httpservicesapcomsltoolset
Software Logistics Toolset 10 Dual-Stack Split
You can download the Java stack and database installation media from SAP Service
Marketplace as described in Preparing the Installation Media in the installation documentation of
your release
NOTE
The release level required for the installation corresponds to the release level of your dual-
stack system
The following table shows the required installation media for the dual-stack split
SAP Instance Installation Required Media
Central services instance central instance
Dual-Stack Split Tool Java DVD RDBMS Client DVD
Move Java Database only Database instance
Dual-Stack Split Tool Java DVD Only valid for MS SQL ServerOracle |
RDBMS DVDEnd of MS SQL ServerOracle |
Only valid for MS SQL ServerOracle |
RDBMS Patch DVD (if available)End of MS SQL ServerOracle |
8 Only valid for HA (MSCS) |
To install a high-availability system with Microsoft Cluster Service (MSCS) you also perform the
MSCS-specific preparation tasks as described in the installation documentation of your releaseEnd of HA (MSCS) |
9 Only valid for HA (MSCS) |
If you choose the split option ldquoKeep Databaserdquo with the scenario ldquoKeep SCS on the Source Cluster
Systemrdquo you perform the following steps
You provide additional disk storage on the target cluster system
For more information see Distribution of SAP System Components to Disks for MSCS Directories in an
MSCS Configuration and IP Addresses in an MSCS Configuration in the installation documentation of
your release
You provide an additional IP address and an additional virtual host name for the Java system
For more information see Mapping Host Names to IP Addresses for MSCS in the installation
documentation of your releaseEnd of HA (MSCS) |
4 Preparation
41 Preparation Checklist
1854 PUBLIC 2012-04-11
10 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 19] of
the dual-stack system
11 You can continue with Splitting [page 21]
42 Performing a Full System Backup
If you decided to use the split option ldquoKeep Databaserdquo you must perform a full system backup of the
dual-stack system or at least a backup of the Java database schema before you start the split procedure
If you decided to use the split option ldquoMove Java Databaserdquo you do not need to perform a backup before
you start the split procedure
For more information about backing up your database see the database-specific backup and recovery
documentation in the SAP Library [page 7] at
SAP MaxDB
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for SAP
MaxDB
Oracle
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Oracle
IBM DB2 for i5OS
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 UDB for iSeries
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for i
4 Preparation
42 Performing a Full System Backup
2012-04-11 PUBLIC 1954
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
i
IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX
and Windows
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
Linux UNIX and Windows
IBM DB2 for zOS
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 UDB for zOS
SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for DB2 for z
OS
Microsoft SQL Server
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Microsoft SQL
Server
4 Preparation
42 Performing a Full System Backup
2054 PUBLIC 2012-04-11
5 Splitting
51 Splitting Checklist
This section includes the splitting steps that you have to perform for the following split options
ldquoMove Java Databaserdquo
ldquoKeep Databaserdquo
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Only valid for Oracle |
You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 You export the Java stack using SAPinst [page 23]
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
4 You restart the source system
5 You run SAPinst [page 23] to install a Java only system using the export from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2012-04-11 PUBLIC 2154
Distributed System
1 Only valid for Oracle |
On the database instance host of the dual-stack system you install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes on the database instance host
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 On the database instance host of the dual-stack system you run SAPinst [page 23] to export the
Java database schema
4 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the Java
parts of the file system of the central instance
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
5 You restart the source system
6 You run SAPinst [page 23] to install a central services instance for the Java target system
7 You run SAPinst [page 23] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
9 You continue with Follow-Up Activities [page 33]
Keep Database
1 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the
file system of the central instance
5 Splitting
51 Splitting Checklist
2254 PUBLIC 2012-04-11
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you wont use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
2 You restart the source system
3 You run SAPinst [page 23] to install a central services instance for the Java target system
4 On the database instance host of the dual-stack system you run SAPinst [page 23] to adapt the
database for the Java target system
NOTE
Make sure that you enter the profile directory of the Java target system in the SAP System gt
General Parameters screen
5 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
52 Running SAPinst
This section describes how to run the installation tool SAPinst SAPinst includes a GUI client and a GUI
server which both use Java
The procedure describes an installation where SAPinst GUI client and GUI server are running on the
same host In the following GUI client and GUI server are addressed as ldquoSAPinst GUIrdquo
If you need to see the installation on a remote display we recommend that you perform a remote
installation with SAPinst where the SAPinst GUI is running on a separate host from SAPinst For more
information see Performing a Remote Installation with SAPinst in the installation documentation of your
release
Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote
access to SAPinst GUI on Windows workstations For more information see SAP Note 1170809
Useful Information About SAPinst
When you start SAPinst it automatically starts the SAPinst GUI
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2354
SAPinst creates the installation directory sapinst_instdir directly below the temporary directory
SAPinst 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 SAPinst
creates the installation directory sapinst_instdir directly below the tmp directory by default
If you want SAPinst to create the installation directory sapinst_instdir in another directory set
the environment variable TEMP to this directory before you start SAPinst
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
Only valid for IBM DB2 for i5OS |
NOTE
When you leave your Qp2Term session all changes of the environment variables done by the
command export are reverted
End of IBM DB2 for i5OS |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
SAPinst creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt
SAPinst extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is located
in the environment variables TEMP TMP or TMPDIR These files are deleted after SAPinst has stopped
running
The temporary directory sapinst_exexxxxxxxxxx sometimes remains undeleted You can safely
delete it
The temporary directory also contains the log file dev_selfexout from the extraction process
which might be useful if an error occurs
CAUTION
If SAPinst cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default ports 21200 21212 and 4239 are used for communication
between SAPinst GUI server GUI and HTTP server as follows
SAPinst uses port 21200 to communicate with the GUI server
The GUI server uses port 21212 to communicate with the GUI client
5 Splitting
52 Running SAPinst
2454 PUBLIC 2012-04-11
4239 is the port of the HTTP server which is part of the GUI server
If the ports for SAPinst and the GUI server are already in use SAPinst automatically searches for
free port numbers If the search fails SAPinst exits
In this case or if you want SAPinst to use specific ports you can assign them by executing the
sapinst executable with the following command line parameters
SAPINST_DIALOG_PORT=ltport_number_sapinst_to_gui_servergt
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
GUISERVER_HTTP_PORT=ltport_number_http_servergt
To see a list of all available SAPinst properties start SAPinst as described above with command line
parameter -p
sapinst -p
If you need to run SAPinst in accessibility mode proceed as described in Running SAPinst in Accessibility
Mode in the installation documentation of your release
If required you can stop SAPinst by choosing SAPinst Cancel in the SAPinst GUI menu
Prerequisites
We recommend that you use the csh shell for the installation with SAPinst If you want to use
another shell make sure that you have first read SAP Note 202227
SAPinst uses csh scripts during the installation to obtain the environment for user ltsapsidgtadm
This is also true if user ltsapsidgtadm already exists from an earlier SAP system installation and the
shell of this user is not csh Before you start SAPinst execute the following command as user
ltsapsidgtadm to make sure that the csh scripts are up-to-date
bincsh -c source lthome directory of ltsapsidgtadmgtcshrcenv
Make sure that you have specified the most important SAP system parameters as described in Basic
SAP System Installation Parameters in the installation documentation of your release before you start
SAPinst
Only valid for IBM DB2 for zOS |
Check that your installation hosts meet the requirements for the installation options that you
want to installEnd of IBM DB2 for zOS |
Only valid for Non-Standalone Engines and Clients |
If you want to perform a distributed or a high-availability installation make sure that you have
exported and mounted global directories For more information see Exporting and Mounting Global
Directories in the installation documentation of your releaseEnd of Non-Standalone Engines and Clients |
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you have carefully planned your database layout in particular the tablespace layout
as described in Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2554
Only valid for AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for Solaris |
Solaris SPARC onlyEnd of Solaris |
If you want to set up DB2s high-availability cluster solution SA MP make sure that you have read
the document IBM DB2 High Availability Solution IBM Tivoli System Automation for Multiplatforms at
httpservicesapcominstguidesnw70 Installation Installation ndash SAP NetWeaver SystemsEnd of AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for zOS |
First make sure that you have installed DB2 for zOS For information on that installation see
SAP DBA Guide DB2 for zOS DB2 Setup especially the section Stored Procedures EnablementEnd of IBM DB2 for zOS |
Check the value of the environment variable TEMP TMP or TMPDIR
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
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 ndash for example by using a crontab entry
Make sure that you have at least 60 MB of free space in the installation directory for each
installation option In addition you need 200 MB free space for the SAPinst executables If you
cannot provide 200 MB free space in the temporary directory you can set one of the
environment variables TEMP TMP or TMPDIR to another directory with 200 MB free space for
the SAPinst executables
Make sure that the temporary directory has the permissions 777
Only valid for IBM DB2 for zOS |
Make sure that your database is up and runningEnd of IBM DB2 for zOS |
Make sure that your DISPLAY environment variable is set to lthost_namegt00 where
lthost_namegt is the host on which you want to display the GUI
Shell Used Command
Bourne shell (sh) DISPLAY=lthost_namegt00
export DISPLAY
C shell (csh) setenv DISPLAY lthost_namegt00
Korn shell (ksh) export DISPLAY=lthost_namegt00
Make sure that umask is set to 022 for user root
As user root enter the following command umask 022
Check the following values for user root
5 Splitting
52 Running SAPinst
2654 PUBLIC 2012-04-11
In csh execute limit
Output Properties
cputime unlimited
filesize unlimited
datasize unlimited
stacksize 8192 KB
coredumpsize unlimited
descriptors 8192
memorysize unlimited
In sh or ksh execute ulimit -a
Output Properties
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192
coredump(blocks) unlimited
nofiles(descriptors) 8192
memory(KBytes) unlimited
If your parameter settings differ from those above change these values accordingly
EXAMPLE
If you have to change the value for descriptors to 8192 proceed as follows
In csh execute
limit descriptors 8192
In sh or ksh execute
ulimit -n 8192
Before you start SAPinst read SAP Note 1697164 for more information about which user to choose
for running the SAPinst SDT GUI server
Procedure
1 Log on to the installation host as user root
CAUTION
Do not use an existing ltsapsidgtadm user
Only valid for Non-Standalone Engines and Clients |
CAUTION
Make sure that the root user has not set any environment variables for a different SAP system
or database
End of Non-Standalone Engines and Clients |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2754
2 Make the Dual-Stack Split Tool available on the installation host Make sure that it is available
locally We do not recommend that you use Network File System (NFS) because reading from
media mounted with NFS might fail
For more information see Preparation Checklist [page 17] and Preparing the Installation Media in the
installation documentation of your release
3 Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
Only valid for Non-Standalone Engines and Clients |
Change to the directory with the sapinst executable for your operating system by entering the
following command cd ltMountpoint of Installation Master mediumgtDATA_UNITS
ltproductgt_IM_ltOSgtEnd of Non-Standalone Engines and Clients |
End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
4 Start SAPinst by executing the following command sapinst
NOTE
If you want to use a virtual host name start SAPinst with the SAPinst property
SAPINST_USE_HOSTNAME as follows
Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
sapinst SAPINST_USE_HOSTNAME=ltvirtual host namegt
End of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
5 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
In addition if you want to use the split option ldquoMove Java Databaserdquo choose ltYour System
Variantgt
Perform the export and installation steps exactly in the order in which they appear
6 Only valid for Non-Standalone Engines and Clients |
Choose NextEnd of Non-Standalone Engines and Clients |
7 Follow the instructions in the SAPinst input screens and enter the required parameters
NOTE
If SAPinst asks for the Java DVD make sure that you provide a Java DVD with the same
release level as your dual-stack system
For more information about the input parameters position the cursor on the parameter
and press F1
After you have entered all requested input parameters SAPinst displays the Parameter Summary screen
This screen shows both the parameters that you entered and those that SAPinst set by default If
required you can revise the parameters before starting the split procedure
5 Splitting
52 Running SAPinst
2854 PUBLIC 2012-04-11
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you check the following parameters depending on the installation type that you
have chosenEnd of IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for Linux and UNIX and Windows |
If you are performing a typical installation SAPinst creates four sapdata directories by
default If you require more or fewer sapdata directories depending on the storage devices
you are using you must change this parameter before you start the installation By selecting
this parameter on the Summary screen and choosing Revise SAPinst returns to the IBM DB2 for
Linux UNIX and Windows ndashgt Sapdata Directories screen
On this screen you can also decide if you want SAPinst to create the regular table and index
tablespaces with DB2s automatic storage management enabled By default the option for
automatic storage management is preselected
NOTE
As of DB2 V91 and higher the database and the SYSCATSPACE tablespace are always created
with automatic storage management enabled even if you deselect this option on the
dialog IBM DB2 for Linux UNIX and Windows gt Sapdata Directories
For more information about DB2s automatic storage management see section DB2
Tablespaces in the installation documentation of your SAP product
If you are performing a custom installation you set these parameters during the Define
Parameters phase of SAPinst
NOTE
If the tablespace layout used by SAPinst does not meet your requirements you can create
the tablespaces manually by deselecting the option Create Tablespaces with SAPinst on the
IBM DB2 for Linux and UNIX and Windows Sapdata Directories screen
During the installation phase SAPinst then displays the following message
You must create the tablespaces now To do so use the
createTablespacessql script that is located in your installation
directory
To continue the installation choose OK Alternatively you can cancel
SAPinst here and restart it again
SAPinst does not check the page size of tablespaces that have either been created manually
or that already exist If you create the tablespaces manually you must make sure that
you use a page size of 16 KBEnd of IBM DB2 for Linux and UNIX and Windows |
8 To start the dual-stack split choose Start
SAPinst starts and displays the progress of the split procedure
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2954
When the split option has finished successfully SAPinst displays the message Execution of
ltOption_Namegt has completed
Only valid for Oracle |
NOTE
When installing the Oracle database instance SAPinst stops the installation and prompts
you to install the Oracle database software For more information see Installing the Oracle
Database Software in the installation documentation of your release
After you have finished the installation of the Oracle database you continue the database
instance installation by choosing OK in the GUI of the database instance installation
Check SAP Note 1431800 for technical information about Oracle Release 112 in SAP
environments
End of Oracle |
Only valid for Enterprise Portal (EP) |
NOTE
During the final restart of Application Server Java performed by SAPinst the portal starts the
processing and uploading of the new portal archives It takes approximately 15 to 90 minutes
before the deployment is completed and the portal is launched
Do not stop SAPinst or Application Server Java during this phase
End of Enterprise Portal (EP) |
9 If required delete directories with the name sapinst_exexxxxxxxxxx after SAPinst has finished
Sometimes these remain in the temporary directory
NOTE
If there are errors with the SAPinst extraction process you can find the log file
dev_selfexout in the temporary directory
Only valid for Non-Standalone Engines and Clients |
RECOMMENDATION
Keep all installation 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 installation 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 installation directories on installation hosts but make sure
that you delete them after saving them separately
End of Non-Standalone Engines and Clients |
10 We recommend that you delete the directory ltuser_homegtsdtgui
11 Only valid for IBM DB2 for Linux and UNIX and Windows |
If not already done install the DB2 license
5 Splitting
52 Running SAPinst
3054 PUBLIC 2012-04-11
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
End of IBM DB2 for Linux and UNIX and Windows |
12 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 3154
This page is left blank for documents that are printed on both sides
6 Follow-Up Activities
61 Follow-Up Activities Checklist
This section includes the follow-up activities that you have to perform for the following split options
ldquoMove Java Databaserdquo for a central system
ldquoMove Java Databaserdquo for a distributed system or a high-availability system
ldquoKeep Databaserdquo for a central distributed or high-availability system
NOTE
Some of the follow-up activities listed in this section are not described in this documentation You
can find the detailed description in the SAP NetWeaver Application Server Java system copy
documentation relevant for your release at
httpservicesapcominstguides
Move Java Database
Central System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3354
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
7 We recommend that you perform regression testing
8 On the source system you run SAPinst [page 23] to remove the Java parts in the file system and in
the database
9 On the source system you call transaction RZ10 to reimport the profiles from the file system
10 In the Transport Management System (TMS) you configure the transport routes [page 38]
11 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
12 You clean up the system landscape data [page 40]
Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3454 PUBLIC 2012-04-11
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the database host of the source system you run SAPinst [page 23] to remove the Java database
schema
12 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
13 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
14 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
15 You clean up the system landscape data [page 40]
Keep Database
Central Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3554
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
12 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
13 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
14 You clean up the system landscape data [page 40]
62 Maintaining the Connection to the System Landscape Directory
After installing the Java system you need to reconfigure the connection between the System Landscape
Directory (SLD) the source system and the target system The steps required differ depending on
whether you use a local or a central SLD To maintain the connection to the SLD you can either run
the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split or perform the required steps manually as described below
NOTE
This step is only required if the connection to the SLD was established on the source system before
the split
Prerequisites
If you want to use the configuration wizard you need an SAP NetWeaver Java system 70 Support
Package 14 or higher in your landscape
SLDAPIUSER credentials are available in the ABAP system
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3654 PUBLIC 2012-04-11
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
6 You install the Java Development Kit This step is not required if you have installed the SAP JVM
4 on your source system
For more information see Installing the Java Development Kit in the installation documentation of your
release
7 You make sure that the required installation media are available on each host
You can download the Dual-Stack Split Tool at httpservicesapcomsltoolset
Software Logistics Toolset 10 Dual-Stack Split
You can download the Java stack and database installation media from SAP Service
Marketplace as described in Preparing the Installation Media in the installation documentation of
your release
NOTE
The release level required for the installation corresponds to the release level of your dual-
stack system
The following table shows the required installation media for the dual-stack split
SAP Instance Installation Required Media
Central services instance central instance
Dual-Stack Split Tool Java DVD RDBMS Client DVD
Move Java Database only Database instance
Dual-Stack Split Tool Java DVD Only valid for MS SQL ServerOracle |
RDBMS DVDEnd of MS SQL ServerOracle |
Only valid for MS SQL ServerOracle |
RDBMS Patch DVD (if available)End of MS SQL ServerOracle |
8 Only valid for HA (MSCS) |
To install a high-availability system with Microsoft Cluster Service (MSCS) you also perform the
MSCS-specific preparation tasks as described in the installation documentation of your releaseEnd of HA (MSCS) |
9 Only valid for HA (MSCS) |
If you choose the split option ldquoKeep Databaserdquo with the scenario ldquoKeep SCS on the Source Cluster
Systemrdquo you perform the following steps
You provide additional disk storage on the target cluster system
For more information see Distribution of SAP System Components to Disks for MSCS Directories in an
MSCS Configuration and IP Addresses in an MSCS Configuration in the installation documentation of
your release
You provide an additional IP address and an additional virtual host name for the Java system
For more information see Mapping Host Names to IP Addresses for MSCS in the installation
documentation of your releaseEnd of HA (MSCS) |
4 Preparation
41 Preparation Checklist
1854 PUBLIC 2012-04-11
10 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 19] of
the dual-stack system
11 You can continue with Splitting [page 21]
42 Performing a Full System Backup
If you decided to use the split option ldquoKeep Databaserdquo you must perform a full system backup of the
dual-stack system or at least a backup of the Java database schema before you start the split procedure
If you decided to use the split option ldquoMove Java Databaserdquo you do not need to perform a backup before
you start the split procedure
For more information about backing up your database see the database-specific backup and recovery
documentation in the SAP Library [page 7] at
SAP MaxDB
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for SAP
MaxDB
Oracle
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Oracle
IBM DB2 for i5OS
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 UDB for iSeries
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for i
4 Preparation
42 Performing a Full System Backup
2012-04-11 PUBLIC 1954
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
i
IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX
and Windows
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
Linux UNIX and Windows
IBM DB2 for zOS
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 UDB for zOS
SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for DB2 for z
OS
Microsoft SQL Server
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Microsoft SQL
Server
4 Preparation
42 Performing a Full System Backup
2054 PUBLIC 2012-04-11
5 Splitting
51 Splitting Checklist
This section includes the splitting steps that you have to perform for the following split options
ldquoMove Java Databaserdquo
ldquoKeep Databaserdquo
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Only valid for Oracle |
You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 You export the Java stack using SAPinst [page 23]
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
4 You restart the source system
5 You run SAPinst [page 23] to install a Java only system using the export from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2012-04-11 PUBLIC 2154
Distributed System
1 Only valid for Oracle |
On the database instance host of the dual-stack system you install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes on the database instance host
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 On the database instance host of the dual-stack system you run SAPinst [page 23] to export the
Java database schema
4 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the Java
parts of the file system of the central instance
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
5 You restart the source system
6 You run SAPinst [page 23] to install a central services instance for the Java target system
7 You run SAPinst [page 23] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
9 You continue with Follow-Up Activities [page 33]
Keep Database
1 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the
file system of the central instance
5 Splitting
51 Splitting Checklist
2254 PUBLIC 2012-04-11
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you wont use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
2 You restart the source system
3 You run SAPinst [page 23] to install a central services instance for the Java target system
4 On the database instance host of the dual-stack system you run SAPinst [page 23] to adapt the
database for the Java target system
NOTE
Make sure that you enter the profile directory of the Java target system in the SAP System gt
General Parameters screen
5 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
52 Running SAPinst
This section describes how to run the installation tool SAPinst SAPinst includes a GUI client and a GUI
server which both use Java
The procedure describes an installation where SAPinst GUI client and GUI server are running on the
same host In the following GUI client and GUI server are addressed as ldquoSAPinst GUIrdquo
If you need to see the installation on a remote display we recommend that you perform a remote
installation with SAPinst where the SAPinst GUI is running on a separate host from SAPinst For more
information see Performing a Remote Installation with SAPinst in the installation documentation of your
release
Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote
access to SAPinst GUI on Windows workstations For more information see SAP Note 1170809
Useful Information About SAPinst
When you start SAPinst it automatically starts the SAPinst GUI
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2354
SAPinst creates the installation directory sapinst_instdir directly below the temporary directory
SAPinst 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 SAPinst
creates the installation directory sapinst_instdir directly below the tmp directory by default
If you want SAPinst to create the installation directory sapinst_instdir in another directory set
the environment variable TEMP to this directory before you start SAPinst
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
Only valid for IBM DB2 for i5OS |
NOTE
When you leave your Qp2Term session all changes of the environment variables done by the
command export are reverted
End of IBM DB2 for i5OS |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
SAPinst creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt
SAPinst extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is located
in the environment variables TEMP TMP or TMPDIR These files are deleted after SAPinst has stopped
running
The temporary directory sapinst_exexxxxxxxxxx sometimes remains undeleted You can safely
delete it
The temporary directory also contains the log file dev_selfexout from the extraction process
which might be useful if an error occurs
CAUTION
If SAPinst cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default ports 21200 21212 and 4239 are used for communication
between SAPinst GUI server GUI and HTTP server as follows
SAPinst uses port 21200 to communicate with the GUI server
The GUI server uses port 21212 to communicate with the GUI client
5 Splitting
52 Running SAPinst
2454 PUBLIC 2012-04-11
4239 is the port of the HTTP server which is part of the GUI server
If the ports for SAPinst and the GUI server are already in use SAPinst automatically searches for
free port numbers If the search fails SAPinst exits
In this case or if you want SAPinst to use specific ports you can assign them by executing the
sapinst executable with the following command line parameters
SAPINST_DIALOG_PORT=ltport_number_sapinst_to_gui_servergt
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
GUISERVER_HTTP_PORT=ltport_number_http_servergt
To see a list of all available SAPinst properties start SAPinst as described above with command line
parameter -p
sapinst -p
If you need to run SAPinst in accessibility mode proceed as described in Running SAPinst in Accessibility
Mode in the installation documentation of your release
If required you can stop SAPinst by choosing SAPinst Cancel in the SAPinst GUI menu
Prerequisites
We recommend that you use the csh shell for the installation with SAPinst If you want to use
another shell make sure that you have first read SAP Note 202227
SAPinst uses csh scripts during the installation to obtain the environment for user ltsapsidgtadm
This is also true if user ltsapsidgtadm already exists from an earlier SAP system installation and the
shell of this user is not csh Before you start SAPinst execute the following command as user
ltsapsidgtadm to make sure that the csh scripts are up-to-date
bincsh -c source lthome directory of ltsapsidgtadmgtcshrcenv
Make sure that you have specified the most important SAP system parameters as described in Basic
SAP System Installation Parameters in the installation documentation of your release before you start
SAPinst
Only valid for IBM DB2 for zOS |
Check that your installation hosts meet the requirements for the installation options that you
want to installEnd of IBM DB2 for zOS |
Only valid for Non-Standalone Engines and Clients |
If you want to perform a distributed or a high-availability installation make sure that you have
exported and mounted global directories For more information see Exporting and Mounting Global
Directories in the installation documentation of your releaseEnd of Non-Standalone Engines and Clients |
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you have carefully planned your database layout in particular the tablespace layout
as described in Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2554
Only valid for AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for Solaris |
Solaris SPARC onlyEnd of Solaris |
If you want to set up DB2s high-availability cluster solution SA MP make sure that you have read
the document IBM DB2 High Availability Solution IBM Tivoli System Automation for Multiplatforms at
httpservicesapcominstguidesnw70 Installation Installation ndash SAP NetWeaver SystemsEnd of AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for zOS |
First make sure that you have installed DB2 for zOS For information on that installation see
SAP DBA Guide DB2 for zOS DB2 Setup especially the section Stored Procedures EnablementEnd of IBM DB2 for zOS |
Check the value of the environment variable TEMP TMP or TMPDIR
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
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 ndash for example by using a crontab entry
Make sure that you have at least 60 MB of free space in the installation directory for each
installation option In addition you need 200 MB free space for the SAPinst executables If you
cannot provide 200 MB free space in the temporary directory you can set one of the
environment variables TEMP TMP or TMPDIR to another directory with 200 MB free space for
the SAPinst executables
Make sure that the temporary directory has the permissions 777
Only valid for IBM DB2 for zOS |
Make sure that your database is up and runningEnd of IBM DB2 for zOS |
Make sure that your DISPLAY environment variable is set to lthost_namegt00 where
lthost_namegt is the host on which you want to display the GUI
Shell Used Command
Bourne shell (sh) DISPLAY=lthost_namegt00
export DISPLAY
C shell (csh) setenv DISPLAY lthost_namegt00
Korn shell (ksh) export DISPLAY=lthost_namegt00
Make sure that umask is set to 022 for user root
As user root enter the following command umask 022
Check the following values for user root
5 Splitting
52 Running SAPinst
2654 PUBLIC 2012-04-11
In csh execute limit
Output Properties
cputime unlimited
filesize unlimited
datasize unlimited
stacksize 8192 KB
coredumpsize unlimited
descriptors 8192
memorysize unlimited
In sh or ksh execute ulimit -a
Output Properties
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192
coredump(blocks) unlimited
nofiles(descriptors) 8192
memory(KBytes) unlimited
If your parameter settings differ from those above change these values accordingly
EXAMPLE
If you have to change the value for descriptors to 8192 proceed as follows
In csh execute
limit descriptors 8192
In sh or ksh execute
ulimit -n 8192
Before you start SAPinst read SAP Note 1697164 for more information about which user to choose
for running the SAPinst SDT GUI server
Procedure
1 Log on to the installation host as user root
CAUTION
Do not use an existing ltsapsidgtadm user
Only valid for Non-Standalone Engines and Clients |
CAUTION
Make sure that the root user has not set any environment variables for a different SAP system
or database
End of Non-Standalone Engines and Clients |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2754
2 Make the Dual-Stack Split Tool available on the installation host Make sure that it is available
locally We do not recommend that you use Network File System (NFS) because reading from
media mounted with NFS might fail
For more information see Preparation Checklist [page 17] and Preparing the Installation Media in the
installation documentation of your release
3 Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
Only valid for Non-Standalone Engines and Clients |
Change to the directory with the sapinst executable for your operating system by entering the
following command cd ltMountpoint of Installation Master mediumgtDATA_UNITS
ltproductgt_IM_ltOSgtEnd of Non-Standalone Engines and Clients |
End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
4 Start SAPinst by executing the following command sapinst
NOTE
If you want to use a virtual host name start SAPinst with the SAPinst property
SAPINST_USE_HOSTNAME as follows
Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
sapinst SAPINST_USE_HOSTNAME=ltvirtual host namegt
End of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
5 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
In addition if you want to use the split option ldquoMove Java Databaserdquo choose ltYour System
Variantgt
Perform the export and installation steps exactly in the order in which they appear
6 Only valid for Non-Standalone Engines and Clients |
Choose NextEnd of Non-Standalone Engines and Clients |
7 Follow the instructions in the SAPinst input screens and enter the required parameters
NOTE
If SAPinst asks for the Java DVD make sure that you provide a Java DVD with the same
release level as your dual-stack system
For more information about the input parameters position the cursor on the parameter
and press F1
After you have entered all requested input parameters SAPinst displays the Parameter Summary screen
This screen shows both the parameters that you entered and those that SAPinst set by default If
required you can revise the parameters before starting the split procedure
5 Splitting
52 Running SAPinst
2854 PUBLIC 2012-04-11
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you check the following parameters depending on the installation type that you
have chosenEnd of IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for Linux and UNIX and Windows |
If you are performing a typical installation SAPinst creates four sapdata directories by
default If you require more or fewer sapdata directories depending on the storage devices
you are using you must change this parameter before you start the installation By selecting
this parameter on the Summary screen and choosing Revise SAPinst returns to the IBM DB2 for
Linux UNIX and Windows ndashgt Sapdata Directories screen
On this screen you can also decide if you want SAPinst to create the regular table and index
tablespaces with DB2s automatic storage management enabled By default the option for
automatic storage management is preselected
NOTE
As of DB2 V91 and higher the database and the SYSCATSPACE tablespace are always created
with automatic storage management enabled even if you deselect this option on the
dialog IBM DB2 for Linux UNIX and Windows gt Sapdata Directories
For more information about DB2s automatic storage management see section DB2
Tablespaces in the installation documentation of your SAP product
If you are performing a custom installation you set these parameters during the Define
Parameters phase of SAPinst
NOTE
If the tablespace layout used by SAPinst does not meet your requirements you can create
the tablespaces manually by deselecting the option Create Tablespaces with SAPinst on the
IBM DB2 for Linux and UNIX and Windows Sapdata Directories screen
During the installation phase SAPinst then displays the following message
You must create the tablespaces now To do so use the
createTablespacessql script that is located in your installation
directory
To continue the installation choose OK Alternatively you can cancel
SAPinst here and restart it again
SAPinst does not check the page size of tablespaces that have either been created manually
or that already exist If you create the tablespaces manually you must make sure that
you use a page size of 16 KBEnd of IBM DB2 for Linux and UNIX and Windows |
8 To start the dual-stack split choose Start
SAPinst starts and displays the progress of the split procedure
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2954
When the split option has finished successfully SAPinst displays the message Execution of
ltOption_Namegt has completed
Only valid for Oracle |
NOTE
When installing the Oracle database instance SAPinst stops the installation and prompts
you to install the Oracle database software For more information see Installing the Oracle
Database Software in the installation documentation of your release
After you have finished the installation of the Oracle database you continue the database
instance installation by choosing OK in the GUI of the database instance installation
Check SAP Note 1431800 for technical information about Oracle Release 112 in SAP
environments
End of Oracle |
Only valid for Enterprise Portal (EP) |
NOTE
During the final restart of Application Server Java performed by SAPinst the portal starts the
processing and uploading of the new portal archives It takes approximately 15 to 90 minutes
before the deployment is completed and the portal is launched
Do not stop SAPinst or Application Server Java during this phase
End of Enterprise Portal (EP) |
9 If required delete directories with the name sapinst_exexxxxxxxxxx after SAPinst has finished
Sometimes these remain in the temporary directory
NOTE
If there are errors with the SAPinst extraction process you can find the log file
dev_selfexout in the temporary directory
Only valid for Non-Standalone Engines and Clients |
RECOMMENDATION
Keep all installation 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 installation 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 installation directories on installation hosts but make sure
that you delete them after saving them separately
End of Non-Standalone Engines and Clients |
10 We recommend that you delete the directory ltuser_homegtsdtgui
11 Only valid for IBM DB2 for Linux and UNIX and Windows |
If not already done install the DB2 license
5 Splitting
52 Running SAPinst
3054 PUBLIC 2012-04-11
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
End of IBM DB2 for Linux and UNIX and Windows |
12 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 3154
This page is left blank for documents that are printed on both sides
6 Follow-Up Activities
61 Follow-Up Activities Checklist
This section includes the follow-up activities that you have to perform for the following split options
ldquoMove Java Databaserdquo for a central system
ldquoMove Java Databaserdquo for a distributed system or a high-availability system
ldquoKeep Databaserdquo for a central distributed or high-availability system
NOTE
Some of the follow-up activities listed in this section are not described in this documentation You
can find the detailed description in the SAP NetWeaver Application Server Java system copy
documentation relevant for your release at
httpservicesapcominstguides
Move Java Database
Central System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3354
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
7 We recommend that you perform regression testing
8 On the source system you run SAPinst [page 23] to remove the Java parts in the file system and in
the database
9 On the source system you call transaction RZ10 to reimport the profiles from the file system
10 In the Transport Management System (TMS) you configure the transport routes [page 38]
11 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
12 You clean up the system landscape data [page 40]
Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3454 PUBLIC 2012-04-11
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the database host of the source system you run SAPinst [page 23] to remove the Java database
schema
12 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
13 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
14 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
15 You clean up the system landscape data [page 40]
Keep Database
Central Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3554
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
12 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
13 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
14 You clean up the system landscape data [page 40]
62 Maintaining the Connection to the System Landscape Directory
After installing the Java system you need to reconfigure the connection between the System Landscape
Directory (SLD) the source system and the target system The steps required differ depending on
whether you use a local or a central SLD To maintain the connection to the SLD you can either run
the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split or perform the required steps manually as described below
NOTE
This step is only required if the connection to the SLD was established on the source system before
the split
Prerequisites
If you want to use the configuration wizard you need an SAP NetWeaver Java system 70 Support
Package 14 or higher in your landscape
SLDAPIUSER credentials are available in the ABAP system
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3654 PUBLIC 2012-04-11
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
10 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 19] of
the dual-stack system
11 You can continue with Splitting [page 21]
42 Performing a Full System Backup
If you decided to use the split option ldquoKeep Databaserdquo you must perform a full system backup of the
dual-stack system or at least a backup of the Java database schema before you start the split procedure
If you decided to use the split option ldquoMove Java Databaserdquo you do not need to perform a backup before
you start the split procedure
For more information about backing up your database see the database-specific backup and recovery
documentation in the SAP Library [page 7] at
SAP MaxDB
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for MaxDB
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for SAP
MaxDB
Oracle
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Oracle
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Oracle
IBM DB2 for i5OS
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 UDB for iSeries
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for i
4 Preparation
42 Performing a Full System Backup
2012-04-11 PUBLIC 1954
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
i
IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX
and Windows
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
Linux UNIX and Windows
IBM DB2 for zOS
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 UDB for zOS
SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for DB2 for z
OS
Microsoft SQL Server
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Microsoft SQL
Server
4 Preparation
42 Performing a Full System Backup
2054 PUBLIC 2012-04-11
5 Splitting
51 Splitting Checklist
This section includes the splitting steps that you have to perform for the following split options
ldquoMove Java Databaserdquo
ldquoKeep Databaserdquo
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Only valid for Oracle |
You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 You export the Java stack using SAPinst [page 23]
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
4 You restart the source system
5 You run SAPinst [page 23] to install a Java only system using the export from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2012-04-11 PUBLIC 2154
Distributed System
1 Only valid for Oracle |
On the database instance host of the dual-stack system you install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes on the database instance host
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 On the database instance host of the dual-stack system you run SAPinst [page 23] to export the
Java database schema
4 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the Java
parts of the file system of the central instance
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
5 You restart the source system
6 You run SAPinst [page 23] to install a central services instance for the Java target system
7 You run SAPinst [page 23] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
9 You continue with Follow-Up Activities [page 33]
Keep Database
1 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the
file system of the central instance
5 Splitting
51 Splitting Checklist
2254 PUBLIC 2012-04-11
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you wont use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
2 You restart the source system
3 You run SAPinst [page 23] to install a central services instance for the Java target system
4 On the database instance host of the dual-stack system you run SAPinst [page 23] to adapt the
database for the Java target system
NOTE
Make sure that you enter the profile directory of the Java target system in the SAP System gt
General Parameters screen
5 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
52 Running SAPinst
This section describes how to run the installation tool SAPinst SAPinst includes a GUI client and a GUI
server which both use Java
The procedure describes an installation where SAPinst GUI client and GUI server are running on the
same host In the following GUI client and GUI server are addressed as ldquoSAPinst GUIrdquo
If you need to see the installation on a remote display we recommend that you perform a remote
installation with SAPinst where the SAPinst GUI is running on a separate host from SAPinst For more
information see Performing a Remote Installation with SAPinst in the installation documentation of your
release
Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote
access to SAPinst GUI on Windows workstations For more information see SAP Note 1170809
Useful Information About SAPinst
When you start SAPinst it automatically starts the SAPinst GUI
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2354
SAPinst creates the installation directory sapinst_instdir directly below the temporary directory
SAPinst 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 SAPinst
creates the installation directory sapinst_instdir directly below the tmp directory by default
If you want SAPinst to create the installation directory sapinst_instdir in another directory set
the environment variable TEMP to this directory before you start SAPinst
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
Only valid for IBM DB2 for i5OS |
NOTE
When you leave your Qp2Term session all changes of the environment variables done by the
command export are reverted
End of IBM DB2 for i5OS |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
SAPinst creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt
SAPinst extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is located
in the environment variables TEMP TMP or TMPDIR These files are deleted after SAPinst has stopped
running
The temporary directory sapinst_exexxxxxxxxxx sometimes remains undeleted You can safely
delete it
The temporary directory also contains the log file dev_selfexout from the extraction process
which might be useful if an error occurs
CAUTION
If SAPinst cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default ports 21200 21212 and 4239 are used for communication
between SAPinst GUI server GUI and HTTP server as follows
SAPinst uses port 21200 to communicate with the GUI server
The GUI server uses port 21212 to communicate with the GUI client
5 Splitting
52 Running SAPinst
2454 PUBLIC 2012-04-11
4239 is the port of the HTTP server which is part of the GUI server
If the ports for SAPinst and the GUI server are already in use SAPinst automatically searches for
free port numbers If the search fails SAPinst exits
In this case or if you want SAPinst to use specific ports you can assign them by executing the
sapinst executable with the following command line parameters
SAPINST_DIALOG_PORT=ltport_number_sapinst_to_gui_servergt
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
GUISERVER_HTTP_PORT=ltport_number_http_servergt
To see a list of all available SAPinst properties start SAPinst as described above with command line
parameter -p
sapinst -p
If you need to run SAPinst in accessibility mode proceed as described in Running SAPinst in Accessibility
Mode in the installation documentation of your release
If required you can stop SAPinst by choosing SAPinst Cancel in the SAPinst GUI menu
Prerequisites
We recommend that you use the csh shell for the installation with SAPinst If you want to use
another shell make sure that you have first read SAP Note 202227
SAPinst uses csh scripts during the installation to obtain the environment for user ltsapsidgtadm
This is also true if user ltsapsidgtadm already exists from an earlier SAP system installation and the
shell of this user is not csh Before you start SAPinst execute the following command as user
ltsapsidgtadm to make sure that the csh scripts are up-to-date
bincsh -c source lthome directory of ltsapsidgtadmgtcshrcenv
Make sure that you have specified the most important SAP system parameters as described in Basic
SAP System Installation Parameters in the installation documentation of your release before you start
SAPinst
Only valid for IBM DB2 for zOS |
Check that your installation hosts meet the requirements for the installation options that you
want to installEnd of IBM DB2 for zOS |
Only valid for Non-Standalone Engines and Clients |
If you want to perform a distributed or a high-availability installation make sure that you have
exported and mounted global directories For more information see Exporting and Mounting Global
Directories in the installation documentation of your releaseEnd of Non-Standalone Engines and Clients |
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you have carefully planned your database layout in particular the tablespace layout
as described in Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2554
Only valid for AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for Solaris |
Solaris SPARC onlyEnd of Solaris |
If you want to set up DB2s high-availability cluster solution SA MP make sure that you have read
the document IBM DB2 High Availability Solution IBM Tivoli System Automation for Multiplatforms at
httpservicesapcominstguidesnw70 Installation Installation ndash SAP NetWeaver SystemsEnd of AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for zOS |
First make sure that you have installed DB2 for zOS For information on that installation see
SAP DBA Guide DB2 for zOS DB2 Setup especially the section Stored Procedures EnablementEnd of IBM DB2 for zOS |
Check the value of the environment variable TEMP TMP or TMPDIR
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
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 ndash for example by using a crontab entry
Make sure that you have at least 60 MB of free space in the installation directory for each
installation option In addition you need 200 MB free space for the SAPinst executables If you
cannot provide 200 MB free space in the temporary directory you can set one of the
environment variables TEMP TMP or TMPDIR to another directory with 200 MB free space for
the SAPinst executables
Make sure that the temporary directory has the permissions 777
Only valid for IBM DB2 for zOS |
Make sure that your database is up and runningEnd of IBM DB2 for zOS |
Make sure that your DISPLAY environment variable is set to lthost_namegt00 where
lthost_namegt is the host on which you want to display the GUI
Shell Used Command
Bourne shell (sh) DISPLAY=lthost_namegt00
export DISPLAY
C shell (csh) setenv DISPLAY lthost_namegt00
Korn shell (ksh) export DISPLAY=lthost_namegt00
Make sure that umask is set to 022 for user root
As user root enter the following command umask 022
Check the following values for user root
5 Splitting
52 Running SAPinst
2654 PUBLIC 2012-04-11
In csh execute limit
Output Properties
cputime unlimited
filesize unlimited
datasize unlimited
stacksize 8192 KB
coredumpsize unlimited
descriptors 8192
memorysize unlimited
In sh or ksh execute ulimit -a
Output Properties
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192
coredump(blocks) unlimited
nofiles(descriptors) 8192
memory(KBytes) unlimited
If your parameter settings differ from those above change these values accordingly
EXAMPLE
If you have to change the value for descriptors to 8192 proceed as follows
In csh execute
limit descriptors 8192
In sh or ksh execute
ulimit -n 8192
Before you start SAPinst read SAP Note 1697164 for more information about which user to choose
for running the SAPinst SDT GUI server
Procedure
1 Log on to the installation host as user root
CAUTION
Do not use an existing ltsapsidgtadm user
Only valid for Non-Standalone Engines and Clients |
CAUTION
Make sure that the root user has not set any environment variables for a different SAP system
or database
End of Non-Standalone Engines and Clients |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2754
2 Make the Dual-Stack Split Tool available on the installation host Make sure that it is available
locally We do not recommend that you use Network File System (NFS) because reading from
media mounted with NFS might fail
For more information see Preparation Checklist [page 17] and Preparing the Installation Media in the
installation documentation of your release
3 Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
Only valid for Non-Standalone Engines and Clients |
Change to the directory with the sapinst executable for your operating system by entering the
following command cd ltMountpoint of Installation Master mediumgtDATA_UNITS
ltproductgt_IM_ltOSgtEnd of Non-Standalone Engines and Clients |
End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
4 Start SAPinst by executing the following command sapinst
NOTE
If you want to use a virtual host name start SAPinst with the SAPinst property
SAPINST_USE_HOSTNAME as follows
Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
sapinst SAPINST_USE_HOSTNAME=ltvirtual host namegt
End of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
5 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
In addition if you want to use the split option ldquoMove Java Databaserdquo choose ltYour System
Variantgt
Perform the export and installation steps exactly in the order in which they appear
6 Only valid for Non-Standalone Engines and Clients |
Choose NextEnd of Non-Standalone Engines and Clients |
7 Follow the instructions in the SAPinst input screens and enter the required parameters
NOTE
If SAPinst asks for the Java DVD make sure that you provide a Java DVD with the same
release level as your dual-stack system
For more information about the input parameters position the cursor on the parameter
and press F1
After you have entered all requested input parameters SAPinst displays the Parameter Summary screen
This screen shows both the parameters that you entered and those that SAPinst set by default If
required you can revise the parameters before starting the split procedure
5 Splitting
52 Running SAPinst
2854 PUBLIC 2012-04-11
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you check the following parameters depending on the installation type that you
have chosenEnd of IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for Linux and UNIX and Windows |
If you are performing a typical installation SAPinst creates four sapdata directories by
default If you require more or fewer sapdata directories depending on the storage devices
you are using you must change this parameter before you start the installation By selecting
this parameter on the Summary screen and choosing Revise SAPinst returns to the IBM DB2 for
Linux UNIX and Windows ndashgt Sapdata Directories screen
On this screen you can also decide if you want SAPinst to create the regular table and index
tablespaces with DB2s automatic storage management enabled By default the option for
automatic storage management is preselected
NOTE
As of DB2 V91 and higher the database and the SYSCATSPACE tablespace are always created
with automatic storage management enabled even if you deselect this option on the
dialog IBM DB2 for Linux UNIX and Windows gt Sapdata Directories
For more information about DB2s automatic storage management see section DB2
Tablespaces in the installation documentation of your SAP product
If you are performing a custom installation you set these parameters during the Define
Parameters phase of SAPinst
NOTE
If the tablespace layout used by SAPinst does not meet your requirements you can create
the tablespaces manually by deselecting the option Create Tablespaces with SAPinst on the
IBM DB2 for Linux and UNIX and Windows Sapdata Directories screen
During the installation phase SAPinst then displays the following message
You must create the tablespaces now To do so use the
createTablespacessql script that is located in your installation
directory
To continue the installation choose OK Alternatively you can cancel
SAPinst here and restart it again
SAPinst does not check the page size of tablespaces that have either been created manually
or that already exist If you create the tablespaces manually you must make sure that
you use a page size of 16 KBEnd of IBM DB2 for Linux and UNIX and Windows |
8 To start the dual-stack split choose Start
SAPinst starts and displays the progress of the split procedure
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2954
When the split option has finished successfully SAPinst displays the message Execution of
ltOption_Namegt has completed
Only valid for Oracle |
NOTE
When installing the Oracle database instance SAPinst stops the installation and prompts
you to install the Oracle database software For more information see Installing the Oracle
Database Software in the installation documentation of your release
After you have finished the installation of the Oracle database you continue the database
instance installation by choosing OK in the GUI of the database instance installation
Check SAP Note 1431800 for technical information about Oracle Release 112 in SAP
environments
End of Oracle |
Only valid for Enterprise Portal (EP) |
NOTE
During the final restart of Application Server Java performed by SAPinst the portal starts the
processing and uploading of the new portal archives It takes approximately 15 to 90 minutes
before the deployment is completed and the portal is launched
Do not stop SAPinst or Application Server Java during this phase
End of Enterprise Portal (EP) |
9 If required delete directories with the name sapinst_exexxxxxxxxxx after SAPinst has finished
Sometimes these remain in the temporary directory
NOTE
If there are errors with the SAPinst extraction process you can find the log file
dev_selfexout in the temporary directory
Only valid for Non-Standalone Engines and Clients |
RECOMMENDATION
Keep all installation 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 installation 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 installation directories on installation hosts but make sure
that you delete them after saving them separately
End of Non-Standalone Engines and Clients |
10 We recommend that you delete the directory ltuser_homegtsdtgui
11 Only valid for IBM DB2 for Linux and UNIX and Windows |
If not already done install the DB2 license
5 Splitting
52 Running SAPinst
3054 PUBLIC 2012-04-11
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
End of IBM DB2 for Linux and UNIX and Windows |
12 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 3154
This page is left blank for documents that are printed on both sides
6 Follow-Up Activities
61 Follow-Up Activities Checklist
This section includes the follow-up activities that you have to perform for the following split options
ldquoMove Java Databaserdquo for a central system
ldquoMove Java Databaserdquo for a distributed system or a high-availability system
ldquoKeep Databaserdquo for a central distributed or high-availability system
NOTE
Some of the follow-up activities listed in this section are not described in this documentation You
can find the detailed description in the SAP NetWeaver Application Server Java system copy
documentation relevant for your release at
httpservicesapcominstguides
Move Java Database
Central System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3354
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
7 We recommend that you perform regression testing
8 On the source system you run SAPinst [page 23] to remove the Java parts in the file system and in
the database
9 On the source system you call transaction RZ10 to reimport the profiles from the file system
10 In the Transport Management System (TMS) you configure the transport routes [page 38]
11 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
12 You clean up the system landscape data [page 40]
Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3454 PUBLIC 2012-04-11
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the database host of the source system you run SAPinst [page 23] to remove the Java database
schema
12 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
13 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
14 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
15 You clean up the system landscape data [page 40]
Keep Database
Central Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3554
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
12 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
13 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
14 You clean up the system landscape data [page 40]
62 Maintaining the Connection to the System Landscape Directory
After installing the Java system you need to reconfigure the connection between the System Landscape
Directory (SLD) the source system and the target system The steps required differ depending on
whether you use a local or a central SLD To maintain the connection to the SLD you can either run
the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split or perform the required steps manually as described below
NOTE
This step is only required if the connection to the SLD was established on the source system before
the split
Prerequisites
If you want to use the configuration wizard you need an SAP NetWeaver Java system 70 Support
Package 14 or higher in your landscape
SLDAPIUSER credentials are available in the ABAP system
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3654 PUBLIC 2012-04-11
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
i
IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX
and Windows
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for IBM DB2 for
Linux UNIX and Windows
IBM DB2 for zOS
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 UDB for zOS
SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for DB2 for zOS
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for DB2 for z
OS
Microsoft SQL Server
SAP NetWeaver 70 and SAP NetWeaver 70 including Enhancement Package 1
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks
Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 2
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General
Administration Tasks Database Administration Database Administration for Microsoft SQL Server
SAP NetWeaver 70 including Enhancement Package 3
SAP NetWeaver by Key Capability Database Administration Database Administration for Microsoft SQL
Server
4 Preparation
42 Performing a Full System Backup
2054 PUBLIC 2012-04-11
5 Splitting
51 Splitting Checklist
This section includes the splitting steps that you have to perform for the following split options
ldquoMove Java Databaserdquo
ldquoKeep Databaserdquo
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Only valid for Oracle |
You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 You export the Java stack using SAPinst [page 23]
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
4 You restart the source system
5 You run SAPinst [page 23] to install a Java only system using the export from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2012-04-11 PUBLIC 2154
Distributed System
1 Only valid for Oracle |
On the database instance host of the dual-stack system you install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes on the database instance host
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 On the database instance host of the dual-stack system you run SAPinst [page 23] to export the
Java database schema
4 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the Java
parts of the file system of the central instance
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
5 You restart the source system
6 You run SAPinst [page 23] to install a central services instance for the Java target system
7 You run SAPinst [page 23] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
9 You continue with Follow-Up Activities [page 33]
Keep Database
1 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the
file system of the central instance
5 Splitting
51 Splitting Checklist
2254 PUBLIC 2012-04-11
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you wont use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
2 You restart the source system
3 You run SAPinst [page 23] to install a central services instance for the Java target system
4 On the database instance host of the dual-stack system you run SAPinst [page 23] to adapt the
database for the Java target system
NOTE
Make sure that you enter the profile directory of the Java target system in the SAP System gt
General Parameters screen
5 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
52 Running SAPinst
This section describes how to run the installation tool SAPinst SAPinst includes a GUI client and a GUI
server which both use Java
The procedure describes an installation where SAPinst GUI client and GUI server are running on the
same host In the following GUI client and GUI server are addressed as ldquoSAPinst GUIrdquo
If you need to see the installation on a remote display we recommend that you perform a remote
installation with SAPinst where the SAPinst GUI is running on a separate host from SAPinst For more
information see Performing a Remote Installation with SAPinst in the installation documentation of your
release
Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote
access to SAPinst GUI on Windows workstations For more information see SAP Note 1170809
Useful Information About SAPinst
When you start SAPinst it automatically starts the SAPinst GUI
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2354
SAPinst creates the installation directory sapinst_instdir directly below the temporary directory
SAPinst 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 SAPinst
creates the installation directory sapinst_instdir directly below the tmp directory by default
If you want SAPinst to create the installation directory sapinst_instdir in another directory set
the environment variable TEMP to this directory before you start SAPinst
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
Only valid for IBM DB2 for i5OS |
NOTE
When you leave your Qp2Term session all changes of the environment variables done by the
command export are reverted
End of IBM DB2 for i5OS |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
SAPinst creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt
SAPinst extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is located
in the environment variables TEMP TMP or TMPDIR These files are deleted after SAPinst has stopped
running
The temporary directory sapinst_exexxxxxxxxxx sometimes remains undeleted You can safely
delete it
The temporary directory also contains the log file dev_selfexout from the extraction process
which might be useful if an error occurs
CAUTION
If SAPinst cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default ports 21200 21212 and 4239 are used for communication
between SAPinst GUI server GUI and HTTP server as follows
SAPinst uses port 21200 to communicate with the GUI server
The GUI server uses port 21212 to communicate with the GUI client
5 Splitting
52 Running SAPinst
2454 PUBLIC 2012-04-11
4239 is the port of the HTTP server which is part of the GUI server
If the ports for SAPinst and the GUI server are already in use SAPinst automatically searches for
free port numbers If the search fails SAPinst exits
In this case or if you want SAPinst to use specific ports you can assign them by executing the
sapinst executable with the following command line parameters
SAPINST_DIALOG_PORT=ltport_number_sapinst_to_gui_servergt
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
GUISERVER_HTTP_PORT=ltport_number_http_servergt
To see a list of all available SAPinst properties start SAPinst as described above with command line
parameter -p
sapinst -p
If you need to run SAPinst in accessibility mode proceed as described in Running SAPinst in Accessibility
Mode in the installation documentation of your release
If required you can stop SAPinst by choosing SAPinst Cancel in the SAPinst GUI menu
Prerequisites
We recommend that you use the csh shell for the installation with SAPinst If you want to use
another shell make sure that you have first read SAP Note 202227
SAPinst uses csh scripts during the installation to obtain the environment for user ltsapsidgtadm
This is also true if user ltsapsidgtadm already exists from an earlier SAP system installation and the
shell of this user is not csh Before you start SAPinst execute the following command as user
ltsapsidgtadm to make sure that the csh scripts are up-to-date
bincsh -c source lthome directory of ltsapsidgtadmgtcshrcenv
Make sure that you have specified the most important SAP system parameters as described in Basic
SAP System Installation Parameters in the installation documentation of your release before you start
SAPinst
Only valid for IBM DB2 for zOS |
Check that your installation hosts meet the requirements for the installation options that you
want to installEnd of IBM DB2 for zOS |
Only valid for Non-Standalone Engines and Clients |
If you want to perform a distributed or a high-availability installation make sure that you have
exported and mounted global directories For more information see Exporting and Mounting Global
Directories in the installation documentation of your releaseEnd of Non-Standalone Engines and Clients |
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you have carefully planned your database layout in particular the tablespace layout
as described in Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2554
Only valid for AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for Solaris |
Solaris SPARC onlyEnd of Solaris |
If you want to set up DB2s high-availability cluster solution SA MP make sure that you have read
the document IBM DB2 High Availability Solution IBM Tivoli System Automation for Multiplatforms at
httpservicesapcominstguidesnw70 Installation Installation ndash SAP NetWeaver SystemsEnd of AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for zOS |
First make sure that you have installed DB2 for zOS For information on that installation see
SAP DBA Guide DB2 for zOS DB2 Setup especially the section Stored Procedures EnablementEnd of IBM DB2 for zOS |
Check the value of the environment variable TEMP TMP or TMPDIR
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
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 ndash for example by using a crontab entry
Make sure that you have at least 60 MB of free space in the installation directory for each
installation option In addition you need 200 MB free space for the SAPinst executables If you
cannot provide 200 MB free space in the temporary directory you can set one of the
environment variables TEMP TMP or TMPDIR to another directory with 200 MB free space for
the SAPinst executables
Make sure that the temporary directory has the permissions 777
Only valid for IBM DB2 for zOS |
Make sure that your database is up and runningEnd of IBM DB2 for zOS |
Make sure that your DISPLAY environment variable is set to lthost_namegt00 where
lthost_namegt is the host on which you want to display the GUI
Shell Used Command
Bourne shell (sh) DISPLAY=lthost_namegt00
export DISPLAY
C shell (csh) setenv DISPLAY lthost_namegt00
Korn shell (ksh) export DISPLAY=lthost_namegt00
Make sure that umask is set to 022 for user root
As user root enter the following command umask 022
Check the following values for user root
5 Splitting
52 Running SAPinst
2654 PUBLIC 2012-04-11
In csh execute limit
Output Properties
cputime unlimited
filesize unlimited
datasize unlimited
stacksize 8192 KB
coredumpsize unlimited
descriptors 8192
memorysize unlimited
In sh or ksh execute ulimit -a
Output Properties
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192
coredump(blocks) unlimited
nofiles(descriptors) 8192
memory(KBytes) unlimited
If your parameter settings differ from those above change these values accordingly
EXAMPLE
If you have to change the value for descriptors to 8192 proceed as follows
In csh execute
limit descriptors 8192
In sh or ksh execute
ulimit -n 8192
Before you start SAPinst read SAP Note 1697164 for more information about which user to choose
for running the SAPinst SDT GUI server
Procedure
1 Log on to the installation host as user root
CAUTION
Do not use an existing ltsapsidgtadm user
Only valid for Non-Standalone Engines and Clients |
CAUTION
Make sure that the root user has not set any environment variables for a different SAP system
or database
End of Non-Standalone Engines and Clients |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2754
2 Make the Dual-Stack Split Tool available on the installation host Make sure that it is available
locally We do not recommend that you use Network File System (NFS) because reading from
media mounted with NFS might fail
For more information see Preparation Checklist [page 17] and Preparing the Installation Media in the
installation documentation of your release
3 Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
Only valid for Non-Standalone Engines and Clients |
Change to the directory with the sapinst executable for your operating system by entering the
following command cd ltMountpoint of Installation Master mediumgtDATA_UNITS
ltproductgt_IM_ltOSgtEnd of Non-Standalone Engines and Clients |
End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
4 Start SAPinst by executing the following command sapinst
NOTE
If you want to use a virtual host name start SAPinst with the SAPinst property
SAPINST_USE_HOSTNAME as follows
Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
sapinst SAPINST_USE_HOSTNAME=ltvirtual host namegt
End of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
5 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
In addition if you want to use the split option ldquoMove Java Databaserdquo choose ltYour System
Variantgt
Perform the export and installation steps exactly in the order in which they appear
6 Only valid for Non-Standalone Engines and Clients |
Choose NextEnd of Non-Standalone Engines and Clients |
7 Follow the instructions in the SAPinst input screens and enter the required parameters
NOTE
If SAPinst asks for the Java DVD make sure that you provide a Java DVD with the same
release level as your dual-stack system
For more information about the input parameters position the cursor on the parameter
and press F1
After you have entered all requested input parameters SAPinst displays the Parameter Summary screen
This screen shows both the parameters that you entered and those that SAPinst set by default If
required you can revise the parameters before starting the split procedure
5 Splitting
52 Running SAPinst
2854 PUBLIC 2012-04-11
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you check the following parameters depending on the installation type that you
have chosenEnd of IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for Linux and UNIX and Windows |
If you are performing a typical installation SAPinst creates four sapdata directories by
default If you require more or fewer sapdata directories depending on the storage devices
you are using you must change this parameter before you start the installation By selecting
this parameter on the Summary screen and choosing Revise SAPinst returns to the IBM DB2 for
Linux UNIX and Windows ndashgt Sapdata Directories screen
On this screen you can also decide if you want SAPinst to create the regular table and index
tablespaces with DB2s automatic storage management enabled By default the option for
automatic storage management is preselected
NOTE
As of DB2 V91 and higher the database and the SYSCATSPACE tablespace are always created
with automatic storage management enabled even if you deselect this option on the
dialog IBM DB2 for Linux UNIX and Windows gt Sapdata Directories
For more information about DB2s automatic storage management see section DB2
Tablespaces in the installation documentation of your SAP product
If you are performing a custom installation you set these parameters during the Define
Parameters phase of SAPinst
NOTE
If the tablespace layout used by SAPinst does not meet your requirements you can create
the tablespaces manually by deselecting the option Create Tablespaces with SAPinst on the
IBM DB2 for Linux and UNIX and Windows Sapdata Directories screen
During the installation phase SAPinst then displays the following message
You must create the tablespaces now To do so use the
createTablespacessql script that is located in your installation
directory
To continue the installation choose OK Alternatively you can cancel
SAPinst here and restart it again
SAPinst does not check the page size of tablespaces that have either been created manually
or that already exist If you create the tablespaces manually you must make sure that
you use a page size of 16 KBEnd of IBM DB2 for Linux and UNIX and Windows |
8 To start the dual-stack split choose Start
SAPinst starts and displays the progress of the split procedure
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2954
When the split option has finished successfully SAPinst displays the message Execution of
ltOption_Namegt has completed
Only valid for Oracle |
NOTE
When installing the Oracle database instance SAPinst stops the installation and prompts
you to install the Oracle database software For more information see Installing the Oracle
Database Software in the installation documentation of your release
After you have finished the installation of the Oracle database you continue the database
instance installation by choosing OK in the GUI of the database instance installation
Check SAP Note 1431800 for technical information about Oracle Release 112 in SAP
environments
End of Oracle |
Only valid for Enterprise Portal (EP) |
NOTE
During the final restart of Application Server Java performed by SAPinst the portal starts the
processing and uploading of the new portal archives It takes approximately 15 to 90 minutes
before the deployment is completed and the portal is launched
Do not stop SAPinst or Application Server Java during this phase
End of Enterprise Portal (EP) |
9 If required delete directories with the name sapinst_exexxxxxxxxxx after SAPinst has finished
Sometimes these remain in the temporary directory
NOTE
If there are errors with the SAPinst extraction process you can find the log file
dev_selfexout in the temporary directory
Only valid for Non-Standalone Engines and Clients |
RECOMMENDATION
Keep all installation 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 installation 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 installation directories on installation hosts but make sure
that you delete them after saving them separately
End of Non-Standalone Engines and Clients |
10 We recommend that you delete the directory ltuser_homegtsdtgui
11 Only valid for IBM DB2 for Linux and UNIX and Windows |
If not already done install the DB2 license
5 Splitting
52 Running SAPinst
3054 PUBLIC 2012-04-11
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
End of IBM DB2 for Linux and UNIX and Windows |
12 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 3154
This page is left blank for documents that are printed on both sides
6 Follow-Up Activities
61 Follow-Up Activities Checklist
This section includes the follow-up activities that you have to perform for the following split options
ldquoMove Java Databaserdquo for a central system
ldquoMove Java Databaserdquo for a distributed system or a high-availability system
ldquoKeep Databaserdquo for a central distributed or high-availability system
NOTE
Some of the follow-up activities listed in this section are not described in this documentation You
can find the detailed description in the SAP NetWeaver Application Server Java system copy
documentation relevant for your release at
httpservicesapcominstguides
Move Java Database
Central System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3354
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
7 We recommend that you perform regression testing
8 On the source system you run SAPinst [page 23] to remove the Java parts in the file system and in
the database
9 On the source system you call transaction RZ10 to reimport the profiles from the file system
10 In the Transport Management System (TMS) you configure the transport routes [page 38]
11 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
12 You clean up the system landscape data [page 40]
Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3454 PUBLIC 2012-04-11
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the database host of the source system you run SAPinst [page 23] to remove the Java database
schema
12 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
13 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
14 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
15 You clean up the system landscape data [page 40]
Keep Database
Central Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3554
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
12 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
13 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
14 You clean up the system landscape data [page 40]
62 Maintaining the Connection to the System Landscape Directory
After installing the Java system you need to reconfigure the connection between the System Landscape
Directory (SLD) the source system and the target system The steps required differ depending on
whether you use a local or a central SLD To maintain the connection to the SLD you can either run
the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split or perform the required steps manually as described below
NOTE
This step is only required if the connection to the SLD was established on the source system before
the split
Prerequisites
If you want to use the configuration wizard you need an SAP NetWeaver Java system 70 Support
Package 14 or higher in your landscape
SLDAPIUSER credentials are available in the ABAP system
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3654 PUBLIC 2012-04-11
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
5 Splitting
51 Splitting Checklist
This section includes the splitting steps that you have to perform for the following split options
ldquoMove Java Databaserdquo
ldquoKeep Databaserdquo
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Only valid for Oracle |
You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 You export the Java stack using SAPinst [page 23]
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
4 You restart the source system
5 You run SAPinst [page 23] to install a Java only system using the export from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2012-04-11 PUBLIC 2154
Distributed System
1 Only valid for Oracle |
On the database instance host of the dual-stack system you install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes on the database instance host
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 On the database instance host of the dual-stack system you run SAPinst [page 23] to export the
Java database schema
4 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the Java
parts of the file system of the central instance
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
5 You restart the source system
6 You run SAPinst [page 23] to install a central services instance for the Java target system
7 You run SAPinst [page 23] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
9 You continue with Follow-Up Activities [page 33]
Keep Database
1 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the
file system of the central instance
5 Splitting
51 Splitting Checklist
2254 PUBLIC 2012-04-11
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you wont use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
2 You restart the source system
3 You run SAPinst [page 23] to install a central services instance for the Java target system
4 On the database instance host of the dual-stack system you run SAPinst [page 23] to adapt the
database for the Java target system
NOTE
Make sure that you enter the profile directory of the Java target system in the SAP System gt
General Parameters screen
5 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
52 Running SAPinst
This section describes how to run the installation tool SAPinst SAPinst includes a GUI client and a GUI
server which both use Java
The procedure describes an installation where SAPinst GUI client and GUI server are running on the
same host In the following GUI client and GUI server are addressed as ldquoSAPinst GUIrdquo
If you need to see the installation on a remote display we recommend that you perform a remote
installation with SAPinst where the SAPinst GUI is running on a separate host from SAPinst For more
information see Performing a Remote Installation with SAPinst in the installation documentation of your
release
Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote
access to SAPinst GUI on Windows workstations For more information see SAP Note 1170809
Useful Information About SAPinst
When you start SAPinst it automatically starts the SAPinst GUI
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2354
SAPinst creates the installation directory sapinst_instdir directly below the temporary directory
SAPinst 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 SAPinst
creates the installation directory sapinst_instdir directly below the tmp directory by default
If you want SAPinst to create the installation directory sapinst_instdir in another directory set
the environment variable TEMP to this directory before you start SAPinst
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
Only valid for IBM DB2 for i5OS |
NOTE
When you leave your Qp2Term session all changes of the environment variables done by the
command export are reverted
End of IBM DB2 for i5OS |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
SAPinst creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt
SAPinst extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is located
in the environment variables TEMP TMP or TMPDIR These files are deleted after SAPinst has stopped
running
The temporary directory sapinst_exexxxxxxxxxx sometimes remains undeleted You can safely
delete it
The temporary directory also contains the log file dev_selfexout from the extraction process
which might be useful if an error occurs
CAUTION
If SAPinst cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default ports 21200 21212 and 4239 are used for communication
between SAPinst GUI server GUI and HTTP server as follows
SAPinst uses port 21200 to communicate with the GUI server
The GUI server uses port 21212 to communicate with the GUI client
5 Splitting
52 Running SAPinst
2454 PUBLIC 2012-04-11
4239 is the port of the HTTP server which is part of the GUI server
If the ports for SAPinst and the GUI server are already in use SAPinst automatically searches for
free port numbers If the search fails SAPinst exits
In this case or if you want SAPinst to use specific ports you can assign them by executing the
sapinst executable with the following command line parameters
SAPINST_DIALOG_PORT=ltport_number_sapinst_to_gui_servergt
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
GUISERVER_HTTP_PORT=ltport_number_http_servergt
To see a list of all available SAPinst properties start SAPinst as described above with command line
parameter -p
sapinst -p
If you need to run SAPinst in accessibility mode proceed as described in Running SAPinst in Accessibility
Mode in the installation documentation of your release
If required you can stop SAPinst by choosing SAPinst Cancel in the SAPinst GUI menu
Prerequisites
We recommend that you use the csh shell for the installation with SAPinst If you want to use
another shell make sure that you have first read SAP Note 202227
SAPinst uses csh scripts during the installation to obtain the environment for user ltsapsidgtadm
This is also true if user ltsapsidgtadm already exists from an earlier SAP system installation and the
shell of this user is not csh Before you start SAPinst execute the following command as user
ltsapsidgtadm to make sure that the csh scripts are up-to-date
bincsh -c source lthome directory of ltsapsidgtadmgtcshrcenv
Make sure that you have specified the most important SAP system parameters as described in Basic
SAP System Installation Parameters in the installation documentation of your release before you start
SAPinst
Only valid for IBM DB2 for zOS |
Check that your installation hosts meet the requirements for the installation options that you
want to installEnd of IBM DB2 for zOS |
Only valid for Non-Standalone Engines and Clients |
If you want to perform a distributed or a high-availability installation make sure that you have
exported and mounted global directories For more information see Exporting and Mounting Global
Directories in the installation documentation of your releaseEnd of Non-Standalone Engines and Clients |
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you have carefully planned your database layout in particular the tablespace layout
as described in Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2554
Only valid for AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for Solaris |
Solaris SPARC onlyEnd of Solaris |
If you want to set up DB2s high-availability cluster solution SA MP make sure that you have read
the document IBM DB2 High Availability Solution IBM Tivoli System Automation for Multiplatforms at
httpservicesapcominstguidesnw70 Installation Installation ndash SAP NetWeaver SystemsEnd of AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for zOS |
First make sure that you have installed DB2 for zOS For information on that installation see
SAP DBA Guide DB2 for zOS DB2 Setup especially the section Stored Procedures EnablementEnd of IBM DB2 for zOS |
Check the value of the environment variable TEMP TMP or TMPDIR
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
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 ndash for example by using a crontab entry
Make sure that you have at least 60 MB of free space in the installation directory for each
installation option In addition you need 200 MB free space for the SAPinst executables If you
cannot provide 200 MB free space in the temporary directory you can set one of the
environment variables TEMP TMP or TMPDIR to another directory with 200 MB free space for
the SAPinst executables
Make sure that the temporary directory has the permissions 777
Only valid for IBM DB2 for zOS |
Make sure that your database is up and runningEnd of IBM DB2 for zOS |
Make sure that your DISPLAY environment variable is set to lthost_namegt00 where
lthost_namegt is the host on which you want to display the GUI
Shell Used Command
Bourne shell (sh) DISPLAY=lthost_namegt00
export DISPLAY
C shell (csh) setenv DISPLAY lthost_namegt00
Korn shell (ksh) export DISPLAY=lthost_namegt00
Make sure that umask is set to 022 for user root
As user root enter the following command umask 022
Check the following values for user root
5 Splitting
52 Running SAPinst
2654 PUBLIC 2012-04-11
In csh execute limit
Output Properties
cputime unlimited
filesize unlimited
datasize unlimited
stacksize 8192 KB
coredumpsize unlimited
descriptors 8192
memorysize unlimited
In sh or ksh execute ulimit -a
Output Properties
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192
coredump(blocks) unlimited
nofiles(descriptors) 8192
memory(KBytes) unlimited
If your parameter settings differ from those above change these values accordingly
EXAMPLE
If you have to change the value for descriptors to 8192 proceed as follows
In csh execute
limit descriptors 8192
In sh or ksh execute
ulimit -n 8192
Before you start SAPinst read SAP Note 1697164 for more information about which user to choose
for running the SAPinst SDT GUI server
Procedure
1 Log on to the installation host as user root
CAUTION
Do not use an existing ltsapsidgtadm user
Only valid for Non-Standalone Engines and Clients |
CAUTION
Make sure that the root user has not set any environment variables for a different SAP system
or database
End of Non-Standalone Engines and Clients |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2754
2 Make the Dual-Stack Split Tool available on the installation host Make sure that it is available
locally We do not recommend that you use Network File System (NFS) because reading from
media mounted with NFS might fail
For more information see Preparation Checklist [page 17] and Preparing the Installation Media in the
installation documentation of your release
3 Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
Only valid for Non-Standalone Engines and Clients |
Change to the directory with the sapinst executable for your operating system by entering the
following command cd ltMountpoint of Installation Master mediumgtDATA_UNITS
ltproductgt_IM_ltOSgtEnd of Non-Standalone Engines and Clients |
End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
4 Start SAPinst by executing the following command sapinst
NOTE
If you want to use a virtual host name start SAPinst with the SAPinst property
SAPINST_USE_HOSTNAME as follows
Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
sapinst SAPINST_USE_HOSTNAME=ltvirtual host namegt
End of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
5 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
In addition if you want to use the split option ldquoMove Java Databaserdquo choose ltYour System
Variantgt
Perform the export and installation steps exactly in the order in which they appear
6 Only valid for Non-Standalone Engines and Clients |
Choose NextEnd of Non-Standalone Engines and Clients |
7 Follow the instructions in the SAPinst input screens and enter the required parameters
NOTE
If SAPinst asks for the Java DVD make sure that you provide a Java DVD with the same
release level as your dual-stack system
For more information about the input parameters position the cursor on the parameter
and press F1
After you have entered all requested input parameters SAPinst displays the Parameter Summary screen
This screen shows both the parameters that you entered and those that SAPinst set by default If
required you can revise the parameters before starting the split procedure
5 Splitting
52 Running SAPinst
2854 PUBLIC 2012-04-11
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you check the following parameters depending on the installation type that you
have chosenEnd of IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for Linux and UNIX and Windows |
If you are performing a typical installation SAPinst creates four sapdata directories by
default If you require more or fewer sapdata directories depending on the storage devices
you are using you must change this parameter before you start the installation By selecting
this parameter on the Summary screen and choosing Revise SAPinst returns to the IBM DB2 for
Linux UNIX and Windows ndashgt Sapdata Directories screen
On this screen you can also decide if you want SAPinst to create the regular table and index
tablespaces with DB2s automatic storage management enabled By default the option for
automatic storage management is preselected
NOTE
As of DB2 V91 and higher the database and the SYSCATSPACE tablespace are always created
with automatic storage management enabled even if you deselect this option on the
dialog IBM DB2 for Linux UNIX and Windows gt Sapdata Directories
For more information about DB2s automatic storage management see section DB2
Tablespaces in the installation documentation of your SAP product
If you are performing a custom installation you set these parameters during the Define
Parameters phase of SAPinst
NOTE
If the tablespace layout used by SAPinst does not meet your requirements you can create
the tablespaces manually by deselecting the option Create Tablespaces with SAPinst on the
IBM DB2 for Linux and UNIX and Windows Sapdata Directories screen
During the installation phase SAPinst then displays the following message
You must create the tablespaces now To do so use the
createTablespacessql script that is located in your installation
directory
To continue the installation choose OK Alternatively you can cancel
SAPinst here and restart it again
SAPinst does not check the page size of tablespaces that have either been created manually
or that already exist If you create the tablespaces manually you must make sure that
you use a page size of 16 KBEnd of IBM DB2 for Linux and UNIX and Windows |
8 To start the dual-stack split choose Start
SAPinst starts and displays the progress of the split procedure
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2954
When the split option has finished successfully SAPinst displays the message Execution of
ltOption_Namegt has completed
Only valid for Oracle |
NOTE
When installing the Oracle database instance SAPinst stops the installation and prompts
you to install the Oracle database software For more information see Installing the Oracle
Database Software in the installation documentation of your release
After you have finished the installation of the Oracle database you continue the database
instance installation by choosing OK in the GUI of the database instance installation
Check SAP Note 1431800 for technical information about Oracle Release 112 in SAP
environments
End of Oracle |
Only valid for Enterprise Portal (EP) |
NOTE
During the final restart of Application Server Java performed by SAPinst the portal starts the
processing and uploading of the new portal archives It takes approximately 15 to 90 minutes
before the deployment is completed and the portal is launched
Do not stop SAPinst or Application Server Java during this phase
End of Enterprise Portal (EP) |
9 If required delete directories with the name sapinst_exexxxxxxxxxx after SAPinst has finished
Sometimes these remain in the temporary directory
NOTE
If there are errors with the SAPinst extraction process you can find the log file
dev_selfexout in the temporary directory
Only valid for Non-Standalone Engines and Clients |
RECOMMENDATION
Keep all installation 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 installation 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 installation directories on installation hosts but make sure
that you delete them after saving them separately
End of Non-Standalone Engines and Clients |
10 We recommend that you delete the directory ltuser_homegtsdtgui
11 Only valid for IBM DB2 for Linux and UNIX and Windows |
If not already done install the DB2 license
5 Splitting
52 Running SAPinst
3054 PUBLIC 2012-04-11
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
End of IBM DB2 for Linux and UNIX and Windows |
12 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 3154
This page is left blank for documents that are printed on both sides
6 Follow-Up Activities
61 Follow-Up Activities Checklist
This section includes the follow-up activities that you have to perform for the following split options
ldquoMove Java Databaserdquo for a central system
ldquoMove Java Databaserdquo for a distributed system or a high-availability system
ldquoKeep Databaserdquo for a central distributed or high-availability system
NOTE
Some of the follow-up activities listed in this section are not described in this documentation You
can find the detailed description in the SAP NetWeaver Application Server Java system copy
documentation relevant for your release at
httpservicesapcominstguides
Move Java Database
Central System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3354
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
7 We recommend that you perform regression testing
8 On the source system you run SAPinst [page 23] to remove the Java parts in the file system and in
the database
9 On the source system you call transaction RZ10 to reimport the profiles from the file system
10 In the Transport Management System (TMS) you configure the transport routes [page 38]
11 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
12 You clean up the system landscape data [page 40]
Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3454 PUBLIC 2012-04-11
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the database host of the source system you run SAPinst [page 23] to remove the Java database
schema
12 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
13 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
14 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
15 You clean up the system landscape data [page 40]
Keep Database
Central Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3554
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
12 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
13 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
14 You clean up the system landscape data [page 40]
62 Maintaining the Connection to the System Landscape Directory
After installing the Java system you need to reconfigure the connection between the System Landscape
Directory (SLD) the source system and the target system The steps required differ depending on
whether you use a local or a central SLD To maintain the connection to the SLD you can either run
the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split or perform the required steps manually as described below
NOTE
This step is only required if the connection to the SLD was established on the source system before
the split
Prerequisites
If you want to use the configuration wizard you need an SAP NetWeaver Java system 70 Support
Package 14 or higher in your landscape
SLDAPIUSER credentials are available in the ABAP system
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3654 PUBLIC 2012-04-11
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
Distributed System
1 Only valid for Oracle |
On the database instance host of the dual-stack system you install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your releaseEnd of Oracle |
2 Only valid for Oracle |
If required you set up multiple Oracle Homes on the database instance host
For more information see Setting Up Multiple Homes in the installation documentation of your releaseEnd of Oracle |
3 On the database instance host of the dual-stack system you run SAPinst [page 23] to export the
Java database schema
4 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the Java
parts of the file system of the central instance
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you do not use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
5 You restart the source system
6 You run SAPinst [page 23] to install a central services instance for the Java target system
7 You run SAPinst [page 23] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
9 You continue with Follow-Up Activities [page 33]
Keep Database
1 On the central instance host of the dual-stack system you run SAPinst [page 23] to export the
file system of the central instance
5 Splitting
51 Splitting Checklist
2254 PUBLIC 2012-04-11
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you wont use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
2 You restart the source system
3 You run SAPinst [page 23] to install a central services instance for the Java target system
4 On the database instance host of the dual-stack system you run SAPinst [page 23] to adapt the
database for the Java target system
NOTE
Make sure that you enter the profile directory of the Java target system in the SAP System gt
General Parameters screen
5 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
52 Running SAPinst
This section describes how to run the installation tool SAPinst SAPinst includes a GUI client and a GUI
server which both use Java
The procedure describes an installation where SAPinst GUI client and GUI server are running on the
same host In the following GUI client and GUI server are addressed as ldquoSAPinst GUIrdquo
If you need to see the installation on a remote display we recommend that you perform a remote
installation with SAPinst where the SAPinst GUI is running on a separate host from SAPinst For more
information see Performing a Remote Installation with SAPinst in the installation documentation of your
release
Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote
access to SAPinst GUI on Windows workstations For more information see SAP Note 1170809
Useful Information About SAPinst
When you start SAPinst it automatically starts the SAPinst GUI
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2354
SAPinst creates the installation directory sapinst_instdir directly below the temporary directory
SAPinst 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 SAPinst
creates the installation directory sapinst_instdir directly below the tmp directory by default
If you want SAPinst to create the installation directory sapinst_instdir in another directory set
the environment variable TEMP to this directory before you start SAPinst
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
Only valid for IBM DB2 for i5OS |
NOTE
When you leave your Qp2Term session all changes of the environment variables done by the
command export are reverted
End of IBM DB2 for i5OS |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
SAPinst creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt
SAPinst extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is located
in the environment variables TEMP TMP or TMPDIR These files are deleted after SAPinst has stopped
running
The temporary directory sapinst_exexxxxxxxxxx sometimes remains undeleted You can safely
delete it
The temporary directory also contains the log file dev_selfexout from the extraction process
which might be useful if an error occurs
CAUTION
If SAPinst cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default ports 21200 21212 and 4239 are used for communication
between SAPinst GUI server GUI and HTTP server as follows
SAPinst uses port 21200 to communicate with the GUI server
The GUI server uses port 21212 to communicate with the GUI client
5 Splitting
52 Running SAPinst
2454 PUBLIC 2012-04-11
4239 is the port of the HTTP server which is part of the GUI server
If the ports for SAPinst and the GUI server are already in use SAPinst automatically searches for
free port numbers If the search fails SAPinst exits
In this case or if you want SAPinst to use specific ports you can assign them by executing the
sapinst executable with the following command line parameters
SAPINST_DIALOG_PORT=ltport_number_sapinst_to_gui_servergt
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
GUISERVER_HTTP_PORT=ltport_number_http_servergt
To see a list of all available SAPinst properties start SAPinst as described above with command line
parameter -p
sapinst -p
If you need to run SAPinst in accessibility mode proceed as described in Running SAPinst in Accessibility
Mode in the installation documentation of your release
If required you can stop SAPinst by choosing SAPinst Cancel in the SAPinst GUI menu
Prerequisites
We recommend that you use the csh shell for the installation with SAPinst If you want to use
another shell make sure that you have first read SAP Note 202227
SAPinst uses csh scripts during the installation to obtain the environment for user ltsapsidgtadm
This is also true if user ltsapsidgtadm already exists from an earlier SAP system installation and the
shell of this user is not csh Before you start SAPinst execute the following command as user
ltsapsidgtadm to make sure that the csh scripts are up-to-date
bincsh -c source lthome directory of ltsapsidgtadmgtcshrcenv
Make sure that you have specified the most important SAP system parameters as described in Basic
SAP System Installation Parameters in the installation documentation of your release before you start
SAPinst
Only valid for IBM DB2 for zOS |
Check that your installation hosts meet the requirements for the installation options that you
want to installEnd of IBM DB2 for zOS |
Only valid for Non-Standalone Engines and Clients |
If you want to perform a distributed or a high-availability installation make sure that you have
exported and mounted global directories For more information see Exporting and Mounting Global
Directories in the installation documentation of your releaseEnd of Non-Standalone Engines and Clients |
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you have carefully planned your database layout in particular the tablespace layout
as described in Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2554
Only valid for AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for Solaris |
Solaris SPARC onlyEnd of Solaris |
If you want to set up DB2s high-availability cluster solution SA MP make sure that you have read
the document IBM DB2 High Availability Solution IBM Tivoli System Automation for Multiplatforms at
httpservicesapcominstguidesnw70 Installation Installation ndash SAP NetWeaver SystemsEnd of AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for zOS |
First make sure that you have installed DB2 for zOS For information on that installation see
SAP DBA Guide DB2 for zOS DB2 Setup especially the section Stored Procedures EnablementEnd of IBM DB2 for zOS |
Check the value of the environment variable TEMP TMP or TMPDIR
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
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 ndash for example by using a crontab entry
Make sure that you have at least 60 MB of free space in the installation directory for each
installation option In addition you need 200 MB free space for the SAPinst executables If you
cannot provide 200 MB free space in the temporary directory you can set one of the
environment variables TEMP TMP or TMPDIR to another directory with 200 MB free space for
the SAPinst executables
Make sure that the temporary directory has the permissions 777
Only valid for IBM DB2 for zOS |
Make sure that your database is up and runningEnd of IBM DB2 for zOS |
Make sure that your DISPLAY environment variable is set to lthost_namegt00 where
lthost_namegt is the host on which you want to display the GUI
Shell Used Command
Bourne shell (sh) DISPLAY=lthost_namegt00
export DISPLAY
C shell (csh) setenv DISPLAY lthost_namegt00
Korn shell (ksh) export DISPLAY=lthost_namegt00
Make sure that umask is set to 022 for user root
As user root enter the following command umask 022
Check the following values for user root
5 Splitting
52 Running SAPinst
2654 PUBLIC 2012-04-11
In csh execute limit
Output Properties
cputime unlimited
filesize unlimited
datasize unlimited
stacksize 8192 KB
coredumpsize unlimited
descriptors 8192
memorysize unlimited
In sh or ksh execute ulimit -a
Output Properties
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192
coredump(blocks) unlimited
nofiles(descriptors) 8192
memory(KBytes) unlimited
If your parameter settings differ from those above change these values accordingly
EXAMPLE
If you have to change the value for descriptors to 8192 proceed as follows
In csh execute
limit descriptors 8192
In sh or ksh execute
ulimit -n 8192
Before you start SAPinst read SAP Note 1697164 for more information about which user to choose
for running the SAPinst SDT GUI server
Procedure
1 Log on to the installation host as user root
CAUTION
Do not use an existing ltsapsidgtadm user
Only valid for Non-Standalone Engines and Clients |
CAUTION
Make sure that the root user has not set any environment variables for a different SAP system
or database
End of Non-Standalone Engines and Clients |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2754
2 Make the Dual-Stack Split Tool available on the installation host Make sure that it is available
locally We do not recommend that you use Network File System (NFS) because reading from
media mounted with NFS might fail
For more information see Preparation Checklist [page 17] and Preparing the Installation Media in the
installation documentation of your release
3 Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
Only valid for Non-Standalone Engines and Clients |
Change to the directory with the sapinst executable for your operating system by entering the
following command cd ltMountpoint of Installation Master mediumgtDATA_UNITS
ltproductgt_IM_ltOSgtEnd of Non-Standalone Engines and Clients |
End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
4 Start SAPinst by executing the following command sapinst
NOTE
If you want to use a virtual host name start SAPinst with the SAPinst property
SAPINST_USE_HOSTNAME as follows
Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
sapinst SAPINST_USE_HOSTNAME=ltvirtual host namegt
End of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
5 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
In addition if you want to use the split option ldquoMove Java Databaserdquo choose ltYour System
Variantgt
Perform the export and installation steps exactly in the order in which they appear
6 Only valid for Non-Standalone Engines and Clients |
Choose NextEnd of Non-Standalone Engines and Clients |
7 Follow the instructions in the SAPinst input screens and enter the required parameters
NOTE
If SAPinst asks for the Java DVD make sure that you provide a Java DVD with the same
release level as your dual-stack system
For more information about the input parameters position the cursor on the parameter
and press F1
After you have entered all requested input parameters SAPinst displays the Parameter Summary screen
This screen shows both the parameters that you entered and those that SAPinst set by default If
required you can revise the parameters before starting the split procedure
5 Splitting
52 Running SAPinst
2854 PUBLIC 2012-04-11
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you check the following parameters depending on the installation type that you
have chosenEnd of IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for Linux and UNIX and Windows |
If you are performing a typical installation SAPinst creates four sapdata directories by
default If you require more or fewer sapdata directories depending on the storage devices
you are using you must change this parameter before you start the installation By selecting
this parameter on the Summary screen and choosing Revise SAPinst returns to the IBM DB2 for
Linux UNIX and Windows ndashgt Sapdata Directories screen
On this screen you can also decide if you want SAPinst to create the regular table and index
tablespaces with DB2s automatic storage management enabled By default the option for
automatic storage management is preselected
NOTE
As of DB2 V91 and higher the database and the SYSCATSPACE tablespace are always created
with automatic storage management enabled even if you deselect this option on the
dialog IBM DB2 for Linux UNIX and Windows gt Sapdata Directories
For more information about DB2s automatic storage management see section DB2
Tablespaces in the installation documentation of your SAP product
If you are performing a custom installation you set these parameters during the Define
Parameters phase of SAPinst
NOTE
If the tablespace layout used by SAPinst does not meet your requirements you can create
the tablespaces manually by deselecting the option Create Tablespaces with SAPinst on the
IBM DB2 for Linux and UNIX and Windows Sapdata Directories screen
During the installation phase SAPinst then displays the following message
You must create the tablespaces now To do so use the
createTablespacessql script that is located in your installation
directory
To continue the installation choose OK Alternatively you can cancel
SAPinst here and restart it again
SAPinst does not check the page size of tablespaces that have either been created manually
or that already exist If you create the tablespaces manually you must make sure that
you use a page size of 16 KBEnd of IBM DB2 for Linux and UNIX and Windows |
8 To start the dual-stack split choose Start
SAPinst starts and displays the progress of the split procedure
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2954
When the split option has finished successfully SAPinst displays the message Execution of
ltOption_Namegt has completed
Only valid for Oracle |
NOTE
When installing the Oracle database instance SAPinst stops the installation and prompts
you to install the Oracle database software For more information see Installing the Oracle
Database Software in the installation documentation of your release
After you have finished the installation of the Oracle database you continue the database
instance installation by choosing OK in the GUI of the database instance installation
Check SAP Note 1431800 for technical information about Oracle Release 112 in SAP
environments
End of Oracle |
Only valid for Enterprise Portal (EP) |
NOTE
During the final restart of Application Server Java performed by SAPinst the portal starts the
processing and uploading of the new portal archives It takes approximately 15 to 90 minutes
before the deployment is completed and the portal is launched
Do not stop SAPinst or Application Server Java during this phase
End of Enterprise Portal (EP) |
9 If required delete directories with the name sapinst_exexxxxxxxxxx after SAPinst has finished
Sometimes these remain in the temporary directory
NOTE
If there are errors with the SAPinst extraction process you can find the log file
dev_selfexout in the temporary directory
Only valid for Non-Standalone Engines and Clients |
RECOMMENDATION
Keep all installation 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 installation 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 installation directories on installation hosts but make sure
that you delete them after saving them separately
End of Non-Standalone Engines and Clients |
10 We recommend that you delete the directory ltuser_homegtsdtgui
11 Only valid for IBM DB2 for Linux and UNIX and Windows |
If not already done install the DB2 license
5 Splitting
52 Running SAPinst
3054 PUBLIC 2012-04-11
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
End of IBM DB2 for Linux and UNIX and Windows |
12 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 3154
This page is left blank for documents that are printed on both sides
6 Follow-Up Activities
61 Follow-Up Activities Checklist
This section includes the follow-up activities that you have to perform for the following split options
ldquoMove Java Databaserdquo for a central system
ldquoMove Java Databaserdquo for a distributed system or a high-availability system
ldquoKeep Databaserdquo for a central distributed or high-availability system
NOTE
Some of the follow-up activities listed in this section are not described in this documentation You
can find the detailed description in the SAP NetWeaver Application Server Java system copy
documentation relevant for your release at
httpservicesapcominstguides
Move Java Database
Central System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3354
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
7 We recommend that you perform regression testing
8 On the source system you run SAPinst [page 23] to remove the Java parts in the file system and in
the database
9 On the source system you call transaction RZ10 to reimport the profiles from the file system
10 In the Transport Management System (TMS) you configure the transport routes [page 38]
11 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
12 You clean up the system landscape data [page 40]
Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3454 PUBLIC 2012-04-11
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the database host of the source system you run SAPinst [page 23] to remove the Java database
schema
12 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
13 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
14 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
15 You clean up the system landscape data [page 40]
Keep Database
Central Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3554
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
12 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
13 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
14 You clean up the system landscape data [page 40]
62 Maintaining the Connection to the System Landscape Directory
After installing the Java system you need to reconfigure the connection between the System Landscape
Directory (SLD) the source system and the target system The steps required differ depending on
whether you use a local or a central SLD To maintain the connection to the SLD you can either run
the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split or perform the required steps manually as described below
NOTE
This step is only required if the connection to the SLD was established on the source system before
the split
Prerequisites
If you want to use the configuration wizard you need an SAP NetWeaver Java system 70 Support
Package 14 or higher in your landscape
SLDAPIUSER credentials are available in the ABAP system
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3654 PUBLIC 2012-04-11
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
CAUTION
Make sure that you stop the Java stack of the source system before you start the export This
is not required if you perform the export for test purposes only that is you wont use the
export in a productive system
To stop the Java stack use transaction SMICM on the ABAP stack
You can decide whether you want the Java stacks of all instances to be activated or deactivated
after the export If you decide to deactivate them you can restart them later as described in Move
Java Database Restarting Instances [page 42]
2 You restart the source system
3 You run SAPinst [page 23] to install a central services instance for the Java target system
4 On the database instance host of the dual-stack system you run SAPinst [page 23] to adapt the
database for the Java target system
NOTE
Make sure that you enter the profile directory of the Java target system in the SAP System gt
General Parameters screen
5 You run SAPinst [page 23] to install a central instance for the Java target system using the export
from the dual-stack system
NOTE
Make sure that you choose a system ID for the Java target system that is different from the
dual-stack source system ID
For a list of forbidden system IDs see also the F1 help in the SAPinst dialog
6 You continue with Follow-Up Activities [page 33]
52 Running SAPinst
This section describes how to run the installation tool SAPinst SAPinst includes a GUI client and a GUI
server which both use Java
The procedure describes an installation where SAPinst GUI client and GUI server are running on the
same host In the following GUI client and GUI server are addressed as ldquoSAPinst GUIrdquo
If you need to see the installation on a remote display we recommend that you perform a remote
installation with SAPinst where the SAPinst GUI is running on a separate host from SAPinst For more
information see Performing a Remote Installation with SAPinst in the installation documentation of your
release
Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote
access to SAPinst GUI on Windows workstations For more information see SAP Note 1170809
Useful Information About SAPinst
When you start SAPinst it automatically starts the SAPinst GUI
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2354
SAPinst creates the installation directory sapinst_instdir directly below the temporary directory
SAPinst 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 SAPinst
creates the installation directory sapinst_instdir directly below the tmp directory by default
If you want SAPinst to create the installation directory sapinst_instdir in another directory set
the environment variable TEMP to this directory before you start SAPinst
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
Only valid for IBM DB2 for i5OS |
NOTE
When you leave your Qp2Term session all changes of the environment variables done by the
command export are reverted
End of IBM DB2 for i5OS |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
SAPinst creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt
SAPinst extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is located
in the environment variables TEMP TMP or TMPDIR These files are deleted after SAPinst has stopped
running
The temporary directory sapinst_exexxxxxxxxxx sometimes remains undeleted You can safely
delete it
The temporary directory also contains the log file dev_selfexout from the extraction process
which might be useful if an error occurs
CAUTION
If SAPinst cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default ports 21200 21212 and 4239 are used for communication
between SAPinst GUI server GUI and HTTP server as follows
SAPinst uses port 21200 to communicate with the GUI server
The GUI server uses port 21212 to communicate with the GUI client
5 Splitting
52 Running SAPinst
2454 PUBLIC 2012-04-11
4239 is the port of the HTTP server which is part of the GUI server
If the ports for SAPinst and the GUI server are already in use SAPinst automatically searches for
free port numbers If the search fails SAPinst exits
In this case or if you want SAPinst to use specific ports you can assign them by executing the
sapinst executable with the following command line parameters
SAPINST_DIALOG_PORT=ltport_number_sapinst_to_gui_servergt
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
GUISERVER_HTTP_PORT=ltport_number_http_servergt
To see a list of all available SAPinst properties start SAPinst as described above with command line
parameter -p
sapinst -p
If you need to run SAPinst in accessibility mode proceed as described in Running SAPinst in Accessibility
Mode in the installation documentation of your release
If required you can stop SAPinst by choosing SAPinst Cancel in the SAPinst GUI menu
Prerequisites
We recommend that you use the csh shell for the installation with SAPinst If you want to use
another shell make sure that you have first read SAP Note 202227
SAPinst uses csh scripts during the installation to obtain the environment for user ltsapsidgtadm
This is also true if user ltsapsidgtadm already exists from an earlier SAP system installation and the
shell of this user is not csh Before you start SAPinst execute the following command as user
ltsapsidgtadm to make sure that the csh scripts are up-to-date
bincsh -c source lthome directory of ltsapsidgtadmgtcshrcenv
Make sure that you have specified the most important SAP system parameters as described in Basic
SAP System Installation Parameters in the installation documentation of your release before you start
SAPinst
Only valid for IBM DB2 for zOS |
Check that your installation hosts meet the requirements for the installation options that you
want to installEnd of IBM DB2 for zOS |
Only valid for Non-Standalone Engines and Clients |
If you want to perform a distributed or a high-availability installation make sure that you have
exported and mounted global directories For more information see Exporting and Mounting Global
Directories in the installation documentation of your releaseEnd of Non-Standalone Engines and Clients |
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you have carefully planned your database layout in particular the tablespace layout
as described in Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2554
Only valid for AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for Solaris |
Solaris SPARC onlyEnd of Solaris |
If you want to set up DB2s high-availability cluster solution SA MP make sure that you have read
the document IBM DB2 High Availability Solution IBM Tivoli System Automation for Multiplatforms at
httpservicesapcominstguidesnw70 Installation Installation ndash SAP NetWeaver SystemsEnd of AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for zOS |
First make sure that you have installed DB2 for zOS For information on that installation see
SAP DBA Guide DB2 for zOS DB2 Setup especially the section Stored Procedures EnablementEnd of IBM DB2 for zOS |
Check the value of the environment variable TEMP TMP or TMPDIR
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
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 ndash for example by using a crontab entry
Make sure that you have at least 60 MB of free space in the installation directory for each
installation option In addition you need 200 MB free space for the SAPinst executables If you
cannot provide 200 MB free space in the temporary directory you can set one of the
environment variables TEMP TMP or TMPDIR to another directory with 200 MB free space for
the SAPinst executables
Make sure that the temporary directory has the permissions 777
Only valid for IBM DB2 for zOS |
Make sure that your database is up and runningEnd of IBM DB2 for zOS |
Make sure that your DISPLAY environment variable is set to lthost_namegt00 where
lthost_namegt is the host on which you want to display the GUI
Shell Used Command
Bourne shell (sh) DISPLAY=lthost_namegt00
export DISPLAY
C shell (csh) setenv DISPLAY lthost_namegt00
Korn shell (ksh) export DISPLAY=lthost_namegt00
Make sure that umask is set to 022 for user root
As user root enter the following command umask 022
Check the following values for user root
5 Splitting
52 Running SAPinst
2654 PUBLIC 2012-04-11
In csh execute limit
Output Properties
cputime unlimited
filesize unlimited
datasize unlimited
stacksize 8192 KB
coredumpsize unlimited
descriptors 8192
memorysize unlimited
In sh or ksh execute ulimit -a
Output Properties
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192
coredump(blocks) unlimited
nofiles(descriptors) 8192
memory(KBytes) unlimited
If your parameter settings differ from those above change these values accordingly
EXAMPLE
If you have to change the value for descriptors to 8192 proceed as follows
In csh execute
limit descriptors 8192
In sh or ksh execute
ulimit -n 8192
Before you start SAPinst read SAP Note 1697164 for more information about which user to choose
for running the SAPinst SDT GUI server
Procedure
1 Log on to the installation host as user root
CAUTION
Do not use an existing ltsapsidgtadm user
Only valid for Non-Standalone Engines and Clients |
CAUTION
Make sure that the root user has not set any environment variables for a different SAP system
or database
End of Non-Standalone Engines and Clients |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2754
2 Make the Dual-Stack Split Tool available on the installation host Make sure that it is available
locally We do not recommend that you use Network File System (NFS) because reading from
media mounted with NFS might fail
For more information see Preparation Checklist [page 17] and Preparing the Installation Media in the
installation documentation of your release
3 Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
Only valid for Non-Standalone Engines and Clients |
Change to the directory with the sapinst executable for your operating system by entering the
following command cd ltMountpoint of Installation Master mediumgtDATA_UNITS
ltproductgt_IM_ltOSgtEnd of Non-Standalone Engines and Clients |
End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
4 Start SAPinst by executing the following command sapinst
NOTE
If you want to use a virtual host name start SAPinst with the SAPinst property
SAPINST_USE_HOSTNAME as follows
Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
sapinst SAPINST_USE_HOSTNAME=ltvirtual host namegt
End of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
5 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
In addition if you want to use the split option ldquoMove Java Databaserdquo choose ltYour System
Variantgt
Perform the export and installation steps exactly in the order in which they appear
6 Only valid for Non-Standalone Engines and Clients |
Choose NextEnd of Non-Standalone Engines and Clients |
7 Follow the instructions in the SAPinst input screens and enter the required parameters
NOTE
If SAPinst asks for the Java DVD make sure that you provide a Java DVD with the same
release level as your dual-stack system
For more information about the input parameters position the cursor on the parameter
and press F1
After you have entered all requested input parameters SAPinst displays the Parameter Summary screen
This screen shows both the parameters that you entered and those that SAPinst set by default If
required you can revise the parameters before starting the split procedure
5 Splitting
52 Running SAPinst
2854 PUBLIC 2012-04-11
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you check the following parameters depending on the installation type that you
have chosenEnd of IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for Linux and UNIX and Windows |
If you are performing a typical installation SAPinst creates four sapdata directories by
default If you require more or fewer sapdata directories depending on the storage devices
you are using you must change this parameter before you start the installation By selecting
this parameter on the Summary screen and choosing Revise SAPinst returns to the IBM DB2 for
Linux UNIX and Windows ndashgt Sapdata Directories screen
On this screen you can also decide if you want SAPinst to create the regular table and index
tablespaces with DB2s automatic storage management enabled By default the option for
automatic storage management is preselected
NOTE
As of DB2 V91 and higher the database and the SYSCATSPACE tablespace are always created
with automatic storage management enabled even if you deselect this option on the
dialog IBM DB2 for Linux UNIX and Windows gt Sapdata Directories
For more information about DB2s automatic storage management see section DB2
Tablespaces in the installation documentation of your SAP product
If you are performing a custom installation you set these parameters during the Define
Parameters phase of SAPinst
NOTE
If the tablespace layout used by SAPinst does not meet your requirements you can create
the tablespaces manually by deselecting the option Create Tablespaces with SAPinst on the
IBM DB2 for Linux and UNIX and Windows Sapdata Directories screen
During the installation phase SAPinst then displays the following message
You must create the tablespaces now To do so use the
createTablespacessql script that is located in your installation
directory
To continue the installation choose OK Alternatively you can cancel
SAPinst here and restart it again
SAPinst does not check the page size of tablespaces that have either been created manually
or that already exist If you create the tablespaces manually you must make sure that
you use a page size of 16 KBEnd of IBM DB2 for Linux and UNIX and Windows |
8 To start the dual-stack split choose Start
SAPinst starts and displays the progress of the split procedure
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2954
When the split option has finished successfully SAPinst displays the message Execution of
ltOption_Namegt has completed
Only valid for Oracle |
NOTE
When installing the Oracle database instance SAPinst stops the installation and prompts
you to install the Oracle database software For more information see Installing the Oracle
Database Software in the installation documentation of your release
After you have finished the installation of the Oracle database you continue the database
instance installation by choosing OK in the GUI of the database instance installation
Check SAP Note 1431800 for technical information about Oracle Release 112 in SAP
environments
End of Oracle |
Only valid for Enterprise Portal (EP) |
NOTE
During the final restart of Application Server Java performed by SAPinst the portal starts the
processing and uploading of the new portal archives It takes approximately 15 to 90 minutes
before the deployment is completed and the portal is launched
Do not stop SAPinst or Application Server Java during this phase
End of Enterprise Portal (EP) |
9 If required delete directories with the name sapinst_exexxxxxxxxxx after SAPinst has finished
Sometimes these remain in the temporary directory
NOTE
If there are errors with the SAPinst extraction process you can find the log file
dev_selfexout in the temporary directory
Only valid for Non-Standalone Engines and Clients |
RECOMMENDATION
Keep all installation 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 installation 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 installation directories on installation hosts but make sure
that you delete them after saving them separately
End of Non-Standalone Engines and Clients |
10 We recommend that you delete the directory ltuser_homegtsdtgui
11 Only valid for IBM DB2 for Linux and UNIX and Windows |
If not already done install the DB2 license
5 Splitting
52 Running SAPinst
3054 PUBLIC 2012-04-11
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
End of IBM DB2 for Linux and UNIX and Windows |
12 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 3154
This page is left blank for documents that are printed on both sides
6 Follow-Up Activities
61 Follow-Up Activities Checklist
This section includes the follow-up activities that you have to perform for the following split options
ldquoMove Java Databaserdquo for a central system
ldquoMove Java Databaserdquo for a distributed system or a high-availability system
ldquoKeep Databaserdquo for a central distributed or high-availability system
NOTE
Some of the follow-up activities listed in this section are not described in this documentation You
can find the detailed description in the SAP NetWeaver Application Server Java system copy
documentation relevant for your release at
httpservicesapcominstguides
Move Java Database
Central System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3354
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
7 We recommend that you perform regression testing
8 On the source system you run SAPinst [page 23] to remove the Java parts in the file system and in
the database
9 On the source system you call transaction RZ10 to reimport the profiles from the file system
10 In the Transport Management System (TMS) you configure the transport routes [page 38]
11 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
12 You clean up the system landscape data [page 40]
Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3454 PUBLIC 2012-04-11
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the database host of the source system you run SAPinst [page 23] to remove the Java database
schema
12 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
13 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
14 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
15 You clean up the system landscape data [page 40]
Keep Database
Central Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3554
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
12 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
13 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
14 You clean up the system landscape data [page 40]
62 Maintaining the Connection to the System Landscape Directory
After installing the Java system you need to reconfigure the connection between the System Landscape
Directory (SLD) the source system and the target system The steps required differ depending on
whether you use a local or a central SLD To maintain the connection to the SLD you can either run
the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split or perform the required steps manually as described below
NOTE
This step is only required if the connection to the SLD was established on the source system before
the split
Prerequisites
If you want to use the configuration wizard you need an SAP NetWeaver Java system 70 Support
Package 14 or higher in your landscape
SLDAPIUSER credentials are available in the ABAP system
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3654 PUBLIC 2012-04-11
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
SAPinst creates the installation directory sapinst_instdir directly below the temporary directory
SAPinst 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 SAPinst
creates the installation directory sapinst_instdir directly below the tmp directory by default
If you want SAPinst to create the installation directory sapinst_instdir in another directory set
the environment variable TEMP to this directory before you start SAPinst
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
Only valid for IBM DB2 for i5OS |
NOTE
When you leave your Qp2Term session all changes of the environment variables done by the
command export are reverted
End of IBM DB2 for i5OS |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
SAPinst creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt
SAPinst extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is located
in the environment variables TEMP TMP or TMPDIR These files are deleted after SAPinst has stopped
running
The temporary directory sapinst_exexxxxxxxxxx sometimes remains undeleted You can safely
delete it
The temporary directory also contains the log file dev_selfexout from the extraction process
which might be useful if an error occurs
CAUTION
If SAPinst cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default ports 21200 21212 and 4239 are used for communication
between SAPinst GUI server GUI and HTTP server as follows
SAPinst uses port 21200 to communicate with the GUI server
The GUI server uses port 21212 to communicate with the GUI client
5 Splitting
52 Running SAPinst
2454 PUBLIC 2012-04-11
4239 is the port of the HTTP server which is part of the GUI server
If the ports for SAPinst and the GUI server are already in use SAPinst automatically searches for
free port numbers If the search fails SAPinst exits
In this case or if you want SAPinst to use specific ports you can assign them by executing the
sapinst executable with the following command line parameters
SAPINST_DIALOG_PORT=ltport_number_sapinst_to_gui_servergt
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
GUISERVER_HTTP_PORT=ltport_number_http_servergt
To see a list of all available SAPinst properties start SAPinst as described above with command line
parameter -p
sapinst -p
If you need to run SAPinst in accessibility mode proceed as described in Running SAPinst in Accessibility
Mode in the installation documentation of your release
If required you can stop SAPinst by choosing SAPinst Cancel in the SAPinst GUI menu
Prerequisites
We recommend that you use the csh shell for the installation with SAPinst If you want to use
another shell make sure that you have first read SAP Note 202227
SAPinst uses csh scripts during the installation to obtain the environment for user ltsapsidgtadm
This is also true if user ltsapsidgtadm already exists from an earlier SAP system installation and the
shell of this user is not csh Before you start SAPinst execute the following command as user
ltsapsidgtadm to make sure that the csh scripts are up-to-date
bincsh -c source lthome directory of ltsapsidgtadmgtcshrcenv
Make sure that you have specified the most important SAP system parameters as described in Basic
SAP System Installation Parameters in the installation documentation of your release before you start
SAPinst
Only valid for IBM DB2 for zOS |
Check that your installation hosts meet the requirements for the installation options that you
want to installEnd of IBM DB2 for zOS |
Only valid for Non-Standalone Engines and Clients |
If you want to perform a distributed or a high-availability installation make sure that you have
exported and mounted global directories For more information see Exporting and Mounting Global
Directories in the installation documentation of your releaseEnd of Non-Standalone Engines and Clients |
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you have carefully planned your database layout in particular the tablespace layout
as described in Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2554
Only valid for AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for Solaris |
Solaris SPARC onlyEnd of Solaris |
If you want to set up DB2s high-availability cluster solution SA MP make sure that you have read
the document IBM DB2 High Availability Solution IBM Tivoli System Automation for Multiplatforms at
httpservicesapcominstguidesnw70 Installation Installation ndash SAP NetWeaver SystemsEnd of AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for zOS |
First make sure that you have installed DB2 for zOS For information on that installation see
SAP DBA Guide DB2 for zOS DB2 Setup especially the section Stored Procedures EnablementEnd of IBM DB2 for zOS |
Check the value of the environment variable TEMP TMP or TMPDIR
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
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 ndash for example by using a crontab entry
Make sure that you have at least 60 MB of free space in the installation directory for each
installation option In addition you need 200 MB free space for the SAPinst executables If you
cannot provide 200 MB free space in the temporary directory you can set one of the
environment variables TEMP TMP or TMPDIR to another directory with 200 MB free space for
the SAPinst executables
Make sure that the temporary directory has the permissions 777
Only valid for IBM DB2 for zOS |
Make sure that your database is up and runningEnd of IBM DB2 for zOS |
Make sure that your DISPLAY environment variable is set to lthost_namegt00 where
lthost_namegt is the host on which you want to display the GUI
Shell Used Command
Bourne shell (sh) DISPLAY=lthost_namegt00
export DISPLAY
C shell (csh) setenv DISPLAY lthost_namegt00
Korn shell (ksh) export DISPLAY=lthost_namegt00
Make sure that umask is set to 022 for user root
As user root enter the following command umask 022
Check the following values for user root
5 Splitting
52 Running SAPinst
2654 PUBLIC 2012-04-11
In csh execute limit
Output Properties
cputime unlimited
filesize unlimited
datasize unlimited
stacksize 8192 KB
coredumpsize unlimited
descriptors 8192
memorysize unlimited
In sh or ksh execute ulimit -a
Output Properties
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192
coredump(blocks) unlimited
nofiles(descriptors) 8192
memory(KBytes) unlimited
If your parameter settings differ from those above change these values accordingly
EXAMPLE
If you have to change the value for descriptors to 8192 proceed as follows
In csh execute
limit descriptors 8192
In sh or ksh execute
ulimit -n 8192
Before you start SAPinst read SAP Note 1697164 for more information about which user to choose
for running the SAPinst SDT GUI server
Procedure
1 Log on to the installation host as user root
CAUTION
Do not use an existing ltsapsidgtadm user
Only valid for Non-Standalone Engines and Clients |
CAUTION
Make sure that the root user has not set any environment variables for a different SAP system
or database
End of Non-Standalone Engines and Clients |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2754
2 Make the Dual-Stack Split Tool available on the installation host Make sure that it is available
locally We do not recommend that you use Network File System (NFS) because reading from
media mounted with NFS might fail
For more information see Preparation Checklist [page 17] and Preparing the Installation Media in the
installation documentation of your release
3 Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
Only valid for Non-Standalone Engines and Clients |
Change to the directory with the sapinst executable for your operating system by entering the
following command cd ltMountpoint of Installation Master mediumgtDATA_UNITS
ltproductgt_IM_ltOSgtEnd of Non-Standalone Engines and Clients |
End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
4 Start SAPinst by executing the following command sapinst
NOTE
If you want to use a virtual host name start SAPinst with the SAPinst property
SAPINST_USE_HOSTNAME as follows
Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
sapinst SAPINST_USE_HOSTNAME=ltvirtual host namegt
End of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
5 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
In addition if you want to use the split option ldquoMove Java Databaserdquo choose ltYour System
Variantgt
Perform the export and installation steps exactly in the order in which they appear
6 Only valid for Non-Standalone Engines and Clients |
Choose NextEnd of Non-Standalone Engines and Clients |
7 Follow the instructions in the SAPinst input screens and enter the required parameters
NOTE
If SAPinst asks for the Java DVD make sure that you provide a Java DVD with the same
release level as your dual-stack system
For more information about the input parameters position the cursor on the parameter
and press F1
After you have entered all requested input parameters SAPinst displays the Parameter Summary screen
This screen shows both the parameters that you entered and those that SAPinst set by default If
required you can revise the parameters before starting the split procedure
5 Splitting
52 Running SAPinst
2854 PUBLIC 2012-04-11
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you check the following parameters depending on the installation type that you
have chosenEnd of IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for Linux and UNIX and Windows |
If you are performing a typical installation SAPinst creates four sapdata directories by
default If you require more or fewer sapdata directories depending on the storage devices
you are using you must change this parameter before you start the installation By selecting
this parameter on the Summary screen and choosing Revise SAPinst returns to the IBM DB2 for
Linux UNIX and Windows ndashgt Sapdata Directories screen
On this screen you can also decide if you want SAPinst to create the regular table and index
tablespaces with DB2s automatic storage management enabled By default the option for
automatic storage management is preselected
NOTE
As of DB2 V91 and higher the database and the SYSCATSPACE tablespace are always created
with automatic storage management enabled even if you deselect this option on the
dialog IBM DB2 for Linux UNIX and Windows gt Sapdata Directories
For more information about DB2s automatic storage management see section DB2
Tablespaces in the installation documentation of your SAP product
If you are performing a custom installation you set these parameters during the Define
Parameters phase of SAPinst
NOTE
If the tablespace layout used by SAPinst does not meet your requirements you can create
the tablespaces manually by deselecting the option Create Tablespaces with SAPinst on the
IBM DB2 for Linux and UNIX and Windows Sapdata Directories screen
During the installation phase SAPinst then displays the following message
You must create the tablespaces now To do so use the
createTablespacessql script that is located in your installation
directory
To continue the installation choose OK Alternatively you can cancel
SAPinst here and restart it again
SAPinst does not check the page size of tablespaces that have either been created manually
or that already exist If you create the tablespaces manually you must make sure that
you use a page size of 16 KBEnd of IBM DB2 for Linux and UNIX and Windows |
8 To start the dual-stack split choose Start
SAPinst starts and displays the progress of the split procedure
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2954
When the split option has finished successfully SAPinst displays the message Execution of
ltOption_Namegt has completed
Only valid for Oracle |
NOTE
When installing the Oracle database instance SAPinst stops the installation and prompts
you to install the Oracle database software For more information see Installing the Oracle
Database Software in the installation documentation of your release
After you have finished the installation of the Oracle database you continue the database
instance installation by choosing OK in the GUI of the database instance installation
Check SAP Note 1431800 for technical information about Oracle Release 112 in SAP
environments
End of Oracle |
Only valid for Enterprise Portal (EP) |
NOTE
During the final restart of Application Server Java performed by SAPinst the portal starts the
processing and uploading of the new portal archives It takes approximately 15 to 90 minutes
before the deployment is completed and the portal is launched
Do not stop SAPinst or Application Server Java during this phase
End of Enterprise Portal (EP) |
9 If required delete directories with the name sapinst_exexxxxxxxxxx after SAPinst has finished
Sometimes these remain in the temporary directory
NOTE
If there are errors with the SAPinst extraction process you can find the log file
dev_selfexout in the temporary directory
Only valid for Non-Standalone Engines and Clients |
RECOMMENDATION
Keep all installation 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 installation 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 installation directories on installation hosts but make sure
that you delete them after saving them separately
End of Non-Standalone Engines and Clients |
10 We recommend that you delete the directory ltuser_homegtsdtgui
11 Only valid for IBM DB2 for Linux and UNIX and Windows |
If not already done install the DB2 license
5 Splitting
52 Running SAPinst
3054 PUBLIC 2012-04-11
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
End of IBM DB2 for Linux and UNIX and Windows |
12 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 3154
This page is left blank for documents that are printed on both sides
6 Follow-Up Activities
61 Follow-Up Activities Checklist
This section includes the follow-up activities that you have to perform for the following split options
ldquoMove Java Databaserdquo for a central system
ldquoMove Java Databaserdquo for a distributed system or a high-availability system
ldquoKeep Databaserdquo for a central distributed or high-availability system
NOTE
Some of the follow-up activities listed in this section are not described in this documentation You
can find the detailed description in the SAP NetWeaver Application Server Java system copy
documentation relevant for your release at
httpservicesapcominstguides
Move Java Database
Central System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3354
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
7 We recommend that you perform regression testing
8 On the source system you run SAPinst [page 23] to remove the Java parts in the file system and in
the database
9 On the source system you call transaction RZ10 to reimport the profiles from the file system
10 In the Transport Management System (TMS) you configure the transport routes [page 38]
11 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
12 You clean up the system landscape data [page 40]
Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3454 PUBLIC 2012-04-11
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the database host of the source system you run SAPinst [page 23] to remove the Java database
schema
12 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
13 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
14 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
15 You clean up the system landscape data [page 40]
Keep Database
Central Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3554
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
12 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
13 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
14 You clean up the system landscape data [page 40]
62 Maintaining the Connection to the System Landscape Directory
After installing the Java system you need to reconfigure the connection between the System Landscape
Directory (SLD) the source system and the target system The steps required differ depending on
whether you use a local or a central SLD To maintain the connection to the SLD you can either run
the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split or perform the required steps manually as described below
NOTE
This step is only required if the connection to the SLD was established on the source system before
the split
Prerequisites
If you want to use the configuration wizard you need an SAP NetWeaver Java system 70 Support
Package 14 or higher in your landscape
SLDAPIUSER credentials are available in the ABAP system
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3654 PUBLIC 2012-04-11
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
4239 is the port of the HTTP server which is part of the GUI server
If the ports for SAPinst and the GUI server are already in use SAPinst automatically searches for
free port numbers If the search fails SAPinst exits
In this case or if you want SAPinst to use specific ports you can assign them by executing the
sapinst executable with the following command line parameters
SAPINST_DIALOG_PORT=ltport_number_sapinst_to_gui_servergt
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
GUISERVER_HTTP_PORT=ltport_number_http_servergt
To see a list of all available SAPinst properties start SAPinst as described above with command line
parameter -p
sapinst -p
If you need to run SAPinst in accessibility mode proceed as described in Running SAPinst in Accessibility
Mode in the installation documentation of your release
If required you can stop SAPinst by choosing SAPinst Cancel in the SAPinst GUI menu
Prerequisites
We recommend that you use the csh shell for the installation with SAPinst If you want to use
another shell make sure that you have first read SAP Note 202227
SAPinst uses csh scripts during the installation to obtain the environment for user ltsapsidgtadm
This is also true if user ltsapsidgtadm already exists from an earlier SAP system installation and the
shell of this user is not csh Before you start SAPinst execute the following command as user
ltsapsidgtadm to make sure that the csh scripts are up-to-date
bincsh -c source lthome directory of ltsapsidgtadmgtcshrcenv
Make sure that you have specified the most important SAP system parameters as described in Basic
SAP System Installation Parameters in the installation documentation of your release before you start
SAPinst
Only valid for IBM DB2 for zOS |
Check that your installation hosts meet the requirements for the installation options that you
want to installEnd of IBM DB2 for zOS |
Only valid for Non-Standalone Engines and Clients |
If you want to perform a distributed or a high-availability installation make sure that you have
exported and mounted global directories For more information see Exporting and Mounting Global
Directories in the installation documentation of your releaseEnd of Non-Standalone Engines and Clients |
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you have carefully planned your database layout in particular the tablespace layout
as described in Setup of Database Layout in the installation documentation of your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2554
Only valid for AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for Solaris |
Solaris SPARC onlyEnd of Solaris |
If you want to set up DB2s high-availability cluster solution SA MP make sure that you have read
the document IBM DB2 High Availability Solution IBM Tivoli System Automation for Multiplatforms at
httpservicesapcominstguidesnw70 Installation Installation ndash SAP NetWeaver SystemsEnd of AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for zOS |
First make sure that you have installed DB2 for zOS For information on that installation see
SAP DBA Guide DB2 for zOS DB2 Setup especially the section Stored Procedures EnablementEnd of IBM DB2 for zOS |
Check the value of the environment variable TEMP TMP or TMPDIR
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
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 ndash for example by using a crontab entry
Make sure that you have at least 60 MB of free space in the installation directory for each
installation option In addition you need 200 MB free space for the SAPinst executables If you
cannot provide 200 MB free space in the temporary directory you can set one of the
environment variables TEMP TMP or TMPDIR to another directory with 200 MB free space for
the SAPinst executables
Make sure that the temporary directory has the permissions 777
Only valid for IBM DB2 for zOS |
Make sure that your database is up and runningEnd of IBM DB2 for zOS |
Make sure that your DISPLAY environment variable is set to lthost_namegt00 where
lthost_namegt is the host on which you want to display the GUI
Shell Used Command
Bourne shell (sh) DISPLAY=lthost_namegt00
export DISPLAY
C shell (csh) setenv DISPLAY lthost_namegt00
Korn shell (ksh) export DISPLAY=lthost_namegt00
Make sure that umask is set to 022 for user root
As user root enter the following command umask 022
Check the following values for user root
5 Splitting
52 Running SAPinst
2654 PUBLIC 2012-04-11
In csh execute limit
Output Properties
cputime unlimited
filesize unlimited
datasize unlimited
stacksize 8192 KB
coredumpsize unlimited
descriptors 8192
memorysize unlimited
In sh or ksh execute ulimit -a
Output Properties
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192
coredump(blocks) unlimited
nofiles(descriptors) 8192
memory(KBytes) unlimited
If your parameter settings differ from those above change these values accordingly
EXAMPLE
If you have to change the value for descriptors to 8192 proceed as follows
In csh execute
limit descriptors 8192
In sh or ksh execute
ulimit -n 8192
Before you start SAPinst read SAP Note 1697164 for more information about which user to choose
for running the SAPinst SDT GUI server
Procedure
1 Log on to the installation host as user root
CAUTION
Do not use an existing ltsapsidgtadm user
Only valid for Non-Standalone Engines and Clients |
CAUTION
Make sure that the root user has not set any environment variables for a different SAP system
or database
End of Non-Standalone Engines and Clients |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2754
2 Make the Dual-Stack Split Tool available on the installation host Make sure that it is available
locally We do not recommend that you use Network File System (NFS) because reading from
media mounted with NFS might fail
For more information see Preparation Checklist [page 17] and Preparing the Installation Media in the
installation documentation of your release
3 Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
Only valid for Non-Standalone Engines and Clients |
Change to the directory with the sapinst executable for your operating system by entering the
following command cd ltMountpoint of Installation Master mediumgtDATA_UNITS
ltproductgt_IM_ltOSgtEnd of Non-Standalone Engines and Clients |
End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
4 Start SAPinst by executing the following command sapinst
NOTE
If you want to use a virtual host name start SAPinst with the SAPinst property
SAPINST_USE_HOSTNAME as follows
Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
sapinst SAPINST_USE_HOSTNAME=ltvirtual host namegt
End of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
5 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
In addition if you want to use the split option ldquoMove Java Databaserdquo choose ltYour System
Variantgt
Perform the export and installation steps exactly in the order in which they appear
6 Only valid for Non-Standalone Engines and Clients |
Choose NextEnd of Non-Standalone Engines and Clients |
7 Follow the instructions in the SAPinst input screens and enter the required parameters
NOTE
If SAPinst asks for the Java DVD make sure that you provide a Java DVD with the same
release level as your dual-stack system
For more information about the input parameters position the cursor on the parameter
and press F1
After you have entered all requested input parameters SAPinst displays the Parameter Summary screen
This screen shows both the parameters that you entered and those that SAPinst set by default If
required you can revise the parameters before starting the split procedure
5 Splitting
52 Running SAPinst
2854 PUBLIC 2012-04-11
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you check the following parameters depending on the installation type that you
have chosenEnd of IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for Linux and UNIX and Windows |
If you are performing a typical installation SAPinst creates four sapdata directories by
default If you require more or fewer sapdata directories depending on the storage devices
you are using you must change this parameter before you start the installation By selecting
this parameter on the Summary screen and choosing Revise SAPinst returns to the IBM DB2 for
Linux UNIX and Windows ndashgt Sapdata Directories screen
On this screen you can also decide if you want SAPinst to create the regular table and index
tablespaces with DB2s automatic storage management enabled By default the option for
automatic storage management is preselected
NOTE
As of DB2 V91 and higher the database and the SYSCATSPACE tablespace are always created
with automatic storage management enabled even if you deselect this option on the
dialog IBM DB2 for Linux UNIX and Windows gt Sapdata Directories
For more information about DB2s automatic storage management see section DB2
Tablespaces in the installation documentation of your SAP product
If you are performing a custom installation you set these parameters during the Define
Parameters phase of SAPinst
NOTE
If the tablespace layout used by SAPinst does not meet your requirements you can create
the tablespaces manually by deselecting the option Create Tablespaces with SAPinst on the
IBM DB2 for Linux and UNIX and Windows Sapdata Directories screen
During the installation phase SAPinst then displays the following message
You must create the tablespaces now To do so use the
createTablespacessql script that is located in your installation
directory
To continue the installation choose OK Alternatively you can cancel
SAPinst here and restart it again
SAPinst does not check the page size of tablespaces that have either been created manually
or that already exist If you create the tablespaces manually you must make sure that
you use a page size of 16 KBEnd of IBM DB2 for Linux and UNIX and Windows |
8 To start the dual-stack split choose Start
SAPinst starts and displays the progress of the split procedure
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2954
When the split option has finished successfully SAPinst displays the message Execution of
ltOption_Namegt has completed
Only valid for Oracle |
NOTE
When installing the Oracle database instance SAPinst stops the installation and prompts
you to install the Oracle database software For more information see Installing the Oracle
Database Software in the installation documentation of your release
After you have finished the installation of the Oracle database you continue the database
instance installation by choosing OK in the GUI of the database instance installation
Check SAP Note 1431800 for technical information about Oracle Release 112 in SAP
environments
End of Oracle |
Only valid for Enterprise Portal (EP) |
NOTE
During the final restart of Application Server Java performed by SAPinst the portal starts the
processing and uploading of the new portal archives It takes approximately 15 to 90 minutes
before the deployment is completed and the portal is launched
Do not stop SAPinst or Application Server Java during this phase
End of Enterprise Portal (EP) |
9 If required delete directories with the name sapinst_exexxxxxxxxxx after SAPinst has finished
Sometimes these remain in the temporary directory
NOTE
If there are errors with the SAPinst extraction process you can find the log file
dev_selfexout in the temporary directory
Only valid for Non-Standalone Engines and Clients |
RECOMMENDATION
Keep all installation 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 installation 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 installation directories on installation hosts but make sure
that you delete them after saving them separately
End of Non-Standalone Engines and Clients |
10 We recommend that you delete the directory ltuser_homegtsdtgui
11 Only valid for IBM DB2 for Linux and UNIX and Windows |
If not already done install the DB2 license
5 Splitting
52 Running SAPinst
3054 PUBLIC 2012-04-11
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
End of IBM DB2 for Linux and UNIX and Windows |
12 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 3154
This page is left blank for documents that are printed on both sides
6 Follow-Up Activities
61 Follow-Up Activities Checklist
This section includes the follow-up activities that you have to perform for the following split options
ldquoMove Java Databaserdquo for a central system
ldquoMove Java Databaserdquo for a distributed system or a high-availability system
ldquoKeep Databaserdquo for a central distributed or high-availability system
NOTE
Some of the follow-up activities listed in this section are not described in this documentation You
can find the detailed description in the SAP NetWeaver Application Server Java system copy
documentation relevant for your release at
httpservicesapcominstguides
Move Java Database
Central System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3354
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
7 We recommend that you perform regression testing
8 On the source system you run SAPinst [page 23] to remove the Java parts in the file system and in
the database
9 On the source system you call transaction RZ10 to reimport the profiles from the file system
10 In the Transport Management System (TMS) you configure the transport routes [page 38]
11 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
12 You clean up the system landscape data [page 40]
Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3454 PUBLIC 2012-04-11
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the database host of the source system you run SAPinst [page 23] to remove the Java database
schema
12 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
13 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
14 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
15 You clean up the system landscape data [page 40]
Keep Database
Central Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3554
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
12 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
13 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
14 You clean up the system landscape data [page 40]
62 Maintaining the Connection to the System Landscape Directory
After installing the Java system you need to reconfigure the connection between the System Landscape
Directory (SLD) the source system and the target system The steps required differ depending on
whether you use a local or a central SLD To maintain the connection to the SLD you can either run
the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split or perform the required steps manually as described below
NOTE
This step is only required if the connection to the SLD was established on the source system before
the split
Prerequisites
If you want to use the configuration wizard you need an SAP NetWeaver Java system 70 Support
Package 14 or higher in your landscape
SLDAPIUSER credentials are available in the ABAP system
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3654 PUBLIC 2012-04-11
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
Only valid for AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for Solaris |
Solaris SPARC onlyEnd of Solaris |
If you want to set up DB2s high-availability cluster solution SA MP make sure that you have read
the document IBM DB2 High Availability Solution IBM Tivoli System Automation for Multiplatforms at
httpservicesapcominstguidesnw70 Installation Installation ndash SAP NetWeaver SystemsEnd of AIXLinuxSolaris | IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for zOS |
First make sure that you have installed DB2 for zOS For information on that installation see
SAP DBA Guide DB2 for zOS DB2 Setup especially the section Stored Procedures EnablementEnd of IBM DB2 for zOS |
Check the value of the environment variable TEMP TMP or TMPDIR
Shell Used Command
Bourne shell (sh) TEMP=ltdirectorygt
export TEMP
C shell (csh) setenv TEMP ltdirectorygt
Korn shell (ksh) export TEMP=ltdirectorygt
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 ndash for example by using a crontab entry
Make sure that you have at least 60 MB of free space in the installation directory for each
installation option In addition you need 200 MB free space for the SAPinst executables If you
cannot provide 200 MB free space in the temporary directory you can set one of the
environment variables TEMP TMP or TMPDIR to another directory with 200 MB free space for
the SAPinst executables
Make sure that the temporary directory has the permissions 777
Only valid for IBM DB2 for zOS |
Make sure that your database is up and runningEnd of IBM DB2 for zOS |
Make sure that your DISPLAY environment variable is set to lthost_namegt00 where
lthost_namegt is the host on which you want to display the GUI
Shell Used Command
Bourne shell (sh) DISPLAY=lthost_namegt00
export DISPLAY
C shell (csh) setenv DISPLAY lthost_namegt00
Korn shell (ksh) export DISPLAY=lthost_namegt00
Make sure that umask is set to 022 for user root
As user root enter the following command umask 022
Check the following values for user root
5 Splitting
52 Running SAPinst
2654 PUBLIC 2012-04-11
In csh execute limit
Output Properties
cputime unlimited
filesize unlimited
datasize unlimited
stacksize 8192 KB
coredumpsize unlimited
descriptors 8192
memorysize unlimited
In sh or ksh execute ulimit -a
Output Properties
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192
coredump(blocks) unlimited
nofiles(descriptors) 8192
memory(KBytes) unlimited
If your parameter settings differ from those above change these values accordingly
EXAMPLE
If you have to change the value for descriptors to 8192 proceed as follows
In csh execute
limit descriptors 8192
In sh or ksh execute
ulimit -n 8192
Before you start SAPinst read SAP Note 1697164 for more information about which user to choose
for running the SAPinst SDT GUI server
Procedure
1 Log on to the installation host as user root
CAUTION
Do not use an existing ltsapsidgtadm user
Only valid for Non-Standalone Engines and Clients |
CAUTION
Make sure that the root user has not set any environment variables for a different SAP system
or database
End of Non-Standalone Engines and Clients |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2754
2 Make the Dual-Stack Split Tool available on the installation host Make sure that it is available
locally We do not recommend that you use Network File System (NFS) because reading from
media mounted with NFS might fail
For more information see Preparation Checklist [page 17] and Preparing the Installation Media in the
installation documentation of your release
3 Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
Only valid for Non-Standalone Engines and Clients |
Change to the directory with the sapinst executable for your operating system by entering the
following command cd ltMountpoint of Installation Master mediumgtDATA_UNITS
ltproductgt_IM_ltOSgtEnd of Non-Standalone Engines and Clients |
End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
4 Start SAPinst by executing the following command sapinst
NOTE
If you want to use a virtual host name start SAPinst with the SAPinst property
SAPINST_USE_HOSTNAME as follows
Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
sapinst SAPINST_USE_HOSTNAME=ltvirtual host namegt
End of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
5 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
In addition if you want to use the split option ldquoMove Java Databaserdquo choose ltYour System
Variantgt
Perform the export and installation steps exactly in the order in which they appear
6 Only valid for Non-Standalone Engines and Clients |
Choose NextEnd of Non-Standalone Engines and Clients |
7 Follow the instructions in the SAPinst input screens and enter the required parameters
NOTE
If SAPinst asks for the Java DVD make sure that you provide a Java DVD with the same
release level as your dual-stack system
For more information about the input parameters position the cursor on the parameter
and press F1
After you have entered all requested input parameters SAPinst displays the Parameter Summary screen
This screen shows both the parameters that you entered and those that SAPinst set by default If
required you can revise the parameters before starting the split procedure
5 Splitting
52 Running SAPinst
2854 PUBLIC 2012-04-11
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you check the following parameters depending on the installation type that you
have chosenEnd of IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for Linux and UNIX and Windows |
If you are performing a typical installation SAPinst creates four sapdata directories by
default If you require more or fewer sapdata directories depending on the storage devices
you are using you must change this parameter before you start the installation By selecting
this parameter on the Summary screen and choosing Revise SAPinst returns to the IBM DB2 for
Linux UNIX and Windows ndashgt Sapdata Directories screen
On this screen you can also decide if you want SAPinst to create the regular table and index
tablespaces with DB2s automatic storage management enabled By default the option for
automatic storage management is preselected
NOTE
As of DB2 V91 and higher the database and the SYSCATSPACE tablespace are always created
with automatic storage management enabled even if you deselect this option on the
dialog IBM DB2 for Linux UNIX and Windows gt Sapdata Directories
For more information about DB2s automatic storage management see section DB2
Tablespaces in the installation documentation of your SAP product
If you are performing a custom installation you set these parameters during the Define
Parameters phase of SAPinst
NOTE
If the tablespace layout used by SAPinst does not meet your requirements you can create
the tablespaces manually by deselecting the option Create Tablespaces with SAPinst on the
IBM DB2 for Linux and UNIX and Windows Sapdata Directories screen
During the installation phase SAPinst then displays the following message
You must create the tablespaces now To do so use the
createTablespacessql script that is located in your installation
directory
To continue the installation choose OK Alternatively you can cancel
SAPinst here and restart it again
SAPinst does not check the page size of tablespaces that have either been created manually
or that already exist If you create the tablespaces manually you must make sure that
you use a page size of 16 KBEnd of IBM DB2 for Linux and UNIX and Windows |
8 To start the dual-stack split choose Start
SAPinst starts and displays the progress of the split procedure
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2954
When the split option has finished successfully SAPinst displays the message Execution of
ltOption_Namegt has completed
Only valid for Oracle |
NOTE
When installing the Oracle database instance SAPinst stops the installation and prompts
you to install the Oracle database software For more information see Installing the Oracle
Database Software in the installation documentation of your release
After you have finished the installation of the Oracle database you continue the database
instance installation by choosing OK in the GUI of the database instance installation
Check SAP Note 1431800 for technical information about Oracle Release 112 in SAP
environments
End of Oracle |
Only valid for Enterprise Portal (EP) |
NOTE
During the final restart of Application Server Java performed by SAPinst the portal starts the
processing and uploading of the new portal archives It takes approximately 15 to 90 minutes
before the deployment is completed and the portal is launched
Do not stop SAPinst or Application Server Java during this phase
End of Enterprise Portal (EP) |
9 If required delete directories with the name sapinst_exexxxxxxxxxx after SAPinst has finished
Sometimes these remain in the temporary directory
NOTE
If there are errors with the SAPinst extraction process you can find the log file
dev_selfexout in the temporary directory
Only valid for Non-Standalone Engines and Clients |
RECOMMENDATION
Keep all installation 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 installation 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 installation directories on installation hosts but make sure
that you delete them after saving them separately
End of Non-Standalone Engines and Clients |
10 We recommend that you delete the directory ltuser_homegtsdtgui
11 Only valid for IBM DB2 for Linux and UNIX and Windows |
If not already done install the DB2 license
5 Splitting
52 Running SAPinst
3054 PUBLIC 2012-04-11
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
End of IBM DB2 for Linux and UNIX and Windows |
12 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 3154
This page is left blank for documents that are printed on both sides
6 Follow-Up Activities
61 Follow-Up Activities Checklist
This section includes the follow-up activities that you have to perform for the following split options
ldquoMove Java Databaserdquo for a central system
ldquoMove Java Databaserdquo for a distributed system or a high-availability system
ldquoKeep Databaserdquo for a central distributed or high-availability system
NOTE
Some of the follow-up activities listed in this section are not described in this documentation You
can find the detailed description in the SAP NetWeaver Application Server Java system copy
documentation relevant for your release at
httpservicesapcominstguides
Move Java Database
Central System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3354
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
7 We recommend that you perform regression testing
8 On the source system you run SAPinst [page 23] to remove the Java parts in the file system and in
the database
9 On the source system you call transaction RZ10 to reimport the profiles from the file system
10 In the Transport Management System (TMS) you configure the transport routes [page 38]
11 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
12 You clean up the system landscape data [page 40]
Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3454 PUBLIC 2012-04-11
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the database host of the source system you run SAPinst [page 23] to remove the Java database
schema
12 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
13 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
14 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
15 You clean up the system landscape data [page 40]
Keep Database
Central Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3554
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
12 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
13 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
14 You clean up the system landscape data [page 40]
62 Maintaining the Connection to the System Landscape Directory
After installing the Java system you need to reconfigure the connection between the System Landscape
Directory (SLD) the source system and the target system The steps required differ depending on
whether you use a local or a central SLD To maintain the connection to the SLD you can either run
the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split or perform the required steps manually as described below
NOTE
This step is only required if the connection to the SLD was established on the source system before
the split
Prerequisites
If you want to use the configuration wizard you need an SAP NetWeaver Java system 70 Support
Package 14 or higher in your landscape
SLDAPIUSER credentials are available in the ABAP system
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3654 PUBLIC 2012-04-11
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
In csh execute limit
Output Properties
cputime unlimited
filesize unlimited
datasize unlimited
stacksize 8192 KB
coredumpsize unlimited
descriptors 8192
memorysize unlimited
In sh or ksh execute ulimit -a
Output Properties
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192
coredump(blocks) unlimited
nofiles(descriptors) 8192
memory(KBytes) unlimited
If your parameter settings differ from those above change these values accordingly
EXAMPLE
If you have to change the value for descriptors to 8192 proceed as follows
In csh execute
limit descriptors 8192
In sh or ksh execute
ulimit -n 8192
Before you start SAPinst read SAP Note 1697164 for more information about which user to choose
for running the SAPinst SDT GUI server
Procedure
1 Log on to the installation host as user root
CAUTION
Do not use an existing ltsapsidgtadm user
Only valid for Non-Standalone Engines and Clients |
CAUTION
Make sure that the root user has not set any environment variables for a different SAP system
or database
End of Non-Standalone Engines and Clients |
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2754
2 Make the Dual-Stack Split Tool available on the installation host Make sure that it is available
locally We do not recommend that you use Network File System (NFS) because reading from
media mounted with NFS might fail
For more information see Preparation Checklist [page 17] and Preparing the Installation Media in the
installation documentation of your release
3 Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
Only valid for Non-Standalone Engines and Clients |
Change to the directory with the sapinst executable for your operating system by entering the
following command cd ltMountpoint of Installation Master mediumgtDATA_UNITS
ltproductgt_IM_ltOSgtEnd of Non-Standalone Engines and Clients |
End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
4 Start SAPinst by executing the following command sapinst
NOTE
If you want to use a virtual host name start SAPinst with the SAPinst property
SAPINST_USE_HOSTNAME as follows
Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
sapinst SAPINST_USE_HOSTNAME=ltvirtual host namegt
End of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
5 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
In addition if you want to use the split option ldquoMove Java Databaserdquo choose ltYour System
Variantgt
Perform the export and installation steps exactly in the order in which they appear
6 Only valid for Non-Standalone Engines and Clients |
Choose NextEnd of Non-Standalone Engines and Clients |
7 Follow the instructions in the SAPinst input screens and enter the required parameters
NOTE
If SAPinst asks for the Java DVD make sure that you provide a Java DVD with the same
release level as your dual-stack system
For more information about the input parameters position the cursor on the parameter
and press F1
After you have entered all requested input parameters SAPinst displays the Parameter Summary screen
This screen shows both the parameters that you entered and those that SAPinst set by default If
required you can revise the parameters before starting the split procedure
5 Splitting
52 Running SAPinst
2854 PUBLIC 2012-04-11
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you check the following parameters depending on the installation type that you
have chosenEnd of IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for Linux and UNIX and Windows |
If you are performing a typical installation SAPinst creates four sapdata directories by
default If you require more or fewer sapdata directories depending on the storage devices
you are using you must change this parameter before you start the installation By selecting
this parameter on the Summary screen and choosing Revise SAPinst returns to the IBM DB2 for
Linux UNIX and Windows ndashgt Sapdata Directories screen
On this screen you can also decide if you want SAPinst to create the regular table and index
tablespaces with DB2s automatic storage management enabled By default the option for
automatic storage management is preselected
NOTE
As of DB2 V91 and higher the database and the SYSCATSPACE tablespace are always created
with automatic storage management enabled even if you deselect this option on the
dialog IBM DB2 for Linux UNIX and Windows gt Sapdata Directories
For more information about DB2s automatic storage management see section DB2
Tablespaces in the installation documentation of your SAP product
If you are performing a custom installation you set these parameters during the Define
Parameters phase of SAPinst
NOTE
If the tablespace layout used by SAPinst does not meet your requirements you can create
the tablespaces manually by deselecting the option Create Tablespaces with SAPinst on the
IBM DB2 for Linux and UNIX and Windows Sapdata Directories screen
During the installation phase SAPinst then displays the following message
You must create the tablespaces now To do so use the
createTablespacessql script that is located in your installation
directory
To continue the installation choose OK Alternatively you can cancel
SAPinst here and restart it again
SAPinst does not check the page size of tablespaces that have either been created manually
or that already exist If you create the tablespaces manually you must make sure that
you use a page size of 16 KBEnd of IBM DB2 for Linux and UNIX and Windows |
8 To start the dual-stack split choose Start
SAPinst starts and displays the progress of the split procedure
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2954
When the split option has finished successfully SAPinst displays the message Execution of
ltOption_Namegt has completed
Only valid for Oracle |
NOTE
When installing the Oracle database instance SAPinst stops the installation and prompts
you to install the Oracle database software For more information see Installing the Oracle
Database Software in the installation documentation of your release
After you have finished the installation of the Oracle database you continue the database
instance installation by choosing OK in the GUI of the database instance installation
Check SAP Note 1431800 for technical information about Oracle Release 112 in SAP
environments
End of Oracle |
Only valid for Enterprise Portal (EP) |
NOTE
During the final restart of Application Server Java performed by SAPinst the portal starts the
processing and uploading of the new portal archives It takes approximately 15 to 90 minutes
before the deployment is completed and the portal is launched
Do not stop SAPinst or Application Server Java during this phase
End of Enterprise Portal (EP) |
9 If required delete directories with the name sapinst_exexxxxxxxxxx after SAPinst has finished
Sometimes these remain in the temporary directory
NOTE
If there are errors with the SAPinst extraction process you can find the log file
dev_selfexout in the temporary directory
Only valid for Non-Standalone Engines and Clients |
RECOMMENDATION
Keep all installation 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 installation 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 installation directories on installation hosts but make sure
that you delete them after saving them separately
End of Non-Standalone Engines and Clients |
10 We recommend that you delete the directory ltuser_homegtsdtgui
11 Only valid for IBM DB2 for Linux and UNIX and Windows |
If not already done install the DB2 license
5 Splitting
52 Running SAPinst
3054 PUBLIC 2012-04-11
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
End of IBM DB2 for Linux and UNIX and Windows |
12 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 3154
This page is left blank for documents that are printed on both sides
6 Follow-Up Activities
61 Follow-Up Activities Checklist
This section includes the follow-up activities that you have to perform for the following split options
ldquoMove Java Databaserdquo for a central system
ldquoMove Java Databaserdquo for a distributed system or a high-availability system
ldquoKeep Databaserdquo for a central distributed or high-availability system
NOTE
Some of the follow-up activities listed in this section are not described in this documentation You
can find the detailed description in the SAP NetWeaver Application Server Java system copy
documentation relevant for your release at
httpservicesapcominstguides
Move Java Database
Central System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3354
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
7 We recommend that you perform regression testing
8 On the source system you run SAPinst [page 23] to remove the Java parts in the file system and in
the database
9 On the source system you call transaction RZ10 to reimport the profiles from the file system
10 In the Transport Management System (TMS) you configure the transport routes [page 38]
11 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
12 You clean up the system landscape data [page 40]
Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3454 PUBLIC 2012-04-11
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the database host of the source system you run SAPinst [page 23] to remove the Java database
schema
12 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
13 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
14 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
15 You clean up the system landscape data [page 40]
Keep Database
Central Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3554
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
12 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
13 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
14 You clean up the system landscape data [page 40]
62 Maintaining the Connection to the System Landscape Directory
After installing the Java system you need to reconfigure the connection between the System Landscape
Directory (SLD) the source system and the target system The steps required differ depending on
whether you use a local or a central SLD To maintain the connection to the SLD you can either run
the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split or perform the required steps manually as described below
NOTE
This step is only required if the connection to the SLD was established on the source system before
the split
Prerequisites
If you want to use the configuration wizard you need an SAP NetWeaver Java system 70 Support
Package 14 or higher in your landscape
SLDAPIUSER credentials are available in the ABAP system
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3654 PUBLIC 2012-04-11
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
2 Make the Dual-Stack Split Tool available on the installation host Make sure that it is available
locally We do not recommend that you use Network File System (NFS) because reading from
media mounted with NFS might fail
For more information see Preparation Checklist [page 17] and Preparing the Installation Media in the
installation documentation of your release
3 Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
Only valid for Non-Standalone Engines and Clients |
Change to the directory with the sapinst executable for your operating system by entering the
following command cd ltMountpoint of Installation Master mediumgtDATA_UNITS
ltproductgt_IM_ltOSgtEnd of Non-Standalone Engines and Clients |
End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBNo DatabaseOracle |
4 Start SAPinst by executing the following command sapinst
NOTE
If you want to use a virtual host name start SAPinst with the SAPinst property
SAPINST_USE_HOSTNAME as follows
Only valid for IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
sapinst SAPINST_USE_HOSTNAME=ltvirtual host namegt
End of IBM DB2 for i5OS (LinuxWindows)IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBOracle |
CAUTION
Make sure that the installation directory is not mounted with NFS or there might be problems
when starting the Java Virtual Machine
5 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
In addition if you want to use the split option ldquoMove Java Databaserdquo choose ltYour System
Variantgt
Perform the export and installation steps exactly in the order in which they appear
6 Only valid for Non-Standalone Engines and Clients |
Choose NextEnd of Non-Standalone Engines and Clients |
7 Follow the instructions in the SAPinst input screens and enter the required parameters
NOTE
If SAPinst asks for the Java DVD make sure that you provide a Java DVD with the same
release level as your dual-stack system
For more information about the input parameters position the cursor on the parameter
and press F1
After you have entered all requested input parameters SAPinst displays the Parameter Summary screen
This screen shows both the parameters that you entered and those that SAPinst set by default If
required you can revise the parameters before starting the split procedure
5 Splitting
52 Running SAPinst
2854 PUBLIC 2012-04-11
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you check the following parameters depending on the installation type that you
have chosenEnd of IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for Linux and UNIX and Windows |
If you are performing a typical installation SAPinst creates four sapdata directories by
default If you require more or fewer sapdata directories depending on the storage devices
you are using you must change this parameter before you start the installation By selecting
this parameter on the Summary screen and choosing Revise SAPinst returns to the IBM DB2 for
Linux UNIX and Windows ndashgt Sapdata Directories screen
On this screen you can also decide if you want SAPinst to create the regular table and index
tablespaces with DB2s automatic storage management enabled By default the option for
automatic storage management is preselected
NOTE
As of DB2 V91 and higher the database and the SYSCATSPACE tablespace are always created
with automatic storage management enabled even if you deselect this option on the
dialog IBM DB2 for Linux UNIX and Windows gt Sapdata Directories
For more information about DB2s automatic storage management see section DB2
Tablespaces in the installation documentation of your SAP product
If you are performing a custom installation you set these parameters during the Define
Parameters phase of SAPinst
NOTE
If the tablespace layout used by SAPinst does not meet your requirements you can create
the tablespaces manually by deselecting the option Create Tablespaces with SAPinst on the
IBM DB2 for Linux and UNIX and Windows Sapdata Directories screen
During the installation phase SAPinst then displays the following message
You must create the tablespaces now To do so use the
createTablespacessql script that is located in your installation
directory
To continue the installation choose OK Alternatively you can cancel
SAPinst here and restart it again
SAPinst does not check the page size of tablespaces that have either been created manually
or that already exist If you create the tablespaces manually you must make sure that
you use a page size of 16 KBEnd of IBM DB2 for Linux and UNIX and Windows |
8 To start the dual-stack split choose Start
SAPinst starts and displays the progress of the split procedure
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2954
When the split option has finished successfully SAPinst displays the message Execution of
ltOption_Namegt has completed
Only valid for Oracle |
NOTE
When installing the Oracle database instance SAPinst stops the installation and prompts
you to install the Oracle database software For more information see Installing the Oracle
Database Software in the installation documentation of your release
After you have finished the installation of the Oracle database you continue the database
instance installation by choosing OK in the GUI of the database instance installation
Check SAP Note 1431800 for technical information about Oracle Release 112 in SAP
environments
End of Oracle |
Only valid for Enterprise Portal (EP) |
NOTE
During the final restart of Application Server Java performed by SAPinst the portal starts the
processing and uploading of the new portal archives It takes approximately 15 to 90 minutes
before the deployment is completed and the portal is launched
Do not stop SAPinst or Application Server Java during this phase
End of Enterprise Portal (EP) |
9 If required delete directories with the name sapinst_exexxxxxxxxxx after SAPinst has finished
Sometimes these remain in the temporary directory
NOTE
If there are errors with the SAPinst extraction process you can find the log file
dev_selfexout in the temporary directory
Only valid for Non-Standalone Engines and Clients |
RECOMMENDATION
Keep all installation 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 installation 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 installation directories on installation hosts but make sure
that you delete them after saving them separately
End of Non-Standalone Engines and Clients |
10 We recommend that you delete the directory ltuser_homegtsdtgui
11 Only valid for IBM DB2 for Linux and UNIX and Windows |
If not already done install the DB2 license
5 Splitting
52 Running SAPinst
3054 PUBLIC 2012-04-11
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
End of IBM DB2 for Linux and UNIX and Windows |
12 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 3154
This page is left blank for documents that are printed on both sides
6 Follow-Up Activities
61 Follow-Up Activities Checklist
This section includes the follow-up activities that you have to perform for the following split options
ldquoMove Java Databaserdquo for a central system
ldquoMove Java Databaserdquo for a distributed system or a high-availability system
ldquoKeep Databaserdquo for a central distributed or high-availability system
NOTE
Some of the follow-up activities listed in this section are not described in this documentation You
can find the detailed description in the SAP NetWeaver Application Server Java system copy
documentation relevant for your release at
httpservicesapcominstguides
Move Java Database
Central System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3354
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
7 We recommend that you perform regression testing
8 On the source system you run SAPinst [page 23] to remove the Java parts in the file system and in
the database
9 On the source system you call transaction RZ10 to reimport the profiles from the file system
10 In the Transport Management System (TMS) you configure the transport routes [page 38]
11 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
12 You clean up the system landscape data [page 40]
Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3454 PUBLIC 2012-04-11
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the database host of the source system you run SAPinst [page 23] to remove the Java database
schema
12 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
13 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
14 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
15 You clean up the system landscape data [page 40]
Keep Database
Central Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3554
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
12 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
13 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
14 You clean up the system landscape data [page 40]
62 Maintaining the Connection to the System Landscape Directory
After installing the Java system you need to reconfigure the connection between the System Landscape
Directory (SLD) the source system and the target system The steps required differ depending on
whether you use a local or a central SLD To maintain the connection to the SLD you can either run
the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split or perform the required steps manually as described below
NOTE
This step is only required if the connection to the SLD was established on the source system before
the split
Prerequisites
If you want to use the configuration wizard you need an SAP NetWeaver Java system 70 Support
Package 14 or higher in your landscape
SLDAPIUSER credentials are available in the ABAP system
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3654 PUBLIC 2012-04-11
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
Only valid for IBM DB2 for Linux and UNIX and Windows |
Make sure that you check the following parameters depending on the installation type that you
have chosenEnd of IBM DB2 for Linux and UNIX and Windows |
Only valid for IBM DB2 for Linux and UNIX and Windows |
If you are performing a typical installation SAPinst creates four sapdata directories by
default If you require more or fewer sapdata directories depending on the storage devices
you are using you must change this parameter before you start the installation By selecting
this parameter on the Summary screen and choosing Revise SAPinst returns to the IBM DB2 for
Linux UNIX and Windows ndashgt Sapdata Directories screen
On this screen you can also decide if you want SAPinst to create the regular table and index
tablespaces with DB2s automatic storage management enabled By default the option for
automatic storage management is preselected
NOTE
As of DB2 V91 and higher the database and the SYSCATSPACE tablespace are always created
with automatic storage management enabled even if you deselect this option on the
dialog IBM DB2 for Linux UNIX and Windows gt Sapdata Directories
For more information about DB2s automatic storage management see section DB2
Tablespaces in the installation documentation of your SAP product
If you are performing a custom installation you set these parameters during the Define
Parameters phase of SAPinst
NOTE
If the tablespace layout used by SAPinst does not meet your requirements you can create
the tablespaces manually by deselecting the option Create Tablespaces with SAPinst on the
IBM DB2 for Linux and UNIX and Windows Sapdata Directories screen
During the installation phase SAPinst then displays the following message
You must create the tablespaces now To do so use the
createTablespacessql script that is located in your installation
directory
To continue the installation choose OK Alternatively you can cancel
SAPinst here and restart it again
SAPinst does not check the page size of tablespaces that have either been created manually
or that already exist If you create the tablespaces manually you must make sure that
you use a page size of 16 KBEnd of IBM DB2 for Linux and UNIX and Windows |
8 To start the dual-stack split choose Start
SAPinst starts and displays the progress of the split procedure
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 2954
When the split option has finished successfully SAPinst displays the message Execution of
ltOption_Namegt has completed
Only valid for Oracle |
NOTE
When installing the Oracle database instance SAPinst stops the installation and prompts
you to install the Oracle database software For more information see Installing the Oracle
Database Software in the installation documentation of your release
After you have finished the installation of the Oracle database you continue the database
instance installation by choosing OK in the GUI of the database instance installation
Check SAP Note 1431800 for technical information about Oracle Release 112 in SAP
environments
End of Oracle |
Only valid for Enterprise Portal (EP) |
NOTE
During the final restart of Application Server Java performed by SAPinst the portal starts the
processing and uploading of the new portal archives It takes approximately 15 to 90 minutes
before the deployment is completed and the portal is launched
Do not stop SAPinst or Application Server Java during this phase
End of Enterprise Portal (EP) |
9 If required delete directories with the name sapinst_exexxxxxxxxxx after SAPinst has finished
Sometimes these remain in the temporary directory
NOTE
If there are errors with the SAPinst extraction process you can find the log file
dev_selfexout in the temporary directory
Only valid for Non-Standalone Engines and Clients |
RECOMMENDATION
Keep all installation 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 installation 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 installation directories on installation hosts but make sure
that you delete them after saving them separately
End of Non-Standalone Engines and Clients |
10 We recommend that you delete the directory ltuser_homegtsdtgui
11 Only valid for IBM DB2 for Linux and UNIX and Windows |
If not already done install the DB2 license
5 Splitting
52 Running SAPinst
3054 PUBLIC 2012-04-11
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
End of IBM DB2 for Linux and UNIX and Windows |
12 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 3154
This page is left blank for documents that are printed on both sides
6 Follow-Up Activities
61 Follow-Up Activities Checklist
This section includes the follow-up activities that you have to perform for the following split options
ldquoMove Java Databaserdquo for a central system
ldquoMove Java Databaserdquo for a distributed system or a high-availability system
ldquoKeep Databaserdquo for a central distributed or high-availability system
NOTE
Some of the follow-up activities listed in this section are not described in this documentation You
can find the detailed description in the SAP NetWeaver Application Server Java system copy
documentation relevant for your release at
httpservicesapcominstguides
Move Java Database
Central System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3354
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
7 We recommend that you perform regression testing
8 On the source system you run SAPinst [page 23] to remove the Java parts in the file system and in
the database
9 On the source system you call transaction RZ10 to reimport the profiles from the file system
10 In the Transport Management System (TMS) you configure the transport routes [page 38]
11 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
12 You clean up the system landscape data [page 40]
Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3454 PUBLIC 2012-04-11
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the database host of the source system you run SAPinst [page 23] to remove the Java database
schema
12 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
13 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
14 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
15 You clean up the system landscape data [page 40]
Keep Database
Central Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3554
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
12 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
13 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
14 You clean up the system landscape data [page 40]
62 Maintaining the Connection to the System Landscape Directory
After installing the Java system you need to reconfigure the connection between the System Landscape
Directory (SLD) the source system and the target system The steps required differ depending on
whether you use a local or a central SLD To maintain the connection to the SLD you can either run
the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split or perform the required steps manually as described below
NOTE
This step is only required if the connection to the SLD was established on the source system before
the split
Prerequisites
If you want to use the configuration wizard you need an SAP NetWeaver Java system 70 Support
Package 14 or higher in your landscape
SLDAPIUSER credentials are available in the ABAP system
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3654 PUBLIC 2012-04-11
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
When the split option has finished successfully SAPinst displays the message Execution of
ltOption_Namegt has completed
Only valid for Oracle |
NOTE
When installing the Oracle database instance SAPinst stops the installation and prompts
you to install the Oracle database software For more information see Installing the Oracle
Database Software in the installation documentation of your release
After you have finished the installation of the Oracle database you continue the database
instance installation by choosing OK in the GUI of the database instance installation
Check SAP Note 1431800 for technical information about Oracle Release 112 in SAP
environments
End of Oracle |
Only valid for Enterprise Portal (EP) |
NOTE
During the final restart of Application Server Java performed by SAPinst the portal starts the
processing and uploading of the new portal archives It takes approximately 15 to 90 minutes
before the deployment is completed and the portal is launched
Do not stop SAPinst or Application Server Java during this phase
End of Enterprise Portal (EP) |
9 If required delete directories with the name sapinst_exexxxxxxxxxx after SAPinst has finished
Sometimes these remain in the temporary directory
NOTE
If there are errors with the SAPinst extraction process you can find the log file
dev_selfexout in the temporary directory
Only valid for Non-Standalone Engines and Clients |
RECOMMENDATION
Keep all installation 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 installation 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 installation directories on installation hosts but make sure
that you delete them after saving them separately
End of Non-Standalone Engines and Clients |
10 We recommend that you delete the directory ltuser_homegtsdtgui
11 Only valid for IBM DB2 for Linux and UNIX and Windows |
If not already done install the DB2 license
5 Splitting
52 Running SAPinst
3054 PUBLIC 2012-04-11
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
End of IBM DB2 for Linux and UNIX and Windows |
12 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 3154
This page is left blank for documents that are printed on both sides
6 Follow-Up Activities
61 Follow-Up Activities Checklist
This section includes the follow-up activities that you have to perform for the following split options
ldquoMove Java Databaserdquo for a central system
ldquoMove Java Databaserdquo for a distributed system or a high-availability system
ldquoKeep Databaserdquo for a central distributed or high-availability system
NOTE
Some of the follow-up activities listed in this section are not described in this documentation You
can find the detailed description in the SAP NetWeaver Application Server Java system copy
documentation relevant for your release at
httpservicesapcominstguides
Move Java Database
Central System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3354
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
7 We recommend that you perform regression testing
8 On the source system you run SAPinst [page 23] to remove the Java parts in the file system and in
the database
9 On the source system you call transaction RZ10 to reimport the profiles from the file system
10 In the Transport Management System (TMS) you configure the transport routes [page 38]
11 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
12 You clean up the system landscape data [page 40]
Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3454 PUBLIC 2012-04-11
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the database host of the source system you run SAPinst [page 23] to remove the Java database
schema
12 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
13 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
14 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
15 You clean up the system landscape data [page 40]
Keep Database
Central Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3554
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
12 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
13 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
14 You clean up the system landscape data [page 40]
62 Maintaining the Connection to the System Landscape Directory
After installing the Java system you need to reconfigure the connection between the System Landscape
Directory (SLD) the source system and the target system The steps required differ depending on
whether you use a local or a central SLD To maintain the connection to the SLD you can either run
the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split or perform the required steps manually as described below
NOTE
This step is only required if the connection to the SLD was established on the source system before
the split
Prerequisites
If you want to use the configuration wizard you need an SAP NetWeaver Java system 70 Support
Package 14 or higher in your landscape
SLDAPIUSER credentials are available in the ABAP system
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3654 PUBLIC 2012-04-11
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
End of IBM DB2 for Linux and UNIX and Windows |
12 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running SAPinst
2012-04-11 PUBLIC 3154
This page is left blank for documents that are printed on both sides
6 Follow-Up Activities
61 Follow-Up Activities Checklist
This section includes the follow-up activities that you have to perform for the following split options
ldquoMove Java Databaserdquo for a central system
ldquoMove Java Databaserdquo for a distributed system or a high-availability system
ldquoKeep Databaserdquo for a central distributed or high-availability system
NOTE
Some of the follow-up activities listed in this section are not described in this documentation You
can find the detailed description in the SAP NetWeaver Application Server Java system copy
documentation relevant for your release at
httpservicesapcominstguides
Move Java Database
Central System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3354
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
7 We recommend that you perform regression testing
8 On the source system you run SAPinst [page 23] to remove the Java parts in the file system and in
the database
9 On the source system you call transaction RZ10 to reimport the profiles from the file system
10 In the Transport Management System (TMS) you configure the transport routes [page 38]
11 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
12 You clean up the system landscape data [page 40]
Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3454 PUBLIC 2012-04-11
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the database host of the source system you run SAPinst [page 23] to remove the Java database
schema
12 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
13 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
14 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
15 You clean up the system landscape data [page 40]
Keep Database
Central Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3554
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
12 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
13 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
14 You clean up the system landscape data [page 40]
62 Maintaining the Connection to the System Landscape Directory
After installing the Java system you need to reconfigure the connection between the System Landscape
Directory (SLD) the source system and the target system The steps required differ depending on
whether you use a local or a central SLD To maintain the connection to the SLD you can either run
the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split or perform the required steps manually as described below
NOTE
This step is only required if the connection to the SLD was established on the source system before
the split
Prerequisites
If you want to use the configuration wizard you need an SAP NetWeaver Java system 70 Support
Package 14 or higher in your landscape
SLDAPIUSER credentials are available in the ABAP system
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3654 PUBLIC 2012-04-11
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
This page is left blank for documents that are printed on both sides
6 Follow-Up Activities
61 Follow-Up Activities Checklist
This section includes the follow-up activities that you have to perform for the following split options
ldquoMove Java Databaserdquo for a central system
ldquoMove Java Databaserdquo for a distributed system or a high-availability system
ldquoKeep Databaserdquo for a central distributed or high-availability system
NOTE
Some of the follow-up activities listed in this section are not described in this documentation You
can find the detailed description in the SAP NetWeaver Application Server Java system copy
documentation relevant for your release at
httpservicesapcominstguides
Move Java Database
Central System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3354
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
7 We recommend that you perform regression testing
8 On the source system you run SAPinst [page 23] to remove the Java parts in the file system and in
the database
9 On the source system you call transaction RZ10 to reimport the profiles from the file system
10 In the Transport Management System (TMS) you configure the transport routes [page 38]
11 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
12 You clean up the system landscape data [page 40]
Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3454 PUBLIC 2012-04-11
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the database host of the source system you run SAPinst [page 23] to remove the Java database
schema
12 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
13 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
14 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
15 You clean up the system landscape data [page 40]
Keep Database
Central Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3554
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
12 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
13 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
14 You clean up the system landscape data [page 40]
62 Maintaining the Connection to the System Landscape Directory
After installing the Java system you need to reconfigure the connection between the System Landscape
Directory (SLD) the source system and the target system The steps required differ depending on
whether you use a local or a central SLD To maintain the connection to the SLD you can either run
the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split or perform the required steps manually as described below
NOTE
This step is only required if the connection to the SLD was established on the source system before
the split
Prerequisites
If you want to use the configuration wizard you need an SAP NetWeaver Java system 70 Support
Package 14 or higher in your landscape
SLDAPIUSER credentials are available in the ABAP system
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3654 PUBLIC 2012-04-11
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
6 Follow-Up Activities
61 Follow-Up Activities Checklist
This section includes the follow-up activities that you have to perform for the following split options
ldquoMove Java Databaserdquo for a central system
ldquoMove Java Databaserdquo for a distributed system or a high-availability system
ldquoKeep Databaserdquo for a central distributed or high-availability system
NOTE
Some of the follow-up activities listed in this section are not described in this documentation You
can find the detailed description in the SAP NetWeaver Application Server Java system copy
documentation relevant for your release at
httpservicesapcominstguides
Move Java Database
Central System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3354
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
7 We recommend that you perform regression testing
8 On the source system you run SAPinst [page 23] to remove the Java parts in the file system and in
the database
9 On the source system you call transaction RZ10 to reimport the profiles from the file system
10 In the Transport Management System (TMS) you configure the transport routes [page 38]
11 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
12 You clean up the system landscape data [page 40]
Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3454 PUBLIC 2012-04-11
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the database host of the source system you run SAPinst [page 23] to remove the Java database
schema
12 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
13 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
14 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
15 You clean up the system landscape data [page 40]
Keep Database
Central Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3554
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
12 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
13 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
14 You clean up the system landscape data [page 40]
62 Maintaining the Connection to the System Landscape Directory
After installing the Java system you need to reconfigure the connection between the System Landscape
Directory (SLD) the source system and the target system The steps required differ depending on
whether you use a local or a central SLD To maintain the connection to the SLD you can either run
the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split or perform the required steps manually as described below
NOTE
This step is only required if the connection to the SLD was established on the source system before
the split
Prerequisites
If you want to use the configuration wizard you need an SAP NetWeaver Java system 70 Support
Package 14 or higher in your landscape
SLDAPIUSER credentials are available in the ABAP system
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3654 PUBLIC 2012-04-11
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
7 We recommend that you perform regression testing
8 On the source system you run SAPinst [page 23] to remove the Java parts in the file system and in
the database
9 On the source system you call transaction RZ10 to reimport the profiles from the file system
10 In the Transport Management System (TMS) you configure the transport routes [page 38]
11 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
12 You clean up the system landscape data [page 40]
Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3454 PUBLIC 2012-04-11
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the database host of the source system you run SAPinst [page 23] to remove the Java database
schema
12 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
13 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
14 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
15 You clean up the system landscape data [page 40]
Keep Database
Central Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3554
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
12 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
13 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
14 You clean up the system landscape data [page 40]
62 Maintaining the Connection to the System Landscape Directory
After installing the Java system you need to reconfigure the connection between the System Landscape
Directory (SLD) the source system and the target system The steps required differ depending on
whether you use a local or a central SLD To maintain the connection to the SLD you can either run
the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split or perform the required steps manually as described below
NOTE
This step is only required if the connection to the SLD was established on the source system before
the split
Prerequisites
If you want to use the configuration wizard you need an SAP NetWeaver Java system 70 Support
Package 14 or higher in your landscape
SLDAPIUSER credentials are available in the ABAP system
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3654 PUBLIC 2012-04-11
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the database host of the source system you run SAPinst [page 23] to remove the Java database
schema
12 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
13 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
14 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
15 You clean up the system landscape data [page 40]
Keep Database
Central Distributed or High-Availability System
1 On the Java target system you change the Java VM parameters as described in SAP Note 723909
if necessary
2 On the Java target system you install the SAP license
For more information see Installing the License Key in the system copy documentation of your release
3 On the Java target system you maintain the connection to the system landscape directory [page 36]
4 On the Java target system you generate the public-key certificates
For more information see Generating Public-Key Certificates in the system copy documentation of your
release
5 Only valid for IBM DB2 for Linux and UNIX and Windows |
On the Java target system you enable the recoverability of the database
For more information see Enabling Recoverability of the Database in the system copy documentation of
your releaseEnd of IBM DB2 for Linux and UNIX and Windows |
6 On the Java target system you perform usage type and software unit-specific follow-up activities
as required
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-04-11 PUBLIC 3554
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
12 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
13 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
14 You clean up the system landscape data [page 40]
62 Maintaining the Connection to the System Landscape Directory
After installing the Java system you need to reconfigure the connection between the System Landscape
Directory (SLD) the source system and the target system The steps required differ depending on
whether you use a local or a central SLD To maintain the connection to the SLD you can either run
the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split or perform the required steps manually as described below
NOTE
This step is only required if the connection to the SLD was established on the source system before
the split
Prerequisites
If you want to use the configuration wizard you need an SAP NetWeaver Java system 70 Support
Package 14 or higher in your landscape
SLDAPIUSER credentials are available in the ABAP system
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3654 PUBLIC 2012-04-11
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
As of SAP NetWeaver 70 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 BI Java usage type
For more information see the SAP Library [page 7] of your release at
Technology Consultants Guide Enterprise Reporting Query and Analysis Wizard-Based Configuration of
BI Java
For more information see the relevant sections in the usage type and software unit-specific follow-
up activities in the system copy documentation of your release
7 We recommend that you perform regression testing
8 On the central instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run SAPinst [page 23] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run SAPinst [page 23] to remove
the central services instance
11 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
12 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
13 If required and not already done so you configure the CTS Deploy Web Service [page 39] on the ABAP
system
14 You clean up the system landscape data [page 40]
62 Maintaining the Connection to the System Landscape Directory
After installing the Java system you need to reconfigure the connection between the System Landscape
Directory (SLD) the source system and the target system The steps required differ depending on
whether you use a local or a central SLD To maintain the connection to the SLD you can either run
the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split or perform the required steps manually as described below
NOTE
This step is only required if the connection to the SLD was established on the source system before
the split
Prerequisites
If you want to use the configuration wizard you need an SAP NetWeaver Java system 70 Support
Package 14 or higher in your landscape
SLDAPIUSER credentials are available in the ABAP system
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3654 PUBLIC 2012-04-11
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
Procedure
Using the Configuration Wizard
To run the wizard-based configuration task System Landscape Directory Setup After Dual-Stack
Split using the configuration wizard proceed as described in the SAP Library [page 7] at
SAP NetWeaver 70
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 1
Technology Consultants Guide Developing Configuring and Adapting Applications Creating Java Applications
Using Web Dynpro J2EE Engine Configuration Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 2
Technology Consultants Guide Configuration Wizard
SAP NetWeaver 70 including Enhancement Package 3
Technology Consultants Guide Configuration Wizard
Performing Manual Steps
If you do not want to use the configuration wizard you have to perform the following steps manually
according to your requirements
For more information about how to perform the individual tasks see the relevant sections in the System
Landscape Directory ndash User Manual and the System Landscape Directory ndash Post-Installation Guide relevant for your
release level at
httpsdnsapcomirjsdnnw-sld
Local SLD
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Configure the SLD Server
For more information see Configuring Server and Persistence Parameters in the post-installation guide
3 Configure the ABAP gateway in the SLD
For more information see Configuring the SLD Bridge
4 Maintain the connection between the ABAP system and the SLD
1 Configure the SLD Data Supplier Service
For more information see Configuring the SLD Data Supplier Default Settings in the user manual
2 Maintain the RFC destination
For more information see Creating an RFC Destination for the SLD ABAP API on the J2EE Side in the
user manual
3 Maintain the HTTP connection parameters on the ABAP system
For more information see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side in
the user manual
5 Maintain the connection between the Java system and the SLD
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-04-11 PUBLIC 3754
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
Central SLD
The following steps are described in the System Landscape Directory post-installation guide
1 Create users groups and roles
For more information see Configuring SLD User Authorizations in the post-installation guide
2 Maintain the connection between the Java system and the SLD
1 Configure the SLD Data Supplier Service in the Visual Administrator
For more information see Setting Up the SLD Data Supplier for J2EE-Based Systems in the user manual
2 Generate a CIM client for accessing the SLD
For more information see Configuring the Interface for CIM Client Generation in the user manual
63 Configuring Transport Routes
If your dual-stack system is not a single system but part of a transport landscape you need to reconfigure
the transport routes within the landscape after installing the Java system
The steps that you have to perform differ depending on the position of the split system within the
transport landscape
Procedure
First System in the Transport Queue
1 In the Transport Management System (TMS) create a Java system with the ABAP system of the
former dual-stack system as communication system and select the Activate Transport Organizer flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 Delete the configuration settings of the Java system in the ABAP system in the TMS
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
3 In the TMS create the transport route between the new Java system and the next system in the
transport queue
6 Follow-Up Activities
63 Configuring Transport Routes
3854 PUBLIC 2012-04-11
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
Subsequent System in the Transport Queue
1 In the TMS create a Java system with the ABAP system of the former dual-stack system as
communication system and select the Activate Deployment Service flag
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Change and Transport System - Overview (BC-CTS) Transporting Non-ABAP
Objects in Change and Transport System Performing Configuration Steps for Non-ABAP Transports Defining and
Configuring Non-ABAP Systems
2 In the ABAP system configure the CTS Deploy Web Service [page 39]
3 In the TMS delete the configuration settings of the Java system in the ABAP system
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Performing Configuration Steps
for Non-ABAP Transports Defining and Configuring Non-ABAP Systems
4 Copy the import buffer of the ABAP system to the Java system This ensures the processing of
pending transport queues
5 In the TMS create the transport routes between the previous Java system in the transport queue
and the new Java system and between the new Java system and the next system in the transport
queue
For more information see the SAP Library [page 7] of your release at SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics
Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS
Configuring the Transport Routes
More Information
Splitting Within a System Landscape [page 43]
64 Configuring the CTS Deploy Web Service
After installing the Java system you need to reconfigure the CTS Deploy Web Service
This step is only required if you used the enhanced Change and Transport System as transport tool in
your dual-stack system before the split or if the split system is a subsequent system in the transport
queue
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
2012-04-11 PUBLIC 3954
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
Procedure
1 In your ABAP system in the client that you use for transports call transaction SM59
2 Under HTTP Connections to External Server select the HTTP connection that you used in the dual-stack
system and choose Display
3 Choose the Technical Settings tab page
1 Enter the name of the host of your Java system and under Service Number enter the port of your
system where the CTS Deploy Web Service runs (5ltSAP System Numbergt00) Ensure that the
path prefix is entered and confirm your entries with Enter
2 If you encounter warnings about invalid query strings or missing documentation ignore them
by choosing Enter
3 Save your entries
4 Choose the Logon amp Security tab page
1 Select Basic Authentication as logon procedure
2 Enter a user and password that is recognized on the system where the Deploy Web Service is
running
3 Save your entries
5 To test the new HTTP connection choose Connection Test
6 Choose Continue to confirm If you have created the new HTTP connection successfully the status
text in the test results is set to OK
65 Cleaning Up the System Landscape
To ensure data consistency for future maintenance you have to clean up system landscape data first
in the SLD and second in SMSY respectively LMDB in the SAP Solution Manager
Make sure that the entries for the removed Java stack are no longer part of the former dual-stack system
in SLD and SMSY respectively LMDB
For more information about how to proceed see
httpservicesapcomsolutionmanager
6 Follow-Up Activities
65 Cleaning Up the System Landscape
4054 PUBLIC 2012-04-11
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
7 Additional Information
71 Troubleshooting with SAPinst
This section describes the steps that you need to perform manually if SAPinst fails
NOTE
If you cannot resolve the problem create a customer message using component BC-INS For more
information about using subcomponents of BC-INS see SAP Note 1669327
Procedure
Dialog Phase
If an error occurs during the dialog phase SAPinst stops and displays a dialog that informs you about
the error
You can now
View the log file directly by choosing View Logs
Try to solve the problem
Stop the process by choosing Cancel in the SAPinst menu
For more information see section Interrupted Installation with SAPinst in the installation documentation
of your SAP product
After resolving the problem you can continue by choosing Retry
Processing Phase
If the export process aborts during the processing 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
1 Remove the ltpackagegtltnnngt dump files the ltpackagegtTOC file and the ltpackagegtlog file
2 Make sure that all tables in the ltpackagegtTSK file have the status flag xeq or err set
3 Repeat the export of the complete package
System Copy ndash export on UNIX (especially for upgraded systems)
Symptom
Processes started as ltsapsidgtadm or oraltsidgt OS users cannot create or open files in the installation
directory
Reason
Only members of sapinst UNIX group can access the installation directory This group is created by
SAPinst as of SAP NetWeaver 70 SR1
7 Additional Information
71 Troubleshooting with SAPinst
2012-04-11 PUBLIC 4154
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
Solution
1 Manually associate ltsapsidgtadm and oraltsidgt OS users with sapinst group if this association is
missing
2 Verify the etcgroup file and check if the sapinst group exists and OS users are members of this
group
3 If the sapinst group does not exist yet start SAPinst SAPinst creates this group during startup
before the product catalog list is displayed
4 Edit etcgroup file and associate OS users with sapinst group
5 Continue with the export
72 Move Java Database Restarting Instances
If you encounter severe problems during the split and decide to stop it you can use the source system
as a dual-stack system again You then have to restart all instances of the source system
NOTE
This is only possible if you have not yet removed the Java stack of the dual-stack source system
Procedure
1 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
2 Restart the central instance service
Log on to the system as ltsidgtadm and invoke sapcontrol-nr ltCI instance numbergt-function
RestartService
3 Restart the instance by calling transaction SMICM
73 Keep Database Restarting Instances
If you encounter severe problems during the split and decide to stop you can use the source system as
a dual-stack system again if you made a backup of your source database before the split You then have
to restart all instances of the source system
NOTE
This is possible only if you have not yet removed the Java stack of the dual-stack source system
Prerequisites
A backup of your source database is available
Procedure
1 Reimport your source database
7 Additional Information
72 Move Java Database Restarting Instances
4254 PUBLIC 2012-04-11
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
2 Edit the central instance profile ltSIDgt_DVEBMGSltXXgt_lthostnamegt Replace the line rdisp
j2ee_start=0 with rdispj2ee_start=1
3 Restart the central instance service
Log on to the central instance host as ltsidgtadm and invoke sapcontrol-nr ltCI instance
numbergt-function RestartService
4 Restart the instance by calling transaction SMICM
74 Splitting Within a System Landscape
Since an SAP system is usually part of a system landscape dependencies between systems and adapting
transport routes within the system landscape are topics to consider when planning a dual-stack split
This section provides information for planning the dual-stack split within an exemplary system
landscape composed of a development system (DEV) a test system (QAS) and a productive system
(PRD) and it lists the required steps for adapting the transport routes
Figure 5 System Landscape Before Split
Process Flow
1 You split the first system in the transport queue
In this example this means that you split the dual-stack system DEV into an ABAP system DEV
and a Java system JDS
2 In the Transport Management System (TMS) you create a Java system (JDS) with the ABAP system
(DEV) as communication system and select the Activate Transport Organizer flag
3 In the TMS you delete the configuration settings of the Java system in the ABAP system (DEV)
4 In the TMS you create the transport route between the new Java system (JDS) and the next system
in the transport queue (QAS)
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4354
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
Figure 6 System Landscape After the First Split with Adapted Transport Routes
5 You split the next system in the transport queue
In this example this means that you split the dual-stack system QAS into an ABAP system QAS
and a Java system JQS
6 In the TMS you create a Java system (JQS) with the ABAP system (QAS) as communication system
and select the Activate Deployment Service flag
7 In the ABAP system (QAS) you configure the CTS Deploy Web Service [page 39]
8 In the TMS you delete the configuration settings of the Java system in the ABAP system (QAS)
9 You copy the import buffer of the ABAP system (QAS) to the Java system (JQS) This ensures the
processing of pending transport queues
10 In the TMS you create the transport routes between the previous Java system in the transport
queue (JDS) and the new Java system (JQS) and between JQS and the next system in the transport
queue (PRD)
7 Additional Information
74 Splitting Within a System Landscape
4454 PUBLIC 2012-04-11
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
Figure 7 System Landscape After the Second Split with Adapted Transport Routes
11 You split the next system in the transport queue
In this example this means that you split the last dual-stack system in the transport queue PRD
into an ABAP system PRD and a Java system JPS
12 In the TMS you create a Java system (JPS) with the ABAP system (PRD) as communication system
and select the Activate Deployment Service flag
13 In the ABAP system (PRD) you configure the CTS Deploy Web Service [page 39]
14 In the TMS you delete the configuration settings of the Java system in the ABAP system (PRD)
15 You copy the import buffer of the ABAP system (PRD) to the Java system (JPS) This ensures the
processing of pending transport queues
16 In the TMS you create the transport route between the new Java system (JPS) and the Java system
preceding in the transport queue (JQS)
Figure 8 System Landscape After the Last Split with Adapted Transport Routes
7 Additional Information
74 Splitting Within a System Landscape
2012-04-11 PUBLIC 4554
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
75 Removing the Java Stack
If you no longer need the Java stack of your dual-stack system you can remove it using the Dual-Stack
Split 20 Tool
Using this procedure you will permanently delete the Java stack from the system
NOTE
During the removal process all Java database content all Java file systems and subdirectories of
the Java stack are deleted Before you start make sure that you have saved a copy of all files and
directories that you want to keep to a secure location
Procedure
1 Start SAPinst and choose split option Keep Database as described in Running SAPinst [page 23]
2 Perform the following steps
Remove Java Stack from Dual-Stack Central Instance
Remove SCS Instance from Dual-Stack System
CAUTION
You must skip the export and installation steps as well as the step for adapting the database
for the target system
3 After you remove the Java stack you have to remove the Java stack data from the SLD transaction
SMSY and LMDB in the SAP Solution Manager
The removal of the technical Java system from the SLD is important for the system landscape data
consistency
For more information see httpservice sapcomsolutionmanager
7 Additional Information
75 Removing the Java Stack
4654 PUBLIC 2012-04-11
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
A Appendix
A1 Online Information from SAP
More information is available online as follows
Only valid for SAP Solution Manager |
NOTE
Before you continue to read this installation guide you must have read the Master Guide Having
finished the installation and the required post-installation steps you have to follow the
instructions in the configuration guide The configuration guide also points you to further
documentation that might be relevant for you
End of SAP Solution Manager |
Only valid for SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
Documentation
Description Internet Address Title
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcomoperationsnw70
Database-Specific GuidesDatabase Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP DBA Guide DB2 for zOS
SAP Planning Guide for SAP NetWeaver for IBM DB2 for zOS
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Planning Guide DB2 for zOS
SAP Security Guide for IBM DB2 for zOS (was formerly part of the SAP Planning Guide DB2 for zOS)
httpservicesapcom OperationsNW70
Database-Specific GuidesSAP Security Guide for IBM DB2 for zOS
Installation of sapccmsr to connect saposcol to SAP application server
httpservicesapcomOperationsnw70
MonitoringMonitoring Setup Guide for NW ltversiongt
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpwwwsdnsapcomirjsdndbos
Multiple Components in One Database (MCOD)Multiple Components in One Database (MCOD)
A Appendix
A1 Online Information from SAP
2012-04-11 PUBLIC 4754
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
Description Internet Address Title
Homogeneous and heterogeneous system copy
Only valid for SAP ERP |
httpservicesapcom erp-inst SAP ERP 60 SAP enhancement package 6 for SAP ERP 60 End of SAP ERP |
Only valid for SAP CRM |
httpservicesapcom crm-inst SAP enhancement package 2 for SAP CRM 70 End of SAP CRM |
Only valid for SAP SRM |
httpservicesapcom srm-inst SAP SRM Server 702 End of SAP SRM |
Only valid for SAP SCM |
httpservicesapcom instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 70 End of SAP SCM |
System Copy Guide ndash System Copy for SAP Systems based on SAP NetWeaver 70 including Enhancement Package 3 ltTechnologygt
End of SAP CRMSAP ERPSAP NetWeaverSAP SCMSAP SRM |
General Quick Links
Description Internet Address
SAP on DB2 for zOS httpwwwsdnsapcomirjsdndb2
SAP Help Portal httphelpsapcom
SAP NetWeaver Library in SAP Help Portal
httphelpsapcomnetweaver
SAP ERP Library in SAP Help Portal httphelpsapcomerp
SAP CRM Library in SAP Help Portal
httphelpsapcomcrm
SAP SRM Library in SAP Help Portal
httphelpsapcomsrm
SAP SCM Library in SAP Help Portal
httphelpsapcomscm
SAP Notes httpservicesapcomnotes
Forums blogs and general information related to all of the supported databases and operating system platforms
httpsdnsapcomirjsdndbos
Product Availability Matrix (PAM) for supported operating system releases
httpservicesapcompam
General information forums and blogs about information related to SAP on Linux
httpsdnsapcomirjsdnlinux
Release notes httpservicesapcomreleasenotes
A Appendix
A1 Online Information from SAP
4854 PUBLIC 2012-04-11
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
Description Internet Address
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver
Life-cycle management for SAP NetWeaver
httpsdnsapcomirjsdnlcm
Landscape design for SAP NetWeaver
httpsdnsapcomirjsdnlandscapedesign
Application management for SAP NetWeaver
httpsdnsapcomirjsdnapplicationmanagement
High Availability httpsdnsapcomirjsdnha
System Landscape Directory httpsdnsapcomirjsdnnw-sld
Software logistics for SAP NetWeaver
httpsdnsapcomirjsdnsoftwarelogistics
SAP NetWeaver operations httpsdnsapcomirjsdnoperations
SAP NetWeaver Development Infrastructure
httpsdnsapcomirjsdnnw-di
Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
End-to-End Root Cause Analysis httpservicesapcomdiagnostics
Only valid for IBM DB2 for Linux and UNIX and Windows |
A2 Online Information from IBM
The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your database
IBM Manuals
Database Version Internet Address
DB2 V97 httpwww-01ibmcomsupport docviewwssrs=71ampuid=swg27015148
IBM DB2 Information Center
Database Version Internet Address
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
A Appendix
A2 Online Information from IBM
2012-04-11 PUBLIC 4954
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
More Information
For more information about web sites that contain important DB2-related documentation see SAP
Note 690471End of IBM DB2 for Linux and UNIX and Windows |
A Appendix
A2 Online Information from IBM
5054 PUBLIC 2012-04-11
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2012-04-11 PUBLIC 5154
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company
5254 PUBLIC 2012-04-11
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-04-11 PUBLIC 5354
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- Dual-Stack Split for SAP NetWeaver ABAP+Java Systems on UNIX
-
- Table of Contents
- 1 Introduction
-
- 11 SAP Notes for the Dual-Stack Split
- 12 Accessing the SAP Library
- 13 How to Use this Guide
-
- 2 Split Options Covered by this Guide
-
- 21 Split Option Move Java Database
- 22 Split Option Keep Database
-
- 3 Planning
-
- 31 Planning Checklist
- 32 User Management
-
- 4 Preparation
-
- 41 Preparation Checklist
- 42 Performing a Full System Backup
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running SAPinst
-
- 6 Follow-Up Activities
-
- 61 Follow-Up Activities Checklist
- 62 Maintaining the Connection to the System Landscape Directory
- 63 Configuring Transport Routes
- 64 Configuring the CTS Deploy Web Service
- 65 Cleaning Up the System Landscape
-
- 7 Additional Information
-
- 71 Troubleshooting with SAPinst
- 72 Move Java Database Restarting Instances
- 73 Keep Database Restarting Instances
- 74 Splitting Within a System Landscape
- 75 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-