Installation Guide | PUBLIC

Software Provisioning Manager 1.0 SP42

Document Version: 4.3 – 2024-10-07

Installation of a Standalone SAP Gateway

Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
© 2024 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN

Content

1 About this Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1.1 About Software Provisioning Manager 1.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2 New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.3 SAP Notes for the Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
1.4 Accessing the SAP Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.5 Naming Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2 Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.1 Hardware and Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Hardware and Software Requirements Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Installing English as a Secondary Language. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.2 Basic Installation Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3 Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.1 Checking and Adjusting Operating System Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.2 Adding a User ASP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.3 SAP Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.4 Using Virtual Host Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.5 Preparing the SAP Installation User onIBM i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.6 Enable the User QSECOFR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
3.7 Preparing the Installation Media. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
Downloading and Extracting the Software Provisioning Manager 1.0 Archive. . . . . . . . . . . . . . . . 30
Using the Physical Media from the Installation Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Downloading Complete Installation Media. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Copying the Installation Media Manually to Your IBM i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

4 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.1 Prerequisites for Running Software Provisioning Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.2 Running Software Provisioning Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4.3 Additional Information about Software Provisioning Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Useful Information About Software Provisioning Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Restarting Interrupted Processing of Software Provisioning Manager. . . . . . . . . . . . . . . . . . . . . 45
Troubleshooting with Software Provisioning Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Using the Step State Editor (SAP Support Experts Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

5 Post-Installation Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
5.1 Ensuring User Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
5.2 Gateway Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
2 PUBLIC Content
6 Additional Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
6.1 Using Virtual Host Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
6.2 Starting and Stopping the Instance Using Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
6.3 Uninstalling the Gateway Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
Content PUBLIC 3
Document History

 Note

Before you start reading, make sure you have the latest version of this installation guide, which
is available at https://support.sap.com/sltoolset System Provisioning Install a System using
Software Provisioning Manager Installation Option of Software Provisioning Manager 1.0 .

The following table provides an overview on the most important document changes:

Version Date Description

4.3 2024-10-07 Updated version for Software Provision-

ing Manager 1.0 SP42 (SL Toolset 1.0
SP42)

4.2 2024-05-27 Updated version for Software Provision-

ing Manager 1.0 SP41 (SL Toolset 1.0
SP41)

4.1 2024-02-12 Updated version for Software Provision-

ing Manager 1.0 SP40 (SL Toolset 1.0
SP40)

4.0 2023-10-09 Updated version for Software Provision-

ing Manager 1.0 SP39 (SL Toolset 1.0
SP39)

Windows operating systems no longer

supported for software provisioning
manager 1.0 SP39 and higher, accord-
ing to SAP Note 2998013 , have been
removed.

3.9.1 2023-10-09 Updated version for software provision-

ing manager 1.0 SP38 (SL Toolset 1.0
SP38): Last version containing informa-
tion about no longer supported Win-
dows operating systems according to
SAP Note 3346502 .

3.9 2023-05-26 Updated version for Software Provision-

ing Manager 1.0 SP38 (SL Toolset 1.0
SP38)

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
4 PUBLIC Document History
 Version Date Description

3.8 2023-02-13 Updated version for Software Provision-

ing Manager 1.0 SP37 (SL Toolset 1.0
SP37)

3.7 2022-10-10 Updated version for Software Provision-

ing Manager 1.0 SP36 (SL Toolset 1.0
SP36)

Operating systems and CPU architec-

tures no longer supported according
to SAP Note 2998013 have been re-
moved.

3.6.1 2022-10-10 Updated version for software provision-

ing manager 1.0 SP35 (SL Toolset 1.0
SP35): Last version containing informa-
tion about no longer supported operat-
ing systems and CPU architectures ac-
cording to SAP Note 2998013 .

3.6 2022-05-24 Updated version for Software Provision-

ing Manager 1.0 SP35 (SL Toolset 1.0
SP35)

3.5 2022-02-14 Updated version for Software Provision-

ing Manager 1.0 SP34 (SL Toolset 1.0
SP34)

3.4 2021-10-11 Updated version for Software Provision-

ing Manager 1.0 SP33 (SL Toolset 1.0
SP33)

3.3 2021-06-21 Updated version for Software Provision-

ing Manager 1.0 SP32 (SL Toolset 1.0
SP32)

3.2 2021-02-15 Updated version for Software Provision-

ing Manager 1.0 SP31 (SL Toolset 1.0
SP31)

3.1 2020-10-05 Updated version for Software Provision-

ing Manager 1.0 SP30 (SL Toolset 1.0
SP30)

3.0 2020-06-08 Updated version for Software Provision-

ing Manager 1.0 SP29 (SL Toolset 1.0
SP29)

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
Document History PUBLIC 5
Version Date Description

2.9 2020-01-20 Updated version for Software Provision-

ing Manager 1.0 SP28 (SL Toolset 1.0
SP28)

2.8 2019-09-16 Updated version for Software Provision-

ing Manager 1.0 SP27 (SL Toolset 1.0
SP27)

2.7 2019-05-27 Updated version for Software Provision-

ing Manager 1.0 SP26 (SL Toolset 1.0
SP26)

2.6 2019-01-21 Updated version for software provision-

ing manager 1.0 SP25 (SL Toolset 1.0
SP25)

2.5 2018-09-17 Updated version for software provision-

ing manager 1.0 SP24 (SL Toolset 1.0
SP24)

• New Features
• New Look and Feel of SL Com-
mon GUI with Software Pro-
visioning Manager 1.0 SP24,
Patch Level 05, documented
in: New Features, Prerequisites
for Running the Software Pro-
visioning Manager

2.4 2017-05-22 Updated version for software provision-

ing manager 1.0 SP20 (SL Toolset 1.0
SP20)

2.3 2017-02-06 Updated version for software provision-

ing manager 1.0 SP19 (SL Toolset 1.0
SP19)

• New Features:
Verification of the integrity of data
units in Software Provisioning Man-
ager, documented in: Downloading
the Software Provisioning Manager
Archive

2.2 2016-10-07 Updated version for software provision-

ing manager 1.0 SP18 (SL Toolset 1.0
SP18)

2.1 2016-06-06 Updated version for software provision-

ing manager 1.0 SP17 (SL Toolset 1.0
SP17)

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
6 PUBLIC Document History
 Version Date Description

2.0 2016-02-15 Updated version for software provision-

ing manager 1.0 SP10 (SL Toolset 1.0
SP16)

1.9 2015-10-12 Updated version for software provision-

ing manager 1.0 SP09 (SL Toolset 1.0
SP15)

1.8 2015-09-14 Updated version for software provision-

ing manager 1.0 SP09 (SL Toolset 1.0
SP14)

1.7 2015-04-27 Updated version for software provision-

ing manager 1.0 SP08 (SL Toolset 1.0
SP13)

1.6 2014-11-24 Updated version for software provision-

ing manager 1.0 SP07 (SL Toolset 1.0
SP12)

1.5 2014-07-07 Updated version for software provision-

ing manager 1.0 SP06 (SL Toolset 1.0
SP11)

1.4 2014-03-17 Updated version for software provision-

ing manager 1.0 SP09 (SL Toolset 1.0
SP10)

1.3 2013-10-28 Updated version

1.2 2013-07-15 Updated version

1.1 2013-04-12 Updated version

1.0 2012-12-17 Initial version

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
Document History PUBLIC 7
1 About this Document

This installation guide describes how to install a standalone Gateway for SAP systems based on SAP
NetWeaver using the software provisioning manager 1.0 SP42, which is part of SL Toolset 1.0 SP42.

You can find a complete list of supported SAP system products in SAP Note 1680045 .

Each instance of an SAP system with AS ABAP has a Gateway. The Gateway enables communication between
work processes and external programs, as well as communication between work processes from different
instances of SAP systems.

With a standalone Gateway, you can install the Gateway service separately from the SAP system. In this case,
the SAP system can access each external Gateway under a different Remote Function Call (RFC) connection.

 Note

There is no difference between a standalone Gateway instance for a Unicode system and a standalone
Gateway for a non-Unicode system.

1.1 About Software Provisioning Manager 1.0

The software provisioning manager 1.0 is the successor of the product- and release-specific delivery of
provisioning tools, such as “SAPinst”. We strongly recommend that you always download the latest version of
the software provisioning manager 1.0. The software provisioning manager 1.0 is part of the Software Logistics
Toolset 1.0 (“SL Toolset” for short). This way, you automatically get the latest fixes and supported processes.
For more information about the software provisioning manager as well as products and releases supported by
it, see SAP Note 1680045 and http://scn.sap.com/docs/DOC-30236 .

“SAPinst” has been renamed to “software provisioning manager” in this documentation, but the terms
“SAPinst” and “sapinst” are still used in:

• The name of the technical framework of the software provisioning manager. For more information about
the SAPinst Framework, see SAP Note 2393060 .
• Texts and screen elements in the the software provisioning manager GUI (SL Common GUI)
• Names of executables, for example sapinst
• Names of command line parameters, for example SAPINST_HTTPS_PORT
• Names of operating system user groups, such as the additional group sapinst

In the following, we generally refer to the software provisioning manager 1.0 as the “software provisioning
manager”. We only use the term “software provisioning manager 1.0” if this is required for technical reasons.

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
8 PUBLIC About this Document
Related Information

Preparing the Installation Media [page 30]

1.2 New Features

This section provides an overview of the new features in the software provisioning manager 1.0.

Make sure that you also read the Release Notes for your SAP product at https://help.sap.com <Search
your SAP Product> <Select your SAP Product Version> What’s New .

Feature Description Availability

New SAPinst Frame- The SAPinst framework patch level has been upgraded from version 749 (SAP software provision-
work Version 753 Note 2393060 SAPinst Framework 749 Central Note) to 753. For more infor- ing manager 1.0
mation, see SAP Note 3207613 SAPinst Framework 753 Central Note. SP36 (SL Toolset
1.0 SP36)

Software Provisioning The new OS release IBM i 7.5 is certified for SAP Solutions since May 30, 2022. Software Provi-
Manager on IBM i For more information, see the SAP on IBM i blog entry "SAP on IBM i: IBM i 7.5 sioning Manager
now supports the Certified for SAP Solutions ". In addition, see SAP Note 1680045 , section 1.0 SP35 (SL Tool-
new OS release IBM i Planning and Preparation : SAP System Installation on OS release IBM i V7R5. set 1.0 SP35)
7.5

SAP Rename for SAP The SAP Rename for IBM i now supports SAP systems installed on the IASP. Software Provi-
systems installed on For more information, see the SAP Rename guide for IBM i. In the past, the sioning Manager
the independent aux- SAP System Copy had to be used to rename a system located on the IASP. 1.0 SP29 (SL Tool-
iliary storage pool set 1.0 SP29)
(IASP).

New Look and Feel of As of version 1.0 SP24 Patch Level (PL) 5, the software provisioning man- Software Provi-
SL-UI ager comes with a new look and feel of the SL-UI. For more informa- sioning Manager
tion, see https://blogs.sap.com/2018/11/10/new-look-for-software-provision- 1.0 SP24, PL05 (SL
ing-manager/ . Toolset 1.0 SP24)

Software Provisioning The software provisioning manager log files are now available immediately Software Provi-
Manager Log Files after the software provisioning manager has been started, that is before a sioning Manager
Improvements product has been selected on the Welcome screen. For more information, 1.0 SP22 (SL Tool-
see Useful Information About Software Provisioning Manager [page 43] and set 1.0 SP22)
Troubleshooting with Software Provisioning Manager [page 48].

Media Signature The digital signature of media is checked automatically by the software pro- Software Provi-
sioning Manager
Check visioning manager during the Define Parameters phase while processing the
1.0 SP21 (SL Tool-
Media Browser screens. The software provisioning manager only accepts me-
set 1.0 SP21)
dia whose digital signature has been checked.

For more information, see Preparing the Installation Media [page 30] and
Running Software Provisioning Manager [page 39].

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
About this Document PUBLIC 9
Feature Description Availability

SL-UI with SAPINST With the new software provisioning manager framework version SAPINST 7.49, Software Provi-
7.49 you can now use the new SAPUI5-based graphical user interface (GUI) “SL- sioning Manager
UI”. For more information, see Useful Information About Software Provisioning 1.0 SP20 (SL Tool-
Manager [page 43], Running Software Provisioning Manager [page 39] . set 1.0 SP20)

Cleanup of Operating You can now specify during the Define Parameters phase that the group Software Provi-
System Users sioning Manager
SAPINST is to be removed from the operating system users after the execu-
1.0 SP20 (SL Tool-
tion of the software provisioning manager has completed.
set 1.0 SP20)
For more information, see Operating System Users in Basic Installation Param-
eters [page 17].

Verification of Integ- The integrity of data units extracted from the Software Provisioning Manager Software Provi-
rity of Data Units in sioning Manager
archive is verified. For more information, see Downloading and Extracting the
Software Provisioning 1.0 SP19 (SL Tool-
Software Provisioning Manager 1.0 Archive [page 30].
Manager set 1.0 SP19)

In addition, check SAP Note 1680045 whether additional information is

available.

Diagnostics Agent The Diagnostics Agent is no longer installed automatically with the SAP sys- Software Provi-
tem. The Install Diagnostics Agent check box on the Install Diagnostics Agent sioning Manager
screen is no longer available. 1.0 SP10 (SL Tool-
set 1.0 SP16)
You now have to install the Diagnostics Agent always separately. We recom-
mend that you install it prior to the installation of your SAP system(s).

For more information, see the Diagnostics Agent Installation Strategy at-
tached to SAP Note 1365123 , to SAP Note 1833501 , and to SAP Note
1858920 and the attached Diagnostics Agent Setup Guide.

Feedback Evaluation SAP SE’s aim is to provide fast and efficient procedures. To evaluate the proce- Software Provi-
Form available in the dure you just carried out, we need information generated by the tool during sioning Manager
Software Provisioning process execution and your experience with the tool itself. A new evaluation 1.0 SP07 (SL Tool-
Manager: form contains a simple questionnaire and XML data generated during the set 1.0 SP12)
procedure.

Port 4239 is used for displaying the feedback evaluation form. For more
information, see the Prerequisites section in Running Software Provisioning
Manager [page 39].

1.3 SAP Notes for the Installation

You must read the following SAP Notes before you start the installation. These SAP Notes contain the most
recent information on the installation, as well as corrections to the installation documentation.

Make sure that you have the up-to-date version of each SAP Note which you can find at https://
support.sap.com/notes .

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
10 PUBLIC About this Document
SAP Notes for the Installation

SAP Note Number Title Description

1680045 Release Note for Software Provisioning Remarks, annotations, and corrections
Manager 1.0 discovered after publication of the docu-
mentation Software Provisioning Manager

893876 IBM i: Creating a Gateway Instance Additional Information about standalone

Gateway installation on IBM i

1.4 Accessing the SAP Library

The references to SAP NetWeaver Library documentation in this installation guide always refer to the following
on SAP Help Portal:

Product and Release SAP Library Path

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 in- http://help.sap.com/nw731 Application Help Function-Oriented
cluding Enhancement Package 1
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

1.5 Naming Conventions

In this documentation, the following naming conventions apply:

 Note

From a technical point of view, the standalone Gateway is set up like an SAP system with its own SAP
system ID (SAPSID), its own operating system users, and its own directory structure.

• SAP system refers to standalone gateway.

• instance refers to astandalone gateway instance.

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
About this Document PUBLIC 11
2 Planning

2.1 Hardware and Software Requirements

You check that your hosts meet the hardware and software requirements for your operating system and the
Gateway instance.

 Caution

If your hosts do not fully meet the requirements, you might experience problems when working with the
SAP system.

Process Flow

1. Check the Product Availability Matrix at https://apps.support.sap.com/sap/support/pam for supported

operating system releases.
2. Check the hardware and software requirements table for the Gateway Instance [page 12].
3. If you want to use the standalone Gateway for a production system, the values provided by the
Prerequisite Checker and the hardware and software requirements checklists are not sufficient. In addition,
do the following:
• You use the hardware sizing information available at https://sap.com/sizing .
• You contact your hardware vendor, who can analyze the load and calculate suitable hardware sizing
depending on:
• The set of applications to be deployed
• How intensively the applications are to be used
• The number of users

2.1.1 Hardware and Software Requirements Tables

The standalone Gateway host must meet the following requirements:

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
12 PUBLIC Planning
Hardware Requirements

Requirement Values and Activities

Processing units For application server instances and database instances: The number or physical or virtual
processing units usable by the operating system image must be equal to or greater than 2.

Examples of processing units are processor cores or hardware threads (multithreading).

In a virtualized environment, ensure that adequate processor resources are available to sup-
port the workloads of the running SAP systems.

Hard disk space • General requirements:

• 4.3 GB of temporary disk space for every required installation medium that you have
to copy to a local hard disk. For more information, see Preparing the Installation
Media [page 30].
• 1.2 GB of temporary disk space for the installation.
• If an advanced disk array is available (for example, RAID), contact your hardware
vendor to make sure that the data security requirements are covered by this tech-
nology.
• Instance-specific requirements:
1 GB of hard disk space.

RAM 8 GB RAM

RAM 8 GB RAM

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
Planning PUBLIC 13
Software Requirements

Requirement Values and Activities

Operating System Requirements The SAP products based on SAP NetWeaver 7.0 SR3, SAP NetWeaver 7.0
EHP1, SAP NetWeaver 7.0 EHP2, and SAP NetWeaver 7.0 EHP3 are released for
V7R2,V7R3,V7R4, and V7R5.

For information about which operating system versions have been released
for SAP on IBM i, see the Product Availability Matrix (PAM) at http://sup-
port.sap.com/pam and search for <Product> then choose <Product>.
On the Database Platforms tab, you see the supported releases under

DB2/400 .... OS/400 ... .

For information about which operating system versions have been released for
SAP on IBM i, see the following:

• For more information about V7R2, see SAP Note 2011710 .

• For more information about V7R3, see SAP Note 2299407 .
• For more information about V7R4, see SAP Note 2786037 .
• For more information about V7R5, see SAP Note 3152440 .

Required PTF List

The list of required PTFs informs you about the PTFs you must install on your IBM i
OS release.

For information about the releases and PTFs for SAP on IBM i and the address
where you can find the lists of the required PTFs, see SAP Note 83292 .

 Note
In the past, Information APAR were used instead of the Required PTF List.

 Caution
Make sure that English is installed as the primary or secondary language. For
more information, see Installing English as a Secondary Language [page 16].

To run an SAP system on IBM i with ASCII code pages, make sure that you have
installed 57nnSS1 option 21 – Extended NLS Support. This option is delivered to
you by IBM with the installation media of the operating system.

For more information about how to install the secondary language, see the IBM
documentation AS/400 National Language Support (SC41-5101-01)

Other Products

The following products are required:

 Note
xx = 70 (V7R2,V7R3,V7R4, and V7R5.)

• 57<xx>TC1 option *BASE – IBM TCP/IP Connectivity Utilities for i

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
14 PUBLIC Planning
 Requirement Values and Activities

• 57<xx>SS1 option *BASE – i5/OS

• 57<xx>SS1 option 1 – Extended Base Support
• 57<xx>SS1 option 2 – Online Information
• 57<xx>SS1 option 3 – Extended Base Directory Support
• 57<xx>SS1 option 12 – Host Servers
• 57<xx>SS1 option 13 – System Openness Includes
• 57<xx>SS1 option 21 – Extended NLS Support
• 57<xx>SS1 option 30 – Qshell
• 57<xx>SS1 option 33 – Portable Application Solutions Environment (PASE)

National Language Support (NLS) Make sure that National Language Support (NLS) and corresponding locales are
installed.

Other Requirements

Requirement Values and Activities

Minimum Web Browser Make sure that you have at least one of the following web browsers installed on the host
where you run the software provisioning manager's SL-UI:

• Microsoft Internet Explorer 11 or higher

• Microsoft Edge
• Mozilla Firefox
• Google Chrome

Always use the latest version of these web browsers.

You need a web browser to be able to run the SL-UI, and to display the Evaluation Form
and send it to SAP.

Host name To find out physical host names, open a command prompt and enter hostname.

 Note
Instead of using the command prompt, you CALL QP2TERM on IBM i.

For more information about the allowed host name length and characters allowed for
SAP system instance hosts, see SAP Note 611361 .

If you want to use virtual host names, see SAP Note 962955 .

If you want to use virtual host names on IBM i, see SAP Note 1624061 .

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
Planning PUBLIC 15
Requirement Values and Activities

Login shell The software provisioning manager only prompts you for this parameter if you use a login
shell other than C shell (csh).

For more information, see SAP Note 202227 .

 Note
On IBM i, you do not have to add or change any entry in the login shell input field.

Shared file systems for decen- If application servers are installed decentralized, a “shared” file system must be installed,
tralized systems for example Network File System (NFS).

 Note
On IBM i, you use QFileSvr.400.

2.1.2 Installing English as a Secondary Language

Use

On every IBM i where English is not the primary language, you must install English as the secondary language
library. This is necessary for SAP to be able to provide support.

 Note

To check if English is already installed on your IBM i host as a secondary language, enter GO LICPGM on the
IBM i command line and use option 20. If the following secondary language libraries is displayed, you have
already installed English as a secondary language library: QSYS2924

Other English language libraries like QSYS2938, QSYS2959, or QSYS2984 will not work, as the related
language package will not bring with the needed PASE language locale en_US. When the PASE language
locale en_US is missing, the software provisioning manager will fail to start.

Procedure

1. On the command line, enter GO LICPGM.

2. Enter option 21 (install secondary languages).
3. Enter option 1 to select the following library: QSYS2924.

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
16 PUBLIC Planning
  Note

If you have installed a different English language package than 2924 as the primary language or as
a secondary language library, you may fail to start the software provisioning manager. The software
provisioning manager is missing the PASE locale en_US.

The following error message will occur directly after staring the sapinst:

[==============================] / extracting… done!

ERROR: Setting native locale failed.

Choose different Locale Environment variables LC_ALL/LC_CTYPE

You can workaround this issue by setting the environment variable LC_ALL right before you start the
sapinst:

export LC_ALL=POSIX

This time the sapinst will start without error. To finally solve the issue you have to install the secondary
language library QSYS2924.

2.2 Basic Installation Parameters

The tables below list the basic system parameters that you need to determine before you start the installation.
For all other SAP system parameters, use the F1 help in the software provisioning manager screens.

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
Planning PUBLIC 17
Parameters Description

SAP System ID <SAPSID> The SAP System ID <SAPSID> identifies the standalone Gateway system.

 Caution
Choose your SAP system ID carefully. You cannot change the SAP system ID after
the installation.

Make sure that your SAP system ID:

• Is unique throughout your organization

• Consists of exactly three alphanumeric characters
• Contains only uppercase letters
• Has a letter for the first character
• Does not include any of the reserved IDs listed in SAP Note 1979280 .

 Caution
You must choose an SAP system ID that is different from the SAP system ID of the
central instance of the SAP system the Gateway belongs to.

Instance Number for the stand- Instance Number:

alone Gateway
Technical identifier for internal processes. Consists of a two-digit number from 00 to
97. The instance number must be unique on a host. That is, if more than one SAP
instance is running on the same host, these instances must be assigned different
numbers.

Virtual Host Name Virtual host name (network name) of the SAP<SAPSID> cluster group

You can assign a virtual host name for the instance to be installed, by specifying it in
the Host Name field of the Gateway Instance screen. Then this instance is installed with
this virtual host name.

After the installation has completed, all application servers can use this virtual host
name to connect to the instance. The virtual host name is also a global host name. If
you do not provide the virtual host name, the instance is installed automatically using
its physical host name.

You must have already reserved the virtual host name (network name) and its IP
address on a DNS server before you run the software provisioning manager. For more
information, see Using Virtual Host Names [page 27].

 Note
Fully qualified host names, IPv4, IPv6 are not accepted as virtual host names.

Alternatively you can assign virtual host names also by starting the software provision-
ing manager with the SAPINST_USE_HOSTNAME command line parameter. For more
information, see Running Software Provisioning Manager [page 39].

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
18 PUBLIC Planning
 Parameters Description

Master Password Common password for all users created during the installation:

Basic Password policy

The master password must meet the following requirements:

• It must be 8 to 30 characters long

• It must contain at least one letter (a-z, A-Z)
• It must contain at least one digit (0-9)
• It must not contain \ (backslash) or " (double quote).

Depending on the installation option, additional restrictions may apply.

 Recommendation
The Master Password feature can be used as a simple method to obtain customer-
specific passwords for all newly created users. A basic security rule is not to have
identical passwords for different users. Following this rule, we strongly recommend
individualizing the values of these passwords after the installation is complete.

For more information, see Ensuring User Security [page 51].

Operating System Users The software provisioning manager creates the users <SAPSID>ADM and
<SAPSID>OWNER.

The software provisioning manager assigns these users to the group R3GROUP.

The software provisioning manager also creates the user sapadm to use central moni-
toring services.

Make sure that the ID of this operating system user is unique and the same on each
application instance host.

If you do not create operating system users manually before you start the installation,
the software provisioning manager creates them automatically during the installation.

During the Define Parameters phase of the software provisioning manager you can
specify that the sapinst group is to be removed from the group set of the operating
system users after the execution of the software provisioning manager has completed.

The sapinst_instdir directory belongs to a group named SAPINST. If this group

is not available, it is created automatically as a local group. For security reasons, SAP
recommends removing the SAPINST group from the operating system user groups
after the execution of the software provisioning manager has completed.

For more information about the SAPINST group, see Preparing the SAP Installation
User onIBM i [page 28].

For more information about the sapinst_instdir directory, see Useful Informa-
tion About Software Provisioning Manager [page 43].

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
Planning PUBLIC 19
3 Preparation

3.1 Checking and Adjusting Operating System Values

To allow the SAP system to run optimally on IBM i, you must adjust a number of operating system values.

Prerequisites

• You have entered the following command to switch on work control block compression:
CHGIPLA CPRJOBTBL(*ALL)
This allows work control block space to be reused.
• The recommendations given below for system values QACTJOB, QTOTJOB, QADLACTJ, and QADLTOTJ
assume that only the SAP system is running on the IBM i. If you are also running other applications, you
might need to preallocate more jobs. The values QACTJOB and QTOTJOB are used for initial space allocation
at initial program load (IPL), time for the number of active jobs and the total number of jobs that are in
the system at any one time. If the allocated number of active or total jobs is reached, the system values
QADLACTJ and QADLTOTJ determine how many additional jobs are to have space allocated. Check and
adapt your TCP/IP configuration on IBM i. For more information, see SAP Note 92589 .

 Caution

Do not forget to perform an IPL after any change. Otherwise, your changes may not work.

• You have applied all installed program temporary fixes (PTFs) on your IBM i. To check this, enter the
following command:
DSPPTF
PTFs with the state Permanently applied, Temporarily applied or Superseded are integrated in the system
or are superseded by a newer PTF. PTFs with another state such as Not applied, Save file only, Damaged or
Cover letter only are not currently active.

 Recommendation

We recommend that you install all required PTFs. They should be applied and active.

Procedure

• To display all system values, enter the following command:

WRKSYSVAL SYSVAL(*ALL) OUTPUT(*PRINT)
• To display or change individual system values, enter the following command:
WRKSYSVAL SYSVAL(<system_value_name>)

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
20 PUBLIC Preparation
 and enter option 5 (Display) or option 2 (Change).
After changing a system value, enter option 5 (Display) to check your changes.

 Note

To avoid having to run an IPL several times, we recommend that you delay the IPL until you have made
all the necessary changes to the system values and, if necessary, have added a user ASP [page 24].

Checking and Adjusting Operating System Values

System Value Recommended Value Description

QMCHPOOL 10–15% of the entire main The fault rate in the *MACHINE pool should be as low as possi-
storage is assigned to the ma- ble, usually, lower than 5 (see SAP Note 49201 ); otherwise,
chine pool the pool must be increased. A change to this system value
takes effect immediately.

QACTJOB 1000 Set system value QACTJOB to a value close to the number of
jobs on your system. To find out the number of jobs, enter the
command WRKACTJOB. For a two-tier system, this is about
1000.

QTOTJOB 2000 Set system value QTOTJOB to 2000. When you have worked
with the SAP system for a while, adjust this value to the value
you usually see for the command WRKSYSSTS in the field Jobs
in system.

QADLACTJ 500 Set system value QADLACTJ to 500 and system value
QADLTOTJ to 1000.
and 1000

QADLTOTJ

QSECURITY 40 System value QSECURITY controls the level of security en-

forced on your system. Set QSECURITY to at least 40 to ensure
object security password, object, and operating system integ-
rity for the SAP objects to be installed. A QSECURITY value of
30 or less is not considered secure!

To activate this system value, you must perform an initial pro-

gram load (IPL).

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
Preparation PUBLIC 21
System Value Recommended Value Description

QCTLSBSD QCTL When you start your IBM i, the program specified in system
value QSTRUPPGM is called. This startup program is responsible
for starting the subsystems. When this startup program runs,
system value QCTLSBSD is queried. The specifications made
for this value determine whether subsystem QBASE or subsys-
tems QCTL, QINTER,QBATCH,QSPL,QCMN, and QSERVER are
started.

Two settings are possible for system value QCTLSBSD (control-

ling subsystem):

• QBASE
The controlling subsystem is QBASE. Subsystem QBASE is
started.
• QCTL
The controlling subsystem is QCTL. Subsys-
tems QCTL,QINTER,QBATCH,QSPL,QCMN,QSERVER are
started. Your change is activated the next time the IBM i
is started. To activate the subsystems, you have to restart
the IBM i.

QDATE Check the system date and adjust it if necessary. (The date
format is determined by system value QDATFMT.)

QTIME Check the system time and adjust it if necessary.

QJOBMSGQFL *WRAP or *PRTWRAP System value QJOBMSGQFL allows you to specify how you
would like the job message queue to be handled if it overflows.
The default value is *NOWRAP. If this value is set, the IBM
i sends a message when the queue is full and ends the job
that is currently running. When an SAP system is installed, a
large amount of information is sent to the job message queue.
For this reason, system value QJOBMSGQFL is automatically
changed to *WRAP during installation. If the queue becomes
full, the oldest entries are deleted and the current job is not in-
terrupted. Once the installation is complete, the system value
is automatically returned to its original value.

QPFRADJ 0 If you have adjusted the size of the IBM i pools as described in
SAP Note 49201 , you have to set the system value QPFRADJ
to 0. This deactivates automatic performance adjustment and
prevents your settings from being lost after an IPL.

QSTRUPPGM To cause your adjusted startup program to be started after an

IPL, change Startup program to QSTRUP and Library to QGPL.

QAUTOCFG 1 To allow device descriptions to be configured automatically, set

system value QAUTOCFG to 1.

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
22 PUBLIC Preparation
 System Value Recommended Value Description

QINACTITV *NONE IBM i V7R3 and higher: When running the software provisioning
manager the system value QINACTIV must be set to *NONE.
Otherwise, the installation is maybe suddenly ended by the
operating system without an error message in the installation
logs. For more information, see SAP Note 2672715 .

QBASACTLVL When installing an SAP sys- QBASACTLVL is the activity level of the base storage pool. This
tem, the value needs to be value indicates how many system and user threads can com-
increased. Use the following pete at the same time for storage in the base storage pool.
formulas to calculate the in- This pool is specified in the subsystem descriptions as *BASE.
crease: QBASACTLVL depends on the types of jobs run in this storage
pool. The lower limit for QBASACTLVL is 1.
(number of SAP work proc-
Note: This value does not affect only SAP work processes but
esses) * 1.20
also processes and threads that belong to other applications
running on your system.

 Note
In the past the Max Act value had an influence on the
database optimizer, but this has changed.

 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)

Changing TCP buffer size:

1. To change the following values, enter the following command:

CHGTCPA TCPRCVBUF(1048576) TCPSNDBUF(1048576)
2. To activate the changes, restart TCP/IP by entering the following commands:
ENDTCP
STRTCP
or perform an IPL.

For more information, see SAP Note 484548 and 92589 .

Changing Expert Cache

Activate the expert cache for the storage pool in which the subsystem of the SAP system runs. Usually, this is
the*BASE pool.

To activate the expert cache, enter the following command:

WRKSYSSTS

This will display the storage pools. Now change the default value in the column for the paging option
from *FIXED to *CALC. The paging option defines whether the system is to dynamically adjust the paging

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
Preparation PUBLIC 23
characteristics of the storage pool to achieve optimum performance in each case. *CALC can be used to
improve the performance of the database read accesses and the database write accesses so that larger blocks
can be read to the main storage and the changed data does not have to be removed from the main storage.

Result

You have made the necessary adjustments to IBM i values to enable the SAP system to run correctly on IBM i.

 Note

When a new SAP system is created a special entry is made automatically in the System Reply List. These
entries make sure that changes of tables attributes work without problems. Do not change or delete this
entry after the installation!

System Reply List Entries

Sequence Reply List Entries Message ID Reply

3201 CPA32B2 I

3.2 Adding a User ASP

Use

If you decide to store the database libraries and journal receiver libraries in separate auxiliary storage pools
(ASPs), make sure that you follow these guidelines:

1. The disk units in the ASP that is holding the journal receiver libraries must be protected by mirrored
protection or a different parity set than the disk units in the ASP that is holding the database libraries.
2. For performance reasons, the ASP that is holding the journal receiver libraries should have a minimum of
three disk arms.
3. The ASP that is holding the journal receivers should be large enough to hold all journal receivers that are
generated while your SAP system is running, until the receivers can be detached, saved, and deleted. If the
journal receivers grow too quickly and the ASP is full, some data might overflow into the system ASP. In this
state, you can no longer perform data recovery after disk failures that result in the loss of the system ASP.

Before you can specify a different ASP during the SAP installation, you must configure the ASP in IBM i and
assign disk units to it. The procedure consists of two steps:

1. You check if a user ASP with sufficient space has been set up.
2. You add or extend a user ASP if required.

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
24 PUBLIC Preparation
Procedure

Checking the User ASP

1. Enter STRSST (Start System Service Tools).

2. Sign on with a valid service tools user ID and password.
3. Enter option 3 (Work with disk units).
4. Enter option 2 (Work with disk configuration).
5. Enter option 1 (Display disk configuration).
6. Enter option 2 (Display disk configuration capacity).
You can see whether a user ASP exists and if it contains enough disk units. On the Display disk
configuration screen, you can also use option 5 (Display device parity status) to verify that your user ASP is
in a separate parity set.

 Note

In early releases of IBM i, user ASPs could only contain objects of type journal receiver or save file. The
libraries to address these objects where kept in the system ASP. If an existing user ASP contains journal
receivers or save files, while the library that contains these objects is in the system ASP, you cannot
create additional libraries in this user ASP and the installation fails. If you have sufficient disk space, we
recommend that you work around this problem by adding a second user ASP (for example, ASP 3). The
alternative would be to remove the old journal receivers or save files from the user ASP, or to create the
SAP journal receivers in the system ASP. For more information, see the IBM i documentation Backup
and Recovery (SC41-5304).

Adding a User ASP

1. Perform a manual initial program load (IPL) of your IBM i.

• Set the mode to manual on the control panel
• Enter the following command:
PWRDWNSYS *IMMED RESTART(*YES)
2. Enter option 3 (Use Dedicated Service Tools (DST)) from the menu that appears.
3. Sign on by entering your DST user and password.
4. Enter option 4 (Work with disk units).
5. Enter option 1 (Work with disk configuration).
6. Enter option 3 (Work with ASP configuration).
7. Enter option 6 (Move units from one ASP to another).
8. Specify the ASP to which you wish to move specific units by entering the number of the ASP next to the
relevant unit in the column New ASP.
9. Choose ENTER .
10. In the next screen, choose ENTER to confirm that you want to continue.
The Confirm Move of Units screen appears.
11. To confirm your choices, choose ENTER .

 Note

Moving units takes several minutes.

12. Continue the procedure and complete the IPL.

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
Preparation PUBLIC 25
13. Switch back to normal mode.

3.3 SAP Directories

The software provisioning manager automatically creates the directories listed in the following figures and
tables. Before running the installation, you have to set up the required file systems manually. In addition, you
have to make sure that the required disk space for the directories to be installed is available on the relevant
hard disks. The figure below assumes that you have set up one file system for the SAP system mount directory
<sapmnt> and one file system for the /usr/sap directory. However, you have to decide for which directories
you want to set up separate file systems. If you do not set up any file system on your installation host,
the software provisioning manager creates all directories in the root directory /. The software provisioning
manager prompts you only for the <sapmnt> directory during the installation.

The directory of the Gateway instance is G<Instance_Number>, for example G00.

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
26 PUBLIC Preparation
SAP Directories in Detail

 Note

The listed file system sizes are initial SAP requirements.

Depending on your operating system, you might also have to add space for administrative purposes.

Directory Name Description Space Required

/<sapmnt>/<SAPSID> The default name for the SAP system mount directory
is sapmnt.

• exe
Contains executable kernel programs
• global
Contains log files
• profile
Contains the start and operations profiles of all
instances

/usr/sap/<SAPSID> There are subdirectories of /usr/sap/<SAPSID>/SYS

with symbolic links to subdirectories of /<sapmnt>/
<SAPSID>:

3.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 without having to reinstall or reconfigure.

Prerequisites

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

Procedure

Proceed as described in SAP Note 1624061 .

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
Preparation PUBLIC 27
3.5 Preparing the SAP Installation User onIBM i

Use

For running the software provisioning manager you need to create a user account on the IBM i host.

The following requirement applies:

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

Procedure

 Note

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

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)

 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 software provisioning manager.

 Note

If you have already an old SAP 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)

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
28 PUBLIC Preparation
  Note

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

3.6 Enable the User QSECOFR

Use

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

Procedure

1. To check the status of the user profile QSECOFR use the following command as your installation user:
DSPUSRPRF USRPRF(QSECOFR)
2. To enable the user QSECOFR use the following command as your installation user:
CHGUSRPRF USRPRF(QSECOFR) STATUS(*ENABLED)

 Note

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

 Recommendation

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

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

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
Preparation PUBLIC 29
3.7 Preparing the Installation Media

This section describes how to prepare the installation media.

Installation media are available as follows:

• The Software Provisioning Manager 1.0 archive containing the software provisioning manager.
You always have to download the latest version of the Software Provisioning Manager 1.0 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 also download the installation media apart from the Software Provisioning Manager 1.0 archive
from https://me.sap.com/softwarecenter , as described at the end of this section.

You need several media during an SAP system installation. We recommend that you copy all relevant media for
an instance installation to the IFS of the IBM i host before you install the instance.

For more information, see the section Copying the Installation Media Manually to your IBM i [page 35].

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, copy performance is poor
from your local Windows media drive or your local Windows filesystem to the IFS on your IBM i.

 Note

The digital signature of media is checked automatically by the software provisioning manager during the
Define Parameters phase while processing the Media Browser screens. The software provisioning manager
only accepts media whose digital signature has been checked.

Related Information

Downloading and Extracting the Software Provisioning Manager 1.0 Archive [page 30]
Downloading Complete Installation Media [page 33]

3.7.1 Downloading and Extracting the Software Provisioning

Manager 1.0 Archive

Prerequisites

• Make sure that you use the latest version of the SAPCAR tool when manually extracting the software
provisioning manager archive. You need the SAPCAR tool to be able to unpack and verify software

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
30 PUBLIC Preparation
 component archives (*.SAR files). *.SAR is the format of software lifecycle media and tools that you can
download from the SAP Software Download Center.

 Note

An older SAPCAR version might extract archive files in a wrong way and this could prevent the software
provisioning manager from working consistently.

Proceed as follows to get the latest version of the SAPCAR tool:

1. Go to https://me.sap.com/softwarecenter SUPPORT PACKAGES & PATCHES By Category
SAP TECHNOLOGY COMPONENTS SAPCAR .
2. Select the SAPCAR for your operating system and download it to an empty directory.
3. Even if you have the latest SAPCAR already available, we strongly recommend that you verify its digital
signature anyway, unless you downloaded it directly from https://me.sap.com/softwarecenter/
yourself. You can do this by verifying the checksum of the downloaded SAPCAR tool:
1. Depending on what operating system you are using, compute a hash of the downloaded SAPCAR
tool, using the SHA-256 algorithm used by SAP .
2. Now verify the digital signature of the downloaded SAPCAR tool by comparing the hash with the
checksum (generated by SAP using the SHA-256 algorithm) from the Content Info button in the
Related Info column on the right-hand side of the place where you downloaded the SAPCAR tool.
4. To improve usability, we recommend that you rename the executable to sapcar.
For more information about SAPCAR, see SAP Note 212876 .
• You require the SAPCAR tool to be able to unpack and verify software component archives (*.SAR files).
*.SAR is the format of software lifecycle media and tools that you can download from the SAP Software
Download Center. For more information about how to get this tool, see the Procedure section below.

Context

Procedure

1. 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.
2. Unpack the Software Provisioning Manager archive to a local directory on your Windows PC using the
following command:

 Note

Make sure that all users have at least read permissions for the directory to which you unpack the
software provisioning manager.

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
Preparation PUBLIC 31
  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.

3. We recommend that you copy the Software Provisioning Manager 1.0 to the IFS of the IBM i host. For more
information about how to do this, see the section copy the installation media manually to your IBM i [page
35].

3.7.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 for your installation as listed below.

 Note

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

The following table shows the media required for the installation of a standalone Gateway instance:

Installation Media Description

Software Provisioning Manager 1.0 Software provisioning manager 1.0 archive

70SWPM10SP<Support_Package_Number>_<Version_Number>.
SAR

SAP Kernel Non-Unicode (NUC) Kernel (folder K_<Version>_N_<OS>) where N

means “non-Unicode”.

2. Make the installation media available on the installation host as follows:

a. Download and unpack the latest version of the software provisioning manager as described in
Downloading and Extracting the Software Provisioning Manager 1.0 Archive [page 30].
b. Make the installation media containing the software to be installed 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 software provisioning manager.

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

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
32 PUBLIC Preparation
  Caution

• If you copy the media to disk, make sure that the paths to the destination location of the
copied media do not contain any blanks and commas.

3.7.3 Downloading Complete Installation Media

This section describes how you can download 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 1.0 Archive [page 30].
2. You identify the required media as listed in Preparing the Installation Media [page 30] .
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://me.sap.com/softwarecenter/
SUPPORT PACKAGES & PATCHES By Category ADDITIONAL COMPONENTS SAP KERNEL
SAP KERNEL 64-BIT UNICODE SAP KERNEL <Version> 64-BIT UNICODE <Select your
OS> .
• Select #DATABASE INDEPENDENT to download the database-independent parts of the
kernel.

 Example

SAPEXE_1110-80002623.SAR
Kernel Part I (753) (*)

SAPEXE_1118-80002612.SAR

• Select <Your DB> to download the database-independent parts of the kernel.

 Example

SAPEXEDB_1110-80002623.SAR
Kernel Part II (753) (*)

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
Preparation PUBLIC 33
 • To download the remaining media required for your SAP product, you can use one of the following
navigation paths:
• https://me.sap.com/softwarecenter INSTALLATIONS & UPGRADES By Category SAP
NETWEAVER AND COMPLEMENTARY PRODUCTS <Product> <Product Release>
• https://me.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:
<Kernelpart>_<Sequence Number>-<Material Number>

 Example

SAPEXE_1110-80002623.SAR
Kernel Part I (753) (*)
SAPEXE_1111-80002623.SAR
Kernel Part I (753) (*)
SAPEXE_1112-80002623.SAR
Kernel Part I (753) (*)

 Example

SAPEXEDB_1110-80002623.SAR
Kernel Part II (753) (*)
SAPEXEDB_1111-80002623.SAR
Kernel Part II (753) (*)
SAPEXEDB_1112-80002623.SAR
Kernel Part II (753) (*)

• Title
All objects that are part of an installation medium have the same title, such as
<Solution><Media_Name><OS> or <Database>RDBMS<OS> for database media.
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 35].

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
34 PUBLIC Preparation
Related Information

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

3.7.4 Copying the Installation Media Manually to Your IBM i

Use

This section describes a secure way to copy the required installation media from your Windows PC to your IBM
i 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

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.

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
.

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
Preparation PUBLIC 35
7. On the Text Conversion tab, do not select Allow file text conversion.
8. To save the share TMPSAP, press OK.

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

 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 the SAP Installation User on IBM i [page 28].

6. To change to the new network drive, enter X: 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> or
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:\<Media> X:\<SAPSID>\<Media_Name> /E or
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:

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
36 PUBLIC Preparation
4 Installation

Prerequisites for Running Software Provisioning Manager [page 37]

Make sure you fulfil the following prerequisites before running the software provisioning manager.

Running Software Provisioning Manager [page 39]

This section describes how to run the installation tool Software Provisioning Manager (the “software
provisioning manager” for short).

Additional Information about Software Provisioning Manager [page 43]

The following sections provide additional information about the software provisioning manager.

4.1 Prerequisites for Running Software Provisioning

Manager

Make sure you fulfil the following prerequisites before running the software provisioning manager.

• For the SL-UI, 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-UI:
• Google Chrome (recommended)
• Mozilla Firefox
• Microsoft Edge
• Microsoft Internet Explorer 11 or higher.
Always use the latest version of these web browsers.
• If you copy the SL-UI 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-UI.

 Caution

The software provisioning manager uses a self-signed certificate, which is used temporarily only
while the software provisioning manager is running. This certificate is not trusted by the browser
unless it is imported manually by the user running the software provisioning manager. This behavior
is intentionally designed in this way because - unlike ordinary public web servers - the software
provisioning manager has different usage patterns. You must configure your browser do trust the
self-issued certificate of the software provisioning manager after carefully performing the “thumbprint”
verification described in Running Software Provisioning Manager [page 39] . For more information
about adding trusted certificates, see the documentation of your browser.

For more information about the SL-UI, see Useful Information About Software Provisioning Manager [page
43].

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
Installation PUBLIC 37
• 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 28].
• Make sure that you have specified the most important SAP system parameters as described in Basic SAP
System Installation Parameters [page 17] before you start the installation.
• Check the value of the environment variable TEMP, TMP, or TMPDIR:

Shells and Commands

Shell Used Command

Command prompt WRKENVVAR

Qp2Term echo $TEMP

• Make sure that your operating system does not delete the contents of the temporary directory /tmp
or the contents of the directories to which the variable TEMP, TMP, or TMPDIR points – for example, by
using a crontab entry.
• Make sure that you have at least 700 MB of free space in the installation directory for each installation
option. In addition, you need 700 MB free space for the software provisioning manager executables. If
you cannot provide 700 MB free space in the temporary directory, you can set one of the environment
variables TEMP, TMP, or TMPDIR to another directory with 700 MB free space for the software
provisioning manager 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 Software Provisioning Manager [page 43].

• Make sure that the following ports are not used by other processes:
• Port 4237 is used by default as HTTPS port for communication between the software provisioning
manager and the SL-UI.
If this port cannot be used, you can assign a free port number by executing sapinst with the following
command line parameter:
SAPINST_HTTPS_PORT=<Free Port Number>

 Example

CD DIR('<Path_To_Unpack_Directory>')

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

Number>')

• Port 4239 is used by default for displaying the feedback evaluation form at the end of the software
provisioning manager 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>

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
38 PUBLIC Installation
4.2 Running Software Provisioning Manager
This section describes how to run the installation tool Software Provisioning Manager (the “software
provisioning manager” for short).

Prerequisites

For more information, see Prerequisites for Running Software Provisioning Manager [page 37].

Context

The software provisioning manager has a web browser-based GUI named “SL-UI of the software provisioning
manager” - “SL-UI” for short.

This procedure describes an installation where you run the software provisioning manager and use the SL-UI,
that is you can control the processing of the software provisioning manager from a browser running on any
device.

For more information about the SL-UI, see Useful Information About Software Provisioning Manager [page
43].

Procedure

1. Log on to the installation host as a user with similar authorization rights to QSECOFR. For more information,
see Preparing an IBM i User Profile [page 28].

 Caution

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

If your security policy requires that the person running the software provisioning manager is not allowed to
know QSECOFR like credentials on the installation 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 .
2. Make the installation media available.

For more information, see Preparing the Installation Media [page 30].

 Recommendation

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

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
Installation PUBLIC 39
3. Start the software provisioning manager from the directory to which you unpacked the Software
Provisioning Manager archive by entering 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 software provisioning manager with the software
provisioning manager property SAPINST_USE_HOSTNAME as follows:

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

'SAPINST_USE_HOSTNAME=<Virtual_Host_Name>')

For more information, see Using Virtual Host Names [page 27].

 Caution

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

4. The software provisioning manager now starts and waits for the connection with the SL-UI.

You can find the URL you require to access the SL-UI at the bottom of the shell from which you are running
the software provisioning manager.

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

 Note

If the host specified by <hostname> cannot be reached due to a special network configuration,
proceed as follows:
1. Terminate the software provisioning manager as described in Useful Information About Software
Provisioning Manager [page 43].
2. Restart the software provisioning manager from the command line with the
SAPINST_GUI_HOSTNAME=<hostname> property.
You can use a fully-qualified host name.

Open the URL on a device with a supported web browser (see Prerequisites for Running Software
Provisioning Manager [page 37]).

 Caution

After opening the browser URL, make sure that the URL in the browser starts with “https://” to avoid
security risks such as SSL stripping .

Before you reach the Welcome screen, your browser warns you that the certificate of the sapinst
process on this computer could not be verified.

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
40 PUBLIC Installation
 Proceed as follows to avoid security risks such as a man-in-the-middle attack:
1. Click on the certificate area on the left hand side in the address bar of your browser, and view the
certificate.
2. Open the certificate fingerprint or thumbprint, and compare all hexadecimal numbers to the ones
displayed in the console output of the software provisioning manager.
Proceed as follows to get the certificate fingerprint or thumbprint from the server certificate
printed in the software provisioning manager console:
1. Go to the sapinst_exe.xxxxxx.xxxx directory in the temporary directory to which the
software provisioning manager has extracted itself:
/home/<Installation_User>/.sapinst
2. In the sapinst_exe.xxxxxx.xxxx directory, execute the sapgenpse tool with the
command line option get_my_name -p.
As a result, you get the server fingerprint or thumbprint from the server certificate.
3. Accept the warning to inform your browser that it can trust this site, even if the certificate could not
be verified.

The SL-UI opens in the browser by displaying the Welcome screen.

5. On the Welcome screen, choose the required option:

 Note

Products with the addition “SAP internal only” are only for SAP internal purposes and may not be used
outside of this purpose.

• To install a new standalone Gateway instance, go to <Product> and choose: Standalone

Engines Gateway
• To rename an existing standalone Gateway instance, go to System Rename and choose: Distributed
System System Rename for Gateway Instance
• To uninstall an existing standalone Gateway instance, go to <Product> Software Life-Cycle
Options Uninstall and choose: Uninstall - Systems / Standalone Engine / Optional Standalone
Unit
6. Choose Next.

 Note

If there are errors during the self-extraction process of the software provisioning manager, you can find
the log file dev_selfex.out in the temporary directory.

7. Follow the instructions on the software provisioning manager 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 , and choose either F1 or the HELP tab. Then the available help
text is displayed in the HELP tab.

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
Installation PUBLIC 41
  Caution

The digital 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. This means
that - if you modify artefacts later on either during the remaining Define Parameters phase or later on
during the Execute Service phase - the digital 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 software provisioning manager displays the
Parameter Summary screen. This screen shows both the parameters that you entered and those that the
software provisioning manager set by default. If required, you can revise the parameters before starting the
installation.
9. To start the installation, choose Next.

The software provisioning manager starts the installation and displays the progress of the installation.

When the installation option has finished successfully, the software provisioning manager displays the
message Execution of <Option Name> has completed.
10. If required, delete directories with the name sapinst_exe.xxxxxx.xxxx after the software provisioning
manager has finished. Sometimes these remain in the temporary directory.

 Recommendation

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

This might be useful for analyzing issues occurring later when you use the system. For security
reasons, do not keep installation directories on installation hosts, 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 installation has
successfully completed.
12. 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 software
provisioning manager has completed.

13. For security reasons, we recommend that you delete the .sapinst directory within the home directory of
the user with which you ran the software provisioning manager:

/home/<Installation_User>/.sapinst
14. The software provisioning manager log files contain IP addresses and User IDs such as the ID of your
S-User. For security, data protection, and privacy-related reasons we strongly recommend that you delete
these log files once you do not need them any longer.

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
42 PUBLIC Installation
 You find the software provisioning manager log files in the sapinst_instdir directory. For more
information, see Useful Information About Software Provisioning Manager [page 43].

4.3 Additional Information about Software Provisioning

Manager
The following sections provide additional information about the software provisioning manager.

Useful Information About Software Provisioning Manager [page 43]

This section contains some useful technical background information about the software provisioning
manager and the software provisioning manager's SL-UI.

Restarting Interrupted Processing of Software Provisioning Manager [page 45]

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

Troubleshooting with Software Provisioning Manager [page 48]

This section tells you how to proceed when errors occur while the software provisioning manager is
running.

Using the Step State Editor (SAP Support Experts Only) [page 49]
This section describes how to use the Step State Editor available in the software provisioning
manager.

4.3.1 Useful Information About Software Provisioning

Manager
This section contains some useful technical background information about the software provisioning manager
and the software provisioning manager's SL-UI.

• The software provisioning manager has a framework named “SAPinst”. For more information about the
current SAPinst Framework version and its features, see SAP Note 3207613 (SAPinst Framework 753
Central Note).

• The software provisioning manager has the web browser-based “SL-UI of the software provisioning
manager” - “SL-UI” for short.
The SL-UI 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.
As of version 1.0 SP24 Patch Level (PL) 5, the software provisioning manager comes with a new look and
feel of the SL-UI. For more information, see https://blogs.sap.com/2018/11/10/new-look-for-software-
provisioning-manager/ .
The SL-UI 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-UI the software provisioning manager provides a pre-generated URL at the bottom of the shell
from which you are running the software provisioning manager . If you have a supported web browser

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
Installation PUBLIC 43
 installed on the host where you run the software provisioning manager, you can start the SL-UI directly
from this URL. Otherwise, open a web browser supported by the SL-UI on any device and run the URL from
there.
For more information about supported web browsers see Prerequisites for Running Software Provisioning
Manager [page 37].
If you need to run the SL-UI in accessibility mode, apply the standard accessibility functions of your web
browser.

• As soon as you have started the sapinst executable, the software provisioning manager creates
a .sapinst directory underneath the /home/<User> directory where it keeps its log files. <User> is
the user with which you have started the software provisioning manager.
After you have reached the Welcome screen and selected the relevant software provisioning manager
option for the SAP system or instance to be installed , the software provisioning manager creates a
directory sapinst_instdir where it keeps its log files, and which is located directly below the temporary
directory. The software provisioning manager 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 software provisioning
manager uses /tmp by default.
All log files which have been stored so far in the .sapinst folder are moved to the sapinst_instdir
directory as soon as the latter has been created.
If you want the sapinst_instdir directory to be created in another directory than /tmp, set the
environment variable TEMP, TMP, or TMPDIR to this directory before you start the software provisioning
manager.

Shell Used Command

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

REPLACE(*YES)

Qp2Term export TEMP=<Directory>

 Caution

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

The software provisioning manager records its progress in the keydb.xml file located in the
sapinst_instdir directory. Therefore, if required, you can continue with the software provisioning
manager from any point of failure, without having to repeat the already completed steps and without
having to reenter the already processed input parameters. For security reasons, a variable encryption key
is generated as soon as the sapinst_instdir directory is created by the software provisioning manager.
This key is used to encrypt the values written to the keydb.xml file.

 Recommendation

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

• The software provisioning manager extracts itself to a temporary directory called

sapinst_exe.xxxxxx.xxxx, which is located in the environment variables TEMP, TMP, or TMPDIR. These
files are deleted after the software provisioning manager has stopped running.

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
44 PUBLIC Installation
 The temporary directory sapinst_exe.xxxxxx.xxxx sometimes remains undeleted. You can safely
delete it.
The temporary directory also contains the log file dev_selfex.out from the self-extraction process of
the software provisioning manager, which might be useful if an error occurs.

 Caution

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

• To see a list of all available software provisioning manager properties (command line options) and related
documentation, enter the following commands:
CD DIR('<Path_To_Unpack_Directory>')
CALL PGM(QP2TERM) PARM('./sapinst' '-p')

• If required, stop the software provisioning manager by choosing the Cancel button.

 Note

If you need to terminate the software provisioning manager, press Shift + Esc then 2 on your IBM
i host.

4.3.2 Restarting Interrupted Processing of Software

Provisioning Manager

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

Context

The processing of the software provisioning manager might be interrupted for one of the following reasons:

• An error occurred during the Define Parameters or Execute phase:

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

• You interrupted the processing of the software provisioning manager by choosing Cancel in the SL-UI.

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

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
Installation PUBLIC 45
The following table describes the options in the dialog box:

Option Definition

Retry The software provisioning manager retries the installation from the point of failure
without repeating any of the previous steps.

This is possible because the software provisioning manager records its 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 software provisioning manager displays
the same dialog box again.

Stop The software provisioning manager stops the installation, closing the dialog box and
the software provisioning manager's SL-UI.

The software provisioning manager records its progress in the keydb.xml file.
Therefore, you can continue with the software provisioning manager from the point of
failure without repeating any of the previous steps. See the procedure below.

Continue The software provisioning manager continues the installation from the current point.

View Log Access installation log files.

The following procedure describes the steps to restart an installation, which you stopped by choosing Stop, or
to continue an interrupted installation after an error situation.

Procedure

1. Log on to the installation host as a user with the required permissions as described in Running Software
Provisioning Manager [page 39] .
2. Make sure that the installation media are still available.

For more information, see Preparing the Installation Media [page 30].

 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 software provisioning manager 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')

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
46 PUBLIC Installation
 4. The software provisioning manager is restarting.

You can find the URL you require to access the SL-UI at the bottom of the shell from which you are running
the software provisioning manager.

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

 Note

If the host specified by <hostname> cannot be reached due to a special network configuration,
proceed as follows:
1. Terminate the software provisioning manager as described in Useful Information About Software
Provisioning Manager [page 43].
2. Restart the software provisioning manager from the command line with the
SAPINST_GUI_HOSTNAME=<hostname> property.
You can use a fully-qualified host name.

Open the URL on a device with a supported web browser (see Prerequisites for Running Software
Provisioning Manager [page 37]).

 Caution

After opening the browser URL, make sure that the URL in the browser starts with “https://” to avoid
security risks such as SSL stripping .

Before you reach the Welcome screen, your browser warns you that the certificate of the sapinst
process on this computer could not be verified.

Proceed as follows to avoid security risks such as a man-in-the-middle attack:

1. Click on the certificate area on the left hand side in the address bar of your browser, and view the
certificate.
2. Open the certificate fingerprint or thumbprint, and compare all hexadecimal numbers to the ones
displayed in the console output of the software provisioning manager.
Proceed as follows to get the certificate fingerprint or thumbprint from the server certificate
printed in the software provisioning manager console:
1. Go to the sapinst_exe.xxxxxx.xxxx directory in the temporary directory to which the
software provisioning manager has extracted itself:
/home/<Installation_User>/.sapinst
2. In the sapinst_exe.xxxxxx.xxxx directory, execute the sapgenpse tool with the
command line option get_my_name -p.
As a result, you get the server fingerprint or thumbprint from the server certificate.
3. Accept the warning to inform your browser that it can trust this site, even if the certificate could not
be verified.

The SL-UI opens in the browser by displaying the Welcome screen.

5. From the tree structure on the Welcome screen, select the installation option that you want to continue and
choose Next.

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
Installation PUBLIC 47
 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:

Alternative Behavior

Perform a new run The software provisioning manager does not continue the interrupted installa-
tion option. Instead, it moves the content of the old software provisioning man-
ager directory and all software provisioning manager-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 installation before you stopped it (such as creating
directories or users) are not revoked.

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

Continue with the existing one The software provisioning manager continues the interrupted installation from
the point of failure.

4.3.3 Troubleshooting with Software Provisioning Manager

This section tells you how to proceed when errors occur while the software provisioning manager is running.

Context

If an error occurs, the software provisioning manager:

• Stops processing
• Displays a dialog informing you about the error

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
48 PUBLIC Installation
Procedure

1. Check SAP Note 3207613 (SAPinst Framework 753 Central Note) for known software provisioning
manager issues.
2. If an error occurs during the Define Parameters or the Execute Service phase, do one of the following:

• Try to solve the problem:

• To check the software provisioning manager log files (sapinst.log and sapinst_dev.log) for
errors, choose the LOG FILES tab.

 Note

The LOG FILES tab is only available if you have selected on the Welcome screen the relevant
software provisioning manager option for the SAP product to be installed .

If you need to access the log files before you have done this selection, you can find them in
the .sapinst directory underneath the /home/<User> directory, where <User> is the user
that you used to start the software provisioning manager.

For more information, see Useful Information About Software Provisioning Manager [page 43].

• To check the log and trace files of the software provisioning manager's SL-UI for errors, go to the
directory /home/<Installation_User>/.sapinst/
• Then continue by choosing Retry.
• If required, abort the software provisioning manager by choosing Cancel in the tool menu and restart
the software provisioning manager. For more information, see Restarting Interrupted Processing of
Software Provisioning Manager [page 45].
3. If you cannot resolve the problem, report an incident using the appropriate subcomponent of BC-INS*.
For more information about using subcomponents of BC-INS*, see SAP Note 1669327 .

4.3.4 Using the Step State Editor (SAP Support Experts

Only)

This section describes how to use the Step State Editor available in the software provisioning manager.

 Note

Only use the Step State Editor if the SAP Support requests you to do so, for example to resolve a
customer incident.

Prerequisites

• SAP Support requests you to use the Step State Editor.

• Make sure that the host where you run the software provisioning manager meets the requirements listed in
Prerequisites for Running Software Provisioning Manager [page 37].

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
Installation PUBLIC 49
Procedure

1. Start the software provisioning manager from the command line as described in Running
Software Provisioning Manager [page 39] with the additional command line parameter
SAPINST_SET_STEPSTATE=true
2. Follow the instructions on the software provisioning manager screens and fill in the parameters prompted
during the Define Parameters phase until you reach the Parameter Summary screen.
3. Choose Next.

The Step State Editor opens as an additional dialog. Within this dialog you see a list of all steps to be
executed by the software provisioning manager during the Execute Service phase. By default all steps are
in an initial state. Underneath each step, you see the assigned software provisioning manager component.
For each step you have a Skip and a Break option.

• Mark the checkbox in front of the Break option of the steps where you want the software provisioning
manager to pause.
• Mark the checkbox in front of the Skip option of the steps which you want the software provisioning
manager to skip.
4. After you have marked all required steps with either the Break or the Skip option, choose OK on the Step
State Editor dialog.

The software provisioning manager starts processing the Execute Service phase and pauses one after
another when reaching each step whose Break option you have marked. You can now choose one of the
following:

• Choose OK to continue with this step.

• Choose Step State Editor to return to the Step State Editor and make changes, for example you
can repeat the step by marking the checkbox in front of the Repeat option.
• Choose Cancel to abort the software provisioning manager.
5. Continue until you have run through all the steps of the Execute Service phase of the software provisioning
manager.

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
50 PUBLIC Installation
5 Post-Installation Activities

5.1 Ensuring User Security

You need to ensure the security of the users that the software provisioning manager created during the
installation.

The tables below at the end of this section list these users:

• Operating system users

• SAP system users

During the installation, the software provisioning manager by default assigned the master password [page 17]
to all users created during the installation unless you specified other passwords.

 Recommendation

The Master Password feature can be used as a simple method to obtain customer-specific passwords for
all newly created users. A basic security rule is not to have identical passwords for different users. Following
this rule, we strongly recommend individualizing the values of these passwords after the installation is
complete.

If you change user passwords, be aware that SAP system users might exist in multiple SAP system clients (for
example, if a user was copied as part of the client copy). Therefore, you need to change the passwords in all the
relevant SAP system clients.

 Recommendation

User ID and password are encoded only when transported across the network. Therefore, we recommend
using encryption at the network layer, either by using the Secure Sockets Layer (SSL) protocol for HTTP
connections or Secure Network Communications (SNC) for the SAP protocols dialog and RFC.

For more information, see:

http://help.sap.com/nw SAP NetWeaver Platform SAP NetWeaver 7.0 <Including

Enhancement_Package> Application Help SAP NetWeaver by Key Capability Security Network
and Transport Layer Security

 Caution

Make sure that you perform this procedure before the newly installed SAP system goes into production. For
security reasons, you also need to copy the installation directory to a separate, secure location – such as a
separate storage medium – and then delete the installation directory.

For the users listed below, take the precautions described in the relevant SAP security guide.

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
Post-Installation Activities PUBLIC 51
Operating System Users

After the installation, operating system users for SAP system, databaset, and SAP Host Agent are available as
listed in the following table:

 Recommendation

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

You do not have to do this if you specified this “cleanup” already during the Define Parameters phase on the
Cleanup Operating System Users screen. Then the removal had already been done automatically when the
processing of the software provisioning manager had completed.

Operating System Users

User Type User Comment

Operating system user <sapsid>adm Administrator for the Standalone Gateway.

SAP Host Agent User

User User Name Comment

Operating system user sapadm SAP system administrator

You do not need to change the password of this user

after the installation.

This user is for administration purposes only.

SAP System Users

More Information

5.2 Gateway Configuration

You have to configure the gateway to be able to use it.

You find the configuration documentation in the SAP Library [page 11] at: Application Platform by Key
Capability Platform-Wide Services Connectivity SAP Gateway

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
52 PUBLIC Post-Installation Activities
6 Additional Information

6.1 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 without having to reinstall or reconfigure.

Prerequisites

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

Procedure

Proceed as described in SAP Note 1624061 .

6.2 Starting and Stopping the Instance Using Commands

Use

You can start and stop the Gateway instance by entering the commands STARTSAP and STOPSAP.

Procedure

Starting the Gateway Instance

1. Log on as user <SID>ADM.

2. Check that there are no active jobs for the Gateway instance that you have just installed. To do this,
proceed as follows:
1. Enter the following command for the Gateway instance:
WRKACTJOB SBS(R3_<instance_number>)
2. If a job is displayed, stop it using command:
ENDSBS SBS(R3_<instance_number>) OPTION(*IMMED)

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
Additional Information PUBLIC 53
3. To start the Gateway instance, enter the following command and press F4 :
STARTSAP
4. Enter the SAP system ID of the Gateway (for example, C11) and instance number (for example, 90).

 Recommendation

We recommend that you retain the default value *ENV for the SAP system ID. *ENV is replaced by the
correct value for the SAP system ID.

5. To check whether the Gateway is started successfully, enter the following command:
WRKACTJOB SBS(R3_nn)

 Note

The instance runs in its own subsystem R3_nn, where nn is the instance number.

Stopping the Gateway Instance

1. Log on as <SID>ADM.
2. To stop the Gateway instance, enter the following command and press F4 :
STOPSAP
3. Enter the SAP system ID of the Gateway (for example, C11) and instance number (for example, 90).

 Recommendation

We recommend that you retain the default value *ENV for the SAP system ID. *ENV is replaced by the
correct value for the SAP system ID.

6.3 Uninstalling the Gateway Instance

The following procedure describes how to uninstall a standalone Gateway instance using the software
provisioning manager.

Procedure

1. Start the software provisioning manager [page 39].

2. On the Welcome screen, choose Software Life-Cycle Options Uninstall System / Standalone Engine /
Optional Standalone Unit .
3. Follow the instructions in the software provisioning manager screens.

 Note

To find more information on each parameter during the Define Parameters phase of uninstalling,
position the cursor on the field of the respective parameter and press F1 .

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
54 PUBLIC Additional Information
Important Disclaimers and Legal Information

Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:

• Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:

• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.

• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

• Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering an SAP-hosted Web site. By using
such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.

Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within
the control or responsibility of SAP.

Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities,
genders, and abilities.

Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP
NetWeaver 7.0 to 7.03 on IBM i
Important Disclaimers and Legal Information PUBLIC 55
www.sap.com/contactsap

© 2024 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.

Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.

SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.

Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.

THE BEST RUN