NW Dual Stack Split guide
-
Upload
gangadhar39 -
Category
Documents
-
view
329 -
download
0
description
Transcript of NW Dual Stack Split guide
Dual-Stack Split GuideDual-Stack Split for SAP NetWeaver ABAP+Java Systems on WindowsUsing the Dual-Stack Split Tool 20
Target Audience System administrators Technology consultants
CUSTOMERDocument version 10 ndash 2012-11-27
Document History
The following table provides an overview of the most important document changes
Version Date Description
12 2012-11-27 Updated version ndash SL Toolset SP06
11 2012-09-26 Updated version
10 2012-08-06 Initial version
260 CUSTOMER 2012-11-27
Table of Contents
Chapter 1 Introduction 5
11 SAP Notes for the Dual-Stack Split 7
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 12
Chapter 3 Planning 17
31 Planning Checklist 17
32 User Management 19
Chapter 4 Preparation 21
41 Preparation Checklist 21
42 Performing a Full System Backup 22
43 Preparing the Dual Stack Split Installation Media 25
Chapter 5 Splitting 27
51 Splitting Checklist 27
52 Running the Installer 29
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 40
65 Cleaning Up the System Landscape 40
Chapter 7 Additional Information 43
71 Troubleshooting 43
72 Additional Information About the Installer 43
2012-11-27 CUSTOMER 360
721 Performing a Remote Installation with the Installer 43
722 Starting the Installer GUI Separately 45
73 Move Java Database Restarting Instances 48
74 Keep Database Restarting Instances 48
75 Splitting Within a System Landscape 49
76 Removing the Java Stack 51
Chapter A Appendix 53
A1 Online Information from SAP 53
A2 Online Information from IBM 55
460 CUSTOMER 2012-11-27
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 You can also use the Dual-Stack
Split 20 tool to remove the Java stack of your SAP dual-stack system
This tool is part of the installation tool and it mainly uses the Java system copy functionality It is
delivered as part of Software Logistics Toolset (SL Toolset) 10 SPS 06
The split procedure is valid for optional dual-stack SAP NetWeaver systems (such as SAP NetWeaver
BW systems with SAP BEx Web) and dual-stack SAP Business Suite systems based on the following SAP
NetWeaver releases
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
NOTE
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 49]
For more information about Dual-Stack Split see httpscnsapcomdocsDOC-25162
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 12])
1 Introduction
2012-11-27 CUSTOMER 560
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-
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 strongly
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
SAP NetWeaver 74
For more information see SAP Note 1655335
If you no longer need the Java stack of your SAP dual-stack system you can use the Dual-Stack
Split 20 tool to remove it as described in Removing the Java Stack [page 51]
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
Heterogeneous 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 media 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
Sybase Split option ldquoKeep Databaserdquo is not supported Only the steps valid for option ldquoMove Java
Databaserdquo are available in the installation tool
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
1 Introduction
660 CUSTOMER 2012-11-27
Only valid for Microsoft Failover Clustering As of Windows Server 2008 the cluster feature is
called Failover Clustering For practical reasons we are continuing to use the previous terminology
Microsoft Cluster Service and abbreviation MSCS in some sections of this guide and the corresponding
installation documentation of your release
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
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
1769205 Dual-Stack Split 20 SP3 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 ltLanguagegt SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 1
httphelpsapcomnw701 Application Help SAP Library ltLanguagegt SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 2
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 3
httphelpsapcomnw703 Application Help SAP Library ltLanguagegt 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
1 Introduction
11 SAP Notes for the Dual-Stack Split
2012-11-27 CUSTOMER 760
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
CAUTION
Sybase Only the functionality of split option ldquoMove Java Databaserdquo is supported
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 17]
Preparation [page 21]
Splitting [page 27]
Follow-up Activities [page 33]
1 Introduction
13 How to Use this Guide
860 CUSTOMER 2012-11-27
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
CAUTION
Sybase Only the functionality of split option ldquoMove Java Databaserdquo is supported
Move Java Database [page 9]
Keep Database [page 12]
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)
Only valid for Microsoft Failover Clustering If your system is a high-availability system with
Microsoft Failover Clustering (previously known as MSCS) the split option ldquoMove Java Databaserdquo offers
the possibility to split a clustered dual-stack system into one ABAP cluster system and one Java cluster
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 the installer 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 the
installer removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
2012-11-27 CUSTOMER 960
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 the installer 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 the
installer removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
1060 CUSTOMER 2012-11-27
Figure 2 Split Option Move Java Database for Distributed System
Move Java Database for High-Availability Systems
When you choose the ldquoMove Java Databaserdquo option for a high-availability system the installer exports
the Java stack of the dual-stack cluster system and uses this export to reinstall all mandatory instances
on a separate cluster system for Java
These are the mandatory instances
Central services instance for Java (SCS)
Enqueue replication server instance (ERS instance) for the SCS instance
Database instance (DB)
Central instance
Dialog instance
After the installation has finished and the System Landscape Directory has been reconfigured the
installer removes all Java parts from the dual-stack cluster system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
2012-11-27 CUSTOMER 1160
Figure 3 Split Option Move Java Database for High-Availability System
22 Split Option Keep Database
CAUTION
Sybase The functionality of split option ldquoKeep Databaserdquo is not supported
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)
Only valid for Microsoft Failover Clustering If your system is a high-availability system with
Microsoft Failover Clustering (MSCS) the split option ldquoKeep Databaserdquo offers the possibility to split a
clustered dual-stack system into one ABAP cluster system and one Java cluster system both using the
same database (MCOD)
Keep Database for Central and Distributed Systems
When you choose the ldquoKeep Databaserdquo option the installer 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 the installer 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 the
installer 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
1260 CUSTOMER 2012-11-27
Figure 4 Split Option Keep Database for Central Systems
Figure 5 Split Option Keep Database for Distributed Systems
Keep Database for High-Availability Systems
When you choose the ldquoKeep Databaserdquo option for a high-availability system you can choose between
the following scenarios
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-11-27 CUSTOMER 1360
Move SCS to New or Other Cluster
The installer exports the Java stack of the dual-stack cluster system and uses this export to install
a central services instance and a central instance on a separate cluster system for Java Additionally
the installer adapts the Java schema of the database of the former dual-stack cluster system to the
target Java cluster system
Figure 6 Split Option Keep Database for High-Availability Systems mdash Move SCS to New or Other
Cluster
Keep SCS on the Source Cluster System
The installer exports the Java central services instance of the source cluster system and uses this
export to install the SCS with a new system ID in a separate cluster on the target cluster system
Additionally the installer adapts the Java schema of the database to the target Java SID
NOTE
This scenario is supported as of Windows Server 2008
2 Split Options Covered by this Guide
22 Split Option Keep Database
1460 CUSTOMER 2012-11-27
Figure 7 Split Option Keep Database for High-Availability Systems mdash Keep SCS on the Source
Cluster System
After the installation has finished and the System Landscape Directory has been reconfigured the
installer removes all Java parts from the dual-stack cluster system except the Java database schema
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-11-27 CUSTOMER 1560
This page is left blank for documents that are printed on both sides
3 Planning
31 Planning Checklist
RECOMMENDATION
We recommend that you first perform the dual-stack split procedure in a test system to identify
possible further application-specific post-split activities required for your scenario
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 19]
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 19]
System Landscape Directory (SLD)
You can ignore SLD parameters
Oracle SAP System Database Parameters Java database schema
3 Planning
31 Planning Checklist
2012-11-27 CUSTOMER 1760
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
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 administrator
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
5 MS SQL Server Oracle For the database installation you decide how to distribute your database
components to disk
For more information see Distribution of SAP System Components to Disk in the installation documentation
of your release
6 SAP MaxDB For the database installation you decide how to distribute your system components
to disk
For more information see Distribution of SAP System Components to Disk in the installation documentation
of your release
7 IBM DB2 for Linux 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 release
8 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
9 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 49]
10 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
11 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
12 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
13 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
14 You can continue with Preparation [page 21]
Split Option ldquoKeep Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
CAUTION
Sybase Split option ldquoKeep Databaserdquo is not supported
3 Planning
31 Planning Checklist
1860 CUSTOMER 2012-11-27
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 19]
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 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 19]
System Landscape Directory (SLD)
You can ignore SLD parameters
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
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 49]
7 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
8 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
9 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
10 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
11 You can continue with Preparation [page 21]
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
3 Planning
32 User Management
2012-11-27 CUSTOMER 1960
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
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
2060 CUSTOMER 2012-11-27
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 You disable the Windows Server firewall on each host
For more information about disabling the Windows firewall see the relevant section in the
installation documentation of your release
2 You perform basic preparations on Windows
For more information see Performing Basic Windows Preparation Steps in the installation documentation
of your release
3 You check that you have the user authorization required for running the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
4 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
5 Only valid for HA (UNIX) |
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) |
6 If required you prepare the SAP system transport host for your SAP system
For more information see Preparing the SAP System Transport Host in the installation documentation
of your release
7 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
4 Preparation
41 Preparation Checklist
2012-11-27 CUSTOMER 2160
8 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 Dual Stack Split Installation Media [page 25]
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 |
9 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) |
10 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) |
11 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 22] of
the dual-stack system
12 You can continue with Splitting [page 27]
42 Performing a Full System Backup
NOTE
This section is not relevant if your database is Sybase
4 Preparation
42 Performing a Full System Backup
2260 CUSTOMER 2012-11-27
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
NOTE
If your system is a high-availability system make sure that you perform a backup of both cluster
nodes of the dual-stack system
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] for your release and database at
DatabaseSAP NetWeaver Release Path in Help Portal
SAP MaxDB SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for MaxDB
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 CapabilityGeneral 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
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for Oracle
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 CapabilityGeneral 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 Linux UNIX and Windows
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
4 Preparation
42 Performing a Full System Backup
2012-11-27 CUSTOMER 2360
DatabaseSAP NetWeaver Release Path in Help Portal
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 CapabilityGeneral 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 CapabilityGeneral 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 zOS
Microsoft SQL Server
SAP NetWeaver 70
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 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 CapabilityGeneral 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
2460 CUSTOMER 2012-11-27
43 Preparing the Dual Stack Split Installation Media
This section describes how to prepare the installation media that is required for the dual stack split
using the installer
Procedure
1 Download the installation media from the software distribution center on SAP Service Marketplace
using the following path
httpservicesapcomswdc Support Package and Patches A - Z Index S SL TOOLSET SL
TOOLSET 10 Entry by Component Dual-Stack Split
2 Create a download directory on the host on which you want to run the DualndashStack Split tool
3 Unpack the DualndashStack Split tool archive to a local directory using the following command
SAPCAR ndashxvf ltdownload directorygtltpathgtltArchivegtSAR -R ltunpack directorygt
4 Preparation
43 Preparing the Dual Stack Split Installation Media
2012-11-27 CUSTOMER 2560
This page is left blank for documents that are printed on both sides
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
NOTE
Sybase Split option ldquoKeep Databaserdquo is not supported You have to consider only the steps
described in section Move Java Database
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Oracle You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your release
2 Oracle If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your release
3 MS SQL Server You install the MS SQL Server database software
For more information see Installing the SQL Server Database Software in the installation documentation
of your release
4 You export the Java stack using the installer [page 29]
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 48]
5 You restart the source system
6 You run the installer [page 29] to install a Java only system using the export from the dual-stack
system
5 Splitting
51 Splitting Checklist
2012-11-27 CUSTOMER 2760
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 installer dialog
7 You continue with Follow-Up Activities [page 33]
Distributed System
1 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 release
2 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 release
3 On the database instance host of the dual-stack system you run the installer [page 29] to export the
Java database schema
4 On the central instance host of the dual-stack system you run the installer [page 29] 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 48]
5 You restart the source system
6 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
7 You run the installer [page 29] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
9 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2860 CUSTOMER 2012-11-27
Keep Database
1 On the central instance host of the dual-stack system you run the installer [page 29] to export 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 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 48]
2 You restart the source system
3 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
4 On the database instance host of the dual-stack system you run the installer [page 29] 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 the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
6 You continue with Follow-Up Activities [page 33]
52 Running the Installer
This section describes how to run the installer The installer includes a GUI client and a GUI server
which both use Java
The procedure describes an installation where the installer GUI client and GUI server are running on
the same host In the following GUI client and GUI server are addressed as ldquonstaller GUIrdquo
Useful Information About the Installer
When you start the installer it automatically starts the installer GUI
The installer creates the installation directory sapinst_instdir which is located directly in the
ProgramFiles directory If the installer is not able to create sapinst_instdir there it tries to
create sapinst_instdir in the directory defined by the environment variable TEMP
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 2960
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
The installer creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt which is located in ProgramFiles
The installer extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is
located in TEMP TMP TMPDIR or SystemRoot These files are deleted after the installer 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 the installer cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default port 21212 is used for communication between the installer
GUI server and the installer GUI client If this port is already in use you see an error message
In this case or if you want the installer to use a specific port open a command prompt and change
to the required directory to which you unpacked the DSS645_IM_ltplatformgtSAR file
Execute sapinstexe with the following command line parameter
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
To see a list of all available installer properties open a command prompt and start the installer
with command line parameter -p
sapinstexe -p
If you need to run the installer in accessibility mode make sure that you have activated and adjusted
accessibility settings as described in Running the Installer in Accessibility Mode in the installation
documentation of your release
If required you can stop the installer by choosing SAPinst Cancel in the installer GUI menu
Prerequisites
Make sure that you use an account with the required user authorization to run the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
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
the installer
Before you start the installer read SAP Note 1697164 which contains important information how
to run the installer
5 Splitting
52 Running the Installer
3060 CUSTOMER 2012-11-27
Procedure
1 Log on to the installation host using an account with the required user authorization to run the
installer
CAUTION
Do not use an existing ltsapsidgtadm user
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 Preparing the DualndashStack Split Installation Media [page 25]
3 Start the installer by double-clicking sapinstexe from the directory to which you unpacked the
DSS645_IM_ltplatformgtSAR file
NOTE
If you need to perform the installation in accessibility mode open a command prompt change
to the ltpath to unpack directorygt directory and execute sapinstexe ndashaccessible
For more information see Running the Installer in Accessibility Mode in the installation
documentation of your release
The GUI starts automatically by displaying the Welcome screen
4 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
CAUTION
Sybase Split options ldquoMove Java Databaserdquo and ldquoKeep Databaserdquo are not available in the
Welcome screen but only the steps valid for split option ldquoMove Java Databaserdquo are listed
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
5 Choose Next
6 If the installer prompts you to log off from your system log off and on again
The installer restarts automatically
7 Follow the instructions in the installer input screens and enter the required parameters
NOTE
If the installer 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 the installer displays the Parameter Summary
screen This screen shows both the parameters that you entered and those that the installer set by
default If required you can revise the parameters before starting the split procedure
8 To start the dual-stack split choose Start
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 3160
The installer starts and displays the progress of the split procedure
When the split option has finished successfully the installer displays the message Execution of
ltOption_Namegt has completed
CAUTION
Multiple Oracle Homes only The installer uses default values for the Oracle Home and
Listener configuration Therefore if you use multiple Oracle Homes you must specify the
new Oracle home as well as the listener port number You can change these values on the
installer Summary screen during the database instance installation On the Summary screen check
both Oracle gt Database System and Oracle gt Listener Configuration and use the Revise button On the
upcoming screen change the Oracle Home and the Listener port number Make sure that
you use a free port number and do not use the numbers 1521 or 1527 as these might already
be in use by default
9 We recommend that you delete the directory userprofilesdtgui
10 IBM DB2 for Linux and UNIX and Windows If not already done install the DB2 license
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
11 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running the Installer
3260 CUSTOMER 2012-11-27
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
Not valid for Sybase 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
httpservicesapcominstallnw70
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3360
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 the installer [page 29] 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 40] 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3460 CUSTOMER 2012-11-27
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 central instance host of the source system you run the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
12 On the database host of the source system you run the installer [page 29] to remove the Java database
schema
13 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
14 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
15 If required and not already done so you configure the CTS Deploy Web Service [page 40] on the ABAP
system
16 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3560
5 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 release
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
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 the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
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 40] on the ABAP
system
15 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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3660 CUSTOMER 2012-11-27
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 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
12 2012-11-27 Updated version ndash SL Toolset SP06
11 2012-09-26 Updated version
10 2012-08-06 Initial version
260 CUSTOMER 2012-11-27
Table of Contents
Chapter 1 Introduction 5
11 SAP Notes for the Dual-Stack Split 7
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 12
Chapter 3 Planning 17
31 Planning Checklist 17
32 User Management 19
Chapter 4 Preparation 21
41 Preparation Checklist 21
42 Performing a Full System Backup 22
43 Preparing the Dual Stack Split Installation Media 25
Chapter 5 Splitting 27
51 Splitting Checklist 27
52 Running the Installer 29
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 40
65 Cleaning Up the System Landscape 40
Chapter 7 Additional Information 43
71 Troubleshooting 43
72 Additional Information About the Installer 43
2012-11-27 CUSTOMER 360
721 Performing a Remote Installation with the Installer 43
722 Starting the Installer GUI Separately 45
73 Move Java Database Restarting Instances 48
74 Keep Database Restarting Instances 48
75 Splitting Within a System Landscape 49
76 Removing the Java Stack 51
Chapter A Appendix 53
A1 Online Information from SAP 53
A2 Online Information from IBM 55
460 CUSTOMER 2012-11-27
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 You can also use the Dual-Stack
Split 20 tool to remove the Java stack of your SAP dual-stack system
This tool is part of the installation tool and it mainly uses the Java system copy functionality It is
delivered as part of Software Logistics Toolset (SL Toolset) 10 SPS 06
The split procedure is valid for optional dual-stack SAP NetWeaver systems (such as SAP NetWeaver
BW systems with SAP BEx Web) and dual-stack SAP Business Suite systems based on the following SAP
NetWeaver releases
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
NOTE
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 49]
For more information about Dual-Stack Split see httpscnsapcomdocsDOC-25162
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 12])
1 Introduction
2012-11-27 CUSTOMER 560
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-
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 strongly
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
SAP NetWeaver 74
For more information see SAP Note 1655335
If you no longer need the Java stack of your SAP dual-stack system you can use the Dual-Stack
Split 20 tool to remove it as described in Removing the Java Stack [page 51]
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
Heterogeneous 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 media 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
Sybase Split option ldquoKeep Databaserdquo is not supported Only the steps valid for option ldquoMove Java
Databaserdquo are available in the installation tool
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
1 Introduction
660 CUSTOMER 2012-11-27
Only valid for Microsoft Failover Clustering As of Windows Server 2008 the cluster feature is
called Failover Clustering For practical reasons we are continuing to use the previous terminology
Microsoft Cluster Service and abbreviation MSCS in some sections of this guide and the corresponding
installation documentation of your release
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
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
1769205 Dual-Stack Split 20 SP3 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 ltLanguagegt SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 1
httphelpsapcomnw701 Application Help SAP Library ltLanguagegt SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 2
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 3
httphelpsapcomnw703 Application Help SAP Library ltLanguagegt 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
1 Introduction
11 SAP Notes for the Dual-Stack Split
2012-11-27 CUSTOMER 760
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
CAUTION
Sybase Only the functionality of split option ldquoMove Java Databaserdquo is supported
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 17]
Preparation [page 21]
Splitting [page 27]
Follow-up Activities [page 33]
1 Introduction
13 How to Use this Guide
860 CUSTOMER 2012-11-27
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
CAUTION
Sybase Only the functionality of split option ldquoMove Java Databaserdquo is supported
Move Java Database [page 9]
Keep Database [page 12]
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)
Only valid for Microsoft Failover Clustering If your system is a high-availability system with
Microsoft Failover Clustering (previously known as MSCS) the split option ldquoMove Java Databaserdquo offers
the possibility to split a clustered dual-stack system into one ABAP cluster system and one Java cluster
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 the installer 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 the
installer removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
2012-11-27 CUSTOMER 960
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 the installer 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 the
installer removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
1060 CUSTOMER 2012-11-27
Figure 2 Split Option Move Java Database for Distributed System
Move Java Database for High-Availability Systems
When you choose the ldquoMove Java Databaserdquo option for a high-availability system the installer exports
the Java stack of the dual-stack cluster system and uses this export to reinstall all mandatory instances
on a separate cluster system for Java
These are the mandatory instances
Central services instance for Java (SCS)
Enqueue replication server instance (ERS instance) for the SCS instance
Database instance (DB)
Central instance
Dialog instance
After the installation has finished and the System Landscape Directory has been reconfigured the
installer removes all Java parts from the dual-stack cluster system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
2012-11-27 CUSTOMER 1160
Figure 3 Split Option Move Java Database for High-Availability System
22 Split Option Keep Database
CAUTION
Sybase The functionality of split option ldquoKeep Databaserdquo is not supported
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)
Only valid for Microsoft Failover Clustering If your system is a high-availability system with
Microsoft Failover Clustering (MSCS) the split option ldquoKeep Databaserdquo offers the possibility to split a
clustered dual-stack system into one ABAP cluster system and one Java cluster system both using the
same database (MCOD)
Keep Database for Central and Distributed Systems
When you choose the ldquoKeep Databaserdquo option the installer 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 the installer 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 the
installer 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
1260 CUSTOMER 2012-11-27
Figure 4 Split Option Keep Database for Central Systems
Figure 5 Split Option Keep Database for Distributed Systems
Keep Database for High-Availability Systems
When you choose the ldquoKeep Databaserdquo option for a high-availability system you can choose between
the following scenarios
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-11-27 CUSTOMER 1360
Move SCS to New or Other Cluster
The installer exports the Java stack of the dual-stack cluster system and uses this export to install
a central services instance and a central instance on a separate cluster system for Java Additionally
the installer adapts the Java schema of the database of the former dual-stack cluster system to the
target Java cluster system
Figure 6 Split Option Keep Database for High-Availability Systems mdash Move SCS to New or Other
Cluster
Keep SCS on the Source Cluster System
The installer exports the Java central services instance of the source cluster system and uses this
export to install the SCS with a new system ID in a separate cluster on the target cluster system
Additionally the installer adapts the Java schema of the database to the target Java SID
NOTE
This scenario is supported as of Windows Server 2008
2 Split Options Covered by this Guide
22 Split Option Keep Database
1460 CUSTOMER 2012-11-27
Figure 7 Split Option Keep Database for High-Availability Systems mdash Keep SCS on the Source
Cluster System
After the installation has finished and the System Landscape Directory has been reconfigured the
installer removes all Java parts from the dual-stack cluster system except the Java database schema
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-11-27 CUSTOMER 1560
This page is left blank for documents that are printed on both sides
3 Planning
31 Planning Checklist
RECOMMENDATION
We recommend that you first perform the dual-stack split procedure in a test system to identify
possible further application-specific post-split activities required for your scenario
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 19]
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 19]
System Landscape Directory (SLD)
You can ignore SLD parameters
Oracle SAP System Database Parameters Java database schema
3 Planning
31 Planning Checklist
2012-11-27 CUSTOMER 1760
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
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 administrator
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
5 MS SQL Server Oracle For the database installation you decide how to distribute your database
components to disk
For more information see Distribution of SAP System Components to Disk in the installation documentation
of your release
6 SAP MaxDB For the database installation you decide how to distribute your system components
to disk
For more information see Distribution of SAP System Components to Disk in the installation documentation
of your release
7 IBM DB2 for Linux 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 release
8 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
9 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 49]
10 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
11 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
12 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
13 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
14 You can continue with Preparation [page 21]
Split Option ldquoKeep Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
CAUTION
Sybase Split option ldquoKeep Databaserdquo is not supported
3 Planning
31 Planning Checklist
1860 CUSTOMER 2012-11-27
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 19]
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 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 19]
System Landscape Directory (SLD)
You can ignore SLD parameters
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
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 49]
7 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
8 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
9 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
10 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
11 You can continue with Preparation [page 21]
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
3 Planning
32 User Management
2012-11-27 CUSTOMER 1960
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
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
2060 CUSTOMER 2012-11-27
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 You disable the Windows Server firewall on each host
For more information about disabling the Windows firewall see the relevant section in the
installation documentation of your release
2 You perform basic preparations on Windows
For more information see Performing Basic Windows Preparation Steps in the installation documentation
of your release
3 You check that you have the user authorization required for running the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
4 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
5 Only valid for HA (UNIX) |
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) |
6 If required you prepare the SAP system transport host for your SAP system
For more information see Preparing the SAP System Transport Host in the installation documentation
of your release
7 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
4 Preparation
41 Preparation Checklist
2012-11-27 CUSTOMER 2160
8 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 Dual Stack Split Installation Media [page 25]
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 |
9 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) |
10 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) |
11 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 22] of
the dual-stack system
12 You can continue with Splitting [page 27]
42 Performing a Full System Backup
NOTE
This section is not relevant if your database is Sybase
4 Preparation
42 Performing a Full System Backup
2260 CUSTOMER 2012-11-27
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
NOTE
If your system is a high-availability system make sure that you perform a backup of both cluster
nodes of the dual-stack system
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] for your release and database at
DatabaseSAP NetWeaver Release Path in Help Portal
SAP MaxDB SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for MaxDB
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 CapabilityGeneral 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
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for Oracle
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 CapabilityGeneral 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 Linux UNIX and Windows
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
4 Preparation
42 Performing a Full System Backup
2012-11-27 CUSTOMER 2360
DatabaseSAP NetWeaver Release Path in Help Portal
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 CapabilityGeneral 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 CapabilityGeneral 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 zOS
Microsoft SQL Server
SAP NetWeaver 70
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 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 CapabilityGeneral 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
2460 CUSTOMER 2012-11-27
43 Preparing the Dual Stack Split Installation Media
This section describes how to prepare the installation media that is required for the dual stack split
using the installer
Procedure
1 Download the installation media from the software distribution center on SAP Service Marketplace
using the following path
httpservicesapcomswdc Support Package and Patches A - Z Index S SL TOOLSET SL
TOOLSET 10 Entry by Component Dual-Stack Split
2 Create a download directory on the host on which you want to run the DualndashStack Split tool
3 Unpack the DualndashStack Split tool archive to a local directory using the following command
SAPCAR ndashxvf ltdownload directorygtltpathgtltArchivegtSAR -R ltunpack directorygt
4 Preparation
43 Preparing the Dual Stack Split Installation Media
2012-11-27 CUSTOMER 2560
This page is left blank for documents that are printed on both sides
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
NOTE
Sybase Split option ldquoKeep Databaserdquo is not supported You have to consider only the steps
described in section Move Java Database
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Oracle You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your release
2 Oracle If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your release
3 MS SQL Server You install the MS SQL Server database software
For more information see Installing the SQL Server Database Software in the installation documentation
of your release
4 You export the Java stack using the installer [page 29]
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 48]
5 You restart the source system
6 You run the installer [page 29] to install a Java only system using the export from the dual-stack
system
5 Splitting
51 Splitting Checklist
2012-11-27 CUSTOMER 2760
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 installer dialog
7 You continue with Follow-Up Activities [page 33]
Distributed System
1 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 release
2 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 release
3 On the database instance host of the dual-stack system you run the installer [page 29] to export the
Java database schema
4 On the central instance host of the dual-stack system you run the installer [page 29] 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 48]
5 You restart the source system
6 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
7 You run the installer [page 29] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
9 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2860 CUSTOMER 2012-11-27
Keep Database
1 On the central instance host of the dual-stack system you run the installer [page 29] to export 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 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 48]
2 You restart the source system
3 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
4 On the database instance host of the dual-stack system you run the installer [page 29] 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 the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
6 You continue with Follow-Up Activities [page 33]
52 Running the Installer
This section describes how to run the installer The installer includes a GUI client and a GUI server
which both use Java
The procedure describes an installation where the installer GUI client and GUI server are running on
the same host In the following GUI client and GUI server are addressed as ldquonstaller GUIrdquo
Useful Information About the Installer
When you start the installer it automatically starts the installer GUI
The installer creates the installation directory sapinst_instdir which is located directly in the
ProgramFiles directory If the installer is not able to create sapinst_instdir there it tries to
create sapinst_instdir in the directory defined by the environment variable TEMP
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 2960
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
The installer creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt which is located in ProgramFiles
The installer extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is
located in TEMP TMP TMPDIR or SystemRoot These files are deleted after the installer 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 the installer cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default port 21212 is used for communication between the installer
GUI server and the installer GUI client If this port is already in use you see an error message
In this case or if you want the installer to use a specific port open a command prompt and change
to the required directory to which you unpacked the DSS645_IM_ltplatformgtSAR file
Execute sapinstexe with the following command line parameter
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
To see a list of all available installer properties open a command prompt and start the installer
with command line parameter -p
sapinstexe -p
If you need to run the installer in accessibility mode make sure that you have activated and adjusted
accessibility settings as described in Running the Installer in Accessibility Mode in the installation
documentation of your release
If required you can stop the installer by choosing SAPinst Cancel in the installer GUI menu
Prerequisites
Make sure that you use an account with the required user authorization to run the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
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
the installer
Before you start the installer read SAP Note 1697164 which contains important information how
to run the installer
5 Splitting
52 Running the Installer
3060 CUSTOMER 2012-11-27
Procedure
1 Log on to the installation host using an account with the required user authorization to run the
installer
CAUTION
Do not use an existing ltsapsidgtadm user
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 Preparing the DualndashStack Split Installation Media [page 25]
3 Start the installer by double-clicking sapinstexe from the directory to which you unpacked the
DSS645_IM_ltplatformgtSAR file
NOTE
If you need to perform the installation in accessibility mode open a command prompt change
to the ltpath to unpack directorygt directory and execute sapinstexe ndashaccessible
For more information see Running the Installer in Accessibility Mode in the installation
documentation of your release
The GUI starts automatically by displaying the Welcome screen
4 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
CAUTION
Sybase Split options ldquoMove Java Databaserdquo and ldquoKeep Databaserdquo are not available in the
Welcome screen but only the steps valid for split option ldquoMove Java Databaserdquo are listed
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
5 Choose Next
6 If the installer prompts you to log off from your system log off and on again
The installer restarts automatically
7 Follow the instructions in the installer input screens and enter the required parameters
NOTE
If the installer 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 the installer displays the Parameter Summary
screen This screen shows both the parameters that you entered and those that the installer set by
default If required you can revise the parameters before starting the split procedure
8 To start the dual-stack split choose Start
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 3160
The installer starts and displays the progress of the split procedure
When the split option has finished successfully the installer displays the message Execution of
ltOption_Namegt has completed
CAUTION
Multiple Oracle Homes only The installer uses default values for the Oracle Home and
Listener configuration Therefore if you use multiple Oracle Homes you must specify the
new Oracle home as well as the listener port number You can change these values on the
installer Summary screen during the database instance installation On the Summary screen check
both Oracle gt Database System and Oracle gt Listener Configuration and use the Revise button On the
upcoming screen change the Oracle Home and the Listener port number Make sure that
you use a free port number and do not use the numbers 1521 or 1527 as these might already
be in use by default
9 We recommend that you delete the directory userprofilesdtgui
10 IBM DB2 for Linux and UNIX and Windows If not already done install the DB2 license
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
11 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running the Installer
3260 CUSTOMER 2012-11-27
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
Not valid for Sybase 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
httpservicesapcominstallnw70
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3360
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 the installer [page 29] 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 40] 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3460 CUSTOMER 2012-11-27
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 central instance host of the source system you run the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
12 On the database host of the source system you run the installer [page 29] to remove the Java database
schema
13 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
14 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
15 If required and not already done so you configure the CTS Deploy Web Service [page 40] on the ABAP
system
16 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3560
5 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 release
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
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 the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
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 40] on the ABAP
system
15 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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3660 CUSTOMER 2012-11-27
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 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 7
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 12
Chapter 3 Planning 17
31 Planning Checklist 17
32 User Management 19
Chapter 4 Preparation 21
41 Preparation Checklist 21
42 Performing a Full System Backup 22
43 Preparing the Dual Stack Split Installation Media 25
Chapter 5 Splitting 27
51 Splitting Checklist 27
52 Running the Installer 29
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 40
65 Cleaning Up the System Landscape 40
Chapter 7 Additional Information 43
71 Troubleshooting 43
72 Additional Information About the Installer 43
2012-11-27 CUSTOMER 360
721 Performing a Remote Installation with the Installer 43
722 Starting the Installer GUI Separately 45
73 Move Java Database Restarting Instances 48
74 Keep Database Restarting Instances 48
75 Splitting Within a System Landscape 49
76 Removing the Java Stack 51
Chapter A Appendix 53
A1 Online Information from SAP 53
A2 Online Information from IBM 55
460 CUSTOMER 2012-11-27
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 You can also use the Dual-Stack
Split 20 tool to remove the Java stack of your SAP dual-stack system
This tool is part of the installation tool and it mainly uses the Java system copy functionality It is
delivered as part of Software Logistics Toolset (SL Toolset) 10 SPS 06
The split procedure is valid for optional dual-stack SAP NetWeaver systems (such as SAP NetWeaver
BW systems with SAP BEx Web) and dual-stack SAP Business Suite systems based on the following SAP
NetWeaver releases
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
NOTE
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 49]
For more information about Dual-Stack Split see httpscnsapcomdocsDOC-25162
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 12])
1 Introduction
2012-11-27 CUSTOMER 560
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-
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 strongly
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
SAP NetWeaver 74
For more information see SAP Note 1655335
If you no longer need the Java stack of your SAP dual-stack system you can use the Dual-Stack
Split 20 tool to remove it as described in Removing the Java Stack [page 51]
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
Heterogeneous 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 media 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
Sybase Split option ldquoKeep Databaserdquo is not supported Only the steps valid for option ldquoMove Java
Databaserdquo are available in the installation tool
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
1 Introduction
660 CUSTOMER 2012-11-27
Only valid for Microsoft Failover Clustering As of Windows Server 2008 the cluster feature is
called Failover Clustering For practical reasons we are continuing to use the previous terminology
Microsoft Cluster Service and abbreviation MSCS in some sections of this guide and the corresponding
installation documentation of your release
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
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
1769205 Dual-Stack Split 20 SP3 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 ltLanguagegt SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 1
httphelpsapcomnw701 Application Help SAP Library ltLanguagegt SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 2
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 3
httphelpsapcomnw703 Application Help SAP Library ltLanguagegt 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
1 Introduction
11 SAP Notes for the Dual-Stack Split
2012-11-27 CUSTOMER 760
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
CAUTION
Sybase Only the functionality of split option ldquoMove Java Databaserdquo is supported
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 17]
Preparation [page 21]
Splitting [page 27]
Follow-up Activities [page 33]
1 Introduction
13 How to Use this Guide
860 CUSTOMER 2012-11-27
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
CAUTION
Sybase Only the functionality of split option ldquoMove Java Databaserdquo is supported
Move Java Database [page 9]
Keep Database [page 12]
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)
Only valid for Microsoft Failover Clustering If your system is a high-availability system with
Microsoft Failover Clustering (previously known as MSCS) the split option ldquoMove Java Databaserdquo offers
the possibility to split a clustered dual-stack system into one ABAP cluster system and one Java cluster
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 the installer 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 the
installer removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
2012-11-27 CUSTOMER 960
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 the installer 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 the
installer removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
1060 CUSTOMER 2012-11-27
Figure 2 Split Option Move Java Database for Distributed System
Move Java Database for High-Availability Systems
When you choose the ldquoMove Java Databaserdquo option for a high-availability system the installer exports
the Java stack of the dual-stack cluster system and uses this export to reinstall all mandatory instances
on a separate cluster system for Java
These are the mandatory instances
Central services instance for Java (SCS)
Enqueue replication server instance (ERS instance) for the SCS instance
Database instance (DB)
Central instance
Dialog instance
After the installation has finished and the System Landscape Directory has been reconfigured the
installer removes all Java parts from the dual-stack cluster system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
2012-11-27 CUSTOMER 1160
Figure 3 Split Option Move Java Database for High-Availability System
22 Split Option Keep Database
CAUTION
Sybase The functionality of split option ldquoKeep Databaserdquo is not supported
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)
Only valid for Microsoft Failover Clustering If your system is a high-availability system with
Microsoft Failover Clustering (MSCS) the split option ldquoKeep Databaserdquo offers the possibility to split a
clustered dual-stack system into one ABAP cluster system and one Java cluster system both using the
same database (MCOD)
Keep Database for Central and Distributed Systems
When you choose the ldquoKeep Databaserdquo option the installer 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 the installer 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 the
installer 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
1260 CUSTOMER 2012-11-27
Figure 4 Split Option Keep Database for Central Systems
Figure 5 Split Option Keep Database for Distributed Systems
Keep Database for High-Availability Systems
When you choose the ldquoKeep Databaserdquo option for a high-availability system you can choose between
the following scenarios
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-11-27 CUSTOMER 1360
Move SCS to New or Other Cluster
The installer exports the Java stack of the dual-stack cluster system and uses this export to install
a central services instance and a central instance on a separate cluster system for Java Additionally
the installer adapts the Java schema of the database of the former dual-stack cluster system to the
target Java cluster system
Figure 6 Split Option Keep Database for High-Availability Systems mdash Move SCS to New or Other
Cluster
Keep SCS on the Source Cluster System
The installer exports the Java central services instance of the source cluster system and uses this
export to install the SCS with a new system ID in a separate cluster on the target cluster system
Additionally the installer adapts the Java schema of the database to the target Java SID
NOTE
This scenario is supported as of Windows Server 2008
2 Split Options Covered by this Guide
22 Split Option Keep Database
1460 CUSTOMER 2012-11-27
Figure 7 Split Option Keep Database for High-Availability Systems mdash Keep SCS on the Source
Cluster System
After the installation has finished and the System Landscape Directory has been reconfigured the
installer removes all Java parts from the dual-stack cluster system except the Java database schema
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-11-27 CUSTOMER 1560
This page is left blank for documents that are printed on both sides
3 Planning
31 Planning Checklist
RECOMMENDATION
We recommend that you first perform the dual-stack split procedure in a test system to identify
possible further application-specific post-split activities required for your scenario
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 19]
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 19]
System Landscape Directory (SLD)
You can ignore SLD parameters
Oracle SAP System Database Parameters Java database schema
3 Planning
31 Planning Checklist
2012-11-27 CUSTOMER 1760
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
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 administrator
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
5 MS SQL Server Oracle For the database installation you decide how to distribute your database
components to disk
For more information see Distribution of SAP System Components to Disk in the installation documentation
of your release
6 SAP MaxDB For the database installation you decide how to distribute your system components
to disk
For more information see Distribution of SAP System Components to Disk in the installation documentation
of your release
7 IBM DB2 for Linux 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 release
8 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
9 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 49]
10 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
11 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
12 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
13 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
14 You can continue with Preparation [page 21]
Split Option ldquoKeep Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
CAUTION
Sybase Split option ldquoKeep Databaserdquo is not supported
3 Planning
31 Planning Checklist
1860 CUSTOMER 2012-11-27
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 19]
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 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 19]
System Landscape Directory (SLD)
You can ignore SLD parameters
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
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 49]
7 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
8 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
9 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
10 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
11 You can continue with Preparation [page 21]
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
3 Planning
32 User Management
2012-11-27 CUSTOMER 1960
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
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
2060 CUSTOMER 2012-11-27
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 You disable the Windows Server firewall on each host
For more information about disabling the Windows firewall see the relevant section in the
installation documentation of your release
2 You perform basic preparations on Windows
For more information see Performing Basic Windows Preparation Steps in the installation documentation
of your release
3 You check that you have the user authorization required for running the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
4 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
5 Only valid for HA (UNIX) |
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) |
6 If required you prepare the SAP system transport host for your SAP system
For more information see Preparing the SAP System Transport Host in the installation documentation
of your release
7 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
4 Preparation
41 Preparation Checklist
2012-11-27 CUSTOMER 2160
8 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 Dual Stack Split Installation Media [page 25]
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 |
9 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) |
10 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) |
11 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 22] of
the dual-stack system
12 You can continue with Splitting [page 27]
42 Performing a Full System Backup
NOTE
This section is not relevant if your database is Sybase
4 Preparation
42 Performing a Full System Backup
2260 CUSTOMER 2012-11-27
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
NOTE
If your system is a high-availability system make sure that you perform a backup of both cluster
nodes of the dual-stack system
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] for your release and database at
DatabaseSAP NetWeaver Release Path in Help Portal
SAP MaxDB SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for MaxDB
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 CapabilityGeneral 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
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for Oracle
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 CapabilityGeneral 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 Linux UNIX and Windows
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
4 Preparation
42 Performing a Full System Backup
2012-11-27 CUSTOMER 2360
DatabaseSAP NetWeaver Release Path in Help Portal
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 CapabilityGeneral 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 CapabilityGeneral 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 zOS
Microsoft SQL Server
SAP NetWeaver 70
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 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 CapabilityGeneral 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
2460 CUSTOMER 2012-11-27
43 Preparing the Dual Stack Split Installation Media
This section describes how to prepare the installation media that is required for the dual stack split
using the installer
Procedure
1 Download the installation media from the software distribution center on SAP Service Marketplace
using the following path
httpservicesapcomswdc Support Package and Patches A - Z Index S SL TOOLSET SL
TOOLSET 10 Entry by Component Dual-Stack Split
2 Create a download directory on the host on which you want to run the DualndashStack Split tool
3 Unpack the DualndashStack Split tool archive to a local directory using the following command
SAPCAR ndashxvf ltdownload directorygtltpathgtltArchivegtSAR -R ltunpack directorygt
4 Preparation
43 Preparing the Dual Stack Split Installation Media
2012-11-27 CUSTOMER 2560
This page is left blank for documents that are printed on both sides
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
NOTE
Sybase Split option ldquoKeep Databaserdquo is not supported You have to consider only the steps
described in section Move Java Database
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Oracle You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your release
2 Oracle If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your release
3 MS SQL Server You install the MS SQL Server database software
For more information see Installing the SQL Server Database Software in the installation documentation
of your release
4 You export the Java stack using the installer [page 29]
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 48]
5 You restart the source system
6 You run the installer [page 29] to install a Java only system using the export from the dual-stack
system
5 Splitting
51 Splitting Checklist
2012-11-27 CUSTOMER 2760
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 installer dialog
7 You continue with Follow-Up Activities [page 33]
Distributed System
1 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 release
2 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 release
3 On the database instance host of the dual-stack system you run the installer [page 29] to export the
Java database schema
4 On the central instance host of the dual-stack system you run the installer [page 29] 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 48]
5 You restart the source system
6 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
7 You run the installer [page 29] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
9 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2860 CUSTOMER 2012-11-27
Keep Database
1 On the central instance host of the dual-stack system you run the installer [page 29] to export 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 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 48]
2 You restart the source system
3 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
4 On the database instance host of the dual-stack system you run the installer [page 29] 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 the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
6 You continue with Follow-Up Activities [page 33]
52 Running the Installer
This section describes how to run the installer The installer includes a GUI client and a GUI server
which both use Java
The procedure describes an installation where the installer GUI client and GUI server are running on
the same host In the following GUI client and GUI server are addressed as ldquonstaller GUIrdquo
Useful Information About the Installer
When you start the installer it automatically starts the installer GUI
The installer creates the installation directory sapinst_instdir which is located directly in the
ProgramFiles directory If the installer is not able to create sapinst_instdir there it tries to
create sapinst_instdir in the directory defined by the environment variable TEMP
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 2960
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
The installer creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt which is located in ProgramFiles
The installer extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is
located in TEMP TMP TMPDIR or SystemRoot These files are deleted after the installer 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 the installer cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default port 21212 is used for communication between the installer
GUI server and the installer GUI client If this port is already in use you see an error message
In this case or if you want the installer to use a specific port open a command prompt and change
to the required directory to which you unpacked the DSS645_IM_ltplatformgtSAR file
Execute sapinstexe with the following command line parameter
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
To see a list of all available installer properties open a command prompt and start the installer
with command line parameter -p
sapinstexe -p
If you need to run the installer in accessibility mode make sure that you have activated and adjusted
accessibility settings as described in Running the Installer in Accessibility Mode in the installation
documentation of your release
If required you can stop the installer by choosing SAPinst Cancel in the installer GUI menu
Prerequisites
Make sure that you use an account with the required user authorization to run the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
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
the installer
Before you start the installer read SAP Note 1697164 which contains important information how
to run the installer
5 Splitting
52 Running the Installer
3060 CUSTOMER 2012-11-27
Procedure
1 Log on to the installation host using an account with the required user authorization to run the
installer
CAUTION
Do not use an existing ltsapsidgtadm user
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 Preparing the DualndashStack Split Installation Media [page 25]
3 Start the installer by double-clicking sapinstexe from the directory to which you unpacked the
DSS645_IM_ltplatformgtSAR file
NOTE
If you need to perform the installation in accessibility mode open a command prompt change
to the ltpath to unpack directorygt directory and execute sapinstexe ndashaccessible
For more information see Running the Installer in Accessibility Mode in the installation
documentation of your release
The GUI starts automatically by displaying the Welcome screen
4 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
CAUTION
Sybase Split options ldquoMove Java Databaserdquo and ldquoKeep Databaserdquo are not available in the
Welcome screen but only the steps valid for split option ldquoMove Java Databaserdquo are listed
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
5 Choose Next
6 If the installer prompts you to log off from your system log off and on again
The installer restarts automatically
7 Follow the instructions in the installer input screens and enter the required parameters
NOTE
If the installer 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 the installer displays the Parameter Summary
screen This screen shows both the parameters that you entered and those that the installer set by
default If required you can revise the parameters before starting the split procedure
8 To start the dual-stack split choose Start
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 3160
The installer starts and displays the progress of the split procedure
When the split option has finished successfully the installer displays the message Execution of
ltOption_Namegt has completed
CAUTION
Multiple Oracle Homes only The installer uses default values for the Oracle Home and
Listener configuration Therefore if you use multiple Oracle Homes you must specify the
new Oracle home as well as the listener port number You can change these values on the
installer Summary screen during the database instance installation On the Summary screen check
both Oracle gt Database System and Oracle gt Listener Configuration and use the Revise button On the
upcoming screen change the Oracle Home and the Listener port number Make sure that
you use a free port number and do not use the numbers 1521 or 1527 as these might already
be in use by default
9 We recommend that you delete the directory userprofilesdtgui
10 IBM DB2 for Linux and UNIX and Windows If not already done install the DB2 license
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
11 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running the Installer
3260 CUSTOMER 2012-11-27
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
Not valid for Sybase 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
httpservicesapcominstallnw70
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3360
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 the installer [page 29] 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 40] 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3460 CUSTOMER 2012-11-27
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 central instance host of the source system you run the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
12 On the database host of the source system you run the installer [page 29] to remove the Java database
schema
13 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
14 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
15 If required and not already done so you configure the CTS Deploy Web Service [page 40] on the ABAP
system
16 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3560
5 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 release
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
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 the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
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 40] on the ABAP
system
15 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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3660 CUSTOMER 2012-11-27
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
721 Performing a Remote Installation with the Installer 43
722 Starting the Installer GUI Separately 45
73 Move Java Database Restarting Instances 48
74 Keep Database Restarting Instances 48
75 Splitting Within a System Landscape 49
76 Removing the Java Stack 51
Chapter A Appendix 53
A1 Online Information from SAP 53
A2 Online Information from IBM 55
460 CUSTOMER 2012-11-27
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 You can also use the Dual-Stack
Split 20 tool to remove the Java stack of your SAP dual-stack system
This tool is part of the installation tool and it mainly uses the Java system copy functionality It is
delivered as part of Software Logistics Toolset (SL Toolset) 10 SPS 06
The split procedure is valid for optional dual-stack SAP NetWeaver systems (such as SAP NetWeaver
BW systems with SAP BEx Web) and dual-stack SAP Business Suite systems based on the following SAP
NetWeaver releases
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
NOTE
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 49]
For more information about Dual-Stack Split see httpscnsapcomdocsDOC-25162
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 12])
1 Introduction
2012-11-27 CUSTOMER 560
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-
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 strongly
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
SAP NetWeaver 74
For more information see SAP Note 1655335
If you no longer need the Java stack of your SAP dual-stack system you can use the Dual-Stack
Split 20 tool to remove it as described in Removing the Java Stack [page 51]
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
Heterogeneous 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 media 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
Sybase Split option ldquoKeep Databaserdquo is not supported Only the steps valid for option ldquoMove Java
Databaserdquo are available in the installation tool
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
1 Introduction
660 CUSTOMER 2012-11-27
Only valid for Microsoft Failover Clustering As of Windows Server 2008 the cluster feature is
called Failover Clustering For practical reasons we are continuing to use the previous terminology
Microsoft Cluster Service and abbreviation MSCS in some sections of this guide and the corresponding
installation documentation of your release
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
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
1769205 Dual-Stack Split 20 SP3 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 ltLanguagegt SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 1
httphelpsapcomnw701 Application Help SAP Library ltLanguagegt SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 2
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 3
httphelpsapcomnw703 Application Help SAP Library ltLanguagegt 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
1 Introduction
11 SAP Notes for the Dual-Stack Split
2012-11-27 CUSTOMER 760
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
CAUTION
Sybase Only the functionality of split option ldquoMove Java Databaserdquo is supported
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 17]
Preparation [page 21]
Splitting [page 27]
Follow-up Activities [page 33]
1 Introduction
13 How to Use this Guide
860 CUSTOMER 2012-11-27
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
CAUTION
Sybase Only the functionality of split option ldquoMove Java Databaserdquo is supported
Move Java Database [page 9]
Keep Database [page 12]
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)
Only valid for Microsoft Failover Clustering If your system is a high-availability system with
Microsoft Failover Clustering (previously known as MSCS) the split option ldquoMove Java Databaserdquo offers
the possibility to split a clustered dual-stack system into one ABAP cluster system and one Java cluster
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 the installer 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 the
installer removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
2012-11-27 CUSTOMER 960
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 the installer 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 the
installer removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
1060 CUSTOMER 2012-11-27
Figure 2 Split Option Move Java Database for Distributed System
Move Java Database for High-Availability Systems
When you choose the ldquoMove Java Databaserdquo option for a high-availability system the installer exports
the Java stack of the dual-stack cluster system and uses this export to reinstall all mandatory instances
on a separate cluster system for Java
These are the mandatory instances
Central services instance for Java (SCS)
Enqueue replication server instance (ERS instance) for the SCS instance
Database instance (DB)
Central instance
Dialog instance
After the installation has finished and the System Landscape Directory has been reconfigured the
installer removes all Java parts from the dual-stack cluster system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
2012-11-27 CUSTOMER 1160
Figure 3 Split Option Move Java Database for High-Availability System
22 Split Option Keep Database
CAUTION
Sybase The functionality of split option ldquoKeep Databaserdquo is not supported
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)
Only valid for Microsoft Failover Clustering If your system is a high-availability system with
Microsoft Failover Clustering (MSCS) the split option ldquoKeep Databaserdquo offers the possibility to split a
clustered dual-stack system into one ABAP cluster system and one Java cluster system both using the
same database (MCOD)
Keep Database for Central and Distributed Systems
When you choose the ldquoKeep Databaserdquo option the installer 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 the installer 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 the
installer 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
1260 CUSTOMER 2012-11-27
Figure 4 Split Option Keep Database for Central Systems
Figure 5 Split Option Keep Database for Distributed Systems
Keep Database for High-Availability Systems
When you choose the ldquoKeep Databaserdquo option for a high-availability system you can choose between
the following scenarios
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-11-27 CUSTOMER 1360
Move SCS to New or Other Cluster
The installer exports the Java stack of the dual-stack cluster system and uses this export to install
a central services instance and a central instance on a separate cluster system for Java Additionally
the installer adapts the Java schema of the database of the former dual-stack cluster system to the
target Java cluster system
Figure 6 Split Option Keep Database for High-Availability Systems mdash Move SCS to New or Other
Cluster
Keep SCS on the Source Cluster System
The installer exports the Java central services instance of the source cluster system and uses this
export to install the SCS with a new system ID in a separate cluster on the target cluster system
Additionally the installer adapts the Java schema of the database to the target Java SID
NOTE
This scenario is supported as of Windows Server 2008
2 Split Options Covered by this Guide
22 Split Option Keep Database
1460 CUSTOMER 2012-11-27
Figure 7 Split Option Keep Database for High-Availability Systems mdash Keep SCS on the Source
Cluster System
After the installation has finished and the System Landscape Directory has been reconfigured the
installer removes all Java parts from the dual-stack cluster system except the Java database schema
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-11-27 CUSTOMER 1560
This page is left blank for documents that are printed on both sides
3 Planning
31 Planning Checklist
RECOMMENDATION
We recommend that you first perform the dual-stack split procedure in a test system to identify
possible further application-specific post-split activities required for your scenario
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 19]
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 19]
System Landscape Directory (SLD)
You can ignore SLD parameters
Oracle SAP System Database Parameters Java database schema
3 Planning
31 Planning Checklist
2012-11-27 CUSTOMER 1760
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
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 administrator
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
5 MS SQL Server Oracle For the database installation you decide how to distribute your database
components to disk
For more information see Distribution of SAP System Components to Disk in the installation documentation
of your release
6 SAP MaxDB For the database installation you decide how to distribute your system components
to disk
For more information see Distribution of SAP System Components to Disk in the installation documentation
of your release
7 IBM DB2 for Linux 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 release
8 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
9 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 49]
10 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
11 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
12 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
13 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
14 You can continue with Preparation [page 21]
Split Option ldquoKeep Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
CAUTION
Sybase Split option ldquoKeep Databaserdquo is not supported
3 Planning
31 Planning Checklist
1860 CUSTOMER 2012-11-27
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 19]
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 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 19]
System Landscape Directory (SLD)
You can ignore SLD parameters
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
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 49]
7 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
8 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
9 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
10 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
11 You can continue with Preparation [page 21]
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
3 Planning
32 User Management
2012-11-27 CUSTOMER 1960
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
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
2060 CUSTOMER 2012-11-27
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 You disable the Windows Server firewall on each host
For more information about disabling the Windows firewall see the relevant section in the
installation documentation of your release
2 You perform basic preparations on Windows
For more information see Performing Basic Windows Preparation Steps in the installation documentation
of your release
3 You check that you have the user authorization required for running the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
4 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
5 Only valid for HA (UNIX) |
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) |
6 If required you prepare the SAP system transport host for your SAP system
For more information see Preparing the SAP System Transport Host in the installation documentation
of your release
7 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
4 Preparation
41 Preparation Checklist
2012-11-27 CUSTOMER 2160
8 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 Dual Stack Split Installation Media [page 25]
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 |
9 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) |
10 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) |
11 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 22] of
the dual-stack system
12 You can continue with Splitting [page 27]
42 Performing a Full System Backup
NOTE
This section is not relevant if your database is Sybase
4 Preparation
42 Performing a Full System Backup
2260 CUSTOMER 2012-11-27
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
NOTE
If your system is a high-availability system make sure that you perform a backup of both cluster
nodes of the dual-stack system
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] for your release and database at
DatabaseSAP NetWeaver Release Path in Help Portal
SAP MaxDB SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for MaxDB
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 CapabilityGeneral 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
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for Oracle
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 CapabilityGeneral 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 Linux UNIX and Windows
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
4 Preparation
42 Performing a Full System Backup
2012-11-27 CUSTOMER 2360
DatabaseSAP NetWeaver Release Path in Help Portal
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 CapabilityGeneral 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 CapabilityGeneral 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 zOS
Microsoft SQL Server
SAP NetWeaver 70
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 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 CapabilityGeneral 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
2460 CUSTOMER 2012-11-27
43 Preparing the Dual Stack Split Installation Media
This section describes how to prepare the installation media that is required for the dual stack split
using the installer
Procedure
1 Download the installation media from the software distribution center on SAP Service Marketplace
using the following path
httpservicesapcomswdc Support Package and Patches A - Z Index S SL TOOLSET SL
TOOLSET 10 Entry by Component Dual-Stack Split
2 Create a download directory on the host on which you want to run the DualndashStack Split tool
3 Unpack the DualndashStack Split tool archive to a local directory using the following command
SAPCAR ndashxvf ltdownload directorygtltpathgtltArchivegtSAR -R ltunpack directorygt
4 Preparation
43 Preparing the Dual Stack Split Installation Media
2012-11-27 CUSTOMER 2560
This page is left blank for documents that are printed on both sides
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
NOTE
Sybase Split option ldquoKeep Databaserdquo is not supported You have to consider only the steps
described in section Move Java Database
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Oracle You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your release
2 Oracle If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your release
3 MS SQL Server You install the MS SQL Server database software
For more information see Installing the SQL Server Database Software in the installation documentation
of your release
4 You export the Java stack using the installer [page 29]
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 48]
5 You restart the source system
6 You run the installer [page 29] to install a Java only system using the export from the dual-stack
system
5 Splitting
51 Splitting Checklist
2012-11-27 CUSTOMER 2760
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 installer dialog
7 You continue with Follow-Up Activities [page 33]
Distributed System
1 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 release
2 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 release
3 On the database instance host of the dual-stack system you run the installer [page 29] to export the
Java database schema
4 On the central instance host of the dual-stack system you run the installer [page 29] 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 48]
5 You restart the source system
6 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
7 You run the installer [page 29] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
9 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2860 CUSTOMER 2012-11-27
Keep Database
1 On the central instance host of the dual-stack system you run the installer [page 29] to export 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 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 48]
2 You restart the source system
3 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
4 On the database instance host of the dual-stack system you run the installer [page 29] 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 the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
6 You continue with Follow-Up Activities [page 33]
52 Running the Installer
This section describes how to run the installer The installer includes a GUI client and a GUI server
which both use Java
The procedure describes an installation where the installer GUI client and GUI server are running on
the same host In the following GUI client and GUI server are addressed as ldquonstaller GUIrdquo
Useful Information About the Installer
When you start the installer it automatically starts the installer GUI
The installer creates the installation directory sapinst_instdir which is located directly in the
ProgramFiles directory If the installer is not able to create sapinst_instdir there it tries to
create sapinst_instdir in the directory defined by the environment variable TEMP
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 2960
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
The installer creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt which is located in ProgramFiles
The installer extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is
located in TEMP TMP TMPDIR or SystemRoot These files are deleted after the installer 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 the installer cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default port 21212 is used for communication between the installer
GUI server and the installer GUI client If this port is already in use you see an error message
In this case or if you want the installer to use a specific port open a command prompt and change
to the required directory to which you unpacked the DSS645_IM_ltplatformgtSAR file
Execute sapinstexe with the following command line parameter
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
To see a list of all available installer properties open a command prompt and start the installer
with command line parameter -p
sapinstexe -p
If you need to run the installer in accessibility mode make sure that you have activated and adjusted
accessibility settings as described in Running the Installer in Accessibility Mode in the installation
documentation of your release
If required you can stop the installer by choosing SAPinst Cancel in the installer GUI menu
Prerequisites
Make sure that you use an account with the required user authorization to run the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
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
the installer
Before you start the installer read SAP Note 1697164 which contains important information how
to run the installer
5 Splitting
52 Running the Installer
3060 CUSTOMER 2012-11-27
Procedure
1 Log on to the installation host using an account with the required user authorization to run the
installer
CAUTION
Do not use an existing ltsapsidgtadm user
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 Preparing the DualndashStack Split Installation Media [page 25]
3 Start the installer by double-clicking sapinstexe from the directory to which you unpacked the
DSS645_IM_ltplatformgtSAR file
NOTE
If you need to perform the installation in accessibility mode open a command prompt change
to the ltpath to unpack directorygt directory and execute sapinstexe ndashaccessible
For more information see Running the Installer in Accessibility Mode in the installation
documentation of your release
The GUI starts automatically by displaying the Welcome screen
4 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
CAUTION
Sybase Split options ldquoMove Java Databaserdquo and ldquoKeep Databaserdquo are not available in the
Welcome screen but only the steps valid for split option ldquoMove Java Databaserdquo are listed
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
5 Choose Next
6 If the installer prompts you to log off from your system log off and on again
The installer restarts automatically
7 Follow the instructions in the installer input screens and enter the required parameters
NOTE
If the installer 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 the installer displays the Parameter Summary
screen This screen shows both the parameters that you entered and those that the installer set by
default If required you can revise the parameters before starting the split procedure
8 To start the dual-stack split choose Start
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 3160
The installer starts and displays the progress of the split procedure
When the split option has finished successfully the installer displays the message Execution of
ltOption_Namegt has completed
CAUTION
Multiple Oracle Homes only The installer uses default values for the Oracle Home and
Listener configuration Therefore if you use multiple Oracle Homes you must specify the
new Oracle home as well as the listener port number You can change these values on the
installer Summary screen during the database instance installation On the Summary screen check
both Oracle gt Database System and Oracle gt Listener Configuration and use the Revise button On the
upcoming screen change the Oracle Home and the Listener port number Make sure that
you use a free port number and do not use the numbers 1521 or 1527 as these might already
be in use by default
9 We recommend that you delete the directory userprofilesdtgui
10 IBM DB2 for Linux and UNIX and Windows If not already done install the DB2 license
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
11 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running the Installer
3260 CUSTOMER 2012-11-27
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
Not valid for Sybase 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
httpservicesapcominstallnw70
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3360
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 the installer [page 29] 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 40] 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3460 CUSTOMER 2012-11-27
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 central instance host of the source system you run the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
12 On the database host of the source system you run the installer [page 29] to remove the Java database
schema
13 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
14 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
15 If required and not already done so you configure the CTS Deploy Web Service [page 40] on the ABAP
system
16 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3560
5 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 release
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
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 the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
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 40] on the ABAP
system
15 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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3660 CUSTOMER 2012-11-27
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 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 You can also use the Dual-Stack
Split 20 tool to remove the Java stack of your SAP dual-stack system
This tool is part of the installation tool and it mainly uses the Java system copy functionality It is
delivered as part of Software Logistics Toolset (SL Toolset) 10 SPS 06
The split procedure is valid for optional dual-stack SAP NetWeaver systems (such as SAP NetWeaver
BW systems with SAP BEx Web) and dual-stack SAP Business Suite systems based on the following SAP
NetWeaver releases
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
NOTE
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 49]
For more information about Dual-Stack Split see httpscnsapcomdocsDOC-25162
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 12])
1 Introduction
2012-11-27 CUSTOMER 560
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-
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 strongly
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
SAP NetWeaver 74
For more information see SAP Note 1655335
If you no longer need the Java stack of your SAP dual-stack system you can use the Dual-Stack
Split 20 tool to remove it as described in Removing the Java Stack [page 51]
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
Heterogeneous 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 media 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
Sybase Split option ldquoKeep Databaserdquo is not supported Only the steps valid for option ldquoMove Java
Databaserdquo are available in the installation tool
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
1 Introduction
660 CUSTOMER 2012-11-27
Only valid for Microsoft Failover Clustering As of Windows Server 2008 the cluster feature is
called Failover Clustering For practical reasons we are continuing to use the previous terminology
Microsoft Cluster Service and abbreviation MSCS in some sections of this guide and the corresponding
installation documentation of your release
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
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
1769205 Dual-Stack Split 20 SP3 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 ltLanguagegt SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 1
httphelpsapcomnw701 Application Help SAP Library ltLanguagegt SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 2
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 3
httphelpsapcomnw703 Application Help SAP Library ltLanguagegt 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
1 Introduction
11 SAP Notes for the Dual-Stack Split
2012-11-27 CUSTOMER 760
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
CAUTION
Sybase Only the functionality of split option ldquoMove Java Databaserdquo is supported
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 17]
Preparation [page 21]
Splitting [page 27]
Follow-up Activities [page 33]
1 Introduction
13 How to Use this Guide
860 CUSTOMER 2012-11-27
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
CAUTION
Sybase Only the functionality of split option ldquoMove Java Databaserdquo is supported
Move Java Database [page 9]
Keep Database [page 12]
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)
Only valid for Microsoft Failover Clustering If your system is a high-availability system with
Microsoft Failover Clustering (previously known as MSCS) the split option ldquoMove Java Databaserdquo offers
the possibility to split a clustered dual-stack system into one ABAP cluster system and one Java cluster
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 the installer 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 the
installer removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
2012-11-27 CUSTOMER 960
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 the installer 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 the
installer removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
1060 CUSTOMER 2012-11-27
Figure 2 Split Option Move Java Database for Distributed System
Move Java Database for High-Availability Systems
When you choose the ldquoMove Java Databaserdquo option for a high-availability system the installer exports
the Java stack of the dual-stack cluster system and uses this export to reinstall all mandatory instances
on a separate cluster system for Java
These are the mandatory instances
Central services instance for Java (SCS)
Enqueue replication server instance (ERS instance) for the SCS instance
Database instance (DB)
Central instance
Dialog instance
After the installation has finished and the System Landscape Directory has been reconfigured the
installer removes all Java parts from the dual-stack cluster system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
2012-11-27 CUSTOMER 1160
Figure 3 Split Option Move Java Database for High-Availability System
22 Split Option Keep Database
CAUTION
Sybase The functionality of split option ldquoKeep Databaserdquo is not supported
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)
Only valid for Microsoft Failover Clustering If your system is a high-availability system with
Microsoft Failover Clustering (MSCS) the split option ldquoKeep Databaserdquo offers the possibility to split a
clustered dual-stack system into one ABAP cluster system and one Java cluster system both using the
same database (MCOD)
Keep Database for Central and Distributed Systems
When you choose the ldquoKeep Databaserdquo option the installer 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 the installer 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 the
installer 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
1260 CUSTOMER 2012-11-27
Figure 4 Split Option Keep Database for Central Systems
Figure 5 Split Option Keep Database for Distributed Systems
Keep Database for High-Availability Systems
When you choose the ldquoKeep Databaserdquo option for a high-availability system you can choose between
the following scenarios
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-11-27 CUSTOMER 1360
Move SCS to New or Other Cluster
The installer exports the Java stack of the dual-stack cluster system and uses this export to install
a central services instance and a central instance on a separate cluster system for Java Additionally
the installer adapts the Java schema of the database of the former dual-stack cluster system to the
target Java cluster system
Figure 6 Split Option Keep Database for High-Availability Systems mdash Move SCS to New or Other
Cluster
Keep SCS on the Source Cluster System
The installer exports the Java central services instance of the source cluster system and uses this
export to install the SCS with a new system ID in a separate cluster on the target cluster system
Additionally the installer adapts the Java schema of the database to the target Java SID
NOTE
This scenario is supported as of Windows Server 2008
2 Split Options Covered by this Guide
22 Split Option Keep Database
1460 CUSTOMER 2012-11-27
Figure 7 Split Option Keep Database for High-Availability Systems mdash Keep SCS on the Source
Cluster System
After the installation has finished and the System Landscape Directory has been reconfigured the
installer removes all Java parts from the dual-stack cluster system except the Java database schema
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-11-27 CUSTOMER 1560
This page is left blank for documents that are printed on both sides
3 Planning
31 Planning Checklist
RECOMMENDATION
We recommend that you first perform the dual-stack split procedure in a test system to identify
possible further application-specific post-split activities required for your scenario
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 19]
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 19]
System Landscape Directory (SLD)
You can ignore SLD parameters
Oracle SAP System Database Parameters Java database schema
3 Planning
31 Planning Checklist
2012-11-27 CUSTOMER 1760
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
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 administrator
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
5 MS SQL Server Oracle For the database installation you decide how to distribute your database
components to disk
For more information see Distribution of SAP System Components to Disk in the installation documentation
of your release
6 SAP MaxDB For the database installation you decide how to distribute your system components
to disk
For more information see Distribution of SAP System Components to Disk in the installation documentation
of your release
7 IBM DB2 for Linux 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 release
8 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
9 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 49]
10 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
11 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
12 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
13 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
14 You can continue with Preparation [page 21]
Split Option ldquoKeep Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
CAUTION
Sybase Split option ldquoKeep Databaserdquo is not supported
3 Planning
31 Planning Checklist
1860 CUSTOMER 2012-11-27
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 19]
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 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 19]
System Landscape Directory (SLD)
You can ignore SLD parameters
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
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 49]
7 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
8 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
9 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
10 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
11 You can continue with Preparation [page 21]
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
3 Planning
32 User Management
2012-11-27 CUSTOMER 1960
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
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
2060 CUSTOMER 2012-11-27
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 You disable the Windows Server firewall on each host
For more information about disabling the Windows firewall see the relevant section in the
installation documentation of your release
2 You perform basic preparations on Windows
For more information see Performing Basic Windows Preparation Steps in the installation documentation
of your release
3 You check that you have the user authorization required for running the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
4 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
5 Only valid for HA (UNIX) |
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) |
6 If required you prepare the SAP system transport host for your SAP system
For more information see Preparing the SAP System Transport Host in the installation documentation
of your release
7 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
4 Preparation
41 Preparation Checklist
2012-11-27 CUSTOMER 2160
8 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 Dual Stack Split Installation Media [page 25]
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 |
9 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) |
10 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) |
11 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 22] of
the dual-stack system
12 You can continue with Splitting [page 27]
42 Performing a Full System Backup
NOTE
This section is not relevant if your database is Sybase
4 Preparation
42 Performing a Full System Backup
2260 CUSTOMER 2012-11-27
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
NOTE
If your system is a high-availability system make sure that you perform a backup of both cluster
nodes of the dual-stack system
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] for your release and database at
DatabaseSAP NetWeaver Release Path in Help Portal
SAP MaxDB SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for MaxDB
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 CapabilityGeneral 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
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for Oracle
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 CapabilityGeneral 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 Linux UNIX and Windows
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
4 Preparation
42 Performing a Full System Backup
2012-11-27 CUSTOMER 2360
DatabaseSAP NetWeaver Release Path in Help Portal
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 CapabilityGeneral 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 CapabilityGeneral 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 zOS
Microsoft SQL Server
SAP NetWeaver 70
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 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 CapabilityGeneral 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
2460 CUSTOMER 2012-11-27
43 Preparing the Dual Stack Split Installation Media
This section describes how to prepare the installation media that is required for the dual stack split
using the installer
Procedure
1 Download the installation media from the software distribution center on SAP Service Marketplace
using the following path
httpservicesapcomswdc Support Package and Patches A - Z Index S SL TOOLSET SL
TOOLSET 10 Entry by Component Dual-Stack Split
2 Create a download directory on the host on which you want to run the DualndashStack Split tool
3 Unpack the DualndashStack Split tool archive to a local directory using the following command
SAPCAR ndashxvf ltdownload directorygtltpathgtltArchivegtSAR -R ltunpack directorygt
4 Preparation
43 Preparing the Dual Stack Split Installation Media
2012-11-27 CUSTOMER 2560
This page is left blank for documents that are printed on both sides
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
NOTE
Sybase Split option ldquoKeep Databaserdquo is not supported You have to consider only the steps
described in section Move Java Database
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Oracle You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your release
2 Oracle If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your release
3 MS SQL Server You install the MS SQL Server database software
For more information see Installing the SQL Server Database Software in the installation documentation
of your release
4 You export the Java stack using the installer [page 29]
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 48]
5 You restart the source system
6 You run the installer [page 29] to install a Java only system using the export from the dual-stack
system
5 Splitting
51 Splitting Checklist
2012-11-27 CUSTOMER 2760
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 installer dialog
7 You continue with Follow-Up Activities [page 33]
Distributed System
1 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 release
2 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 release
3 On the database instance host of the dual-stack system you run the installer [page 29] to export the
Java database schema
4 On the central instance host of the dual-stack system you run the installer [page 29] 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 48]
5 You restart the source system
6 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
7 You run the installer [page 29] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
9 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2860 CUSTOMER 2012-11-27
Keep Database
1 On the central instance host of the dual-stack system you run the installer [page 29] to export 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 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 48]
2 You restart the source system
3 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
4 On the database instance host of the dual-stack system you run the installer [page 29] 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 the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
6 You continue with Follow-Up Activities [page 33]
52 Running the Installer
This section describes how to run the installer The installer includes a GUI client and a GUI server
which both use Java
The procedure describes an installation where the installer GUI client and GUI server are running on
the same host In the following GUI client and GUI server are addressed as ldquonstaller GUIrdquo
Useful Information About the Installer
When you start the installer it automatically starts the installer GUI
The installer creates the installation directory sapinst_instdir which is located directly in the
ProgramFiles directory If the installer is not able to create sapinst_instdir there it tries to
create sapinst_instdir in the directory defined by the environment variable TEMP
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 2960
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
The installer creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt which is located in ProgramFiles
The installer extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is
located in TEMP TMP TMPDIR or SystemRoot These files are deleted after the installer 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 the installer cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default port 21212 is used for communication between the installer
GUI server and the installer GUI client If this port is already in use you see an error message
In this case or if you want the installer to use a specific port open a command prompt and change
to the required directory to which you unpacked the DSS645_IM_ltplatformgtSAR file
Execute sapinstexe with the following command line parameter
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
To see a list of all available installer properties open a command prompt and start the installer
with command line parameter -p
sapinstexe -p
If you need to run the installer in accessibility mode make sure that you have activated and adjusted
accessibility settings as described in Running the Installer in Accessibility Mode in the installation
documentation of your release
If required you can stop the installer by choosing SAPinst Cancel in the installer GUI menu
Prerequisites
Make sure that you use an account with the required user authorization to run the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
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
the installer
Before you start the installer read SAP Note 1697164 which contains important information how
to run the installer
5 Splitting
52 Running the Installer
3060 CUSTOMER 2012-11-27
Procedure
1 Log on to the installation host using an account with the required user authorization to run the
installer
CAUTION
Do not use an existing ltsapsidgtadm user
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 Preparing the DualndashStack Split Installation Media [page 25]
3 Start the installer by double-clicking sapinstexe from the directory to which you unpacked the
DSS645_IM_ltplatformgtSAR file
NOTE
If you need to perform the installation in accessibility mode open a command prompt change
to the ltpath to unpack directorygt directory and execute sapinstexe ndashaccessible
For more information see Running the Installer in Accessibility Mode in the installation
documentation of your release
The GUI starts automatically by displaying the Welcome screen
4 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
CAUTION
Sybase Split options ldquoMove Java Databaserdquo and ldquoKeep Databaserdquo are not available in the
Welcome screen but only the steps valid for split option ldquoMove Java Databaserdquo are listed
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
5 Choose Next
6 If the installer prompts you to log off from your system log off and on again
The installer restarts automatically
7 Follow the instructions in the installer input screens and enter the required parameters
NOTE
If the installer 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 the installer displays the Parameter Summary
screen This screen shows both the parameters that you entered and those that the installer set by
default If required you can revise the parameters before starting the split procedure
8 To start the dual-stack split choose Start
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 3160
The installer starts and displays the progress of the split procedure
When the split option has finished successfully the installer displays the message Execution of
ltOption_Namegt has completed
CAUTION
Multiple Oracle Homes only The installer uses default values for the Oracle Home and
Listener configuration Therefore if you use multiple Oracle Homes you must specify the
new Oracle home as well as the listener port number You can change these values on the
installer Summary screen during the database instance installation On the Summary screen check
both Oracle gt Database System and Oracle gt Listener Configuration and use the Revise button On the
upcoming screen change the Oracle Home and the Listener port number Make sure that
you use a free port number and do not use the numbers 1521 or 1527 as these might already
be in use by default
9 We recommend that you delete the directory userprofilesdtgui
10 IBM DB2 for Linux and UNIX and Windows If not already done install the DB2 license
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
11 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running the Installer
3260 CUSTOMER 2012-11-27
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
Not valid for Sybase 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
httpservicesapcominstallnw70
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3360
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 the installer [page 29] 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 40] 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3460 CUSTOMER 2012-11-27
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 central instance host of the source system you run the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
12 On the database host of the source system you run the installer [page 29] to remove the Java database
schema
13 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
14 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
15 If required and not already done so you configure the CTS Deploy Web Service [page 40] on the ABAP
system
16 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3560
5 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 release
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
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 the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
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 40] on the ABAP
system
15 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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3660 CUSTOMER 2012-11-27
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
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-
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 strongly
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
SAP NetWeaver 74
For more information see SAP Note 1655335
If you no longer need the Java stack of your SAP dual-stack system you can use the Dual-Stack
Split 20 tool to remove it as described in Removing the Java Stack [page 51]
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
Heterogeneous 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 media 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
Sybase Split option ldquoKeep Databaserdquo is not supported Only the steps valid for option ldquoMove Java
Databaserdquo are available in the installation tool
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
1 Introduction
660 CUSTOMER 2012-11-27
Only valid for Microsoft Failover Clustering As of Windows Server 2008 the cluster feature is
called Failover Clustering For practical reasons we are continuing to use the previous terminology
Microsoft Cluster Service and abbreviation MSCS in some sections of this guide and the corresponding
installation documentation of your release
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
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
1769205 Dual-Stack Split 20 SP3 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 ltLanguagegt SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 1
httphelpsapcomnw701 Application Help SAP Library ltLanguagegt SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 2
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 3
httphelpsapcomnw703 Application Help SAP Library ltLanguagegt 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
1 Introduction
11 SAP Notes for the Dual-Stack Split
2012-11-27 CUSTOMER 760
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
CAUTION
Sybase Only the functionality of split option ldquoMove Java Databaserdquo is supported
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 17]
Preparation [page 21]
Splitting [page 27]
Follow-up Activities [page 33]
1 Introduction
13 How to Use this Guide
860 CUSTOMER 2012-11-27
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
CAUTION
Sybase Only the functionality of split option ldquoMove Java Databaserdquo is supported
Move Java Database [page 9]
Keep Database [page 12]
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)
Only valid for Microsoft Failover Clustering If your system is a high-availability system with
Microsoft Failover Clustering (previously known as MSCS) the split option ldquoMove Java Databaserdquo offers
the possibility to split a clustered dual-stack system into one ABAP cluster system and one Java cluster
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 the installer 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 the
installer removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
2012-11-27 CUSTOMER 960
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 the installer 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 the
installer removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
1060 CUSTOMER 2012-11-27
Figure 2 Split Option Move Java Database for Distributed System
Move Java Database for High-Availability Systems
When you choose the ldquoMove Java Databaserdquo option for a high-availability system the installer exports
the Java stack of the dual-stack cluster system and uses this export to reinstall all mandatory instances
on a separate cluster system for Java
These are the mandatory instances
Central services instance for Java (SCS)
Enqueue replication server instance (ERS instance) for the SCS instance
Database instance (DB)
Central instance
Dialog instance
After the installation has finished and the System Landscape Directory has been reconfigured the
installer removes all Java parts from the dual-stack cluster system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
2012-11-27 CUSTOMER 1160
Figure 3 Split Option Move Java Database for High-Availability System
22 Split Option Keep Database
CAUTION
Sybase The functionality of split option ldquoKeep Databaserdquo is not supported
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)
Only valid for Microsoft Failover Clustering If your system is a high-availability system with
Microsoft Failover Clustering (MSCS) the split option ldquoKeep Databaserdquo offers the possibility to split a
clustered dual-stack system into one ABAP cluster system and one Java cluster system both using the
same database (MCOD)
Keep Database for Central and Distributed Systems
When you choose the ldquoKeep Databaserdquo option the installer 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 the installer 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 the
installer 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
1260 CUSTOMER 2012-11-27
Figure 4 Split Option Keep Database for Central Systems
Figure 5 Split Option Keep Database for Distributed Systems
Keep Database for High-Availability Systems
When you choose the ldquoKeep Databaserdquo option for a high-availability system you can choose between
the following scenarios
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-11-27 CUSTOMER 1360
Move SCS to New or Other Cluster
The installer exports the Java stack of the dual-stack cluster system and uses this export to install
a central services instance and a central instance on a separate cluster system for Java Additionally
the installer adapts the Java schema of the database of the former dual-stack cluster system to the
target Java cluster system
Figure 6 Split Option Keep Database for High-Availability Systems mdash Move SCS to New or Other
Cluster
Keep SCS on the Source Cluster System
The installer exports the Java central services instance of the source cluster system and uses this
export to install the SCS with a new system ID in a separate cluster on the target cluster system
Additionally the installer adapts the Java schema of the database to the target Java SID
NOTE
This scenario is supported as of Windows Server 2008
2 Split Options Covered by this Guide
22 Split Option Keep Database
1460 CUSTOMER 2012-11-27
Figure 7 Split Option Keep Database for High-Availability Systems mdash Keep SCS on the Source
Cluster System
After the installation has finished and the System Landscape Directory has been reconfigured the
installer removes all Java parts from the dual-stack cluster system except the Java database schema
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-11-27 CUSTOMER 1560
This page is left blank for documents that are printed on both sides
3 Planning
31 Planning Checklist
RECOMMENDATION
We recommend that you first perform the dual-stack split procedure in a test system to identify
possible further application-specific post-split activities required for your scenario
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 19]
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 19]
System Landscape Directory (SLD)
You can ignore SLD parameters
Oracle SAP System Database Parameters Java database schema
3 Planning
31 Planning Checklist
2012-11-27 CUSTOMER 1760
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
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 administrator
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
5 MS SQL Server Oracle For the database installation you decide how to distribute your database
components to disk
For more information see Distribution of SAP System Components to Disk in the installation documentation
of your release
6 SAP MaxDB For the database installation you decide how to distribute your system components
to disk
For more information see Distribution of SAP System Components to Disk in the installation documentation
of your release
7 IBM DB2 for Linux 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 release
8 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
9 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 49]
10 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
11 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
12 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
13 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
14 You can continue with Preparation [page 21]
Split Option ldquoKeep Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
CAUTION
Sybase Split option ldquoKeep Databaserdquo is not supported
3 Planning
31 Planning Checklist
1860 CUSTOMER 2012-11-27
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 19]
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 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 19]
System Landscape Directory (SLD)
You can ignore SLD parameters
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
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 49]
7 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
8 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
9 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
10 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
11 You can continue with Preparation [page 21]
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
3 Planning
32 User Management
2012-11-27 CUSTOMER 1960
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
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
2060 CUSTOMER 2012-11-27
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 You disable the Windows Server firewall on each host
For more information about disabling the Windows firewall see the relevant section in the
installation documentation of your release
2 You perform basic preparations on Windows
For more information see Performing Basic Windows Preparation Steps in the installation documentation
of your release
3 You check that you have the user authorization required for running the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
4 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
5 Only valid for HA (UNIX) |
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) |
6 If required you prepare the SAP system transport host for your SAP system
For more information see Preparing the SAP System Transport Host in the installation documentation
of your release
7 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
4 Preparation
41 Preparation Checklist
2012-11-27 CUSTOMER 2160
8 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 Dual Stack Split Installation Media [page 25]
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 |
9 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) |
10 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) |
11 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 22] of
the dual-stack system
12 You can continue with Splitting [page 27]
42 Performing a Full System Backup
NOTE
This section is not relevant if your database is Sybase
4 Preparation
42 Performing a Full System Backup
2260 CUSTOMER 2012-11-27
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
NOTE
If your system is a high-availability system make sure that you perform a backup of both cluster
nodes of the dual-stack system
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] for your release and database at
DatabaseSAP NetWeaver Release Path in Help Portal
SAP MaxDB SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for MaxDB
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 CapabilityGeneral 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
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for Oracle
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 CapabilityGeneral 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 Linux UNIX and Windows
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
4 Preparation
42 Performing a Full System Backup
2012-11-27 CUSTOMER 2360
DatabaseSAP NetWeaver Release Path in Help Portal
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 CapabilityGeneral 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 CapabilityGeneral 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 zOS
Microsoft SQL Server
SAP NetWeaver 70
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 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 CapabilityGeneral 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
2460 CUSTOMER 2012-11-27
43 Preparing the Dual Stack Split Installation Media
This section describes how to prepare the installation media that is required for the dual stack split
using the installer
Procedure
1 Download the installation media from the software distribution center on SAP Service Marketplace
using the following path
httpservicesapcomswdc Support Package and Patches A - Z Index S SL TOOLSET SL
TOOLSET 10 Entry by Component Dual-Stack Split
2 Create a download directory on the host on which you want to run the DualndashStack Split tool
3 Unpack the DualndashStack Split tool archive to a local directory using the following command
SAPCAR ndashxvf ltdownload directorygtltpathgtltArchivegtSAR -R ltunpack directorygt
4 Preparation
43 Preparing the Dual Stack Split Installation Media
2012-11-27 CUSTOMER 2560
This page is left blank for documents that are printed on both sides
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
NOTE
Sybase Split option ldquoKeep Databaserdquo is not supported You have to consider only the steps
described in section Move Java Database
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Oracle You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your release
2 Oracle If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your release
3 MS SQL Server You install the MS SQL Server database software
For more information see Installing the SQL Server Database Software in the installation documentation
of your release
4 You export the Java stack using the installer [page 29]
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 48]
5 You restart the source system
6 You run the installer [page 29] to install a Java only system using the export from the dual-stack
system
5 Splitting
51 Splitting Checklist
2012-11-27 CUSTOMER 2760
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 installer dialog
7 You continue with Follow-Up Activities [page 33]
Distributed System
1 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 release
2 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 release
3 On the database instance host of the dual-stack system you run the installer [page 29] to export the
Java database schema
4 On the central instance host of the dual-stack system you run the installer [page 29] 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 48]
5 You restart the source system
6 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
7 You run the installer [page 29] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
9 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2860 CUSTOMER 2012-11-27
Keep Database
1 On the central instance host of the dual-stack system you run the installer [page 29] to export 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 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 48]
2 You restart the source system
3 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
4 On the database instance host of the dual-stack system you run the installer [page 29] 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 the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
6 You continue with Follow-Up Activities [page 33]
52 Running the Installer
This section describes how to run the installer The installer includes a GUI client and a GUI server
which both use Java
The procedure describes an installation where the installer GUI client and GUI server are running on
the same host In the following GUI client and GUI server are addressed as ldquonstaller GUIrdquo
Useful Information About the Installer
When you start the installer it automatically starts the installer GUI
The installer creates the installation directory sapinst_instdir which is located directly in the
ProgramFiles directory If the installer is not able to create sapinst_instdir there it tries to
create sapinst_instdir in the directory defined by the environment variable TEMP
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 2960
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
The installer creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt which is located in ProgramFiles
The installer extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is
located in TEMP TMP TMPDIR or SystemRoot These files are deleted after the installer 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 the installer cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default port 21212 is used for communication between the installer
GUI server and the installer GUI client If this port is already in use you see an error message
In this case or if you want the installer to use a specific port open a command prompt and change
to the required directory to which you unpacked the DSS645_IM_ltplatformgtSAR file
Execute sapinstexe with the following command line parameter
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
To see a list of all available installer properties open a command prompt and start the installer
with command line parameter -p
sapinstexe -p
If you need to run the installer in accessibility mode make sure that you have activated and adjusted
accessibility settings as described in Running the Installer in Accessibility Mode in the installation
documentation of your release
If required you can stop the installer by choosing SAPinst Cancel in the installer GUI menu
Prerequisites
Make sure that you use an account with the required user authorization to run the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
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
the installer
Before you start the installer read SAP Note 1697164 which contains important information how
to run the installer
5 Splitting
52 Running the Installer
3060 CUSTOMER 2012-11-27
Procedure
1 Log on to the installation host using an account with the required user authorization to run the
installer
CAUTION
Do not use an existing ltsapsidgtadm user
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 Preparing the DualndashStack Split Installation Media [page 25]
3 Start the installer by double-clicking sapinstexe from the directory to which you unpacked the
DSS645_IM_ltplatformgtSAR file
NOTE
If you need to perform the installation in accessibility mode open a command prompt change
to the ltpath to unpack directorygt directory and execute sapinstexe ndashaccessible
For more information see Running the Installer in Accessibility Mode in the installation
documentation of your release
The GUI starts automatically by displaying the Welcome screen
4 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
CAUTION
Sybase Split options ldquoMove Java Databaserdquo and ldquoKeep Databaserdquo are not available in the
Welcome screen but only the steps valid for split option ldquoMove Java Databaserdquo are listed
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
5 Choose Next
6 If the installer prompts you to log off from your system log off and on again
The installer restarts automatically
7 Follow the instructions in the installer input screens and enter the required parameters
NOTE
If the installer 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 the installer displays the Parameter Summary
screen This screen shows both the parameters that you entered and those that the installer set by
default If required you can revise the parameters before starting the split procedure
8 To start the dual-stack split choose Start
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 3160
The installer starts and displays the progress of the split procedure
When the split option has finished successfully the installer displays the message Execution of
ltOption_Namegt has completed
CAUTION
Multiple Oracle Homes only The installer uses default values for the Oracle Home and
Listener configuration Therefore if you use multiple Oracle Homes you must specify the
new Oracle home as well as the listener port number You can change these values on the
installer Summary screen during the database instance installation On the Summary screen check
both Oracle gt Database System and Oracle gt Listener Configuration and use the Revise button On the
upcoming screen change the Oracle Home and the Listener port number Make sure that
you use a free port number and do not use the numbers 1521 or 1527 as these might already
be in use by default
9 We recommend that you delete the directory userprofilesdtgui
10 IBM DB2 for Linux and UNIX and Windows If not already done install the DB2 license
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
11 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running the Installer
3260 CUSTOMER 2012-11-27
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
Not valid for Sybase 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
httpservicesapcominstallnw70
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3360
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 the installer [page 29] 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 40] 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3460 CUSTOMER 2012-11-27
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 central instance host of the source system you run the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
12 On the database host of the source system you run the installer [page 29] to remove the Java database
schema
13 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
14 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
15 If required and not already done so you configure the CTS Deploy Web Service [page 40] on the ABAP
system
16 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3560
5 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 release
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
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 the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
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 40] on the ABAP
system
15 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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3660 CUSTOMER 2012-11-27
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
Only valid for Microsoft Failover Clustering As of Windows Server 2008 the cluster feature is
called Failover Clustering For practical reasons we are continuing to use the previous terminology
Microsoft Cluster Service and abbreviation MSCS in some sections of this guide and the corresponding
installation documentation of your release
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
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
1769205 Dual-Stack Split 20 SP3 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 ltLanguagegt SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 1
httphelpsapcomnw701 Application Help SAP Library ltLanguagegt SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 2
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
SAP NetWeaver 70 including Enhancement Package 3
httphelpsapcomnw703 Application Help SAP Library ltLanguagegt 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
1 Introduction
11 SAP Notes for the Dual-Stack Split
2012-11-27 CUSTOMER 760
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
CAUTION
Sybase Only the functionality of split option ldquoMove Java Databaserdquo is supported
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 17]
Preparation [page 21]
Splitting [page 27]
Follow-up Activities [page 33]
1 Introduction
13 How to Use this Guide
860 CUSTOMER 2012-11-27
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
CAUTION
Sybase Only the functionality of split option ldquoMove Java Databaserdquo is supported
Move Java Database [page 9]
Keep Database [page 12]
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)
Only valid for Microsoft Failover Clustering If your system is a high-availability system with
Microsoft Failover Clustering (previously known as MSCS) the split option ldquoMove Java Databaserdquo offers
the possibility to split a clustered dual-stack system into one ABAP cluster system and one Java cluster
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 the installer 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 the
installer removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
2012-11-27 CUSTOMER 960
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 the installer 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 the
installer removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
1060 CUSTOMER 2012-11-27
Figure 2 Split Option Move Java Database for Distributed System
Move Java Database for High-Availability Systems
When you choose the ldquoMove Java Databaserdquo option for a high-availability system the installer exports
the Java stack of the dual-stack cluster system and uses this export to reinstall all mandatory instances
on a separate cluster system for Java
These are the mandatory instances
Central services instance for Java (SCS)
Enqueue replication server instance (ERS instance) for the SCS instance
Database instance (DB)
Central instance
Dialog instance
After the installation has finished and the System Landscape Directory has been reconfigured the
installer removes all Java parts from the dual-stack cluster system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
2012-11-27 CUSTOMER 1160
Figure 3 Split Option Move Java Database for High-Availability System
22 Split Option Keep Database
CAUTION
Sybase The functionality of split option ldquoKeep Databaserdquo is not supported
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)
Only valid for Microsoft Failover Clustering If your system is a high-availability system with
Microsoft Failover Clustering (MSCS) the split option ldquoKeep Databaserdquo offers the possibility to split a
clustered dual-stack system into one ABAP cluster system and one Java cluster system both using the
same database (MCOD)
Keep Database for Central and Distributed Systems
When you choose the ldquoKeep Databaserdquo option the installer 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 the installer 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 the
installer 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
1260 CUSTOMER 2012-11-27
Figure 4 Split Option Keep Database for Central Systems
Figure 5 Split Option Keep Database for Distributed Systems
Keep Database for High-Availability Systems
When you choose the ldquoKeep Databaserdquo option for a high-availability system you can choose between
the following scenarios
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-11-27 CUSTOMER 1360
Move SCS to New or Other Cluster
The installer exports the Java stack of the dual-stack cluster system and uses this export to install
a central services instance and a central instance on a separate cluster system for Java Additionally
the installer adapts the Java schema of the database of the former dual-stack cluster system to the
target Java cluster system
Figure 6 Split Option Keep Database for High-Availability Systems mdash Move SCS to New or Other
Cluster
Keep SCS on the Source Cluster System
The installer exports the Java central services instance of the source cluster system and uses this
export to install the SCS with a new system ID in a separate cluster on the target cluster system
Additionally the installer adapts the Java schema of the database to the target Java SID
NOTE
This scenario is supported as of Windows Server 2008
2 Split Options Covered by this Guide
22 Split Option Keep Database
1460 CUSTOMER 2012-11-27
Figure 7 Split Option Keep Database for High-Availability Systems mdash Keep SCS on the Source
Cluster System
After the installation has finished and the System Landscape Directory has been reconfigured the
installer removes all Java parts from the dual-stack cluster system except the Java database schema
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-11-27 CUSTOMER 1560
This page is left blank for documents that are printed on both sides
3 Planning
31 Planning Checklist
RECOMMENDATION
We recommend that you first perform the dual-stack split procedure in a test system to identify
possible further application-specific post-split activities required for your scenario
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 19]
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 19]
System Landscape Directory (SLD)
You can ignore SLD parameters
Oracle SAP System Database Parameters Java database schema
3 Planning
31 Planning Checklist
2012-11-27 CUSTOMER 1760
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
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 administrator
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
5 MS SQL Server Oracle For the database installation you decide how to distribute your database
components to disk
For more information see Distribution of SAP System Components to Disk in the installation documentation
of your release
6 SAP MaxDB For the database installation you decide how to distribute your system components
to disk
For more information see Distribution of SAP System Components to Disk in the installation documentation
of your release
7 IBM DB2 for Linux 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 release
8 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
9 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 49]
10 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
11 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
12 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
13 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
14 You can continue with Preparation [page 21]
Split Option ldquoKeep Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
CAUTION
Sybase Split option ldquoKeep Databaserdquo is not supported
3 Planning
31 Planning Checklist
1860 CUSTOMER 2012-11-27
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 19]
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 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 19]
System Landscape Directory (SLD)
You can ignore SLD parameters
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
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 49]
7 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
8 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
9 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
10 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
11 You can continue with Preparation [page 21]
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
3 Planning
32 User Management
2012-11-27 CUSTOMER 1960
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
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
2060 CUSTOMER 2012-11-27
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 You disable the Windows Server firewall on each host
For more information about disabling the Windows firewall see the relevant section in the
installation documentation of your release
2 You perform basic preparations on Windows
For more information see Performing Basic Windows Preparation Steps in the installation documentation
of your release
3 You check that you have the user authorization required for running the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
4 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
5 Only valid for HA (UNIX) |
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) |
6 If required you prepare the SAP system transport host for your SAP system
For more information see Preparing the SAP System Transport Host in the installation documentation
of your release
7 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
4 Preparation
41 Preparation Checklist
2012-11-27 CUSTOMER 2160
8 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 Dual Stack Split Installation Media [page 25]
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 |
9 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) |
10 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) |
11 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 22] of
the dual-stack system
12 You can continue with Splitting [page 27]
42 Performing a Full System Backup
NOTE
This section is not relevant if your database is Sybase
4 Preparation
42 Performing a Full System Backup
2260 CUSTOMER 2012-11-27
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
NOTE
If your system is a high-availability system make sure that you perform a backup of both cluster
nodes of the dual-stack system
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] for your release and database at
DatabaseSAP NetWeaver Release Path in Help Portal
SAP MaxDB SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for MaxDB
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 CapabilityGeneral 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
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for Oracle
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 CapabilityGeneral 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 Linux UNIX and Windows
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
4 Preparation
42 Performing a Full System Backup
2012-11-27 CUSTOMER 2360
DatabaseSAP NetWeaver Release Path in Help Portal
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 CapabilityGeneral 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 CapabilityGeneral 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 zOS
Microsoft SQL Server
SAP NetWeaver 70
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 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 CapabilityGeneral 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
2460 CUSTOMER 2012-11-27
43 Preparing the Dual Stack Split Installation Media
This section describes how to prepare the installation media that is required for the dual stack split
using the installer
Procedure
1 Download the installation media from the software distribution center on SAP Service Marketplace
using the following path
httpservicesapcomswdc Support Package and Patches A - Z Index S SL TOOLSET SL
TOOLSET 10 Entry by Component Dual-Stack Split
2 Create a download directory on the host on which you want to run the DualndashStack Split tool
3 Unpack the DualndashStack Split tool archive to a local directory using the following command
SAPCAR ndashxvf ltdownload directorygtltpathgtltArchivegtSAR -R ltunpack directorygt
4 Preparation
43 Preparing the Dual Stack Split Installation Media
2012-11-27 CUSTOMER 2560
This page is left blank for documents that are printed on both sides
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
NOTE
Sybase Split option ldquoKeep Databaserdquo is not supported You have to consider only the steps
described in section Move Java Database
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Oracle You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your release
2 Oracle If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your release
3 MS SQL Server You install the MS SQL Server database software
For more information see Installing the SQL Server Database Software in the installation documentation
of your release
4 You export the Java stack using the installer [page 29]
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 48]
5 You restart the source system
6 You run the installer [page 29] to install a Java only system using the export from the dual-stack
system
5 Splitting
51 Splitting Checklist
2012-11-27 CUSTOMER 2760
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 installer dialog
7 You continue with Follow-Up Activities [page 33]
Distributed System
1 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 release
2 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 release
3 On the database instance host of the dual-stack system you run the installer [page 29] to export the
Java database schema
4 On the central instance host of the dual-stack system you run the installer [page 29] 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 48]
5 You restart the source system
6 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
7 You run the installer [page 29] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
9 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2860 CUSTOMER 2012-11-27
Keep Database
1 On the central instance host of the dual-stack system you run the installer [page 29] to export 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 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 48]
2 You restart the source system
3 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
4 On the database instance host of the dual-stack system you run the installer [page 29] 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 the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
6 You continue with Follow-Up Activities [page 33]
52 Running the Installer
This section describes how to run the installer The installer includes a GUI client and a GUI server
which both use Java
The procedure describes an installation where the installer GUI client and GUI server are running on
the same host In the following GUI client and GUI server are addressed as ldquonstaller GUIrdquo
Useful Information About the Installer
When you start the installer it automatically starts the installer GUI
The installer creates the installation directory sapinst_instdir which is located directly in the
ProgramFiles directory If the installer is not able to create sapinst_instdir there it tries to
create sapinst_instdir in the directory defined by the environment variable TEMP
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 2960
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
The installer creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt which is located in ProgramFiles
The installer extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is
located in TEMP TMP TMPDIR or SystemRoot These files are deleted after the installer 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 the installer cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default port 21212 is used for communication between the installer
GUI server and the installer GUI client If this port is already in use you see an error message
In this case or if you want the installer to use a specific port open a command prompt and change
to the required directory to which you unpacked the DSS645_IM_ltplatformgtSAR file
Execute sapinstexe with the following command line parameter
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
To see a list of all available installer properties open a command prompt and start the installer
with command line parameter -p
sapinstexe -p
If you need to run the installer in accessibility mode make sure that you have activated and adjusted
accessibility settings as described in Running the Installer in Accessibility Mode in the installation
documentation of your release
If required you can stop the installer by choosing SAPinst Cancel in the installer GUI menu
Prerequisites
Make sure that you use an account with the required user authorization to run the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
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
the installer
Before you start the installer read SAP Note 1697164 which contains important information how
to run the installer
5 Splitting
52 Running the Installer
3060 CUSTOMER 2012-11-27
Procedure
1 Log on to the installation host using an account with the required user authorization to run the
installer
CAUTION
Do not use an existing ltsapsidgtadm user
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 Preparing the DualndashStack Split Installation Media [page 25]
3 Start the installer by double-clicking sapinstexe from the directory to which you unpacked the
DSS645_IM_ltplatformgtSAR file
NOTE
If you need to perform the installation in accessibility mode open a command prompt change
to the ltpath to unpack directorygt directory and execute sapinstexe ndashaccessible
For more information see Running the Installer in Accessibility Mode in the installation
documentation of your release
The GUI starts automatically by displaying the Welcome screen
4 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
CAUTION
Sybase Split options ldquoMove Java Databaserdquo and ldquoKeep Databaserdquo are not available in the
Welcome screen but only the steps valid for split option ldquoMove Java Databaserdquo are listed
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
5 Choose Next
6 If the installer prompts you to log off from your system log off and on again
The installer restarts automatically
7 Follow the instructions in the installer input screens and enter the required parameters
NOTE
If the installer 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 the installer displays the Parameter Summary
screen This screen shows both the parameters that you entered and those that the installer set by
default If required you can revise the parameters before starting the split procedure
8 To start the dual-stack split choose Start
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 3160
The installer starts and displays the progress of the split procedure
When the split option has finished successfully the installer displays the message Execution of
ltOption_Namegt has completed
CAUTION
Multiple Oracle Homes only The installer uses default values for the Oracle Home and
Listener configuration Therefore if you use multiple Oracle Homes you must specify the
new Oracle home as well as the listener port number You can change these values on the
installer Summary screen during the database instance installation On the Summary screen check
both Oracle gt Database System and Oracle gt Listener Configuration and use the Revise button On the
upcoming screen change the Oracle Home and the Listener port number Make sure that
you use a free port number and do not use the numbers 1521 or 1527 as these might already
be in use by default
9 We recommend that you delete the directory userprofilesdtgui
10 IBM DB2 for Linux and UNIX and Windows If not already done install the DB2 license
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
11 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running the Installer
3260 CUSTOMER 2012-11-27
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
Not valid for Sybase 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
httpservicesapcominstallnw70
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3360
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 the installer [page 29] 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 40] 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3460 CUSTOMER 2012-11-27
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 central instance host of the source system you run the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
12 On the database host of the source system you run the installer [page 29] to remove the Java database
schema
13 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
14 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
15 If required and not already done so you configure the CTS Deploy Web Service [page 40] on the ABAP
system
16 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3560
5 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 release
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
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 the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
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 40] on the ABAP
system
15 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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3660 CUSTOMER 2012-11-27
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
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
CAUTION
Sybase Only the functionality of split option ldquoMove Java Databaserdquo is supported
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 17]
Preparation [page 21]
Splitting [page 27]
Follow-up Activities [page 33]
1 Introduction
13 How to Use this Guide
860 CUSTOMER 2012-11-27
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
CAUTION
Sybase Only the functionality of split option ldquoMove Java Databaserdquo is supported
Move Java Database [page 9]
Keep Database [page 12]
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)
Only valid for Microsoft Failover Clustering If your system is a high-availability system with
Microsoft Failover Clustering (previously known as MSCS) the split option ldquoMove Java Databaserdquo offers
the possibility to split a clustered dual-stack system into one ABAP cluster system and one Java cluster
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 the installer 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 the
installer removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
2012-11-27 CUSTOMER 960
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 the installer 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 the
installer removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
1060 CUSTOMER 2012-11-27
Figure 2 Split Option Move Java Database for Distributed System
Move Java Database for High-Availability Systems
When you choose the ldquoMove Java Databaserdquo option for a high-availability system the installer exports
the Java stack of the dual-stack cluster system and uses this export to reinstall all mandatory instances
on a separate cluster system for Java
These are the mandatory instances
Central services instance for Java (SCS)
Enqueue replication server instance (ERS instance) for the SCS instance
Database instance (DB)
Central instance
Dialog instance
After the installation has finished and the System Landscape Directory has been reconfigured the
installer removes all Java parts from the dual-stack cluster system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
2012-11-27 CUSTOMER 1160
Figure 3 Split Option Move Java Database for High-Availability System
22 Split Option Keep Database
CAUTION
Sybase The functionality of split option ldquoKeep Databaserdquo is not supported
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)
Only valid for Microsoft Failover Clustering If your system is a high-availability system with
Microsoft Failover Clustering (MSCS) the split option ldquoKeep Databaserdquo offers the possibility to split a
clustered dual-stack system into one ABAP cluster system and one Java cluster system both using the
same database (MCOD)
Keep Database for Central and Distributed Systems
When you choose the ldquoKeep Databaserdquo option the installer 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 the installer 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 the
installer 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
1260 CUSTOMER 2012-11-27
Figure 4 Split Option Keep Database for Central Systems
Figure 5 Split Option Keep Database for Distributed Systems
Keep Database for High-Availability Systems
When you choose the ldquoKeep Databaserdquo option for a high-availability system you can choose between
the following scenarios
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-11-27 CUSTOMER 1360
Move SCS to New or Other Cluster
The installer exports the Java stack of the dual-stack cluster system and uses this export to install
a central services instance and a central instance on a separate cluster system for Java Additionally
the installer adapts the Java schema of the database of the former dual-stack cluster system to the
target Java cluster system
Figure 6 Split Option Keep Database for High-Availability Systems mdash Move SCS to New or Other
Cluster
Keep SCS on the Source Cluster System
The installer exports the Java central services instance of the source cluster system and uses this
export to install the SCS with a new system ID in a separate cluster on the target cluster system
Additionally the installer adapts the Java schema of the database to the target Java SID
NOTE
This scenario is supported as of Windows Server 2008
2 Split Options Covered by this Guide
22 Split Option Keep Database
1460 CUSTOMER 2012-11-27
Figure 7 Split Option Keep Database for High-Availability Systems mdash Keep SCS on the Source
Cluster System
After the installation has finished and the System Landscape Directory has been reconfigured the
installer removes all Java parts from the dual-stack cluster system except the Java database schema
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-11-27 CUSTOMER 1560
This page is left blank for documents that are printed on both sides
3 Planning
31 Planning Checklist
RECOMMENDATION
We recommend that you first perform the dual-stack split procedure in a test system to identify
possible further application-specific post-split activities required for your scenario
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 19]
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 19]
System Landscape Directory (SLD)
You can ignore SLD parameters
Oracle SAP System Database Parameters Java database schema
3 Planning
31 Planning Checklist
2012-11-27 CUSTOMER 1760
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
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 administrator
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
5 MS SQL Server Oracle For the database installation you decide how to distribute your database
components to disk
For more information see Distribution of SAP System Components to Disk in the installation documentation
of your release
6 SAP MaxDB For the database installation you decide how to distribute your system components
to disk
For more information see Distribution of SAP System Components to Disk in the installation documentation
of your release
7 IBM DB2 for Linux 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 release
8 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
9 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 49]
10 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
11 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
12 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
13 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
14 You can continue with Preparation [page 21]
Split Option ldquoKeep Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
CAUTION
Sybase Split option ldquoKeep Databaserdquo is not supported
3 Planning
31 Planning Checklist
1860 CUSTOMER 2012-11-27
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 19]
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 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 19]
System Landscape Directory (SLD)
You can ignore SLD parameters
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
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 49]
7 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
8 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
9 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
10 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
11 You can continue with Preparation [page 21]
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
3 Planning
32 User Management
2012-11-27 CUSTOMER 1960
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
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
2060 CUSTOMER 2012-11-27
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 You disable the Windows Server firewall on each host
For more information about disabling the Windows firewall see the relevant section in the
installation documentation of your release
2 You perform basic preparations on Windows
For more information see Performing Basic Windows Preparation Steps in the installation documentation
of your release
3 You check that you have the user authorization required for running the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
4 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
5 Only valid for HA (UNIX) |
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) |
6 If required you prepare the SAP system transport host for your SAP system
For more information see Preparing the SAP System Transport Host in the installation documentation
of your release
7 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
4 Preparation
41 Preparation Checklist
2012-11-27 CUSTOMER 2160
8 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 Dual Stack Split Installation Media [page 25]
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 |
9 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) |
10 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) |
11 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 22] of
the dual-stack system
12 You can continue with Splitting [page 27]
42 Performing a Full System Backup
NOTE
This section is not relevant if your database is Sybase
4 Preparation
42 Performing a Full System Backup
2260 CUSTOMER 2012-11-27
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
NOTE
If your system is a high-availability system make sure that you perform a backup of both cluster
nodes of the dual-stack system
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] for your release and database at
DatabaseSAP NetWeaver Release Path in Help Portal
SAP MaxDB SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for MaxDB
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 CapabilityGeneral 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
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for Oracle
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 CapabilityGeneral 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 Linux UNIX and Windows
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
4 Preparation
42 Performing a Full System Backup
2012-11-27 CUSTOMER 2360
DatabaseSAP NetWeaver Release Path in Help Portal
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 CapabilityGeneral 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 CapabilityGeneral 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 zOS
Microsoft SQL Server
SAP NetWeaver 70
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 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 CapabilityGeneral 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
2460 CUSTOMER 2012-11-27
43 Preparing the Dual Stack Split Installation Media
This section describes how to prepare the installation media that is required for the dual stack split
using the installer
Procedure
1 Download the installation media from the software distribution center on SAP Service Marketplace
using the following path
httpservicesapcomswdc Support Package and Patches A - Z Index S SL TOOLSET SL
TOOLSET 10 Entry by Component Dual-Stack Split
2 Create a download directory on the host on which you want to run the DualndashStack Split tool
3 Unpack the DualndashStack Split tool archive to a local directory using the following command
SAPCAR ndashxvf ltdownload directorygtltpathgtltArchivegtSAR -R ltunpack directorygt
4 Preparation
43 Preparing the Dual Stack Split Installation Media
2012-11-27 CUSTOMER 2560
This page is left blank for documents that are printed on both sides
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
NOTE
Sybase Split option ldquoKeep Databaserdquo is not supported You have to consider only the steps
described in section Move Java Database
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Oracle You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your release
2 Oracle If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your release
3 MS SQL Server You install the MS SQL Server database software
For more information see Installing the SQL Server Database Software in the installation documentation
of your release
4 You export the Java stack using the installer [page 29]
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 48]
5 You restart the source system
6 You run the installer [page 29] to install a Java only system using the export from the dual-stack
system
5 Splitting
51 Splitting Checklist
2012-11-27 CUSTOMER 2760
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 installer dialog
7 You continue with Follow-Up Activities [page 33]
Distributed System
1 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 release
2 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 release
3 On the database instance host of the dual-stack system you run the installer [page 29] to export the
Java database schema
4 On the central instance host of the dual-stack system you run the installer [page 29] 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 48]
5 You restart the source system
6 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
7 You run the installer [page 29] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
9 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2860 CUSTOMER 2012-11-27
Keep Database
1 On the central instance host of the dual-stack system you run the installer [page 29] to export 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 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 48]
2 You restart the source system
3 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
4 On the database instance host of the dual-stack system you run the installer [page 29] 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 the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
6 You continue with Follow-Up Activities [page 33]
52 Running the Installer
This section describes how to run the installer The installer includes a GUI client and a GUI server
which both use Java
The procedure describes an installation where the installer GUI client and GUI server are running on
the same host In the following GUI client and GUI server are addressed as ldquonstaller GUIrdquo
Useful Information About the Installer
When you start the installer it automatically starts the installer GUI
The installer creates the installation directory sapinst_instdir which is located directly in the
ProgramFiles directory If the installer is not able to create sapinst_instdir there it tries to
create sapinst_instdir in the directory defined by the environment variable TEMP
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 2960
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
The installer creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt which is located in ProgramFiles
The installer extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is
located in TEMP TMP TMPDIR or SystemRoot These files are deleted after the installer 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 the installer cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default port 21212 is used for communication between the installer
GUI server and the installer GUI client If this port is already in use you see an error message
In this case or if you want the installer to use a specific port open a command prompt and change
to the required directory to which you unpacked the DSS645_IM_ltplatformgtSAR file
Execute sapinstexe with the following command line parameter
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
To see a list of all available installer properties open a command prompt and start the installer
with command line parameter -p
sapinstexe -p
If you need to run the installer in accessibility mode make sure that you have activated and adjusted
accessibility settings as described in Running the Installer in Accessibility Mode in the installation
documentation of your release
If required you can stop the installer by choosing SAPinst Cancel in the installer GUI menu
Prerequisites
Make sure that you use an account with the required user authorization to run the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
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
the installer
Before you start the installer read SAP Note 1697164 which contains important information how
to run the installer
5 Splitting
52 Running the Installer
3060 CUSTOMER 2012-11-27
Procedure
1 Log on to the installation host using an account with the required user authorization to run the
installer
CAUTION
Do not use an existing ltsapsidgtadm user
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 Preparing the DualndashStack Split Installation Media [page 25]
3 Start the installer by double-clicking sapinstexe from the directory to which you unpacked the
DSS645_IM_ltplatformgtSAR file
NOTE
If you need to perform the installation in accessibility mode open a command prompt change
to the ltpath to unpack directorygt directory and execute sapinstexe ndashaccessible
For more information see Running the Installer in Accessibility Mode in the installation
documentation of your release
The GUI starts automatically by displaying the Welcome screen
4 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
CAUTION
Sybase Split options ldquoMove Java Databaserdquo and ldquoKeep Databaserdquo are not available in the
Welcome screen but only the steps valid for split option ldquoMove Java Databaserdquo are listed
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
5 Choose Next
6 If the installer prompts you to log off from your system log off and on again
The installer restarts automatically
7 Follow the instructions in the installer input screens and enter the required parameters
NOTE
If the installer 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 the installer displays the Parameter Summary
screen This screen shows both the parameters that you entered and those that the installer set by
default If required you can revise the parameters before starting the split procedure
8 To start the dual-stack split choose Start
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 3160
The installer starts and displays the progress of the split procedure
When the split option has finished successfully the installer displays the message Execution of
ltOption_Namegt has completed
CAUTION
Multiple Oracle Homes only The installer uses default values for the Oracle Home and
Listener configuration Therefore if you use multiple Oracle Homes you must specify the
new Oracle home as well as the listener port number You can change these values on the
installer Summary screen during the database instance installation On the Summary screen check
both Oracle gt Database System and Oracle gt Listener Configuration and use the Revise button On the
upcoming screen change the Oracle Home and the Listener port number Make sure that
you use a free port number and do not use the numbers 1521 or 1527 as these might already
be in use by default
9 We recommend that you delete the directory userprofilesdtgui
10 IBM DB2 for Linux and UNIX and Windows If not already done install the DB2 license
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
11 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running the Installer
3260 CUSTOMER 2012-11-27
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
Not valid for Sybase 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
httpservicesapcominstallnw70
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3360
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 the installer [page 29] 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 40] 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3460 CUSTOMER 2012-11-27
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 central instance host of the source system you run the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
12 On the database host of the source system you run the installer [page 29] to remove the Java database
schema
13 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
14 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
15 If required and not already done so you configure the CTS Deploy Web Service [page 40] on the ABAP
system
16 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3560
5 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 release
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
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 the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
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 40] on the ABAP
system
15 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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3660 CUSTOMER 2012-11-27
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 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
CAUTION
Sybase Only the functionality of split option ldquoMove Java Databaserdquo is supported
Move Java Database [page 9]
Keep Database [page 12]
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)
Only valid for Microsoft Failover Clustering If your system is a high-availability system with
Microsoft Failover Clustering (previously known as MSCS) the split option ldquoMove Java Databaserdquo offers
the possibility to split a clustered dual-stack system into one ABAP cluster system and one Java cluster
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 the installer 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 the
installer removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
2012-11-27 CUSTOMER 960
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 the installer 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 the
installer removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
1060 CUSTOMER 2012-11-27
Figure 2 Split Option Move Java Database for Distributed System
Move Java Database for High-Availability Systems
When you choose the ldquoMove Java Databaserdquo option for a high-availability system the installer exports
the Java stack of the dual-stack cluster system and uses this export to reinstall all mandatory instances
on a separate cluster system for Java
These are the mandatory instances
Central services instance for Java (SCS)
Enqueue replication server instance (ERS instance) for the SCS instance
Database instance (DB)
Central instance
Dialog instance
After the installation has finished and the System Landscape Directory has been reconfigured the
installer removes all Java parts from the dual-stack cluster system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
2012-11-27 CUSTOMER 1160
Figure 3 Split Option Move Java Database for High-Availability System
22 Split Option Keep Database
CAUTION
Sybase The functionality of split option ldquoKeep Databaserdquo is not supported
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)
Only valid for Microsoft Failover Clustering If your system is a high-availability system with
Microsoft Failover Clustering (MSCS) the split option ldquoKeep Databaserdquo offers the possibility to split a
clustered dual-stack system into one ABAP cluster system and one Java cluster system both using the
same database (MCOD)
Keep Database for Central and Distributed Systems
When you choose the ldquoKeep Databaserdquo option the installer 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 the installer 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 the
installer 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
1260 CUSTOMER 2012-11-27
Figure 4 Split Option Keep Database for Central Systems
Figure 5 Split Option Keep Database for Distributed Systems
Keep Database for High-Availability Systems
When you choose the ldquoKeep Databaserdquo option for a high-availability system you can choose between
the following scenarios
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-11-27 CUSTOMER 1360
Move SCS to New or Other Cluster
The installer exports the Java stack of the dual-stack cluster system and uses this export to install
a central services instance and a central instance on a separate cluster system for Java Additionally
the installer adapts the Java schema of the database of the former dual-stack cluster system to the
target Java cluster system
Figure 6 Split Option Keep Database for High-Availability Systems mdash Move SCS to New or Other
Cluster
Keep SCS on the Source Cluster System
The installer exports the Java central services instance of the source cluster system and uses this
export to install the SCS with a new system ID in a separate cluster on the target cluster system
Additionally the installer adapts the Java schema of the database to the target Java SID
NOTE
This scenario is supported as of Windows Server 2008
2 Split Options Covered by this Guide
22 Split Option Keep Database
1460 CUSTOMER 2012-11-27
Figure 7 Split Option Keep Database for High-Availability Systems mdash Keep SCS on the Source
Cluster System
After the installation has finished and the System Landscape Directory has been reconfigured the
installer removes all Java parts from the dual-stack cluster system except the Java database schema
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-11-27 CUSTOMER 1560
This page is left blank for documents that are printed on both sides
3 Planning
31 Planning Checklist
RECOMMENDATION
We recommend that you first perform the dual-stack split procedure in a test system to identify
possible further application-specific post-split activities required for your scenario
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 19]
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 19]
System Landscape Directory (SLD)
You can ignore SLD parameters
Oracle SAP System Database Parameters Java database schema
3 Planning
31 Planning Checklist
2012-11-27 CUSTOMER 1760
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
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 administrator
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
5 MS SQL Server Oracle For the database installation you decide how to distribute your database
components to disk
For more information see Distribution of SAP System Components to Disk in the installation documentation
of your release
6 SAP MaxDB For the database installation you decide how to distribute your system components
to disk
For more information see Distribution of SAP System Components to Disk in the installation documentation
of your release
7 IBM DB2 for Linux 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 release
8 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
9 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 49]
10 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
11 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
12 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
13 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
14 You can continue with Preparation [page 21]
Split Option ldquoKeep Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
CAUTION
Sybase Split option ldquoKeep Databaserdquo is not supported
3 Planning
31 Planning Checklist
1860 CUSTOMER 2012-11-27
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 19]
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 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 19]
System Landscape Directory (SLD)
You can ignore SLD parameters
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
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 49]
7 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
8 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
9 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
10 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
11 You can continue with Preparation [page 21]
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
3 Planning
32 User Management
2012-11-27 CUSTOMER 1960
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
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
2060 CUSTOMER 2012-11-27
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 You disable the Windows Server firewall on each host
For more information about disabling the Windows firewall see the relevant section in the
installation documentation of your release
2 You perform basic preparations on Windows
For more information see Performing Basic Windows Preparation Steps in the installation documentation
of your release
3 You check that you have the user authorization required for running the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
4 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
5 Only valid for HA (UNIX) |
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) |
6 If required you prepare the SAP system transport host for your SAP system
For more information see Preparing the SAP System Transport Host in the installation documentation
of your release
7 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
4 Preparation
41 Preparation Checklist
2012-11-27 CUSTOMER 2160
8 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 Dual Stack Split Installation Media [page 25]
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 |
9 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) |
10 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) |
11 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 22] of
the dual-stack system
12 You can continue with Splitting [page 27]
42 Performing a Full System Backup
NOTE
This section is not relevant if your database is Sybase
4 Preparation
42 Performing a Full System Backup
2260 CUSTOMER 2012-11-27
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
NOTE
If your system is a high-availability system make sure that you perform a backup of both cluster
nodes of the dual-stack system
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] for your release and database at
DatabaseSAP NetWeaver Release Path in Help Portal
SAP MaxDB SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for MaxDB
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 CapabilityGeneral 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
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for Oracle
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 CapabilityGeneral 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 Linux UNIX and Windows
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
4 Preparation
42 Performing a Full System Backup
2012-11-27 CUSTOMER 2360
DatabaseSAP NetWeaver Release Path in Help Portal
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 CapabilityGeneral 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 CapabilityGeneral 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 zOS
Microsoft SQL Server
SAP NetWeaver 70
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 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 CapabilityGeneral 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
2460 CUSTOMER 2012-11-27
43 Preparing the Dual Stack Split Installation Media
This section describes how to prepare the installation media that is required for the dual stack split
using the installer
Procedure
1 Download the installation media from the software distribution center on SAP Service Marketplace
using the following path
httpservicesapcomswdc Support Package and Patches A - Z Index S SL TOOLSET SL
TOOLSET 10 Entry by Component Dual-Stack Split
2 Create a download directory on the host on which you want to run the DualndashStack Split tool
3 Unpack the DualndashStack Split tool archive to a local directory using the following command
SAPCAR ndashxvf ltdownload directorygtltpathgtltArchivegtSAR -R ltunpack directorygt
4 Preparation
43 Preparing the Dual Stack Split Installation Media
2012-11-27 CUSTOMER 2560
This page is left blank for documents that are printed on both sides
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
NOTE
Sybase Split option ldquoKeep Databaserdquo is not supported You have to consider only the steps
described in section Move Java Database
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Oracle You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your release
2 Oracle If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your release
3 MS SQL Server You install the MS SQL Server database software
For more information see Installing the SQL Server Database Software in the installation documentation
of your release
4 You export the Java stack using the installer [page 29]
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 48]
5 You restart the source system
6 You run the installer [page 29] to install a Java only system using the export from the dual-stack
system
5 Splitting
51 Splitting Checklist
2012-11-27 CUSTOMER 2760
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 installer dialog
7 You continue with Follow-Up Activities [page 33]
Distributed System
1 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 release
2 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 release
3 On the database instance host of the dual-stack system you run the installer [page 29] to export the
Java database schema
4 On the central instance host of the dual-stack system you run the installer [page 29] 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 48]
5 You restart the source system
6 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
7 You run the installer [page 29] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
9 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2860 CUSTOMER 2012-11-27
Keep Database
1 On the central instance host of the dual-stack system you run the installer [page 29] to export 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 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 48]
2 You restart the source system
3 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
4 On the database instance host of the dual-stack system you run the installer [page 29] 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 the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
6 You continue with Follow-Up Activities [page 33]
52 Running the Installer
This section describes how to run the installer The installer includes a GUI client and a GUI server
which both use Java
The procedure describes an installation where the installer GUI client and GUI server are running on
the same host In the following GUI client and GUI server are addressed as ldquonstaller GUIrdquo
Useful Information About the Installer
When you start the installer it automatically starts the installer GUI
The installer creates the installation directory sapinst_instdir which is located directly in the
ProgramFiles directory If the installer is not able to create sapinst_instdir there it tries to
create sapinst_instdir in the directory defined by the environment variable TEMP
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 2960
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
The installer creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt which is located in ProgramFiles
The installer extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is
located in TEMP TMP TMPDIR or SystemRoot These files are deleted after the installer 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 the installer cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default port 21212 is used for communication between the installer
GUI server and the installer GUI client If this port is already in use you see an error message
In this case or if you want the installer to use a specific port open a command prompt and change
to the required directory to which you unpacked the DSS645_IM_ltplatformgtSAR file
Execute sapinstexe with the following command line parameter
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
To see a list of all available installer properties open a command prompt and start the installer
with command line parameter -p
sapinstexe -p
If you need to run the installer in accessibility mode make sure that you have activated and adjusted
accessibility settings as described in Running the Installer in Accessibility Mode in the installation
documentation of your release
If required you can stop the installer by choosing SAPinst Cancel in the installer GUI menu
Prerequisites
Make sure that you use an account with the required user authorization to run the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
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
the installer
Before you start the installer read SAP Note 1697164 which contains important information how
to run the installer
5 Splitting
52 Running the Installer
3060 CUSTOMER 2012-11-27
Procedure
1 Log on to the installation host using an account with the required user authorization to run the
installer
CAUTION
Do not use an existing ltsapsidgtadm user
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 Preparing the DualndashStack Split Installation Media [page 25]
3 Start the installer by double-clicking sapinstexe from the directory to which you unpacked the
DSS645_IM_ltplatformgtSAR file
NOTE
If you need to perform the installation in accessibility mode open a command prompt change
to the ltpath to unpack directorygt directory and execute sapinstexe ndashaccessible
For more information see Running the Installer in Accessibility Mode in the installation
documentation of your release
The GUI starts automatically by displaying the Welcome screen
4 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
CAUTION
Sybase Split options ldquoMove Java Databaserdquo and ldquoKeep Databaserdquo are not available in the
Welcome screen but only the steps valid for split option ldquoMove Java Databaserdquo are listed
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
5 Choose Next
6 If the installer prompts you to log off from your system log off and on again
The installer restarts automatically
7 Follow the instructions in the installer input screens and enter the required parameters
NOTE
If the installer 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 the installer displays the Parameter Summary
screen This screen shows both the parameters that you entered and those that the installer set by
default If required you can revise the parameters before starting the split procedure
8 To start the dual-stack split choose Start
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 3160
The installer starts and displays the progress of the split procedure
When the split option has finished successfully the installer displays the message Execution of
ltOption_Namegt has completed
CAUTION
Multiple Oracle Homes only The installer uses default values for the Oracle Home and
Listener configuration Therefore if you use multiple Oracle Homes you must specify the
new Oracle home as well as the listener port number You can change these values on the
installer Summary screen during the database instance installation On the Summary screen check
both Oracle gt Database System and Oracle gt Listener Configuration and use the Revise button On the
upcoming screen change the Oracle Home and the Listener port number Make sure that
you use a free port number and do not use the numbers 1521 or 1527 as these might already
be in use by default
9 We recommend that you delete the directory userprofilesdtgui
10 IBM DB2 for Linux and UNIX and Windows If not already done install the DB2 license
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
11 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running the Installer
3260 CUSTOMER 2012-11-27
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
Not valid for Sybase 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
httpservicesapcominstallnw70
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3360
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 the installer [page 29] 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 40] 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3460 CUSTOMER 2012-11-27
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 central instance host of the source system you run the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
12 On the database host of the source system you run the installer [page 29] to remove the Java database
schema
13 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
14 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
15 If required and not already done so you configure the CTS Deploy Web Service [page 40] on the ABAP
system
16 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3560
5 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 release
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
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 the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
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 40] on the ABAP
system
15 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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3660 CUSTOMER 2012-11-27
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 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 the installer 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 the
installer removes all Java parts from the dual-stack system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
1060 CUSTOMER 2012-11-27
Figure 2 Split Option Move Java Database for Distributed System
Move Java Database for High-Availability Systems
When you choose the ldquoMove Java Databaserdquo option for a high-availability system the installer exports
the Java stack of the dual-stack cluster system and uses this export to reinstall all mandatory instances
on a separate cluster system for Java
These are the mandatory instances
Central services instance for Java (SCS)
Enqueue replication server instance (ERS instance) for the SCS instance
Database instance (DB)
Central instance
Dialog instance
After the installation has finished and the System Landscape Directory has been reconfigured the
installer removes all Java parts from the dual-stack cluster system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
2012-11-27 CUSTOMER 1160
Figure 3 Split Option Move Java Database for High-Availability System
22 Split Option Keep Database
CAUTION
Sybase The functionality of split option ldquoKeep Databaserdquo is not supported
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)
Only valid for Microsoft Failover Clustering If your system is a high-availability system with
Microsoft Failover Clustering (MSCS) the split option ldquoKeep Databaserdquo offers the possibility to split a
clustered dual-stack system into one ABAP cluster system and one Java cluster system both using the
same database (MCOD)
Keep Database for Central and Distributed Systems
When you choose the ldquoKeep Databaserdquo option the installer 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 the installer 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 the
installer 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
1260 CUSTOMER 2012-11-27
Figure 4 Split Option Keep Database for Central Systems
Figure 5 Split Option Keep Database for Distributed Systems
Keep Database for High-Availability Systems
When you choose the ldquoKeep Databaserdquo option for a high-availability system you can choose between
the following scenarios
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-11-27 CUSTOMER 1360
Move SCS to New or Other Cluster
The installer exports the Java stack of the dual-stack cluster system and uses this export to install
a central services instance and a central instance on a separate cluster system for Java Additionally
the installer adapts the Java schema of the database of the former dual-stack cluster system to the
target Java cluster system
Figure 6 Split Option Keep Database for High-Availability Systems mdash Move SCS to New or Other
Cluster
Keep SCS on the Source Cluster System
The installer exports the Java central services instance of the source cluster system and uses this
export to install the SCS with a new system ID in a separate cluster on the target cluster system
Additionally the installer adapts the Java schema of the database to the target Java SID
NOTE
This scenario is supported as of Windows Server 2008
2 Split Options Covered by this Guide
22 Split Option Keep Database
1460 CUSTOMER 2012-11-27
Figure 7 Split Option Keep Database for High-Availability Systems mdash Keep SCS on the Source
Cluster System
After the installation has finished and the System Landscape Directory has been reconfigured the
installer removes all Java parts from the dual-stack cluster system except the Java database schema
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-11-27 CUSTOMER 1560
This page is left blank for documents that are printed on both sides
3 Planning
31 Planning Checklist
RECOMMENDATION
We recommend that you first perform the dual-stack split procedure in a test system to identify
possible further application-specific post-split activities required for your scenario
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 19]
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 19]
System Landscape Directory (SLD)
You can ignore SLD parameters
Oracle SAP System Database Parameters Java database schema
3 Planning
31 Planning Checklist
2012-11-27 CUSTOMER 1760
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
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 administrator
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
5 MS SQL Server Oracle For the database installation you decide how to distribute your database
components to disk
For more information see Distribution of SAP System Components to Disk in the installation documentation
of your release
6 SAP MaxDB For the database installation you decide how to distribute your system components
to disk
For more information see Distribution of SAP System Components to Disk in the installation documentation
of your release
7 IBM DB2 for Linux 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 release
8 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
9 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 49]
10 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
11 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
12 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
13 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
14 You can continue with Preparation [page 21]
Split Option ldquoKeep Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
CAUTION
Sybase Split option ldquoKeep Databaserdquo is not supported
3 Planning
31 Planning Checklist
1860 CUSTOMER 2012-11-27
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 19]
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 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 19]
System Landscape Directory (SLD)
You can ignore SLD parameters
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
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 49]
7 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
8 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
9 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
10 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
11 You can continue with Preparation [page 21]
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
3 Planning
32 User Management
2012-11-27 CUSTOMER 1960
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
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
2060 CUSTOMER 2012-11-27
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 You disable the Windows Server firewall on each host
For more information about disabling the Windows firewall see the relevant section in the
installation documentation of your release
2 You perform basic preparations on Windows
For more information see Performing Basic Windows Preparation Steps in the installation documentation
of your release
3 You check that you have the user authorization required for running the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
4 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
5 Only valid for HA (UNIX) |
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) |
6 If required you prepare the SAP system transport host for your SAP system
For more information see Preparing the SAP System Transport Host in the installation documentation
of your release
7 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
4 Preparation
41 Preparation Checklist
2012-11-27 CUSTOMER 2160
8 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 Dual Stack Split Installation Media [page 25]
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 |
9 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) |
10 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) |
11 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 22] of
the dual-stack system
12 You can continue with Splitting [page 27]
42 Performing a Full System Backup
NOTE
This section is not relevant if your database is Sybase
4 Preparation
42 Performing a Full System Backup
2260 CUSTOMER 2012-11-27
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
NOTE
If your system is a high-availability system make sure that you perform a backup of both cluster
nodes of the dual-stack system
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] for your release and database at
DatabaseSAP NetWeaver Release Path in Help Portal
SAP MaxDB SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for MaxDB
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 CapabilityGeneral 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
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for Oracle
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 CapabilityGeneral 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 Linux UNIX and Windows
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
4 Preparation
42 Performing a Full System Backup
2012-11-27 CUSTOMER 2360
DatabaseSAP NetWeaver Release Path in Help Portal
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 CapabilityGeneral 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 CapabilityGeneral 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 zOS
Microsoft SQL Server
SAP NetWeaver 70
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 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 CapabilityGeneral 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
2460 CUSTOMER 2012-11-27
43 Preparing the Dual Stack Split Installation Media
This section describes how to prepare the installation media that is required for the dual stack split
using the installer
Procedure
1 Download the installation media from the software distribution center on SAP Service Marketplace
using the following path
httpservicesapcomswdc Support Package and Patches A - Z Index S SL TOOLSET SL
TOOLSET 10 Entry by Component Dual-Stack Split
2 Create a download directory on the host on which you want to run the DualndashStack Split tool
3 Unpack the DualndashStack Split tool archive to a local directory using the following command
SAPCAR ndashxvf ltdownload directorygtltpathgtltArchivegtSAR -R ltunpack directorygt
4 Preparation
43 Preparing the Dual Stack Split Installation Media
2012-11-27 CUSTOMER 2560
This page is left blank for documents that are printed on both sides
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
NOTE
Sybase Split option ldquoKeep Databaserdquo is not supported You have to consider only the steps
described in section Move Java Database
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Oracle You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your release
2 Oracle If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your release
3 MS SQL Server You install the MS SQL Server database software
For more information see Installing the SQL Server Database Software in the installation documentation
of your release
4 You export the Java stack using the installer [page 29]
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 48]
5 You restart the source system
6 You run the installer [page 29] to install a Java only system using the export from the dual-stack
system
5 Splitting
51 Splitting Checklist
2012-11-27 CUSTOMER 2760
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 installer dialog
7 You continue with Follow-Up Activities [page 33]
Distributed System
1 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 release
2 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 release
3 On the database instance host of the dual-stack system you run the installer [page 29] to export the
Java database schema
4 On the central instance host of the dual-stack system you run the installer [page 29] 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 48]
5 You restart the source system
6 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
7 You run the installer [page 29] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
9 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2860 CUSTOMER 2012-11-27
Keep Database
1 On the central instance host of the dual-stack system you run the installer [page 29] to export 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 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 48]
2 You restart the source system
3 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
4 On the database instance host of the dual-stack system you run the installer [page 29] 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 the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
6 You continue with Follow-Up Activities [page 33]
52 Running the Installer
This section describes how to run the installer The installer includes a GUI client and a GUI server
which both use Java
The procedure describes an installation where the installer GUI client and GUI server are running on
the same host In the following GUI client and GUI server are addressed as ldquonstaller GUIrdquo
Useful Information About the Installer
When you start the installer it automatically starts the installer GUI
The installer creates the installation directory sapinst_instdir which is located directly in the
ProgramFiles directory If the installer is not able to create sapinst_instdir there it tries to
create sapinst_instdir in the directory defined by the environment variable TEMP
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 2960
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
The installer creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt which is located in ProgramFiles
The installer extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is
located in TEMP TMP TMPDIR or SystemRoot These files are deleted after the installer 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 the installer cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default port 21212 is used for communication between the installer
GUI server and the installer GUI client If this port is already in use you see an error message
In this case or if you want the installer to use a specific port open a command prompt and change
to the required directory to which you unpacked the DSS645_IM_ltplatformgtSAR file
Execute sapinstexe with the following command line parameter
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
To see a list of all available installer properties open a command prompt and start the installer
with command line parameter -p
sapinstexe -p
If you need to run the installer in accessibility mode make sure that you have activated and adjusted
accessibility settings as described in Running the Installer in Accessibility Mode in the installation
documentation of your release
If required you can stop the installer by choosing SAPinst Cancel in the installer GUI menu
Prerequisites
Make sure that you use an account with the required user authorization to run the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
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
the installer
Before you start the installer read SAP Note 1697164 which contains important information how
to run the installer
5 Splitting
52 Running the Installer
3060 CUSTOMER 2012-11-27
Procedure
1 Log on to the installation host using an account with the required user authorization to run the
installer
CAUTION
Do not use an existing ltsapsidgtadm user
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 Preparing the DualndashStack Split Installation Media [page 25]
3 Start the installer by double-clicking sapinstexe from the directory to which you unpacked the
DSS645_IM_ltplatformgtSAR file
NOTE
If you need to perform the installation in accessibility mode open a command prompt change
to the ltpath to unpack directorygt directory and execute sapinstexe ndashaccessible
For more information see Running the Installer in Accessibility Mode in the installation
documentation of your release
The GUI starts automatically by displaying the Welcome screen
4 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
CAUTION
Sybase Split options ldquoMove Java Databaserdquo and ldquoKeep Databaserdquo are not available in the
Welcome screen but only the steps valid for split option ldquoMove Java Databaserdquo are listed
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
5 Choose Next
6 If the installer prompts you to log off from your system log off and on again
The installer restarts automatically
7 Follow the instructions in the installer input screens and enter the required parameters
NOTE
If the installer 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 the installer displays the Parameter Summary
screen This screen shows both the parameters that you entered and those that the installer set by
default If required you can revise the parameters before starting the split procedure
8 To start the dual-stack split choose Start
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 3160
The installer starts and displays the progress of the split procedure
When the split option has finished successfully the installer displays the message Execution of
ltOption_Namegt has completed
CAUTION
Multiple Oracle Homes only The installer uses default values for the Oracle Home and
Listener configuration Therefore if you use multiple Oracle Homes you must specify the
new Oracle home as well as the listener port number You can change these values on the
installer Summary screen during the database instance installation On the Summary screen check
both Oracle gt Database System and Oracle gt Listener Configuration and use the Revise button On the
upcoming screen change the Oracle Home and the Listener port number Make sure that
you use a free port number and do not use the numbers 1521 or 1527 as these might already
be in use by default
9 We recommend that you delete the directory userprofilesdtgui
10 IBM DB2 for Linux and UNIX and Windows If not already done install the DB2 license
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
11 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running the Installer
3260 CUSTOMER 2012-11-27
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
Not valid for Sybase 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
httpservicesapcominstallnw70
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3360
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 the installer [page 29] 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 40] 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3460 CUSTOMER 2012-11-27
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 central instance host of the source system you run the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
12 On the database host of the source system you run the installer [page 29] to remove the Java database
schema
13 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
14 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
15 If required and not already done so you configure the CTS Deploy Web Service [page 40] on the ABAP
system
16 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3560
5 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 release
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
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 the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
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 40] on the ABAP
system
15 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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3660 CUSTOMER 2012-11-27
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 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
Move Java Database for High-Availability Systems
When you choose the ldquoMove Java Databaserdquo option for a high-availability system the installer exports
the Java stack of the dual-stack cluster system and uses this export to reinstall all mandatory instances
on a separate cluster system for Java
These are the mandatory instances
Central services instance for Java (SCS)
Enqueue replication server instance (ERS instance) for the SCS instance
Database instance (DB)
Central instance
Dialog instance
After the installation has finished and the System Landscape Directory has been reconfigured the
installer removes all Java parts from the dual-stack cluster system
2 Split Options Covered by this Guide
21 Split Option Move Java Database
2012-11-27 CUSTOMER 1160
Figure 3 Split Option Move Java Database for High-Availability System
22 Split Option Keep Database
CAUTION
Sybase The functionality of split option ldquoKeep Databaserdquo is not supported
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)
Only valid for Microsoft Failover Clustering If your system is a high-availability system with
Microsoft Failover Clustering (MSCS) the split option ldquoKeep Databaserdquo offers the possibility to split a
clustered dual-stack system into one ABAP cluster system and one Java cluster system both using the
same database (MCOD)
Keep Database for Central and Distributed Systems
When you choose the ldquoKeep Databaserdquo option the installer 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 the installer 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 the
installer 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
1260 CUSTOMER 2012-11-27
Figure 4 Split Option Keep Database for Central Systems
Figure 5 Split Option Keep Database for Distributed Systems
Keep Database for High-Availability Systems
When you choose the ldquoKeep Databaserdquo option for a high-availability system you can choose between
the following scenarios
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-11-27 CUSTOMER 1360
Move SCS to New or Other Cluster
The installer exports the Java stack of the dual-stack cluster system and uses this export to install
a central services instance and a central instance on a separate cluster system for Java Additionally
the installer adapts the Java schema of the database of the former dual-stack cluster system to the
target Java cluster system
Figure 6 Split Option Keep Database for High-Availability Systems mdash Move SCS to New or Other
Cluster
Keep SCS on the Source Cluster System
The installer exports the Java central services instance of the source cluster system and uses this
export to install the SCS with a new system ID in a separate cluster on the target cluster system
Additionally the installer adapts the Java schema of the database to the target Java SID
NOTE
This scenario is supported as of Windows Server 2008
2 Split Options Covered by this Guide
22 Split Option Keep Database
1460 CUSTOMER 2012-11-27
Figure 7 Split Option Keep Database for High-Availability Systems mdash Keep SCS on the Source
Cluster System
After the installation has finished and the System Landscape Directory has been reconfigured the
installer removes all Java parts from the dual-stack cluster system except the Java database schema
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-11-27 CUSTOMER 1560
This page is left blank for documents that are printed on both sides
3 Planning
31 Planning Checklist
RECOMMENDATION
We recommend that you first perform the dual-stack split procedure in a test system to identify
possible further application-specific post-split activities required for your scenario
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 19]
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 19]
System Landscape Directory (SLD)
You can ignore SLD parameters
Oracle SAP System Database Parameters Java database schema
3 Planning
31 Planning Checklist
2012-11-27 CUSTOMER 1760
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
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 administrator
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
5 MS SQL Server Oracle For the database installation you decide how to distribute your database
components to disk
For more information see Distribution of SAP System Components to Disk in the installation documentation
of your release
6 SAP MaxDB For the database installation you decide how to distribute your system components
to disk
For more information see Distribution of SAP System Components to Disk in the installation documentation
of your release
7 IBM DB2 for Linux 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 release
8 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
9 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 49]
10 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
11 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
12 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
13 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
14 You can continue with Preparation [page 21]
Split Option ldquoKeep Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
CAUTION
Sybase Split option ldquoKeep Databaserdquo is not supported
3 Planning
31 Planning Checklist
1860 CUSTOMER 2012-11-27
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 19]
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 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 19]
System Landscape Directory (SLD)
You can ignore SLD parameters
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
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 49]
7 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
8 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
9 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
10 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
11 You can continue with Preparation [page 21]
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
3 Planning
32 User Management
2012-11-27 CUSTOMER 1960
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
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
2060 CUSTOMER 2012-11-27
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 You disable the Windows Server firewall on each host
For more information about disabling the Windows firewall see the relevant section in the
installation documentation of your release
2 You perform basic preparations on Windows
For more information see Performing Basic Windows Preparation Steps in the installation documentation
of your release
3 You check that you have the user authorization required for running the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
4 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
5 Only valid for HA (UNIX) |
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) |
6 If required you prepare the SAP system transport host for your SAP system
For more information see Preparing the SAP System Transport Host in the installation documentation
of your release
7 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
4 Preparation
41 Preparation Checklist
2012-11-27 CUSTOMER 2160
8 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 Dual Stack Split Installation Media [page 25]
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 |
9 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) |
10 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) |
11 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 22] of
the dual-stack system
12 You can continue with Splitting [page 27]
42 Performing a Full System Backup
NOTE
This section is not relevant if your database is Sybase
4 Preparation
42 Performing a Full System Backup
2260 CUSTOMER 2012-11-27
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
NOTE
If your system is a high-availability system make sure that you perform a backup of both cluster
nodes of the dual-stack system
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] for your release and database at
DatabaseSAP NetWeaver Release Path in Help Portal
SAP MaxDB SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for MaxDB
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 CapabilityGeneral 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
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for Oracle
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 CapabilityGeneral 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 Linux UNIX and Windows
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
4 Preparation
42 Performing a Full System Backup
2012-11-27 CUSTOMER 2360
DatabaseSAP NetWeaver Release Path in Help Portal
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 CapabilityGeneral 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 CapabilityGeneral 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 zOS
Microsoft SQL Server
SAP NetWeaver 70
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 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 CapabilityGeneral 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
2460 CUSTOMER 2012-11-27
43 Preparing the Dual Stack Split Installation Media
This section describes how to prepare the installation media that is required for the dual stack split
using the installer
Procedure
1 Download the installation media from the software distribution center on SAP Service Marketplace
using the following path
httpservicesapcomswdc Support Package and Patches A - Z Index S SL TOOLSET SL
TOOLSET 10 Entry by Component Dual-Stack Split
2 Create a download directory on the host on which you want to run the DualndashStack Split tool
3 Unpack the DualndashStack Split tool archive to a local directory using the following command
SAPCAR ndashxvf ltdownload directorygtltpathgtltArchivegtSAR -R ltunpack directorygt
4 Preparation
43 Preparing the Dual Stack Split Installation Media
2012-11-27 CUSTOMER 2560
This page is left blank for documents that are printed on both sides
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
NOTE
Sybase Split option ldquoKeep Databaserdquo is not supported You have to consider only the steps
described in section Move Java Database
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Oracle You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your release
2 Oracle If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your release
3 MS SQL Server You install the MS SQL Server database software
For more information see Installing the SQL Server Database Software in the installation documentation
of your release
4 You export the Java stack using the installer [page 29]
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 48]
5 You restart the source system
6 You run the installer [page 29] to install a Java only system using the export from the dual-stack
system
5 Splitting
51 Splitting Checklist
2012-11-27 CUSTOMER 2760
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 installer dialog
7 You continue with Follow-Up Activities [page 33]
Distributed System
1 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 release
2 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 release
3 On the database instance host of the dual-stack system you run the installer [page 29] to export the
Java database schema
4 On the central instance host of the dual-stack system you run the installer [page 29] 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 48]
5 You restart the source system
6 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
7 You run the installer [page 29] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
9 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2860 CUSTOMER 2012-11-27
Keep Database
1 On the central instance host of the dual-stack system you run the installer [page 29] to export 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 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 48]
2 You restart the source system
3 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
4 On the database instance host of the dual-stack system you run the installer [page 29] 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 the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
6 You continue with Follow-Up Activities [page 33]
52 Running the Installer
This section describes how to run the installer The installer includes a GUI client and a GUI server
which both use Java
The procedure describes an installation where the installer GUI client and GUI server are running on
the same host In the following GUI client and GUI server are addressed as ldquonstaller GUIrdquo
Useful Information About the Installer
When you start the installer it automatically starts the installer GUI
The installer creates the installation directory sapinst_instdir which is located directly in the
ProgramFiles directory If the installer is not able to create sapinst_instdir there it tries to
create sapinst_instdir in the directory defined by the environment variable TEMP
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 2960
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
The installer creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt which is located in ProgramFiles
The installer extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is
located in TEMP TMP TMPDIR or SystemRoot These files are deleted after the installer 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 the installer cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default port 21212 is used for communication between the installer
GUI server and the installer GUI client If this port is already in use you see an error message
In this case or if you want the installer to use a specific port open a command prompt and change
to the required directory to which you unpacked the DSS645_IM_ltplatformgtSAR file
Execute sapinstexe with the following command line parameter
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
To see a list of all available installer properties open a command prompt and start the installer
with command line parameter -p
sapinstexe -p
If you need to run the installer in accessibility mode make sure that you have activated and adjusted
accessibility settings as described in Running the Installer in Accessibility Mode in the installation
documentation of your release
If required you can stop the installer by choosing SAPinst Cancel in the installer GUI menu
Prerequisites
Make sure that you use an account with the required user authorization to run the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
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
the installer
Before you start the installer read SAP Note 1697164 which contains important information how
to run the installer
5 Splitting
52 Running the Installer
3060 CUSTOMER 2012-11-27
Procedure
1 Log on to the installation host using an account with the required user authorization to run the
installer
CAUTION
Do not use an existing ltsapsidgtadm user
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 Preparing the DualndashStack Split Installation Media [page 25]
3 Start the installer by double-clicking sapinstexe from the directory to which you unpacked the
DSS645_IM_ltplatformgtSAR file
NOTE
If you need to perform the installation in accessibility mode open a command prompt change
to the ltpath to unpack directorygt directory and execute sapinstexe ndashaccessible
For more information see Running the Installer in Accessibility Mode in the installation
documentation of your release
The GUI starts automatically by displaying the Welcome screen
4 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
CAUTION
Sybase Split options ldquoMove Java Databaserdquo and ldquoKeep Databaserdquo are not available in the
Welcome screen but only the steps valid for split option ldquoMove Java Databaserdquo are listed
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
5 Choose Next
6 If the installer prompts you to log off from your system log off and on again
The installer restarts automatically
7 Follow the instructions in the installer input screens and enter the required parameters
NOTE
If the installer 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 the installer displays the Parameter Summary
screen This screen shows both the parameters that you entered and those that the installer set by
default If required you can revise the parameters before starting the split procedure
8 To start the dual-stack split choose Start
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 3160
The installer starts and displays the progress of the split procedure
When the split option has finished successfully the installer displays the message Execution of
ltOption_Namegt has completed
CAUTION
Multiple Oracle Homes only The installer uses default values for the Oracle Home and
Listener configuration Therefore if you use multiple Oracle Homes you must specify the
new Oracle home as well as the listener port number You can change these values on the
installer Summary screen during the database instance installation On the Summary screen check
both Oracle gt Database System and Oracle gt Listener Configuration and use the Revise button On the
upcoming screen change the Oracle Home and the Listener port number Make sure that
you use a free port number and do not use the numbers 1521 or 1527 as these might already
be in use by default
9 We recommend that you delete the directory userprofilesdtgui
10 IBM DB2 for Linux and UNIX and Windows If not already done install the DB2 license
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
11 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running the Installer
3260 CUSTOMER 2012-11-27
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
Not valid for Sybase 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
httpservicesapcominstallnw70
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3360
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 the installer [page 29] 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 40] 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3460 CUSTOMER 2012-11-27
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 central instance host of the source system you run the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
12 On the database host of the source system you run the installer [page 29] to remove the Java database
schema
13 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
14 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
15 If required and not already done so you configure the CTS Deploy Web Service [page 40] on the ABAP
system
16 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3560
5 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 release
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
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 the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
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 40] on the ABAP
system
15 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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3660 CUSTOMER 2012-11-27
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
Figure 3 Split Option Move Java Database for High-Availability System
22 Split Option Keep Database
CAUTION
Sybase The functionality of split option ldquoKeep Databaserdquo is not supported
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)
Only valid for Microsoft Failover Clustering If your system is a high-availability system with
Microsoft Failover Clustering (MSCS) the split option ldquoKeep Databaserdquo offers the possibility to split a
clustered dual-stack system into one ABAP cluster system and one Java cluster system both using the
same database (MCOD)
Keep Database for Central and Distributed Systems
When you choose the ldquoKeep Databaserdquo option the installer 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 the installer 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 the
installer 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
1260 CUSTOMER 2012-11-27
Figure 4 Split Option Keep Database for Central Systems
Figure 5 Split Option Keep Database for Distributed Systems
Keep Database for High-Availability Systems
When you choose the ldquoKeep Databaserdquo option for a high-availability system you can choose between
the following scenarios
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-11-27 CUSTOMER 1360
Move SCS to New or Other Cluster
The installer exports the Java stack of the dual-stack cluster system and uses this export to install
a central services instance and a central instance on a separate cluster system for Java Additionally
the installer adapts the Java schema of the database of the former dual-stack cluster system to the
target Java cluster system
Figure 6 Split Option Keep Database for High-Availability Systems mdash Move SCS to New or Other
Cluster
Keep SCS on the Source Cluster System
The installer exports the Java central services instance of the source cluster system and uses this
export to install the SCS with a new system ID in a separate cluster on the target cluster system
Additionally the installer adapts the Java schema of the database to the target Java SID
NOTE
This scenario is supported as of Windows Server 2008
2 Split Options Covered by this Guide
22 Split Option Keep Database
1460 CUSTOMER 2012-11-27
Figure 7 Split Option Keep Database for High-Availability Systems mdash Keep SCS on the Source
Cluster System
After the installation has finished and the System Landscape Directory has been reconfigured the
installer removes all Java parts from the dual-stack cluster system except the Java database schema
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-11-27 CUSTOMER 1560
This page is left blank for documents that are printed on both sides
3 Planning
31 Planning Checklist
RECOMMENDATION
We recommend that you first perform the dual-stack split procedure in a test system to identify
possible further application-specific post-split activities required for your scenario
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 19]
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 19]
System Landscape Directory (SLD)
You can ignore SLD parameters
Oracle SAP System Database Parameters Java database schema
3 Planning
31 Planning Checklist
2012-11-27 CUSTOMER 1760
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
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 administrator
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
5 MS SQL Server Oracle For the database installation you decide how to distribute your database
components to disk
For more information see Distribution of SAP System Components to Disk in the installation documentation
of your release
6 SAP MaxDB For the database installation you decide how to distribute your system components
to disk
For more information see Distribution of SAP System Components to Disk in the installation documentation
of your release
7 IBM DB2 for Linux 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 release
8 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
9 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 49]
10 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
11 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
12 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
13 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
14 You can continue with Preparation [page 21]
Split Option ldquoKeep Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
CAUTION
Sybase Split option ldquoKeep Databaserdquo is not supported
3 Planning
31 Planning Checklist
1860 CUSTOMER 2012-11-27
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 19]
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 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 19]
System Landscape Directory (SLD)
You can ignore SLD parameters
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
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 49]
7 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
8 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
9 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
10 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
11 You can continue with Preparation [page 21]
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
3 Planning
32 User Management
2012-11-27 CUSTOMER 1960
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
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
2060 CUSTOMER 2012-11-27
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 You disable the Windows Server firewall on each host
For more information about disabling the Windows firewall see the relevant section in the
installation documentation of your release
2 You perform basic preparations on Windows
For more information see Performing Basic Windows Preparation Steps in the installation documentation
of your release
3 You check that you have the user authorization required for running the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
4 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
5 Only valid for HA (UNIX) |
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) |
6 If required you prepare the SAP system transport host for your SAP system
For more information see Preparing the SAP System Transport Host in the installation documentation
of your release
7 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
4 Preparation
41 Preparation Checklist
2012-11-27 CUSTOMER 2160
8 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 Dual Stack Split Installation Media [page 25]
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 |
9 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) |
10 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) |
11 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 22] of
the dual-stack system
12 You can continue with Splitting [page 27]
42 Performing a Full System Backup
NOTE
This section is not relevant if your database is Sybase
4 Preparation
42 Performing a Full System Backup
2260 CUSTOMER 2012-11-27
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
NOTE
If your system is a high-availability system make sure that you perform a backup of both cluster
nodes of the dual-stack system
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] for your release and database at
DatabaseSAP NetWeaver Release Path in Help Portal
SAP MaxDB SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for MaxDB
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 CapabilityGeneral 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
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for Oracle
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 CapabilityGeneral 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 Linux UNIX and Windows
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
4 Preparation
42 Performing a Full System Backup
2012-11-27 CUSTOMER 2360
DatabaseSAP NetWeaver Release Path in Help Portal
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 CapabilityGeneral 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 CapabilityGeneral 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 zOS
Microsoft SQL Server
SAP NetWeaver 70
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 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 CapabilityGeneral 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
2460 CUSTOMER 2012-11-27
43 Preparing the Dual Stack Split Installation Media
This section describes how to prepare the installation media that is required for the dual stack split
using the installer
Procedure
1 Download the installation media from the software distribution center on SAP Service Marketplace
using the following path
httpservicesapcomswdc Support Package and Patches A - Z Index S SL TOOLSET SL
TOOLSET 10 Entry by Component Dual-Stack Split
2 Create a download directory on the host on which you want to run the DualndashStack Split tool
3 Unpack the DualndashStack Split tool archive to a local directory using the following command
SAPCAR ndashxvf ltdownload directorygtltpathgtltArchivegtSAR -R ltunpack directorygt
4 Preparation
43 Preparing the Dual Stack Split Installation Media
2012-11-27 CUSTOMER 2560
This page is left blank for documents that are printed on both sides
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
NOTE
Sybase Split option ldquoKeep Databaserdquo is not supported You have to consider only the steps
described in section Move Java Database
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Oracle You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your release
2 Oracle If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your release
3 MS SQL Server You install the MS SQL Server database software
For more information see Installing the SQL Server Database Software in the installation documentation
of your release
4 You export the Java stack using the installer [page 29]
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 48]
5 You restart the source system
6 You run the installer [page 29] to install a Java only system using the export from the dual-stack
system
5 Splitting
51 Splitting Checklist
2012-11-27 CUSTOMER 2760
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 installer dialog
7 You continue with Follow-Up Activities [page 33]
Distributed System
1 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 release
2 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 release
3 On the database instance host of the dual-stack system you run the installer [page 29] to export the
Java database schema
4 On the central instance host of the dual-stack system you run the installer [page 29] 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 48]
5 You restart the source system
6 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
7 You run the installer [page 29] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
9 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2860 CUSTOMER 2012-11-27
Keep Database
1 On the central instance host of the dual-stack system you run the installer [page 29] to export 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 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 48]
2 You restart the source system
3 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
4 On the database instance host of the dual-stack system you run the installer [page 29] 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 the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
6 You continue with Follow-Up Activities [page 33]
52 Running the Installer
This section describes how to run the installer The installer includes a GUI client and a GUI server
which both use Java
The procedure describes an installation where the installer GUI client and GUI server are running on
the same host In the following GUI client and GUI server are addressed as ldquonstaller GUIrdquo
Useful Information About the Installer
When you start the installer it automatically starts the installer GUI
The installer creates the installation directory sapinst_instdir which is located directly in the
ProgramFiles directory If the installer is not able to create sapinst_instdir there it tries to
create sapinst_instdir in the directory defined by the environment variable TEMP
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 2960
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
The installer creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt which is located in ProgramFiles
The installer extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is
located in TEMP TMP TMPDIR or SystemRoot These files are deleted after the installer 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 the installer cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default port 21212 is used for communication between the installer
GUI server and the installer GUI client If this port is already in use you see an error message
In this case or if you want the installer to use a specific port open a command prompt and change
to the required directory to which you unpacked the DSS645_IM_ltplatformgtSAR file
Execute sapinstexe with the following command line parameter
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
To see a list of all available installer properties open a command prompt and start the installer
with command line parameter -p
sapinstexe -p
If you need to run the installer in accessibility mode make sure that you have activated and adjusted
accessibility settings as described in Running the Installer in Accessibility Mode in the installation
documentation of your release
If required you can stop the installer by choosing SAPinst Cancel in the installer GUI menu
Prerequisites
Make sure that you use an account with the required user authorization to run the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
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
the installer
Before you start the installer read SAP Note 1697164 which contains important information how
to run the installer
5 Splitting
52 Running the Installer
3060 CUSTOMER 2012-11-27
Procedure
1 Log on to the installation host using an account with the required user authorization to run the
installer
CAUTION
Do not use an existing ltsapsidgtadm user
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 Preparing the DualndashStack Split Installation Media [page 25]
3 Start the installer by double-clicking sapinstexe from the directory to which you unpacked the
DSS645_IM_ltplatformgtSAR file
NOTE
If you need to perform the installation in accessibility mode open a command prompt change
to the ltpath to unpack directorygt directory and execute sapinstexe ndashaccessible
For more information see Running the Installer in Accessibility Mode in the installation
documentation of your release
The GUI starts automatically by displaying the Welcome screen
4 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
CAUTION
Sybase Split options ldquoMove Java Databaserdquo and ldquoKeep Databaserdquo are not available in the
Welcome screen but only the steps valid for split option ldquoMove Java Databaserdquo are listed
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
5 Choose Next
6 If the installer prompts you to log off from your system log off and on again
The installer restarts automatically
7 Follow the instructions in the installer input screens and enter the required parameters
NOTE
If the installer 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 the installer displays the Parameter Summary
screen This screen shows both the parameters that you entered and those that the installer set by
default If required you can revise the parameters before starting the split procedure
8 To start the dual-stack split choose Start
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 3160
The installer starts and displays the progress of the split procedure
When the split option has finished successfully the installer displays the message Execution of
ltOption_Namegt has completed
CAUTION
Multiple Oracle Homes only The installer uses default values for the Oracle Home and
Listener configuration Therefore if you use multiple Oracle Homes you must specify the
new Oracle home as well as the listener port number You can change these values on the
installer Summary screen during the database instance installation On the Summary screen check
both Oracle gt Database System and Oracle gt Listener Configuration and use the Revise button On the
upcoming screen change the Oracle Home and the Listener port number Make sure that
you use a free port number and do not use the numbers 1521 or 1527 as these might already
be in use by default
9 We recommend that you delete the directory userprofilesdtgui
10 IBM DB2 for Linux and UNIX and Windows If not already done install the DB2 license
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
11 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running the Installer
3260 CUSTOMER 2012-11-27
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
Not valid for Sybase 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
httpservicesapcominstallnw70
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3360
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 the installer [page 29] 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 40] 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3460 CUSTOMER 2012-11-27
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 central instance host of the source system you run the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
12 On the database host of the source system you run the installer [page 29] to remove the Java database
schema
13 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
14 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
15 If required and not already done so you configure the CTS Deploy Web Service [page 40] on the ABAP
system
16 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3560
5 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 release
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
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 the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
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 40] on the ABAP
system
15 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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3660 CUSTOMER 2012-11-27
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
Figure 4 Split Option Keep Database for Central Systems
Figure 5 Split Option Keep Database for Distributed Systems
Keep Database for High-Availability Systems
When you choose the ldquoKeep Databaserdquo option for a high-availability system you can choose between
the following scenarios
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-11-27 CUSTOMER 1360
Move SCS to New or Other Cluster
The installer exports the Java stack of the dual-stack cluster system and uses this export to install
a central services instance and a central instance on a separate cluster system for Java Additionally
the installer adapts the Java schema of the database of the former dual-stack cluster system to the
target Java cluster system
Figure 6 Split Option Keep Database for High-Availability Systems mdash Move SCS to New or Other
Cluster
Keep SCS on the Source Cluster System
The installer exports the Java central services instance of the source cluster system and uses this
export to install the SCS with a new system ID in a separate cluster on the target cluster system
Additionally the installer adapts the Java schema of the database to the target Java SID
NOTE
This scenario is supported as of Windows Server 2008
2 Split Options Covered by this Guide
22 Split Option Keep Database
1460 CUSTOMER 2012-11-27
Figure 7 Split Option Keep Database for High-Availability Systems mdash Keep SCS on the Source
Cluster System
After the installation has finished and the System Landscape Directory has been reconfigured the
installer removes all Java parts from the dual-stack cluster system except the Java database schema
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-11-27 CUSTOMER 1560
This page is left blank for documents that are printed on both sides
3 Planning
31 Planning Checklist
RECOMMENDATION
We recommend that you first perform the dual-stack split procedure in a test system to identify
possible further application-specific post-split activities required for your scenario
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 19]
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 19]
System Landscape Directory (SLD)
You can ignore SLD parameters
Oracle SAP System Database Parameters Java database schema
3 Planning
31 Planning Checklist
2012-11-27 CUSTOMER 1760
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
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 administrator
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
5 MS SQL Server Oracle For the database installation you decide how to distribute your database
components to disk
For more information see Distribution of SAP System Components to Disk in the installation documentation
of your release
6 SAP MaxDB For the database installation you decide how to distribute your system components
to disk
For more information see Distribution of SAP System Components to Disk in the installation documentation
of your release
7 IBM DB2 for Linux 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 release
8 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
9 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 49]
10 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
11 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
12 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
13 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
14 You can continue with Preparation [page 21]
Split Option ldquoKeep Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
CAUTION
Sybase Split option ldquoKeep Databaserdquo is not supported
3 Planning
31 Planning Checklist
1860 CUSTOMER 2012-11-27
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 19]
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 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 19]
System Landscape Directory (SLD)
You can ignore SLD parameters
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
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 49]
7 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
8 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
9 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
10 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
11 You can continue with Preparation [page 21]
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
3 Planning
32 User Management
2012-11-27 CUSTOMER 1960
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
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
2060 CUSTOMER 2012-11-27
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 You disable the Windows Server firewall on each host
For more information about disabling the Windows firewall see the relevant section in the
installation documentation of your release
2 You perform basic preparations on Windows
For more information see Performing Basic Windows Preparation Steps in the installation documentation
of your release
3 You check that you have the user authorization required for running the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
4 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
5 Only valid for HA (UNIX) |
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) |
6 If required you prepare the SAP system transport host for your SAP system
For more information see Preparing the SAP System Transport Host in the installation documentation
of your release
7 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
4 Preparation
41 Preparation Checklist
2012-11-27 CUSTOMER 2160
8 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 Dual Stack Split Installation Media [page 25]
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 |
9 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) |
10 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) |
11 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 22] of
the dual-stack system
12 You can continue with Splitting [page 27]
42 Performing a Full System Backup
NOTE
This section is not relevant if your database is Sybase
4 Preparation
42 Performing a Full System Backup
2260 CUSTOMER 2012-11-27
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
NOTE
If your system is a high-availability system make sure that you perform a backup of both cluster
nodes of the dual-stack system
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] for your release and database at
DatabaseSAP NetWeaver Release Path in Help Portal
SAP MaxDB SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for MaxDB
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 CapabilityGeneral 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
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for Oracle
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 CapabilityGeneral 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 Linux UNIX and Windows
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
4 Preparation
42 Performing a Full System Backup
2012-11-27 CUSTOMER 2360
DatabaseSAP NetWeaver Release Path in Help Portal
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 CapabilityGeneral 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 CapabilityGeneral 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 zOS
Microsoft SQL Server
SAP NetWeaver 70
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 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 CapabilityGeneral 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
2460 CUSTOMER 2012-11-27
43 Preparing the Dual Stack Split Installation Media
This section describes how to prepare the installation media that is required for the dual stack split
using the installer
Procedure
1 Download the installation media from the software distribution center on SAP Service Marketplace
using the following path
httpservicesapcomswdc Support Package and Patches A - Z Index S SL TOOLSET SL
TOOLSET 10 Entry by Component Dual-Stack Split
2 Create a download directory on the host on which you want to run the DualndashStack Split tool
3 Unpack the DualndashStack Split tool archive to a local directory using the following command
SAPCAR ndashxvf ltdownload directorygtltpathgtltArchivegtSAR -R ltunpack directorygt
4 Preparation
43 Preparing the Dual Stack Split Installation Media
2012-11-27 CUSTOMER 2560
This page is left blank for documents that are printed on both sides
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
NOTE
Sybase Split option ldquoKeep Databaserdquo is not supported You have to consider only the steps
described in section Move Java Database
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Oracle You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your release
2 Oracle If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your release
3 MS SQL Server You install the MS SQL Server database software
For more information see Installing the SQL Server Database Software in the installation documentation
of your release
4 You export the Java stack using the installer [page 29]
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 48]
5 You restart the source system
6 You run the installer [page 29] to install a Java only system using the export from the dual-stack
system
5 Splitting
51 Splitting Checklist
2012-11-27 CUSTOMER 2760
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 installer dialog
7 You continue with Follow-Up Activities [page 33]
Distributed System
1 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 release
2 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 release
3 On the database instance host of the dual-stack system you run the installer [page 29] to export the
Java database schema
4 On the central instance host of the dual-stack system you run the installer [page 29] 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 48]
5 You restart the source system
6 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
7 You run the installer [page 29] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
9 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2860 CUSTOMER 2012-11-27
Keep Database
1 On the central instance host of the dual-stack system you run the installer [page 29] to export 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 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 48]
2 You restart the source system
3 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
4 On the database instance host of the dual-stack system you run the installer [page 29] 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 the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
6 You continue with Follow-Up Activities [page 33]
52 Running the Installer
This section describes how to run the installer The installer includes a GUI client and a GUI server
which both use Java
The procedure describes an installation where the installer GUI client and GUI server are running on
the same host In the following GUI client and GUI server are addressed as ldquonstaller GUIrdquo
Useful Information About the Installer
When you start the installer it automatically starts the installer GUI
The installer creates the installation directory sapinst_instdir which is located directly in the
ProgramFiles directory If the installer is not able to create sapinst_instdir there it tries to
create sapinst_instdir in the directory defined by the environment variable TEMP
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 2960
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
The installer creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt which is located in ProgramFiles
The installer extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is
located in TEMP TMP TMPDIR or SystemRoot These files are deleted after the installer 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 the installer cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default port 21212 is used for communication between the installer
GUI server and the installer GUI client If this port is already in use you see an error message
In this case or if you want the installer to use a specific port open a command prompt and change
to the required directory to which you unpacked the DSS645_IM_ltplatformgtSAR file
Execute sapinstexe with the following command line parameter
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
To see a list of all available installer properties open a command prompt and start the installer
with command line parameter -p
sapinstexe -p
If you need to run the installer in accessibility mode make sure that you have activated and adjusted
accessibility settings as described in Running the Installer in Accessibility Mode in the installation
documentation of your release
If required you can stop the installer by choosing SAPinst Cancel in the installer GUI menu
Prerequisites
Make sure that you use an account with the required user authorization to run the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
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
the installer
Before you start the installer read SAP Note 1697164 which contains important information how
to run the installer
5 Splitting
52 Running the Installer
3060 CUSTOMER 2012-11-27
Procedure
1 Log on to the installation host using an account with the required user authorization to run the
installer
CAUTION
Do not use an existing ltsapsidgtadm user
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 Preparing the DualndashStack Split Installation Media [page 25]
3 Start the installer by double-clicking sapinstexe from the directory to which you unpacked the
DSS645_IM_ltplatformgtSAR file
NOTE
If you need to perform the installation in accessibility mode open a command prompt change
to the ltpath to unpack directorygt directory and execute sapinstexe ndashaccessible
For more information see Running the Installer in Accessibility Mode in the installation
documentation of your release
The GUI starts automatically by displaying the Welcome screen
4 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
CAUTION
Sybase Split options ldquoMove Java Databaserdquo and ldquoKeep Databaserdquo are not available in the
Welcome screen but only the steps valid for split option ldquoMove Java Databaserdquo are listed
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
5 Choose Next
6 If the installer prompts you to log off from your system log off and on again
The installer restarts automatically
7 Follow the instructions in the installer input screens and enter the required parameters
NOTE
If the installer 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 the installer displays the Parameter Summary
screen This screen shows both the parameters that you entered and those that the installer set by
default If required you can revise the parameters before starting the split procedure
8 To start the dual-stack split choose Start
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 3160
The installer starts and displays the progress of the split procedure
When the split option has finished successfully the installer displays the message Execution of
ltOption_Namegt has completed
CAUTION
Multiple Oracle Homes only The installer uses default values for the Oracle Home and
Listener configuration Therefore if you use multiple Oracle Homes you must specify the
new Oracle home as well as the listener port number You can change these values on the
installer Summary screen during the database instance installation On the Summary screen check
both Oracle gt Database System and Oracle gt Listener Configuration and use the Revise button On the
upcoming screen change the Oracle Home and the Listener port number Make sure that
you use a free port number and do not use the numbers 1521 or 1527 as these might already
be in use by default
9 We recommend that you delete the directory userprofilesdtgui
10 IBM DB2 for Linux and UNIX and Windows If not already done install the DB2 license
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
11 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running the Installer
3260 CUSTOMER 2012-11-27
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
Not valid for Sybase 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
httpservicesapcominstallnw70
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3360
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 the installer [page 29] 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 40] 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3460 CUSTOMER 2012-11-27
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 central instance host of the source system you run the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
12 On the database host of the source system you run the installer [page 29] to remove the Java database
schema
13 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
14 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
15 If required and not already done so you configure the CTS Deploy Web Service [page 40] on the ABAP
system
16 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3560
5 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 release
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
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 the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
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 40] on the ABAP
system
15 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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3660 CUSTOMER 2012-11-27
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
Move SCS to New or Other Cluster
The installer exports the Java stack of the dual-stack cluster system and uses this export to install
a central services instance and a central instance on a separate cluster system for Java Additionally
the installer adapts the Java schema of the database of the former dual-stack cluster system to the
target Java cluster system
Figure 6 Split Option Keep Database for High-Availability Systems mdash Move SCS to New or Other
Cluster
Keep SCS on the Source Cluster System
The installer exports the Java central services instance of the source cluster system and uses this
export to install the SCS with a new system ID in a separate cluster on the target cluster system
Additionally the installer adapts the Java schema of the database to the target Java SID
NOTE
This scenario is supported as of Windows Server 2008
2 Split Options Covered by this Guide
22 Split Option Keep Database
1460 CUSTOMER 2012-11-27
Figure 7 Split Option Keep Database for High-Availability Systems mdash Keep SCS on the Source
Cluster System
After the installation has finished and the System Landscape Directory has been reconfigured the
installer removes all Java parts from the dual-stack cluster system except the Java database schema
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-11-27 CUSTOMER 1560
This page is left blank for documents that are printed on both sides
3 Planning
31 Planning Checklist
RECOMMENDATION
We recommend that you first perform the dual-stack split procedure in a test system to identify
possible further application-specific post-split activities required for your scenario
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 19]
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 19]
System Landscape Directory (SLD)
You can ignore SLD parameters
Oracle SAP System Database Parameters Java database schema
3 Planning
31 Planning Checklist
2012-11-27 CUSTOMER 1760
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
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 administrator
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
5 MS SQL Server Oracle For the database installation you decide how to distribute your database
components to disk
For more information see Distribution of SAP System Components to Disk in the installation documentation
of your release
6 SAP MaxDB For the database installation you decide how to distribute your system components
to disk
For more information see Distribution of SAP System Components to Disk in the installation documentation
of your release
7 IBM DB2 for Linux 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 release
8 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
9 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 49]
10 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
11 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
12 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
13 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
14 You can continue with Preparation [page 21]
Split Option ldquoKeep Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
CAUTION
Sybase Split option ldquoKeep Databaserdquo is not supported
3 Planning
31 Planning Checklist
1860 CUSTOMER 2012-11-27
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 19]
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 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 19]
System Landscape Directory (SLD)
You can ignore SLD parameters
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
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 49]
7 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
8 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
9 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
10 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
11 You can continue with Preparation [page 21]
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
3 Planning
32 User Management
2012-11-27 CUSTOMER 1960
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
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
2060 CUSTOMER 2012-11-27
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 You disable the Windows Server firewall on each host
For more information about disabling the Windows firewall see the relevant section in the
installation documentation of your release
2 You perform basic preparations on Windows
For more information see Performing Basic Windows Preparation Steps in the installation documentation
of your release
3 You check that you have the user authorization required for running the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
4 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
5 Only valid for HA (UNIX) |
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) |
6 If required you prepare the SAP system transport host for your SAP system
For more information see Preparing the SAP System Transport Host in the installation documentation
of your release
7 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
4 Preparation
41 Preparation Checklist
2012-11-27 CUSTOMER 2160
8 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 Dual Stack Split Installation Media [page 25]
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 |
9 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) |
10 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) |
11 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 22] of
the dual-stack system
12 You can continue with Splitting [page 27]
42 Performing a Full System Backup
NOTE
This section is not relevant if your database is Sybase
4 Preparation
42 Performing a Full System Backup
2260 CUSTOMER 2012-11-27
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
NOTE
If your system is a high-availability system make sure that you perform a backup of both cluster
nodes of the dual-stack system
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] for your release and database at
DatabaseSAP NetWeaver Release Path in Help Portal
SAP MaxDB SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for MaxDB
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 CapabilityGeneral 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
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for Oracle
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 CapabilityGeneral 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 Linux UNIX and Windows
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
4 Preparation
42 Performing a Full System Backup
2012-11-27 CUSTOMER 2360
DatabaseSAP NetWeaver Release Path in Help Portal
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 CapabilityGeneral 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 CapabilityGeneral 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 zOS
Microsoft SQL Server
SAP NetWeaver 70
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 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 CapabilityGeneral 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
2460 CUSTOMER 2012-11-27
43 Preparing the Dual Stack Split Installation Media
This section describes how to prepare the installation media that is required for the dual stack split
using the installer
Procedure
1 Download the installation media from the software distribution center on SAP Service Marketplace
using the following path
httpservicesapcomswdc Support Package and Patches A - Z Index S SL TOOLSET SL
TOOLSET 10 Entry by Component Dual-Stack Split
2 Create a download directory on the host on which you want to run the DualndashStack Split tool
3 Unpack the DualndashStack Split tool archive to a local directory using the following command
SAPCAR ndashxvf ltdownload directorygtltpathgtltArchivegtSAR -R ltunpack directorygt
4 Preparation
43 Preparing the Dual Stack Split Installation Media
2012-11-27 CUSTOMER 2560
This page is left blank for documents that are printed on both sides
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
NOTE
Sybase Split option ldquoKeep Databaserdquo is not supported You have to consider only the steps
described in section Move Java Database
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Oracle You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your release
2 Oracle If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your release
3 MS SQL Server You install the MS SQL Server database software
For more information see Installing the SQL Server Database Software in the installation documentation
of your release
4 You export the Java stack using the installer [page 29]
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 48]
5 You restart the source system
6 You run the installer [page 29] to install a Java only system using the export from the dual-stack
system
5 Splitting
51 Splitting Checklist
2012-11-27 CUSTOMER 2760
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 installer dialog
7 You continue with Follow-Up Activities [page 33]
Distributed System
1 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 release
2 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 release
3 On the database instance host of the dual-stack system you run the installer [page 29] to export the
Java database schema
4 On the central instance host of the dual-stack system you run the installer [page 29] 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 48]
5 You restart the source system
6 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
7 You run the installer [page 29] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
9 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2860 CUSTOMER 2012-11-27
Keep Database
1 On the central instance host of the dual-stack system you run the installer [page 29] to export 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 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 48]
2 You restart the source system
3 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
4 On the database instance host of the dual-stack system you run the installer [page 29] 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 the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
6 You continue with Follow-Up Activities [page 33]
52 Running the Installer
This section describes how to run the installer The installer includes a GUI client and a GUI server
which both use Java
The procedure describes an installation where the installer GUI client and GUI server are running on
the same host In the following GUI client and GUI server are addressed as ldquonstaller GUIrdquo
Useful Information About the Installer
When you start the installer it automatically starts the installer GUI
The installer creates the installation directory sapinst_instdir which is located directly in the
ProgramFiles directory If the installer is not able to create sapinst_instdir there it tries to
create sapinst_instdir in the directory defined by the environment variable TEMP
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 2960
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
The installer creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt which is located in ProgramFiles
The installer extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is
located in TEMP TMP TMPDIR or SystemRoot These files are deleted after the installer 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 the installer cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default port 21212 is used for communication between the installer
GUI server and the installer GUI client If this port is already in use you see an error message
In this case or if you want the installer to use a specific port open a command prompt and change
to the required directory to which you unpacked the DSS645_IM_ltplatformgtSAR file
Execute sapinstexe with the following command line parameter
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
To see a list of all available installer properties open a command prompt and start the installer
with command line parameter -p
sapinstexe -p
If you need to run the installer in accessibility mode make sure that you have activated and adjusted
accessibility settings as described in Running the Installer in Accessibility Mode in the installation
documentation of your release
If required you can stop the installer by choosing SAPinst Cancel in the installer GUI menu
Prerequisites
Make sure that you use an account with the required user authorization to run the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
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
the installer
Before you start the installer read SAP Note 1697164 which contains important information how
to run the installer
5 Splitting
52 Running the Installer
3060 CUSTOMER 2012-11-27
Procedure
1 Log on to the installation host using an account with the required user authorization to run the
installer
CAUTION
Do not use an existing ltsapsidgtadm user
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 Preparing the DualndashStack Split Installation Media [page 25]
3 Start the installer by double-clicking sapinstexe from the directory to which you unpacked the
DSS645_IM_ltplatformgtSAR file
NOTE
If you need to perform the installation in accessibility mode open a command prompt change
to the ltpath to unpack directorygt directory and execute sapinstexe ndashaccessible
For more information see Running the Installer in Accessibility Mode in the installation
documentation of your release
The GUI starts automatically by displaying the Welcome screen
4 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
CAUTION
Sybase Split options ldquoMove Java Databaserdquo and ldquoKeep Databaserdquo are not available in the
Welcome screen but only the steps valid for split option ldquoMove Java Databaserdquo are listed
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
5 Choose Next
6 If the installer prompts you to log off from your system log off and on again
The installer restarts automatically
7 Follow the instructions in the installer input screens and enter the required parameters
NOTE
If the installer 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 the installer displays the Parameter Summary
screen This screen shows both the parameters that you entered and those that the installer set by
default If required you can revise the parameters before starting the split procedure
8 To start the dual-stack split choose Start
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 3160
The installer starts and displays the progress of the split procedure
When the split option has finished successfully the installer displays the message Execution of
ltOption_Namegt has completed
CAUTION
Multiple Oracle Homes only The installer uses default values for the Oracle Home and
Listener configuration Therefore if you use multiple Oracle Homes you must specify the
new Oracle home as well as the listener port number You can change these values on the
installer Summary screen during the database instance installation On the Summary screen check
both Oracle gt Database System and Oracle gt Listener Configuration and use the Revise button On the
upcoming screen change the Oracle Home and the Listener port number Make sure that
you use a free port number and do not use the numbers 1521 or 1527 as these might already
be in use by default
9 We recommend that you delete the directory userprofilesdtgui
10 IBM DB2 for Linux and UNIX and Windows If not already done install the DB2 license
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
11 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running the Installer
3260 CUSTOMER 2012-11-27
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
Not valid for Sybase 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
httpservicesapcominstallnw70
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3360
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 the installer [page 29] 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 40] 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3460 CUSTOMER 2012-11-27
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 central instance host of the source system you run the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
12 On the database host of the source system you run the installer [page 29] to remove the Java database
schema
13 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
14 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
15 If required and not already done so you configure the CTS Deploy Web Service [page 40] on the ABAP
system
16 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3560
5 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 release
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
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 the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
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 40] on the ABAP
system
15 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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3660 CUSTOMER 2012-11-27
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
Figure 7 Split Option Keep Database for High-Availability Systems mdash Keep SCS on the Source
Cluster System
After the installation has finished and the System Landscape Directory has been reconfigured the
installer removes all Java parts from the dual-stack cluster system except the Java database schema
2 Split Options Covered by this Guide
22 Split Option Keep Database
2012-11-27 CUSTOMER 1560
This page is left blank for documents that are printed on both sides
3 Planning
31 Planning Checklist
RECOMMENDATION
We recommend that you first perform the dual-stack split procedure in a test system to identify
possible further application-specific post-split activities required for your scenario
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 19]
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 19]
System Landscape Directory (SLD)
You can ignore SLD parameters
Oracle SAP System Database Parameters Java database schema
3 Planning
31 Planning Checklist
2012-11-27 CUSTOMER 1760
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
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 administrator
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
5 MS SQL Server Oracle For the database installation you decide how to distribute your database
components to disk
For more information see Distribution of SAP System Components to Disk in the installation documentation
of your release
6 SAP MaxDB For the database installation you decide how to distribute your system components
to disk
For more information see Distribution of SAP System Components to Disk in the installation documentation
of your release
7 IBM DB2 for Linux 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 release
8 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
9 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 49]
10 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
11 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
12 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
13 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
14 You can continue with Preparation [page 21]
Split Option ldquoKeep Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
CAUTION
Sybase Split option ldquoKeep Databaserdquo is not supported
3 Planning
31 Planning Checklist
1860 CUSTOMER 2012-11-27
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 19]
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 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 19]
System Landscape Directory (SLD)
You can ignore SLD parameters
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
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 49]
7 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
8 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
9 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
10 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
11 You can continue with Preparation [page 21]
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
3 Planning
32 User Management
2012-11-27 CUSTOMER 1960
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
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
2060 CUSTOMER 2012-11-27
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 You disable the Windows Server firewall on each host
For more information about disabling the Windows firewall see the relevant section in the
installation documentation of your release
2 You perform basic preparations on Windows
For more information see Performing Basic Windows Preparation Steps in the installation documentation
of your release
3 You check that you have the user authorization required for running the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
4 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
5 Only valid for HA (UNIX) |
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) |
6 If required you prepare the SAP system transport host for your SAP system
For more information see Preparing the SAP System Transport Host in the installation documentation
of your release
7 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
4 Preparation
41 Preparation Checklist
2012-11-27 CUSTOMER 2160
8 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 Dual Stack Split Installation Media [page 25]
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 |
9 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) |
10 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) |
11 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 22] of
the dual-stack system
12 You can continue with Splitting [page 27]
42 Performing a Full System Backup
NOTE
This section is not relevant if your database is Sybase
4 Preparation
42 Performing a Full System Backup
2260 CUSTOMER 2012-11-27
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
NOTE
If your system is a high-availability system make sure that you perform a backup of both cluster
nodes of the dual-stack system
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] for your release and database at
DatabaseSAP NetWeaver Release Path in Help Portal
SAP MaxDB SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for MaxDB
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 CapabilityGeneral 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
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for Oracle
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 CapabilityGeneral 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 Linux UNIX and Windows
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
4 Preparation
42 Performing a Full System Backup
2012-11-27 CUSTOMER 2360
DatabaseSAP NetWeaver Release Path in Help Portal
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 CapabilityGeneral 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 CapabilityGeneral 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 zOS
Microsoft SQL Server
SAP NetWeaver 70
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 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 CapabilityGeneral 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
2460 CUSTOMER 2012-11-27
43 Preparing the Dual Stack Split Installation Media
This section describes how to prepare the installation media that is required for the dual stack split
using the installer
Procedure
1 Download the installation media from the software distribution center on SAP Service Marketplace
using the following path
httpservicesapcomswdc Support Package and Patches A - Z Index S SL TOOLSET SL
TOOLSET 10 Entry by Component Dual-Stack Split
2 Create a download directory on the host on which you want to run the DualndashStack Split tool
3 Unpack the DualndashStack Split tool archive to a local directory using the following command
SAPCAR ndashxvf ltdownload directorygtltpathgtltArchivegtSAR -R ltunpack directorygt
4 Preparation
43 Preparing the Dual Stack Split Installation Media
2012-11-27 CUSTOMER 2560
This page is left blank for documents that are printed on both sides
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
NOTE
Sybase Split option ldquoKeep Databaserdquo is not supported You have to consider only the steps
described in section Move Java Database
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Oracle You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your release
2 Oracle If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your release
3 MS SQL Server You install the MS SQL Server database software
For more information see Installing the SQL Server Database Software in the installation documentation
of your release
4 You export the Java stack using the installer [page 29]
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 48]
5 You restart the source system
6 You run the installer [page 29] to install a Java only system using the export from the dual-stack
system
5 Splitting
51 Splitting Checklist
2012-11-27 CUSTOMER 2760
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 installer dialog
7 You continue with Follow-Up Activities [page 33]
Distributed System
1 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 release
2 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 release
3 On the database instance host of the dual-stack system you run the installer [page 29] to export the
Java database schema
4 On the central instance host of the dual-stack system you run the installer [page 29] 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 48]
5 You restart the source system
6 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
7 You run the installer [page 29] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
9 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2860 CUSTOMER 2012-11-27
Keep Database
1 On the central instance host of the dual-stack system you run the installer [page 29] to export 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 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 48]
2 You restart the source system
3 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
4 On the database instance host of the dual-stack system you run the installer [page 29] 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 the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
6 You continue with Follow-Up Activities [page 33]
52 Running the Installer
This section describes how to run the installer The installer includes a GUI client and a GUI server
which both use Java
The procedure describes an installation where the installer GUI client and GUI server are running on
the same host In the following GUI client and GUI server are addressed as ldquonstaller GUIrdquo
Useful Information About the Installer
When you start the installer it automatically starts the installer GUI
The installer creates the installation directory sapinst_instdir which is located directly in the
ProgramFiles directory If the installer is not able to create sapinst_instdir there it tries to
create sapinst_instdir in the directory defined by the environment variable TEMP
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 2960
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
The installer creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt which is located in ProgramFiles
The installer extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is
located in TEMP TMP TMPDIR or SystemRoot These files are deleted after the installer 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 the installer cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default port 21212 is used for communication between the installer
GUI server and the installer GUI client If this port is already in use you see an error message
In this case or if you want the installer to use a specific port open a command prompt and change
to the required directory to which you unpacked the DSS645_IM_ltplatformgtSAR file
Execute sapinstexe with the following command line parameter
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
To see a list of all available installer properties open a command prompt and start the installer
with command line parameter -p
sapinstexe -p
If you need to run the installer in accessibility mode make sure that you have activated and adjusted
accessibility settings as described in Running the Installer in Accessibility Mode in the installation
documentation of your release
If required you can stop the installer by choosing SAPinst Cancel in the installer GUI menu
Prerequisites
Make sure that you use an account with the required user authorization to run the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
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
the installer
Before you start the installer read SAP Note 1697164 which contains important information how
to run the installer
5 Splitting
52 Running the Installer
3060 CUSTOMER 2012-11-27
Procedure
1 Log on to the installation host using an account with the required user authorization to run the
installer
CAUTION
Do not use an existing ltsapsidgtadm user
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 Preparing the DualndashStack Split Installation Media [page 25]
3 Start the installer by double-clicking sapinstexe from the directory to which you unpacked the
DSS645_IM_ltplatformgtSAR file
NOTE
If you need to perform the installation in accessibility mode open a command prompt change
to the ltpath to unpack directorygt directory and execute sapinstexe ndashaccessible
For more information see Running the Installer in Accessibility Mode in the installation
documentation of your release
The GUI starts automatically by displaying the Welcome screen
4 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
CAUTION
Sybase Split options ldquoMove Java Databaserdquo and ldquoKeep Databaserdquo are not available in the
Welcome screen but only the steps valid for split option ldquoMove Java Databaserdquo are listed
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
5 Choose Next
6 If the installer prompts you to log off from your system log off and on again
The installer restarts automatically
7 Follow the instructions in the installer input screens and enter the required parameters
NOTE
If the installer 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 the installer displays the Parameter Summary
screen This screen shows both the parameters that you entered and those that the installer set by
default If required you can revise the parameters before starting the split procedure
8 To start the dual-stack split choose Start
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 3160
The installer starts and displays the progress of the split procedure
When the split option has finished successfully the installer displays the message Execution of
ltOption_Namegt has completed
CAUTION
Multiple Oracle Homes only The installer uses default values for the Oracle Home and
Listener configuration Therefore if you use multiple Oracle Homes you must specify the
new Oracle home as well as the listener port number You can change these values on the
installer Summary screen during the database instance installation On the Summary screen check
both Oracle gt Database System and Oracle gt Listener Configuration and use the Revise button On the
upcoming screen change the Oracle Home and the Listener port number Make sure that
you use a free port number and do not use the numbers 1521 or 1527 as these might already
be in use by default
9 We recommend that you delete the directory userprofilesdtgui
10 IBM DB2 for Linux and UNIX and Windows If not already done install the DB2 license
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
11 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running the Installer
3260 CUSTOMER 2012-11-27
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
Not valid for Sybase 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
httpservicesapcominstallnw70
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3360
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 the installer [page 29] 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 40] 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3460 CUSTOMER 2012-11-27
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 central instance host of the source system you run the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
12 On the database host of the source system you run the installer [page 29] to remove the Java database
schema
13 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
14 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
15 If required and not already done so you configure the CTS Deploy Web Service [page 40] on the ABAP
system
16 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3560
5 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 release
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
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 the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
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 40] on the ABAP
system
15 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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3660 CUSTOMER 2012-11-27
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 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
3 Planning
31 Planning Checklist
RECOMMENDATION
We recommend that you first perform the dual-stack split procedure in a test system to identify
possible further application-specific post-split activities required for your scenario
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 19]
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 19]
System Landscape Directory (SLD)
You can ignore SLD parameters
Oracle SAP System Database Parameters Java database schema
3 Planning
31 Planning Checklist
2012-11-27 CUSTOMER 1760
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
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 administrator
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
5 MS SQL Server Oracle For the database installation you decide how to distribute your database
components to disk
For more information see Distribution of SAP System Components to Disk in the installation documentation
of your release
6 SAP MaxDB For the database installation you decide how to distribute your system components
to disk
For more information see Distribution of SAP System Components to Disk in the installation documentation
of your release
7 IBM DB2 for Linux 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 release
8 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
9 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 49]
10 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
11 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
12 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
13 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
14 You can continue with Preparation [page 21]
Split Option ldquoKeep Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
CAUTION
Sybase Split option ldquoKeep Databaserdquo is not supported
3 Planning
31 Planning Checklist
1860 CUSTOMER 2012-11-27
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 19]
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 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 19]
System Landscape Directory (SLD)
You can ignore SLD parameters
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
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 49]
7 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
8 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
9 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
10 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
11 You can continue with Preparation [page 21]
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
3 Planning
32 User Management
2012-11-27 CUSTOMER 1960
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
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
2060 CUSTOMER 2012-11-27
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 You disable the Windows Server firewall on each host
For more information about disabling the Windows firewall see the relevant section in the
installation documentation of your release
2 You perform basic preparations on Windows
For more information see Performing Basic Windows Preparation Steps in the installation documentation
of your release
3 You check that you have the user authorization required for running the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
4 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
5 Only valid for HA (UNIX) |
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) |
6 If required you prepare the SAP system transport host for your SAP system
For more information see Preparing the SAP System Transport Host in the installation documentation
of your release
7 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
4 Preparation
41 Preparation Checklist
2012-11-27 CUSTOMER 2160
8 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 Dual Stack Split Installation Media [page 25]
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 |
9 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) |
10 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) |
11 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 22] of
the dual-stack system
12 You can continue with Splitting [page 27]
42 Performing a Full System Backup
NOTE
This section is not relevant if your database is Sybase
4 Preparation
42 Performing a Full System Backup
2260 CUSTOMER 2012-11-27
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
NOTE
If your system is a high-availability system make sure that you perform a backup of both cluster
nodes of the dual-stack system
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] for your release and database at
DatabaseSAP NetWeaver Release Path in Help Portal
SAP MaxDB SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for MaxDB
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 CapabilityGeneral 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
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for Oracle
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 CapabilityGeneral 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 Linux UNIX and Windows
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
4 Preparation
42 Performing a Full System Backup
2012-11-27 CUSTOMER 2360
DatabaseSAP NetWeaver Release Path in Help Portal
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 CapabilityGeneral 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 CapabilityGeneral 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 zOS
Microsoft SQL Server
SAP NetWeaver 70
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 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 CapabilityGeneral 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
2460 CUSTOMER 2012-11-27
43 Preparing the Dual Stack Split Installation Media
This section describes how to prepare the installation media that is required for the dual stack split
using the installer
Procedure
1 Download the installation media from the software distribution center on SAP Service Marketplace
using the following path
httpservicesapcomswdc Support Package and Patches A - Z Index S SL TOOLSET SL
TOOLSET 10 Entry by Component Dual-Stack Split
2 Create a download directory on the host on which you want to run the DualndashStack Split tool
3 Unpack the DualndashStack Split tool archive to a local directory using the following command
SAPCAR ndashxvf ltdownload directorygtltpathgtltArchivegtSAR -R ltunpack directorygt
4 Preparation
43 Preparing the Dual Stack Split Installation Media
2012-11-27 CUSTOMER 2560
This page is left blank for documents that are printed on both sides
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
NOTE
Sybase Split option ldquoKeep Databaserdquo is not supported You have to consider only the steps
described in section Move Java Database
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Oracle You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your release
2 Oracle If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your release
3 MS SQL Server You install the MS SQL Server database software
For more information see Installing the SQL Server Database Software in the installation documentation
of your release
4 You export the Java stack using the installer [page 29]
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 48]
5 You restart the source system
6 You run the installer [page 29] to install a Java only system using the export from the dual-stack
system
5 Splitting
51 Splitting Checklist
2012-11-27 CUSTOMER 2760
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 installer dialog
7 You continue with Follow-Up Activities [page 33]
Distributed System
1 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 release
2 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 release
3 On the database instance host of the dual-stack system you run the installer [page 29] to export the
Java database schema
4 On the central instance host of the dual-stack system you run the installer [page 29] 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 48]
5 You restart the source system
6 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
7 You run the installer [page 29] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
9 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2860 CUSTOMER 2012-11-27
Keep Database
1 On the central instance host of the dual-stack system you run the installer [page 29] to export 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 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 48]
2 You restart the source system
3 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
4 On the database instance host of the dual-stack system you run the installer [page 29] 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 the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
6 You continue with Follow-Up Activities [page 33]
52 Running the Installer
This section describes how to run the installer The installer includes a GUI client and a GUI server
which both use Java
The procedure describes an installation where the installer GUI client and GUI server are running on
the same host In the following GUI client and GUI server are addressed as ldquonstaller GUIrdquo
Useful Information About the Installer
When you start the installer it automatically starts the installer GUI
The installer creates the installation directory sapinst_instdir which is located directly in the
ProgramFiles directory If the installer is not able to create sapinst_instdir there it tries to
create sapinst_instdir in the directory defined by the environment variable TEMP
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 2960
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
The installer creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt which is located in ProgramFiles
The installer extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is
located in TEMP TMP TMPDIR or SystemRoot These files are deleted after the installer 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 the installer cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default port 21212 is used for communication between the installer
GUI server and the installer GUI client If this port is already in use you see an error message
In this case or if you want the installer to use a specific port open a command prompt and change
to the required directory to which you unpacked the DSS645_IM_ltplatformgtSAR file
Execute sapinstexe with the following command line parameter
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
To see a list of all available installer properties open a command prompt and start the installer
with command line parameter -p
sapinstexe -p
If you need to run the installer in accessibility mode make sure that you have activated and adjusted
accessibility settings as described in Running the Installer in Accessibility Mode in the installation
documentation of your release
If required you can stop the installer by choosing SAPinst Cancel in the installer GUI menu
Prerequisites
Make sure that you use an account with the required user authorization to run the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
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
the installer
Before you start the installer read SAP Note 1697164 which contains important information how
to run the installer
5 Splitting
52 Running the Installer
3060 CUSTOMER 2012-11-27
Procedure
1 Log on to the installation host using an account with the required user authorization to run the
installer
CAUTION
Do not use an existing ltsapsidgtadm user
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 Preparing the DualndashStack Split Installation Media [page 25]
3 Start the installer by double-clicking sapinstexe from the directory to which you unpacked the
DSS645_IM_ltplatformgtSAR file
NOTE
If you need to perform the installation in accessibility mode open a command prompt change
to the ltpath to unpack directorygt directory and execute sapinstexe ndashaccessible
For more information see Running the Installer in Accessibility Mode in the installation
documentation of your release
The GUI starts automatically by displaying the Welcome screen
4 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
CAUTION
Sybase Split options ldquoMove Java Databaserdquo and ldquoKeep Databaserdquo are not available in the
Welcome screen but only the steps valid for split option ldquoMove Java Databaserdquo are listed
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
5 Choose Next
6 If the installer prompts you to log off from your system log off and on again
The installer restarts automatically
7 Follow the instructions in the installer input screens and enter the required parameters
NOTE
If the installer 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 the installer displays the Parameter Summary
screen This screen shows both the parameters that you entered and those that the installer set by
default If required you can revise the parameters before starting the split procedure
8 To start the dual-stack split choose Start
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 3160
The installer starts and displays the progress of the split procedure
When the split option has finished successfully the installer displays the message Execution of
ltOption_Namegt has completed
CAUTION
Multiple Oracle Homes only The installer uses default values for the Oracle Home and
Listener configuration Therefore if you use multiple Oracle Homes you must specify the
new Oracle home as well as the listener port number You can change these values on the
installer Summary screen during the database instance installation On the Summary screen check
both Oracle gt Database System and Oracle gt Listener Configuration and use the Revise button On the
upcoming screen change the Oracle Home and the Listener port number Make sure that
you use a free port number and do not use the numbers 1521 or 1527 as these might already
be in use by default
9 We recommend that you delete the directory userprofilesdtgui
10 IBM DB2 for Linux and UNIX and Windows If not already done install the DB2 license
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
11 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running the Installer
3260 CUSTOMER 2012-11-27
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
Not valid for Sybase 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
httpservicesapcominstallnw70
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3360
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 the installer [page 29] 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 40] 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3460 CUSTOMER 2012-11-27
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 central instance host of the source system you run the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
12 On the database host of the source system you run the installer [page 29] to remove the Java database
schema
13 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
14 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
15 If required and not already done so you configure the CTS Deploy Web Service [page 40] on the ABAP
system
16 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3560
5 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 release
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
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 the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
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 40] on the ABAP
system
15 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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3660 CUSTOMER 2012-11-27
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
3 Planning
31 Planning Checklist
RECOMMENDATION
We recommend that you first perform the dual-stack split procedure in a test system to identify
possible further application-specific post-split activities required for your scenario
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 19]
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 19]
System Landscape Directory (SLD)
You can ignore SLD parameters
Oracle SAP System Database Parameters Java database schema
3 Planning
31 Planning Checklist
2012-11-27 CUSTOMER 1760
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
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 administrator
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
5 MS SQL Server Oracle For the database installation you decide how to distribute your database
components to disk
For more information see Distribution of SAP System Components to Disk in the installation documentation
of your release
6 SAP MaxDB For the database installation you decide how to distribute your system components
to disk
For more information see Distribution of SAP System Components to Disk in the installation documentation
of your release
7 IBM DB2 for Linux 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 release
8 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
9 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 49]
10 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
11 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
12 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
13 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
14 You can continue with Preparation [page 21]
Split Option ldquoKeep Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
CAUTION
Sybase Split option ldquoKeep Databaserdquo is not supported
3 Planning
31 Planning Checklist
1860 CUSTOMER 2012-11-27
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 19]
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 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 19]
System Landscape Directory (SLD)
You can ignore SLD parameters
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
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 49]
7 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
8 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
9 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
10 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
11 You can continue with Preparation [page 21]
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
3 Planning
32 User Management
2012-11-27 CUSTOMER 1960
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
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
2060 CUSTOMER 2012-11-27
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 You disable the Windows Server firewall on each host
For more information about disabling the Windows firewall see the relevant section in the
installation documentation of your release
2 You perform basic preparations on Windows
For more information see Performing Basic Windows Preparation Steps in the installation documentation
of your release
3 You check that you have the user authorization required for running the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
4 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
5 Only valid for HA (UNIX) |
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) |
6 If required you prepare the SAP system transport host for your SAP system
For more information see Preparing the SAP System Transport Host in the installation documentation
of your release
7 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
4 Preparation
41 Preparation Checklist
2012-11-27 CUSTOMER 2160
8 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 Dual Stack Split Installation Media [page 25]
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 |
9 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) |
10 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) |
11 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 22] of
the dual-stack system
12 You can continue with Splitting [page 27]
42 Performing a Full System Backup
NOTE
This section is not relevant if your database is Sybase
4 Preparation
42 Performing a Full System Backup
2260 CUSTOMER 2012-11-27
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
NOTE
If your system is a high-availability system make sure that you perform a backup of both cluster
nodes of the dual-stack system
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] for your release and database at
DatabaseSAP NetWeaver Release Path in Help Portal
SAP MaxDB SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for MaxDB
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 CapabilityGeneral 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
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for Oracle
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 CapabilityGeneral 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 Linux UNIX and Windows
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
4 Preparation
42 Performing a Full System Backup
2012-11-27 CUSTOMER 2360
DatabaseSAP NetWeaver Release Path in Help Portal
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 CapabilityGeneral 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 CapabilityGeneral 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 zOS
Microsoft SQL Server
SAP NetWeaver 70
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 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 CapabilityGeneral 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
2460 CUSTOMER 2012-11-27
43 Preparing the Dual Stack Split Installation Media
This section describes how to prepare the installation media that is required for the dual stack split
using the installer
Procedure
1 Download the installation media from the software distribution center on SAP Service Marketplace
using the following path
httpservicesapcomswdc Support Package and Patches A - Z Index S SL TOOLSET SL
TOOLSET 10 Entry by Component Dual-Stack Split
2 Create a download directory on the host on which you want to run the DualndashStack Split tool
3 Unpack the DualndashStack Split tool archive to a local directory using the following command
SAPCAR ndashxvf ltdownload directorygtltpathgtltArchivegtSAR -R ltunpack directorygt
4 Preparation
43 Preparing the Dual Stack Split Installation Media
2012-11-27 CUSTOMER 2560
This page is left blank for documents that are printed on both sides
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
NOTE
Sybase Split option ldquoKeep Databaserdquo is not supported You have to consider only the steps
described in section Move Java Database
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Oracle You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your release
2 Oracle If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your release
3 MS SQL Server You install the MS SQL Server database software
For more information see Installing the SQL Server Database Software in the installation documentation
of your release
4 You export the Java stack using the installer [page 29]
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 48]
5 You restart the source system
6 You run the installer [page 29] to install a Java only system using the export from the dual-stack
system
5 Splitting
51 Splitting Checklist
2012-11-27 CUSTOMER 2760
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 installer dialog
7 You continue with Follow-Up Activities [page 33]
Distributed System
1 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 release
2 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 release
3 On the database instance host of the dual-stack system you run the installer [page 29] to export the
Java database schema
4 On the central instance host of the dual-stack system you run the installer [page 29] 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 48]
5 You restart the source system
6 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
7 You run the installer [page 29] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
9 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2860 CUSTOMER 2012-11-27
Keep Database
1 On the central instance host of the dual-stack system you run the installer [page 29] to export 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 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 48]
2 You restart the source system
3 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
4 On the database instance host of the dual-stack system you run the installer [page 29] 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 the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
6 You continue with Follow-Up Activities [page 33]
52 Running the Installer
This section describes how to run the installer The installer includes a GUI client and a GUI server
which both use Java
The procedure describes an installation where the installer GUI client and GUI server are running on
the same host In the following GUI client and GUI server are addressed as ldquonstaller GUIrdquo
Useful Information About the Installer
When you start the installer it automatically starts the installer GUI
The installer creates the installation directory sapinst_instdir which is located directly in the
ProgramFiles directory If the installer is not able to create sapinst_instdir there it tries to
create sapinst_instdir in the directory defined by the environment variable TEMP
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 2960
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
The installer creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt which is located in ProgramFiles
The installer extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is
located in TEMP TMP TMPDIR or SystemRoot These files are deleted after the installer 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 the installer cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default port 21212 is used for communication between the installer
GUI server and the installer GUI client If this port is already in use you see an error message
In this case or if you want the installer to use a specific port open a command prompt and change
to the required directory to which you unpacked the DSS645_IM_ltplatformgtSAR file
Execute sapinstexe with the following command line parameter
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
To see a list of all available installer properties open a command prompt and start the installer
with command line parameter -p
sapinstexe -p
If you need to run the installer in accessibility mode make sure that you have activated and adjusted
accessibility settings as described in Running the Installer in Accessibility Mode in the installation
documentation of your release
If required you can stop the installer by choosing SAPinst Cancel in the installer GUI menu
Prerequisites
Make sure that you use an account with the required user authorization to run the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
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
the installer
Before you start the installer read SAP Note 1697164 which contains important information how
to run the installer
5 Splitting
52 Running the Installer
3060 CUSTOMER 2012-11-27
Procedure
1 Log on to the installation host using an account with the required user authorization to run the
installer
CAUTION
Do not use an existing ltsapsidgtadm user
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 Preparing the DualndashStack Split Installation Media [page 25]
3 Start the installer by double-clicking sapinstexe from the directory to which you unpacked the
DSS645_IM_ltplatformgtSAR file
NOTE
If you need to perform the installation in accessibility mode open a command prompt change
to the ltpath to unpack directorygt directory and execute sapinstexe ndashaccessible
For more information see Running the Installer in Accessibility Mode in the installation
documentation of your release
The GUI starts automatically by displaying the Welcome screen
4 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
CAUTION
Sybase Split options ldquoMove Java Databaserdquo and ldquoKeep Databaserdquo are not available in the
Welcome screen but only the steps valid for split option ldquoMove Java Databaserdquo are listed
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
5 Choose Next
6 If the installer prompts you to log off from your system log off and on again
The installer restarts automatically
7 Follow the instructions in the installer input screens and enter the required parameters
NOTE
If the installer 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 the installer displays the Parameter Summary
screen This screen shows both the parameters that you entered and those that the installer set by
default If required you can revise the parameters before starting the split procedure
8 To start the dual-stack split choose Start
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 3160
The installer starts and displays the progress of the split procedure
When the split option has finished successfully the installer displays the message Execution of
ltOption_Namegt has completed
CAUTION
Multiple Oracle Homes only The installer uses default values for the Oracle Home and
Listener configuration Therefore if you use multiple Oracle Homes you must specify the
new Oracle home as well as the listener port number You can change these values on the
installer Summary screen during the database instance installation On the Summary screen check
both Oracle gt Database System and Oracle gt Listener Configuration and use the Revise button On the
upcoming screen change the Oracle Home and the Listener port number Make sure that
you use a free port number and do not use the numbers 1521 or 1527 as these might already
be in use by default
9 We recommend that you delete the directory userprofilesdtgui
10 IBM DB2 for Linux and UNIX and Windows If not already done install the DB2 license
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
11 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running the Installer
3260 CUSTOMER 2012-11-27
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
Not valid for Sybase 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
httpservicesapcominstallnw70
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3360
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 the installer [page 29] 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 40] 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3460 CUSTOMER 2012-11-27
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 central instance host of the source system you run the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
12 On the database host of the source system you run the installer [page 29] to remove the Java database
schema
13 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
14 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
15 If required and not already done so you configure the CTS Deploy Web Service [page 40] on the ABAP
system
16 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3560
5 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 release
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
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 the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
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 40] on the ABAP
system
15 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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3660 CUSTOMER 2012-11-27
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
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
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 administrator
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
5 MS SQL Server Oracle For the database installation you decide how to distribute your database
components to disk
For more information see Distribution of SAP System Components to Disk in the installation documentation
of your release
6 SAP MaxDB For the database installation you decide how to distribute your system components
to disk
For more information see Distribution of SAP System Components to Disk in the installation documentation
of your release
7 IBM DB2 for Linux 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 release
8 You decide on the transport host to use
For more information see SAP System Transport Host in the installation documentation of your release
9 You plan for adapting the transport routes within your system landscape For more information
see Splitting Within a System Landscape [page 49]
10 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
11 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
12 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
13 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
14 You can continue with Preparation [page 21]
Split Option ldquoKeep Databaserdquo ndash Checklist for Central Distributed and High-Availability Systems
CAUTION
Sybase Split option ldquoKeep Databaserdquo is not supported
3 Planning
31 Planning Checklist
1860 CUSTOMER 2012-11-27
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 19]
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 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 19]
System Landscape Directory (SLD)
You can ignore SLD parameters
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
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 49]
7 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
8 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
9 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
10 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
11 You can continue with Preparation [page 21]
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
3 Planning
32 User Management
2012-11-27 CUSTOMER 1960
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
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
2060 CUSTOMER 2012-11-27
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 You disable the Windows Server firewall on each host
For more information about disabling the Windows firewall see the relevant section in the
installation documentation of your release
2 You perform basic preparations on Windows
For more information see Performing Basic Windows Preparation Steps in the installation documentation
of your release
3 You check that you have the user authorization required for running the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
4 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
5 Only valid for HA (UNIX) |
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) |
6 If required you prepare the SAP system transport host for your SAP system
For more information see Preparing the SAP System Transport Host in the installation documentation
of your release
7 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
4 Preparation
41 Preparation Checklist
2012-11-27 CUSTOMER 2160
8 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 Dual Stack Split Installation Media [page 25]
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 |
9 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) |
10 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) |
11 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 22] of
the dual-stack system
12 You can continue with Splitting [page 27]
42 Performing a Full System Backup
NOTE
This section is not relevant if your database is Sybase
4 Preparation
42 Performing a Full System Backup
2260 CUSTOMER 2012-11-27
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
NOTE
If your system is a high-availability system make sure that you perform a backup of both cluster
nodes of the dual-stack system
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] for your release and database at
DatabaseSAP NetWeaver Release Path in Help Portal
SAP MaxDB SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for MaxDB
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 CapabilityGeneral 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
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for Oracle
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 CapabilityGeneral 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 Linux UNIX and Windows
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
4 Preparation
42 Performing a Full System Backup
2012-11-27 CUSTOMER 2360
DatabaseSAP NetWeaver Release Path in Help Portal
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 CapabilityGeneral 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 CapabilityGeneral 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 zOS
Microsoft SQL Server
SAP NetWeaver 70
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 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 CapabilityGeneral 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
2460 CUSTOMER 2012-11-27
43 Preparing the Dual Stack Split Installation Media
This section describes how to prepare the installation media that is required for the dual stack split
using the installer
Procedure
1 Download the installation media from the software distribution center on SAP Service Marketplace
using the following path
httpservicesapcomswdc Support Package and Patches A - Z Index S SL TOOLSET SL
TOOLSET 10 Entry by Component Dual-Stack Split
2 Create a download directory on the host on which you want to run the DualndashStack Split tool
3 Unpack the DualndashStack Split tool archive to a local directory using the following command
SAPCAR ndashxvf ltdownload directorygtltpathgtltArchivegtSAR -R ltunpack directorygt
4 Preparation
43 Preparing the Dual Stack Split Installation Media
2012-11-27 CUSTOMER 2560
This page is left blank for documents that are printed on both sides
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
NOTE
Sybase Split option ldquoKeep Databaserdquo is not supported You have to consider only the steps
described in section Move Java Database
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Oracle You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your release
2 Oracle If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your release
3 MS SQL Server You install the MS SQL Server database software
For more information see Installing the SQL Server Database Software in the installation documentation
of your release
4 You export the Java stack using the installer [page 29]
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 48]
5 You restart the source system
6 You run the installer [page 29] to install a Java only system using the export from the dual-stack
system
5 Splitting
51 Splitting Checklist
2012-11-27 CUSTOMER 2760
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 installer dialog
7 You continue with Follow-Up Activities [page 33]
Distributed System
1 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 release
2 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 release
3 On the database instance host of the dual-stack system you run the installer [page 29] to export the
Java database schema
4 On the central instance host of the dual-stack system you run the installer [page 29] 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 48]
5 You restart the source system
6 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
7 You run the installer [page 29] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
9 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2860 CUSTOMER 2012-11-27
Keep Database
1 On the central instance host of the dual-stack system you run the installer [page 29] to export 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 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 48]
2 You restart the source system
3 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
4 On the database instance host of the dual-stack system you run the installer [page 29] 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 the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
6 You continue with Follow-Up Activities [page 33]
52 Running the Installer
This section describes how to run the installer The installer includes a GUI client and a GUI server
which both use Java
The procedure describes an installation where the installer GUI client and GUI server are running on
the same host In the following GUI client and GUI server are addressed as ldquonstaller GUIrdquo
Useful Information About the Installer
When you start the installer it automatically starts the installer GUI
The installer creates the installation directory sapinst_instdir which is located directly in the
ProgramFiles directory If the installer is not able to create sapinst_instdir there it tries to
create sapinst_instdir in the directory defined by the environment variable TEMP
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 2960
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
The installer creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt which is located in ProgramFiles
The installer extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is
located in TEMP TMP TMPDIR or SystemRoot These files are deleted after the installer 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 the installer cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default port 21212 is used for communication between the installer
GUI server and the installer GUI client If this port is already in use you see an error message
In this case or if you want the installer to use a specific port open a command prompt and change
to the required directory to which you unpacked the DSS645_IM_ltplatformgtSAR file
Execute sapinstexe with the following command line parameter
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
To see a list of all available installer properties open a command prompt and start the installer
with command line parameter -p
sapinstexe -p
If you need to run the installer in accessibility mode make sure that you have activated and adjusted
accessibility settings as described in Running the Installer in Accessibility Mode in the installation
documentation of your release
If required you can stop the installer by choosing SAPinst Cancel in the installer GUI menu
Prerequisites
Make sure that you use an account with the required user authorization to run the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
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
the installer
Before you start the installer read SAP Note 1697164 which contains important information how
to run the installer
5 Splitting
52 Running the Installer
3060 CUSTOMER 2012-11-27
Procedure
1 Log on to the installation host using an account with the required user authorization to run the
installer
CAUTION
Do not use an existing ltsapsidgtadm user
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 Preparing the DualndashStack Split Installation Media [page 25]
3 Start the installer by double-clicking sapinstexe from the directory to which you unpacked the
DSS645_IM_ltplatformgtSAR file
NOTE
If you need to perform the installation in accessibility mode open a command prompt change
to the ltpath to unpack directorygt directory and execute sapinstexe ndashaccessible
For more information see Running the Installer in Accessibility Mode in the installation
documentation of your release
The GUI starts automatically by displaying the Welcome screen
4 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
CAUTION
Sybase Split options ldquoMove Java Databaserdquo and ldquoKeep Databaserdquo are not available in the
Welcome screen but only the steps valid for split option ldquoMove Java Databaserdquo are listed
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
5 Choose Next
6 If the installer prompts you to log off from your system log off and on again
The installer restarts automatically
7 Follow the instructions in the installer input screens and enter the required parameters
NOTE
If the installer 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 the installer displays the Parameter Summary
screen This screen shows both the parameters that you entered and those that the installer set by
default If required you can revise the parameters before starting the split procedure
8 To start the dual-stack split choose Start
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 3160
The installer starts and displays the progress of the split procedure
When the split option has finished successfully the installer displays the message Execution of
ltOption_Namegt has completed
CAUTION
Multiple Oracle Homes only The installer uses default values for the Oracle Home and
Listener configuration Therefore if you use multiple Oracle Homes you must specify the
new Oracle home as well as the listener port number You can change these values on the
installer Summary screen during the database instance installation On the Summary screen check
both Oracle gt Database System and Oracle gt Listener Configuration and use the Revise button On the
upcoming screen change the Oracle Home and the Listener port number Make sure that
you use a free port number and do not use the numbers 1521 or 1527 as these might already
be in use by default
9 We recommend that you delete the directory userprofilesdtgui
10 IBM DB2 for Linux and UNIX and Windows If not already done install the DB2 license
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
11 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running the Installer
3260 CUSTOMER 2012-11-27
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
Not valid for Sybase 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
httpservicesapcominstallnw70
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3360
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 the installer [page 29] 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 40] 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3460 CUSTOMER 2012-11-27
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 central instance host of the source system you run the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
12 On the database host of the source system you run the installer [page 29] to remove the Java database
schema
13 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
14 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
15 If required and not already done so you configure the CTS Deploy Web Service [page 40] on the ABAP
system
16 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3560
5 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 release
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
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 the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
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 40] on the ABAP
system
15 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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3660 CUSTOMER 2012-11-27
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
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 19]
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 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 19]
System Landscape Directory (SLD)
You can ignore SLD parameters
4 You decide whether you want to perform a domain or local installation
For more information see Domain or Local Installation in the installation documentation of your release
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 49]
7 Oracle You decide if you want to use Multiple Oracle Homes
For more information see Multiple Oracle Homes in the installation documentation of your release
8 Only valid for HA (UNIX) |
To install a high-availability system you read Planning the Switchover Cluster in the installation
documentation of your releaseEnd of HA (UNIX) |
9 IBM DB2 for zOS If you want to execute a Software Life-Cycle Option with the installer in an SAP
system with thick client connectivity see Special Considerations Regarding Connectivity for Software Life-
Cycle Options in the installation documentation of your release
10 To install a high-availability system with Microsoft Cluster Service (MSCS) you perform the
MSCS-specific planning steps as described in the installation documentation of your release
11 You can continue with Preparation [page 21]
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
3 Planning
32 User Management
2012-11-27 CUSTOMER 1960
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
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
2060 CUSTOMER 2012-11-27
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 You disable the Windows Server firewall on each host
For more information about disabling the Windows firewall see the relevant section in the
installation documentation of your release
2 You perform basic preparations on Windows
For more information see Performing Basic Windows Preparation Steps in the installation documentation
of your release
3 You check that you have the user authorization required for running the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
4 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
5 Only valid for HA (UNIX) |
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) |
6 If required you prepare the SAP system transport host for your SAP system
For more information see Preparing the SAP System Transport Host in the installation documentation
of your release
7 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
4 Preparation
41 Preparation Checklist
2012-11-27 CUSTOMER 2160
8 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 Dual Stack Split Installation Media [page 25]
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 |
9 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) |
10 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) |
11 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 22] of
the dual-stack system
12 You can continue with Splitting [page 27]
42 Performing a Full System Backup
NOTE
This section is not relevant if your database is Sybase
4 Preparation
42 Performing a Full System Backup
2260 CUSTOMER 2012-11-27
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
NOTE
If your system is a high-availability system make sure that you perform a backup of both cluster
nodes of the dual-stack system
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] for your release and database at
DatabaseSAP NetWeaver Release Path in Help Portal
SAP MaxDB SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for MaxDB
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 CapabilityGeneral 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
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for Oracle
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 CapabilityGeneral 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 Linux UNIX and Windows
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
4 Preparation
42 Performing a Full System Backup
2012-11-27 CUSTOMER 2360
DatabaseSAP NetWeaver Release Path in Help Portal
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 CapabilityGeneral 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 CapabilityGeneral 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 zOS
Microsoft SQL Server
SAP NetWeaver 70
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 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 CapabilityGeneral 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
2460 CUSTOMER 2012-11-27
43 Preparing the Dual Stack Split Installation Media
This section describes how to prepare the installation media that is required for the dual stack split
using the installer
Procedure
1 Download the installation media from the software distribution center on SAP Service Marketplace
using the following path
httpservicesapcomswdc Support Package and Patches A - Z Index S SL TOOLSET SL
TOOLSET 10 Entry by Component Dual-Stack Split
2 Create a download directory on the host on which you want to run the DualndashStack Split tool
3 Unpack the DualndashStack Split tool archive to a local directory using the following command
SAPCAR ndashxvf ltdownload directorygtltpathgtltArchivegtSAR -R ltunpack directorygt
4 Preparation
43 Preparing the Dual Stack Split Installation Media
2012-11-27 CUSTOMER 2560
This page is left blank for documents that are printed on both sides
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
NOTE
Sybase Split option ldquoKeep Databaserdquo is not supported You have to consider only the steps
described in section Move Java Database
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Oracle You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your release
2 Oracle If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your release
3 MS SQL Server You install the MS SQL Server database software
For more information see Installing the SQL Server Database Software in the installation documentation
of your release
4 You export the Java stack using the installer [page 29]
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 48]
5 You restart the source system
6 You run the installer [page 29] to install a Java only system using the export from the dual-stack
system
5 Splitting
51 Splitting Checklist
2012-11-27 CUSTOMER 2760
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 installer dialog
7 You continue with Follow-Up Activities [page 33]
Distributed System
1 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 release
2 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 release
3 On the database instance host of the dual-stack system you run the installer [page 29] to export the
Java database schema
4 On the central instance host of the dual-stack system you run the installer [page 29] 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 48]
5 You restart the source system
6 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
7 You run the installer [page 29] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
9 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2860 CUSTOMER 2012-11-27
Keep Database
1 On the central instance host of the dual-stack system you run the installer [page 29] to export 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 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 48]
2 You restart the source system
3 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
4 On the database instance host of the dual-stack system you run the installer [page 29] 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 the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
6 You continue with Follow-Up Activities [page 33]
52 Running the Installer
This section describes how to run the installer The installer includes a GUI client and a GUI server
which both use Java
The procedure describes an installation where the installer GUI client and GUI server are running on
the same host In the following GUI client and GUI server are addressed as ldquonstaller GUIrdquo
Useful Information About the Installer
When you start the installer it automatically starts the installer GUI
The installer creates the installation directory sapinst_instdir which is located directly in the
ProgramFiles directory If the installer is not able to create sapinst_instdir there it tries to
create sapinst_instdir in the directory defined by the environment variable TEMP
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 2960
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
The installer creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt which is located in ProgramFiles
The installer extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is
located in TEMP TMP TMPDIR or SystemRoot These files are deleted after the installer 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 the installer cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default port 21212 is used for communication between the installer
GUI server and the installer GUI client If this port is already in use you see an error message
In this case or if you want the installer to use a specific port open a command prompt and change
to the required directory to which you unpacked the DSS645_IM_ltplatformgtSAR file
Execute sapinstexe with the following command line parameter
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
To see a list of all available installer properties open a command prompt and start the installer
with command line parameter -p
sapinstexe -p
If you need to run the installer in accessibility mode make sure that you have activated and adjusted
accessibility settings as described in Running the Installer in Accessibility Mode in the installation
documentation of your release
If required you can stop the installer by choosing SAPinst Cancel in the installer GUI menu
Prerequisites
Make sure that you use an account with the required user authorization to run the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
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
the installer
Before you start the installer read SAP Note 1697164 which contains important information how
to run the installer
5 Splitting
52 Running the Installer
3060 CUSTOMER 2012-11-27
Procedure
1 Log on to the installation host using an account with the required user authorization to run the
installer
CAUTION
Do not use an existing ltsapsidgtadm user
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 Preparing the DualndashStack Split Installation Media [page 25]
3 Start the installer by double-clicking sapinstexe from the directory to which you unpacked the
DSS645_IM_ltplatformgtSAR file
NOTE
If you need to perform the installation in accessibility mode open a command prompt change
to the ltpath to unpack directorygt directory and execute sapinstexe ndashaccessible
For more information see Running the Installer in Accessibility Mode in the installation
documentation of your release
The GUI starts automatically by displaying the Welcome screen
4 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
CAUTION
Sybase Split options ldquoMove Java Databaserdquo and ldquoKeep Databaserdquo are not available in the
Welcome screen but only the steps valid for split option ldquoMove Java Databaserdquo are listed
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
5 Choose Next
6 If the installer prompts you to log off from your system log off and on again
The installer restarts automatically
7 Follow the instructions in the installer input screens and enter the required parameters
NOTE
If the installer 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 the installer displays the Parameter Summary
screen This screen shows both the parameters that you entered and those that the installer set by
default If required you can revise the parameters before starting the split procedure
8 To start the dual-stack split choose Start
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 3160
The installer starts and displays the progress of the split procedure
When the split option has finished successfully the installer displays the message Execution of
ltOption_Namegt has completed
CAUTION
Multiple Oracle Homes only The installer uses default values for the Oracle Home and
Listener configuration Therefore if you use multiple Oracle Homes you must specify the
new Oracle home as well as the listener port number You can change these values on the
installer Summary screen during the database instance installation On the Summary screen check
both Oracle gt Database System and Oracle gt Listener Configuration and use the Revise button On the
upcoming screen change the Oracle Home and the Listener port number Make sure that
you use a free port number and do not use the numbers 1521 or 1527 as these might already
be in use by default
9 We recommend that you delete the directory userprofilesdtgui
10 IBM DB2 for Linux and UNIX and Windows If not already done install the DB2 license
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
11 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running the Installer
3260 CUSTOMER 2012-11-27
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
Not valid for Sybase 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
httpservicesapcominstallnw70
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3360
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 the installer [page 29] 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 40] 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3460 CUSTOMER 2012-11-27
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 central instance host of the source system you run the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
12 On the database host of the source system you run the installer [page 29] to remove the Java database
schema
13 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
14 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
15 If required and not already done so you configure the CTS Deploy Web Service [page 40] on the ABAP
system
16 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3560
5 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 release
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
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 the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
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 40] on the ABAP
system
15 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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3660 CUSTOMER 2012-11-27
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
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
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
2060 CUSTOMER 2012-11-27
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 You disable the Windows Server firewall on each host
For more information about disabling the Windows firewall see the relevant section in the
installation documentation of your release
2 You perform basic preparations on Windows
For more information see Performing Basic Windows Preparation Steps in the installation documentation
of your release
3 You check that you have the user authorization required for running the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
4 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
5 Only valid for HA (UNIX) |
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) |
6 If required you prepare the SAP system transport host for your SAP system
For more information see Preparing the SAP System Transport Host in the installation documentation
of your release
7 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
4 Preparation
41 Preparation Checklist
2012-11-27 CUSTOMER 2160
8 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 Dual Stack Split Installation Media [page 25]
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 |
9 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) |
10 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) |
11 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 22] of
the dual-stack system
12 You can continue with Splitting [page 27]
42 Performing a Full System Backup
NOTE
This section is not relevant if your database is Sybase
4 Preparation
42 Performing a Full System Backup
2260 CUSTOMER 2012-11-27
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
NOTE
If your system is a high-availability system make sure that you perform a backup of both cluster
nodes of the dual-stack system
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] for your release and database at
DatabaseSAP NetWeaver Release Path in Help Portal
SAP MaxDB SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for MaxDB
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 CapabilityGeneral 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
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for Oracle
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 CapabilityGeneral 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 Linux UNIX and Windows
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
4 Preparation
42 Performing a Full System Backup
2012-11-27 CUSTOMER 2360
DatabaseSAP NetWeaver Release Path in Help Portal
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 CapabilityGeneral 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 CapabilityGeneral 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 zOS
Microsoft SQL Server
SAP NetWeaver 70
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 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 CapabilityGeneral 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
2460 CUSTOMER 2012-11-27
43 Preparing the Dual Stack Split Installation Media
This section describes how to prepare the installation media that is required for the dual stack split
using the installer
Procedure
1 Download the installation media from the software distribution center on SAP Service Marketplace
using the following path
httpservicesapcomswdc Support Package and Patches A - Z Index S SL TOOLSET SL
TOOLSET 10 Entry by Component Dual-Stack Split
2 Create a download directory on the host on which you want to run the DualndashStack Split tool
3 Unpack the DualndashStack Split tool archive to a local directory using the following command
SAPCAR ndashxvf ltdownload directorygtltpathgtltArchivegtSAR -R ltunpack directorygt
4 Preparation
43 Preparing the Dual Stack Split Installation Media
2012-11-27 CUSTOMER 2560
This page is left blank for documents that are printed on both sides
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
NOTE
Sybase Split option ldquoKeep Databaserdquo is not supported You have to consider only the steps
described in section Move Java Database
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Oracle You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your release
2 Oracle If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your release
3 MS SQL Server You install the MS SQL Server database software
For more information see Installing the SQL Server Database Software in the installation documentation
of your release
4 You export the Java stack using the installer [page 29]
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 48]
5 You restart the source system
6 You run the installer [page 29] to install a Java only system using the export from the dual-stack
system
5 Splitting
51 Splitting Checklist
2012-11-27 CUSTOMER 2760
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 installer dialog
7 You continue with Follow-Up Activities [page 33]
Distributed System
1 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 release
2 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 release
3 On the database instance host of the dual-stack system you run the installer [page 29] to export the
Java database schema
4 On the central instance host of the dual-stack system you run the installer [page 29] 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 48]
5 You restart the source system
6 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
7 You run the installer [page 29] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
9 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2860 CUSTOMER 2012-11-27
Keep Database
1 On the central instance host of the dual-stack system you run the installer [page 29] to export 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 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 48]
2 You restart the source system
3 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
4 On the database instance host of the dual-stack system you run the installer [page 29] 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 the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
6 You continue with Follow-Up Activities [page 33]
52 Running the Installer
This section describes how to run the installer The installer includes a GUI client and a GUI server
which both use Java
The procedure describes an installation where the installer GUI client and GUI server are running on
the same host In the following GUI client and GUI server are addressed as ldquonstaller GUIrdquo
Useful Information About the Installer
When you start the installer it automatically starts the installer GUI
The installer creates the installation directory sapinst_instdir which is located directly in the
ProgramFiles directory If the installer is not able to create sapinst_instdir there it tries to
create sapinst_instdir in the directory defined by the environment variable TEMP
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 2960
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
The installer creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt which is located in ProgramFiles
The installer extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is
located in TEMP TMP TMPDIR or SystemRoot These files are deleted after the installer 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 the installer cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default port 21212 is used for communication between the installer
GUI server and the installer GUI client If this port is already in use you see an error message
In this case or if you want the installer to use a specific port open a command prompt and change
to the required directory to which you unpacked the DSS645_IM_ltplatformgtSAR file
Execute sapinstexe with the following command line parameter
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
To see a list of all available installer properties open a command prompt and start the installer
with command line parameter -p
sapinstexe -p
If you need to run the installer in accessibility mode make sure that you have activated and adjusted
accessibility settings as described in Running the Installer in Accessibility Mode in the installation
documentation of your release
If required you can stop the installer by choosing SAPinst Cancel in the installer GUI menu
Prerequisites
Make sure that you use an account with the required user authorization to run the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
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
the installer
Before you start the installer read SAP Note 1697164 which contains important information how
to run the installer
5 Splitting
52 Running the Installer
3060 CUSTOMER 2012-11-27
Procedure
1 Log on to the installation host using an account with the required user authorization to run the
installer
CAUTION
Do not use an existing ltsapsidgtadm user
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 Preparing the DualndashStack Split Installation Media [page 25]
3 Start the installer by double-clicking sapinstexe from the directory to which you unpacked the
DSS645_IM_ltplatformgtSAR file
NOTE
If you need to perform the installation in accessibility mode open a command prompt change
to the ltpath to unpack directorygt directory and execute sapinstexe ndashaccessible
For more information see Running the Installer in Accessibility Mode in the installation
documentation of your release
The GUI starts automatically by displaying the Welcome screen
4 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
CAUTION
Sybase Split options ldquoMove Java Databaserdquo and ldquoKeep Databaserdquo are not available in the
Welcome screen but only the steps valid for split option ldquoMove Java Databaserdquo are listed
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
5 Choose Next
6 If the installer prompts you to log off from your system log off and on again
The installer restarts automatically
7 Follow the instructions in the installer input screens and enter the required parameters
NOTE
If the installer 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 the installer displays the Parameter Summary
screen This screen shows both the parameters that you entered and those that the installer set by
default If required you can revise the parameters before starting the split procedure
8 To start the dual-stack split choose Start
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 3160
The installer starts and displays the progress of the split procedure
When the split option has finished successfully the installer displays the message Execution of
ltOption_Namegt has completed
CAUTION
Multiple Oracle Homes only The installer uses default values for the Oracle Home and
Listener configuration Therefore if you use multiple Oracle Homes you must specify the
new Oracle home as well as the listener port number You can change these values on the
installer Summary screen during the database instance installation On the Summary screen check
both Oracle gt Database System and Oracle gt Listener Configuration and use the Revise button On the
upcoming screen change the Oracle Home and the Listener port number Make sure that
you use a free port number and do not use the numbers 1521 or 1527 as these might already
be in use by default
9 We recommend that you delete the directory userprofilesdtgui
10 IBM DB2 for Linux and UNIX and Windows If not already done install the DB2 license
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
11 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running the Installer
3260 CUSTOMER 2012-11-27
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
Not valid for Sybase 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
httpservicesapcominstallnw70
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3360
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 the installer [page 29] 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 40] 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3460 CUSTOMER 2012-11-27
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 central instance host of the source system you run the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
12 On the database host of the source system you run the installer [page 29] to remove the Java database
schema
13 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
14 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
15 If required and not already done so you configure the CTS Deploy Web Service [page 40] on the ABAP
system
16 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3560
5 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 release
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
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 the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
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 40] on the ABAP
system
15 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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3660 CUSTOMER 2012-11-27
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 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 You disable the Windows Server firewall on each host
For more information about disabling the Windows firewall see the relevant section in the
installation documentation of your release
2 You perform basic preparations on Windows
For more information see Performing Basic Windows Preparation Steps in the installation documentation
of your release
3 You check that you have the user authorization required for running the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
4 If applicable you set up virtual host names
For more information see Using Virtual Host Names in the installation documentation of your release
5 Only valid for HA (UNIX) |
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) |
6 If required you prepare the SAP system transport host for your SAP system
For more information see Preparing the SAP System Transport Host in the installation documentation
of your release
7 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
4 Preparation
41 Preparation Checklist
2012-11-27 CUSTOMER 2160
8 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 Dual Stack Split Installation Media [page 25]
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 |
9 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) |
10 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) |
11 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 22] of
the dual-stack system
12 You can continue with Splitting [page 27]
42 Performing a Full System Backup
NOTE
This section is not relevant if your database is Sybase
4 Preparation
42 Performing a Full System Backup
2260 CUSTOMER 2012-11-27
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
NOTE
If your system is a high-availability system make sure that you perform a backup of both cluster
nodes of the dual-stack system
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] for your release and database at
DatabaseSAP NetWeaver Release Path in Help Portal
SAP MaxDB SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for MaxDB
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 CapabilityGeneral 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
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for Oracle
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 CapabilityGeneral 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 Linux UNIX and Windows
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
4 Preparation
42 Performing a Full System Backup
2012-11-27 CUSTOMER 2360
DatabaseSAP NetWeaver Release Path in Help Portal
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 CapabilityGeneral 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 CapabilityGeneral 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 zOS
Microsoft SQL Server
SAP NetWeaver 70
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 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 CapabilityGeneral 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
2460 CUSTOMER 2012-11-27
43 Preparing the Dual Stack Split Installation Media
This section describes how to prepare the installation media that is required for the dual stack split
using the installer
Procedure
1 Download the installation media from the software distribution center on SAP Service Marketplace
using the following path
httpservicesapcomswdc Support Package and Patches A - Z Index S SL TOOLSET SL
TOOLSET 10 Entry by Component Dual-Stack Split
2 Create a download directory on the host on which you want to run the DualndashStack Split tool
3 Unpack the DualndashStack Split tool archive to a local directory using the following command
SAPCAR ndashxvf ltdownload directorygtltpathgtltArchivegtSAR -R ltunpack directorygt
4 Preparation
43 Preparing the Dual Stack Split Installation Media
2012-11-27 CUSTOMER 2560
This page is left blank for documents that are printed on both sides
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
NOTE
Sybase Split option ldquoKeep Databaserdquo is not supported You have to consider only the steps
described in section Move Java Database
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Oracle You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your release
2 Oracle If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your release
3 MS SQL Server You install the MS SQL Server database software
For more information see Installing the SQL Server Database Software in the installation documentation
of your release
4 You export the Java stack using the installer [page 29]
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 48]
5 You restart the source system
6 You run the installer [page 29] to install a Java only system using the export from the dual-stack
system
5 Splitting
51 Splitting Checklist
2012-11-27 CUSTOMER 2760
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 installer dialog
7 You continue with Follow-Up Activities [page 33]
Distributed System
1 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 release
2 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 release
3 On the database instance host of the dual-stack system you run the installer [page 29] to export the
Java database schema
4 On the central instance host of the dual-stack system you run the installer [page 29] 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 48]
5 You restart the source system
6 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
7 You run the installer [page 29] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
9 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2860 CUSTOMER 2012-11-27
Keep Database
1 On the central instance host of the dual-stack system you run the installer [page 29] to export 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 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 48]
2 You restart the source system
3 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
4 On the database instance host of the dual-stack system you run the installer [page 29] 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 the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
6 You continue with Follow-Up Activities [page 33]
52 Running the Installer
This section describes how to run the installer The installer includes a GUI client and a GUI server
which both use Java
The procedure describes an installation where the installer GUI client and GUI server are running on
the same host In the following GUI client and GUI server are addressed as ldquonstaller GUIrdquo
Useful Information About the Installer
When you start the installer it automatically starts the installer GUI
The installer creates the installation directory sapinst_instdir which is located directly in the
ProgramFiles directory If the installer is not able to create sapinst_instdir there it tries to
create sapinst_instdir in the directory defined by the environment variable TEMP
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 2960
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
The installer creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt which is located in ProgramFiles
The installer extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is
located in TEMP TMP TMPDIR or SystemRoot These files are deleted after the installer 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 the installer cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default port 21212 is used for communication between the installer
GUI server and the installer GUI client If this port is already in use you see an error message
In this case or if you want the installer to use a specific port open a command prompt and change
to the required directory to which you unpacked the DSS645_IM_ltplatformgtSAR file
Execute sapinstexe with the following command line parameter
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
To see a list of all available installer properties open a command prompt and start the installer
with command line parameter -p
sapinstexe -p
If you need to run the installer in accessibility mode make sure that you have activated and adjusted
accessibility settings as described in Running the Installer in Accessibility Mode in the installation
documentation of your release
If required you can stop the installer by choosing SAPinst Cancel in the installer GUI menu
Prerequisites
Make sure that you use an account with the required user authorization to run the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
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
the installer
Before you start the installer read SAP Note 1697164 which contains important information how
to run the installer
5 Splitting
52 Running the Installer
3060 CUSTOMER 2012-11-27
Procedure
1 Log on to the installation host using an account with the required user authorization to run the
installer
CAUTION
Do not use an existing ltsapsidgtadm user
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 Preparing the DualndashStack Split Installation Media [page 25]
3 Start the installer by double-clicking sapinstexe from the directory to which you unpacked the
DSS645_IM_ltplatformgtSAR file
NOTE
If you need to perform the installation in accessibility mode open a command prompt change
to the ltpath to unpack directorygt directory and execute sapinstexe ndashaccessible
For more information see Running the Installer in Accessibility Mode in the installation
documentation of your release
The GUI starts automatically by displaying the Welcome screen
4 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
CAUTION
Sybase Split options ldquoMove Java Databaserdquo and ldquoKeep Databaserdquo are not available in the
Welcome screen but only the steps valid for split option ldquoMove Java Databaserdquo are listed
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
5 Choose Next
6 If the installer prompts you to log off from your system log off and on again
The installer restarts automatically
7 Follow the instructions in the installer input screens and enter the required parameters
NOTE
If the installer 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 the installer displays the Parameter Summary
screen This screen shows both the parameters that you entered and those that the installer set by
default If required you can revise the parameters before starting the split procedure
8 To start the dual-stack split choose Start
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 3160
The installer starts and displays the progress of the split procedure
When the split option has finished successfully the installer displays the message Execution of
ltOption_Namegt has completed
CAUTION
Multiple Oracle Homes only The installer uses default values for the Oracle Home and
Listener configuration Therefore if you use multiple Oracle Homes you must specify the
new Oracle home as well as the listener port number You can change these values on the
installer Summary screen during the database instance installation On the Summary screen check
both Oracle gt Database System and Oracle gt Listener Configuration and use the Revise button On the
upcoming screen change the Oracle Home and the Listener port number Make sure that
you use a free port number and do not use the numbers 1521 or 1527 as these might already
be in use by default
9 We recommend that you delete the directory userprofilesdtgui
10 IBM DB2 for Linux and UNIX and Windows If not already done install the DB2 license
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
11 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running the Installer
3260 CUSTOMER 2012-11-27
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
Not valid for Sybase 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
httpservicesapcominstallnw70
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3360
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 the installer [page 29] 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 40] 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3460 CUSTOMER 2012-11-27
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 central instance host of the source system you run the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
12 On the database host of the source system you run the installer [page 29] to remove the Java database
schema
13 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
14 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
15 If required and not already done so you configure the CTS Deploy Web Service [page 40] on the ABAP
system
16 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3560
5 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 release
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
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 the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
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 40] on the ABAP
system
15 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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3660 CUSTOMER 2012-11-27
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
8 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 Dual Stack Split Installation Media [page 25]
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 |
9 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) |
10 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) |
11 If you decided to use the split option ldquoKeep Databaserdquo you perform a full system backup [page 22] of
the dual-stack system
12 You can continue with Splitting [page 27]
42 Performing a Full System Backup
NOTE
This section is not relevant if your database is Sybase
4 Preparation
42 Performing a Full System Backup
2260 CUSTOMER 2012-11-27
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
NOTE
If your system is a high-availability system make sure that you perform a backup of both cluster
nodes of the dual-stack system
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] for your release and database at
DatabaseSAP NetWeaver Release Path in Help Portal
SAP MaxDB SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for MaxDB
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 CapabilityGeneral 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
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for Oracle
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 CapabilityGeneral 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 Linux UNIX and Windows
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
4 Preparation
42 Performing a Full System Backup
2012-11-27 CUSTOMER 2360
DatabaseSAP NetWeaver Release Path in Help Portal
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 CapabilityGeneral 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 CapabilityGeneral 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 zOS
Microsoft SQL Server
SAP NetWeaver 70
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 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 CapabilityGeneral 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
2460 CUSTOMER 2012-11-27
43 Preparing the Dual Stack Split Installation Media
This section describes how to prepare the installation media that is required for the dual stack split
using the installer
Procedure
1 Download the installation media from the software distribution center on SAP Service Marketplace
using the following path
httpservicesapcomswdc Support Package and Patches A - Z Index S SL TOOLSET SL
TOOLSET 10 Entry by Component Dual-Stack Split
2 Create a download directory on the host on which you want to run the DualndashStack Split tool
3 Unpack the DualndashStack Split tool archive to a local directory using the following command
SAPCAR ndashxvf ltdownload directorygtltpathgtltArchivegtSAR -R ltunpack directorygt
4 Preparation
43 Preparing the Dual Stack Split Installation Media
2012-11-27 CUSTOMER 2560
This page is left blank for documents that are printed on both sides
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
NOTE
Sybase Split option ldquoKeep Databaserdquo is not supported You have to consider only the steps
described in section Move Java Database
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Oracle You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your release
2 Oracle If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your release
3 MS SQL Server You install the MS SQL Server database software
For more information see Installing the SQL Server Database Software in the installation documentation
of your release
4 You export the Java stack using the installer [page 29]
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 48]
5 You restart the source system
6 You run the installer [page 29] to install a Java only system using the export from the dual-stack
system
5 Splitting
51 Splitting Checklist
2012-11-27 CUSTOMER 2760
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 installer dialog
7 You continue with Follow-Up Activities [page 33]
Distributed System
1 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 release
2 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 release
3 On the database instance host of the dual-stack system you run the installer [page 29] to export the
Java database schema
4 On the central instance host of the dual-stack system you run the installer [page 29] 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 48]
5 You restart the source system
6 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
7 You run the installer [page 29] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
9 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2860 CUSTOMER 2012-11-27
Keep Database
1 On the central instance host of the dual-stack system you run the installer [page 29] to export 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 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 48]
2 You restart the source system
3 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
4 On the database instance host of the dual-stack system you run the installer [page 29] 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 the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
6 You continue with Follow-Up Activities [page 33]
52 Running the Installer
This section describes how to run the installer The installer includes a GUI client and a GUI server
which both use Java
The procedure describes an installation where the installer GUI client and GUI server are running on
the same host In the following GUI client and GUI server are addressed as ldquonstaller GUIrdquo
Useful Information About the Installer
When you start the installer it automatically starts the installer GUI
The installer creates the installation directory sapinst_instdir which is located directly in the
ProgramFiles directory If the installer is not able to create sapinst_instdir there it tries to
create sapinst_instdir in the directory defined by the environment variable TEMP
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 2960
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
The installer creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt which is located in ProgramFiles
The installer extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is
located in TEMP TMP TMPDIR or SystemRoot These files are deleted after the installer 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 the installer cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default port 21212 is used for communication between the installer
GUI server and the installer GUI client If this port is already in use you see an error message
In this case or if you want the installer to use a specific port open a command prompt and change
to the required directory to which you unpacked the DSS645_IM_ltplatformgtSAR file
Execute sapinstexe with the following command line parameter
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
To see a list of all available installer properties open a command prompt and start the installer
with command line parameter -p
sapinstexe -p
If you need to run the installer in accessibility mode make sure that you have activated and adjusted
accessibility settings as described in Running the Installer in Accessibility Mode in the installation
documentation of your release
If required you can stop the installer by choosing SAPinst Cancel in the installer GUI menu
Prerequisites
Make sure that you use an account with the required user authorization to run the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
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
the installer
Before you start the installer read SAP Note 1697164 which contains important information how
to run the installer
5 Splitting
52 Running the Installer
3060 CUSTOMER 2012-11-27
Procedure
1 Log on to the installation host using an account with the required user authorization to run the
installer
CAUTION
Do not use an existing ltsapsidgtadm user
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 Preparing the DualndashStack Split Installation Media [page 25]
3 Start the installer by double-clicking sapinstexe from the directory to which you unpacked the
DSS645_IM_ltplatformgtSAR file
NOTE
If you need to perform the installation in accessibility mode open a command prompt change
to the ltpath to unpack directorygt directory and execute sapinstexe ndashaccessible
For more information see Running the Installer in Accessibility Mode in the installation
documentation of your release
The GUI starts automatically by displaying the Welcome screen
4 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
CAUTION
Sybase Split options ldquoMove Java Databaserdquo and ldquoKeep Databaserdquo are not available in the
Welcome screen but only the steps valid for split option ldquoMove Java Databaserdquo are listed
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
5 Choose Next
6 If the installer prompts you to log off from your system log off and on again
The installer restarts automatically
7 Follow the instructions in the installer input screens and enter the required parameters
NOTE
If the installer 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 the installer displays the Parameter Summary
screen This screen shows both the parameters that you entered and those that the installer set by
default If required you can revise the parameters before starting the split procedure
8 To start the dual-stack split choose Start
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 3160
The installer starts and displays the progress of the split procedure
When the split option has finished successfully the installer displays the message Execution of
ltOption_Namegt has completed
CAUTION
Multiple Oracle Homes only The installer uses default values for the Oracle Home and
Listener configuration Therefore if you use multiple Oracle Homes you must specify the
new Oracle home as well as the listener port number You can change these values on the
installer Summary screen during the database instance installation On the Summary screen check
both Oracle gt Database System and Oracle gt Listener Configuration and use the Revise button On the
upcoming screen change the Oracle Home and the Listener port number Make sure that
you use a free port number and do not use the numbers 1521 or 1527 as these might already
be in use by default
9 We recommend that you delete the directory userprofilesdtgui
10 IBM DB2 for Linux and UNIX and Windows If not already done install the DB2 license
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
11 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running the Installer
3260 CUSTOMER 2012-11-27
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
Not valid for Sybase 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
httpservicesapcominstallnw70
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3360
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 the installer [page 29] 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 40] 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3460 CUSTOMER 2012-11-27
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 central instance host of the source system you run the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
12 On the database host of the source system you run the installer [page 29] to remove the Java database
schema
13 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
14 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
15 If required and not already done so you configure the CTS Deploy Web Service [page 40] on the ABAP
system
16 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3560
5 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 release
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
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 the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
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 40] on the ABAP
system
15 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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3660 CUSTOMER 2012-11-27
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
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
NOTE
If your system is a high-availability system make sure that you perform a backup of both cluster
nodes of the dual-stack system
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] for your release and database at
DatabaseSAP NetWeaver Release Path in Help Portal
SAP MaxDB SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for MaxDB
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 CapabilityGeneral 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
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for Oracle
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 CapabilityGeneral 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 Linux UNIX and Windows
SAP NetWeaver 70
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Database Administration Database Administration for IBM DB2 for Linux UNIX and Windows
4 Preparation
42 Performing a Full System Backup
2012-11-27 CUSTOMER 2360
DatabaseSAP NetWeaver Release Path in Help Portal
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 CapabilityGeneral 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 CapabilityGeneral 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 zOS
Microsoft SQL Server
SAP NetWeaver 70
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 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 CapabilityGeneral 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
2460 CUSTOMER 2012-11-27
43 Preparing the Dual Stack Split Installation Media
This section describes how to prepare the installation media that is required for the dual stack split
using the installer
Procedure
1 Download the installation media from the software distribution center on SAP Service Marketplace
using the following path
httpservicesapcomswdc Support Package and Patches A - Z Index S SL TOOLSET SL
TOOLSET 10 Entry by Component Dual-Stack Split
2 Create a download directory on the host on which you want to run the DualndashStack Split tool
3 Unpack the DualndashStack Split tool archive to a local directory using the following command
SAPCAR ndashxvf ltdownload directorygtltpathgtltArchivegtSAR -R ltunpack directorygt
4 Preparation
43 Preparing the Dual Stack Split Installation Media
2012-11-27 CUSTOMER 2560
This page is left blank for documents that are printed on both sides
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
NOTE
Sybase Split option ldquoKeep Databaserdquo is not supported You have to consider only the steps
described in section Move Java Database
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Oracle You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your release
2 Oracle If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your release
3 MS SQL Server You install the MS SQL Server database software
For more information see Installing the SQL Server Database Software in the installation documentation
of your release
4 You export the Java stack using the installer [page 29]
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 48]
5 You restart the source system
6 You run the installer [page 29] to install a Java only system using the export from the dual-stack
system
5 Splitting
51 Splitting Checklist
2012-11-27 CUSTOMER 2760
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 installer dialog
7 You continue with Follow-Up Activities [page 33]
Distributed System
1 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 release
2 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 release
3 On the database instance host of the dual-stack system you run the installer [page 29] to export the
Java database schema
4 On the central instance host of the dual-stack system you run the installer [page 29] 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 48]
5 You restart the source system
6 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
7 You run the installer [page 29] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
9 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2860 CUSTOMER 2012-11-27
Keep Database
1 On the central instance host of the dual-stack system you run the installer [page 29] to export 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 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 48]
2 You restart the source system
3 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
4 On the database instance host of the dual-stack system you run the installer [page 29] 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 the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
6 You continue with Follow-Up Activities [page 33]
52 Running the Installer
This section describes how to run the installer The installer includes a GUI client and a GUI server
which both use Java
The procedure describes an installation where the installer GUI client and GUI server are running on
the same host In the following GUI client and GUI server are addressed as ldquonstaller GUIrdquo
Useful Information About the Installer
When you start the installer it automatically starts the installer GUI
The installer creates the installation directory sapinst_instdir which is located directly in the
ProgramFiles directory If the installer is not able to create sapinst_instdir there it tries to
create sapinst_instdir in the directory defined by the environment variable TEMP
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 2960
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
The installer creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt which is located in ProgramFiles
The installer extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is
located in TEMP TMP TMPDIR or SystemRoot These files are deleted after the installer 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 the installer cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default port 21212 is used for communication between the installer
GUI server and the installer GUI client If this port is already in use you see an error message
In this case or if you want the installer to use a specific port open a command prompt and change
to the required directory to which you unpacked the DSS645_IM_ltplatformgtSAR file
Execute sapinstexe with the following command line parameter
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
To see a list of all available installer properties open a command prompt and start the installer
with command line parameter -p
sapinstexe -p
If you need to run the installer in accessibility mode make sure that you have activated and adjusted
accessibility settings as described in Running the Installer in Accessibility Mode in the installation
documentation of your release
If required you can stop the installer by choosing SAPinst Cancel in the installer GUI menu
Prerequisites
Make sure that you use an account with the required user authorization to run the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
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
the installer
Before you start the installer read SAP Note 1697164 which contains important information how
to run the installer
5 Splitting
52 Running the Installer
3060 CUSTOMER 2012-11-27
Procedure
1 Log on to the installation host using an account with the required user authorization to run the
installer
CAUTION
Do not use an existing ltsapsidgtadm user
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 Preparing the DualndashStack Split Installation Media [page 25]
3 Start the installer by double-clicking sapinstexe from the directory to which you unpacked the
DSS645_IM_ltplatformgtSAR file
NOTE
If you need to perform the installation in accessibility mode open a command prompt change
to the ltpath to unpack directorygt directory and execute sapinstexe ndashaccessible
For more information see Running the Installer in Accessibility Mode in the installation
documentation of your release
The GUI starts automatically by displaying the Welcome screen
4 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
CAUTION
Sybase Split options ldquoMove Java Databaserdquo and ldquoKeep Databaserdquo are not available in the
Welcome screen but only the steps valid for split option ldquoMove Java Databaserdquo are listed
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
5 Choose Next
6 If the installer prompts you to log off from your system log off and on again
The installer restarts automatically
7 Follow the instructions in the installer input screens and enter the required parameters
NOTE
If the installer 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 the installer displays the Parameter Summary
screen This screen shows both the parameters that you entered and those that the installer set by
default If required you can revise the parameters before starting the split procedure
8 To start the dual-stack split choose Start
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 3160
The installer starts and displays the progress of the split procedure
When the split option has finished successfully the installer displays the message Execution of
ltOption_Namegt has completed
CAUTION
Multiple Oracle Homes only The installer uses default values for the Oracle Home and
Listener configuration Therefore if you use multiple Oracle Homes you must specify the
new Oracle home as well as the listener port number You can change these values on the
installer Summary screen during the database instance installation On the Summary screen check
both Oracle gt Database System and Oracle gt Listener Configuration and use the Revise button On the
upcoming screen change the Oracle Home and the Listener port number Make sure that
you use a free port number and do not use the numbers 1521 or 1527 as these might already
be in use by default
9 We recommend that you delete the directory userprofilesdtgui
10 IBM DB2 for Linux and UNIX and Windows If not already done install the DB2 license
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
11 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running the Installer
3260 CUSTOMER 2012-11-27
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
Not valid for Sybase 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
httpservicesapcominstallnw70
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3360
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 the installer [page 29] 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 40] 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3460 CUSTOMER 2012-11-27
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 central instance host of the source system you run the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
12 On the database host of the source system you run the installer [page 29] to remove the Java database
schema
13 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
14 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
15 If required and not already done so you configure the CTS Deploy Web Service [page 40] on the ABAP
system
16 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3560
5 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 release
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
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 the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
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 40] on the ABAP
system
15 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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3660 CUSTOMER 2012-11-27
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
DatabaseSAP NetWeaver Release Path in Help Portal
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 CapabilityGeneral 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 CapabilityGeneral 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 zOS
Microsoft SQL Server
SAP NetWeaver 70
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 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 CapabilityGeneral 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
2460 CUSTOMER 2012-11-27
43 Preparing the Dual Stack Split Installation Media
This section describes how to prepare the installation media that is required for the dual stack split
using the installer
Procedure
1 Download the installation media from the software distribution center on SAP Service Marketplace
using the following path
httpservicesapcomswdc Support Package and Patches A - Z Index S SL TOOLSET SL
TOOLSET 10 Entry by Component Dual-Stack Split
2 Create a download directory on the host on which you want to run the DualndashStack Split tool
3 Unpack the DualndashStack Split tool archive to a local directory using the following command
SAPCAR ndashxvf ltdownload directorygtltpathgtltArchivegtSAR -R ltunpack directorygt
4 Preparation
43 Preparing the Dual Stack Split Installation Media
2012-11-27 CUSTOMER 2560
This page is left blank for documents that are printed on both sides
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
NOTE
Sybase Split option ldquoKeep Databaserdquo is not supported You have to consider only the steps
described in section Move Java Database
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Oracle You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your release
2 Oracle If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your release
3 MS SQL Server You install the MS SQL Server database software
For more information see Installing the SQL Server Database Software in the installation documentation
of your release
4 You export the Java stack using the installer [page 29]
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 48]
5 You restart the source system
6 You run the installer [page 29] to install a Java only system using the export from the dual-stack
system
5 Splitting
51 Splitting Checklist
2012-11-27 CUSTOMER 2760
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 installer dialog
7 You continue with Follow-Up Activities [page 33]
Distributed System
1 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 release
2 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 release
3 On the database instance host of the dual-stack system you run the installer [page 29] to export the
Java database schema
4 On the central instance host of the dual-stack system you run the installer [page 29] 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 48]
5 You restart the source system
6 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
7 You run the installer [page 29] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
9 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2860 CUSTOMER 2012-11-27
Keep Database
1 On the central instance host of the dual-stack system you run the installer [page 29] to export 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 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 48]
2 You restart the source system
3 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
4 On the database instance host of the dual-stack system you run the installer [page 29] 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 the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
6 You continue with Follow-Up Activities [page 33]
52 Running the Installer
This section describes how to run the installer The installer includes a GUI client and a GUI server
which both use Java
The procedure describes an installation where the installer GUI client and GUI server are running on
the same host In the following GUI client and GUI server are addressed as ldquonstaller GUIrdquo
Useful Information About the Installer
When you start the installer it automatically starts the installer GUI
The installer creates the installation directory sapinst_instdir which is located directly in the
ProgramFiles directory If the installer is not able to create sapinst_instdir there it tries to
create sapinst_instdir in the directory defined by the environment variable TEMP
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 2960
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
The installer creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt which is located in ProgramFiles
The installer extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is
located in TEMP TMP TMPDIR or SystemRoot These files are deleted after the installer 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 the installer cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default port 21212 is used for communication between the installer
GUI server and the installer GUI client If this port is already in use you see an error message
In this case or if you want the installer to use a specific port open a command prompt and change
to the required directory to which you unpacked the DSS645_IM_ltplatformgtSAR file
Execute sapinstexe with the following command line parameter
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
To see a list of all available installer properties open a command prompt and start the installer
with command line parameter -p
sapinstexe -p
If you need to run the installer in accessibility mode make sure that you have activated and adjusted
accessibility settings as described in Running the Installer in Accessibility Mode in the installation
documentation of your release
If required you can stop the installer by choosing SAPinst Cancel in the installer GUI menu
Prerequisites
Make sure that you use an account with the required user authorization to run the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
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
the installer
Before you start the installer read SAP Note 1697164 which contains important information how
to run the installer
5 Splitting
52 Running the Installer
3060 CUSTOMER 2012-11-27
Procedure
1 Log on to the installation host using an account with the required user authorization to run the
installer
CAUTION
Do not use an existing ltsapsidgtadm user
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 Preparing the DualndashStack Split Installation Media [page 25]
3 Start the installer by double-clicking sapinstexe from the directory to which you unpacked the
DSS645_IM_ltplatformgtSAR file
NOTE
If you need to perform the installation in accessibility mode open a command prompt change
to the ltpath to unpack directorygt directory and execute sapinstexe ndashaccessible
For more information see Running the Installer in Accessibility Mode in the installation
documentation of your release
The GUI starts automatically by displaying the Welcome screen
4 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
CAUTION
Sybase Split options ldquoMove Java Databaserdquo and ldquoKeep Databaserdquo are not available in the
Welcome screen but only the steps valid for split option ldquoMove Java Databaserdquo are listed
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
5 Choose Next
6 If the installer prompts you to log off from your system log off and on again
The installer restarts automatically
7 Follow the instructions in the installer input screens and enter the required parameters
NOTE
If the installer 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 the installer displays the Parameter Summary
screen This screen shows both the parameters that you entered and those that the installer set by
default If required you can revise the parameters before starting the split procedure
8 To start the dual-stack split choose Start
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 3160
The installer starts and displays the progress of the split procedure
When the split option has finished successfully the installer displays the message Execution of
ltOption_Namegt has completed
CAUTION
Multiple Oracle Homes only The installer uses default values for the Oracle Home and
Listener configuration Therefore if you use multiple Oracle Homes you must specify the
new Oracle home as well as the listener port number You can change these values on the
installer Summary screen during the database instance installation On the Summary screen check
both Oracle gt Database System and Oracle gt Listener Configuration and use the Revise button On the
upcoming screen change the Oracle Home and the Listener port number Make sure that
you use a free port number and do not use the numbers 1521 or 1527 as these might already
be in use by default
9 We recommend that you delete the directory userprofilesdtgui
10 IBM DB2 for Linux and UNIX and Windows If not already done install the DB2 license
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
11 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running the Installer
3260 CUSTOMER 2012-11-27
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
Not valid for Sybase 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
httpservicesapcominstallnw70
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3360
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 the installer [page 29] 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 40] 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3460 CUSTOMER 2012-11-27
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 central instance host of the source system you run the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
12 On the database host of the source system you run the installer [page 29] to remove the Java database
schema
13 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
14 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
15 If required and not already done so you configure the CTS Deploy Web Service [page 40] on the ABAP
system
16 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3560
5 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 release
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
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 the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
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 40] on the ABAP
system
15 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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3660 CUSTOMER 2012-11-27
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
43 Preparing the Dual Stack Split Installation Media
This section describes how to prepare the installation media that is required for the dual stack split
using the installer
Procedure
1 Download the installation media from the software distribution center on SAP Service Marketplace
using the following path
httpservicesapcomswdc Support Package and Patches A - Z Index S SL TOOLSET SL
TOOLSET 10 Entry by Component Dual-Stack Split
2 Create a download directory on the host on which you want to run the DualndashStack Split tool
3 Unpack the DualndashStack Split tool archive to a local directory using the following command
SAPCAR ndashxvf ltdownload directorygtltpathgtltArchivegtSAR -R ltunpack directorygt
4 Preparation
43 Preparing the Dual Stack Split Installation Media
2012-11-27 CUSTOMER 2560
This page is left blank for documents that are printed on both sides
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
NOTE
Sybase Split option ldquoKeep Databaserdquo is not supported You have to consider only the steps
described in section Move Java Database
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Oracle You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your release
2 Oracle If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your release
3 MS SQL Server You install the MS SQL Server database software
For more information see Installing the SQL Server Database Software in the installation documentation
of your release
4 You export the Java stack using the installer [page 29]
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 48]
5 You restart the source system
6 You run the installer [page 29] to install a Java only system using the export from the dual-stack
system
5 Splitting
51 Splitting Checklist
2012-11-27 CUSTOMER 2760
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 installer dialog
7 You continue with Follow-Up Activities [page 33]
Distributed System
1 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 release
2 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 release
3 On the database instance host of the dual-stack system you run the installer [page 29] to export the
Java database schema
4 On the central instance host of the dual-stack system you run the installer [page 29] 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 48]
5 You restart the source system
6 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
7 You run the installer [page 29] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
9 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2860 CUSTOMER 2012-11-27
Keep Database
1 On the central instance host of the dual-stack system you run the installer [page 29] to export 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 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 48]
2 You restart the source system
3 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
4 On the database instance host of the dual-stack system you run the installer [page 29] 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 the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
6 You continue with Follow-Up Activities [page 33]
52 Running the Installer
This section describes how to run the installer The installer includes a GUI client and a GUI server
which both use Java
The procedure describes an installation where the installer GUI client and GUI server are running on
the same host In the following GUI client and GUI server are addressed as ldquonstaller GUIrdquo
Useful Information About the Installer
When you start the installer it automatically starts the installer GUI
The installer creates the installation directory sapinst_instdir which is located directly in the
ProgramFiles directory If the installer is not able to create sapinst_instdir there it tries to
create sapinst_instdir in the directory defined by the environment variable TEMP
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 2960
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
The installer creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt which is located in ProgramFiles
The installer extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is
located in TEMP TMP TMPDIR or SystemRoot These files are deleted after the installer 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 the installer cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default port 21212 is used for communication between the installer
GUI server and the installer GUI client If this port is already in use you see an error message
In this case or if you want the installer to use a specific port open a command prompt and change
to the required directory to which you unpacked the DSS645_IM_ltplatformgtSAR file
Execute sapinstexe with the following command line parameter
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
To see a list of all available installer properties open a command prompt and start the installer
with command line parameter -p
sapinstexe -p
If you need to run the installer in accessibility mode make sure that you have activated and adjusted
accessibility settings as described in Running the Installer in Accessibility Mode in the installation
documentation of your release
If required you can stop the installer by choosing SAPinst Cancel in the installer GUI menu
Prerequisites
Make sure that you use an account with the required user authorization to run the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
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
the installer
Before you start the installer read SAP Note 1697164 which contains important information how
to run the installer
5 Splitting
52 Running the Installer
3060 CUSTOMER 2012-11-27
Procedure
1 Log on to the installation host using an account with the required user authorization to run the
installer
CAUTION
Do not use an existing ltsapsidgtadm user
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 Preparing the DualndashStack Split Installation Media [page 25]
3 Start the installer by double-clicking sapinstexe from the directory to which you unpacked the
DSS645_IM_ltplatformgtSAR file
NOTE
If you need to perform the installation in accessibility mode open a command prompt change
to the ltpath to unpack directorygt directory and execute sapinstexe ndashaccessible
For more information see Running the Installer in Accessibility Mode in the installation
documentation of your release
The GUI starts automatically by displaying the Welcome screen
4 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
CAUTION
Sybase Split options ldquoMove Java Databaserdquo and ldquoKeep Databaserdquo are not available in the
Welcome screen but only the steps valid for split option ldquoMove Java Databaserdquo are listed
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
5 Choose Next
6 If the installer prompts you to log off from your system log off and on again
The installer restarts automatically
7 Follow the instructions in the installer input screens and enter the required parameters
NOTE
If the installer 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 the installer displays the Parameter Summary
screen This screen shows both the parameters that you entered and those that the installer set by
default If required you can revise the parameters before starting the split procedure
8 To start the dual-stack split choose Start
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 3160
The installer starts and displays the progress of the split procedure
When the split option has finished successfully the installer displays the message Execution of
ltOption_Namegt has completed
CAUTION
Multiple Oracle Homes only The installer uses default values for the Oracle Home and
Listener configuration Therefore if you use multiple Oracle Homes you must specify the
new Oracle home as well as the listener port number You can change these values on the
installer Summary screen during the database instance installation On the Summary screen check
both Oracle gt Database System and Oracle gt Listener Configuration and use the Revise button On the
upcoming screen change the Oracle Home and the Listener port number Make sure that
you use a free port number and do not use the numbers 1521 or 1527 as these might already
be in use by default
9 We recommend that you delete the directory userprofilesdtgui
10 IBM DB2 for Linux and UNIX and Windows If not already done install the DB2 license
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
11 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running the Installer
3260 CUSTOMER 2012-11-27
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
Not valid for Sybase 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
httpservicesapcominstallnw70
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3360
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 the installer [page 29] 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 40] 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3460 CUSTOMER 2012-11-27
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 central instance host of the source system you run the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
12 On the database host of the source system you run the installer [page 29] to remove the Java database
schema
13 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
14 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
15 If required and not already done so you configure the CTS Deploy Web Service [page 40] on the ABAP
system
16 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3560
5 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 release
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
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 the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
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 40] on the ABAP
system
15 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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3660 CUSTOMER 2012-11-27
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 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
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
NOTE
Sybase Split option ldquoKeep Databaserdquo is not supported You have to consider only the steps
described in section Move Java Database
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Oracle You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your release
2 Oracle If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your release
3 MS SQL Server You install the MS SQL Server database software
For more information see Installing the SQL Server Database Software in the installation documentation
of your release
4 You export the Java stack using the installer [page 29]
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 48]
5 You restart the source system
6 You run the installer [page 29] to install a Java only system using the export from the dual-stack
system
5 Splitting
51 Splitting Checklist
2012-11-27 CUSTOMER 2760
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 installer dialog
7 You continue with Follow-Up Activities [page 33]
Distributed System
1 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 release
2 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 release
3 On the database instance host of the dual-stack system you run the installer [page 29] to export the
Java database schema
4 On the central instance host of the dual-stack system you run the installer [page 29] 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 48]
5 You restart the source system
6 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
7 You run the installer [page 29] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
9 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2860 CUSTOMER 2012-11-27
Keep Database
1 On the central instance host of the dual-stack system you run the installer [page 29] to export 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 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 48]
2 You restart the source system
3 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
4 On the database instance host of the dual-stack system you run the installer [page 29] 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 the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
6 You continue with Follow-Up Activities [page 33]
52 Running the Installer
This section describes how to run the installer The installer includes a GUI client and a GUI server
which both use Java
The procedure describes an installation where the installer GUI client and GUI server are running on
the same host In the following GUI client and GUI server are addressed as ldquonstaller GUIrdquo
Useful Information About the Installer
When you start the installer it automatically starts the installer GUI
The installer creates the installation directory sapinst_instdir which is located directly in the
ProgramFiles directory If the installer is not able to create sapinst_instdir there it tries to
create sapinst_instdir in the directory defined by the environment variable TEMP
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 2960
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
The installer creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt which is located in ProgramFiles
The installer extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is
located in TEMP TMP TMPDIR or SystemRoot These files are deleted after the installer 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 the installer cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default port 21212 is used for communication between the installer
GUI server and the installer GUI client If this port is already in use you see an error message
In this case or if you want the installer to use a specific port open a command prompt and change
to the required directory to which you unpacked the DSS645_IM_ltplatformgtSAR file
Execute sapinstexe with the following command line parameter
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
To see a list of all available installer properties open a command prompt and start the installer
with command line parameter -p
sapinstexe -p
If you need to run the installer in accessibility mode make sure that you have activated and adjusted
accessibility settings as described in Running the Installer in Accessibility Mode in the installation
documentation of your release
If required you can stop the installer by choosing SAPinst Cancel in the installer GUI menu
Prerequisites
Make sure that you use an account with the required user authorization to run the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
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
the installer
Before you start the installer read SAP Note 1697164 which contains important information how
to run the installer
5 Splitting
52 Running the Installer
3060 CUSTOMER 2012-11-27
Procedure
1 Log on to the installation host using an account with the required user authorization to run the
installer
CAUTION
Do not use an existing ltsapsidgtadm user
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 Preparing the DualndashStack Split Installation Media [page 25]
3 Start the installer by double-clicking sapinstexe from the directory to which you unpacked the
DSS645_IM_ltplatformgtSAR file
NOTE
If you need to perform the installation in accessibility mode open a command prompt change
to the ltpath to unpack directorygt directory and execute sapinstexe ndashaccessible
For more information see Running the Installer in Accessibility Mode in the installation
documentation of your release
The GUI starts automatically by displaying the Welcome screen
4 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
CAUTION
Sybase Split options ldquoMove Java Databaserdquo and ldquoKeep Databaserdquo are not available in the
Welcome screen but only the steps valid for split option ldquoMove Java Databaserdquo are listed
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
5 Choose Next
6 If the installer prompts you to log off from your system log off and on again
The installer restarts automatically
7 Follow the instructions in the installer input screens and enter the required parameters
NOTE
If the installer 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 the installer displays the Parameter Summary
screen This screen shows both the parameters that you entered and those that the installer set by
default If required you can revise the parameters before starting the split procedure
8 To start the dual-stack split choose Start
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 3160
The installer starts and displays the progress of the split procedure
When the split option has finished successfully the installer displays the message Execution of
ltOption_Namegt has completed
CAUTION
Multiple Oracle Homes only The installer uses default values for the Oracle Home and
Listener configuration Therefore if you use multiple Oracle Homes you must specify the
new Oracle home as well as the listener port number You can change these values on the
installer Summary screen during the database instance installation On the Summary screen check
both Oracle gt Database System and Oracle gt Listener Configuration and use the Revise button On the
upcoming screen change the Oracle Home and the Listener port number Make sure that
you use a free port number and do not use the numbers 1521 or 1527 as these might already
be in use by default
9 We recommend that you delete the directory userprofilesdtgui
10 IBM DB2 for Linux and UNIX and Windows If not already done install the DB2 license
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
11 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running the Installer
3260 CUSTOMER 2012-11-27
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
Not valid for Sybase 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
httpservicesapcominstallnw70
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3360
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 the installer [page 29] 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 40] 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3460 CUSTOMER 2012-11-27
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 central instance host of the source system you run the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
12 On the database host of the source system you run the installer [page 29] to remove the Java database
schema
13 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
14 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
15 If required and not already done so you configure the CTS Deploy Web Service [page 40] on the ABAP
system
16 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3560
5 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 release
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
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 the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
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 40] on the ABAP
system
15 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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3660 CUSTOMER 2012-11-27
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 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
NOTE
Sybase Split option ldquoKeep Databaserdquo is not supported You have to consider only the steps
described in section Move Java Database
Detailed information about the steps is available in the relevant section
Move Java Database
Central and High-Availability Systems
1 Oracle You install the Oracle database software
For more information see Installing the Oracle Database Software in the installation documentation of
your release
2 Oracle If required you set up multiple Oracle Homes
For more information see Setting Up Multiple Homes in the installation documentation of your release
3 MS SQL Server You install the MS SQL Server database software
For more information see Installing the SQL Server Database Software in the installation documentation
of your release
4 You export the Java stack using the installer [page 29]
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 48]
5 You restart the source system
6 You run the installer [page 29] to install a Java only system using the export from the dual-stack
system
5 Splitting
51 Splitting Checklist
2012-11-27 CUSTOMER 2760
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 installer dialog
7 You continue with Follow-Up Activities [page 33]
Distributed System
1 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 release
2 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 release
3 On the database instance host of the dual-stack system you run the installer [page 29] to export the
Java database schema
4 On the central instance host of the dual-stack system you run the installer [page 29] 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 48]
5 You restart the source system
6 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
7 You run the installer [page 29] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
9 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2860 CUSTOMER 2012-11-27
Keep Database
1 On the central instance host of the dual-stack system you run the installer [page 29] to export 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 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 48]
2 You restart the source system
3 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
4 On the database instance host of the dual-stack system you run the installer [page 29] 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 the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
6 You continue with Follow-Up Activities [page 33]
52 Running the Installer
This section describes how to run the installer The installer includes a GUI client and a GUI server
which both use Java
The procedure describes an installation where the installer GUI client and GUI server are running on
the same host In the following GUI client and GUI server are addressed as ldquonstaller GUIrdquo
Useful Information About the Installer
When you start the installer it automatically starts the installer GUI
The installer creates the installation directory sapinst_instdir which is located directly in the
ProgramFiles directory If the installer is not able to create sapinst_instdir there it tries to
create sapinst_instdir in the directory defined by the environment variable TEMP
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 2960
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
The installer creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt which is located in ProgramFiles
The installer extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is
located in TEMP TMP TMPDIR or SystemRoot These files are deleted after the installer 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 the installer cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default port 21212 is used for communication between the installer
GUI server and the installer GUI client If this port is already in use you see an error message
In this case or if you want the installer to use a specific port open a command prompt and change
to the required directory to which you unpacked the DSS645_IM_ltplatformgtSAR file
Execute sapinstexe with the following command line parameter
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
To see a list of all available installer properties open a command prompt and start the installer
with command line parameter -p
sapinstexe -p
If you need to run the installer in accessibility mode make sure that you have activated and adjusted
accessibility settings as described in Running the Installer in Accessibility Mode in the installation
documentation of your release
If required you can stop the installer by choosing SAPinst Cancel in the installer GUI menu
Prerequisites
Make sure that you use an account with the required user authorization to run the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
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
the installer
Before you start the installer read SAP Note 1697164 which contains important information how
to run the installer
5 Splitting
52 Running the Installer
3060 CUSTOMER 2012-11-27
Procedure
1 Log on to the installation host using an account with the required user authorization to run the
installer
CAUTION
Do not use an existing ltsapsidgtadm user
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 Preparing the DualndashStack Split Installation Media [page 25]
3 Start the installer by double-clicking sapinstexe from the directory to which you unpacked the
DSS645_IM_ltplatformgtSAR file
NOTE
If you need to perform the installation in accessibility mode open a command prompt change
to the ltpath to unpack directorygt directory and execute sapinstexe ndashaccessible
For more information see Running the Installer in Accessibility Mode in the installation
documentation of your release
The GUI starts automatically by displaying the Welcome screen
4 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
CAUTION
Sybase Split options ldquoMove Java Databaserdquo and ldquoKeep Databaserdquo are not available in the
Welcome screen but only the steps valid for split option ldquoMove Java Databaserdquo are listed
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
5 Choose Next
6 If the installer prompts you to log off from your system log off and on again
The installer restarts automatically
7 Follow the instructions in the installer input screens and enter the required parameters
NOTE
If the installer 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 the installer displays the Parameter Summary
screen This screen shows both the parameters that you entered and those that the installer set by
default If required you can revise the parameters before starting the split procedure
8 To start the dual-stack split choose Start
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 3160
The installer starts and displays the progress of the split procedure
When the split option has finished successfully the installer displays the message Execution of
ltOption_Namegt has completed
CAUTION
Multiple Oracle Homes only The installer uses default values for the Oracle Home and
Listener configuration Therefore if you use multiple Oracle Homes you must specify the
new Oracle home as well as the listener port number You can change these values on the
installer Summary screen during the database instance installation On the Summary screen check
both Oracle gt Database System and Oracle gt Listener Configuration and use the Revise button On the
upcoming screen change the Oracle Home and the Listener port number Make sure that
you use a free port number and do not use the numbers 1521 or 1527 as these might already
be in use by default
9 We recommend that you delete the directory userprofilesdtgui
10 IBM DB2 for Linux and UNIX and Windows If not already done install the DB2 license
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
11 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running the Installer
3260 CUSTOMER 2012-11-27
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
Not valid for Sybase 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
httpservicesapcominstallnw70
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3360
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 the installer [page 29] 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 40] 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3460 CUSTOMER 2012-11-27
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 central instance host of the source system you run the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
12 On the database host of the source system you run the installer [page 29] to remove the Java database
schema
13 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
14 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
15 If required and not already done so you configure the CTS Deploy Web Service [page 40] on the ABAP
system
16 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3560
5 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 release
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
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 the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
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 40] on the ABAP
system
15 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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3660 CUSTOMER 2012-11-27
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
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 installer dialog
7 You continue with Follow-Up Activities [page 33]
Distributed System
1 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 release
2 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 release
3 On the database instance host of the dual-stack system you run the installer [page 29] to export the
Java database schema
4 On the central instance host of the dual-stack system you run the installer [page 29] 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 48]
5 You restart the source system
6 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
7 You run the installer [page 29] to install a database instance for the Java target system using the export
from the dual-stack system
8 You run the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
9 You continue with Follow-Up Activities [page 33]
5 Splitting
51 Splitting Checklist
2860 CUSTOMER 2012-11-27
Keep Database
1 On the central instance host of the dual-stack system you run the installer [page 29] to export 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 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 48]
2 You restart the source system
3 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
4 On the database instance host of the dual-stack system you run the installer [page 29] 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 the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
6 You continue with Follow-Up Activities [page 33]
52 Running the Installer
This section describes how to run the installer The installer includes a GUI client and a GUI server
which both use Java
The procedure describes an installation where the installer GUI client and GUI server are running on
the same host In the following GUI client and GUI server are addressed as ldquonstaller GUIrdquo
Useful Information About the Installer
When you start the installer it automatically starts the installer GUI
The installer creates the installation directory sapinst_instdir which is located directly in the
ProgramFiles directory If the installer is not able to create sapinst_instdir there it tries to
create sapinst_instdir in the directory defined by the environment variable TEMP
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 2960
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
The installer creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt which is located in ProgramFiles
The installer extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is
located in TEMP TMP TMPDIR or SystemRoot These files are deleted after the installer 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 the installer cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default port 21212 is used for communication between the installer
GUI server and the installer GUI client If this port is already in use you see an error message
In this case or if you want the installer to use a specific port open a command prompt and change
to the required directory to which you unpacked the DSS645_IM_ltplatformgtSAR file
Execute sapinstexe with the following command line parameter
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
To see a list of all available installer properties open a command prompt and start the installer
with command line parameter -p
sapinstexe -p
If you need to run the installer in accessibility mode make sure that you have activated and adjusted
accessibility settings as described in Running the Installer in Accessibility Mode in the installation
documentation of your release
If required you can stop the installer by choosing SAPinst Cancel in the installer GUI menu
Prerequisites
Make sure that you use an account with the required user authorization to run the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
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
the installer
Before you start the installer read SAP Note 1697164 which contains important information how
to run the installer
5 Splitting
52 Running the Installer
3060 CUSTOMER 2012-11-27
Procedure
1 Log on to the installation host using an account with the required user authorization to run the
installer
CAUTION
Do not use an existing ltsapsidgtadm user
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 Preparing the DualndashStack Split Installation Media [page 25]
3 Start the installer by double-clicking sapinstexe from the directory to which you unpacked the
DSS645_IM_ltplatformgtSAR file
NOTE
If you need to perform the installation in accessibility mode open a command prompt change
to the ltpath to unpack directorygt directory and execute sapinstexe ndashaccessible
For more information see Running the Installer in Accessibility Mode in the installation
documentation of your release
The GUI starts automatically by displaying the Welcome screen
4 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
CAUTION
Sybase Split options ldquoMove Java Databaserdquo and ldquoKeep Databaserdquo are not available in the
Welcome screen but only the steps valid for split option ldquoMove Java Databaserdquo are listed
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
5 Choose Next
6 If the installer prompts you to log off from your system log off and on again
The installer restarts automatically
7 Follow the instructions in the installer input screens and enter the required parameters
NOTE
If the installer 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 the installer displays the Parameter Summary
screen This screen shows both the parameters that you entered and those that the installer set by
default If required you can revise the parameters before starting the split procedure
8 To start the dual-stack split choose Start
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 3160
The installer starts and displays the progress of the split procedure
When the split option has finished successfully the installer displays the message Execution of
ltOption_Namegt has completed
CAUTION
Multiple Oracle Homes only The installer uses default values for the Oracle Home and
Listener configuration Therefore if you use multiple Oracle Homes you must specify the
new Oracle home as well as the listener port number You can change these values on the
installer Summary screen during the database instance installation On the Summary screen check
both Oracle gt Database System and Oracle gt Listener Configuration and use the Revise button On the
upcoming screen change the Oracle Home and the Listener port number Make sure that
you use a free port number and do not use the numbers 1521 or 1527 as these might already
be in use by default
9 We recommend that you delete the directory userprofilesdtgui
10 IBM DB2 for Linux and UNIX and Windows If not already done install the DB2 license
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
11 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running the Installer
3260 CUSTOMER 2012-11-27
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
Not valid for Sybase 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
httpservicesapcominstallnw70
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3360
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 the installer [page 29] 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 40] 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3460 CUSTOMER 2012-11-27
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 central instance host of the source system you run the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
12 On the database host of the source system you run the installer [page 29] to remove the Java database
schema
13 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
14 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
15 If required and not already done so you configure the CTS Deploy Web Service [page 40] on the ABAP
system
16 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3560
5 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 release
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
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 the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
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 40] on the ABAP
system
15 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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3660 CUSTOMER 2012-11-27
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
Keep Database
1 On the central instance host of the dual-stack system you run the installer [page 29] to export 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 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 48]
2 You restart the source system
3 You run the installer [page 29] to install a central services instance for the Java target 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 installer dialog
4 On the database instance host of the dual-stack system you run the installer [page 29] 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 the installer [page 29] to install a central instance for the Java target system using the export
from the dual-stack system
6 You continue with Follow-Up Activities [page 33]
52 Running the Installer
This section describes how to run the installer The installer includes a GUI client and a GUI server
which both use Java
The procedure describes an installation where the installer GUI client and GUI server are running on
the same host In the following GUI client and GUI server are addressed as ldquonstaller GUIrdquo
Useful Information About the Installer
When you start the installer it automatically starts the installer GUI
The installer creates the installation directory sapinst_instdir which is located directly in the
ProgramFiles directory If the installer is not able to create sapinst_instdir there it tries to
create sapinst_instdir in the directory defined by the environment variable TEMP
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 2960
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
The installer creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt which is located in ProgramFiles
The installer extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is
located in TEMP TMP TMPDIR or SystemRoot These files are deleted after the installer 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 the installer cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default port 21212 is used for communication between the installer
GUI server and the installer GUI client If this port is already in use you see an error message
In this case or if you want the installer to use a specific port open a command prompt and change
to the required directory to which you unpacked the DSS645_IM_ltplatformgtSAR file
Execute sapinstexe with the following command line parameter
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
To see a list of all available installer properties open a command prompt and start the installer
with command line parameter -p
sapinstexe -p
If you need to run the installer in accessibility mode make sure that you have activated and adjusted
accessibility settings as described in Running the Installer in Accessibility Mode in the installation
documentation of your release
If required you can stop the installer by choosing SAPinst Cancel in the installer GUI menu
Prerequisites
Make sure that you use an account with the required user authorization to run the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
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
the installer
Before you start the installer read SAP Note 1697164 which contains important information how
to run the installer
5 Splitting
52 Running the Installer
3060 CUSTOMER 2012-11-27
Procedure
1 Log on to the installation host using an account with the required user authorization to run the
installer
CAUTION
Do not use an existing ltsapsidgtadm user
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 Preparing the DualndashStack Split Installation Media [page 25]
3 Start the installer by double-clicking sapinstexe from the directory to which you unpacked the
DSS645_IM_ltplatformgtSAR file
NOTE
If you need to perform the installation in accessibility mode open a command prompt change
to the ltpath to unpack directorygt directory and execute sapinstexe ndashaccessible
For more information see Running the Installer in Accessibility Mode in the installation
documentation of your release
The GUI starts automatically by displaying the Welcome screen
4 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
CAUTION
Sybase Split options ldquoMove Java Databaserdquo and ldquoKeep Databaserdquo are not available in the
Welcome screen but only the steps valid for split option ldquoMove Java Databaserdquo are listed
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
5 Choose Next
6 If the installer prompts you to log off from your system log off and on again
The installer restarts automatically
7 Follow the instructions in the installer input screens and enter the required parameters
NOTE
If the installer 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 the installer displays the Parameter Summary
screen This screen shows both the parameters that you entered and those that the installer set by
default If required you can revise the parameters before starting the split procedure
8 To start the dual-stack split choose Start
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 3160
The installer starts and displays the progress of the split procedure
When the split option has finished successfully the installer displays the message Execution of
ltOption_Namegt has completed
CAUTION
Multiple Oracle Homes only The installer uses default values for the Oracle Home and
Listener configuration Therefore if you use multiple Oracle Homes you must specify the
new Oracle home as well as the listener port number You can change these values on the
installer Summary screen during the database instance installation On the Summary screen check
both Oracle gt Database System and Oracle gt Listener Configuration and use the Revise button On the
upcoming screen change the Oracle Home and the Listener port number Make sure that
you use a free port number and do not use the numbers 1521 or 1527 as these might already
be in use by default
9 We recommend that you delete the directory userprofilesdtgui
10 IBM DB2 for Linux and UNIX and Windows If not already done install the DB2 license
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
11 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running the Installer
3260 CUSTOMER 2012-11-27
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
Not valid for Sybase 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
httpservicesapcominstallnw70
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3360
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 the installer [page 29] 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 40] 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3460 CUSTOMER 2012-11-27
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 central instance host of the source system you run the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
12 On the database host of the source system you run the installer [page 29] to remove the Java database
schema
13 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
14 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
15 If required and not already done so you configure the CTS Deploy Web Service [page 40] on the ABAP
system
16 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3560
5 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 release
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
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 the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
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 40] on the ABAP
system
15 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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3660 CUSTOMER 2012-11-27
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed
The installer creates a subdirectory for each installation option called sapinst_instdir
ltinstallation_option_directorygt which is located in ProgramFiles
The installer extracts itself to a temporary directory called sapinst_exexxxxxxxxxx which is
located in TEMP TMP TMPDIR or SystemRoot These files are deleted after the installer 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 the installer cannot find a temporary directory the installation terminates with the error
FCO-00058
During the installation the default port 21212 is used for communication between the installer
GUI server and the installer GUI client If this port is already in use you see an error message
In this case or if you want the installer to use a specific port open a command prompt and change
to the required directory to which you unpacked the DSS645_IM_ltplatformgtSAR file
Execute sapinstexe with the following command line parameter
GUISERVER_DIALOG_PORT=ltport_number_gui_server_to_gui_clientgt
To see a list of all available installer properties open a command prompt and start the installer
with command line parameter -p
sapinstexe -p
If you need to run the installer in accessibility mode make sure that you have activated and adjusted
accessibility settings as described in Running the Installer in Accessibility Mode in the installation
documentation of your release
If required you can stop the installer by choosing SAPinst Cancel in the installer GUI menu
Prerequisites
Make sure that you use an account with the required user authorization to run the installer
For more information see Required User Authorization for Running the Installer in the installation
documentation of your release
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
the installer
Before you start the installer read SAP Note 1697164 which contains important information how
to run the installer
5 Splitting
52 Running the Installer
3060 CUSTOMER 2012-11-27
Procedure
1 Log on to the installation host using an account with the required user authorization to run the
installer
CAUTION
Do not use an existing ltsapsidgtadm user
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 Preparing the DualndashStack Split Installation Media [page 25]
3 Start the installer by double-clicking sapinstexe from the directory to which you unpacked the
DSS645_IM_ltplatformgtSAR file
NOTE
If you need to perform the installation in accessibility mode open a command prompt change
to the ltpath to unpack directorygt directory and execute sapinstexe ndashaccessible
For more information see Running the Installer in Accessibility Mode in the installation
documentation of your release
The GUI starts automatically by displaying the Welcome screen
4 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
CAUTION
Sybase Split options ldquoMove Java Databaserdquo and ldquoKeep Databaserdquo are not available in the
Welcome screen but only the steps valid for split option ldquoMove Java Databaserdquo are listed
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
5 Choose Next
6 If the installer prompts you to log off from your system log off and on again
The installer restarts automatically
7 Follow the instructions in the installer input screens and enter the required parameters
NOTE
If the installer 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 the installer displays the Parameter Summary
screen This screen shows both the parameters that you entered and those that the installer set by
default If required you can revise the parameters before starting the split procedure
8 To start the dual-stack split choose Start
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 3160
The installer starts and displays the progress of the split procedure
When the split option has finished successfully the installer displays the message Execution of
ltOption_Namegt has completed
CAUTION
Multiple Oracle Homes only The installer uses default values for the Oracle Home and
Listener configuration Therefore if you use multiple Oracle Homes you must specify the
new Oracle home as well as the listener port number You can change these values on the
installer Summary screen during the database instance installation On the Summary screen check
both Oracle gt Database System and Oracle gt Listener Configuration and use the Revise button On the
upcoming screen change the Oracle Home and the Listener port number Make sure that
you use a free port number and do not use the numbers 1521 or 1527 as these might already
be in use by default
9 We recommend that you delete the directory userprofilesdtgui
10 IBM DB2 for Linux and UNIX and Windows If not already done install the DB2 license
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
11 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running the Installer
3260 CUSTOMER 2012-11-27
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
Not valid for Sybase 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
httpservicesapcominstallnw70
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3360
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 the installer [page 29] 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 40] 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3460 CUSTOMER 2012-11-27
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 central instance host of the source system you run the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
12 On the database host of the source system you run the installer [page 29] to remove the Java database
schema
13 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
14 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
15 If required and not already done so you configure the CTS Deploy Web Service [page 40] on the ABAP
system
16 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3560
5 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 release
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
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 the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
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 40] on the ABAP
system
15 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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3660 CUSTOMER 2012-11-27
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
Procedure
1 Log on to the installation host using an account with the required user authorization to run the
installer
CAUTION
Do not use an existing ltsapsidgtadm user
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 Preparing the DualndashStack Split Installation Media [page 25]
3 Start the installer by double-clicking sapinstexe from the directory to which you unpacked the
DSS645_IM_ltplatformgtSAR file
NOTE
If you need to perform the installation in accessibility mode open a command prompt change
to the ltpath to unpack directorygt directory and execute sapinstexe ndashaccessible
For more information see Running the Installer in Accessibility Mode in the installation
documentation of your release
The GUI starts automatically by displaying the Welcome screen
4 In the Welcome screen choose Dual-Stack Split ltYour Split Optiongt
CAUTION
Sybase Split options ldquoMove Java Databaserdquo and ldquoKeep Databaserdquo are not available in the
Welcome screen but only the steps valid for split option ldquoMove Java Databaserdquo are listed
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
5 Choose Next
6 If the installer prompts you to log off from your system log off and on again
The installer restarts automatically
7 Follow the instructions in the installer input screens and enter the required parameters
NOTE
If the installer 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 the installer displays the Parameter Summary
screen This screen shows both the parameters that you entered and those that the installer set by
default If required you can revise the parameters before starting the split procedure
8 To start the dual-stack split choose Start
5 Splitting
52 Running the Installer
2012-11-27 CUSTOMER 3160
The installer starts and displays the progress of the split procedure
When the split option has finished successfully the installer displays the message Execution of
ltOption_Namegt has completed
CAUTION
Multiple Oracle Homes only The installer uses default values for the Oracle Home and
Listener configuration Therefore if you use multiple Oracle Homes you must specify the
new Oracle home as well as the listener port number You can change these values on the
installer Summary screen during the database instance installation On the Summary screen check
both Oracle gt Database System and Oracle gt Listener Configuration and use the Revise button On the
upcoming screen change the Oracle Home and the Listener port number Make sure that
you use a free port number and do not use the numbers 1521 or 1527 as these might already
be in use by default
9 We recommend that you delete the directory userprofilesdtgui
10 IBM DB2 for Linux and UNIX and Windows If not already done install the DB2 license
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
11 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running the Installer
3260 CUSTOMER 2012-11-27
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
Not valid for Sybase 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
httpservicesapcominstallnw70
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3360
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 the installer [page 29] 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 40] 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3460 CUSTOMER 2012-11-27
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 central instance host of the source system you run the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
12 On the database host of the source system you run the installer [page 29] to remove the Java database
schema
13 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
14 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
15 If required and not already done so you configure the CTS Deploy Web Service [page 40] on the ABAP
system
16 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3560
5 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 release
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
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 the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
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 40] on the ABAP
system
15 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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3660 CUSTOMER 2012-11-27
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
The installer starts and displays the progress of the split procedure
When the split option has finished successfully the installer displays the message Execution of
ltOption_Namegt has completed
CAUTION
Multiple Oracle Homes only The installer uses default values for the Oracle Home and
Listener configuration Therefore if you use multiple Oracle Homes you must specify the
new Oracle home as well as the listener port number You can change these values on the
installer Summary screen during the database instance installation On the Summary screen check
both Oracle gt Database System and Oracle gt Listener Configuration and use the Revise button On the
upcoming screen change the Oracle Home and the Listener port number Make sure that
you use a free port number and do not use the numbers 1521 or 1527 as these might already
be in use by default
9 We recommend that you delete the directory userprofilesdtgui
10 IBM DB2 for Linux and UNIX and Windows If not already done install the DB2 license
NOTE
If you have bought your DB2 license from SAP (OEM customers) install the DB2 license as
described in SAP Note 816773
11 If you copied installation media to your hard disk you can delete these files when the installation
has successfully completed
5 Splitting
52 Running the Installer
3260 CUSTOMER 2012-11-27
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
Not valid for Sybase 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
httpservicesapcominstallnw70
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3360
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 the installer [page 29] 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 40] 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3460 CUSTOMER 2012-11-27
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 central instance host of the source system you run the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
12 On the database host of the source system you run the installer [page 29] to remove the Java database
schema
13 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
14 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
15 If required and not already done so you configure the CTS Deploy Web Service [page 40] on the ABAP
system
16 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3560
5 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 release
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
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 the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
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 40] on the ABAP
system
15 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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3660 CUSTOMER 2012-11-27
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 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
Not valid for Sybase 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
httpservicesapcominstallnw70
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3360
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 the installer [page 29] 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 40] 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3460 CUSTOMER 2012-11-27
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 central instance host of the source system you run the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
12 On the database host of the source system you run the installer [page 29] to remove the Java database
schema
13 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
14 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
15 If required and not already done so you configure the CTS Deploy Web Service [page 40] on the ABAP
system
16 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3560
5 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 release
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
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 the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
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 40] on the ABAP
system
15 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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3660 CUSTOMER 2012-11-27
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 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 the installer [page 29] 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 40] 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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 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 release
6 You perform the required usage type and software unit-specific follow-up activities such as
configuring SAP Java Connector (SAP JCo) settings
For more information see the follow-up activities section in the product specific system copy
documentation of your product version
NOTE
BI Java only
6 Follow-Up Activities
61 Follow-Up Activities Checklist
3460 CUSTOMER 2012-11-27
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 central instance host of the source system you run the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
12 On the database host of the source system you run the installer [page 29] to remove the Java database
schema
13 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
14 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
15 If required and not already done so you configure the CTS Deploy Web Service [page 40] on the ABAP
system
16 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3560
5 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 release
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
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 the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
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 40] on the ABAP
system
15 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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3660 CUSTOMER 2012-11-27
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 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 central instance host of the source system you run the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
12 On the database host of the source system you run the installer [page 29] to remove the Java database
schema
13 On the ABAP system you call transaction RZ10 to reimport the profiles from the file system
14 In the Transport Management System (TMS) on the ABAP system you configure the transport routes
[page 38]
15 If required and not already done so you configure the CTS Deploy Web Service [page 40] on the ABAP
system
16 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
If your system is a high-availability system you install a license on each cluster node of the Java
target system
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
6 Follow-Up Activities
61 Follow-Up Activities Checklist
2012-11-27 CUSTOMER 3560
5 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 release
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
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 the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
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 40] on the ABAP
system
15 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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3660 CUSTOMER 2012-11-27
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
5 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 release
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
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 the installer [page 29] to remove the Java
parts from the central instance
9 On the dialog instance host of the source system you run the installer [page 29] to remove the Java
parts from the dialog instance
10 On the central services instance host of the source system you run the installer [page 29] to remove
the central services instance
11 Only valid for HA (MSCS) |
On the enqueue replication server instance host of the source system you run the installer [page
29] to remove the enqueue replication server instanceEnd of HA (MSCS) |
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 40] on the ABAP
system
15 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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
3660 CUSTOMER 2012-11-27
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
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
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
6 Follow-Up Activities
62 Maintaining the Connection to the System Landscape Directory
2012-11-27 CUSTOMER 3760
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
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
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
6 Follow-Up Activities
63 Configuring Transport Routes
3860 CUSTOMER 2012-11-27
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
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
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 40]
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
6 Follow-Up Activities
63 Configuring Transport Routes
2012-11-27 CUSTOMER 3960
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
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 49]
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
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
6 Follow-Up Activities
64 Configuring the CTS Deploy Web Service
4060 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
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
2012-11-27 CUSTOMER 4160
This page is left blank for documents that are printed on both sides
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 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
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
7 Additional Information
71 Troubleshooting
This section describes the steps that you need to perform manually if the installer 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 the installer 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 installer menu
For more information see section Interrupted Installation with the installer 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
72 Additional Information About the Installer
721 Performing a Remote Installation with the Installer
You use this procedure to install your SAP system on a remote host In this case the installer runs on
the remote host and the installer GUI runs on the local host The local host is the host from which
7 Additional Information
71 Troubleshooting
2012-11-27 CUSTOMER 4360
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
you control the installation with the installer GUI The installer GUI connects using a secure SSL
connection to the installer
If your security policy requires that the person performing the installation by running the installer
GUI on the local host is not allowed to know administrator credentials on the remote host you can
specify another operating system user for authentication purposes You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting sapinstexe from the command line You
have to confirm that the user is a trusted one For more information see SAP Note 1745524
Prerequisites
The remote host meets the prerequisites for starting the installer as described in Running the
Installer [page 29]
Both computers are in the same network and can ping each other
To test this
1 Log on to your remote host and enter the command ping ltlocal hostgt
2 Log on to the local host and enter the command ping ltremote hostgt
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Starting the Installer GUI Separately [page 45]
If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter make sure that this user exists on the remote host
Procedure
1 Log on to your remote host as a user that is a member of the local administrators group
2 Make available the installation media
3 Open a command prompt and change to the required directory by entering the following
command
cd d ltpath to unpack directorygt
4 Check the version of the sapinst executable by entering the following command
sapinst ndashsfxver
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 45])
5 Execute sapinstexe -nogui
The installer now starts and waits for the connection to the installer GUI You see the following
at the command prompt
guiengine no GUI connected waiting for a connection on host lthost_namegt port
ltport_numbergt to continue with the installation
6 Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page
45]
7 Additional Information
72 Additional Information About the Installer
4460 CUSTOMER 2012-11-27
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
722 Starting the Installer GUI Separately
You use this procedure to start the installer GUI separately You need to start the installer GUI separately
in the following cases
You closed the installer GUI using File Exit from the installer menu while the installer is still
running
You want to perform a remote installation where the installer GUI runs on a different host from
the installer For more information see Performing a Remote Installation with the Installer [page 43]
Prerequisites
The host on which you want to start the installer GUI meets the prerequisites for starting the
installer as described in Running the Installer [page 29]
Make sure that the sapinstexe on the remote host and the sapinstguiexe on the local host
have exactly the same version You can check this by using the option ndashsfxver as described in the
procedure below and in the procedure in Performing a Remote Installation with the Installer [page 43]
Procedure
Starting the Installer GUI on Windows
1 Make the unpack directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
2 Change to the directory of the sapinstgui executable using the following command
cd d ltpath to unpack directorygt
NOTE
If you start the installer GUI executable on Windows 7 or Windows 2008 you must use the
option Run as administrator Typically you first start a command prompt using Run as
administrator Then in this command prompt you enter the installer GUI command
3 Start the installer GUI from a command prompt by executing sapinstguiexe with the relevant
command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of sapinstguiexe by entering the following command
sapinstguiexe ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4560
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstguiexe -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstguiexe -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
Starting the Installer GUI on UNIX
1 Make the download directory available on the host on which you want to start the installer GUI
For more information see Preparing the Dual Stack Split Installation Media [page 25]
RECOMMENDATION
Make installation media locally available For example if you use Network File System (NFS)
reading from media mounted with NFS might fail
2 Change to the directory of the sapinstgui executable using the following command
cd ltpath to unpack directorygt
3 Start the installer GUI by executing sapinstgui with the relevant command line parameters
If you want to perform a remote installation proceed as follows
1 Check the version of the sapinstgui executable by entering the following command
sapinstgui ndashsfxver
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with the
Installer [page 43])
2 Start the installer GUI by entering the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
7 Additional Information
72 Additional Information About the Installer
4660 CUSTOMER 2012-11-27
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you closed the installer GUI using File Exit and want to reconnect to the installer
proceed as follows
If you are performing a local installation with the installer and the installer GUI running
on the same host execute the following command
sapinstgui -port ltport_number_gui_server_to_gui_clientgt
ndash where ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
If you are performing a remote installation with the installer and the installer GUI running
on different hosts execute the following command
sapinstgui -host ltremote_hostgt -port
ltport_number_gui_server_to_gui_clientgt
ndash where ltremote_hostgt is the name of the remote host and
ltport_number_gui_server_to_gui_clientgt is the port the GUI server uses to
communicate with the GUI client (21212 by default)
The installer GUI starts and connects to the installer
4 Only valid for zOS |
Start the installer GUI in one of the following ways
If the installer GUI runs on the same host as the installer enter the following command
without any additional parameters
startInstGuish
By default the installer GUI uses the local host
If the installer runs on a different host from the installer GUI (remote installation) enter the
following command with additional parameters
startInstGuish -host lthost_namegt where lthost_namegt is the host name of the
installation host
NOTE
If you enter the command without additional parameters the installer GUI uses the
local host as default The installer GUI starts and tries to connect to the installer
Since the installer is running on another host the installer GUI cannot connect and
the SAP Installation GUI Connection dialog appears
In this case enter the name of host on which the installer is running and choose Log
on
The first screen of the installation appears and you can perform the remote
installation from your local host
7 Additional Information
72 Additional Information About the Installer
2012-11-27 CUSTOMER 4760
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
For a list of options to start the installer GUI change to the same directory as your
installer executable and enter the command
startInstGuish -h
End of zOS |
73 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
In SAP MMC choose All tasks Restart service
3 Restart the instance by calling transaction SMICM
74 Keep Database Restarting Instances
NOTE
This section is not relevant for Sybase
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
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
In SAP MMC choose All tasks Restart service
7 Additional Information
73 Move Java Database Restarting Instances
4860 CUSTOMER 2012-11-27
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
4 Restart the instance by calling transaction SMICM
75 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 8 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
75 Splitting Within a System Landscape
2012-11-27 CUSTOMER 4960
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
Figure 9 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 40]
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)
Figure 10 System Landscape After the Second Split with Adapted Transport Routes
7 Additional Information
75 Splitting Within a System Landscape
5060 CUSTOMER 2012-11-27
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
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 40]
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 11 System Landscape After the Last Split with Adapted Transport Routes
76 Removing the Java Stack
If you only want to delete 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 without the need to
start the dual stack split procedure
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
PrerequisitesBefore you start the removal procedure perform the following
7 Additional Information
76 Removing the Java Stack
2012-11-27 CUSTOMER 5160
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
Shut down the J2EE cluster using transaction SMICM
Set rdispj2ee_start = 0 in the central and all dialog instance profiles
Restart the instance services as follows
Windows
In SAP MMC on the relevant instances choose All Tasks Restart Service
UNIXIBM i
Log on as ltsidgtadm and execute the following for the relevant instances
sapcontrol -nr ltinstance numbergt -function RestartService
Procedure
1 Start the installer and choose split option Move Database as described in Running the Installer [page 29]
2 Depending on your system variant perform the steps listed below
Central System
Remove Java Stack from Dual-Stack System
Distributed System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
High-Availability System
Remove Java Stack from Dual-Stack Central Instance
Remove Java Stack from Dual-Stack Dialog Instance
Remove SCS Instance from Dual-Stack System
Remove ERS Instance from Dual-Stack System
Remove Java Schema of Dual-Stack Database Instance
CAUTION
You must skip the export and installation steps
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
76 Removing the Java Stack
5260 CUSTOMER 2012-11-27
A Appendix
A1 Online Information from SAP
More information is available online as follows
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 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
Documentation
Description Internet Address Title
Installation of Multiple Components in One Database (MCOD) and its availability on different platforms
httpscnsapcomdocsDOC-8559 Multiple Components in One Database (MCOD)
Installation guide for SAP systems running on IBM DB2 with the pureScale Feature
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Installation Installation ndash SAP NetWeaver Systems
Database Installation Guide Running an SAP System on IBM DB2 101 with the pureScale Feature
Database administration guide for SAP systems on IBM DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Guide ndash SAP on IBM DB2 for Linux UNIX and Windows
Database administration using the DBA Cockpit
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
Database Administration Using the DBA Cockpit IBM DB2 for Linux UNIX and Windows
BW administration tasks for SAP systems on DB2 for Linux UNIX and Windows
httpservicesapcominstguidesnw ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides
SAP NetWeaver Business Warehouse ltReleasegt - Administrative Tasks IBM DB2 for Linux UNIX and Windows
Enabling SAP NetWeaver Business Warehouse Systems to use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
httpservicesapcominstguides ltSAP NetWeaver Main Releasegt Operations Database-Specific Guides Enabling SAP BW to use DB2 for LUW as NLS Database
How-to Guide Enabling SAP NetWeaver Business Warehouse Systems to Use IBM DB2 for Linux UNIX and Windows as Near-Line Storage (NLS)
Database Administration Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Database Administration Guide SAP on IBM DB2 for zOS
Planning Guide for SAP systems running with IBM DB2 for zOS
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
Planning Guide SAP on IBM DB2 for zOS
A Appendix
A1 Online Information from SAP
2012-11-27 CUSTOMER 5360
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
Description Internet Address Title
SAP Security Guide for SAP systems running with IBM DB2 for zOS (was formerly part of the Planning Guide SAP on IBM DB2 for zOS)
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Operations Database-Specific Guides
SAP Security Guide for IBM DB2 for zOS
SAP Front End installation Guide
httpservicesapcominstguidesnw ltSAP NetWeaver releasegt Installation Installation - Clients
SAP Front End Installation Guide ndash ltCurrent Releasegt
System Copy for SAP system based on SAP NetWeaver 73 and higher
httpservicesapcominstguides ltSAP NetWeaver | SAP Business Suite Applicationsgt ltReleasegt
Installation
System Copy for SAP Systems Based on SAP NetWeaver 73 ltEnhancement Packagegt
Maintenance Planning Guide
httpservicesapcommopz How-Tos and Guides Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)
General Quick Links
Description Internet Address
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
Installation Guides httpservicesapcominstguides
Software Logistics in Application Lifecycle Management
httpscnsapcomcommunityit-managementalmsoftware-
logistics
SAP Notes httpservicesapcomnotes
Supported platforms and operating systems
httpscnsapcomcommunitydatabase Related Resources (SCN Spaces)
SAP on DB2 for zOS httpscnsapcomcommunitydb2-for-z-os
Product Availability Matrix (PAM) httpservicesapcompam
Release notes httpservicesapcomreleasenotes
Unicode SAP systems and their availability
httpservicesapcomunicode
System sizing (Quick Sizer tool) httpservicesapcomsizing
SAP NetWeaver capabilities httpscnsapcomcommunitynetweaver
A Appendix
A1 Online Information from SAP
5460 CUSTOMER 2012-11-27
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-
Description Internet Address
Application management for SAP NetWeaver
httpscnsapcomcommunityit-managementalm
Security for SAP NetWeaver httpscnsapcomcommunitysecurity
NOTE
For information on Windows operating system security seehttpwwwmicrosoftcomsecurity
Information on SAP Support Package Stacks
httpservicesapcomsp-stacks
SAP Solution Manager httpservicesapcomsolutionmanager
Maintenance Optimizer httpservicesapcomsolman-mopz
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 V91 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009552
DB2 V95 httpwwwibmcomsupportdocviewwssrs=71ampuid=swg27009727
DB2 V97 httpwwwibmcomsupport docviewwssrs=71ampuid=swg27015148
DB2 101 httpwwwibmcomsupportdocviewwssuid=swg27024478
IBM DB2 Information Center
Database Version Internet Address
DB2 V91 httppublibboulderibmcominfocenterdb2luwv9indexjsp
DB2 V95 httppublibboulderibmcominfocenterdb2luwv9r5indexjsp
DB2 V97 httppublibboulderibmcom infocenterdb2luwv9r7indexjsp
DB2 101 httppublibboulderibmcominfocenterdb2luwv10r1
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms
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
2012-11-27 CUSTOMER 5560
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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 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
5660 CUSTOMER 2012-11-27
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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 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
2012-11-27 CUSTOMER 5760
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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 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
5860 CUSTOMER 2012-11-27
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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 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 Windows
-
- 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
- 43 Preparing the Dual Stack Split Installation Media
-
- 5 Splitting
-
- 51 Splitting Checklist
- 52 Running the Installer
-
- 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
- 72 Additional Information About the Installer
-
- 721 Performing a Remote Installation with the Installer
- 722 Starting the Installer GUI Separately
-
- 73 Move Java Database Restarting Instances
- 74 Keep Database Restarting Instances
- 75 Splitting Within a System Landscape
- 76 Removing the Java Stack
-
- A Appendix
-
- A1 Online Information from SAP
- A2 Online Information from IBM
-
- Copyright and trademarks
-