Installation Guide | PUBLIC Software Provisioning Manager 1.0 SP32 Document Version: 3.6 – 2021-06-21

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i company. All rights reserved. affiliate

THE BEST RUN 2021 SAP SE or an SAP © Content

1 About this Document...... 10 1.1 About Software Provisioning Manager 1.0...... 10 1.2 New Features...... 11 1.3 SAP Notes for the Installation...... 13 1.4 Accessing the SAP Library...... 14 1.5 Naming Conventions...... 15

2 Planning...... 16 2.1 Hardware and Software Requirements...... 16 Hardware and Software Requirements Tables...... 16 2.2 Basic Installation Parameters...... 20

3 Preparation...... 23 3.1 SAP Directories...... 23 3.2 Using Virtual Host Names...... 26 3.3 Installing English as a Secondary Language...... 26 3.4 Preparing the SAP Installation User on IBM i...... 27 3.5 Enable the User QSECOFR...... 28 3.6 Preparing the Installation Media ...... 29 Downloading and Extracting the Software Provisioning Manager 1.0 Archive...... 30 Downloading Installation Archives (Archive-Based Installation)...... 31 Downloading Complete Installation Media...... 32 Copying the Installation Media Manually to Your IBM i...... 34

4 Installation...... 36 4.1 Prerequisites for Running the Installer...... 36 4.2 Running the Installer...... 38 4.3 Additional Information about the Installer...... 41 Useful Information about the Installer...... 41 Interrupted Processing of the Installer...... 43 Troubleshooting with the Installer...... 47 Using the Step State Editor (SAP Support Experts Only)...... 48

5 Post-Installation Activities...... 49 5.1 Gateway Configuration ...... 49

6 Additional Information...... 50 6.1 Using Virtual Host Names...... 50

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i 2 PUBLIC Content 6.2 Starting and Stopping the Instance Manually...... 50 6.3 Uninstall...... 51

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x 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 SP .

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

Version Date Description

3.6 2021-06-21 Updated version for Software Provision­ ing Manager 1.0 SP32 (SL Toolset 1.0 SP32)

3.5 2021-02-15 Updated version for Software Provision­ ing Manager 1.0 SP31 (SL Toolset 1.0 SP31)

3.4 2020-10-05 Updated version for Software Provision­ ing Manager 1.0 SP30 (SL Toolset 1.0 SP30)

3.3 2020-06-08 Updated version for Software Provision­ ing Manager 1.0 SP29 (SL Toolset 1.0 SP29)

3.2 2020-01-20 Updated version for Software Provision­ ing Manager 1.0 SP28 (SL Toolset 1.0 SP28)

3.1 2019-09-16 Updated version for Software Provision­ ing Manager 1.0 SP27 (SL Toolset 1.0 SP27)

3.0 2019-05-27 Updated version for Software Provision­ ing Manager 1.0 SP26 (SL Toolset 1.0 SP26)

2.9 2019-01-21 Updated version for Software Provision­ ing Manager 1.0 SP25 (SL Toolset 1.0 SP25)

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

2.8 2018-09-17 Updated version for Software Provision­ ing Manager 1.0 SP24 (SL Toolset 1.0 SP24)

2.7 2018-05-07 Updated version for Software Provision­ ing Manager 1.0 SP23 (SL Toolset 1.0 SP23)

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

2.6 2018-01-15 Updated version for Software Provision­ ing Manager 1.0 SP22 (SL Toolset 1.0 SP22)

● New Features: ○ Signature check for installa­ tion archives, documented in: New Features, Downloading SAP Kernel Archives (Archive- Based Installation) Archive- Based Installation for Diagnos­ tics Agent, Downloading the SAP Kernel Archives Required for the Dual-Stack Split (With­ out Operating System and Da­ tabase Migration), Download­ ing the SAP Kernel Archives Required for Operating System and Database Migration ○ Installer Log Files Improve­ ments, documented in: New Features, Useful Information about the Installer, Trouble­ shooting with the Installer ○ Enabling IPv6, documented in: New Features, Prerequisites for Running the Installer ● New Features section restructured: As of SP22, a dedicated subsection for each new SP has been created. New features below SP22 remain in a common table. ● The Java SDT GUI - which was in the SP21 version still available in parallel to the SL Common GUI - has been deprecated with SP22. As of SP22, SL Common GUI is the only available installer GUI: ○ The following sections which were explicitely related to Java SDT GUI were completely re­ moved from this documenta­ tion: Performing a Remote In­ stallation Remote Processing of the Installer ( Java SDT GUI only), Starting the Java SDT

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

GUI Separately, Running the Installer in Accessibility Mode (general accessibility informa­ tion was moved to Useful In­ formation About the Installer). ○ The Java SDT GUI-specific in­ formation was removed from the common installer sec­ tions: Running the Installer, Useful Information About the Installer, Interrupted Process­ ing of the Installer, Trouble­ shooting with the Installer ● New section Using the Step State Editor (SAP Support Experts Only) was added to section Additional In­ formation About the Installer

2.5 2017-09-11 Updated version for Software Provision­ ing Manager 1.0 SP21 (SL Toolset 1.0 SP21)

● New Features: ○ Media Signature Check, docu­ mented in: New Features, Run­ ning the Installer, Preparing the Installation Media . This feature implies that sec­ tion Creating Kernel Archives from an Existing SAP System has been deleted from this documentation because the related option in the installer had to be removed. ○ SAP Host Agent Upgrade , documented in: New Features, SAP System Parameters, Downloading SAP Kernel Ar­ chives (Archive-Based Installa­ tion)

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i Document History PUBLIC 7 Version Date Description

2.4 2017-05-22 Updated version for Software Provision­ ing Manager 1.0 SP20 (SL Toolset 1.0 SP20)

● New Features: ○ New SAPUI5-based graphical user interface (GUI) “SL Com­ mon GUI”, documented in: Prerequisites for Running the Installer, Running the Installer, Useful Information About the Installer ○ Cleanup of operating system users, documented in: SAP System Parameters, Creating Operating System Users and Groups

2.3 2017-02-06 Updated version for Software Provision­ ing Manager 1.0 SP19 (SL Toolset 1.0 SP19)

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)

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)

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i 8 PUBLIC Document History Version Date Description

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 Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i Document History PUBLIC 9 1 About this Document

This documentation describes how to install or rename a standalone Gateway instance on IBM i, for SAP system products based on SAP NetWeaver 7.1 to 7.52, using the Software Provisioning Manager 1.0 SP32 [page 10] (“installer” for short), which is part of SL Toolset 1.0 SP32.

You can find a complete list of the SAP system products that are supported by Software Provisioning Manager 1.0 attached to SAP Note 1680045 .

Each instance of an SAP system with an ABAP application server 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.

You can also install a standalone Gateway. With the 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 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

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 Software Provisioning Manager 1.0. 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 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” (“installer” for short) in this documentation, but the terms “SAPinst” and “sapinst” are still used in:

● The name of the technical framework of Software Provisioning Manager. For more information about the SAPinst Framework, see SAP Note 2393060 . ● Texts and screen elements in 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 Software Provisioning Manager 1.0 as the “installer”. We only use the term “Software Provisioning Manager 1.0” if this is required for technical reasons.

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i 10 PUBLIC About this Document Related Information

Preparing the Installation Media [page 29]

1.2 New Features

This section provides an overview of the new features in Software Provisioning Manager 1.0 (the“ installer” for short).

Make sure that you also read the Release Notes for your SAP product at https://help.sap.com

What’s New .

Feature Description Availability

SAP Rename for The SAP Rename for IBM i now supports SAP systems installed Software Provisioning Manager SAP systems instal­ on the IASP. For more information, see the SAP Rename guide for 1.0 SP29 (SL Toolset 1.0 SP29 led on the independ­ IBM i. In the past, the SAP System Copy had to be used to rename ent auxiliary storage a system located on the IASP. pool (IASP).

Homogeneous Sys­ The SAP Refresh Database Content on IBM i now supports exist­ Software Provisioning Manager tem Copy using ex­ ing SAP database libraries. For more information, see the system 1.0 SP28 (SL Toolset 1.0 SP28) isting SAP database copy guide section Copying the Database Only - Refresh Database library for Refresh Content. Database Content

Software Provision­ The new OS release IBM i 7.4 is certified for SAP Solutions since Software Provisioning Manager ing Manager on IBM July 19, 2019. For more information, see the SAP on IBM i blog en­ 1.0 SP27 (SL Toolset 1.0 SP27) i now supports the try "SAP on IBM i: IBM i 7.4 Certified for SAP Solutions ". In ad­ new OS release IBM dition, see SAP Note 1680045 , section Planning and Prepara­ i 7.4 tion : SAP System Installation on OS release IBM i V7R4.

New Look and Feel As of version 1.0 SP24 Patch Level (PL) 5, Software Provisioning Software Provisioning Manager of SL Common GUI Manager comes with a new look and feel of the SL Common GUI. 1.0 SP24, PL05 (SL Toolset 1.0 For more information, see https://blogs.sap.com/2018/11/10/ SP24) new-look-for-software-provisioning-manager/ .

Installer Log Files Installer log files are now available immediately after the installer Software Provisioning Manager Improvements has been started, that is before a product has been selected on 1.0 SP22 (SL Toolset 1.0 SP22) the Welcome screen. For more information, see Useful Informa­ tion about the Installer [page 41] and Troubleshooting with the Installer [page 47].

Signature Check of The signature of installation archives is checked automatically by Software Provisioning Manager the installer during the Define Parameters phase while processing 1.0 SP22 (SL Toolset 1.0 SP22) Installation Archives the Software Package Browser screens. As of now the installer only accepts archives whose signature has been checked. For more information, see Downloading Installation Archives (Ar­ chive-Based Installation) [page 31] .

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i About this Document PUBLIC 11 Feature Description Availability

Enabling IPv6 You can now set up a new SAP system or SAP system instance us­ Software Provisioning Manager 1.0 SP22 (SL Toolset 1.0 SP22) ing Internet Protocol Version 6 (IPv6).

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

Media Signature The signature of media is checked automatically by the installer Software Provisioning Manager 1.0 SP21 (SL Toolset 1.0 SP21) Check during the Define Parameters phase while processing the Media Browser screens. As of now the installer only accepts media whose signature has been checked. See also the description of this new security feature in SAP Note 2393060 .

For more information, see Preparing the Installation Media [page 29] and Running the Installer [page 38].

SAP Host Agent Up­ During the Define Parameters phase of the installation, the instal­ Software Provisioning Manager grade During the In­ ler prompts you whether you want to upgrade an existing version 1.0 SP21 (SL Toolset 1.0 SP21) stallation (Optional) of the SAP Host Agent on the installation host. If there is no SAP Host Agent on the installation host, it is installed automatically without prompt. For more information, see Basic Installation Pa­ rameters [page 20].

SL Common GUI With the new installer framework version SAPINST 7.49, you can Software Provisioning Manager with SAPINST 7.49 now use the new SAPUI5-based graphical user interface (GUI) “SL 1.0 SP20 (SL Toolset 1.0 SP20) Common GUI”. For more information, see Useful Information about the Installer [page 41], Running the Installer [page 38] .

Cleanup of Operat­ You can now specify during the Define Parameters phase that the Software Provisioning Manager ing System Users 1.0 SP20 (SL Toolset 1.0 SP20) group SAPINST is to be removed from the operating system users after the execution of the installer has completed.

For more information, see Operating System Users in Basic Instal­ lation Parameters [page 20].

Verification of Integ­ The integrity of data units extracted from the Software Provision­ Software Provisioning Manager rity of Data Units in 1.0 SP19 (SL Toolset 1.0 SP19) ing Manager archive is verified. For more information, see Down­ Software Provision­ loading and Extracting the Software Provisioning Manager 1.0 Ar­ ing Manager chive [page 30] .

In addition, check SAP Note 1680045 whether additional infor­ mation is available.

Archive-Based In­ You can now download the required installation archives for the Software Provisioning Manager stallation SAP Gateway installation, instead of using the complete SAP ker­ 1.0 SP18 (SL Toolset 1.0 SP18) nel installation media. For more information, see Downloading In­ stallation Archives (Archive-Based Installation) [page 31].

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i 12 PUBLIC About this Document Feature Description Availability

System Provisioning All system provisioning tasks (installation, system copy, system Software Provisioning Manager for SAP NetWeaver rename) are available for the new SAP NetWeaver 7.5 release. 1.0 SP09 (SL Toolset 1.0 SP15) 7.5 and SAP The Dual Stack option, which integrates an AS ABAP and AS Java NetWeaver 7.5- in a single system (common System ID , common based Products startup framework, common database), is no longer supported in SAP systems based on SAP NetWeaver 7.5.

Feedback Evaluation SAP SE’s aim is to provide fast and efficient procedures. To evalu­ Software Provisioning Manager Form ate the procedure you just carried out, we need information gen­ 1.0 SP07 (SL Toolset 1.0 SP12) erated by the tool during process execution and your experience with the tool itself. A new evaluation form contains a simple ques­ tionnaire and XML data generated during the procedure.

Port 4239 is used for displaying the feedback evaluation form.

Option Verify Signed The digital signature ensures that the signatory of a digital docu­ Software Provisioning Manager Media ment can be identified unambiguously and signatory’s name is 1.0 SP06 (SL Toolset 1.0 SP11) documented together with the signed document, the date, and the time.

For more information, see SAP Note 1979965 .

Automatic user The installer checks if the user QSECOFR and the IBM i installa­ Software Provisioning Manager check of the tion user are prepared correctly. Only if the installer detects an in­ 1.0 SP20 (SL Toolset 1.0 SP20) QSECOFR and the consistency, then a dialog screen appears. IBM i installation For more information about how to prepare these users, see Pre­ user paring the SAP Installation User on IBM i [page 27] and Enable the User QSECOFR [page 28] .

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 .

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

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i About this Document PUBLIC 13 SAP Note Number Title Description

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.0x http://help.sap.com/nw SAP NetWeaver Platform SAP NetWeaver 7.0 Application Help SAP NetWeaver by Key Capability

SAP systems based on SAP NetWeaver 7.1x ● SAP NetWeaver Mobile 7.1: http://help.sap.com/nwmobile71 : (Out of Maintenance, see SAP Note 2980160 ) Application Help ● SAP NetWeaver Mobile 7.1 EHP1: http://help.sap.com/nwmobile711

: Application Help ● SAP NetWeaver Process Integration 7.1: http://help.sap.com/nwpi71/

Application Help SAP Library SAP NetWeaver Process

Integration Library ● SAP NetWeaver Process Integration 7.1 EHP1: http://help.sap.com/

nwpi711/ Application Help SAP Library SAP NetWeaver

Process Integration Library

SAP systems based on SAP NetWeaver 7.2 SAP NetWeaver Composition Environment 7.2: http://help.sap.com/

(Out of Maintenance, see SAP Note 2980160 nwce72 Application Help SAP Library )

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

SAP NetWeaver Library: Function-Oriented View ● SAP NetWeaver 7.3 EHP1: http://help.sap.com/nw731

Application Help SAP NetWeaver Library: Function-Oriented

View

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

Library: Function-Oriented View

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i 14 PUBLIC About this Document Product and Release SAP Library Path

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

SAP NetWeaver Library: Function-Oriented View ● SAP NetWeaver Application Server for ABAP 7.51 innovation package:

https://help.sap.com/nw751abap Application Help SAP

NetWeaver Library: Function-Oriented View ● SAP NetWeaver AS for ABAP 7.52: https://help.sap.com/nw752abap

Application Help SAP NetWeaver Library: Function-Oriented

View

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.

● “installer” refers to “Software Provisioning Manager 1.0” . ● “SAP system” refers to the “standalone Gateway” as such. ● “instance” refers to the “standalone Gateway instance”.

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i About this Document PUBLIC 15 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.

 Caution

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

Procedure

1. Check the Product Availability Matrix at https://support.sap.com/pam for supported operating system releases. 2. Check the hardware and software requirements table for the Gateway Instance [page 16]. 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:

Hardware Requirements

Requirement Values and Activities

Hardware requirements ● Optical Media drive (on the Windows installer GUI host) ● Before installing an SAP system on IBM i, you must obtain detailed sizing information from your IBM representative.

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i 16 PUBLIC Planning Requirement Values and Activities

Optical media drive ISO 9660 compatible

Hard disk space ● General Requirements: ○ 2 GB of temporary disk space for each required physical installation media - or al­ ternatively the downloaded SAP kernel archives - that you have to copy to a local hard disk. For more information, see Preparing the Installation Media [page 29]. ○ If you prefer downloading the separate kernel archives instead of using the com­ plete kernel media, you require 1 GB of temporary disk space for the set of archives that you have to copy to a local hard disk. For more information, see Downloading Installation Archives (Archive-Based Installation) [page 31] . ○ 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: The standalone Gateway instance requires 1 GB of hard disk space minimum.

RAM

Space requirements The amount of space required for an SAP system on IBM i is dependent on many variables, such as:

● Number of work processes ● Number of users

Sizing recommendations are made by the IBM Competency Center. We recommend that aux­ iliary storage pool (ASP) usage in SAP production systems is 70% or less.

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i Planning PUBLIC 17 Software Requirements

Requirement Values and Activities

Operating system requirements The SAP products based on SAP NetWeaver 7.5 are released for V7R2, V7R3, and V7R4.

For information about which operating system versions have been released for SAP on IBM i, see the Product Availability Matrix (PAM) at http://support.sap.com/pam and search for then choose . 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 V7R1, see SAP Note 1432783 .

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 .

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.

To be able 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 doc­ umentation AS/400 National Language Support (SC41-5101-01).

Other Products

The following products are required:

 Note

xx=70 (V7R1,V7R2,V7R3, and V7R4)

● 57xxTC1 option *BASE – IBM TCP/IP Connectivity Utilities for iSeries ● 57xxSS1 option *BASE – i5/OS ● 57xxSS1 option 1 – Extended Base Support ● 57xxSS1 option 2 – Online Information ● 57xxSS1 option 3 – Extended Base Directory Support ● 57xxSS1 option 12 – Host Servers

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i 18 PUBLIC Planning Requirement Values and Activities

● 57xxSS1 option 13 – System Openness Includes ● 57xxSS1 option 21 – Extended NLS Support ● 57xxSS1 option 30 – Qshell Interpreter ● 57xxSS1 option 33 – Portable Application Solutions Environment (PASE)

SAP Kernel Releases and Versions To use regular Software Provisioning Manager (SWPM10.SAR) with SAP kernel 7.49 or higher on RHEL 6 or SLES 11 or Oracle Linux 6, you must install the required libstdc++ RPM packages. For more information, see SAP Note 2195019 .

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 installer GUI:

● 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 Common GUI, and to display the Evalua­ tion 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 Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i Planning PUBLIC 19 Requirement Values and Activities

Login shell The installer 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.

Installer GUI host Windows or Linux PC to start the installer GUI

2.2 Basic Installation Parameters

The table below lists the basic input parameters that are prompted by the installer. For all remaining input parameters, use the tool help or the descriptions on the installer screens.

Parameters Description

SAP System ID The SAP System ID 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.

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i 20 PUBLIC Planning Parameters Description

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 in­ stance is running on the same host, these instances must be assigned different num­ bers.

Virtual Host Name Virtual host name (network name) of the SAP 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 ad­ dress on a DNS server before you run the installer. For more information, see Using Vir­ tual Host Names [page 26].

 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 installer with the SAPINST_USE_HOSTNAME command line parameter. For more information, see Run­ ning the Installer [page 38].

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i Planning PUBLIC 21 Parameters Description

Operating System Users The installer creates the users ADM and OWNER.

The installer assigns these users to the group R3GROUP.

The installer also creates the user sapadm to use central monitoring 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 installer creates them automatically during the installation.

During the Define Parameters phase of the installer you can specify that the sapinst group is to be removed from the group set of the operating system users after the exe­ cution of the installer 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 af­ ter the execution of the installer has completed.

For more information about the SAPINST group, see Preparing the SAP Installation User on IBM i [page 27].

For more information about the sapinst_instdir directory, see Useful Informa­ tion about the Installer [page 41].

SAP Host Agent Upgrade (Op­ If there already exists an SAP Host Agent on the installation host, the installer asks you tional) if you want to upgrade it to a newer patch level version. If you want the existing version to be upgraded, you must provide the new target version of the SAPHOSTAGENT.SAR archive.

For more information, see Downloading Installation Archives (Archive-Based Installa­ tion) [page 31]

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i 22 PUBLIC Planning 3 Preparation

This section describes in detail the steps you need to take before installing your .

3.1 SAP Directories

The installer 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 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 installer creates all directories in the root directory /. The installer prompts you only for the directory during the installation.

SAP Directories of a Standalone Gateway for SAP Systems based on SAP NetWeaver 7.0 to SAP NetWeaver 7.0 EHP3

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i Preparation PUBLIC 23 SAP Directories of a Standalone Gateway for SAP Systems based on SAP NetWeaver 7.1 and Higher

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

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.

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i 24 PUBLIC Preparation File System Name Description Space Required

// The default name for the SAP system mount directory is 500 MB sapmount.

● exe Contains executable kernel programs ● global Contains log files ● profile Contains the start and operations profiles of the Gateway instance

/usr/sap/ This directory contains the following subdirectories: 500 MB

● SYS

 Note

The subdirectories of /usr/sap//SYS have symbolic links to the corresponding subdirectories of / /, as shown in the figure above.

● The instance name (instance ID) of the Gateway instance is G, for example G00.

There are subdirectories of /usr/sap//SYS with symbolic links to subdirectories of //:

/usr/sap/trans This directory contains SAP software for the transport of objects This value heavily depends between SAP systems . on the use of your SAP sys­ tem.

For the installation, it is suffi- cient to use 200 MB. You can enlarge the file system afterwards if required.

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i Preparation PUBLIC 25 3.2 Using Virtual Host Names

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

Prerequisites

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

Context

Procedure

Proceed as described in SAP Note 1624061 .

3.3 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 as a secondary language, enter GO LICPGM on the IBM i command line and use option 20. If one of the following secondary language libraries is displayed, you have already installed English as a secondary language library:

QSYS2924, QSYS2938, QSYS2959, or QSYS2984.

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i 26 PUBLIC Preparation Procedure

1. On the IBM i command line, enter GO LICPGM 2. Enter option 21 (install secondary languages). 3. Enter option 1 to select any of the following libraries: QSYS2924, QSYS2938, QSYS2959, or QSYS2984.

3.4 Preparing the SAP Installation User on IBM i

For running the installer, you must create the SAP installtion user profile on the IBM i host.

The following requirement applies:

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

Procedure

 Note

The user name SAPIUSR and the password SAP are used as examples. You can use a different user name for the SAP installation user. Make sure you do not user SAP as the password as this is not secure.

To create the SAP installation user profile, enter the following command:

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

 Caution

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

RMVENVVAR ENVVAR(QIBM_PASE_CCSID) LEVEL(*SYS)

 Note

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

CHGUSRPRF USRPRF(SAPIUSR) GRPPRF(SAPINST)

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i Preparation PUBLIC 27 Now the user SAPINST can also be used as a group by the installer.

 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, enter the following command:

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

 Note

In a distributed environment, the SAP 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 SAP installation user of a remote additional application server instance.

3.5 Enable the User QSECOFR

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

 Note

If the SAP Host Agent release 7.21, patch level 43 and higher is used, the QSECOFR can be disabled. Whether the QSECOFR needs to be disabled depends on the customer's security concept. As of SAP Host Agent release 7.21, patch level 43, the installation no longer requires an enabled QSECOFR.

For more information, see SAP Note 1031096 - Installing Package SAPHOSTAGENT.

Procedure

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

 Note

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

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i 28 PUBLIC Preparation  Recommendation

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

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

3.6 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 installer You always have to download the latest version of the Software Provisioning Manager 1.0 archive. For more information, see Downloading and Extracting the Software Provisioning Manager 1.0 Archive [page 30]. ● Kernel Media.

Installation Media Description

SAP Kernel Non-Unicode (NUC) Kernel (folder K__N_) where N means non-Unicode.

You can provide them in one of the following ways: ○ Download the SAP Kernel Archives (SAR files) from the SAP Software Download Center - this is the recommended way. For more information, see Downloading Installation Archives (Archive-Based Installation) [page 31]. ○ Use the physical installation media as part of the installation package: ○ Download the complete kernel media from the SAP Software Download Center. For more information, see Downloading Complete Installation Media [page 32].

 Note

The signature of installation media is checked automatically by the installer during the Define Parameters phase while the Media Browser screens are processed (see also Running the Installer [page 38] ). The installer only accepts media whose signature has been checked. For more information, see SAP Note 2393060 .

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i Preparation PUBLIC 29 3.6.1 Downloading and Extracting the Software Provisioning Manager 1.0 Archive

You must always download and extract the Software Provisioning Manager 1.0 archive from the SAP Software Download Center because you must use the latest version.

Prerequisites

● Make sure that you use the latest version of the SAPCAR tool when manually extracting the Software Provisioning Manager archive.

 Note

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

Proceed as follows to get the latest version of SAPCAR: 1. Go to https://launchpad.support.sap.com/#/softwarecenter SUPPORT PACKAGES & PATCHES By Category SAP TECHNOLOGY COMPONENTS SAPCAR . 2. Select the archive file for your operating system and download it to an empty directory. 3. To check the validity of the downloaded executable, right-click the executable and choose Properties. On the Digital Signatures tab you can find information about the SAP signature with which the executable was signed. 4. Rename the executable to sapcar.exe. For more information about SAPCAR, see SAP Note 212876 .

Procedure

1. Download the latest version of the Software Provisioning Manager 1.0 archive [70]SWPM10SP_.SAR :

https://support.sap.com/sltoolset System Provisioning Download Software Provisioning Manager 2. If you did not do so already, make sure you have configured your TCP/IP as described in SAP Note 92589 . Afterwards, do not forget 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. 3. Unpack the Software Provisioning Manager archive to a local directory on your Windows PC using the following command:

\sapcar.exe -xvf \[70]SWPM10SP_.SAR -R

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i 30 PUBLIC Preparation  Note

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

 Caution

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

4. 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 Copying the Installation Media Manually to Your IBM i [page 34].

3.6.2 Downloading Installation Archives (Archive-Based Installation)

As an alternative to downloading the complete installation media, you can also download exactly the archives that are required for your installation.

Context

You must download - apart from the Software Provisioning Manager 1.0 archive which is always required for an installation - the SAPEXE .SAR and SAPHOSTAGENT.SAR archive files.

 Note

The SAPHOSTAGENT.SAR archive is only prompted if there is either no SAP Host Agent available on the installation host or you specified during the Define Parameters phase that you want to upgrade an existing version of the SAP Host Agent already available on the installation host. In the latter case, you must specify a higher version of the SAPHOSTAGENT.SAR .Otherwise, the existing SAP Host Agent is not upgraded.

During the installation, you can either specify the path to each archive separately, or provide the path to a download basket with all downloaded archives.

 Note

The signature of installation archives is checked automatically by the installer [page 38] during the Define Parameters phase while processing the Software Package Browser screens. The installer only accepts archives whose signature has been checked. After scanning the archives and verifying the signature, an info file is written where you can find detailed information about matching and non-matching archive files. You can access this info file by choosing the info file link in the Archive Scanning Result section of the Software Package Browser screen. The info file contains only the results of the latest archive scan. For more information, see SAP Note 2393060 .

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i Preparation PUBLIC 31 Procedure

1. Go to https://launchpad.support.sap.com/#/softwarecenter SUPPORT PACKAGES & PATCHES By Category 2. Download the latest patch level of the following software component archives (*.SAR files) from the following paths:

○ SAPEXE .SAR: from the following path: Additional Components SAP Kernel SAP KERNEL 64-BIT 64-BIT> #DATABASE INDEPENDENT ○ SAPHOSTAGENT .SAR: SAP Technology Components SAP HOST AGENT SAP HOST AGENT 7.21

 Note

The SAPHOSTAGENT.SAR archive is only prompted if there is either no SAP Host Agent available on the installation host or you specified during the Define Parameters phase that you want to upgrade an existing version of the SAP Host Agent already available on the installation host. In the latter case, you must specify a higher version of the SAPHOSTAGENT.SAR .Otherwise, the existing SAP Host Agent is not upgraded.

3.6.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. Create a download directory on your Windows host from where you will transfer the media to your IBM i host (for example, C:\tmp\download) 3. You identify the required media as listed in Preparing the Installation Media [page 29] . 4. Identify all download objects that belong to one medium according to one of the following:

 Note

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

○ Download path or location: ○ To download the complete kernel media, go to https://support.sap.com/sltoolset System Provisioning Software Provisioning Manager 1.0 SP Download Kernel

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i 32 PUBLIC Preparation releases delivered for SL Toolset SL TOOLSET 1.0 (INSTALLATIONS AND UPGRADES) KERNEL FOR INSTALLATION/SWPM . ○ To download all media required for your SAP product, you can use one of the following navigation paths: ○ https://launchpad.support.sap.com/#/softwarecenter INSTALLATIONS & UPGRADES By Category SAP NETWEAVER AND COMPLEMENTARY PRODUCTS ○ https://launchpad.support.sap.com/#/softwarecenter INSTALLATIONS & UPGRADES By Alphabetical Index (A-Z) ○ Material number All download objects that are part of an installation medium have the same material number and an individual sequence number: _

 Example

51031387_1

51031387_2

...

○ Title All objects that are part of an installation medium have the same title, such as . 5. Download the objects to the download directory. 6. 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.

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

Related Information

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

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i Preparation PUBLIC 33 3.6.4 Copying the Installation Media Manually to Your IBM i

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

 Note

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

 Note

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

Procedure

Creating a Binary Share on IBM i

If you do not already have a binary share TMPSAP on your IBM i, and you want to copy manually media from your Windows PC into the IFS of your IBM i, you have to create this share manually using the IBM Systems Director Navigator for i. To do so, proceed as follows:

1. Start the IBM Systems Director Navigator for i on your Windows PC. 2. Connect to your IBM i using My Connections. 3. To create or change the share TMPSAP, choose File Systems File Shares . 4. Right-click File Shares Open i5/OS Netserver . A new screen i5/OS Netserver appears. 5. Click the folder Shared Objects to see the shares. 6. To check the already existing share TMPSAP or create a new share TMPSAP, right-click New File .

 Note

The share TMPSAP must have the access permission Read/Write and the path name should be /tmp/ SAP. If the directory /tmp/SAP does not exist directly create it manually as QSECOFR or installation user using the following command:

mkdir /tmp/SAP .

7. On the Text Conversion tab, do not select Allow file text conversion. 8. To save the share TMPSAP, press OK.

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

Copying the Installation Media Manually Using the Binary Share TMPSAP

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i 34 PUBLIC Preparation 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 \\\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: \\\TMPSAP SAP /USER:SAPIUSR X: is now your new network drive to share \\\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 27].

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:

 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:

 Note

You must copy the root directory of the media respectively of the and all required subdirectories to the IFS of your IBM i.

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

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i Preparation PUBLIC 35 4 Installation

4.1 Prerequisites for Running the Installer

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

● For the SL Common GUI, make sure that the following web browser requirements are met: ○ You have one of the following supported browsers on the device where you want to run the SL Common GUI: ○ Google Chrome (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 Common GUI URL manually in the browser window, make sure that you open a new Web browser window in private browsing mode (Internet Explorer), incognito mode (Chrome) or private browsing mode (Firefox). This is to prevent Web browser plugins and settings from interfering with the SL Common GUI.

 Caution

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

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

● If you want to enable Internet Protocol Version 6 (IPv6), make sure that you set SAP_IPv6_ACTIVE=1 in the environment of the user with root authorization which you use to start the installer. While running the installer, this setting is then also added to the environment of the adm user.

 Note

By applying this setting the SAP system administrator is responsible for configuring the IP version on each host of the system landscape, before installing any additional instance to it.

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

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i 36 PUBLIC Installation ● Check the value of the temporary directory set in the environment if available:

Shell Command

Command prompt WRKENVVAR

Qp2Term echo $TEMP, echo $TMP or echo $TMPDIR

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

 Recommendation

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

● Make sure that you have at least 300 MB of free space in the installation directory for each installation option. In addition, you need 300 MB free space for the installer executables. If you cannot provide 300 MB free space in the temporary directory, you can set one of the environment variables TEMP, TMP, or TMPDIR to another directory with 300 MB free space for the installer executables. You can set values for the TEMP, TMP, or TMPDIR environment variable to an alternative installation directory as described in section Useful Information About the Installer [page 41]. ● Make sure that you have defined the most important SAP system parameters as described in Basic Installation Parameters [page 20] before you start the installation. ● 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 installer and the SL Common GUI. If this port cannot be used, you can assign a free port number by executing sapinst with the following command line parameter: SAPINST_HTTPS_PORT=

 Example

CD DIR('')

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

○ Port 4239 is used by default for displaying the feedback evaluation form at the end of the installer processing. The filled-out evaluation form is then sent to SAP using HTTPS. If this port cannot be used, you can assign a free port number by executing sapinst with the following command line parameter: SAPINST_HTTP_PORT=

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i Installation PUBLIC 37 4.2 Running the Installer

This section describes how to run the installer.

Prerequisites

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

Context

The installer has a web browser-based GUI named “SL Common GUI of the Software Provisioning Manager” - “SL Common GUI” for short.

This procedure describes an installation where you run the installer and use the SL Common GUI, that is you can control the processing of the installer from a browser running on any device.

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

Procedure

1. Log on to the installation host as the SAP installation user. For more information, see Preparing the SAP Installation User on IBM i [page 27].

 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 installer 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 sapinst1745524 . 2. Start the installer from the directory to which you unpacked the Software Provisioning Manager archive by entering the following commands:

CD DIR('')

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

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i 38 PUBLIC Installation  Note

If you need to assign a virtual host name to the instance to be installed and you do not want to assign it by entering it as a parameter using the installer screens (see Basic Installation Parameters [page 20]), you can alternatively assign it as follows:

CD DIR('')

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

3. The installer is starting up.

The installer now starts and waits for the connection with the SL Common GUI.

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

... ************************************************************************ Open your browser and paste the following URL address to access the GUI

https://[]:4237/sapinst/docs/index.html

Logon users: []

************************************************************************ ...

 Note

If the host specified by cannot be reached due to a special network configuration, proceed as follows: 1. Terminate the installer as described in Useful Information about the Installer [page 41]. 2. Restart the installer from the command line with the SAPINST_GUI_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 the Installer [page 36]).

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

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i Installation PUBLIC 39 Proceed as follows to get the certificate fingerprint or thumbprint from the server certificate printed in the installer console: 1. Go to the sapinst_exe.xxxxxx.xxxx directory in the temporary directory to which the installer has extracted itself: /home//.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 Common GUI opens in the browser by displaying the Welcome screen. 4. On the Welcome screen, choose the required option:

○ To install a new standalone Gateway instance, choose Installation 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 Generic Options Uninstall and choose Uninstall - SAP Systems or Single Instances 5. Choose Next.  Note

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

6. Follow the instructions on the installer 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.

 Caution

The signature of installation media and installation archives is checked automatically during the Define Parameters phase while processing the Media Browser and - if you perform an archive-based installation - the Software Package Browser screens.

Note that this automatic check is only committed once and not repeated if you modify artifacts 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 signature is not checked again.

For more information, see SAP Note 2393060 .

After you have entered all requested input parameters, the installer displays the Parameter Summary screen. This screen shows both the parameters that you entered and those that the installer set by default. If required, you can revise the parameters before starting the installation.

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i 40 PUBLIC Installation 7. To start the installation, choose Next.

The installer starts the installation and displays the progress of the installation. When the installation has finished, the installer shows the message: Execution of has completed. 8. If you copied the installer software to your hard disk, you can delete these files when the installation has successfully completed. 9. For security reasons, we recommend that you remove the group SAPINST from the operating system users after you have completed the installation.

 Note

This step is only required, if you did not specify during the Define Parameters phase that the group SAPINST is to be removed from the operating system users after the execution of the installer has completed.

10. For security reasons, we recommend that you delete the .sapinst directory within the home directory of the user with which you ran the installer:

/home//.sapinst 11. The installer 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. You find the installer log files in the sapinst_instdir directory. For more information, see Useful Information about the Installer [page 41].

4.3 Additional Information about the Installer

The following sections provide additional information about the installer.

Useful Information about the Installer [page 41] This section contains some useful technical background information about the installer and the installer GUI.

Interrupted Processing of the Installer [page 43] Here you find information about how to restart the installer if its processing has been interrupted.

Troubleshooting with the Installer [page 47] This section tells you how to proceed when errors occur while the installer is running.

Using the Step State Editor (SAP Support Experts Only) [page 48] This section describes how to use the Step State Editor available in the installer.

4.3.1 Useful Information about the Installer

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

● Software Provisioning Manager (the “installer” for short) has the web browser-based “SL Common GUI of the Software Provisioning Manager” - “SL Common GUI” for short.

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i Installation PUBLIC 41 The SL Common GUI 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, Software Provisioning Manager comes with a new look and feel of the SL Common GUI. For more information, see https://blogs.sap.com/2018/11/10/new-look-for- software-provisioning-manager/ . The SL Common GUI connects the web browser on a client with the sapinst executable - which is part of Software Provisioning Manager - running on the installation host using the standard protocol HTTPS. For the SL Common GUI the installer provides a pre-generated URL at the bottom of the shell from which you are running the installer . If you have a supported web browser installed on the host where you run the installer, you can start the SL Common GUI directly from this URL. Otherwise, open a web browser supported by the SL Common GUI on any device and run the URL from there. For more information about supported web browsers see Prerequisites for Running the Installer [page 36]. If you need to run the SL Common GUI in accessibility mode, apply the standard accessibility functions of your web browser.

● As soon as you have started the sapinst executable, the installer creates a .sapinst directory underneath the /home/ directory where it keeps its log files. is the user with which you have started the installer. After you have reached the Welcome screen and selected the relevant installer option for the SAP system or instance to be installed , the installer creates a directory sapinst_instdir where it keeps its log files, and which is located directly below the temporary directory. The installer finds the temporary directory by checking the value of the TEMP, TMP, or TMPDIR environment variable. If no value is set for these variables, the installer uses /tmp 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 installer.

Shell Used Command

Command prompt ADDENVVAR ENVVAR(TEMP) VALUE('') REPLACE(*YES)

Qp2Term export TEMP=

 Note

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

 Caution

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

The installer records its progress in the keydb.xml file located in the sapinst_instdir directory. Therefore, if required, you can continue with the installer from any point of failure, without having to repeat

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i 42 PUBLIC Installation 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 installer. 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 installer extracts itself to the temporary directory. These executables are deleted again after the installer has stopped running. Directories called sapinst_exe.xxxxxx.xxxx sometimes remain in the temporary directory after the installer has finished. You can safely delete them. The temporary directory also contains the log file dev_selfex.out from the self-extraction process of the installer, which might be useful if an error occurs.

 Caution

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

● To see a list of all available installer properties, enter the following commands: CD DIR('') CALL PGM(QP2TERM) PARM('./sapinst' '-p')

● If required, stop the installer by choosing the Cancel button.

 Note

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

4.3.2 Interrupted Processing of the Installer

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

Context

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

● An error occurred during the Define Parameters or Execute phase: The installer does not abort the installation in error situations. If an error occurs, the installation pauses and a dialog box appears. The dialog box contains a short description of the choices listed in the table below as well as a path to a log file that contains detailed information about the error.

● You interrupted the processing of the installer by choosing Cancel in the SL Common GUI.

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i Installation PUBLIC 43  Caution

If you stop an option in the Execute phase, any system or component installed by this option is incomplete and not ready to be used. Any system or component uninstalled by this option is not completely uninstalled.

The following table describes the options in the dialog box:

Option Definition

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

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

Stop The installer stops the installation, closing the dialog box, the installer GUI, and the GUI server.

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

Continue The installer continues the installation from the current point.

View Log Access installation log files.

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

Procedure

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

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

 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. Make sure that the installation media are still available.

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

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i 44 PUBLIC Installation  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.

4. Restart the installer from the installation media directory to which you unpacked the Software Provisioning Manager archive.

Enter the following commands:

CD DIR('')

CALL PGM(QP2TERM) PARM('./sapinst') 5. The installer is restarting.

The installer now starts and waits for the connection with the SL Common GUI.

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

... ************************************************************************ Open your browser and paste the following URL address to access the GUI

https://[]:4237/sapinst/docs/index.html

Logon users: []

************************************************************************ ...

 Note

If the host specified by cannot be reached due to a special network configuration, proceed as follows: 1. Terminate the installer as described in Useful Information about the Installer [page 41]. 2. Restart the installer from the command line with the SAPINST_GUI_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 the Installer [page 36]).

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

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i Installation PUBLIC 45 Proceed as follows to get the certificate fingerprint or thumbprint from the server certificate printed in the installer console: 1. Go to the sapinst_exe.xxxxxx.xxxx directory in the temporary directory to which the installer has extracted itself: /home//.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 Common GUI opens in the browser by displaying the Welcome screen. 6. From the tree structure on the Welcome screen, select the installation option that you want to continue and choose Next.

The What do you want to do? screen appears. 7. 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 installer does not continue the interrupted installation option. Instead, it moves the content of the old installer directory and all installer-specific files to a backup directory. Afterwards, you can no longer continue the old option.

The following naming convention is used for the backup directory:

log______

 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 installer moves all the files and folders to a new log directory, even if these files and folders are owned by other users. If there are any processes currently running on these files and folders, they might no longer function properly.

Continue with the existing one The installer continues the interrupted installation from the point of failure.

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i 46 PUBLIC Installation 4.3.3 Troubleshooting with the Installer

This section tells you how to proceed when errors occur while the installer is running.

Context

If an error occurs, the installer:

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

Procedure

1. Check SAP Note 2393060 for known installer issues. 2. If an error occurs during the Define Parameters or the Execute Service phase, do one of the following:

○ Try to solve the problem: ○ To check the installer log files (sapinst.log and sapinst_dev.log) for errors, choose the LOG FILES tab.

 Note

The LOG FILES tab is only available if you have selected on the Welcome screen the relevant installer 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/ directory, where is the user that you used to start the installer.

For more information, see Useful Information about the Installer [page 41].

○ To check the log and trace files of the installer GUI for errors, go to the directory /home/ /.sapinst/ ○ Then continue by choosing Retry. ○ If required, abort the installer by choosing Cancel in the tool menu and restart the installer. For more information, see Interrupted Processing of the Installer [page 43]. 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 .

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i Installation PUBLIC 47 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 installer.

 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 installer meets the requirements listed in Prerequisites for Running the Installer [page 36].

Procedure

1. Start the installer from the command line as described in Running the Installer [page 38] with the additional command line parameter SAPINST_SET_STEPSTATE=true 2. Follow the instructions on the installer 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 installer during the Execute Service phase. By default all steps are in an initial state. Underneath each step, you see the assigned installer 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 installer to pause. ○ Mark the checkbox in front of the Skip option of the steps which you want the installer 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 installer 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 installer. 5. Continue until you have run through all the steps of the Execute Service phase of the installer.

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i 48 PUBLIC Installation 5 Post-Installation Activities

5.1 Gateway Configuration

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

You can find the configuration documentation in the SAP Library [page 14] at: SAP NetWeaver Library: Function-Oriented View Application Server Infrastructure Connectivity Gateway

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i Post-Installation Activities PUBLIC 49 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 since you do not need to reinstall or reconfigure.

Prerequisites

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

Context

Procedure

Proceed as described in SAP Note 1624061 .

6.2 Starting and Stopping the Instance Manually

Use

You check that you can start and stop the standalone Gateway by entering the commands STARTSAP and STOPSAP.

Procedure

Starting the Instance

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i 50 PUBLIC Additional Information 1. Log on as user adm to the standalone Gateway host. Log on as user adm to the Web Dispatcher host. 2. Enter the SAP system ID (for example, C11) and the instance number (for example, 90). 3. To check whether the instance started successfully, enter the following command: WRKACTJOB SBS(R3_).

Stopping the Instance

1. Log on as user adm to the standalone Gateway host. 2. Enter the following command and choose F4 : STOPSAP 3. Enter the SAP system ID (for example, C11) and the instance number (for example, 90).

6.3 Uninstall

The following procedure describes how to uninstall a standalone Gateway using the installer.

Procedure

1. Start the Installer [page 38]. 2. On the Welcome screen, choose Generic Options Uninstall Uninstall SAP Systems or Single Instances . 3. Follow the instructions in the installer screens.

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i Additional Information PUBLIC 51 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 a 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.

Gender-Related Language

We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i 52 PUBLIC Important Disclaimers and Legal Information Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to 7.5x on IBM i Important Disclaimers and Legal Information PUBLIC 53 www.sap.com/contactsap

© 2021 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