SAP Provisioning Manager Software Operations Guide

Preparing the Dual-Stack Split Media

1.4 Naming Conventions

● “usage type”, “technical usage”, and “product instance”

As of Software Provisioning Manager 1.0 SP07 (SL Toolset 1.0 SP12), the term “product instance” replaces the terms “ usage type” and “technical usage” for SAP systems based on SAP NetWeaver 7.3 including enhancement package 1 and higher. For more information, see SAP Note 1970349 . Note that there is no terminology change for older releases and all mentioned terms can be used as synonyms. As this guide is a generic document, the currently used terms remain but only “product instance” is going to be used from now on when referring to SAP NetWeaver 7.3 EHP1 and higher.

For more information, see

New Features [page 8]

● 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.5 New Features

The table below provides an overview of the new features in Software Provisioning Manager.

Make sure that you also read the release notes for your SAP product at http://help.sap.com

Area> <Product> <Release>

What’s New – Release Notes

<Product

C U S T O M E R

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Introduction

Table 2:

Feature

Media Signature

Check

Support of Oracle

12.2

SL Common GUI with SAPINST 7.49

Cleanup of Operat ing System Users

Description Availability

The signature of media is checked automatically by the installer during the

Define Parameters

phase while processing the

Media

Browser

screens. As of now the installer only accepts media whose signature has been checked. See also the description of this new security feature in SAP Note 2393060 .

For more information, see

[page 34]

and Running the Installer [page 51] .

Software Provisioning Manager

1.0 SP21 (SL Toolset 1.0 SP21)

Software Provisioning Manager (the “installer”) now supports dual-stack split for SAP systems with Oracle 12.2.

Software Provisioning Manager

1.0 SP21 (SL Toolset 1.0 SP21)

With the new installer framework version SAPINST 7.49, you can now use the new SAPUI5-based graphical user interface (GUI)

“SL Common GUI”. For more information, see Useful Information

About the Installer [page 57]

, Running the Installer [page 51] ,

and SAP Note 2336746 .

Software Provisioning Manager

1.0 SP20 (SL Toolset 1.0 SP20)

You can now specify during the

Define Parameters

phase that the group SAPINST is to be removed from the operating system users after the execution of the installer has completed.

Software Provisioning Manager

1.0 SP20 (SL Toolset 1.0 SP20)

Verification of Integ rity of Data Units in

Software Provision ing Manager

The integrity of data units extracted from the Software Provision ing Manager archive is verified. For more information, see

Down loading and Extracting the Software Provisioning Manager Ar chive [page 35] .

Software Provisioning Manager

1.0 SP19 (SL Toolset 1.0 SP19)

In addition, check SAP Note 1680045 whether additional in formation is available.

Move of AS Java

Target System to

Different Operating

System and Data base Type During

Dual-Stack Split

When performing a dual-stack split, you can now move the Java stack of the dual-stack system being split to an AS Java system on an operating system or database type different from the oper ating system and database type of the original dual-stack system.

For more information, see

Operating System and Database Mi gration During Dual-Stack Split [page 16]

Software Provisioning Manager

1.0 SP18 (SL Toolset 1.0 SP18)

Note

With Software Provisioning Manager 1.0 SP17 this feature was already available but only supported for database migration to

SAP Solution Manager 7.2 on SAP HANA database. It is now generally supported.

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Introduction

C U S T O M E R

Feature Description Availability

System Provision ing for SAP

NetWeaver 7.5 and

SAP NetWeaver 7.5based Products

All system provisioning tasks (installation, system copy, system rename) are available for the new SAP NetWeaver 7.5 release.

The Dual Stack option, which integrates an AS ABAP and AS Java in a single system (common System ID

SAP systems based on SAP NetWeaver 7.5.

, common startup framework, common database), is no longer supported in

Software Provisioning Manager

1.0 SP09 (SL Toolset 1.0 SP15)

After upgrading to SAP NetWeaver 7.5 PI, you first have to split the still existing dual stack-system before you can use SAP

NetWeaver 7.5 PI productively.

For more information, see the Upgrade Master Guide - SAP Net

Weaver 7.5 at:

Upgrade

http://help.sap.com/nw75

Installation and

System Provision ing for SAP Solution

Manager 7.2

All system provisioning tasks (installation, system copy, system rename) are available for the new SAP Solution Manager 7.2 re lease. Compared to previous SAP Solution Manager releases,

SAP Solution Manager 7.2 is no longer provided as a classical dual-stack system (ABAP system with Java Add-in), but consists of a separate ABAP and Java stack.

Software Provisioning Manager

1.0 SP09 (SL Toolset 1.0 SP15)

Reusing Server

Ports from the origi nal dual-stack sys tem that is being split

You can now reuse specific ports from the original dual-stack sys tem in the target Java system, such as the ICM server ports and the message server ports.

For more information, see

Planning Checklist [page 21]

Software Provisioning Manager

1.0 SP10 (SL Toolset 1.0 SP14)

Usage Type Library

Deprecation for

SAP Systems Based on SAP NetWeaver

7.3 EHP1 and Higher

Software Provisioning Manager 1.0 no longer uses the “Usage

Types” definitions in its business logic for SAP systems based on

SAP NetWeaver 7.3 EHP1 and higher. This is done to unify model ing and terminology across all SAP tools used during the plan ning, installation and maintenance activities. The “Product In stance” definition replaces “Usage Types” regarding product modeling. For more information, see SAP Notes 1970349 and

1877731 .

Software Provisioning Manager

1.0 SP07 (SL Toolset 1.0 SP12)

Feedback Evalua tion Form

SAP SE’s aim is to provide fast and efficient procedures. To eval uate the procedure you just carried out, we need information gen erated by the tool during process execution and your experience with the tool itself. A new evaluation form contains a simple ques tionnaire and XML data generated during the procedure.

Software Provisioning Manager

1.0 SP07 (SL Toolset 1.0 SP12)

Port 4239 is used for displaying the feedback evaluation form.

For more information, see

Prerequisites for Running the Installer

[page 49] .

C U S T O M E R

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Introduction

Feature Description Availability

Option

Verify Signed

Media

The digital signature ensures that the signatory of a digital docu ment can be identified unambiguously and signatory’s name is documented together with the signed document, the date, and the time.

For more information, see SAP Note 1979965 .

Software Provisioning Manager

1.0 SP06 (SL Toolset 1.0 SP11)

Automatic user check of the

QSECOFR

and the

IBM i installation user

The installer checks if the user

QSECOFR

and the IBM i installa tion user are prepared correctly. Only if the installer detects an inconsistency, then a dialog screen appears.

For more information about how to prepare these users, see

Pre paring an IBM i User Profile [page 43] and

Enable the User QSE

COFR [page 45]

Software Provisioning Manager

1.0 SP20 (SL Toolset 1.0 SP20)

1.6 Constraints

You need to consider some constraints before you start splitting your SAP dual-stack system.

● Dual Stack Split scenario “Keep Database” (see

Split Option: Keep Database [page 18] ) in a

heterogeneous system setup - SCS instance and primary application server (PAS) instance are running on different operating systems - of a distributed target Java system is not supported. This is because the installation of the target SCS instance and PAS instance reuses the kernel, SAPJVM, and other executables of the source PAS instance. Thus the target SCS instance and PAS instance must be installed on an operating system compatible with the kernel of the source PAS instance.

● The dual-stack split procedure does not support the splitting of the following:

○ SAP Process Integration systems based on SAP NetWeaver releases lower than 7.5.

○ SAP Solution Manager systems with releases lower than 7.2.

○ Heterogeneous systems

○ Since MCOD is not supported for SAP systems with SAP ASE, you cannot use split option Keep

Database. Instead, you can only use split option Move Java Database [page 14]

● The dual-stack split procedure does not implicate the following:

○ Prerequisites Checker

○ SAP host agent

○ Diagnostics agent

○ Additional application server 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.

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Introduction

C U S T O M E R

● Only SAP systems that are using the SAP NetWeaver 7.20 kernel or higher are split .

1.7 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 http:// support.sap.com/notes .

Table 3: SAP Notes for the Dual-Stack Split

SAP Note Number Title Description

1680045

1797362

1655335

Release Note for Software Provisioning

Manager 1.0

Software provisioning manager 1.0 with installation, system copy, system re name and dual-stack split for SAP

NetWeaver-based systems

Dual-Stack Split for Systems Based on

SAP NetWeaver

Problems discovered after the publica tion of the dual-stack split guide

Use Cases for Splitting Dual-Stack Sys tems

—

1.8 Accessing the SAP Library

The references to the SAP NetWeaver Library documentation in this guide always refer to the following on

SAP Help Portal:

● SAP systems based on SAP NetWeaver 7.3: http://help.sap.com/nw73

Application Help Function-Oriented View: English

● SAP systems based on SAP NetWeaver 7.3 including Enhancement Package 1: http://help.sap.com/nw731

Application Help Function-Oriented View: English

● SAP systems based on SAP NetWeaver 7.4: http://help.sap.com/nw74

Application Help Function-Oriented View: English

● SAP systems based on SAP NetWeaver 7.5: http://help.sap.com/nw75

Application Help Function-Oriented View: English

C U S T O M E R

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Introduction

1.9 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 Java installation guide relevant for your database and operating system platform, which you can find at: https://help.sap.com/sltoolset

Area System Provisioning Guide for Installation of Systems Based on

SAP NetWeaver 7.1 and Higher Installation Guides by Database

Java

In the following, we refer to this documentation as “installation guide”.

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:

○ “Move Java Database” (one SAP system on one host)

○ “Keep Database” (multiple SAP systems on one host)

For more information, see

Split Options Covered by this Guide [page 14]

2. You follow the list of steps at the beginning of each phase:

○

Planning [page 21]

○

Preparation [page 24]

○

Splitting [page 46]

○

Follow-up Activities [page 70]

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Introduction

C U S T O M E R

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.

Related Information

Split Option: Move Java Database [page 14]

Split Option: Keep Database [page 18]

2.1 Split Option: Move Java Database

The split option “Move Java Database” offers the possibility to split a dual-stack system into one ABAP system and one Java system each on a different system host.

Move Java Database for Standard Systems

When you choose the “Move Java Database” option for a standard system, the tool 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 standard system.

These are the following instances:

● Primary application server instance (PAS instance)

● Central services instance (SCS instance)

● Database instance (DB)

Note

If required, you can install the primary application server 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 tool removes all Java parts from the dual-stack system.

C U S T O M E R

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Split Options Covered by this Guide

Figure 1: Split Option: Move Java Database for Standard Systems

Move Java Database for Distributed System

When you choose the “Move Java Database” option for a distributed system, the tool 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:

● Primary application server instance (PAS instance)

● Central services instance (SCS instance)

● Database instance (DB)

Note

If required, you can reinstall the primary application server 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 tool removes all Java parts from the dual-stack system.

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Split Options Covered by this Guide

C U S T O M E R

Figure 2: Split Option: Move Java Database for Distributed System

Related Information

Operating System and Database Migration During Dual-Stack Split [page 16]

2.1.1 Operating System and Database Migration During Dual-

Stack Split

During the export of the Java stack in the “Move Database” scenario, you can specify an operating system and database type that is different from the original operating system and database type of the source dual-stack system.

The target Java system that you are about to split off from the source dual-stack system is then installed on this newly specified operating system and database type.

Recommendation

We recommend this feature is recommended if you want to upgrade your SAP Solution Manager to release

7.2 and migrate it to SAP HANA.

For more information, see SAP Note 2227300 and SAP Solution Manager 7.2: Simplified Upgrade and

Migration to SAP HANA .

C U S T O M E R

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Split Options Covered by this Guide

If you decide to change the operating system and database type, you must provide the following SAP kernel archives for the target AS Java system. These archives must be Unicode and match the version of the SAP kernel which is used by the dual-stack system. You can download the archives from http://support.sap.com/ swdc either beforehand or during the dual-stack split procedure:

● for SAPEXE.SAR

● SAPEXEDB.SAR

● SAPJVM

<Version> .SAR

● and IGSEXE.SAR

● optional: SAPCRYPTOLIB.SAR

Note

The manifests inside the provided archives are checked, if they match the values of the source system and hardcoded values, such as target operating system or Unicode. The export is created as usual, the so-called

EXE.SAR is created from the provided archives, and the SOURCE.PROPERTIES file of the export is updated with the target operating system and database type, overwriting the values of the source dual-stack system. The target Java installation works the same way as if you did not change the operating system and database type.

Related Information

Split Option: Move Java Database [page 14]

user management [page 23] .

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Split Options Covered by this Guide

C U S T O M E R

2.2 Split Option: Keep Database

The split option “Keep Database” offers the possibility for the Java system to reuse the existing Java database library of the dual-stack system using multiple SAP systems on one host.

Recommendation

MCOD is generally available and there is no intention to de-support this installation feature.

However, SAP recommends that customers should not use the MCOD feature when installing new systems.

The major drawbacks are as follows:

● Previous-point-in-time (PPT) recovery of a single system within an MCOD installation becomes a highly complex and time-consuming procedure.

● SAP Landscape Management (LaMa) is generally not supported for MCOD installations. For more information, see SAP Note 1709155 .

● There are strong dependencies, for example on the database version used for the MCOD system.

● Downtime - planned or unplanned - always affects all systems sharing the same database.

Exception: In case of a dual-stack split you can use the “Keep Database” option thus keeping ABAP and

Java stack in one database. There, the PPT recovery problem does not apply because both stacks belong logically together and would always be recovered jointly anyhow. However, keep in mind that even for this specific case the introduction of SAP Landscape Management would require a split into separate database subsystems.

Additional information might be available in SAP Note 2146542 .

Keep Database for Central and Distributed Systems

When you choose the “Keep Database” option, the tool exports the Java file system on the dual-stack system.

It uses this export to reinstall a central services instance (SCS) and a primary application server instance

(PAS) for Java. They can be installed on one host, on different hosts, or on the source system hosts again.

Additionally, the tool 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 tool removes all Java parts from the dual-stack system except the Java database schema.

C U S T O M E R

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Split Options Covered by this Guide

Figure 3: Split Option: Keep Database for Standard Systems

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Split Options Covered by this Guide

C U S T O M E R

Figure 4: Split Option: Keep Database for Distributed Systems

C U S T O M E R

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Split Options Covered by this Guide

3 Planning

3.1 Planning Checklist

This section includes the planning steps that you must perform when you want to install the new Java system on one or more hosts.

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.

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 Java installation guide relevant for your database and operating system platform, which you can find at: https://support.sap.com/sltoolset

System Provisioning Installation Option of Software Provisioning

Manager Guide for Installation of Systems Based on SAP NetWeaver 7.1 and Higher Installation Guides by Database

Java

In the following, we refer to this documentation as “installation guide”.

Prerequisites

You have decided on your

split option [page 14] .

Procedure

1. You check the hardware and software requirements for the Java installation host.

For more information, see Hardware and Software Requirements in the installation guide.

2. You read about

3. You plan for independent ASPs.

For more information, see Planning for Independent ASPs in the installation guide.

4. You identify basic SAP system installation parameters.

For more information, see Basic Installation Parameters in the installation guide.

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Planning

C U S T O M E R

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 23]

○ System Landscape Directory (SLD)

You can ignore SLD parameters.

○ SAP system ports

You can specify the ports that you plan to reuse in the Java system you are about to create during the dual-stack split procedure.

Note

If you choose to reuse the ports from the original dual-stack system in the target AS Java system, keep in mind that you cannot access the additional application server instances of the original dual-stack system using these ports any longer during the split procedure, because the original ports are now used by the newly installed Java system.

○ Internet Communication Manager Ports:

You can specify the Internet Communication Manager (ICM) ports that you want the target

AS Java to take over from the source system. The selected ports are removed from the primary application server instance of the source system and then inserted in the instance profile of the primary application server instance of the target AS Java system. An ICM server port is the icm/server_port_

<xx>

profile parameter.

Note

Before the ports are moved, they are resolved to numerical values.

○ Message Server Ports:

You can migrate message server ports from the original dual-stack system to the target AS

Java system, if you want to ensure that the newly created ABAP and Java systems stay connected. You can move all ms/server_port_

<XX>

port parameters from the SCS instance of the original dual-stack system to SCS instance of the Java system being created during the split procedure.

Note

Before the ports are moved, they are resolved to numerical values.

○ “Move Database only”: You can specify whether you want to install the split-off target AS Java system on an operating system or database type different from the source dual-stack system. Otherwise the

SAP Kernel from the dual-stack system is archived and used to install the target AS Java system on the same operating system and database type as the source dual-stack system.

○ Target Database Type:

Specify the target database type if you want to migrate the target AS Java system to a database type different from that of the source dual-stack system.

○ Target Operating System:

Specify the target operating system if you want to migrate the target AS Java system to an operating system different from that of the source dual-stack system.

C U S T O M E R

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Planning

○ SAP Kernel archives (*.SAR files) downloaded from http://support.sap.com/swdc .

The archives must be Unicode and of the same version as the SAP Kernel of the dual-stack system.

5. You decide on the transport host to use.

For more information, see SAP System Transport Host in the installation guide

6. You plan for adapting the transport routes within your system landscape. For more information, see

Splitting Within a System Landscape [page 78]

7. To install a high-availability system, you read Planning the Switchover Cluster in the installation guide.

8. Optionally, you decide whether you want to install multiple SAP systems on a single host.

For more information, see Multiple SAP Systems on a Single Host in the installation guide.

9. You can continue with

Preparation [page 24] .

3.2 User Management

The dual-stack split procedure does not change the user management and you cannot choose which kind of user management you want to use for the target AS Java system. That is, the separated Java system and the

ABAP system both use the user management of the former dual-stack system. The following is possible:

● If the dual-stack system uses AS ABAP as data source for the User Management Engine (UME), after the split the separated Java stack will also use the ABAP UME.

● If the dual-stack system uses an LDAP directory as source for user data, this is also valid for the Java stack.

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 .

Note

If the UME data source is configured to use an ABAP data source and the UME data source configuration file is not one of the supported files mentioned in SAP Note 718383 , the tool does not work.

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Planning

C U S T O M E R

4 Preparation

4.1 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 Java installation guide relevant for your database and operating system platform, which you can find at: https://support.sap.com/sltoolset

System Provisioning Installation Option of Software Provisioning

Manager Guide for Installation of Systems Based on SAP NetWeaver 7.1 and Higher Installation Guides by Database

Java

In the following, we refer to this documentation as “installation guide”.

1. If you want to install the application server Java on a new IBM i host which is not yet prepared, you must complete the preparation for IBM i on this host.

For more information, see Preparation for IBM i in the installation guide.

2. You set up file systems and make sure that the required disk space is available for the directories to be created during the installation of the Java system.

For more information, see Setting Up File Systems in the installation guide.

3. If applicable, you set up virtual host names.

For more information, see

Using Virtual Host Names [page 33]

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

5. If you want to share the transport directory trans from another system, make this directory available to your installation hosts.

For more information, see Setting Up the Transport Directory in the installation guide.

6. If the Java stack is used as non-ABAP target system, we recommend that you clean up the import queue by importing all transport requests in the queue. If this is not possible, you must copy the import buffer after performing the dual-stack split. For more information, see

Configuring Target Systems for Non-

ABAP Transports [page 76]

7. If you want to use customized UME data source configuration file, see the

SAP Library [page 12] for your

release at:

Security Identity Management User Management of the Application Server Java Configuring User

Management UME Data Sources LDAP Directory as Data Source Customizing a UME Data Source

Configuration

8. You make sure that the required media are available on each host.

C U S T O M E R

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Preparation

You can download the Java stack and database installation media from SAP Service Marketplace as

described in Preparing the Dual-Stack Split Media [page 34] .

9. You copy the media manually to your IBM i.

For more information, see

Copying the Installation Media Manually to Your IBM i [page 41] .

10. You can continue with

Splitting the Dual-Stack System [page 46] .

4.2 Configuring TCP/IP

Use

This section describes how to integrate IBM i into your TCP/IP network.

Prerequisites

Before configuring TCP/IP, you must do the following:

● Make sure that you have the following information:

○ The interface of your IBM i to which the Local Area Network is attached

○ The IP addresses of your IBM i, subnet mask, and router or Gateway

○ The local domain name

○ The IBM i host name

● Decide on your IBM i host name. The host name cannot be longer than eight characters although SAP allows 13 characters as of Release 4.6.

For more information, see SAP Note 611361 .

Note

The TCP/IP configuration on IBM i is case sensitive. Do not enter your host name once in uppercase and then in lowercase characters. It is important that you enclose your host name entry in single quotation marks. Otherwise, the IBM i interprets the characters as uppercase characters.

Procedure

Note

An IP address is a unique address in a TCP/IP network for a particular IBM i. A subnet mask is a mask used to divide a single network address into multiple logical networks.

1. To change the name of the computer, enter the command

chgneta

and prompt

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Preparation

C U S T O M E R

You must then enter the following information and choose

ENTER

○ System name

○ Local network ID

○ Default local location name

The following screen appears:

2. To set up the description line, enter the command

WRKHDWRSC TYPE(*CMN)

and proceed as follows:

1. On the

Work with Communication Resources

screen, enter option

(Work with configuration descriptions)

for the port and choose

ENTER

2. On the

Work with Configurations Description

screen, enter option

(Create)

to enter the description gigaline or ethline and choose

ENTER

. On the following screen, enter the line speed and duplex and then press

F10

and page down two screens.

C U S T O M E R

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Preparation

On the

Create Line Desc (Ethernet) (CRTLINETH)

screen, make sure the autocreate controller is set to

*yes.

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Preparation

C U S T O M E R

3. To call the TCP/IP configuration menu, enter the command

CFGTCP

and proceed as follows:

1. To work with interfaces, enter option

(

Work with TCP/IP interfaces

C U S T O M E R

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Preparation

The following screen appears:

You need at least two entries: one for the loopback entry and one for the IP address of your IBM i.

The loopback address always takes the IP address

127.0.0.1

, subnet mask

255.0.0.0

and line description

*LOOPBACK

To add an entry, enter option

(

ADD

) and choose

ENTER

Add entries for the first three fields and accept the default values for the other fields.

2. To work with routes, enter option

(

Work with TCP/IP routes

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Preparation

C U S T O M E R

The following screen appears:

If the route to the remote host, in this case the PC workstation, is through a Gateway or if the remote host resides in a different network or subnetwork to the local host, you need to configure a route.

3. To change the domain information, enter option

(

Change TCP/IP domain information

C U S T O M E R

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Preparation

The following screen appears:

Note

It is important that you enclose your host name entry in single quotation marks. If you do not, the

IBM i interprets the characters as uppercase characters.

If you have one or more remote name servers, you need to define the IP address here. Note that the

Host name server priority

must be set to *LOCAL.

Testing the TCP/IP Connection

Before proceeding with the SAP installation (that is, the installation of the executable programs), check that this TCP/IP connection has been set up correctly. To do so, enter the command

ping

(Network Connection) specifying your own system as

Remote system

. Do this twice, once specifying only <Host_Name>, and once

<Host_Name>.<Domain_Name>.

Example

In this example we assume that the host name is as0008 and the domain name is wdf.sap.corp. In this case, your entries are the following:

●

ping 'as0008'

●

ping 'as0008.wdf.sap.corp'

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Preparation

C U S T O M E R

After installing the SAP system kernel, check the TCP/IP connection again with the command:

WRKLNK '/QFileSvr.400/<Host_Name>'

Your host name should be displayed under

Object link

, for example,

as0008

for the host in the example given above.

For more information about TCP/IP configuration, see the IBM documentation in the IBM Knowledge Center.

Result

The IBM i is integrated into your TCP/IP network.

4.3 Adjusting the Relational Database Name

Use

You use the following procedure to adjust the local relational database name (RDB name) so it is the same as the TCP/IP host name.

Note

The *Local database name must match the TCP/IP host name for the SAP system to work properly.

Procedure

1. Log on to your database host as user QSECOFR.

2. To display your TCP/IP host name, enter the following command and press

CHGTCPDMN

3. Search for the contents of HOSTNAME.

This is your TCP/IP host name.

4. Before you can adjust the local RDB name, you have to check if the entry remote location equals

*Local exists. To do this, enter the following command:

WRKRDBDIRE

5. Depending on the outcome, proceed as follows:

○ If an entry for RDB name exists and you want to adjust the name to the TCP/IP host name

<TCP_Host_Name>, enter the following command:

CHGRDBDIRE RMTLOCNAME(*LOCAL *IP) PORT(*DRDA)

RMTAUTMTH(*ENCRYPTED *ALWLOWER) DEV(*LOC) LCLLOCNAME(*LOC)

RMTNETID(*LOC) MODE(*NETATR) TNSPGM(*DRDA)

C U S T O M E R

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Preparation

○ If an entry for RDB name does not exist and a different entry exists with Remote Location *LOCAL you have to delete it using

RMVRDBDIRE RDB(<Current_RDB_*LOCAL>)

. Afterwards go to the next step and add the required RDB name.

○ If an entry for RDB name does not exist, you have to add one with the correct name

<TCP_Host_Name>.

To do this, enter the following command:

ADDRDBDIRE RDB(<TCP_Host_Name>)

RMTLOCNAME(*LOCAL *IP) PORT(*DRDA)

RMTAUTMTH(*ENCRYPTED *ALWLOWER) DEV(*LOC) LCLLOCNAME(*LOC)

RMTNETID(*LOC) MODE(*NETATR) TNSPGM(*DRDA)

6. If you are planning to use an independent ASP, make sure there is an entry for it in the RDB directory.

4.4 Using Virtual Host Names

You can use one or more virtual TCP/IP host names for SAP servers within an SAP server landscape to hide their physical network identities from each other. This can be useful when quickly moving SAP servers or complete server landscapes to alternative hardware since you do not need to reinstall or reconfigure.

Prerequisites

Make sure that the virtual host name can be correctly resolved in your Domain Name System (DNS) setup.

Context

Procedure

Proceed as described in SAP Note 1624061 .

4.5 Performing a Full System Backup

If you decided to use the split option “Keep Database”, you must perform a full system backup of the dualstack system before you start the split procedure.

If you decided to use the split option “Move Java Database”, you do not need to perform a backup before you start the split procedure.

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Preparation

C U S T O M E R

For more information about backing up your database, see the database-specific backup and recovery

documentation in the SAP Library [page 12] for your release and database at:

Table 4:

Database Path in Help Portal

IBM DB2 for i

SAP NetWeaver Library: Function-Oriented View

Database Administration Database Administration for IBM

DB2 for i

4.6 Preparing the Dual-Stack Split Media

This section describes how to prepare the media that is required for the dual-stack split, which are available as follows.

● The Software Provisioning Manager archive containing the installer.

You always have to download the latest version of the Software Provisioning Manager archive.

● The media containing the software to be installed, which are available as follows:

○ You normally obtain the physical installation media as part of the installation package. You can find them listed under Using the Physical Installation Media from the Installation Package below.

○ As an alternative to downloading the complete SAP kernel media, you can download only the archives

(SAR files) that are required from the SAP kernel for the target Java system installation, as described under Downloading the Archives Required for the Dual-Stack Split (Without Operating System and

Database Migration) below.

○ If you want to change the operating system and database type during the dual-stack split (see

Operating System and Database Migration During Dual-Stack Split [page 16] ), you have to provide the

SAPEXE <Version> .SAR, SAPEXEDB <Version> .SAR, SAPJVM <Version> .SAR, igsexe

<version> .sar, SAPCRYPTOLIB.SAR (optional) archives for the target operating system and database. You can find the information on where to download these archives under Downloading the

Archives Required for Operating System and Database Migration below.

○ You can also download the complete installation media apart from the Software Provisioning Manager archive from SAP, as described in Downloading the Complete Installation Media below.

Note

The signature of media is checked automatically by the installer during the

Define Parameters

phase while processing the

Media Browser

screens. As of now the installer only accepts media whose signature has been checked. See also the description of this new security feature in SAP Note 2393060 .

For more information about which kernel version to use, see SAP Note 1680045 . In addition, check the

Product Availability Matrix at: http://support.sap.com/pam .

You need several media during the dual-stack split. We recommend that you copy all relevant media for a dual stack split to the IFS of the IBM i host before you start the split process.

For more information, see the section

Copying the Installation Media Manually to Your IBM i [page 41] .

C U S T O M E R

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Preparation

If you did not do so already, make sure you have configured your TCP/IP as described in SAP Note 92589 .

To make the change effective, do not forget afterwards to perform an IPL. Otherwise, copy performance is poor from your local Windows media drive or Windows file system to the IFS on your IBM i.

Related Information

Downloading and Extracting the Software Provisioning Manager Archive [page 35]

Using the Physical Media from the Installation Package [page 37]

Downloading the SAP Kernel Archives Required for the Dual-Stack Split (Without Operating System and

Database Migration) [page 38]

Downloading the SAP Kernel Archives Required for Operating System and Database Migration [page 38]

Downloading Complete Installation Media [page 40]

4.6.1 Downloading and Extracting the Software Provisioning

Manager Archive

You must always download and extract the Software Provisioning Manager 1.0 archive from the SAP Software

Download Center because you must use the latest version.

Procedure

1. Download the latest version of the Software Provisioning Manager 1.0 archive

SWPM10SP <Support_Package_Number> _ <Version_Number> .SAR from: https://launchpad.support.sap.com/#/softwarecenter

SUPPORT PACKAGES & PATCHES By

Alphabetical Index (A-Z) S SOFTWARE PROVISIONING MANAGER

2. We recommend that you copy the software provisioning manager 1.0 archive to the IFS of the IBM i host.

3. If you did not do so already, make sure you have configured your TCP/IP as described in SAP Note 92589

. Do not forget afterwards to perform an IPL to make the change effective. Otherwise, the file copying is very slow from your local Windows optical media drive or Windows file system to the IFS on your IBM i.

4. Get the latest version of the SAPCAR tool on the host where you want to run the installer: a. Go to https://launchpad.support.sap.com/#/softwarecenter

SUPPORT PACKAGES &

PATCHES

and search for “

sapcar

”.

b. Select the archive file for your operating system and download it to an empty directory.

c. Rename the executable to

sapcar.exe

For more information about SAPCAR, see SAP Note 212876 .

5. Using the latest version of SAPCAR, you can verify the signature of the downloaded

SWPM10SP <Support_Package_Number> _ <Version_Number> .SAR archive as follows:

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Preparation

C U S T O M E R

a. Get the latest version of the SAPCRYPTOLIB archive to your Windows PC as follows:

1. Go to https://launchpad.support.sap.com/#/softwarecenter

SUPPORT PACKAGES &

PATCHES

and search for “

sapcryptolib

”.

2. Select the archive file for your operating system and download it to the same directory where you have put the SAPCAR executable.

3. Use the following command to extract the SAPCRYPTOLIB archive to the same directory where you have put the SAPCAR executable:

sapcar –xvf sapcryptolibp_84…sar –R <target directory>

4. Download the Certificate Revocation List from

https://tcs.mysap.com/crl/ crlbag.p7s

and move it into the same directory.

b. Verify the signature of the downloaded

SWPM10SP <Support_Package_Number> _ <Version_Number> .SAR archive by executing the following command:

Note

Check SAP Notes 2178665 and 1680045 whether additional information is available.

<Path to SAPCAR>\sapcar.exe -tvVf<Path to Download Directory>

\SWPM10SP<Support_Package_Number>_<Version_Number>.SAR -crl<file name of revocation list>

6. Unpack the Software Provisioning Manager archive to a local directory on your Windows PC using the following command:

<Path to SAPCAR>\sapcar.exe -xvf <Path to Download Directory>

\SWPM10SP<Support_Package_Number>_<Version_Number>.SAR <Path to Unpack

Directory>

Note

Make sure that all users have read permissions for the directory where you want to unpack the installer.

Caution

Make sure that you unpack the Software Provisioning Manager archive to a dedicated folder. Do not unpack it to the same folder as other installation media.

C U S T O M E R

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Preparation

4.6.2 Using the Physical Media from the Installation Package

This section describes how you use the physical installation media as part of the installation package.

Procedure

1. Identify the required media as listed below.

The following table lists the media required for the dual-stack split:

Table 5:

SAP Instance Installation

Central services instance

Central services instance, primary application server instance

Move Java Database only: Data base instance

Required Media

○ Software Provisioning Manager archive

○ UC Kernel (folder K_U_

<Version_Number> _ <OS>

) where “U” means Uni code.

○ Software Provisioning Manager archive

○ UC Kernel (folder K_U_

<Version_Number> _ <OS>

) where “U” means Uni code.

○ SAP NetWeaver Java Component (folders JAVA_*)

○ Software Provisioning Manager archive

○ UC Kernel (folder K_U_

<Version_Number> _ <OS>

) where “U” means Uni code.

○ SAP NetWeaver Java Component (folders JAVA_*)

○ MS SQL Server, Oracle Database: RDBMS media

○ MS SQL Server, Oracle Database: RDBMS patch media (if available)

2. Make the installation media available on each installation host as follows: a. Download and unpack the latest version of Software Provisioning Manager as described in

Downloading and Extracting the Software Provisioning Manager Archive [page 35] .

b. Make the installation media containing the software to be split available.

To make the media available, copy the media manually to your IBM i host before you start the installation. Do not use the Media Browser dialog during the installation to copy the entire installation media from Windows to your IBM i host. Make sure that all users have read permissions for the directory where you want to unpack the installer.

You need to

copy the installation media manually to your IBM i [page 41] .

Related Information

Copying the Installation Media Manually to Your IBM i [page 41]

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Preparation

C U S T O M E R

4.6.3 Downloading the SAP Kernel Archives Required for the

Dual-Stack Split (Without Operating System and

Database Migration)

As an alternative to providing the complete SAP kernel media, you can also download only the required installation archives for your SAP system installation. During the installation, you can either specify the dedicated path to the archive, or provide the path to a download basket with all downloaded archives.

Context

You only need to provide the SAPHOSTAGENT

<Version> .SAR for the Java target system host. The remaining software packages required for the Java target system installation are taken from the Java stack of the source system.

Procedure

You can download the SAPHOSTAGENT

<Version> .SAR archive from the following path: http://support.sap.com/swdc

Support Packages and Patches Software Downloads Support

Packages & Patches By Category SAP TECHNOLOGY COMPONENTS SAP HOST AGENT SAP HOST

AGENT 7.21

4.6.4 Downloading the SAP Kernel Archives Required for

Operating System and Database Migration

If you want to change the operating system and database type during the dual-stack split, you have to provide the SAPEXE

<Version> .SAR, SAPEXEDB <Version> .SAR, SAPJVM <Version> .SAR, igsexe

<version> .sar archives for the target operating system and database.

Procedure

1. Go to http://support.sap.com/swdc

Support Packages & Patches By Category

Support Packages and Patches Software Downloads

2. Choose the required software component and release:

○ For an SAP NetWeaver system choose

SAP NetWeaver and complementary products SAP

NetWeaver

Application Server Java

C U S T O M E R

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Preparation

○ For an SAP Business Suite system based on SAP NetWeaver, choose

SAP Application Components

Entry by Component

<Java

Product Instance>

3. Choose the required package:

Note

You have to choose the same operating system type as that of the primary application server of the dual-stack system.

Caution

○ Make sure that you always use the highest available patch level unless special patch levels are specified for the relevant package in SAP Note 1680045 .

○ Make sure that you always choose SAPEXE

<Version> .SAR, SAPEXEDB <Version> .SAR of the same SAP kernel release and extension:

Example

○ If SAPEXE

<Version> .SAR is of version 7.42 EXT, then SAPEXEDB <Version> .SAR must also be of version 7.42 EXT.

○ If SAPEXE

<Version> .SAR is of version 7.45, then SAPEXEDB <Version> .SAR must also be of version 7.45.

○ If you provide the archives in one download folder, and there is more than one version of the same archive available - for example SAPEXE

<Version> .SAR - and these versions match the productspecific requirements, the installer selects one of these archive versions. If you want a specific archive version to be used, make sure that this is the only version available in the download folder.

When running system provisioning in GUI mode, you can also check in the GUI which archive is being used. So even if there is more than one version of the same archive available in the download folder, you can select the exact archive version you want to use and enter the exact path to the required archive file.

○

SAPEXE

.SAR

SAP KERNEL

#Database independent

○

SAPEXEDB

.SAR

SAP KERNEL

○ igsexe

<version> .sar:

SAP IGS

○ SAPJVM

<Version> .SAR:

SAP JVM

○ If your target system based on SAP NetWeaver 7.3 including EHP1 or lower - that is you have to use

SAP Kernel 7.21 - download the latest patch level of SAPCRYPTOLIB

<Version> .SAR from the following path: http://support.sap.com/swdc

Support Packages and Patches Software Downloads

Support Packages & Patches By Category Additional Components SAPCRYPTOLIB

COMMONCRYPTOLIB

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Preparation

C U S T O M E R

Related Information

Operating System and Database Migration During Dual-Stack Split [page 16]

4.6.5 Downloading Complete Installation Media

This section describes how you download complete media from the SAP Software Download Center.

Procedure

1. Download and unpack the latest version of Software Provisioning Manager as described in

Downloading and Extracting the Software Provisioning Manager Archive [page 35] .

2. Create a download directory on your Windows host from where you will transfer the media to your IBM i host (for example, C:\tmp\download)

3. Identify all download objects that belong to one medium according to one of the following:

Note

Installation media might be split into several files. In this case, you have to reassemble the required files after the download.

○ Download path or location:

○ To download the complete kernel media, go to https://support.sap.com/sltoolset

System

Provisioning Software Provisioning Manager 1.0 SP

Download Kernel releases delivered for SL Toolset SL TOOLSET 1.0 (INSTALLATIONS AND UPGRADES)

KERNEL FOR INSTALLATION/SWPM

○ To download all media required for your SAP product, you can use one of the following navigation paths:

○ https://launchpad.support.sap.com/#/softwarecenter

INSTALLATIONS & UPGRADES

By Category SAP NETWEAVER AND COMPLEMENTARY PRODUCTS

○ https://launchpad.support.sap.com/#/softwarecenter

INSTALLATIONS & UPGRADES

By Alphabetical Index (A-Z)

<First Letter of Product> <Product> <Product

Release>

○ Material number

All download objects that are part of an installation medium have the same material number and an individual sequence number:

<Material_Number> _ <Sequence_Number>

Example

51031387_1

C U S T O M E R

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Preparation

51031387_2

...

○ Title

All objects that are part of an installation medium have the same title, such as

4. Download the objects to the download directory.

5. To correctly re-combine the media that are split into small parts, unpack all parts into the same directory.

In the unpacking directory, the system creates a subdirectory with a short text describing the medium and copies the data into it. The data is now all in the correct directory, the same as on the medium that was physically produced. For more information, see SAP Note 1258173 .

Caution

Make sure that you unpack each installation media to a separate folder. Do not unpack installation media to the same folder where you unpack the Software Provisioning Manager archive.

Do not unpack installation media to the same folder where you unpack the SAP kernel archives for archive-based installation.

6. You need to copy the installation media manually to your IBM i [page 41]

Related Information

Copying the Installation Media Manually to Your IBM i [page 41]

4.6.6 Copying the Installation Media Manually to Your IBM i

This section describes a secure way to copy the required installation media from your Windows PC to your IBM i using OS version V7R2 and higher. To copy the media, you have to use a binary share TMPSAP. This guarantees that the content of the media is copied correctly from the Windows PC to your IBM i. No copied content is corrupted, and no copied files with longer file names are shortened by a converting share.

Note

This procedure should not be used on a V7R1 IBM i host. On V7R1, you must use an alternative method such as FTP.

Note

In the past, we suggested to create a binary share pointing to the root directory / on your IBM i host. We do not recommend this because it is not considered secure anymore.

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Preparation

C U S T O M E R

Procedure

Creating a Binary Share on IBM i

If you do not already have a binary share TMPSAP on your IBM i, and you want to copy manually media from your Windows PC into the IFS of your IBM i, you have to create this share manually using the IBM Systems

Director Navigator for i. To do so, proceed as follows:

1. Start the IBM Systems Director Navigator for i on your Windows PC.

2. Connect to your IBM i using

My Connections

3. To create or change the share TMPSAP, choose

File Systems File Shares

4. Right-click

File Shares Open i5/OS Netserver

A new screen

i5/OS Netserver

appears.

5. Click the folder

Shared Objects

to see the shares.

6. To check the already existing share TMPSAP or create a new share TMPSAP, right-click

New File

Note

The share TMPSAP must have the access permission

Read/Write

and the path name should be

/tmp/

SAP

If the directory /tmp/SAP does not exist directly create it manually as QSECOFR or installation user using the following command:

mkdir /tmp/SAP

7. On the

Text Conversion

tab, do not select

Allow file text conversion

8. To save the share TMPSAP, press

Now you have created the share TMPSAP on your IBM i.

Copying the Installation Media Manually Using the Binary Share TMPSAP

1. To open the command prompt on Windows, choose

Start Run

2. Enter

cmd.exe

3. Press

The command prompt appears.

4. In the command prompt, enter

net use

All network connections to shared resources are displayed.

5. Check if you have a connection to your IBM i.

If you find \\

<IBM_i_Host_Name> \TMPSAP in the

Remote

column and a drive directory letter in the

Local

column, you have already established the required connection to your IBM i.

Otherwise, you have to establish this connection. To do this, enter:

net use X: \\<IBM_i_Host_Name>\TMPSAP SAP /USER:SAPIUSR

X: is now your new network drive to share \\ <IBM_i_Host_Name> \TMPSAP to your IFS on the

IBM i. If X: is already in use, choose another drive letter that is free.

C U S T O M E R

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Preparation

Note

We use the user name SAPIUSR and the password SAP as examples. For more information about how

to create the installation user SAPIUSR, see Preparing an IBM i User Profile [page 43]

6. To change to the new network drive, enter

in the command prompt.

7. Create the subdirectories in your IFS where you want to copy the required media.

For each media, enter:

mkdir /tmp/sap/<SAPSID>/<Media_Name>

mkdir /tmp/sap/<SAPSID>/<Unpack_Directory>

Note

You must avoid blanks or commas in the media path name.

8. Copy the installation media from your Windows drive (for example D:\) or your download directory to the

IFS of your IBM i host by entering the following command:

xcopy D:\ X:\<SAPSID>\<Media_Name> /E

xcopy C:\tmp\download\<Unpack_Directory> X:\<SAPSID>\<Unpack_Directory> /E

Note

You must copy the root directory of the media respectively of the

<Unpack_Directory>

and all required subdirectories to the IFS of your IBM i.

9. For each required media, create a subdirectory and copy the required media.

Note

For advanced users only: Instead of copying the complete media you also can copy only dedicated subdirectories. For IBM i the following directories have to be copied:

● K_

<Version> _ <U or N> _OS400_PPC64

● JAVA*

● SL_CONTROLLER_

<nnn>

4.7 Preparing an IBM i User Profile

For running the installer you must create a user account on the IBM i host.

The following requirement applies:

● The IBM i installation user profile must have user class *SECOFR and all special authorities that belong to user QSECOFR.

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Preparation

C U S T O M E R

Procedure

Note

The user name SAPIUSR and the password SAP are used as examples in the procedures.

Enter the following command:

CRTUSRPRF USRPRF(SAPIUSR) PASSWORD(SAP) USRCLS(*SECOFR) TEXT('SAP installation user') SPCAUT(*USRCLS) OWNER(*USRPRF) LANGID(ENU) CNTRYID(US) CCSID(500)

LOCALE(*NONE)

SCM Only:

Caution

You should not set the system variable QIBM_PASE_CCSID. Do not leave this variable empty. Make sure that QIBM_PASE_CCSID is deleted at least for the time while you are installing your SAP system using the following command:

RMVENVVAR ENVVAR(QIBM_PASE_CCSID) LEVEL(*SYS)

Note

In previous releases, we recommended that you create the user SAPINST on IBM i to install the SAP system. In the current release, a group SAPINST is created generically on all platforms and is used for the installation of the SAP system. If the user SAPINST already exists on your system, you must delete this user. If you do not want to delete this user for any reason, you must add to the user profile SAPINST the feature of a group by adding SAPINST to the group of a different user profile such as SAPIUSR. To do this, use the following command:

CHGUSRPRF USRPRF(SAPIUSR) GRPPRF(SAPINST)

Now the user SAPINST can also be used as a group by the installer.

Note

If you have already an old installation user and you want to make sure this user is configured correctly for your next SAP system installation, call the following command:

CHGUSRPRF USRPRF(SAPIUSR) USRCLS(*SECOFR) TEXT('SAP installation user')

SPCAUT(*USRCLS) OWNER(*USRPRF) LANGID(ENU) CNTRYID(US) CCSID(500) LOCALE(*NONE)

Note

In a distributed environment, the installation user must have the same name and password on all hosts so that the required remote access permissions are available. For example, the profile directory on the global host should be accessible to the installation user of a remote additional application server instance.

C U S T O M E R

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Preparation

4.8 Enable the User QSECOFR

The user QSECOFR is the standard administrator user on IBM i. This user has the most authority. For running the installer on IBM i, the user QSECOFR must be enabled. Although for running the installer you only require the installation user, the SAP kernel tools on IBM i need some adopted permissions from the user QSECOFR. If the user QSECOFR is disabled this will lead to errors when SAP kernel tools such as CRTR3INST are called.

Procedure

1. To check the status of the user profile QSECOFR use the following command using your installation user:

DSPUSRPRF USRPRF(QSECOFR)

2. To enable the user QSECOFR use the following command using your installation user:

CHGUSRPRF USRPRF(QSECOFR) STATUS(*ENABLED)

Note

Recommendation

Check also if the password of the user QSECOFR is expired. To do this, login as QSECOFR. When the password is already expired you will be asked for a new password. Set a new password and the password of

QSECOFR is then no longer expired.

Only when the password of the QSECOFR is not expired the installation procedure will finish successfully.

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Preparation

C U S T O M E R

5 Splitting the Dual-Stack System

5.1 Splitting Checklist

This section includes the splitting steps that you have to perform for the following split options:

● “Move Java Database”

● “Keep Database”

Detailed information about the steps is available in the relevant section.

Note

Some of the required processing steps listed in this section are not described in this documentation. You can find the detailed description in the Java installation guide relevant for your database and operating system platform, which you can find at: https://help.sap.com/sltoolset

Area System Provisioning Guide for Installation of Systems Based on

SAP NetWeaver 7.1 and Higher Installation Guides by Database

Java

In the following, we refer to this documentation as “installation guide”.

Move Java Database

Central System

1. You

export the Java stack using the installer [page 51]

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 84] .

2. If AS Java has been disabled, you restart the source system.

3. You

run the installer [page 51] to install a Java only system

using the export from the dual-stack system.

C U S T O M E R

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Splitting the Dual-Stack System

Note

Make sure that you choose a system ID for the Java target system that is different from the dual-stack source system ID.

For a list of forbidden system IDs, see also the

help in the tool dialog.

4. You continue with Follow-Up Activities [page 70]

Distributed and High-Availability System

1. On the primary application server instance host of the dual-stack system, you check the prerequisites

[page 49]

and run the installer [page 51] to export the Java parts of the file system of the primary

application server instance.

Caution

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 84] .

2. If AS Java has been disabled, you restart the source system.

3. You merge the export directories of the database instance and of the central instance.

4. You

run the installer [page 51] 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

help in the tool dialog.

5. You

check the prerequisites [page 49]

and run the installer [page 51] to install a database instance for

the Java target system using the export from the dual-stack system.

6. You

check the prerequisites [page 49]

and run the installer [page 51] to install a primary application

server instance for the Java target system using the export from the dual-stack system.

7. You continue with Follow-Up Activities [page 70]

Keep Database

1. On the primary application server instance host of the dual-stack system, you check the prerequisites

[page 49]

and run the installer [page 51] to export the file system of the primary application server

instance.

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Splitting the Dual-Stack System

C U S T O M E R

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 will 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 84] .

2. If AS Java has been disabled, you restart the source system.

3. You

run the installer [page 51] 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

help in the tool dialog.

4. All databases except IBM DB2 for z/OS: On the database instance host of the dual-stack system, you

run the installer [page 51] 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 > General

Parameters

screen.

5. IBM DB2 for z/OS only: On the primary application server instance host of the dual-stack system, you

run the installer [page 51] 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 > General

Parameters

screen.

6. You

run the installer [page 51] to install a primary application

server instance for the Java target system using the export from the dual-stack system.

7. You continue with Follow-Up Activities [page 70]

C U S T O M E R

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Splitting the Dual-Stack System

5.2 Prerequisites for Running the Installer

Make sure you fulfil the following prerequisites before running the installer.

● If you want to use the SL Common GUI, make sure that the following web browser requirements are met:

○ You have one of the following supported browsers on the device where you want to run the SL

Common GUI: Google Chrome, Mozilla Firefox, Microsoft Edge, or Microsoft Internet Explorer 11.

Always use the latest version of these web browsers.

Recommendation

We recommend using Google Chrome.

○ If you copy the SL Common GUI URL manually in the browser window, make sure that you open a new

Web browser window in private browsing mode (Internet Explorer), incognito mode (Chrome) or private browsing mode (Firefox). This is to prevent Web browser plugins and settings from interfering with the SL Common GUI.

For more information about the SL Common GUI, see Useful Information About the Installer [page 57] .

● Make sure that you have logged on to your host as an installation user with similar authorization rights to

QSECOFR. For more information about how to create an installation user, see

Preparing an IBM i User

Profile [page 43]

● Check the value of the temporary directory set in the environment if available:

Table 6:

Shell Command

Command prompt

Qp2Term

WRKENVVAR echo $TEMP, echo $TMP or echo $TMPDIR

● Make sure that your operating system does not delete the contents of the temporary directory /tmp or the contents of the directories to which the variables TEMP, TMP, or TMPDIR point, for example by using a crontab entry.

● Each SAP instance requires a separate installation directory.

Recommendation

We recommend that you keep all installation directories until the system is completely and correctly installed.

● Make sure that you have at least 300 MB of free space in the installation directory for each installation option. In addition, you need 300 MB free space for the installer executables. If you cannot provide 300

MB free space in the temporary directory, you can set one of the environment variables TEMP, TMP, or

TMPDIR to another directory with 300 MB free space for the installer executables.

You can set values for the TEMP, TMP, or TMPDIR environment variable to an alternative installation

directory as described in section Useful Information About the Installer [page 57]

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Splitting the Dual-Stack System

C U S T O M E R

● The following information is only valid if you use the Java GUI:

Note

This is optional for advanced users.

Make sure that your DISPLAY environment variable is set to

<Host_Name>:0.0

, where

<Host_Name>

is the host on which you want to display the installer GUI.

You can set values for the DISPLAY environment variables as follows:

Table 7:

Shell Used Command

Command prompt

ADDENVVAR ENVVAR(DISPLAY) VALUE('<Host_Name>:

0.0') REPLACE(*YES)

Qp2Term

export DISPLAY=<Host_Name>:0.0

Note

When you leave your Qp2Term session, all changes of the environment variables done by the command export are reverted.

Note

For advanced users only:

PASE, which is similar to AIX, allows you to set the DISPLAY variable. If your X server for Microsoft

Windows or Linux is already configured and running, you can try to direct the graphical output of the installer to an XWindow by setting the DISPLAY variable. If this works, you do not have to use the remote installer GUI separately. We do not recommend that you start the installer using the DISPLAY variable as there is no support available.

Note

For advanced users only:

Beside using an XWindows Server and the DISPLAY variable, you can use VNC. For more information about VNC, see the IBM i documentation. VNC also offers a GUI by using IBM i tools. When VNC is prepared as described in the IBM i documentation, the installer GUI is directly started on your Windows

PC after starting the installer on IBM i.

● Make sure that the following ports are not used by other processes:

○ When using the SL Common GUI:

○ Port 4237 is used by default as HTTPS port for communication between the installer and the SL

Common GUI.

If this port cannot be used, you can assign a free port number by executing sapinst with the following command line parameter:

SAPINST_HTTPS_PORT=<Free Port Number>

C U S T O M E R

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Splitting the Dual-Stack System

Example

CD DIR('<Path_To_Unpack_Directory>')

CALL PGM(QP2TERM) PARM('./sapinst' 'SAPINST_HTTPS_PORT=<Free Port

Number>')

○ Port 4239 is used by default for displaying the feedback evaluation form at the end of the installer processing.

The filled-out evaluation form is then sent to SAP using HTTPS.

If this port cannot be used, you can assign a free port number by executing sapinst with the following command line parameter:

SAPINST_HTTP_PORT=<Free Port Number>

○ When using the Java SDT GUI:

○ Port 21212 is used by default for communication between the installer GUI server and the installer

GUI client.

If this port cannot be used, you can assign a free port number by executing sapinst with the following command line parameter:

SAPINST_DIALOG_PORT=<Free Port Number>

Example

CD DIR('<Path_To_Unpack_Directory>')

CALL PGM(QP2TERM) PARM('./sapinst' 'SAPINST_DIALOG_PORT=<Free Port

Number>')

○ Port 4239 is used by default for displaying the feedback evaluation form at the end of the installer processing.

The filled-out evaluation form is then sent to SAP using HTTPS.

If this port cannot be used, you can assign a free port number by executing sapinst with the following command line parameter:

SAPINST_HTTP_PORT=<Free Port Number>

● If you have changed the host name of your system, you also have to perform the steps described in sections

Configuring TCP/IP [page 25]

and

Adjusting the Relational Database Name [page 32] .

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

5.3 Running the Installer

This section describes how to run the installer to perform the dual-stack split .

Prerequisites

For more information, see Prerequisites for Running the Installer [page 49]

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Splitting the Dual-Stack System

C U S T O M E R

Context

Software Provisioning Manager (the “installer” for short) offers two GUIs:

● The new web browser-based “SL Common GUI of the Software Provisioning Manager” - “SL Common

GUI” for short

● The “classic” Java-based GUI with a CUI client and server - “Java SDT GUI” for short

Note

If the SL Common GUI does not meet your requirements you can still use the “classic” Java SDT GUI.

You then have to start the sapinst executable with the command line option

SAPINST_SLP_MODE=false

In cases where both GUIs behave the same way, we address them as “installer GUI”.

For more information, see Useful Information About the Installer [page 57] .

This procedure describes an installation where you use one of the following GUI scenarios:

● You run the installer and use the SL Common GUI. Then you can control the processing of the installer in the browser running on any device.

● You run the installer and use the Java SDT GUI. The installer is running on the installation host and the

Java SDT GUI on a Windows PC.

The following information is only valid if you use the Java SDT GUI:

● If you need to see the installation on a remote display, we recommend that you

perform a remote installation [page 61] , where the installer GUI is running on a separate host from the installer.

● Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote access to the installer GUI on Windows workstations. For more information, see SAP Note 1170809 .

Recommendation

The following information is only valid if you use the Java SDT GUI:

Since IBM i does not have GUI capabilities, we recommend that you perform a remote installation with the installer. You first have to start the installer without the installer GUI on the IBM i host using QP2TERM and then you have to start the installer GUI on the Windows installation host. Afterwards the installer behaves

the same as if started completely on one host. For more information, see Performing a Remote Installation

[page 61] and

Starting the Installer GUI Separately [page 63] . The remote installation is the default

installation option on IBM i. The section

Running the Installer

is used only for information.

However, the remote GUI display (using the DISPLAY environment variable) is possible, but this is considered an advanced user option.

Procedure

1. Log on to the host where you want to run the installer.

Make sure that you log on as a user with similar authorization rights to QSECOFR. For more information,

see Preparing an IBM i User Profile [page 43]

C U S T O M E R

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Splitting the Dual-Stack System

Caution

Make sure that the installation user has not set any environment variables for a different SAP system or database by using the command

WRKENVVAR

SL Common GUI only: If your security policy requires that the person running the installer is not allowed to know QSECOFR like credentials on the host where the installer is to perform the dual-stack split, you can specify another operating system user for authentication purposes. You do this using the

SAPINST_REMOTE_ACCESS_USER parameter when starting the sapinst executable from the command line. You have to confirm that the user is a trusted one. For more information, see SAP Note 1745524 .

2. Make the required media available.

For more information, see

Open the URL on a device with a supported web browser (see Prerequisites for Running the Installer

Recommendation

Make the installation media available locally . For example, if you use Network File System (NFS), reading from media mounted with NFS might fail.

3. Start the installer as follows:

Open a command prompt and enter the following command:

CD DIR('<Path_To_Unpack_Directory>')

CALL PGM(QP2TERM) PARM(’./sapinst’)

Note

If you want to use a virtual host name, start the installer with the installer property

SAPINST_USE_HOSTNAME as follows:

CALL PGM(QP2TERM) PARM(’./sapinst’ ’SAPINST_USE_HOSTNAME=<Virtual_Host_Name>')

Caution

Make sure that the installation directory is not mounted with NFS, or there might be problems when starting the Java Virtual Machine.

4. The installer is starting up.

Depending on the type of the installer GUI you want to use, do one of the following:

○ If you use the SL Common GUI, the installer now starts and waits for the connection with the SL

Common GUI.

You can find the URL you require to access the SL Common GUI at the bottom of the shell from which you are running the installer.

Sample Code

...

*************************************************************************

*******

Open your browser and paste the following URL address to access the GUI https://[ <hostname> ]:4237/sapinst/docs/index.html

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Splitting the Dual-Stack System

C U S T O M E R

Logon users: [ <users> ]

*************************************************************************

*******

...

[page 49] ).

The SL Common GUI opens in the browser by displaying the

Welcome

screen.

Note

Before you reach the

Welcome

screen, your browser might warn you that the certificate of the sapinst process on this computer could not be verified. Accept this warning to inform your browser that it can trust this site, even if the certificate could not be verified.

○ If you use the Java SDT GUI - that is you started the sapinst executable with command line option

SAPINST_SLP_MODE=false

, you still need to start the Java SDT GUI separately on a Windows PC to get the

Welcome

screen displayed. For more information, see Starting the Installer GUI Separately

[page 63]

5. In the

Welcome

screen, choose

Dual-Stack Split

<Database> <Keep Database | Move Java

Database> <Standard System|Distributed System|High-Availability System>

Perform the related dual-stack split options exactly in the order they appear.

6. Choose

Next

7. Follow the instructions in the installer input screens and enter the required parameters.

Note

To find more information on each parameter during the

Define Parameters

phase, position the cursor on the required parameter input field :

○ If you use the SL Common GUI, choose either

or the

HELP

tab. Then the available help text is displayed in the

HELP

tab.

○ If you use the Java SDT GUI, choose

. Then a dialog opens with the available help text.

Note

If the installer asks for the Java media, make sure that you provide a Java media with the same release level as your dual-stack system.

Caution

Whenever you are asked by the installer for the password of the user

<SAPSID> ADM on a remote IBM i host put also the UID number of the

<SAPSID> ADM into the input screen when it is not set already. You can get this number from the global host where the SCS or ASCS instance is already installed using following command:

DSPUSRPRF USRPRF(<SAPSID>ADM)

CALL PGM(QP2TERM) PARM('/QOpenSys/usr/bin/id' '<SAPSID>ADM')

The SCS or ASCS installation is the installation which initially determinates the UID of the user

<SAPSID> ADM.

C U S T O M E R

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Splitting the Dual-Stack System

Caution

The signature of media is checked automatically during the

Define Parameters

phase while processing the

Media Browser

screens.

Keep in mind that this automatic check is only committed once and not repeated if you modify artefacts such as SAR archives or files on the media after the initial check has been done - that is if you modify artefacts later on either during the remaining

Define Parameters

phase or later on during the

Execute Service

phase the signature is not checked again.

See also the description of this new security feature in SAP Note 2393060 .

8. After you have entered all requested input parameters, the installer displays the

Parameter Summary

screen. This screen shows both the parameters that you entered and those that the installer set by default.

If required, you can revise the parameters before starting the dual-stack split procedure.

9. To start the execution, choose

Next

The installer starts the split procedure and displays its progress on the

Task Progress

screen.

The installer starts the export and displays its progress of the system copy export during the processing phase.

When the dual-stack option has finished successfully, the installer displays the message

Execution of

<Split_Option>

has completed

10. If required, delete directories with the name sapinst_exe.xxxxxx.xxxx after the installer has finished.

Sometimes these remain in the temporary directory.

Note

If there are errors with the installer extraction process, you can find the log file dev_selfex.out in the temporary directory.

Recommendation

Keep all installer directories until you are sure that the system, including all instances, is completely and correctly installed. Once the system is completely and correctly installed, make a copy of the installer directories with all their contents. Save the copy to a physically separate medium, such as a medium or a USB drive that is separate from your installation hosts.

This might be useful for analyzing any issues that might occur later when using the system. For security reasons, do not keep the installer directories on hosts where you processed it, but make sure that you delete them after saving them separately.

11. If you copied installation media to your hard disk, you can delete these files when the installer has successfully completed.

Note

For more information about how to remove the installer files on IBM i, see

Removing the Installer

Installation Files [page 68] .

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Splitting the Dual-Stack System

C U S T O M E R

12. Java GUI only: For security reasons, we recommend that you delete the .sdtgui directory within the home directory of the user with which you ran the installer:

/home/ <Installation_User> /.stdgui

13. For security reasons, we recommend that you remove the group SAPINST from the operating system users after you have completed the installation.

Note

This step is only required, if you did not specify during the

Define Parameters

phase that the group

SAPINST is to be removed from the operating system users after the execution of the installer has completed.

Related Information

Useful Information About the Installer [page 57]

Interrupted Processing of the Installer [page 58]

Performing Remote Processing of the Installer (Java SDT GUI only) [page 61]

Running the Installer in Accessibility Mode [page 66]

Troubleshooting with the Installer [page 67]

5.4 Additional Information About the Installer

The following sections provide additional information about the installer.

Related Information

Useful Information About the Installer [page 57]

Interrupted Processing of the Installer [page 58]

Performing Remote Processing of the Installer (Java SDT GUI only) [page 61]

Running the Installer in Accessibility Mode [page 66]

Troubleshooting with the Installer [page 67]

Removing the Installer Installation Files [page 68]

C U S T O M E R

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Splitting the Dual-Stack System

5.4.1 Useful Information About the Installer

This section contains some useful technical background information about the installer and the installer GUI.

● Software Provisioning Manager (the installer) offers two GUIs:

○ The new web browser-based “SL Common GUI of the Software Provisioning Manager” - “SL Common

GUI” for short

○ The “classic” Java-based GUI with a CUI client and server - “Java SDT GUI” for short

The SL Common GUI of the Software Provisioning Manager (or “SL Common GUI” for short) uses the SAP

UI Development Toolkit for HTML5 - also known as SAPUI5 - a client-side HTML5 rendering library based on JavaScript. The benefits of this new user interface technology for the user are:

○ Zero foot print, since only a web browser is required on the client

○ New controls and functionality, for example, view logs in web browser.

The SL Common GUI connects the web browser on a client with the sapinst executable - which is part of

Software Provisioning Manager - running on the installation host using the standard protocol HTTPS.

For the SL Common GUI the installer provides a pre-generated URL at the bottom of the shell from which you are running the installer . If you have a supported web browser installed on the host where you run the installer, you can start the SL Common GUI directly from this URL. Otherwise, open a web browser supported by the SL Common GUI on any device and run the URL from there.

For more information about supported web browsers see

Prerequisites for Running the Installer [page

49]

If the SL Common GUI does not meet your requirements, you can still use the “classic” Java SDT GUI. To do so, you must start the sapinst executable with the command line option

SAPINST_SLP_MODE=false

You can switch back to the default installer GUI at any time with the following steps:

1. Stop the installer.

2. Restart the installer with command line option

SAPINST_SLP_MODE=false

3. On the

What do you want to do?

screen choose

Continue with the existing run

● The installer creates the installation directory sapinst_instdir directly below the temporary directory.

The installer finds the temporary directory by checking the value of the TEMP, TMP, or TMPDIR environment variable. If no value is set for these variables, the installer uses /tmp as default installation directory.

If you want to use an alternative installation directory, set the environment variable TEMP, TMP, or TMPDIR to the required directory before you start the installer.

Table 8:

Shell Used Command

Command prompt

ADDENVVAR ENVVAR(TEMP) VALUE('<Directory>')

REPLACE(*YES)

Qp2Term

export TEMP=<Directory>

Note

When you leave your Qp2Term session, all changes of the environment variables done by the command export are reverted.

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Splitting the Dual-Stack System

C U S T O M E R

Caution

Make sure that the installation directory is not mounted with NFS, otherwise there might be problems when the Java Virtual Machine is started.

● For each option, the installer creates a subdirectory located in the sapinst_instdir directory.

● The installer extracts itself to the temporary directory. These executables are deleted again after the installer has stopped running.

Directories called sapinst_exe.xxxxxx.xxxx sometimes remain in the temporary directory. You can safely delete them.

The temporary directory also contains the log file dev_selfex.out from the extraction process, which might be useful if an error occurs.

Caution

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

● To see a list of all available installer properties, enter the following commands:

CD DIR('<Path_To_Unpack_Directory>')

CALL PGM(QP2TERM) PARM('./sapinst' '-p')

● This information is only relevant if you use the Java GUI of the installer: If you need to run the installer in accessibility mode, proceed as described in

Running the Installer in Accessibility Mode [page 66]

● If required, stop the installer by choosing one of the following, depending on the installer GUI you use:

○ In the SL Common GUI, choose the

Cancel

button.

○ In the Java SDT GUI, choose

SAPinst Exit Process

in the installer Java SDT GUI menu on your

Windows PC..

Note

If you need to terminate the installer, press

Shift

Esc

then

on your IBM i host.

5.4.2 Interrupted Processing of the Installer

Here you find information about how to restart the installer if its processing has been interrupted.

Context

The processing of the installer might be interrupted for one of the following reasons:

● An error occurred during the

Define Parameters

Execute

phase:

The installer does not abort the installation in error situations. If an error occurs, the installation pauses and a dialog box appears. The dialog box contains a short description of the choices listed in the table below as well as a path to a log file that contains detailed information about the error.

C U S T O M E R

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Splitting the Dual-Stack System

● You interrupted the installation by choosing

○

Cancel

in the SL Common GUI

○

Exit Process

in the

SAPinst

menu in the Java SDT GUI

Caution

If you stop an option in the

Execute

phase, any system or component installed by this option is incomplete and not ready to be used. Any system or component uninstalled by this option is not completely uninstalled.

The following table describes the options in the dialog box:

Table 9:

Option Definition

Retry

Stop

Continue

View Log

The installer retries the installation from the point of failure without repeating any of the previous steps.

This is possible because the installer records the installation progress in the keydb.xml file.

We recommend that you view the entries in the log files, try to solve the problem, and then choose

Retry

If the same or a different error occurs, the installer displays the same dialog box again.

The installer stops the installation, closing the dialog box, the installer GUI, and the

GUI server.

The installer records the installation progress in the keydb.xml file. Therefore, you can continue the installation from the point of failure without repeating any of the previous steps. See the procedure below.

The installer continues the installation from the current point.

Access installation log files.

The following procedure describes the steps to restart an installation, which you stopped by choosing

Stop

, or to continue an interrupted installation after an error situation.

Procedure

1. Log on to the installation host as a user with the required permissions as described in Running the Installer

[page 51]

2. Make sure that the media required for the dual-stack split are still available.

For more information, see

Open the URL on a device with a supported web browser (see Prerequisites for Running the Installer

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Splitting the Dual-Stack System

C U S T O M E R

Recommendation

Make the installation media available locally. For example, if you use remote file shares on other

Windows hosts, CIFS shares on third-party SMB-servers, or Network File System (NFS), reading from media mounted with NFS might fail.

3. Restart the installer from the installation media directory to which you unpacked the Software

Provisioning Manager archive.

Enter the following commands:

CD DIR('<Path_To_Unpack_Directory>')

CALL PGM(QP2TERM) PARM('./sapinst')

4. The installer is restarting.

Depending on the type of the installer GUI you want to use, do one of the following:

○ If you use the SL Common GUI, the installer now starts and waits for the connection with the SL

Common GUI.

You can find the URL you require to access the SL Common GUI at the bottom of the shell from which you are running the installer.

Sample Code

...

*************************************************************************

*******

Open your browser and paste the following URL address to access the GUI https://[ <hostname> ]:4237/sapinst/docs/index.html

Logon users: [ <users> ]

*************************************************************************

*******

...

[page 49] ).

The SL Common GUI opens in the browser by displaying the

Welcome

screen.

Note

Before you reach the

Welcome

○ If you use the Java SDT GUI - that is you started the sapinst executable with command line option

SAPINST_SLP_MODE=false

, you still need to start the Java SDT GUI separately on a Windows PC to get the

Welcome

screen displayed. For more information, see Starting the Installer GUI Separately

[page 63]

5. From the tree structure on the

Welcome

screen, select the installation option that you want to continue and choose

Next

The

What do you want to do?

screen appears.

6. On the

What do you want to do?

screen, decide between the following alternatives and continue with

Next

C U S T O M E R

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Splitting the Dual-Stack System

Table 10:

Alternative

Perform a new run

Continue with the existing one

Behavior

The installer does not continue the interrupted dual-stack split option. Instead, it moves the content of the old installer directory and all installer-specific files to a backup directory. Afterwards, you can no longer continue the old option.

The following naming convention is used for the backup directory: log_ <Day> _ <Month> _ <Year> _ <Hours> _ <Minutes> _ <Seconds>

Example log_01_Oct_2016_13_47_56

Note

All actions taken by the dual-stack split before you stopped it (such as cre ating directories or users) are not revoked.

Caution

The installer moves all the files and folders to a new log directory, even if these files and folders are owned by other users. If there are any processes currently running on these files and folders, they might no longer function properly.

The installer continues the interrupted dual-stack split from the point of failure.

5.4.3 Performing Remote Processing of the Installer (Java

SDT GUI only)

Here you find information about how to process the installer on a remote host.

Note

This section is only valid if you use the Java SDT GUI. That is, you started the sapinst executable with command line option

SAPINST_SLP_MODE=false

Prerequisites

● The remote host meets the prerequisites for starting the installer as described in

Prerequisites for

Running the Installer [page 49] .

● Both computers are in the same network and can ping each other.

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Splitting the Dual-Stack System

C U S T O M E R

To test this:

1. Log on to your remote host (IBM i) and enter the command:

PING RMTSYS('<Local_Host>')

2. Log on to the local host (Windows PC) and enter the command:

ping <Remote_Host>

● If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER command line parameter, make sure that this user exists on the remote host and that this user owns an existing home directory on IBM i (/home/

<User_Name>

Context

You use this procedure to process the installer on a remote host. In this case, the installer runs on the remote host, and the installer GUI runs on the local host. The local host is the host from which you control the installation with the installer GUI. The installer GUI connects using a secure SSL connection to the installer.

If your security policy requires that the person performing the installation by running the installer GUI on the local host is not allowed to know QSECOFR like credentials on the remote host, you can specify another operating system user for authentication purposes. You do this using the SAPINST_REMOTE_ACCESS_USER parameter when starting the sapinst executable from the command line. You have to confirm that the user is a trusted one. For more information, see SAP Note 1745524 .

Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote access to the installer GUI on Windows workstations. For more information, see SAP Note 1170809 .

Caution

In this section, “local host” refers to the Windows installation host, and “remote host” refers to the IBM i host where the SAP system is installed.

Procedure

1. Log on to the remote host as the installation user with similar authorization rights to QSECOFR. For more

information, see Preparing an IBM i User Profile [page 43]

Caution

Make sure that the installation user has not set any environment variables for a different SAP system or database by using the command

WRKENVVAR

2. Make the installation media available on your remote host.

For more information, see

Starting the Installer GUI Separately [page 63] ).

Recommendation

Make the installation media available locally . For example, if you use Network File System (NFS), reading from media mounted with NFS might fail.

C U S T O M E R

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Splitting the Dual-Stack System

3. Open a command prompt and change to the directory to which you unpacked the Software Provisioning

Manager archive.

4. Check the version of the sapinst executable by entering the following command:

CD DIR('<Path_To_Unpack_Directory>')

CALL PGM(QP2TERM) PARM('./sapinst' '-sfxver')

The version of the sapinst executable must be exactly the same as the version of the sapinstgui executable on the local host (see also

5. Start the installer by entering the following command:

CD DIR('<Path_To_Unpack_Directory>')

CALL PGM(QP2TERM) PARM('./sapinst')

Note

If you need to specify another operating system user for authentication purposes, this command is as follows:

CALL PGM(QP2TERM) PARM('./sapinst'

'SAPINST_REMOTE_ACCESS_USER=<Specified_OS_User>')

The installer now starts and waits for the connection to the installer GUI. You see the following at the command prompt: guiengine: no GUI connected; waiting for a connection on host <Host_Name> , port

<Port_Number> to continue with the installation

6. There is no GUI on IBM i, so you do not see the installer

Welcome

screen. As a default, you must start the installer GUI separately on a Windows operating system . For more information, see

Starting the Installer

GUI Separately [page 63]

5.4.4 Starting the Java SDT GUI Separately

Here you find information about how to start the Java SDT GUI separately.

Note

This section is only valid if you use the Java SDT GUI. That is, you started the sapinst executable with command line option

SAPINST_SLP_MODE=false

Prerequisites

The host on which you want to start the installer GUI meets the prerequisites for starting the installer as described in

Prerequisites for Running the Installer [page 49] .

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Splitting the Dual-Stack System

C U S T O M E R

Note

If you want to run the installer on a Windows host, make sure that you meet the prerequisites for the installer listed in the relevant Windows guide.

Context

You might need to start the installer GUI separately in the following cases:

● You are running IBM i and did not set a DISPLAY environment variable.

● You closed the installer GUI using

File Close GUI only

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 Remote Processing of the Installer (Java SDT GUI only)

[page 61] .

● You want to run the installer in accessibility mode. In this case, you have to start the installer GUI separately on a Windows host as described below with the command line parameter

-accessible

For more information, see

Running the Installer in Accessibility Mode [page 66] .

Caution

This is the default on IBM i. Since there is no GUI on IBM i, you must start the installer GUI separately.

In the this procedure, the following variables are used:

<Remote_Host>

is the name of the remote host, and

<Port_Number_Gui_Server_To_Gui_Client>

is the port the GUI server uses to communicate with the GUI client (21212 by default).

Procedure

● Starting the Installer GUI on Windows a. Make the installer software available on the host on which you want to start the installer GUI.

For more information, see Preparing the Dual-Stack Split Media [page 34] .

b. Start the installer GUI by executing the sapinstgui executable with the appropriate command line parameters:

Note

If you start the installer GUI executable on Windows 7 or Windows 2008, you must use the option

Run as administrator

. Typically, you first start a command prompt using

Run as administrator

. Then in this command prompt, you enter the installer GUI command.

C U S T O M E R

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Splitting the Dual-Stack System

Note

If you have a share TMPSAP on your IBM i and you have mapped this share to the drive for example

X, you can start the installer GUI using your copied unpack directory:

X:\ <SAPSID> \ <Unpack_Directory>

For more information, see

Copying the Installation Media Manually to Your IBM i [page 41] .

By default the Windows sapinstgui.exe is part of the Software Provisioning Manager archive for

IBM i. Only when the file sapinstgui.exe is missing, you must download the Software

Provisioning Manager archive for Windows.

○ If you want to perform a remote installation, proceed as follows:

1. Check the version of sapinstgui.exe by entering the following command:

<Path_To_Unpack_Directory>\sapinstgui.exe -sfxver

The version of the sapinstgui executable must be exactly the same as the version of the sapinst executable on the remote host (see also

Performing a Remote Installation [page

61] ).

2. Start the installer GUI by entering the following command:

<Path_To_Unpack_Directory>\sapinstgui.exe -host <Remote_Host> -port

<Port_Number_Gui_Server_To_Gui_Client>

○ If you closed the installer GUI using

File Close GUI only

and want to reconnect to the installer, proceed as follows:

1. If you are performing a local installation with the installer and the installer GUI running on the same host, execute the following command:

<Path_To_Unpack_Directory>\sapinstgui.exe -port

<Port_Number_Gui_Server_To_Gui_Client>

2. If you are performing a remote installation with the installer and the installer GUI running on different hosts, execute the following command:

<Path_To_Unpack_Directory>\sapinstgui.exe -host <Remote_Host> -port

<Port_Number_Gui_Server_To_Gui_Client>

c. The installer GUI starts and connects to the installer.

● Starting the Installer GUI on UNIX a. Make the installer software available on the host on which you want to start the installer GUI.

For more information, see Preparing the Dual-Stack Split Media [page 34] .

b. Start the installer GUI by executing the sapinstgui executable with the appropriate command line parameters:

○ If you want to perform a remote installation, proceed as follows:

1. Check the version of the sapinstgui executable by entering the following command:

<Path_To_Unpack_Directory>/sapinstgui -sfxver

The version of the sapinstgui executable must be exactly the same as the version of the sapinst executable on the remote host (see also

Performing a Remote Installation [page

61] ).

2. Start the installer GUI by entering the following command:

<Path_To_Unpack_Directory>/sapinstgui -host <Remote_Host> -port

<Port_Number_Gui_Server_To_Gui_Client>

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Splitting the Dual-Stack System

C U S T O M E R

○ If you closed the installer GUI using

File Close GUI only

and want to reconnect to the installer, proceed as follows:

1. If you are performing a local installation with the installer and the installer GUI running on the same host, execute the following command:

<Path_To_Unpack_Directory>/sapinstgui -port

<Port_Number_Gui_Server_To_Gui_Client>

2. If you are performing a remote installation with the installer and the installer GUI running on different hosts, execute the following command:

<Path_To_Unpack_Directory>/sapinstgui -host <Remote_Host> -port

<Port_Number_Gui_Server_To_Gui_Client>

c. The installer GUI starts and connects to the installer.

5.4.5 Running the Installer in Accessibility Mode

You can also run the installer in accessibility mode.

Note

The information contained in this section is only valid if you use the Java SDT GUI. That is, you started the sapinst executable with command line option

SAPINST_SLP_MODE=false

If you use the SL Common GUI, apply the standard accessibility functions of your web browser.

Context

The following features are available:

● Keyboard access:

This feature is generally available for all operating systems.

● High-contrast color:

This feature is derived from the Windows display properties. Therefore, to enable this feature, perform a remote installation with the installer GUI running on a Windows host.

● Custom font setting:

This feature is derived from the Windows display properties. Therefore, to enable this feature, perform a remote installation with the installer GUI running on a Windows host.

Procedure

● Activating and Adjusting Accessibility Settings on Windows

You first have to activate and adjust the relevant settings for the font size and color schemes before you start the installer or the installer GUI.

C U S T O M E R

Dual-Stack Split for SAP Systems Based on SAP NetWeaver 7.1 to 7.5 on IBM i

Splitting the Dual-Stack System

Note

The following procedure applies for Windows Server 2012 and might be different when using another

Windows operating system.

a. Right click on your Windows desktop and choose

Personalize

b. Select

Adjust font size (DPI)

and choose

Larger scale (120 DPI)

To define other font size schemes, choose

Custom DPI

c. In the right-hand pane, select

Window Color and Appearance

Select a color scheme from the

Color scheme

drop-down box.

To define your own color schemes, choose

Advanced

● Running the Installer in Accessibility Mode a. Start the installer on the remote host by executing the following command from the command line as described in

Performing Remote Processing of the Installer (Java SDT GUI only) [page 61]

<Path_To_Unpack_Directory>/sapinst

b. Start the installer GUI on a local Windows host by executing the following command from the command line as described in

Performing Remote Processing of the Installer (Java SDT GUI only) [page 61]

<Path_To_Unpack_Directory>\sapinstgui.exe -accessible -host <Remote_Host> port <Port_Number_Gui_Server_To_Gui_Client>

You perform a remote installation as follows: a. Start the installer on the remote IBM i host by executing the following command from the command line as described in

CD DIR('<Path_To_Unpack_Directory>')

CALL PGM(QP2TERM) PARM('./sapinst')

b. Start the installer GUI on a local Windows host by executing the following command from the command line as described in