0% found this document useful (0 votes)

9 views202 pages

NW71x ABAPJava

This installation guide provides detailed instructions for installing SAP systems based on the Application Server Dual-Stack (ABAP+Java) of SAP NetWeaver 7.1 to 7.4 on IBM i using Software Provisioning Manager 1.0 SP30. It includes sections on document history, installation options, planning, preparation, and the installation process itself. The guide is intended for users managing out-of-maintenance releases and covers various system configurations and requirements.

Uploaded by

koragi

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

9 views202 pages

NW71x ABAPJava

Uploaded by

koragi

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

Installation Guide | PUBLIC

Software Provisioning Manager 1.0 SP30 (Out-Of-Maintenance Releases)

Document Version: 3.6 – 2020-10-05

Installation of SAP Systems Based on the

Application Server Dual-Stack (ABAP+Java) of
SAP NetWeaver 7.1 to 7.4 Support Release 2 (Out-
© 2021 SAP SE or an SAP affiliate company. All rights reserved.

Of-Maintenance Releases) on IBM i : IBM Db2 for i

THE BEST RUN

Content

1 Document History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2 About this Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2.1 SAP Product Releases Out-Of-Maintenance, Based on SAP NetWeaver 7.1 to 7.4 Support Release 2
Supported for Installation Using Software Provisioning Manager 1.0 for Out-Of-Maintenance
Product Releases ( SWPM10RMSP30_<Version>.SAR). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.2 Naming Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.3 Constraints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
2.4 Before You Start. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.5 SAP Notes for the Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.6 New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3 Installation Options Covered by this Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

3.1 Standard System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.2 Distributed System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.3 High-Availability System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.4 Additional Application Server Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.5 Splitting off an ABAP Central Services Instance from an Existing Primary Application Server
Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.6 ASCS Instance with Integrated SAP Web Dispatcher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.7 ASCS Instance with Integrated Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

4 Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.1 Planning Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.2 Changed File System Structure and Profiles for SAP Systems Based on SAP NetWeaver 7.1 and
Higher. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.3 Hardware and Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Running the Prerequisites Check in Standalone Mode (Optional). . . . . . . . . . . . . . . . . . . . . . . . 35
Requirements for the SAP System Hosts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.4 Planning User and Access Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
4.5 Planning for Independent ASPs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
4.6 Basic Installation Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
SAP System Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
SAP System Database Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Parameters for Additional Components to be Included in the ASCS Instance. . . . . . . . . . . . . . . . 57
4.7 SAP System Transport Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58
4.8 Planning the Switchover Cluster for High Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

5 Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
2 PUBLIC Content
5.1 Preparation Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
5.2 Required File Systems and Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
SAP Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
5.3 Using Virtual Host Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
5.4 Performing Switchover Preparations for High Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
5.5 Preparation for IBM i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Installing the Toolbox JDBC Driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Checking the Transport Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Qp2Term, Qp2Shell, and the Portable Application Solution Environment. . . . . . . . . . . . . . . . . . . 74
Installing the Qshell. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Checking and Adjusting Operating System Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Adjusting Startup Program QSTRUP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Adding a User ASP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Configuring TCP/IP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Adjusting the Relational Database Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Installing English as a Secondary Language. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Preparing the SAP Installation User on IBM i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Enable the User QSECOFR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Distribution of Libraries on ASPs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
5.6 Installing the SAP Front-End Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
5.7 Preparing the Installation Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Media Required for the Installation - Listed by SAP System Instance. . . . . . . . . . . . . . . . . . . . . . 95

6 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
6.1 Installation Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
6.2 Linking Global Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
6.3 Specifying the Initial Data Source of the User Management Engine. . . . . . . . . . . . . . . . . . . . . . . . . 115
6.4 Prerequisites for Running the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
6.5 Running the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
6.6 Additional Information about the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121
Useful Information about the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122
Interrupted Processing of the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Entries in the Services File Created by the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127
Troubleshooting with the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Troubleshooting During the Database Load. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Using the Step State Editor (SAP Support Experts Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

7 Post-Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
7.1 Post-Installation Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
7.2 Logging On to the Application Server ABAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
7.3 Logging On to the Application Server Java. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
7.4 Providing Access to the SAP NetWeaver Administrator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
Content PUBLIC 3
7.5 Installing the SAP License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
7.6 High Availability: Setting Up Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
7.7 Configuring the Remote Connection to SAP Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
7.8 Enabling Note Assistant to Apply Note Corrections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139
7.9 Configuring Documentation Provided on the SAP Help Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
7.10 Performing the Consistency Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
7.11 Setting Up a Secondary Host for IASP Switchover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142
7.12 Setting Up the Transport Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
7.13 Configuring the Change and Transport System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145
7.14 Connecting the System to SAP Solution Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
7.15 Applying the Latest Kernel and Support Package Stacks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
7.16 Performing Post-Installation Steps for the ABAP Application Server. . . . . . . . . . . . . . . . . . . . . . . . 149
7.17 Installing Additional Languages and Performing Language Transport. . . . . . . . . . . . . . . . . . . . . . . 151
7.18 SAP Kernel 7.40 and Higher: IP Multicast Configuration and Wake-Up Mechanism. . . . . . . . . . . . . . 153
7.19 Configuring the User Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
7.20 Ensuring User Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
7.21 Performing Automated Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
7.22 Production Client Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
7.23 Performing the Client Copy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
7.24 SAP Systems Based on SAP NetWeaver 7.4 and Higher: Changing Keys for the Secure Storage
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
7.25 Removing the Installer Installation Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
7.26 Performing a Full Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
7.27 Logging on to the SAP Web Dispatcher Management Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
7.28 SAP Web Dispatcher Configuration (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
7.29 Gateway Configuration (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166

8 Additional Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

8.1 Integration of LDAP Directory Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
8.2 Multiple SAP Systems on a Single Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
8.3 Creating a User for LDAP Directory Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174
8.4 Installing the SAP Host Agent Separately. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
8.5 Splitting Off an ABAP Central Services Instance from an Existing Primary Application Server
Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
8.6 Starting and Stopping SAP System Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177
Starting and Stopping SAP System Instances Using the SAP Management Console. . . . . . . . . . 178
Starting and Stopping the SAP System Using Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . .181
8.7 IBM i-specific Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Correcting Errors in RFC Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
IBM i Library Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
IBM i Integrated File System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Restoring a Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187

A Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
A.1 Online Information from SAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

 Note

Before you start reading, make sure you have the latest version of this installation guide, which you can
download from from SAP Note 2980160 .

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

Version Date Description

3.7.1 2021-01-11 Updated version for Software Provisioning Manager 1.0 SP30 (SL Toolset 1.0 SP30)

● New Features:
○ Introducing SWPM10RMSP30_<Version>.SAR for Out-Of-Maintenance Products,
documented in: About this Document, New Features, Downloading and Extracting
the Software Provisioning Manager 1.0
(SWPM10RMA73J74SP30_<Version_Number>.SAR) Archive

3.7 2020-10-05 Updated version for Software Provisioning Manager 1.0 SP30 (SL Toolset 1.0 SP30)

3.6 2020-06-08 Updated version for Software Provisioning Manager 1.0 SP29 (SL Toolset 1.0 SP29)

3.5 2020-01-20 Updated version for Software Provisioning Manager 1.0 SP28 (SL Toolset 1.0 SP28)

3.4 2019-09-16 Updated version for Software Provisioning Manager 1.0 SP27 (SL Toolset 1.0 SP27)

3.3 2019-05-27 Updated version for Software Provisioning Manager 1.0 SP26 (SL Toolset 1.0 SP26)

3.2 2019-01-21 Updated version for software provisioning manager 1.0 SP25 (SL Toolset 1.0 SP25)

3.1 2018-09-17 Updated version for software provisioning manager 1.0 SP24 (SL Toolset 1.0 SP24)

● New Features:
New Look and Feel of SL Common GUI with Software Provisioning Manager 1.0 SP24,
Patch Level 05, documented in: New Features, Prerequisites for Running the Installer

3.0 2018-05-07 Updated version for software provisioning manager 1.0 SP23 (SL Toolset 1.0 SP23)

2.9 2018-01-15 Updated version for software provisioning manager 1.0 SP22 (SL Toolset 1.0 SP22)

● New Features:
○ Signature check for installation archives, documented in: New Features, Download
ing SAP Kernel Archives (Archive-Based Installation) Archive-Based Installation for
Diagnostics Agent, Downloading the SAP Kernel Archives Required for the Dual-Stack
Split (Without Operating System and Database Migration), Downloading the SAP
Kernel Archives Required for Operating System and Database Migration
○ Installer Log Files Improvements, documented in: New Features, Useful Information
about the Installer, Troubleshooting with the Installer
○ Secure ABAP message server connection, documented in: New Features, SAP Sys
tem Parameters
○ 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 Com
mon 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 com
pletely removed from this documentation: Performing a Remote Installation Remote
Processing of the Installer ( Java SDT GUI only), Starting the Java SDT GUI Sepa
rately, Running the Installer in Accessibility Mode (general accessibility information
was moved to Useful Information About the Installer).
○ The Java SDT GUI-specific information was removed from the common installer
sections: Running the Installer, Useful Information About the Installer, Interrupted
Processing of the Installer, Troubleshooting with the Installer, Deleting an SAP Sys
tem or Single Instances
● New section Using the Step State Editor (SAP Support Experts Only) was added to sec
tion Additional Information About the Installer

2.8 2017-09-11 Updated version for software provisioning manager 1.0 SP21 (SL Toolset 1.0 SP21)

● New Features:
○ Media Signature Check, documented in: New Features, Running the Installer, Prepar
ing the Installation Media .
This feature implies that section Creating Kernel Archives from an Existing SAP Sys
tem has been deleted from this documentation because the related option in the in
staller had to be removed.
○ SAP Host Agent Upgrade , documented in: New Features, SAP System Parameters,
Downloading SAP Kernel Archives (Archive-Based Installation)
○ Load tools are now available as LOADTOOLS.SAR in the Software Provisioning Man
ager archive, documented in: New Features, Downloading and Extracting the Soft
ware Provisioning Manager Archive

2.7 2017-05-22 Updated version for software provisioning manager 1.0 SP20 (SL Toolset 1.0 SP20)

● New Features:
○ New SAPUI5-based graphical user interface (GUI) “SL Common GUI”, documented
in: Prerequisites for Running the Installer, Running the Installer, Useful Information
About the Installer
○ Option for choosing to install an integrated SAP Gateway during the ASCS instance
installation, documented in: Installation Options Covered by this Guide, SAP System
Parameters, Parameters for Additional Components to be Included in the ASCS In
stance , Post-Installation Checklist, SAP Gateway Configuration
○ Cleanup of operating system users, documented in: SAP System Parameters, Creat
ing Operating System Users and Groups

2.6 2017-02-06 Updated version for software provisioning manager 1.0 SP19 (SL Toolset 1.0 SP19)

● New Features:
Verification of the integrity of data units in Software Provisioning Manager, documented
in: New Features, Downloading the Software Provisioning Manager Archive

2.5 2016-10-07 Updated version for software provisioning manager 1.0 SP18 (SL Toolset 1.0 SP18)

● New Features:
Option to choose installing an integrated SAP Web Dispatcher during the ASCS instance
installation, documented in: ASCS Instance with Integrated SAP Web Dispatcher.

2.4 2016-06-06 Updated version for software provisioning manager 1.0 SP17 (SL Toolset 1.0 SP17)

● New Features:
“ Archive-Based Installation”, documented in:
○ New Features [page 16]

○ Preparing the Installation Media [page 94] Downloading Specific Installation

Archives (Archive-Based Installation)

2.3 2016-02-15 Updated version for software provisioning manager 1.0 SP10 (SL Toolset 1.0 SP16)

2.2 2015-10-12 Updated version for software provisioning manager 1.0 SP09 (SL Toolset 1.0 SP15)

2.1 2015-09-14 Updated version for software provisioning manager 1.0 SP09 (SL Toolset 1.0 SP14)

1.9 2015-04-27 Updated version for software provisioning manager 1.0 SP08 (SL Toolset 1.0 SP13)

1.8 2015-11-24 Updated version for software provisioning manager 1.0 SP07 (SL Toolset 1.0 SP12)

1.7 2014-07-07 Updated version for software provisioning manager 1.0 SP06 (SL Toolset 1.0 SP11)

1.6 2014-03-17 Updated version for software provisioning manager 1.0 SP05 (SL Toolset 1.0 SP10)

1.5 2013-11-28 Updated version

1.4 2013-11-13 Updated version

1.3 2013-10-28 Updated version

1.2 2013-10-27 Updated version

1.1 2013-09-25 Updated version

1.0 2012-08-06 First version for Software Provisioning Manager 1.0

This installation guide describes how to install SAP systems for out-of-maintenance product versions based on
SAP Process Integration on SAP NetWeaver 7.1 to 7.4 Support Release 2, using the installation tool Software
Provisioning Manager 1.0 ( SWPM10RMSP30_<Version>.SAR), “installer” for short, which is part of SL Toolset
1.0 SP30. An SAP Process Integration system is a dual-stack (ABAP+Java) system comprising both an ABAP
and a Java stack under one common SAP system ID (<SAPSID>).

 Note

Application Server ABAP based on SAP NetWeaver 7.10, 7.11, 7.20, 7.30, 7.40 SR1 are supported in
mainstream maintenance only until the end of 2020. Extended maintenance will not be provided.

Application Server Java based on SAP NetWeaver 7.10, 7.11, 7.20, 7.30, 7.31, 7.40, 7.40 SR1, 7.40 SR2 (except
SAP Solution Manager 7.2 SR2 Java) are supported in mainstream maintenance only until the end of 2020.
Extended maintenance will not be provided.

For more information, see SAP Note 2980160 .

You can download the last published version of the guide set for the last Software Provisioning Manager 1.0
SP30 for out-of-maintenance products (SWPM10RMSP30_<Version>.SAR) from SAP Note 2980160 .
This guide set covers only the SAP product versions which have reached end of maintenance.

 Note

As an alternative to using Software Provisioning Manager, you can install your system with a completely
automated end-to-end framework available using SAP Landscape Management. For more information, see
SAP Note 1709155 and https://help.sap.com/lama .

This guide covers the SAP system products and releases listed in SAP Product Releases Out-Of-Maintenance,
Based on SAP NetWeaver 7.1 to 7.4 Support Release 2 Supported for Installation Using Software Provisioning
Manager 1.0 for Out-Of-Maintenance Product Releases ( SWPM10RMSP30_<Version>.SAR) [page 11] and
SAP Note 2980160 .

For information about maintenance of SAP Business Suite and corresponding SAP NetWeaver versions, see
SAP Note 1648480 .

For information about supported operating system and database platforms for the SAP product you want to
install, see the Product Availability Matrix at http://support.sap.com/pam

 Caution

Make sure you have read Before You Start [page 14] before you continue with this installation guide.

SAP Product Releases Out-Of-Maintenance, Based on SAP NetWeaver 7.1 to 7.4 Support Release 2
Supported for Installation Using Software Provisioning Manager 1.0 for Out-Of-Maintenance Product
Releases ( SWPM10RMSP30_<Version>.SAR) [page 11]
Here you can find a list of the SAP product releases that have reached out-of-maintenance, based on
SAP NetWeaver 7.1 to 7.4 Support Release 2 Dual Stack that are supported for installation, using
Software Provisioning Manager 1.0 for Out-Of-Maintenance Product Releases

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
10 PUBLIC About this Document
( SWPM10RMSP30_<Version>.SAR), on the specific operating system and database combination
described in this guide.

Naming Conventions [page 12]

This section lists the naming conventions that are currently apply for Software Provisioning Manager
1.0 (the “installer”) and terms used in this documentation.

Constraints [page 13]

This section lists the naming constraints that are currently valid for Software Provisioning Manager 1.0
(the “installer”) and this documentation.

Before You Start [page 14]

Make sure that you have read the release-specific “Master Guide” for your SAP NetWeaver application
before you continue with this installation guide.

SAP Notes for the Installation [page 15]

This section lists the most important SAP Notes relevant for an installation using Software Provisioning
Manager

New Features [page 16]

This section provides an overview of the new features in Software Provisioning Manager 1.0
(the“ installer” for short), until the introduction of SWPM10RMSP30_<Version>.SAR for Out-Of-
Maintenance Products.

2.1 SAP Product Releases Out-Of-Maintenance, Based on

SAP NetWeaver 7.1 to 7.4 Support Release 2 Supported
for Installation Using Software Provisioning Manager
1.0 for Out-Of-Maintenance Product Releases
( SWPM10RMSP30_<Version>.SAR)

Here you can find a list of the SAP product releases that have reached out-of-maintenance, based on SAP
NetWeaver 7.1 to 7.4 Support Release 2 Dual Stack that are supported for installation, using Software
Provisioning Manager 1.0 for Out-Of-Maintenance Product Releases ( SWPM10RMSP30_<Version>.SAR), on
the specific operating system and database combination described in this guide.

Based on the following SAP NetWeaver Re

SAP Product lease

SAP NetWeaver 7.4 Support Release 2 SAP NetWeaver 7.4

SAP Enhancement Package 1 for SAP NetWeaver 7.3 SAP NetWeaver 7.3

SAP NetWeaver 7.3 SAP NetWeaver 7.3

SAP NetWeaver Process Integration 7.1 EHP1 SAP NetWeaver 7.1 EHP1

SAP NetWeaver Process Integration 7.1 SAP NetWeaver 7.1

 Note
SAP NetWeaver Process Integration 7.1 Java comprises the following
optional standalone units:

2.2 Naming Conventions

This section lists the naming conventions that are currently apply for Software Provisioning Manager 1.0 (the
“installer”) and terms used in this documentation.

● Software Provisioning Manager 1.0 is the successor of the product- and release-specific delivery of
provisioning tools, such as “SAPinst”.
Before you perform an installation from scratch or a target system installation in the context of a system
copy, we strongly recommend that you always download the latest version of the Software Provisioning
Manager 1.0 which is part of the Software Logistics Toolset 1.0 (“SL Toolset” for short). For more
information, see Preparing the Installation Media [page 94].
This way, you automatically get the latest version with the latest fixes of the tool and supported processes.
For more information about Software Provisioning Manager 1.0 as well as products and releases supported
by it, see SAP Note 1680045 and https://wiki.scn.sap.com/wiki/display/SL/Software+Provisioning
+Manager+1.0+and+2.0 .
“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
○ Names of executables, for example sapinst
○ Names of command line parameters, for example SAPINST_STACK_XML
○ Names of operating system user groups, such as the additional group sapinst
● “usage type”, “technical usage”, and “product instance”
As of Software Provisioning Manager 1.0 SP07 (SL Toolset 1.0 SP12), the term “product instance” replaces
the terms “ usage type” and “technical usage” for SAP systems based on SAP NetWeaver 7.3 including
enhancement package 1 and higher. For more information, see SAP Note 1970349 . Note that there is no
terminology change for older releases and all mentioned terms can be used as synonyms. As this guide is a
generic document, the currently used terms remain but only “product instance” is used from now on when
referring to SAP NetWeaver 7.3 EHP1 and higher.
For more information, see New Features [page 16].
● “installer” refers to “Software Provisioning Manager”.
● “SAP system” refers to SAP system based on the application server of SAP NetWeaver PI 7.1 / 7.1 including
Enhancement Package 1 / SAP NetWeaver 7.3 / 7.3 including Enhancement Package 1 / SAP NetWeaver
7.4.

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
12 PUBLIC About this Document
● “ABAP+Java system” refers to SAP NetWeaver PI 7.1 / 7.1 including Enhancement Package 1 / SAP
NetWeaver 7.3 / 7.3 including Enhancement Package 1 / SAP NetWeaver 7.4 or SAP NetWeaver PI 7.1 / 7.1
including Enhancement Package 1 / SAP NetWeaver 7.3 / 7.3 including Enhancement Package 1 / SAP
NetWeaver 7.4 / 7.4 SR1 (for Process Integration) system.
● “Diagnostics Agent” refers to the SAP Solution Manager Diagnostics Agent which is the remote component
of End-to-End Root Cause Analysis. It allows having a connection between SAP Solution Manager and
managed systems, and then to collect information from the managed systems for reporting purposes.
● SAP System ID
The “SAP system ID” is abbreviated to “SID” and “SAPSID” or “sid” and “sapsid”. For <sid>/<sapsid>,
substitute your SAP system ID in lowercase characters, for example, “prd”. For <SID>/<SAPSID>,
substitute your SAP system ID in uppercase characters, for example, “PRD”.
● Operating System Names
As of operating system version IBM i 5.4, the operating system has been renamed from “IBM i5/OS” to
“IBM i” (short form: “i”). The names of previous operating system versions remain unchanged.
In this document, the name“IBM i” is used if we do not refer to a specific operating system version. If we
refer to a specific version, we use the relevant operating system name.
● Database Names
As of operating system version IBM i 5.4, the database has been renamed from “IBM DB2 for i5/OS” to
“IBM Db2 for i”. In previous SAP documents, “IBM Db2 for i” was referred to as “IBM DB2 for i5/OS”, “IBM
DB2 Universal Database for iSeries”, “IBM DB2 Universal Database for AS/400” or “DB2/400”.

2.3 Constraints

This section lists the naming constraints that are currently valid for Software Provisioning Manager 1.0 (the
“installer”) and this documentation.

 Note

Application Server ABAP based on SAP NetWeaver 7.10, 7.11, 7.20, 7.30, 7.40 SR1 are supported in
mainstream maintenance only until the end of 2020. Extended maintenance will not be provided.

For more information, see SAP Note 2980160 .

● Not all SAP NetWeaver releases or SAP Business Suite applications that are available in Software
Provisioning Manager 1.0 and are described in this installation guide have already been released. Always
check the list of supported products [page 11] and SAP Note 1680045 to ensure that the installation
options you want to perform are already supported. For information about supported operating system
and database platforms, see the Product Availability Matrix at http://support.sap.com/pam .
● Note that a complete system installation from scratch is not available for every product. For some products
- such as SAP NetWeaver 7.4 - a complete new system installation from scratch is only provided for the

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
About this Document PUBLIC 13
highest support release. If there are one or more support releases, then a complete system installation is
only available for the highest of these support releases. As for the lower support releases, only options for
system copy and additional application server instances are provided.
● Your operating system platform must be 64-bit.
● The installation of dual-stack SAP Business Suite and optional dual-stack application systems is not
supported.
By way of exception, dual-stack implementations can still exist in former SAP Process Integration
installations. However, note that a single-stack SAP Process Integration Java (Advanced Adapter Engine
Extended) exists that offers almost all features of classical dual-stack implementations. Therefore, you
should investigate, if a Java-only implementation of SAP PI is a feasible approach for your use cases. Due
to the harmonized process orchestration stack (SAP PI and SAP BPM running on the same Java instance),
stateful system-centric processes can be developed using SAP Process Orchestration capabilities.
Processes that are created with ccBPM need to be redesigned and modeled with SAP BPM. For more
information about how to do this, see the SAP Community Network at: http://scn.sap.com/docs/
DOC-28803
For more information about the discontinuation of optional dual-stack deployments, see the SAP
Community Network at: http://scn.sap.com/docs/DOC-33703

2.4 Before You Start

Make sure that you have read the release-specific “Master Guide” for your SAP NetWeaver application before
you continue with this installation guide.

The “Master Guide” is the central document leading you through the overall implementation process for your
SAP system installation. It contains crucial information about the overall implementation sequence, that is
activities you have to perform before and after the installation process described in this installation guide.

You can find a printed version of this guide in your installation package or you can download the latest version
from https://help.sap.com.

The following table lists the “Master Guide” of the SAP system application for which you can use this
installation guide, along with the available quick link or path to the appropriate download location:

Document Internet Address

Master Guide – SAP NetWeaver 7.4 http://help.sap.com/nw74

Installation and Upgrade

Master Guide – SAP Enhancement Package 1 for http://help.sap.com/nw731

SAP NetWeaver 7.3
Installation and Upgrade

Master Guide – SAP NetWeaver 7.3 http://help.sap.com/nw73

Installation and Upgrade

Master Guide - SAP NetWeaver PI 7.1 http://help.sap.com/nwpi71

Installation and Upgrade

2.5 SAP Notes for the Installation

This section lists the most important SAP Notes relevant for an installation using Software Provisioning
Manager

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

2980160 Release Note for Software Provisioning Man Covers No Longer Supported Java and Dual-
ager 1.0 for out-of-maintenance releases Stack Options and Access to Guides for Software
( SWPM10RMSP30_<Version>.SAR) Provisioning Manager 1.0 Java and Dual Stack

1680045 Release Note for Software Provisioning Man Software Provisioning Manager 1.0 with installa
ager 1.0 tion and system copy for SAP NetWeaver-based
systems

737368 Hardware requirements of Java Development Information on the hardware requirements for
Infrastructure Java Development Infrastructure, which depends
on the size of your development team

73606 Supported Languages and Code Pages Information on possible languages and language
combinations in SAP systems

1067221 Composite SAP Note for heterogeneous instal This SAP Note and its related SAP Notes describe
lation the released operating system and database
combinations for heterogeneous SAP systems
landscapes.

789220 Support Package levels for SAP NetWeaver in Information about the ABAP Support Package
stallations/upgrades levels and kernel patch levels contained in the
current SAP NetWeaver release

1990240 Support of mixed landscapes (Unicode and Temporarily your system landscape is mixed with
Non-Unicode) Unicode and Non-Unicode systems. You have
third party software in your system landscape
which does not support Unicode at all. You won
der whether such a heterogeneous system land
scape is supported without restrictions.

886535 Downloading multispanning archives Downloading multispanning archives

2.6 New Features

This section provides an overview of the new features in Software Provisioning Manager 1.0 (the“ installer” for
short), until the introduction of SWPM10RMSP30_<Version>.SAR for Out-Of-Maintenance Products.

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

Introducing SWPM10RMSP30_<Version>.SAR replaces SWPM 1.0 SP30 (SL Toolset 1.0

SWPM10RMSP30_<V SWPM10SP<Support_Package_Number>_<Version_Number> SP30)
ersion>.SAR for .SAR for SAP products which have reached out-of-maintenance.
Out-Of-Maintenance For more information, see SAP Note 2980160 .
Products

Support the IASP of The SWPM now supports the installation of SAP systems using an SWPM 1.0 SP30 (SL Toolset 1.0
the type User-De IASP of the type UDFS. An IASP of the type UDFS is required when SP30)
fined File System you want to run an SAP system with IBM Db2 Mirror for i. For
(UDFS). The two more information about IBM Db2 Mirror for i, see the SAP Note
other types primary 2808345 . For more information about the IASP, see Planning
IASP and secondary for Independent ASPs [page 44].
IASP were already
supported.

Configuring the You can now enter the number of work processes interactively Software Provisioning Manager
Number of Work 1.0 SP30 (SL Toolset 1.0 SP30
when performing an installation in custom mode.
Processes during
the Installation For more information, see Basic Installation Parameters [page
46].

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.

Homogeneous Sys The SAP system copy on IBM i now supports existing SAP data Software Provisioning Manager
tem Copy using ex base libraries to create a new SAP system. For more information, 1.0 SP26 (SL Toolset 1.0 SP26)
isting SAP database see the SAP system copy guide, section IBM Db2 for i-Specific
library Procedure . In addition, the SAP Uninstall now supports the option
to leave the SAP database library(ies) when the entire SAP sys
tem is deleted. For more information, see Uninstalling an SAP
System or Single Instances [page 191] .

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

Secure ABAP Mes The installer now uses secure connections to the ABAP message Software Provisioning Manager
1.0 SP22 (SL Toolset 1.0 SP22)
sage Server Con server of the SAP system being installed. For more information,
nection see the ABAP Message Server Port entry within the Ports table in
SAP System Parameters [page 47].

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 122] and Troubleshooting with the
Installer [page 128].

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 SAP Kernel Archives (Ar
chive-Based Installation) [page 101] .

LOADTOOLS.SAR The load tools in Software Provisioning Manager

archive in Software 1.0 SP22 (SL Toolset 1.0 SP22)
SWPM10SP<Support_Package_Number>_<Version_Number>
Provisioning Man
.SAR are now also enabled for an installation using non-Unicode
ager enabled for
NUC (NUC) SAP kernel version 7.40 or higher.

For more information, see Downloading and Extracting the Soft

ware Provisioning Manager 1.0 (SWPM10RMSP30_Version.SAR)
Archive [page 99]

 Note
This feature enhances feature LOADTOOLS.SAR archive in
Software Provisioning Manager of Software Provisioning Man
ager 1.0 SP21 (SL Toolset 1.0 SP21) (see entry
LOADTOOLS.SAR archive in Software Provisioning Manager
below in this table).

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

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

94] and Running the Installer [page 118].

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 the General Parame
ters table in SAP System Parameters [page 47] .

LOADTOOLS.SAR An up-to-date version of the load tools - such as R3load, Software Provisioning Manager
archive in Software R3szchk, R3ldctl, SAPuptool - which were available so far only 1.0 SP21 (SL Toolset 1.0 SP21)
Provisioning Man in the SAPEXEDB.SAR archive of the kernel media, has now been
ager made available in the Software Provisioning Manager archive. For
an installation using Unicode kernel version 7.40 or higher, the
load tools from the
SWPM10SP<Support_Package_Number>_<Version_Number>
.SAR are used automatically.

For more information, see Downloading and Extracting the Soft

ware Provisioning Manager 1.0 (SWPM10RMSP30_Version.SAR)
Archive [page 99]

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 122], Running the Installer [page 118] .

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 SAP System

Parameters [page 47].

Option to install an You can now install an SAP Gateway in an ASCS instance. You can Software Provisioning Manager
SAP Gateway in an choose this option while running the ASCS instance installation. 1.0 SP20 (SL Toolset 1.0 SP20)
ASCS instance
For more information, see ASCS Instance with Integrated Gate
way [page 30]

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
ing Manager
(SWPM10RMSP30_Version.SAR) Archive [page 99] .

In addition, check SAP Note 1680045 whether additional infor

mation is available.

Option to install an You can now install an SAP Web Dispatcher in an ASCS instance. Software Provisioning Manager
SAP Web Dispatcher You can choose this option while running the ASCS instance in 1.0 SP18 (SL Toolset 1.0 SP18)
in an ASCS instance stallation.

For more information, see ASCS Instance with Integrated SAP

Web Dispatcher [page 29]

Archive-Based In You can now download the required installation archives instead Software Provisioning Manager
stallation of the complete SAP kernel installation media. For more informa 1.0 SP17 (SL Toolset 1.0 SP17)
tion, see section Downloading Specific Installation Archives (Ar
chive-Based Installation) in Preparing the Installation Media [page
94] .

Diagnostics Agent The Diagnostics Agent is no longer installed automatically with Software Provisioning Manager
the SAP system. The Install Diagnostics Agent check box on the 1.0 SP10 (SL Toolset 1.0 SP16)
Install Diagnostics Agent screen is no longer available.

You now have to install the Diagnostics Agent always separately.

We recommend that you install it prior to the installation of your
SAP system(s).

For more information, see the Diagnostics Agent Installation

Strategy attached to SAP Note 1365123 , to SAP Note 1833501
, and to SAP Note 1858920 and the attached Diagnostics
Agent Setup Guide.

Creating Kernel Ar You can reuse the binaries of a dedicated SAP system for a new Software Provisioning Manager
chives from existing SAP system installation or target system installation in the con 1.0 SP09 (SL Toolset 1.0 SP14)
SAP System text of a system copy by creating *.SAR archives based on the
*.lst files from the executable (exe) directories of the source
SAP system.

 Note
This feature is only available for Unicode systems.

 Caution
This feature has been deprecated with Software Provisioning
Manager 1.0 SP21 (SL Toolset 1.0 SP21) and the related op
tion has been removed from the Welcome screen. This depre
cation has been accomplished to ensure compliancy with the
new feature “Media Signature Check” of Software Provision
ing Manager 1.0 SP21 (SL Toolset 1.0 SP21) described above
in this table.

Usage Type Library Software Provisioning Manager 1.0 no longer uses the “Usage Software Provisioning Manager
Deprecation for SAP Types” definitions in its business logic for SAP systems based on 1.0 SP07 (SL Toolset 1.0 SP12)
Systems Based on SAP NetWeaver 7.3 EHP1 and higher. This is done to unify model
SAP NetWeaver 7.3 ing and terminology across all SAP tools used during the plan
EHP1 and Higher ning, installation and maintenance activities. The “Product In
stance” definition replaces “Usage Types” regarding product
modeling. For more information, see SAP Notes 1970349 and
1877731 .

Adaptive Installation You can assign virtual host names to SAP system instances during Software Provisioning Manager
the input phase of the installation directly on the screens where 1.0 SP07 (SL Toolset 1.0 SP12)
you define the instance parameters.

For more information, see SAP System Parameters [page 47].

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. For
more information, see Prerequisites for Running the Installer
[page 115].

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 91] and Enable
the User QSECOFR [page 93] .

This section shows the installation options covered by this installation guide. You have to decide what exactly
you want to install because the steps you have to perform vary according to the installation option you choose.

After you have decided on the installation option that you want to use, continue with Planning [page 32].

Standard System [page 22]

Distributed System [page 23]

High-Availability System [page 24]

Additional Application Server Instance [page 25]

Splitting off an ABAP Central Services Instance from an Existing Primary Application Server Instance [page
28]

ASCS Instance with Integrated SAP Web Dispatcher [page 29]

ASCS Instance with Integrated Gateway [page 30]

3.1 Standard System

You can install a standard system on a single host.

In a standard system, all main instances run on a single host.

There are the following instances:

● ABAP Central services instance (ASCS instance)

Contains the ABAP message server and the Standalone Enqueue Server
○ Optionally, you can install the ASCS instance with an integrated SAP Web Dispatcher. For more
information, see ASCS Instance with Integrated SAP Web Dispatcher [page 29].
○ Optionally, you can install the ASCS instance with an integrated gateway. For more information, see
ASCS Instance with Integrated Gateway [page 30].
● Central services instance (SCS instance)
Contains the Java message server and the Java enqueue server
● Database instance (DB)
The ABAP stack and the Java stack use their own database schema.
● Primary application server instance (PAS instance)

3.2 Distributed System

An SAP system consists of SAP instances. An SAP instance is a group of processes that are started and
stopped at the same time.

In a distributed system, every instance can run on a separate host, with the exception of the ASCS instance
and the SCS instance. The ASCS instance and the SCS instance must run on the same host:

● ABAP Central services instance (ASCS instance)

The graphics below assume that you use the global directories of the ASCS instance and SCS instance as
global file system. That means that the host with the ASCS and SCS is the SAP global host. However, you can
also separately install the global directories on any host of your SAP system landscape.

You can also use the SAP transport host or the host with the global file system (SAP global host) as your
primary application server instance host.

Optionally, you can install one or more additional application server instances. For more information, see
Installation of an Additional Application Server Instance [page 25].

3.3 High-Availability System

An SAP system consists of SAP instances. An SAP instance is a group of processes that are started and
stopped at the same time.

In a high-availability system, every instance can run on a separate host.

There are the following instances:

● ABAP central services instance (ASCS instance)

Contains the ABAP message server and the Standalone Enqueue Server
○ Optionally you can install the ASCS instance with an integrated SAP Web Dispatcher. For more
information, see ASCS Instance with Integrated SAP Web Dispatcher [page 29].
○ Optionally you can install the ASCS instance with an integrated gateway. For more information, see
ASCS Instance with Integrated Gateway [page 30].
● ERS instance for the ASCS instance (mandatory)
The ERS instance contains the replication table, which is a copy of the lock table of the Standalone
Enqueue Server in the ASCS instance.
● Central services instance (SCS instance)
Contains the Java message server and the Java enqueue server
● ERS instance for the SCS instance (mandatory)
The ERS instance contains the replication table, which is a copy of the lock table in the SCS instance.
● Database instance (DB)
The ABAP stack and the Java stack use their own database schema in the same database.
● Primary application server instance (PAS)

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
24 PUBLIC Installation Options Covered by this Guide
The graphics below each assumes that you run the ASCS instance, the SCS instance, and the related ERS
instances on the switchover cluster infrastructure. However, you can also run other SAP system instances that
are a single point of failure (SPOF) on a switchover cluster infrastructure, for example the database instance.

We recommend that you run both the ASCS instance and the SCS instance in a switchover cluster
infrastructure. Both the ASCS instance and the SCS instance must each have their own ERS instance.

To increase high availability by creating redundancy, we recommend that you install additional application
server instances on hosts different from the primary application server instance host. For more information,
see Installation of an Additional Application Server Instance [page 25].

The following figure shows an example for the distribution of the SAP system instances in a high-availability
system.

High-Availability System

3.4 Additional Application Server Instance

You can install one or more additional application server instances for an existing SAP system. Additional
application server instances are optional and can be installed on separate hosts.

An additional application server instance can run on:

● The host of any instance of the existing SAP system (exceptions see below)
● On a dedicated host

For example, the following figure shows a standard system with additional application server instances that
run:

● On the main host of the SAP system, that is, on the host on which the primary application server instance
and the database instance run
● On dedicated hosts

Additional Application Server Instance for a Standard Dual-Stack (ABAP+Java) System

For more information, see Standard System [page 22].

Additional Application Server Instance for a Distributed System

The following figure shows a distributed system with additional application server instances that run:

● On the main host of the SAP system, that is, on the host on which the primary application server instance
runs
● On dedicated hosts

We do not recommend installing additional application server instances on the SAP global host.

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
26 PUBLIC Installation Options Covered by this Guide
Additional Application Server Instance for a Distributed Dual-Stack (ABAP+Java) System

For more information, see Distributed System [page 23].

Additional Application Server Instance for a High-Availability System

The following figure shows a high-availability system with additional application server instances that run:

● On the host of the primary application server instance

● On dedicated hosts

For more information, see High-Availability System [page 24].

3.5 Splitting off an ABAP Central Services Instance from an

Existing Primary Application Server Instance

A central services instance consists of the essential enqueue and message system services only. This has been
standard for the Java stack and is now also standard for the ABAP stack.

The benefit of having a separate ASCS instance is mainly in the area of high-availability. This approach
concentrates the possible single points of failure of a system into a single instance and, therefore, restricts
failure to a single instance.

Every newly installed SAP system based on SAP NetWeaver 7.3 and higher is automatically installed with an
ASCS instance, even if you install all SAP system instances on one host (standard system).

However, if you upgraded your SAP system from a release based on a SAP NetWeaver release lower than 7.3,
your SAP system might not yet have a separate ASCS instance.

The section Splitting Off an ABAP Central Services Instance from an Existing Primary Application Server
Instance [page 175] describes how you can move the message server and the enqueue work process from the
ABAP stack of an existing primary application server instance to a newly installed ABAP central services
instance (ASCS instance).

You can install an SAP Web Dispatcher integrated in the ASCS instance. If you select this option, an SAP Web
Dispatcher is installed running within the ASCS instance. No separate SAP Web Dispatcher instance and no
dedicated <SAPSID> are created for the SAP Web Dispatcher. We recommend this if you want to use the SAP
Web Dispatcher for the system to which the ASCS instance belongs.

 Note

We only recommend this option for special scenarios. For more information, see SAP Note 908097 . For
an SAP Web Dispatcher installation, a standalone installation (see below) continues to be the default
scenario.

 Note

An ASCS instance for IBM Db2 for i is only installed on IBM i.

ASCS Instance with Integrated SAP Web Dispatcher

The SAP Web Dispatcher is located between the Web client (browser) and your SAP system that is running the
Web application.

It acts as single point of entry for incoming requests (HTTP, HTTPS), defined by the IP address, port, and URL,
and forwards them in turn to the application server (AS) of the SAP system.

The SAP Web Dispatcher receives information about the SAP system that it needs for load distribution (load
balancing) from the message server and application server via HTTP.

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
Installation Options Covered by this Guide PUBLIC 29
Installation of “Standalone” SAP Web Dispatcher with its own <SAPSID> and
Instance

If you want to install an SAP Web Dispatcher for another system - that is not for the system for which you use
the ASCS instance and with its own SAP system ID and instance number - you have to install SAP Web
Dispatcher separately as described in the documentation which you can find under http://support.sap.com/
sltoolset System Provisioning Installation Option of Software Provisioning Manager Guide for SAP
Web Dispatcher for SAP NetWeaver 7.0 or Higher .

More Information

For more information about the architecture and the functions of SAP Web Dispatcher, see the SAP Web
Dispatcher documentation in theSAP Library at:

SAP Release and SAP Library Quicklink SAP Library Path (Continued)

● SAP NetWeaver Process Integration 7.1

Application Help Function-Oriented View Application
http://help.sap.com/nwpi71
Server Application Server Infrastructure SAP Web
● SAP NetWeaver Process Integration 7.1 Including En
Dispatcher
hancement Package 1
http://help.sap.com/nwpi711

● SAP NetWeaver 7.3

Application Help Function-Oriented View Application
http://help.sap.com/nw73
Server Application Server Infrastructure Components of
● SAP NetWeaver 7.3 including Enhancement Package
SAP NetWeaver Application Server SAP Web Dispatcher
1
http://help.sap.com/nw731
● SAP NetWeaver 7.4
http://help.sap.com/nw74

Related Information

Parameters for Additional Components to be Included in the ASCS Instance [page 57]

3.7 ASCS Instance with Integrated Gateway

You can install a gateway integrated in the ASCS instance. If you select this option, a gateway is installed within
the ASCS instance.

No separate standalone gateway instance and no dedicated <SAPSID> are created for the gateway.

Gateway Integrated in the ASCS Instance

The gateway enables communication between work processes and external programs, as well as
communication between work processes from different instances or SAP systems.

You can also install a standalone gateway instance. For more information, see the documentation Installation
Guide – Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver <Release> at
http://support.sap.com/sltoolset System Provisioning Installation Option .

Related Information

Parameters for Additional Components to be Included in the ASCS Instance [page 57]

4.1 Planning Checklist

This section includes the planning steps that you have to complete for the following installation options.

● Standard, distributed, or high-availability system

● Additional application server instance

Detailed information about the steps are available in the linked sections.

Prerequisites

1. You have planned your SAP system landscape according to the Master Guide available at the appropriate
download location as described in Before You Start [page 14] .
2. You have decided on your installation option (see Installation Options Covered by this Guide [page 22]).

Standard, Distributed, or High-Availability System

1. Make yourself familiar with the changed file system structure and profiles for SAP systems based on SAP
NetWeaver 7.1 and higher compared to SAP systems based on lower SAP NetWeaver releases. For more
information, see Changed File System Structure and Profiles for SAP Systems Based on SAP NetWeaver
7.1 and Higher [page 33].
2. You check the hardware and software requirements [page 34] on every installation host.
3. You plan how to set up user and access management [page 43].
4. You plan for independent ASPs [page 44].
5. You identify Basic SAP System Installation Parameters [page 46].
6. You decide on the transport host to use [page 58].
7. You decide whether you want to integrate LDAP Directory Services in your SAP system [page 168].
8. To install a high-availability system, you read Planning the Switchover Cluster for High Availability [page
59].
9. Optionally, you decide whether you want to install multiple SAP systems on a single host [page 173].
10. Continue with Preparation [page 63].

Additional Application Server Instance

1. You check the hardware and software requirements [page 34] for every installation host on which you
want to install one or more additional application server instances.

4.2 Changed File System Structure and Profiles for SAP

Systems Based on SAP NetWeaver 7.1 and Higher

File system structure

● For SAP system releases based on SAP NetWeaver 7.1 and higher, the directory structure was changed
compared to SAP NetWeaver 7.0, in order to support heterogeneous system installations and updates
more efficiently.

 Caution

The directory structure of systems based on SAP NetWeaver 7.1 or higher is not supported on systems
based on SAP NetWeaver 7.0 including Enhancement Packages.

● For a manual switch, see the details about targeted file system structure in this documentation and adjust
your file system accordingly to avoid later issues for system transformation such as system copy and
system rename.

Profiles

● As of SAP NetWeaver 7.3, the start profile as separate file has been removed. In earlier versions of SAP
NetWeaver there was one default profile per SAP system, one start profile per Instance and one Instance
profile per instance. Now the start profile contents are merged with the instance profile. With the help of
the new instance profile, SAP processes are started and at the same time instance-specific parameters are
read. This reduces the total number of profile files to one default profile per SAP System, and one instance
profile per instance.
For more information, see the SCN blog What's new in SAP NetWeaver 7.3 - A Basis perspective at: https://
blogs.sap.com/2012/05/22/whats-new-in-sap-netweaver-73-a-basis-perspective/ .

 Caution

The merged profiles are not supported for SAP NetWeaver 7.0 including Enhancement Packages
because this could lead to issues for SAP system copy. If you are not sure which SAP NetWeaver
product version you have, see SAP Note 1877731 for more information.

● Concatenate instance profile and start profile entries and remove the start profile from the profile
directory. For more information, see SAP Note 1898687 .
● Adjust the /usr/sap/sapservices profile file by replacing the start profile with the instance profiles for
starting the sapstartsrv process, and then restart the SAP start service.
● Additional application server instances: Double-check the values with the profile values from the primary
application server - for example for parameters DIR_CT_RUN , DIR_EXECUTABLE, DIR_SAPJVM - to avoid
startup issues.

Ensure that your hosts meet the hardware and software requirements for your operating system and the SAP
instances. Otherwise you might experience problems when working with the SAP system. If you have any
questions, contact the person in charge of the installation, your Competence Center, or your local IBM
representative.

Prerequisites

● Make sure that the host name meets the requirements listed in SAP Note 611361 .
● Contact your OS vendor for the latest OS patches.

Procedure

1. Check the Product Availability Matrix at http://support.sap.com/pam for supported operating system
releases.
2. Check the hardware and software requirements using:
○ The Prerequisite Checker:
○ Standalone (optional) before the installation process
For more information, see Running the Prerequisites Check Standalone [page 35].
○ Integrated in the installation tool (mandatory) as part of the installation process
For more information, see Running the Installer [page 118].
○ The hardware and software requirements tables in Requirements for the SAP System Hosts [page
36].
3. If you want to install 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 Quick Sizer tool available at http://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

This section describes how to run the prerequisites check in standalone mode. Running the prerequisites
check in standalone mode is optional.

Context

When you install an SAP system, the installer automatically starts the prerequisites check and checks the
hardware and software requirements in the background. As an optional step during planning, you can also run
the prerequisites check in standalone mode to check the hardware and software requirements for your
operating system and the SAP instances before the actual installation.

 Recommendation

We recommend that you use both the prerequisites check and the requirements tables for reference.

Procedure

1. Download and unpack the Software Provisioning Manager archive to a local directory as described in
Downloading and Extracting the Software Provisioning Manager 1.0 (SWPM10RMSP30_Version.SAR)
Archive [page 99] .
2. Make either the separate SAPEXE<Version>.SAR archive or the complete kernel medium available as
described in Preparing the Installation Media [page 94] .
3. Start the installer as described in Running the Installer [page 118].

4. On the Welcome screen, choose <SAP_Product> <Database> Preparations Prerequisites

Check .
5. Follow the instructions in the installer dialogs 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.

After you have finished, the Parameter Summary screen appears. This screen summarizes all parameters
that you have entered and that you want to have checked. If you want to make a change, select the relevant
parameters and choose Revise.
6. To start the prerequisites check, choose Next.

The Prerequisite Checker Results screen displays the results found. If required, you can also check the results in
file prerequisite_checker_results.html, which you can find in the installation directory.

Related Information

Downloading and Extracting the Software Provisioning Manager 1.0 (SWPM10RMSP30_Version.SAR) Archive
[page 99]
Preparing the Installation Media [page 94]

4.3.2 Requirements for the SAP System Hosts

Every installation host must meet at least the requirements listed in the following tables. Most of the
requirements are valid for every installation host whereas some requirements are instance-specific and are
marked accordingly.

IBM Db2 for i

The IBM Db2 for i is fully integrated into the operating system and is always available. No separate installation
phase is required for the database code and database tools, and there is no need to start or stop the RDBMS.

Related Information

General Installation Information for Your Operating System [page 36]

Hardware Requirements [page 37]
Software Requirements [page 40]
Other Requirements [page 42]

4.3.2.1 General Installation Information for Your Operating

System

Before checking the hardware and software requirements, we recommend that you make yourself familiar with
some general information about installation of SAP systems on your operating system platform.

Every installation host must meet at least the hardware requirements listed in the following tables. Most of the
requirements are valid for every installation host whereas some requirements are instance-specific and are
marked accordingly.

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.

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 94].
○ If you prefer downloading the separate SAP kernel archives instead of using the
complete SAP kernel media, you require 2 GB of temporary disk space for the set of
SAP kernel archives that you have to copy to a local hard disk. For more information,
see Downloading SAP Kernel Archives (Archive-Based Installation) [page 101] .
○ 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:
If you install several instances on one host, you have to add up the requirements ac
cordingly.
● ○ Central services instance (SCS):
Minimum 2 GB
○ ERS instance for the SCS instance (if required):
Minimum 2 GB
○ ABAP central services instance (ASCS):
Minimum 2 GB
○ If you install the ASCS instance with an integrated SAP Web Dispatcher, for the
installation as such you require at least 1 GB of hard disk space in addition. For
production use of the SAP Web Dispatcher, you need to reserve at least 5 GB.
○ If you install the ASCS instance with an integrated SAP Gateway, you require at
least 1 GB of hard disk space in addition.
○ ERS instance for the ASCS instance (if required):
Minimum 2 GB
○ Database Instance:
Minimum 80 GB
○ Primary application server instance:
Minimum 5 GB
○ Additional application server instance:
Minimum 5 GB
○ SAP Host Agent:
Minimum 0.5 GB

RAM 11 GB

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

● Size of the database

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

Every installation host must meet at least the software requirements listed in the following tables. Most of the
requirements are valid for every installation host whereas some requirements are instance-specific and are
marked accordingly.

Software Requirements

Requirement Values and Activities

Operating system requirements The SAP products based on SAP NetWeaver 7.10, 7.11, 7.2, 7.3, and 7.4 are released
for V7R1, 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 <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 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.

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

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
● 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 For more information about release and roadmap information for the kernel ver
sions, and how this relates to SAP NetWeaver support packages - including impor
tant notes on downward compatibility and release dates - see SAP Note 1969546
.

To use regular Software Provisioning Manager (SWPM10<Version>.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.

IP Multicast Configuration SAP Kernel 7.40 and Higher: Make sure that you have applied the operating system
patches required for IP Multicast Configuration. For more information, see SAP Note
1931675 .

As of SAP Kernel 7.41 PL 47 and 7.42 PL 14, see SAP Note 2050408 .

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 .

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

Other requirements Make sure the local relational database name (RDB name) of your system equals the
host’s TCP/IP. To do so, compare the following values:

● On a WRKRDBDIRE screen, use the relational database name where remote

location equals *LOCAL.
● On a CHGTCPDMN command prompt, look at the value of host name.

For more information, see Adjusting the Relational Database Name (RDB name) [page
90].

Make sure the subsystem QUSRWRK is running by default. QUSRWRK is started automati
cally after every IPL because there is an entry in the program QSTRUP. Do not delete the
entry QUSRWRK from QSTRUP (or any other startup program name which you might have
chosen instead of QSTRUP). For more information, see Adjusting the Startup Program
QSTRUP [page 81].

IBM Db2 for i

The IBM Db2 for i is fully integrated into the operating system. No separate installation phase is required for the
database code and database tools.

4.4 Planning User and Access Management

You have to plan how to configure user and access management for the SAP system to be installed.

The user management of your SAP system is stored in the ABAP application server (AS ABAP).

Procedure

To specify the initial data source of the User Management Engine (UME), proceed as described in Specifying
the Initial Data Source of the User Management Engine [page 115].

For more information about configuring the user management of your SAP system to be installed, see the SAP
Library at:

SAP Release and SAP Library Quicklink SAP Library Path (Continued)

● SAP NetWeaver Mobile 7.1

Application Help SAP NetWeaver Library: Function-
http://help.sap.com/nwmobile71
Oriented View Security Identity Management Identity
● SAP NetWeaver Mobile 7.1 including Enhancement
Management of the Application Server ABAP
Package 1
http://help.sap.com/nwmobile711

● SAP NetWeaver 7.1 for Banking Services from SAP See the SAP NetWeaver Mobile Library.
5.0 and 6.0
● SAP NetWeaver 7.1 including Enhancement Package  Note
1 for Banking Services from SAP 5.0 and 6.0 Since the SAP NetWeaver Mobile 7.1 Library is the only
available SAP Library for ABAP systems based on SAP
NetWeaver 7.1, in this guide we always refer to it also for
SAP NetWeaver 7.1 for Banking Services from SAP 5.0 and
6.0.

● SAP NetWeaver Process Integration 7.1

Application Help SAP NetWeaver Library: Function-
http://help.sap.com/nwpi71
Oriented View Security Identity Management Identity
● SAP NetWeaver Process Integration 7.1 Including En
Management of the Application Server ABAP
hancement Package 1
http://help.sap.com/nwpi711

● SAP NetWeaver 7.3

Application Help SAP NetWeaver Library: Function-
http://help.sap.com/nw73
Oriented View Security Identity Management User and
● SAP NetWeaver 7.3 including Enhancement Package
Role Administration of Application Server ABAP
1
http://help.sap.com/nw731 Configuration of User and Role Administration Directory

● SAP NetWeaver 7.4 Services LDAP Connector

http://help.sap.com/nw74

4.5 Planning for Independent ASPs

Independent ASPs (IASPs) are user ASPs that can be varied offline or online independent of the rest of the
server storage. You can switch IASPs between IBM i servers or partitions. Planned and unplanned downtimes
are part of every system landscape. Try to minimize offline times for tasks such as system backups, software
upgrades, and application and database management.

For the installation of SAP systems the SWPM supports the following three types of IASP: primary,
secondary and User-Defined File System (UDFS). UDFS can only hold IFS objects, while primary and
secondary can also contain library objects. The support of the UDFS was added for IBM Db2 Mirror for i. For
more information about IBM Db2 Mirror for i, see the SAP Note 2808345 .Also, SAP Note 2808345
tells you the releases that are currently supported. For example, initially Java and ABAP+Java are not
supported.

Also SAP Note 2808345 tells you

what releases are currently supported. For example, initially Java and ABAP+Java are not supported.

Installing an SAP system on an IASP in combination with virtual hostnames and cluster services allows you to
move SAP systems between different physical hosts and provides the most convenient combination between
high availability and simplicity for SAP on IBM i. A switchable IASP configuration allows the customer to take
advantage of other high-availability solutions such as cross-site mirroring.

 Recommendation

Contact your IBM provider for the best recommendations based on your environment.

To ensure a successful installation on an IASP and to take full advantage of the benefits it provides, you must
plan for the following activities:

 Note

When you want to use a IBM Db2 Mirror for i scenario, you must first follow the SAP Note 2808345 to
prepare your IBM i environment.

● You set up the IASP with the required configuration.

 Note

If you want to use IBM Db2 Mirror for i make sure you configure an UDFS IASP. Later the SWPM has to
install the global SAP directories into this UDFS IASP. The SAP databases will be installed in a different
ASP, not in an UDFS IASP.

 Note

If a switchable environment is required, make sure you can move this IASP between the primary and
secondary host.

● You set up an IP for both systems and set the virtual host.

 Recommendation

We recommend that you install the system using a virtual hostname. If you change the hostname of an
already installed system an error can occur.

● You use the IBM System i Navigator to set up the clustering services, which you need for administrating the
systems.

 Note

Make sure you use installer option SAPINST_USE_HOSTNAME to set your virtual hostname [page 69].
For more information, see Running the Installer [page 118].

● IBM Db2 Mirror for i scenario: You follow SAP Note 2808345 to activate IBM Db2 Mirror for i for the
fresh installed SAP system.

● IASP Switchover scenario: You follow the steps as described in Setting Up a Secondary Host for IASP
Switchover [page 142].

4.6 Basic Installation Parameters

The installer prompts for input parameters during the Define Parameters phase of the installation.

You can install your SAP system either in Typical or Custom mode:

● Typical
If you choose Typical, the installation is performed with default settings. This means that the installer
prompts you only for a small selection of installation parameters. These parameters include at least the
following:
○ SAP system ID and database connectivity parameters
○ Master password
○ SAP system profile directory – only for systems with instances on separate hosts
○ SAP systems based on SAP NetWeaver 7.40 and higher: Individual encryption key for the secure
storage
For more information about the installation parameters, see the corresponding tables below in this
document. If you want to change any of the default settings, you can do so on the Parameter Summary
screen.
● Custom
If you choose Custom, you are prompted for all parameters. At the end, you can still change any of these
parameters on the Parameter Summary screen.

 Note

You cannot change from Custom to Typical mode or from Typical to Custom mode on the Parameter
Summary screen.

 Note

● If you want to install an ASCS instance with an integrated SAP Web Dispatcher [page 29], you must
choose Custom. Otherwise, you are not prompted for the SAP Web Dispatcher installation parameters
[page 57] during the Define Parameters phase of the ASCS instance installation.
● If you want to install an ASCS instance with an integrated Gateway [page 30], you must choose
Custom. Otherwise, you are not prompted for the SAP Gateway installation during the Define
Parameters phase of the ASCS instance installation.

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
46 PUBLIC Planning
The tables in the sections below list the basic SAP system installation parameters that you need to specify
before installing your SAP system. For all other installation parameters, use the tool help on the installer
screens.

Related Information

SAP System Parameters [page 47]

SAP System Database Parameters [page 57]
Parameters for Additional Components to be Included in the ASCS Instance [page 57]

4.6.1 SAP System Parameters

The tables in this section lists the basic SAP system installation parameters that you need to specify before
installing your SAP system. For all other installation parameters, use the tool help on the installer screens.

General Parameters

Parameter Description

Unicode System Every new installation of an SAP system is Unicode.

You can only deselect this option if you perform the target system installation in the context of a system
copy for a non-Unicode SAP system that has been upgraded to the current release.

If you install an additional application server instance in an existing non-Unicode system (that has been
upgraded to the current release), the additional application server instance is installed automatically as
a non-Unicode instance. The installer checks whether a non-Unicode system exists and chooses the
right executables for the system type.

SAP System ID The SAP system ID (<SAPSID>) identifies the entire SAP system.
<SAPSID>
The installer prompts you for the <SAPSID> when you execute the first installation option to install a
new SAP system.

If there are further installation options to be executed, the installer prompts you for the profile direc
tory. For more information, see the description of the parameter SAP System Profile Directory.

 Example
This prompt appears when you install the ASCS instance, which is the first instance to be installed in
a distributed system.

 Caution
Choose your SAP system ID carefully since renaming requires considerable effort.

Make sure that your SAP system ID:

● Is unique throughout your organization. Do not use an existing <SAPSID> when installing a new
SAP system.

 Example
If you have already installed an ABAP system and you want to install a new Java system on the
same host, make sure that you enter a <SAPSID> that is different from the <SAPSID> of the
existing ABAP system. The <SAPSID> of a Java stack can only by equal to the <SAPSID> of an
ABAP stack if they form a dual-stack system.

Dual stack is no longer supported in SAP systems based on SAP NetWeaver 7.5 or higher.

● 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 .
● If you want to install an additional application server instance, make sure that no Gateway instance
with the same SAP System ID (SAPSID) exists in your SAP system landscape.

SAP System In Technical identifier for internal processes. It consists of a two-digit number from 00 to 97.
stance Numbers
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.

If you do not enter a specific value, the instance number is set automatically to the next free and valid
instance number that has not yet been assigned to the SAP system to be installed or to SAP systems
that already exist on the installation host.

For more information about the naming of SAP system instances, see SAP Directories [page 64].

Virtual Host Virtual host name (network name) of the SAP<SAPSID> cluster group
Name
You can assign a virtual host name to an SAP instance in one of the following ways:

● You can assign a virtual host name for the instance to be installed, by specifying it in the
<Instance Name> Host Name field of the <Instance Name> Instance screen. Then this instance
is installed with this virtual host name.
● Alternatively you can assign virtual host names also by starting the installer with the
SAPINST_USE_HOSTNAME property. For more information, see Running the Installer [page 118].

After the installation has completed, all application servers can use this virtual host name to connect to
the instance. If you do not provide the virtual host name, the instance is installed automatically using the
physical host name of the host where you run the installer.

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

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

SAP System Pro /<sapmnt>/<SAPSID>/profile or /usr/sap/<SAPSID>/SYS/profile

file Directory
The installer retrieves parameters from the SAP system profile directory of an existing SAP system.

SAP profiles are operating system files that contain instance configuration information.

The installer prompts you to enter the location of the profile directory when the installation option
that you execute is not the first one belonging to your SAP system installation, for example if you are
installing a distributed system or an additional application server instance to an existing SAP system.
See also the description of the parameters SAP System ID and Database ID.

/usr/sap/<SAPSID>/SYS/profile is the soft link referring to /<sapmnt>/<SAPSID>/profile.

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

● Operating system users (for example <sapsid>adm)

 Caution
If you did not create the operating system users manually before the installation, the installer
creates them with the common master password (see Operating System Users). In this case,
make sure that the master password meets the requirements of your operating system.

● ABAP users: SAP*, DDIC, and EARLYWATCH.

● Java users
(for example J2EE_ADMIN)
● Secure Store key phrase
SAP systems based on SAP NetWeaver lower than 7.4: For more information, see line Key Phrase
for Secure Store Settings in this table.
SAP systems based on SAP NetWeaver 7.4 and Higher: For more information, see line Key Phrase
for Secure Store Settings and line Individual Encryption Key for the Secure Storage in this table.

 Note
If your global host is on IBM i, the name of the Windows SAP service user isSAPSe<sapsid> instead
of SAPService<sapsid>.

Basic Password policy

The master password must meet the following requirements:

● It must be 8 to 14 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).

 Caution
Software Provisioning Manager uses a password length from 8 to 14 characters by default. When
you limit the password length on your IBM i host, for example by the system values
QSECURITY,QPWDLVL, or QPWDMAXLEN this can influence the maximum length of the SAP pass
words. If you set QPWDMAXLEN to 10, then only a password length from 8 to 10 characters can be
used. The recommended security level of 30 (set by system value QSECURITY) enables a maximum
password length of 128 on the IBM i host. For more information, see Checking and Adjusting Operat
ing System Values [page 75] .

Depending on the installation option, additional restrictions may apply.

 Example
The master password must not contain the name of a Java user created during the installation).

Message Server You can specify if you want to have a message server Access Control List (ACL) created.
Access Control
The ACL is created as a file in the /<sapmnt>/<SAPSID>/global directory. If it exists, it defines the
List
hosts from which the message server accepts requests.

 Caution
Only trigger the creation of this file if you do not plan to install any additional instances for this sys
tem. With the creation of this ACL, you overwrite existing settings and prevent instances from being
installed on additional hosts. If you decide to install an additional instance later, you need to remove
this file manually before the installation and create it again after the installation of the additional in
stance.

For more information, see the information about ms/acl_info in SAP Notes 1495075 and 826779
.

SAP systems You can set a randomly generated individual encryption key for the secure storage in the file system and
based on SAP the secure storage in the database. If you skip this step, the system is installed with a default key which
NetWeaver 7.4 provides obfuscation only, but it can be changed later.
and Higher only:
● For more information on the secure storage in the file system, see the SAP Library - depending on
Individual En the SAP NetWeaver release your SAP system is based on - at:
cryption Key for http://help.sap.com/nw74
the Secure Stor Application Help Function-Oriented View: English Security System Security System
age
Security for SAP NetWeaver AS ABAP Only Secure Storage in the File System (AS ABAP)
● For more information on the secure storage in the database, see the SAP Library - depending on the
SAP NetWeaver release your SAP system is based on - at:
http://help.sap.com/nw74

Application Help Function-Oriented View: English Security System Security System

Security for SAP NetWeaver AS ABAP Only Secure Storage (ABAP) Key Management Using

Individual Encryption Keys Generating Encryption Keys

Key Phrase for This is a random word or phrase that is used to encrypt the secure store.
Secure Store
The Java EE engine uses this phrase to generate the key that is used to encrypt the data.
Settings
The uniqueness of the phrase you use contributes to the uniqueness of the resulting key.

 Recommendation
Use a long key phrase that cannot be guessed easily. Use both uppercase and lowercase letters in
the phrase and include special characters.

 Note
If you choose Typical mode, the installer sets the master password for the key phrase. In this case,
make sure that you replace the master password with the required unique key phrase either on the
Parameter Summary screen or after the installation has finished.

Path to The SAP Cryptographic Library is required to enable Secure Sockets Layer (SSL) encryption of HTTP
SAPCRYPTO.SAR connections. In most cases it is installed automatically from the kernel medium. In case it is not installed
automatically and you are prompted for it during the installation, you can download it as described in
SAP Note 455033 .

For more information about SAP Cryptographic Library on IBM i, see SAP Note 758667 .

This software product is subject to export control regulations in Germany as the country of origin and
import regulations of your own country. SAP may not yet have a corresponding export license for your
user or company. Contact the contract department in your local SAP company. To download the SAP
Cryptographic Software from the SAP Help Portal, you need a customer user ID. Before any transfer of
these software products to persons, companies or other organizations outside your company, in partic
ular in the case of any re-export of the software products, authorization is required from the German
export control authorities. This might also be required from your responsible national export control au
thorities. This also applies to transfers to affiliated companies. Corresponding laws and regulations in
the recipient country may also exist which restrict the import or the use of these software products.

DNS Domain If you want to use HTTP-based URL frameworks such as Web Dynpro applications, you have to specify
Name for SAP the DNS domain name for the SAP system.
System
The DNS Domain Name is used to calculate the Fully Qualified Domain Name (FQDN), which is config-
ured in profile parameter SAPLOCALHOSTFULL. FQDN is the fully qualified domain name for an IP ad
dress. It consists of the host name and the domain name:

<Host_Name>.<Domain_Name>

The DNS Domain Name is needed to define the URLs for the ABAP and Java application servers. It is
appended to the server name to calculate the FQDN.

 Example
If your application server host is called kirk.wdf.sap.com, the DNS Domain Name is
wdf.sap.com.

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

For more information, see Downloading SAP Kernel Archives (Archive-Based Installation) [page 101]

Parameter Description

ABAP Message Server Port

 Caution
The message server port number must be unique on the host where the message
server for the SAP system is running. If there are several message servers running on
one host, the message server ports must all be unique.

If you do not specify a value, the default port number is used.

ABAP Message Server Port

There is an external messagev server port and an internal message server port.

The ABAP message server uses both the internal and the external message server ports.
The default profile contains the configuration for both message server ports.

The external message server port uses the parameter rdisp/msserv with default value
36<ABAP_Message_Server_Instance_Number>.

The internal message server port uses the parameter rdisp/msserv_internal with de
fault value 39<ABAP_Message_Server_Instance_Number>.

During the installation of an SAP system from scratch or an additional application server
instance to an existing SAP system , the message server is configured to only accept secure
connections. The DEFAULT.PFL profile parameter system/secure_communication
is set to ON (system/secure_communication = ON) if the kernel supports secure
connections to the message server. For more information, see SAP Note 2040644 .

Java Message Server Port

The Java message server only uses the internal message server port. The SCS instance
profile contains the configuration for the Java message server.

The parameter rdisp/msserv is set to 0, so that the external port is not open.

The internal message server port uses the parameter rdisp/msserv_internal with de
fault value 39<SCS_Instance_Number>.

For more information about the parameters used for message server ports, see SAP Note
821875 .

Parameter Definition

Operating System Users The installer creates the users <SAPSID>ADM and <SAPSID>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 instal
lation, the installer creates them automatically during the installation.

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, we recommend removing the SAPINST group from the operating sys
tem users after the execution of the installer has completed.

During the Define Parameters phase of the installer, you can specify that the
group SAPINST is to be removed automatically from the operating system users
after the execution of the installer has completed.

For more information about the SAPINST group, see Preparing the SAP Installa
tion User on IBM i [page 91].

For more information about the sapinst_instdir directory, see Useful Infor
mation about the Installer [page 122].

User Management Engine Parameters

Parameter Definition

Java Administrator User The installer creates this user in the ABAP system.

After the installation, this user is available both in the ABAP

and in the Java system.

The installer sets the user name J2EE_ADMIN and the mas
ter password by default.

If required, you can choose another user name and pass

word according to your requirements.

Java Guest User This user is for employees who do not belong to a company
or who have registered as company users and who are wait
ing for approval. Guest users belong to the default group
Authenticated Users.

The installer creates this user in the ABAP system.

After the installation, it is available both in the ABAP and in

the Java system.

The installer sets the user name J2EE_GUEST and the mas
ter password by default.

If required, you can choose another user name and pass

word according to your requirements.

For more information about supported UME data sources

and change options, see SAP Note 718383 .

Communication User The installer creates this user in the ABAP system.

After the installation, it is available both in the ABAP and in

the Java system

This user is used for the communication between the ABAP

system and the Java system.

The installer sets the user name SAPJSF and the master
password by default.

If required, you can choose another user name and pass

word according to your requirements.

For more information about supported UME data sources

and change options, see SAP Note 718383 .

Parameter Definition

SLD Destination for the System The System Landscape Directory (SLD) registers the systems and the installed software
of your entire system landscape.

You can choose between the following options:

● Register in existing SLD

Choose this option to register the SAP system you are installing in an existing SAP
System Landscape Directory (SLD) by specifying the SLD connection parameters
listed below in this table.
● No SLD destination
Choose this option if you do not want to register the SAP system you are installing
in an existing SAP System Landscape Directory (SLD).
You then have to configure the SLD destination manually after the installation has
finished.

For more information, see Performing Post-Installation Steps for the ABAP Application
Server [page 149]

SLD Host The host name of the existing SLD.

SLD HTTP(S) Port HTTP port of the SAP system based on AS Java on which the System Landscape Direc
tory (SLD) resides. The following naming convention applies:
5<Primary_Application_Server_Instance_Number>00.

 Example
If the primary application server instance number of the AS Java on which the Sys
tem Landscape Directory (SLD) resides is 01, the SLD HTTP Port is 50100.

SLD Data Supplier User and The existing SLD Data Supplier user and password of the existing SLD
password

Parameters Description

Database ID <DBSID> The <DBSID> identifies the database instance. The installer prompts you for the <DBSID>
when you are installing the database instance.

For IBM i, the <DBSID> is always the same as the <SAPSID>.

● If you want to install a new database:

Make sure that your database 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 .

Database schema The database schema name is SAP<SAPSID>DB for Java systems.

The database schema name is R3<SAPSID>DATA for ABAP systems.

Location of the Toolbox Enter the path where the Toolbox JDBC driver files are located.
JDBC Driver
Make sure that the correct version of the JDBC driver is used.

For more information, see Installing the Toolbox JDBC Driver [page 71].

ASP of SAP<SAPSID>DB Auxiliary Storage Pool (ASP) for the Java Database Library SAP<SAPSID>DB and the Java
and SAP<SAPSID>JRN Journal Receiver Library SAP<SAPSID>JRN. For more information, see Distribution of Libra
ries on ASPs [page 93].

ASP of R3<SAPSID>DATA Auxiliary Storage Pool (ASP) for the ABAP Database Library R3<SAPSID>DATA and the ABAP
and R3<SAPSID>JRN Journal Receiver Library R3<SAPSID>JRN. For more information, see Distribution of Libraries
on ASPs [page 93].

ASP of SAP<SAPSID>IND Auxiliary Storage Pool (ASP) for the kernel library SAP<SAPSID>IND. For more information,
and see Distribution of Libraries on ASPs [page 93].
SAP<SAPSID>I<Instanc
e_Number>

4.6.3 Parameters for Additional Components to be Included

in the ASCS Instance
You only need to specify the following parameters during the ASCS instance installation if you perform an
integrated installation of additional components.

 Note

You must choose Custom parameter mode. Otherwise you are not prompted for the parameters related to
these additional components during the Define Parameters phase.

Install an SAP Web Dispatcher inte When processing the screens for the ASCS instance installation, you are
grated in the ASCS instance prompted to mark this checkbox on the screen Additional Components to be
Included in the ASCS Instance.

If you mark the checkbox for SAP Web Dispatcher, you are prompted for the ad
ditional parameters required for the SAP Web Dispatcher installation on the sub
sequent screens:

Message Server Host

The name of the host on which the message server is located (profile parameter
rdisp/mshost)

Message Server HTTP Port

HTTP port of the message server (profile parameter ms/server_port_<xx>)

Password for the Internet Communication Management (ICM) user

In order to use the web administration interface for the Internet Communication
Manager (ICM) and SAP Web Dispatcher, an administration user webadm is cre
ated by the installer.

You have to assign a password for this user.

Related Information

ASCS Instance with Integrated SAP Web Dispatcher [page 29]

ASCS Instance with Integrated Gateway [page 30]

4.7 SAP System Transport Host

The transport host contains the transport directory used by the SAP transport system to store transport data
and change SAP system information, such as software programs, write dictionary data, or customizing data. If
you have several SAP systems it depends on your security requirements whether you want them to share a
transport directory or whether you use separate directories.

When you install an SAP system, you have to decide which transport host and directory you want to use for
your SAP system:

● Use the transport directory that the installer creates during the installation of the SAP system by default on
the global host.
The installer by default creates the transport directory on the global host in /usr/sap/trans.
● Use a transport directory located on a host other than the default host:
○ You can use an existing transport directory and host in your SAP system landscape.

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
58 PUBLIC Planning
○ You can set up a new transport directory on a different host.
In either case, you must prepare this host for use by the new SAP system. For more information, see
Setting Up the Transport Directory [page 143].

More Information

● Setting Up File Systems [page 64]

● See the SAP Library at:

Release SAP Library Path

○ SAP NetWeaver Process Integration 7.1

Application Help Function-Oriented View ABAP Technology /
http://help.sap.com/nwpi71
Application Server ABAP Administration Tools for AS ABAP
○ SAP NetWeaver Process Integration 7.1 In
cluding Enhancement Package 1 Change and Transport System Change and Transport System –

http://help.sap.com/nwpi711 Overview Basics of the Change and Transport System

Transport Management System – Concept

○ SAP NetWeaver 7.3

Application Help Function-Oriented View Solution Life Cycle
http://help.sap.com/nw73
Management Software Logistics Change and Transport System
○ SAP NetWeaver 7.3 including Enhancement
Package 1 Change and Transport System – Overview Basics of the Change

http://help.sap.com/nw731 and Transport System Transport Management System –

○ SAP NetWeaver 7.4 Concept
http://help.sap.com/nw74

4.8 Planning the Switchover Cluster for High Availability

This section describes basic aspects of planning the switchover cluster for a high-availability system.

You can reduce unplanned downtime for your SAP system by setting up a switchover cluster. This setup installs
critical software units – known as “single points of failure” (SPOFs) – across multiple host machines in the
cluster. In the event of a failure on the primary node, proprietary switchover software automatically switches
the failed software unit to another hardware node in the cluster. Manual intervention is not required.
Applications trying to access the failed software unit might experience a short delay but can then resume
processing as normal.

Switchover clusters also have the advantage that you can deliberately initiate switchover to release a particular
node for planned system maintenance. Switchover solutions can protect against hardware failure and
operating system failure but not against human error, such as operator errors or faulty application software.
Additional downtime might be caused by upgrading your SAP system or applying patches to it.

Without a switchover cluster, the SAP system SPOFs – central services instance, the database instance, and
the central file share – are vulnerable to failure because they cannot be replicated. All of these can only exist
once in a normal SAP system.

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
Planning PUBLIC 59
You can protect software units that are not SPOFs against failure by making them redundant, which means
simply installing multiple instances. For example, you can add additional application server instances. This
complements the switchover solution and is an essential part of building high availability (HA) into your SAP
system.

 Recommendation

We recommend switchover clusters to improve the availability of your SAP system.

A switchover cluster consists of:

● A hardware cluster of two or more physically separate host machines to run multiple copies of the critical
software units, in an SAP system the SPOFs referred to above
● Switchover software to detect failure in a node and switch the affected software unit to the standby node,
where it can continue operating
● A mechanism to enable application software to seamlessly continue working with the switched software
unit – normally this is achieved by virtual addressing (although identity switchover is also possible)

Prerequisites

You must first discuss switchover clusters with your hardware partner because this is a complex technical area.
In particular, you need to choose a proprietary switchover product that works with your operating system.

We recommend that you read the following documentation before you start:

● Check the SAP High Availability pages at https://wiki.scn.sap.com/wiki/display/SI/SAP+High+Availability

. They contain crucial information about high-availability cluster certification and certified high-
availability partners.
● You can reduce unplanned downtime. The ERS instance is essential for a high-availability system. You need
one ERS instance for the Java SCS and one ERS instance for the ASCS installed in your system.

Features

 Note

The diagrams in this section are only examples. Only the instances relevant to the switchover are shown.

These diagrams summarize the overall setup and do not show the exact constellation for an installation
based on one of the available technologies.

You need to discuss your individual HA setup with your HA partner.

Constraints

This documentation concentrates on the switchover solution for the central services instance. For more
information about how to protect the Network File System (NFS) software and the database instance by using
switchover software or (for the database) replicated database servers, contact your HA partner.

This documentation concentrates on the switchover solution for the central services instance. For more
information about how to protect the central file share and the database instance by using switchover software
or (for of the database) replicated database servers, contact your HA partner.

Make sure that your hardware is powerful enough and your configuration is robust enough to handle the
increased workload after a switchover. Some reduction in performance might be acceptable after an
emergency. However, it is not acceptable if the system comes to a standstill because it is overloaded after
switchover.

5.1 Preparation Checklist

This section includes the preparation steps that you have to perform for the following installation options:

● Standard, distributed, or high-availability system

● Additional application server instance

Detailed information about the steps are available in the linked sections.

Standard, Distributed, or High-Availability System

1. You set up file systems [page 64] and make sure that the required disk space is available for the
directories to be created during the installation.
2. If you want to use virtual host names, you have to set the environment variable SAPINST_USE_HOSTNAME
[page 69] using the following command:
ADDENVVAR ENVVAR(SAPINST_USE_HOSTNAME) VALUE('<Virtual_Host_Name>')
REPLACE(*YES)
Alternatively, you can specify the virtual host name in the command to run the installer [page 118].
3. If you want to install a high-availability system, you perform switchover preparations [page 70].
4. You complete the preparation for IBM i [page 70].
5. If you want to share the transport directory [page 143] trans from another system, make this directory
available to your installation hosts.
6. You install the SAP front-end software [page 94] on the desktop of the user.
7. You check that the required installation media [page 94] are available for each installation host.
8. You copy the installation media manually to your IBM i [page 105].
9. If you decided to use a generic LDAP directory, you have to create a user for LDAP directory access [page
174].
10. You continue with Installation [page 108].

Additional Application Server Instance

You have to perform the following preparations on the host where you install the additional application server
instances:

1. You set up file systems [page 64] and make sure that the required disk space is available for the
directories to be created during the installation.

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
Preparation PUBLIC 63
2. If you want to use virtual host names, you have to set the environment variable SAPINST_USE_HOSTNAME
[page 69] using the following command:
ADDENVVAR ENVVAR(SAPINST_USE_HOSTNAME) VALUE('<Virtual_Host_Name>')
REPLACE(*YES)
Alternatively, you can specify the virtual host name in the command to run the installer [page 118].
3. You complete the preparation for IBM i [page 70].
4. If you want to share the transport directory [page 143] trans from another system, make this directory
available to your installation hosts.
5. You install the SAP front-end software [page 94] on the desktop of the user.
6. You check that the required installation media [page 94] are available on each installation host.
7. You copy the installation media manually to your IBM i [page 105].
8. You continue with Installation [page 108].

5.2 Required File Systems and Directories

The following sections describe how to set up SAP file systems for the SAP instances on operating system
level:

 Note

The installation of any SAP system does not require a special file system setup or separate partitions.

Related Information

SAP Directories [page 64]

5.2.1 SAP Directories

Depending on the installation option you have chosen, 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 installer creates the following types of directories:

● Physically shared directories

● Logically shared directories
● Local directories

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 installer creates
all directories in the root directory (/ ). A high-availability setup might influence the file system structure.
Contact your HA partner for their recommendation.

On IBM i, the directory /sapmnt is used as the SAP system mount directory <sapmnt>, and the installer does
not prompt you for the <sapmnt> directory during the installation.

The following figure shows the directory structure of the SAP system:

Directory Structure for a Dual-Stack (ABAP+Java) System

Both the ABAP stack and the Java stack of every new installation of a Dual-Stack (ABAP+Java) system are
Unicode (directory uc – Unicode).

Physically Shared Directories (SAP System)

Physically shared directories, which reside on the global host and are shared by QFileSvr.400. The installer
creates the following directories:

● The directory /<sapmnt>/<SAPSID>, which contains SAP kernel and related files, is created on the first
installation host. Normally, the first installation host is the host on which the central services instance is to
run, but you can also choose another host for /<sapmnt>/<SAPSID>.

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
Preparation PUBLIC 65
You need to manually share this directory with QFileSvr.400 and – for a distributed system – link it from
the other installation hosts.
The installer creates the following shared subdirectories in /<sapmnt>/<SAPSID> during the SAP system
installation:
○ global
Contains globally shared data
○ profile
Contains the profiles of all instances
○ exe
For Java:
○ jdbc
Contains the JDBC driver to connect to the Java database on IBM i
○ j2ee (deprecated)
Contains data to run the Java EE Server using IBM Classic JVM
● The directory /usr/sap/trans, which is the global transport directory.
If you want to use an existing transport directory, you have to make it available with QFileSvr.400 before
you install the application server instance in question. Otherwise, the installer creates /usr/sap/trans
locally.
For more information about the global transport directory, see Setting Up the Transport Directory [page
143].

Physically Shared SAP Directories

Directory Required Minimum Disk Space

/<sapmnt>/ Minimum 2.5 GB

/usr/sap/trans This value heavily depends on the use of your SAP system.

For production systems, we recommend to use as much free space as available (at least 2 GB), be
cause the space requirement normally grows dynamically.

For the installation, it is sufficient to use 2 GB for each SAP system instance. You can enlarge the file
system afterwards.

Logically Shared Directories (SAP System)

Logically shared directories reside on the local hosts with symbolic links to the global host. The installer creates
the directory /usr/sap/<SAPSID>/SYS on each host.

This directory contains the following symbolic links to physically shared directories:

● Symbolic link profile points to /<sapmnt>/<SAPSID>/profile

● Symbolic link global points to /<sapmnt>/<SAPSID>/global

This directory contains the exe subdirectory with symbolic links pointing to the corresponding subdirectories
of /<sapmnt>/<SAPSID>/exe on the SAP global host:

● Symbolic link uc (for Unicode) points to /<sapmnt>/<SAPSID>/exe/uc

● Symbolic link nuc (for non-Unicode) points to /<sapmnt>/<SAPSID>/exe/nuc
● Symbolic link run points to /<sapmnt>/<SAPSID>/exe/uc/<platform>

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
66 PUBLIC Preparation
Whenever a local instance is started, the sapcpe program checks the executables against those in the logically
shared directories and, if necessary, replicates them to the local instance.

The installer uses sapcpe to replicate the kernel automatically from /usr/sap/<SAPSID>/SYS/exe/run/
DIR_CT_RUN to /usr/sap/<SAPSID>/<INSTANCE>/exe/DIR_EXECUTABLE for each SAP system instance.

Local Directories (SAP System)

The installer also creates local directories that reside on the local hosts. The directory /usr/sap/<SAPSID>
contains files for the operation of a local instance as well as symbolic links to the data for one system. This
directory is physically located on each host in the SAP system and contains the following subdirectories:

● SYS

 Note

The subdirectories of /usr/sap/<SAPSID>/SYS have symbolic links to the corresponding

subdirectories of /<sapmnt>/<SAPSID>, as shown in the figure above.

● Instance-specific directories with the following names:

○ The directory of the primary application server instance is called DVEBMGS<Instance_Number>.
○ The directory of an additional application server instance is called D<Instance_Number>.
● The directory of the central services instance (SCS) instance is called SCS<Instance_Number>.
● The directory of the ABAP central services instance (ASCS) instance is called ASCS<Instance_Number>.
● The directory of an ERS instance is called ERS<Instance_Number>.
If you install a high-availability system, you must install an ERS instance for both the ASCS instance and for
the SCS instance.

Local SAP Directories

Directory Description Required Minimum Disk Space

/usr/sap/<SAPSID>/ Primary application server in Minimum 6 GB

DVEBMGS<Instance Number> stance directory

/usr/sap/<SAPSID>/D<Instance Additional application server Minimum 6 GB

Number> instance directory

/usr/sap/<SAPSID>/ASCS<Instance ABAP central services in Minimum 2 GB

Number> stance (ASCS instance) direc
tory

/usr/sap/<SAPSID>/ERS<Instance ERS instance directory for the Minimum 2 GB

Number> ASCS instance (high availabil
ity only)

/usr/sap/<SAPSID>/SCS<Instance Java central services instance Minimum 2 GB

Number> (SCS instance) directory

/usr/sap/<SAPSID>/ERS<Instance ERS instance directory for the Minimum 2 GB

Number> SCS instance (high availability
only)

The SAP Host Agent has only local directories as shown in the following figure:

Directory Structure for the SAP Host Agent

Local Directories (SAP Host Agent)

The SAP Host Agent directory /usr/sap/hostctrl requires 100 MB of disk space. It contains the following
subdirectories:

● exe
Contains the profile host_profile
● work
Working directory of the SAP Host Agent

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

If you want to install a high-availability (HA) system [page 24], you need the virtual host name when you install
the ASCS instance and the SCS instance in a cluster.

Procedure

1. Assign the required virtual host names to the instance to be installed by specifying them in one of the
following ways:
○ By starting the installer with the SAPINST_USE_HOSTNAME property. For more information, see
Running the Installer [page 118].
○ Alternatively by specifying vitual host names in the <Instance Name> Host Name field of the
<Instance Name> Instance screen.

For more information, see the Virtual Host Name parameter description in SAP System Parameters [page
47] and SAP Note 962955 .
2. Proceed as described in SAP Note 1624061 .

You have to assign virtual host names to prepare the switchover for high-availability.

Context

To be able to use the required virtual host names [page 69], you must set the installer property
SAPINST_USE_HOSTNAME to specify the required virtual host name. You can do this in one of the following
ways:

● By starting the installer with the SAPINST_USE_HOSTNAME property. For more information, see Running
the Installer [page 118].
● Alternatively by specifying vitual host names in the <Instance Name> Host Name field of the <Instance
Name> Instance screen.

For more information, see Virtual Host Name in SAP System Parameters [page 47].

Procedure

Assign the virtual IP addresses and host names for the SCS and ASCS instance, and (if required) NFS to
appropriate failover groups.

 Note

For more information on virtual addresses and virtual host names and how to assign resources to failover
groups, ask your HA partner.

To enable a failover in a dual-stack system (ABAP+Java), both central services instances – SCS and ASCS
– have to use the same virtual host name.

5.5 Preparation for IBM i

You have to complete the following preparations for IBM i, which are described in more detail in the linked
sections:

● You install the Toolbox JDBC driver [page 71].

● You check the transport directory [page 72].
● You check Qp2Term, Qp2Shell, and the Portable Application Solution Environment [page 74].
● You install the Qshell [page 75].
● You check and adjust system values [page 75].

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
70 PUBLIC Preparation
● You adjust startup program QSTRUP [page 81].
● You check distribution of libraries on ASPs [page 93].
● You add a user ASP [page 81].
● You configure TCP/IP [page 83].
● You adjust the relational database name [page 90].
● You install English as a secondary language [page 91].
● You prepare the SAP installation user onIBM i [page 91].
● You enable the user QSECOFR [page 93].

5.5.1 Installing the Toolbox JDBC Driver

Use

All database access from Java occurs through the JDBC API (Java Database Connectivity). Implementations of
this are called Toolbox JDBC driver. The Toolbox JDBC driver typically runs on the application server. SAP
certifies one Toolbox JDBC driver for access to IBM i:

● IBM Toolbox for Java JDBC Driver also referred to as Toolbox JDBC driver
Toolbox JDBC driver is a type 4 JDBC driver. That means that it is completely written in Java. It is therefore
OS-independent. SAP certifies this driver for the following:
○ Local (two-tier) access from an IBM i to an IBM i database
○ Remote (three-tier) access from any platform that was certified by SAP for SAP NetWeaver to an IBM i
database

 Note

IBM Developer Kit for Java JDBC driver, also referred to as the native JDBC driver is not supported for
SAP NetWeaver 7.1 and higher running SAP JVM.

Prerequisites

Toolbox JDBC Driver

● Make sure that the QUSER profile is enabled. To do so, log on as user with similar permissions such as
QSECOFR and enter the following command:
CHGUSRPRF USRPRF(QUSER) STATUS(*ENABLED)
● You need to start the distributed data management (DDM) TCP/IP server and host servers after each initial
program load (IPL). To do so, proceed as follows:
○ To start the DDM TCP/IP server, enter the following command:
STRTCPSVR SERVER(*DDM)
○ To start host servers, enter the following command:
STRHOSTSVR SERVER(*ALL)

You must want to start server jobs automatically after each IPL. For more information, see
Adjusting Startup Program QSTRUP [page 81].

Procedure

 Note

You must follow the patch strategy described in the respective IBM Information APAR (IBM i 7.1 or higher)
to obtain the current correction level of the supported IBM Toolbox for Java JDBC driver.

Since you use the Toolbox JDBC driver that is not supplied by a PTF but that has to be downloaded from an IBM
webpage, we recommend that you do not overwrite the Toolbox product. Instead, proceed as follows:

1. Log on to your database instance host with your installation user.

2. Follow the download instructions in the respective Information APAR.
3. Extract the patch into an arbitrary directory on your database instance host, for example:
/sapmnt/jdbc/toolbox/jt400.jar

 Note

There are currently three versions of the Toolbox JDBC driver: 3.0, 4.0, and 4.2. Make sure you
downloaded version 4.0 for SAP system installations based on SAP NetWeaver 7.2 and higher and
version 3.0 for SAP system installations based on SAP NetWeaver 7.1/7.11. If you have the wrong
version, the installer will detect this and it will ask you again for the Toolbox JDBC driver location. The
installer will do this until you put in the right version. Afterwards, the installation will continue. For more
information, see SAP 1232613 .

4. During the installation process, choose Toolbox JDBC driver and specify the directory you have chosen
above. In the above example, this is the following directory:
/sapmnt/jdbc/toolbox

 Note

The installation process copies the Toolbox JDBC driver into the directory /usr/sap/<SAPSID>/SYS/
jdbc/tbx. You have to maintain this Toolbox JDBC driver for your SAP system in this directory. If you
have several SAP systems using the Toolbox JDBC driver you have to maintain the driver individually
for every SAP system.

5.5.2 Checking the Transport Directory

The transport host has a directory structure that is used by the SAP transport system to store transport data
and metadata. The transport system stores the change information, such as ABAP programs, data dictionary
data, and customization data as well as SAP support packages from SAP Help Portal in files that are located in

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
72 PUBLIC Preparation
this directory structure. If you do not intend to use the directory structure of the system you are going to install,
you need to prepare the directory structure on the transport host.

● If the directory structure already exists, you must set up security for it to allow the new system to write into
the structure.
● If the directory structure does not yet exist, you must create the core directory structure and a share to
make it available for other computers as well as setting the security on core directory structure.

The global transport directory \usr\sap\trans is used by the Change and Transport System (CTS). The CTS
helps you to organize development projects in the ABAP Workbench and in Customizing, and then transport
the changes between the SAP systems in your system landscape.

For more information about the CTS, see the SAP Library at :

SAP Release and SAP Library Quick Link SAP Library Path (Continued)

● SAP NetWeaver Mobile 7.1

Application Help Function-Oriented View: English
http://help.sap.com/nwmobile71
ABAP Technology Administration Tools for AS ABAP
● SAP NetWeaver Mobile 7.1 including Enhancement
Change and Transport System Transport Management
Package 1
http://help.sap.com/nwmobile711 System (BC-CTS-TMS)

● SAP NetWeaver 7.1 including Enhancement Package 1

for Banking Services from SAP 5.0 and 6.0 (see SAP
NetWeaver Mobile 7.1EhP1)

● SAP NetWeaver Process Integration 7.1

Application Help Function-Oriented View: English
http://help.sap.com/nwpi71
ABAP Technology Administration Tools for AS ABAP
● SAP NetWeaver Process Integration 7.1 Including En
Change and Transport System Transport Management
hancement Package 1
http://help.sap.com/nwpi711 System (BC-CTS-TMS)

● SAP NetWeaver 7.3:

Application Help SAP NetWeaver Library: Function-
http://help.sap.com/nw73
Oriented View Solution Life Cycle Management Software
● SAP NetWeaver 7.3 including Enhancement Package 1
Logistics Change and Transport System Change and
http://help.sap.com/nw731
● SAP NetWeaver 7.4 Transport System – Overview Basics of the Change and

http://help.sap.com/nw74 Transport System Transport Management System –

Concept

Prerequisites

The transport directory /usr/sap/trans only exists on your IBM i after you successfully finished an SAP
system installation. If there is already a directory /usr/sap/trans this directory should be linked to the local
directory /sapmnt/trans. However, if this link points to a remote host using QFileSvr.400 (/QFileSvr.400/
<GLOBALHOST>/sapmnt/trans), you must create the missing users on the remote host.

If there is a link /usr/sap/trans on your host pointing to a remote host, you have to create the following
users on this remote host:

● Installation user
● <SAPSID>ADM

 Note

When using QFileSvr.400, the passwords must be the same for each user on every host.

For more information about how to create an installation user on the remote host, see Preparing the SAP
Installation User on IBM i [page 91]. For more information about how to create <SAPSID> users using
CRTSAPUSR, see SAP Note 1123501 .

5.5.3 Qp2Term, Qp2Shell, and the Portable Application

Solution Environment

Use

The Portable Application Solution Environment delivers similar UNIX command line flexibility such as the
Qshell. IBM PASE for i (PASE for i) is more than just a shell interpreter, it is an entire programming environment
based on the AIX Application Binary Interface.

The Qp2Term program runs an interactive terminal application on the IBM i, similar to the Qshell command
line.

The Qp2Shell programs allow you to execute a shell script or a PASE for i application. Qshell accomplishes
these features by a command wrapper that either starts the Qshell command line, or executes scripts non
interactively.

You call the Qp2Term and Qp2Shell programs using command CALL mechanism.

 Recommendation

We recommend that you use Qp2Term instead of QShell.

Procedure

If not already installed, install option 33 of the license program 57nnSS1, the Portable Application Solution
Environment. For more information about Qp2Term, Qp2Shell and installing PASE for i, see the documentation
in the IBM Knowledge Center.

Use

You must install the Qshell on your IBM i. This gives you greater flexibility in dealing with stream files because
you can use a large set of utilities that are common on UNIX systems, for example, grep, tail, or ls.

In addition, Qshell is compatible with ksh scripts in UNIX.

Procedure

Install option 30 of the Qshell (license program 57nnSS1).

 Note

For more information about Qshell, see the IBM documentation.

5.5.5 Checking and Adjusting Operating System Values

Use

To allow the SAP system to run optimally on IBM i, you have to 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 do not work.

● You have applied all installed PTFs on your IBM i. To check this, enter the following command:
DSPPTF

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
Preparation PUBLIC 75
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>)
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 initial program load (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 81].

Checking and Adjusting Operating System Values

System Value Recommended Value Description

QMCHPOOL 10–15% of the entire main storage is as The fault rate in the *MACHINE pool should be as
signed to the machine pool low as possible, usually, lower than 5 (see SAP
Note 49201 ); otherwise, the pool must be in
creased. A change to this system value takes ef
fect immediately.

QACTJOB 1000 Set system value QACTJOB to a value close to the

number of jobs typically 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, ad
just this value to the value you typically see in the
field Jobs in system on the WRKSYSSTS com
mand.

QADLACTJ 500 Set system value QADLACTJ to 500 and system

value QADLTOTJ to 1000.
and 1000

QADLTOTJ

QSECURITY 30 or 40 System value QSECURITY controls the level of se

curity enforced on your system. Set QSECURITY
to at least 30 to ensure object security for the
SAP objects to be installed.

Security levels 10 and 20 are theoretically possi

ble. However, we do not recommend that you use
either of these values. Security level 10 provides
neither password nor object protection. Security
level 20 provides no object protection.

To activate this system value, you must perform

an initial program load (IPL).

QCTLSBSD QCTL When you start your IBM i, the program specified
in system value QSTRUPPGM (the default is
QSTRUP) is called. This startup program is re
sponsible 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 (controlling subsystem):

● QBASE
The controlling subsystem is QBASE. Subsys
tem QBASE is started.
● QCTL
The controlling subsystem is QCTL. Subsys
tems
QCTL,QINTER,QBATCH,QSPL,QCMN,QSERV
ER 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 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 wish the job message queue to be han
dled 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 interrupted. Once the installation is
complete, the system value is automatically re
turned 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 au

tomatically, set system value QAUTOCFG to 1.

QINACTITV *NONE IBM i V7R3 and higher: When running the SWPM
the system value QINACTIV must be set to
*NONE. Otherwise, the installation is maybe sud
denly 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 system, the value QBASACTLVL is the activity level of the base stor
needs to be increased. Use the following age pool. This value indicates how many system
formulas to calculate the increase: and user threads can compete at the same time
for storage in the base storage pool. This pool is
ABAP
specified in the subsystem descriptions as
Database server: *BASE. QBASACTLVL depends on the types of

(number of SAP work processes on data jobs run in this storage pool. The lower limit for

base server + number of SAP work proc QBASACTLVL is 1.

esses on each remote application server) * Note: This value does not affect only SAP work
1.20 processes but also processes and threads that

Application server: belong to other applications running on your sys

tem.
(number of SAP work processes on appli
cation server) * 1.20 Since the Java processes contains more than 100
threads, we strongly recommend that you adjust
Database server and application server: the Max Act (Maximum Active) value of the
(number of SAP work processes) * 1.20 memory pool your Java processes are running in.
To do this, enter command WRKSYSSTS and edit
Java the parameter Max Act or enter command
WRKSYSVAL with Option 2 to change system
Java server:
value QBASACTLVL. The change becomes active
(number of servers) * 700 immediately. As a rule of thumb, you have to add

ABAP + Java: to your current Max Act value a number of 700

for each Java server process you start on your
Add the values calculated for ABAP and
IBM i.
Java
 Example
When you install one Java only system on
your IBM i, this system has at the beginning
only one Java server (called server0). At that
point you have to add 700 to your current
Max Act value. When you later reconfigure
your Java only system to have two Java
server running in parallel (server0 and
server1) you have to add once again 700 to
your current Max Act value. Finally in total
you have added 1400 to Max Act value.

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

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

Use

When you use the operating system IBM i to start a partition or a server, the system automatically executes a
startup program that is used to start services, servers, and subsystems. The customers can change the startup
program that is delivered with the operating system.

 Recommendation

We highly recommend to start the services, servers and subsystems in the order shown below.

Procedure

To ensure that SAP Host Agent and SAP systems can start and work correctly, the following functions must be
executed by the startup program:

1. Automatic start of TCP/IP

2. Automatic start of the host servers
3. Start of the EDRSQL server
4. Only for Java systems: Start of the DDM-TCP/IP server
5. Automatic creation of directory entries under /QFileSvr.400
6. Start of the subsystem QUSRWRK

For more information about how to setup the startup program for SAP, see SAP Note 1703667 .

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

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
Preparation PUBLIC 81
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.

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.

 Note

Moving units takes several minutes.

12. Continue the procedure and complete the IPL.

13. Switch back to normal mode.

5.5.8 Configuring TCP/IP

Use

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

Prerequisites

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

● Make sure that you have the following information:

○ The interface of your IBM i to which the Local Area Network is attached
○ The IP addresses of your IBM i, subnet mask, and router or Gateway
○ The local domain name
○ The IBM i host name
● Decide on your IBM i host name. The host name cannot be longer than eight characters although SAP
allows 13 characters as of Release 4.6.
For more information, see SAP Note 611361 .

 Note

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

Procedure

 Note

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

1. To change the name of the computer, enter the command chgneta and prompt F4 .

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
Preparation PUBLIC 83
You must then enter the following information and choose ENTER :
○ System name
○ Local network ID
○ Default local location name
The following screen appears:

2. To set up the description line, enter the command WRKHDWRSC TYPE(*CMN) and proceed as follows:
1. On the Work with Communication Resources screen, enter option 5 (Work with configuration
descriptions) for the port and choose ENTER .
2. On the Work with Configurations Description screen, enter option 1 (Create) to enter the description
gigaline or ethline and choose ENTER . On the following screen, enter the line speed and duplex and
then press F10 and page down two screens.

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
Preparation PUBLIC 85
3. To call the TCP/IP configuration menu, enter the command CFGTCP and proceed as follows:
1. To work with interfaces, enter option 1 (Work with TCP/IP interfaces).

You need at least two entries: one for the loopback entry and one for the IP address of your IBM i.
The loopback address always takes the IP address 127.0.0.1, subnet mask 255.0.0.0 and line
description *LOOPBACK.
To add an entry, enter option 1 (ADD) and choose ENTER .
Add entries for the first three fields and accept the default values for the other fields.
2. To work with routes, enter option 2 (Work with TCP/IP routes).

If the route to the remote host, in this case the PC workstation, is through a Gateway or if the remote
host resides in a different network or subnetwork to the local host, you need to configure a route.
3. To change the domain information, enter option 12 (Change TCP/IP domain information).

 Note

It is important that you enclose your host name entry in single quotation marks. If you do not, the
IBM i interprets the characters as uppercase characters.

If you have one or more remote name servers, you need to define the IP address here. Note that the Host name
server priority must be set to *LOCAL.

Testing the TCP/IP Connection

Before proceeding with the SAP installation (that is, the installation of the executable programs), check that
this TCP/IP connection has been set up correctly. To do so, enter the command ping (Network Connection)
specifying your own system as Remote system. Do this twice, once specifying only <Host_Name>, and once
<Host_Name>.<Domain_Name>.

 Example

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

● ping 'as0008'

● ping 'as0008.wdf.sap.corp'

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

WRKLNK '/QFileSvr.400/<Host_Name>'

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

Result

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

5.5.9 Adjusting the Relational Database Name

Use

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

 Note

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

Procedure

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

2. To display your TCP/IP host name, enter the following command and press F4 :
CHGTCPDMN
3. Search for the contents of HOSTNAME.
This is your TCP/IP host name.
4. Before you can adjust the local RDB name, you have to check if the entry remote location equals
*Local exists. To do this, enter the following command:
WRKRDBDIRE
5. Depending on the outcome, proceed as follows:
○ If an entry for RDB name exists and you want to adjust the name to the TCP/IP host name
<TCP_Host_Name>, enter the following command:
CHGRDBDIRE RMTLOCNAME(*LOCAL *IP) PORT(*DRDA)
RMTAUTMTH(*ENCRYPTED *ALWLOWER) DEV(*LOC) LCLLOCNAME(*LOC)
RMTNETID(*LOC) MODE(*NETATR) TNSPGM(*DRDA)
○ If an entry for RDB name does not exist and a different entry exists with Remote Location *LOCAL you
have to delete it using RMVRDBDIRE RDB(<Current_RDB_*LOCAL>). Afterwards go to the next step
and add the required RDB name.
○ If an entry for RDB name does not exist, you have to add one with the correct name
<TCP_Host_Name>.

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
90 PUBLIC Preparation
To do this, enter the following command:
ADDRDBDIRE RDB(<TCP_Host_Name>)
RMTLOCNAME(*LOCAL *IP) PORT(*DRDA)
RMTAUTMTH(*ENCRYPTED *ALWLOWER) DEV(*LOC) LCLLOCNAME(*LOC)
RMTNETID(*LOC) MODE(*NETATR) TNSPGM(*DRDA)
6. If you are planning to use an independent ASP, make sure there is an entry for it in the RDB directory.

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

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.

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

 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

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)

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.

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.

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

5.5.13 Distribution of Libraries on ASPs

Disk units that are attached to an IBM i server are combined into one or multiple auxiliary storage pools (ASPs).
You always have an ASP 1, also known as system ASP. Optionally, you can configure one or multiple additional
ASPs. These are called user ASPs.

Before you run the installer to install your SAP system, you must decide on the following:

● Which ASP you want to use to install new libraries for ABAP

For a production system, we recommend that you use two different ASPs for the database library and database
journal receiver library. Make sure that the database library and the database journal receiver library are
located on separate physical disks and not merely on different virtual ASPs that reside on the same physical
disk. This is necessary to prevent that a single hardware failure of a disk unit destroys both the database and
the database journal receiver. For test and quality assurance systems, both the database and journal receiver
libraries can be installed on the same ASP.

 Note

● The database and journal receiver libraries can be installed only in the same ASP group.
● The database library can only be installed on the system ASP (1), user ASP (2-32) or on a primary
independent ASP.
● The journal receiver library can be installed on a system ASP (1), user ASP (2-32), on a primary
independent
ASP or on a secondary independent ASP.

5.6 Installing the SAP Front-End Software

Before you start the installation, make sure that the SAP front-end software is installed on at least one
computer in your system environment to be able to log on to the SAP system after the installation has finished.

Procedure

1. Check SAP Note 147519 for the recommended SAP front-end release.
2. Install the SAP front-end software required for your SAP system release as described in the documentation
SAP Frontend Installation Guide - <Release> at: https://wiki.scn.sap.com/wiki/display/ATopics/SAP+GUI
+Family

5.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 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
(SWPM10RMSP30_Version.SAR) Archive [page 99].

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
94 PUBLIC Preparation
● The media containing the software to be installed. These are the following:
○ Kernel media:
You can make them available 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 SAP Kernel Archives (Archive-Based Installation) [page
101].
○ Use the physical installation media as part of the installation package.
For more information, see Media Required for the Installation - Listed by SAP System Instance
[page 95].
○ Download the complete kernel media from the SAP Software Download Center.
For more information, see Downloading Complete Installation Media [page 103].
○ RDBMS and export media.
You can make them available in one of the following ways:
○ Use the physical installation media as part of the installation package.
○ Download the complete kernel media from the SAP Software Download Center.
For detailed information about how to obtain these media, see Media Required for the Installation - Listed
by SAP System Instance [page 95].

Media Required for the Installation - Listed by SAP System Instance [page 95]
This section provides a list of the media required for the installation, listed by SAP system instance to
be installed.

5.7.1 Media Required for the Installation - Listed by SAP

System Instance

This section provides a list of the media required for the installation, listed by SAP system instance to be
installed.

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 118] ). The installer
only accepts media whose signature has been checked. For more information, see SAP Note 2393060 .

For more information about which kernel version to use, see SAP Note 1680045 . In addition, check the
Product Availability Matrix at: http://support.sap.com/pam .

For more information about release and roadmap information for the kernel versions, and how this relates to
SAP NetWeaver support packages - including important notes on downward compatibility and release dates -
see SAP Note 1969546 .

Proceed as follows to make the media available:

1. Identify the required media for your installation [page 22] as listed below.
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 105].
If not already done, 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 file system to the IFS on your IBM i.

ABAP Central ○ Software Provisioning Manager 1.0 archive

services in ○ UC or NUC Kernel (folder K_<Version>_<N or U>_<OS>) where U means Unicode and N
stance (ASCS means non-Unicode.
instance)
 Note
Every new installation of an SAP system is Unicode. You can only use the non-Unicode ker
nel if you perform the system copy for a non-Unicode SAP system that has been upgraded
to the current release.

Central services ○ Software Provisioning Manager 1.0 archive

instance (SCS ○ UC Kernel (folder K_<Version>_U_<OS>) where U means Unicode.

instance)

Database in ○ Software Provisioning Manager 1.0 archive

stance ○ UC or NUC Kernel (folder K_<Version>_<N or U>_<OS>) where U means Unicode and N
means non-Unicode.

 Note
Every new installation of an SAP system is Unicode. You can only use the non-Unicode ker
nel if you perform the system copy for a non-Unicode SAP system that has been upgraded
to the current release.

○ Installation Export (folders EXP*)

○ SAP NetWeaver AS for Java Component (folders JAVA_*)

Enqueue Repli ○ Software Provisioning Manager 1.0 archive

cation Server ○ UC or NUC Kernel (folder K_<Version>_<N or U>_<OS>) where U means Unicode and N
means non-Unicode.

Primary appli ○ Software Provisioning Manager 1.0 archive

cation server in ○ UC or UC & NUC (folder K_<Version>_<N or U>_<OS>) where U means Unicode and N
stance means non-Unicode.

○ Installation Export (folders EXP*)

○ SAP NetWeaver AS for Java Component (folders JAVA_*)
○ CLI Driver / JDBC Driver

Additional appli ○ Software Provisioning Manager 1.0 archive

cation server in ○ UC or UC & NUC (folder K_<Version>_<N or U>_<OS>) where U means Unicode and N
stance means non-Unicode.

 Note
If you install an additional application server instance in an existing non-Unicode system,
the additional application server instance is created automatically as a non-Unicode in
stance. The installer checks whether a non-Unicode system exists and chooses the right ex
ecutables for the system type.

○ SAP NetWeaver AS for Java Component (folders JAVA_*)

SAP Host Agent (Separate Installation Only)

SAP Instance Installation Required Media

SAP Host Agent (separate installation only) ○ Software provisioning manager 1.0 archive
○ UC Kernel (folder K_<Version>_U_<OS>) where U
means Unicode.

2. Make the installation media available on your Windows PC as follows:

1. Download and unpack the latest version of Software Provisioning Manager as described in
Downloading and Extracting the Software Provisioning Manager 1.0 (SWPM10RMSP30_Version.SAR)
Archive [page 99].
2. Make the kernel media available.
You can do this in one of the following ways:
○ Download the dedicated kernel archives - this is the recommended way.
For more information, see Downloading SAP Kernel Archives (Archive-Based Installation) [page
101].
○ Use the physical kernel medium from the installation package.
You can do this in one of the following ways:
○ Copy the required media folders directly to the installation hosts.
○ Mount the media on a central media server that can be accessed from the installation hosts.

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
Preparation PUBLIC 97
To make 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 all copied directories and files on your IBM i host.
You need to copy the installation media manually to your IBM i [page 105].

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

○ Download the kernel medium from the Software Download Center.

For more information, see Downloading Complete Installation Media [page 103].

 Note

Even if you use the complete kernel media, the installer might prompt you during the provisioning
process for additional archives (*.SAR files) due to special Patch Level (PL) requirements
depending on categories such as the product, operating system, and database platform at the end
of this section.

For example: The installer might require a certain PL of <X> of the SAPEXEDB.SAR (for DBTYPE
<Y>), but this PL of the SAPEXEDB.SAR is not contained in the SAP kernel media . In this case you
have to download the required PL from https://launchpad.support.sap.com/#/softwarecenter
following the instructions in Downloading SAP Kernel Archives (Archive-Based Installation) [page
101].

 Note

If you perform an additional application server installation, kernel archives - such as

SAPEXE<Version>.SAR, SAPEXEDB<Version>.SAR, IGSEXE<Version>.SAR,
igshelper<version>.sar, SAPJVM<Version>.SAR - are only prompted if they cannot be
retrieved from the primary application server instance or the ASCS instance of the existing SAP
system.

3. Make the RDBMS and export media. available.

You can do this in one of the following ways:
○ Copy the required media folders directly to the installation hosts.
○ Mount the media on a central media server that can be accessed from the installation hosts.
To make 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 all copied directories
and files on your IBM i host.
You need to copy the installation media manually to your IBM i [page 105].

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

3. If you want to perform target system installation in the context of a heterogeneous system copy you need
a migration key. You can generate it at https://support.sap.com/migrationkey .

Downloading and Extracting the Software Provisioning Manager 1.0 (SWPM10RMSP30_Version.SAR) Archive
[page 99]
Downloading SAP Kernel Archives (Archive-Based Installation) [page 101]
Downloading Complete Installation Media [page 103]
Copying the Installation Media Manually to Your IBM i [page 105]
Copying the Installation Media Manually to Your IBM i [page 105]

5.7.1.1 Downloading and Extracting the Software

Provisioning Manager 1.0
(SWPM10RMSP30_<Version>.SAR) Archive

You must always download the latest version of the SOFTWARE PROVISIONING MGR SP30 SWPM10_IM_<OS>
medium and extract the contained SWPM10RMSP30_<Version>.SAR archive.

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 .

Context

An up-to-date version of the load tools - such as R3load, R3szchk, R3ldctl, SAPuptool - which were
available so far only in the SAPEXEDB.SAR archive of the kernel media, has now been made available in the

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
Preparation PUBLIC 99
Software Provisioning Manager archive (SWPM10RMSP30_<Version>.SAR), in a sub-archive named
LOADTOOLS.SAR, located in the COMMON/LOADTOOLS folder. For an installation using kernel version 7.40 or
higher, the load tools from the SWPM10SP<Support_Package_Number>_<Version_Number>.SAR are used
automatically instead of the loadtools available in the SAPEXEDB.SAR archive of the kernel media. There is no
action required from your side, the installer uses the relevant loadtools automatically once you run it from the
extracted SWPM10RMSP30_<Version>.SAR archive.

Procedure

1. Get the latest version of the Software Provisioning Manager 1.0 (SWPM10RMSP30_<Version>.SAR)
archive:
a. Download and unzip the latest version of the SOFTWARE PROVISIONING MGR SP30
SWPM10_IM_<OS> medium from:

https://launchpad.support.sap.com/#/softwarecenter INSTALLATIONS & UPGRADES By

Category SAP TECHNOLOGY COMPONENTS SL TOOLSET SL TOOLSET 1.0 Installation
51054279_<No> SOFTWARE PROVISIONING MGR SP30 SWPM10_IM_<OS>
b. Change to the DATA_UNITS\SWPM10_IM_<OS> folder contained within the unzipped medium and
copy the SWPM10RMSP30_<Version>.SAR archive contained in this medium to a local directory on
your Windows PC.

For more information, see SAP Note 2980160 .

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 SWPM10RMSP30_<Version>.SAR archive to a local directory on your Windows PC using the
following command:

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

\SWPM10RMSP30_<Version>.SAR.SAR -R <Path to Unpack Directory>

 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 SWPM10RMSP30_<Version>.SAR 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 105].

Instead of downloading the complete SAP kernel media, we recommend that you download the SAP kernel
archives specificly required for your installation option. 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.

Context

The signature of installation archives is checked automatically by the installer [page 118] 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 .

Procedure

2. Go to https://launchpad.support.sap.com/#/softwarecenter SUPPORT PACKAGES & PATCHES

By Category
3. Choose the required software component, release, and technical stack:

○ If you want to install SAP NetWeaver Process Integration 7.1 or SAP NetWeaver Process Integration 7.1
EHP1, choose SAP NetWeaver and complementary products SAP NETWEAVER PI 7.1X Entry by
Component
○ If you want to install SAP NetWeaver Process Integration 7.3, 7.3 EHP1, or 7.4, choose both of the
following:
○ SAP NetWeaver and complementary products SAP NetWeaver <Release> Entry by
Component Application Server ABAP
○ SAP NetWeaver and complementary products SAP NetWeaver <Release> Entry by
Component Application Server Java
4. Choose the required package:

 Note

If you perform an additional application server installation, kernel archives - such as

SAPEXE<Version>.SAR, SAPEXEDB<Version>.SAR, IGSEXE<Version>.SAR,
igshelper<version>.sar, SAPJVM<Version>.SAR - are only prompted if they cannot be retrieved
from the primary application server instance or the ASCS instance of the existing SAP system.

○ Make sure that you always use the highest available patch level unless special patch levels are
specified for the relevant package in SAP Note 2980160 .
○ Make sure that you always choose SAPEXE<Version>.SAR, SAPEXEDB<Version>.SAR of the
same SAP kernel release and extension.

 Example

○ If SAPEXE<Version>.SAR is of version 7.53 DCK, then SAPEXEDB<Version>.SAR must

also be of version 7.53 DCK.
○ If SAPEXE<Version>.SAR is of version 7.49, then SAPEXEDB<Version>.SAR must also
be of version 7.49.

○ If you provide the archives in one download folder, and there is more than one version of the same
archive available - for example SAPEXE<Version>.SAR - and these versions match the product-
specific requirements, the installer selects one of these archive versions. If you want a specific
archive version to be used, make sure that this is the only version available in the download folder.
When running system provisioning in GUI mode, you can also check in the GUI which archive is
being used. So even if there is more than one version of the same archive available in the download
folder, you can select the exact archive version you want to use and enter the exact path to the
required archive file.

○ SAPEXE<Version>.SAR
SAP KERNEL <Version> <UC> <Operating System> #DATABASE INDEPENDENT
○ If you want to install an SAP system based on SAP NetWeaver 7.4, you can choose either 7.53 DCK
or 7.49 UNICODE for SAP KERNEL <Version>.
○ If you want to install an SAP system based on SAP NetWeaver 7.3 EHP1 or lower, choose 7.22 EXT
for SAP KERNEL <Version>.
○ SAPEXEDB<Version>.SAR
Choose the version corresponding to the SAPEXE<Version>.SAR from SAP KERNEL <Version>
<UC> <Operating System> <DATABASE>
○ igsexe<Version>.sar
SAP IGS <Version> <Operating System>
○ If you want to install an SAP system based on SAP NetWeaver 7.4, choose SAP IGS <7.53 or
higher> # OS independent .
○ If you want to install an SAP system based on SAP NetWeaver 7.3 EHP1, choose SAP IGS
7.20_EXT # OS independent
○ If you want to install an SAP system based on SAP NetWeaver 7.3 or lower and use SAP kernel
7.22_EXT, choose SAP IGS 7.20_EXT <Operating System>
○ If you want to install an SAP system based on SAP NetWeaver 7.3 or lower and use SAP kernel 7.22,
choose SAP IGS 7.20 <Operating System>
○ If you want to install an SAP system based on SAP NetWeaver 7.3 EHP1 or higher, you require the
igshelper<Version>.sar.
Choose SAP IGS HELPER # OS independent
○ SAPJVM<Version>.SAR:
SAP JVM <Version> <Operating System>

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
102 PUBLIC Preparation
○ If you want to install an SAP system based on SAP NetWeaver 7.4 or lower, choose SAP JVM
6.1.<Version> <Select Your Operating System>
○ SAPHOSTAGENT<Version>.SAR
SAP HOST AGENT 7.21 <Operating System>

 Recommendation

It is highly recommended that you always choose the highest SP version of the
SAPHOSTAGENT<SP-version>.SAR archive.

 Note

The SAPHOSTAGENT<Version>.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<Version>.SAR .Otherwise, the existing SAP Host Agent is not upgraded.

5. If you want to install an SAP system based on SAP NetWeaver 7.3 EHP1 or lower - that is you have to use
SAP kernel 7.22 - download the latest patch level of SAPCRYPTOLIB <Version>.SAR from the following
path:

https://launchpad.support.sap.com/#/softwarecenter Support Packages and Patches By Category

Additional Components SAPCRYPTOLIB COMMONCRYPTOLIB<Version> <Operating
System>
6. Make the RDBMS and the export media available - either by using physical media as described in Media
Required for the Installation - Listed by SAP System Instance [page 95] or by downloading them as
described in Downloading Complete Installation Media [page 103].

5.7.1.3 Downloading Complete Installation Media

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

Procedure

1. Download and unpack the latest version of Software Provisioning Manager as described in Downloading
and Extracting the Software Provisioning Manager 1.0 (SWPM10RMSP30_Version.SAR) Archive [page 99].
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 als listed in Media Required for the Installation - Listed by SAP System
Instance [page 95] .
4. Identify all download objects that belong to one medium according to one of the following:

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<Current Version> Download Kernel
releases delivered for SL Toolset SL TOOLSET 1.0 (INSTALLATIONS AND UPGRADES) KERNEL
FOR INSTALLATION/SWPM .
○ To download all media required for your SAP product, you can use one of the following navigation
paths:
○ https://launchpad.support.sap.com/#/softwarecenter INSTALLATIONS & UPGRADES
By Category SAP NETWEAVER AND COMPLEMENTARY PRODUCTS <Product>
<Product Release>
○ https://launchpad.support.sap.com/#/softwarecenter INSTALLATIONS & UPGRADES
By Alphabetical Index (A-Z) <First Letter of Product> <Product> <Product
Release>
○ Material number
All download objects that are part of an installation medium have the same material number and an
individual sequence number:
<Material_Number>_<Sequence_Number>

 Example

51031387_1

51031387_2

...

○ Title
All objects that are part of an installation medium have the same title, such as
<Solution><Media_Name><OS>.
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 105].

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

5.7.1.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:

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

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:\ 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.

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

● K_<Version>_<U or N>_OS400_PPC64
● EXP*
● JAVA*
● SL_CONTROLLER_<nnn>

6.1 Installation Checklist

This section includes the installation steps for the following:

● Standard system
● Distributed system
● High-availability system
● Additional application server instance

Detailed information about the steps are available in the linked sections.

 Note

The installer uses the UID and GID of the DEFAULT.PFL file in the SAPGLOBALHOST and assumes that the
UID belongs to the user <SAPSID>ADM and the GID to the group R3GROUP. To have a successful distributed
landscape installation, you must do the following:

1. Make sure the UID for the user <SAPSID>ADM and the GID for the group R3GROUP are available across
all of the system landscape. You can set these values from the installer GUI.
2. Additional users <SAPSID>OWNER and SAP<SAPSID>DB are also created during the installation. The
installer does not make sure the UIDs for these users match across the landscape. It is not required to
have matching UIDs, but it causes delays during database switchover scenarios.
3. After installing the SAPGLOBALHOST, you must check to make sure that the DEFAULT.PFL file is owned
by the user <SAPSID>ADM and the primary group is In every additional installation option on a host
distinct from R3GROUP.
4. SAPGLOBALHOST, you must check that the installer contains the right values for UID and GID for the
users displayed on the Summary screen.

Standard System

1. You check the prerequisites [page 115] and run the installer [page 118] to install the SAP system.

 Note

In a standard system, all mandatory instances are installed on one host in one installation run.

2. You continue with Post-Installation [page 132].

1. If you want to share the transport directory trans from another remote system, you have to make it
available on all related hosts of the distributed SAP system installation using QFileSvr.400. Otherwise, we
recommend that you share the trans directory that is created during the installation of the primary
application server instance. For more information, see Setting Up the Transport Directory [page 143].
2. On the ASCS instance host, you do the following:
1. You check the prerequisites [page 115] and run the installer [page 118] to install the ABAP central
services instance (ASCS instance).

 Note

If you want to install an ASCS instance with integrated SAP Web Dispatcher [page 29] or with
integrated SAP Gateway [page 30] or both, you must choose the Custom parameter mode.

When processing the screens for the ASCS instance installation, you are prompted to mark the
corresponding checkbox on the screen Additional Components to be Included in the ASCS
Instance.

If you mark the checkbox for SAP Web Dispatcher, you are prompted for the additional parameters
required for the SAP Web Dispatcher installation on the subsequent screens.

3. On the SCS instance host, you do the following:

1. You check the prerequisites [page 115] and run the installer [page 118] to install the central services
instance (SCS instance).
4. On the database instance host, you do the following:
1. You link the global directories [page 113] in <sapmnt>/<SAPSID> from the SAP global host and –
optionally – the trans directory from the SAP transport host.
2. You check the prerequisites [page 115] and run the installer [page 118] to install the database
instance.
5. On the primary application server instance host, you do the following:
1. You link the global directories [page 113] in <sapmnt>/<SAPSID> from the SAP global host.
2. You check the prerequisites [page 115] and run the installer [page 118] to install the primary
application server instance.
6. You continue with Post-Installation [page 132].

Graphical Overview

Distribution of Instances in an ABAP+Java System

High-Availability System

 Note

The following procedure is only an example. In this example, we use only one primary cluster node, host A,
and one standby cluster node, host B. However, for your production system, we recommend that you have
more that one standby node.

If required, you can also install the ASCS instance and the SCS instance on different hosts.

In this case, you require:

● At least one primary cluster node, host A1, for the primary node with the ASCS instance, and at least
one primary cluster node, host A2, for the primary node with the SCS instance.
● At least one standby node, host B1, for the primary node with the ASCS instance, and at least one
standby node, host B2, for the primary node with the SCS instance.

1. You make sure that you have already prepared the standby node, host B. You ought to have already made
sure that it meets the hardware and software requirements and that it has all the necessary file systems,
mount points, and (if required) Network File System (NFS), as described in Performing Switchover
Preparations for High Availability [page 70].
2. If you want to share the transport directory trans from another remote system, you have to make it
available on this system. Otherwise, we recommend that you share the trans directory that is created
during the installation of the primary application server instance. For more information, see Setting Up the
Transport Directory [page 143].

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
110 PUBLIC Installation
3. You set up the switchover cluster infrastructure as follows:
1. You check the prerequisites [page 115] and run the installer [page 118] to install the ABAP central
services instance (ASCS instance) on the primary cluster node, host A. Use a virtual host name [page
69].

 Note

If you want to install an ASCS instance with integrated SAP Web Dispatcher [page 29] or with
integrated SAP Gateway [page 30] or both, you must choose the Custom parameter mode.

When processing the screens for the ASCS instance installation, you are prompted to mark the
corresponding checkbox on the screen Additional Components to be Included in the ASCS
Instance.

If you mark the checkbox for SAP Web Dispatcher, you are prompted for the additional parameters
required for the SAP Web Dispatcher installation on the subsequent screens.

2. You check the prerequisites [page 115] and run the installer [page 118] to install the ERS instance for
the ASCS instance on the primary cluster node, host A. Use a virtual host name [page 69].
3. You check the prerequisites [page 115] and run the installer [page 118] to install the SCS instance on
the primary cluster node, host A. Use a virtual host name [page 69].
4. You check the prerequisites [page 115] and run the installer [page 118] to install the ERS instance for
the SCS instance on the primary cluster node, host A. Use a virtual host name [page 69].
5. You prepare the standby cluster node, host B, making sure that it meets the hardware and software
requirements and it has all the necessary file systems, mount points, and (if required) Network File
System (NFS).
6. You configure the switchover software and test that switchover functions correctly to all standby nodes
in the cluster.
7. You repeat the following steps until you have finished installing the ERS instance on all nodes in the
cluster:
1. You perform the switchover to a node where you want to install the ERS instance for the ASCS
instance.
2. You check the prerequisites [page 115] and run the installer [page 118] to install the ERS instance
for the ASCS instance on the standby node, host B.
3. You perform the switchover to a node where you want to install the ERS instance for the SCS
instance.
4. You check the prerequisites [page 115] and run the installer [page 118] to install the ERS instance
for the SCS instance on the standby node, host B.
4. On the database instance host, you do the following:

 Recommendation

We recommend that the database instance is part of the hardware cluster or of any other proprietary
high-availability solution for the database.

1. You make available the global directories in <sapmnt>/<SAPSID> from the switchover cluster
infrastructure and – optionally – from the SAP transport host.
2. You check the prerequisites [page 115] and run the installer [page 118] to install the database instance
on the database instance host.

 Note

In a high-availability installation, the primary application server instance does not need to be part of the
cluster because it is no longer a single point of failure (SPOF). The SPOF is now in the central services
instance (SCS instance) and ABAP central services instance (ASCS instance), which are protected by
the cluster.

1. You link the global directories [page 113] in <sapmnt>/<SAPSID> from the switchover cluster
infrastructure.
2. You check the prerequisites [page 115] and run the installer [page 118] to install the database instance
on the database instance host.

 Recommendation

We recommend that the database instance is part of the hardware cluster or of any other
proprietary high-availability solution for the database.

3. You check the prerequisites [page 115] and run the installer [page 118] to install the primary
application server instance.
6. We recommend you to install additional application server (AS) instances to create redundancy.
The AS instances are not a SPOF. Therefore, do not include these instances in the cluster.
7. You continue with Post-Installation [page 132].

Graphical Overview

The following figure provides an overview of how you install the various instances in a high-availability
installation:

Distribution of Instances in a High-Availability ABAP+Java System

Installation Steps for Additional Application Server Instances for a Standard System

1. On every additional application server instance host, you do the following:

1. You link the global directories [page 113] in <sapmnt>/<SAPSID> from the SAP global host.
2. You check the prerequisites [page 115] and run the installer [page 118] to install the additional
application server instance.
2. You continue with Post-Installation [page 132].

Installation Steps for an Application Server Instance for a Distributed System

1. If you want to share the transport directory trans from another system, you have to make it available from
this system. Otherwise we recommend that you share the trans directory that is created during the
installation of the primary application server instance. For more information, see Setting Up the Transport
Directory [page 143].
2. On every additional application server instance host, you do the following:
1. You link the global directories [page 113] in <sapmnt>/<SAPSID> from the SAP global host.
2. You check the prerequisites [page 115] and run the installer [page 118] to install the additional
application server instance.
3. You continue with Post-Installation [page 132].

Installation Steps for an Additional Application Server Instance for a High-Availability System

 Note

For information about configuration and administration of the switchover infrastructure on IBM i, see SAP
Note 1635602 .

1. If you want to share the transport directory trans from another system, you have to make it available from
this system. Otherwise we recommend that you share the trans directory that is created during the
installation of the primary application server instance. For more information, see Setting Up the Transport
Directory [page 143].
2. On each additional application server instance host, do the following:
1. You make available the global directories [page 113] in <sapmnt>/<SAPSID> from the SAP global
host.
2. You check the prerequisites [page 115] and run the installer [page 118] to install the additional
application server instance.
3. You continue with Post-Installation [page 132].

6.2 Linking Global Directories

Use

If you install an instance on a host other than the SAP global host, you must make available the global
directories from the SAP global host, and you have to link to the global directories using the command ADDLNK.

You make sure the /QFileSvr.400/<SAPGLOBALHOST> directory is always available after the initial program
load (IPL) of the additional host. For more information, see Adjusting Startup Program QSTRUP [page 81].

 Note

If you have installed the SAPGLOBALHOST on a virtual host, you must use the virtual hostname to create

the directory /QFileSvr.400/<virtual_hostname_SAPGLOBALHOST> on the additional host.

Procedure

1. Make sure that the global transport directory is also available on every host where you want to install an
SAP instance. Otherwise, the installation fails. For more information, see Setting Up the Transport
Directory [page 143].
2. Log on to the host of the new instance that you want to install as the SAP installation user that later
executes the installation. This SAP installation user must exist in IBM i systems in the distributed system
landscape.
For more information about how to create the installation user, see Preparing the SAP Installation User on
IBM i [page 91].
3. Create the following link to the SAP global host file system:
ADDLNK OBJ('/QFileSvr.400/<SAPGLOBALHOST>/sapmnt/<SAPSID>') NEWLNK('/sapmnt/
<SAPSID>')

 Note

If you have installed the global directories of your SAP system into an IASP, you have to add the IASP

directory name to the path of the link target:

ADDLNK OBJ('/QFileSvr.400/<SAPGLOBALHOSTSAPGLOBALHOST>/<IASP_Name>/sapmnt/
<SAPSID>) NEWLNK('/sapmnt/<SAPSID>')

During the installation of your SAP system, you have to specify the initial data source of the User Management
Engine (UME).

Prerequisites

You have planned how you want to configure user and access management for your SAP system to be installed
as described in Planning User and Access Management [page 43].

Procedure

Using AS ABAP
You install your SAP system as described in this installation guide. During the installation, the SAP system is
automatically configured to use AS ABAP as data source for the User Management Engine (UME). After the
installation has finished, you can still change the user management configuration. For more information, see
Configuring User Management [page 153].

Using an LDAP directory as Source for User Data

1. You install your SAP system as described in this installation guide.
2. Configure the user management of the newly installed SAP system to use an LDAP directory.
For more information, see Configuring User Management [page 153].

6.4 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

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
Installation PUBLIC 115
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 118] . 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 122].

● 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 <sapsid>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 91].
● 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 122].

Some tools such as jsplitter may create files while the installer is running. The required free space
in the /tmp directory depends on the amount of databases which you intend to unload.

● Make sure that you have defined the most important SAP system parameters as described in Basic
Installation Parameters [page 46] before you start the installation.
● Check that your installation host meets the requirements for the installation options that you want to
install.
For more information, see Running the Prerequisite Checker [page 35].
● If you want to install an additional application server instance in an existing SAP system, make sure that:
○ There is exactly one entry in the /usr/sap/sapservices file for each SAP instance installed on this
host. Be sure to check that the entry refers to the correct profile.
○ There are no profile backup files with an underscore “_” in their profile name. If so, replace the “_” with
a “.”.

 Example

Rename /usr/sap/S14/SYS/profile/S14_D20_zsi-aix693p2_D20081204
to /usr/sap/S14/SYS/profile/S14_DVEBMGS20_zsi-aix693p2.D20081204.

● If you are installing an additional SAP system into an existing database, see Multiple SAP Systems on a
Single Host [page 173].
● 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=<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 installer
processing.
The filled-out evaluation form is then sent to SAP using HTTPS.
If this port cannot be used, you can assign a free port number by executing sapinst with the following
command line parameter:
SAPINST_HTTP_PORT=<Free Port Number>
● If you want to perform the installation in unattended mode, see SAP Note 2230669 which describes an
improved procedure using inifile.params.

This section describes how to run the installer.

Prerequisites

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

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

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

 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('<Path_To_Unpack_Directory>')

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

 Note

If you need to assign virtual host names to the instance to be installed, and it is not possible to do this
(for example, for database instances) by specifying it as an input parameter on the <Instance Name>

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
118 PUBLIC Installation
Instance screen, you can assign a virtual host name by starting the installer with the
SAPINST_USE_HOSTNAME property:

CD DIR('<Path_To_Unpack_Directory>')

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

'SAPINST_USE_HOSTNAME=<Virtual_Host_Name>')

For more information, see Virtual Host Name in SAP System Parameters [page 47].

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://[<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 installer as described in Useful Information about the Installer [page 122].
2. Restart the installer 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 the Installer [page
115]).

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

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
Installation PUBLIC 119
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:
○ Perform preparations
Go to Generic Options <Database> Preparations and choose the required task.
To install SAP Host Agent separately, choose Generic Options <Database> Preparations SAP
Host Agent .
○ Install an SAP system:
○ To install an SAP Process Integration system based on SAP NetWeaver 7.1 to 7.4 from scratch,
choose SAP NetWeaver <Release> <Database> Installation Process Integration
<System Variant> .
○ To install an SAP Process Integration system based on SAP NetWeaver 7.1 to 7.4 as target system
of a system copy, choose SAP NetWeaver <Release> <Database> System Copy Target
System <System_Variant> Based on AS ABAP and AS Java .
○ Install an additional SAP system instance, go to <Product> <Database> Additional SAP
System Instances Additional Application Server Instance .
○ Perform other tasks or install additional components
Go to Generic Options <Database> and choose the required task.
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

If you want to install an ASCS instance with integrated SAP Web Dispatcher [page 29] or with
integrated SAP Gateway [page 30] or both, you must choose the Custom parameter mode.

When processing the screens for the ASCS instance installation, you are prompted to mark the
corresponding checkbox on the screen Additional Components to be Included in the ASCS Instance.

If you mark the checkbox for SAP Web Dispatcher, you are prompted for the additional parameters
required for the SAP Web Dispatcher installation on the subsequent screens.

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.
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 <Option_Name> has completed.
8. If you copied the installer software to your hard disk, you can delete these files when the installation has
successfully completed.
For more information, see Removing the Installer Installation Files [page 161].
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/<Installation_User>/.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 122].

6.6 Additional Information about the Installer

The following sections provide additional information about the installer.

Useful Information about the Installer [page 122]

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
Installation PUBLIC 121
This section contains some useful technical background information about the installer and the
installer GUI.

Interrupted Processing of the Installer [page 124]

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

Entries in the Services File Created by the Installer [page 127]

Troubleshooting with the Installer [page 128]

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

Troubleshooting During the Database Load [page 129]

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

6.6.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.
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 115].
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/<User> directory where it keeps its log files. <User> 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.

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
122 PUBLIC Installation
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('<Directory>')

REPLACE(*YES)

Qp2Term export TEMP=<Directory>

 Note

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

 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
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('<Path_To_Unpack_Directory>')
CALL PGM(QP2TERM) PARM('./sapinst' '-p')
● If you want to perform the installation in unattended mode, see SAP Note 2230669 which describes an
improved procedure using inifile.params.

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

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

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

 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 118] .
2. Make sure that the installation media are still available.

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

 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 94] .

 Recommendation

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

Enter the following commands:

CD DIR('<Path_To_Unpack_Directory>')

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

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.

 Note

Open the URL on a device with a supported web browser (see Prerequisites for Running the Installer [page
115]).

 Caution

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.
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/<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 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:

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

6.6.3 Entries in the Services File Created by the Installer

After the installation has finished successfully, the installer has created the following entries in the service
table:

To review the entries, use the command WRKSRVTBLE.

Service Table

Service Port Protocol

sapdp<nn> 32<nn> tcp

sapdp<nn>s 47<nn> tcp

sapgw<nn> 33<nn> tcp

sapgw<nn>s 48<nn> tcp

sapms<SAPSID> 36<nn> tcp

(unless you specified another value during the in

stallation)

sapxdn<SAPSID> 96<xx> tcp

 Note

● There is a port created for every possible instance number, regardless of which instance number you
specified during the installation. For example, for sapgw<Instance_Number> =
33<Instance_Number>/tcp the following range of entries is created:
sapgw00 = 3300/tcp
sapgw01 = 3301/tcp
sapgw02 = 3302/tcp
[...]
sapgw98 = 3398/tcp
sapgw99 = 3399/tcp
● If there is more than one entry for the same port number, this is not an error.
● <Instance_Number> is the number of the instance in which the ABAP message server is running.

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

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/<User> directory, where <User> is the user
that you used to start the installer.

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

○ To check the log and trace files of the installer GUI for errors, go to the directory /home/
<Installation_User>/.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 124].
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 .

6.6.5 Troubleshooting During the Database Load

The database load is divided into several sections, which are performed in parallel. Each section writes a log file
to your installation directory. The names of these files are as follows:

● SAP0000.log
● SAPUSER.log
● SAPSSRC.log
● SAPSSEXC.log
● SAPSPROT.log
● SAPSLOAD.log
● SAPSLEXC.log
● SAPSDIC.log
● SAPSDOCU.log
● SAPPOOL.log
● SAPCLUST.log
● SAPAPPL2.log
● SAPAPPL1.log
● SAPAPPL0.log
● SAPVIEW.log
● SAPDDIM.log
● SAPDFACT.log
● SAPDODS.log

1. If errors occur during database load find out which load process failed by checking the log files. You can do
this by entering:
EDTF '/<Installation_Directory>/<Log_File>.log'

 Example

EDTF '/<Installation_Directory>/SAPSDIC.log'

The log file contains additional information about the status of the job and the corresponding IBM i job.
2. Scroll to the bottom of this file and check the error message.
The start of each import attempt is logged to this file and looks like this:
TS61CEO34/R3LOADDB4: START OF LOG: 20010926170456
TS61CEO34/R3LOADDB4: sccsid @(#) $Id:
//bas/620_COR/src/R3ld/R3load/R3ldmain.c#4 $ SAP
TS61CEO34/R3LOADDB4: version R6.10/V1.
TS61CEO34/R3LOADDB4 -i SAPSDIC.cmd -p SAPSDIC.log -nojournal
-datacodepage 1100 -dbcodepage 0120
...

No Journaling During the Database Load

You should keep in mind that the new tables are not journaled during the database load. Therefore, you receive
the following message:

SQL7905 Information 20 10/21/01 17:18:38 QSQCRTT QSYS 1013 QSQCRTT

Message . . . . : Table <table_name> in R3<SAPSID>DATA created but could not be

journaled.

You can ignore this message. Journaling is switched on later.

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

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
130 PUBLIC Installation
● Make sure that the host where you run the installer meets the requirements listed in Prerequisites for
Running the Installer [page 115].

Procedure

1. Start the installer from the command line as described in Running the Installer [page 118] 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.

7.1 Post-Installation Checklist

This section includes the post-installation steps that you have to perform for the following:

● Standard, distributed, or high-availability system

● Additional application server instance

More detailed information about the steps are available in the linked sections.

Standard, Distributed, or High-Availability System

 Note

In a standard system, all mandatory instances are installed on one host. Therefore, if you are installing a
standard system, you can ignore references to other hosts.

1. If required, you perform a full backup [page 162] immediately after the installation has finished.
2. You check whether you can log on to the Application Server ABAP [page 133].
3. You check whether you can log on to the Application Server Java [page 135].
4. You provide access to the SAP NetWeaver Administrator [page 136].
5. You install the SAP license [page 136].
6. If you have installed a high-availability system, you set up the licenses for high availability [page 137].
7. You configure the remote connection to SAP support [page 138].
8. You enable the Note Assistant to apply note corrections [page 139].
9. You configure the documentation provided on the SAP Help Portal [page 139].
10. You perform the consistency check [page 141].
11. You set up a secondary host for iASP Switchover [page 142].
12. You set up the transport directory [page 143].
13. You configure the Transport Management System [page 145].
14. For production systems it is highly recommended that you connect the system to SAP Solution Manager
[page 146].
15. You apply the latest kernel and Support Packages [page 148].
16. You perform post-installation steps for the application server ABAP [page 149].
17. If required, you install additional languages and perform language transport [page 151].
18. SAP Kernel Release 7.4 and Higher: You perform IP Multicast Configuration [page 153].
19. You configure the user management [page 153].
20.You ensure user security [page 154].
21. You run automated configuration [page 156].

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
132 PUBLIC Post-Installation
22. You decide on your production client [page 157].
23. You perform the client copy [page 159].
24. SAP systems based on SAP NetWeaver 7.4 and higher only: If required, you change the keys for the
secure storage [page 160].
25. You remove the installer installation files [page 161].
26. You perform a full backup [page 162].
27. If you chose to install an integrated SAP Web Dispatcher within the ASCS instance, you log on to the SAP
Web Dispatcher Management Console [page 164]
28. If you chose to install an integrated SAP Web Dispatcher within the ASCS instance, you configure the SAP
Web Dispatcher [page 166]
29. If you chose to install an integrated Gateway within the ASCS instance, you configure the SAP Gateway
[page 166].
30.You check the Master Guide for your SAP Business Suite application or SAP NetWeaver application
(section Configuration of Systems and Follow-Up Activities) for additional implementation and
configuration steps, such as language installation, monitoring, work processes, transports, SAP license,
printers, system logs, and connectivity to system landscape directory (SLD).

Additional Application Server Instance

7.2 Logging On to the Application Server ABAP

You need to check that you can log on to the Application Server ABAP with the standard users, given in the
table below.

Prerequisites

● The SAP system is up and running.

● You have installed the SAP front-end software.

In a distributed or high-availability system, you check whether you can log on to every instance of the SAP
system that you installed.

User User Name Client

SAP system user SAP* 000, 001, 066

DDIC 000, 001

You access the application server ABAP using SAP Logon.

Procedure

1. Start SAP Logon on the host where you have installed the SAP front-end software as follows:

○ SAP GUI for Windows:

○ Windows Server 2012 (R2) and higher:
1. Press Windows + Q , and enter SAP Logon in the Search field.
2. Choose SAP Logon.
○ Windows Server 2008 (R2) and higher:
Choose Start All Programs SAP Front End SAP Logon .
○ SAP GUI for Java:
○ Windows Server 2012 (R2) and higher:
1. Press Windows + Q , and enter SAP GUI for Java <Release>
2. Choose SAP GUI for Java <Release>.
○ Windows Server 2008 (R2):
Choose Start All Programs SAP Clients SAP GUI for Java <Release> .
The SAP Logon appears.

 Note

You can alternatively enter the command guilogon in the SAP GUI installation directory to start
SAP GUI for Java.

2. Create a logon entry for the newly installed system in the SAP Logon.
For more information about creating new logon entries, press F1 .
3. When you have created the entry, log on as user SAP* or DDIC.

You need to check that you can log on to the Application Server Java with the appropriate administrator user,
given in the table below.

Prerequisites

● The SAP system is up and running.

Context

 Note

In a distributed or high-availability system, you check whether you can log on to every instance of the SAP
system that you installed.

Java User in a Dual-Stack System

User User Name Storage: ABAP System

Administrator J2EE_ADMIN (default) or the name you gave this user during the installation proc
ess.

You access AS Java with a URL using a web browser from your client machines. To log on to the application
server Java, proceed as follows:

Procedure

1. Start a web browser and enter the following URL:

http://<Hostname_of_AS_Java_Server>:5<Instance_Number>00

 Note

You must always enter a two-digit number for <Instance_Number>. For example, do not enter 1 but
instead enter 01.

 Example

If you installed SAP NetWeaver Application Server for Java on host saphost06 and the instance
number of your SAP NetWeaver Application Server for Java is 04, enter the following URL:

http://saphost06:50400

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
Post-Installation PUBLIC 135
The start page of the SAP NetWeaver Application Server for Java appears in the web browser.
2. Log on by pressing the link of any of the provided applications, for example SAP NetWeaver Administrator
or System Information.

7.4 Providing Access to the SAP NetWeaver Administrator

To be able to log on the SAP NetWeaver Administrator, you must allow access to administration URLs of the
NetWeaver Administrator in the Internet Communication Manager (ICM).

Context

Due to security restrictions, the SAP NetWeaver Administrator can only be accessed locally via http://
<Hostname_of_AS_Java_Server>:5<Instance_Number>00/nwa after the installation has finished.

Procedure

Allow access to administration requests for the required network segments as described in SAP Note 1451753
.

7.5 Installing the SAP License

You must install a permanent SAP license. When you install your SAP system, a temporary license is
automatically installed.

Context

 Caution

Before the temporary license expires, you must apply for a permanent license key from SAP.

We recommend that you apply for a permanent license key as soon as possible after installing your system.

For more information about SAP license keys and how to obtain them, see http://support.sap.com/licensekey
.

Install the SAP license as described in the SAP Library at:

SAP Release and SAP Library Quick Link SAP Library Path (Continued)

○ SAP NetWeaver Process Integration 7.1

http://help.sap.com/nwpi711 License Configuration

○ SAP NetWeaver 7.3

Application Help Function-Oriented View: English Solution
http://help.sap.com/nw73
Life Cycle Management SAP Licenses
○ SAP NetWeaver 7.3 including Enhancement Pack
age 1
http://help.sap.com/nw731
○ SAP NetWeaver 7.4
http://help.sap.com/nw74

7.6 High Availability: Setting Up Licenses

You need to install a permanent license, which is determined by the hardware environment of the message
server.

Prerequisites

The SAP system is up and running.

Context

SAP has implemented a license mechanism for switchover solutions and clustered environments. Your
customer key is calculated on the basis of local information on the message server host. This is the host
machine where the ABAP central services instance (ASCS instance) runs.

To be able to perform a switchover, the temporary license that is installed automatically with the ASCS
instance is not sufficient. You first need to install a permanent license, which is determined by the hardware
environment of the message server. Since SAP's high-availability (HA) solution stipulates two or more cluster
nodes (host machines) where the message server is enabled to run, you have to order as many license keys
[page 136] as you have cluster nodes.

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
Post-Installation PUBLIC 137
When we receive confirmation from your vendor that you are implementing a switchover environment, we
provide the required license keys for your system, one key for each machine.

Procedure

1. To find the hardware ID of the primary host, log on to any application server instance of the SAP system
and call transaction SLICENSE.
2. Perform a switchover of the ABAP central services instance (ASCS) to another node in the cluster and
repeat the previous step.

Repeat this for all remaining nodes in the cluster.

3. To obtain the two license keys, enter the hardware IDs for each cluster node, where message server is
enabled to run: http://support.sap.com/licensekey
4. To import the files containing the two licenses, log on to any application server instance of the SAP system
and call transaction SLICENSE.
5. Perform a switchover of the ABAP central services instance (ASCS) to another node in the cluster and
repeat the previous step.
Repeat this for all remaining nodes in the cluster.

Results

The license is no longer a problem during switchover. This means you do not need to call saplicense in your
switchover scripts.

7.7 Configuring the Remote Connection to SAP Support

SAP offers its customers access to support and a number of remote services such as the Early Watch
Service or the GoingLive Service. Therefore, you have to set up a remote network connection to SAP.

For more information, see SAP Support Portal at https://support.sap.com/remote-support.html .

Use the Note Assistant to implement note corrections in your ABAP system.

Context

The Note Assistant allows you to automatically implement note corrections in your ABAP system. For more
information about the Note Assistant, see https://support.sap.com/noteassistant and https://
help.sap.com/netweaver SAP NetWeaver Platform <Release> Application Help SAP NetWeaver
Library: Function-Oriented View Solution Life Cycle Management Software Logistics Note Assistant .

Procedure

1. Follow the instructions in SAP Note 2836302 for enabling the Note Assistant for TCI and Digitally Signed
SAP Notes.
2. Apply important SAP Notes for SAP_BASIS as described in SAP Note 1668882 .

7.9 Configuring Documentation Provided on the SAP Help

Portal

In transaction SR13, you can configure the settings of your backend system to point to documentation that is
provided on the SAP Help Portal.

Context

You can configure your backend system to access documentation that is provided on the SAP Help Portal.

Prerequisites

● The documentation you want to access must be available on the SAP Help Portal.
● The users who access the documentation must have access to the Internet.
● You can configure an ABAP system to connect to only one combination of product and version.

If you cannot fulfill one or more of these prerequisites, you must install the documentation in your local system
landscape using the download packages or media provided.

For more information about installing the documentation in your local system landscape, see the
Installation of SAP Library guide.

Procedure

1. Open transaction SR13.

2. Select the tab PlainHtmlHttp.
3. Choose New Entries.

 Caution

You have to create entries for both documentation and XML documentation areas for each platform
you are using and each language in which you want to provide documentation.

You must use the exact combination of uppercase and lowercase characters specified in the product
and version.

To find the correct entry for the Path field, see the list of products and versions attached to SAP Note
2652009 .
4. To create entries for the documentation area, enter the following values:

Name Value to be entered

Variant Enter a name for the variant.

Platform Select the platform relevant for your implementation from

the list of available platforms, for example, WN32.

Area Select Documentation from the list; this will display as

IWBHELP in the table.

Server Names https://help.sap.com/http.svc/ahp2

Path <product/version>

To find the correct entry for the Path field, see the list of
products and versions attached to SAP Note 2652009 .

Language Select the language you need from the list.

5. To create entries for the XML documentation area, enter the following values:

Name Value to be entered

Variant Enter a name for the variant (any name).

Platform Select the platform relevant for your implementation from

the list of available platforms, for example, WN32.

Area Select XML Documentation from the list; this will display
as XML_DOCU in the table.

Server Names https://help.sap.com/http.svc/ahp2

Path <product/version>

To find the correct entry for the Path field, see the list of
products and versions attached to SAP Note 2652009 .

Language Select the language you need from the list.

6. Repeat steps 4 and 5 for each relevant platform and language.

7. Select one entry as the default language for each platform and area.
8. Save your entries.

Results

You have configured the settings to point to documentation that is provided on the SAP Help Portal.

Related Information

Installation of SAP Library

SAP Note 2149786
SAP Note 2652009

7.10 Performing the Consistency Check

We recommend that you check the consistency of the newly installed SAP ABAP system.

Prerequisites

● If the installation finished successfully, your SAP system should be up and running. Otherwise, start it as
described in Starting and Stopping SAP System Instances [page 177].
● You have logged on to the SAP system [page 133].

Context

When logging on to the system for the first time, you need to trigger a consistency check manually. The
function is then called automatically whenever you start the system or an application server.

● Completeness of installation
● Version compatibility between the SAP release and the operating system
The initial consistency check determines whether:
○ The release number in the SAP kernel matches the release number defined in the database system
○ The character set specified in the SAP kernel matches the character set specified in the database
system
○ Critical structure definitions that are defined in both the data dictionary and the SAP kernel are
identical. The structures checked by this function include SYST, T100, TSTC, TDCT and TFDIR.
● Accessibility of the message server
● Availability of all work process types
● Information about the standalone enqueue server and the update service

Procedure

1. Perform a system check:

Call transaction SICK.

You should see the entry SAP System Check | no errors reported
2. Perform a database check:

In the DBA Cockpit (transaction DBACOCKPIT), check for missing tables or indexes by choosing
Diagnostics Missing Tables and Indexes .

7.11 Setting Up a Secondary Host for IASP Switchover

Use

When creating a standard system using the IASP installation, your new system can be part of a switchable
environment if your IASP is configured correctly. Providing that the installation was done using switchable IASP
and a virtual hostname and complemented with the cluster services available, you can set up the secondary
host to take over the SAP system already installed in a primary host. The secondary host acts as a passive host
that can run the SAP system after an IASP failover or switchover. For more information, see SAP Note 568820
.

Procedure

1. Sign on to the systems with a user profile with *ALLOBJ authority, preferably QSECOFR.

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
142 PUBLIC Post-Installation
2. Copy the installed primary host kernel library SAP<SAPSID>IND to the secondary host and then add the
library to the library list using the command ADDLIBLE. The kernel libraries always reside in the system
ASP.
3. Depending on the user concept of the installed system, set the environment variable
CLASSICUSERCONCEPT accordingly. For more information, see SAP Note 1045022 .
4. Make sure that the UIDs and GIDs match for all user profiles for the SAP system on the primary and
secondary hosts. You can use the IBM Systems Director Navigator for i and your clustering software.

 Caution

You must make sure the users are set up before continuing.

5. Create a new SAP system with the same SID as the original system using the following command:
CRTR3SYS SID(<SAPSID>) INLPGMLIB(SAP<SAPSID>IND)
6. Create new SAP instances with the same instance numbers as the original system using the following:
○ CRTR3INST SID(<SAPSID>) INST(<Instance_Number>) ROLE(*CENTRAL)
○ CRTR3INST SID(<SAPSID>) INST(<SCS_Instance_Number>) ROLE(*SCS)
○ CRTSAPUSR USER(*J2EEDB) SID(<SAPSID>)
7. After creating the new SAP system on the secondary host, the SAP user profile passwords on the primary
and secondary hosts may not be identical. If this is the case, change the passwords on the secondary host
to match the passwords on the primary host.
8. If the library exists, delete it using the following command:
DLTLIB LIB(SAPJ2EE<Instance_Number>)
9. Create IFS symbolic links, modify job descriptions, user profiles, and data areas using the following
command:
CFGSAP2HO SID(<SAPSID>) IASPP(<Primary_Independent_ASP>)
VHOST(<Virtual_Host_Name>)
10. Switch the independent ASP to the secondary host.
11. Start the SAP system on the secondary host.

7.12 Setting Up the Transport Directory

You need to set up the transport directory for your SAP system.

If you have several SAP systems, it depends on your security requirements whether you want them to share a
transport directory or whether you use separate directories. For more information, see the SAP Library at:

SAP Release and SAP Library Quick Link SAP Library Path (Continued)

● SAP NetWeaver Process Integration 7.1

Application Help SAP Library: English SAP NetWeaver
http://help.sap.com/nwpi71
Process Integration Library Function-Oriented View ABAP
● SAP NetWeaver Process Integration 7.1 Including
Technology / Application Server ABAP Administration Tools for
Enhancement Package 1
http://help.sap.com/nwpi71 AS ABAP Change and Transport System Transport

Management System (BC-CTS-TMS) Configuring TMS

● SAP NetWeaver 7.3

Application Help Function-Oriented View: English Solution
http://help.sap.com/nw73
Life Cycle Management Software Logistics Change and
● SAP NetWeaver 7.3 including Enhancement Pack
Transport System Change and Transport System – Overview
age 1
http://help.sap.com/nw731 Basics of the Change and Transport System Transport

● SAP NetWeaver 7.4 Management System – Concept

http://help.sap.com/nw74

Using a shared system transport directory /usr/sap/trans makes it easier to maintain your SAP system and
instance configuration data. We recommend that you link /usr/sap/trans to the IFS directory /sapmnt/
trans on the primary application server instance host of an SAP system.

If the primary application server instance is on a different host, the directory should be linked using QFileSvr.
400.

You must make sure the /QFileSvr.400/<SAPTRANSHOST> directory is always available after an initial
program load (IPL).

By default, the installation creates the directory /usr/sap/trans if it does not exist. Otherwise, installer
reuses /usr/sap/trans. When the transport directory is newly created by the installer it is a normal
directory. You should move this directory to /sapmnt after you successfully finished the installation and you
should create a link /usr/sap/trans pointing to /sapmnt/trans.

Procedure

To move the newly created directory /usr/sap/trans to /sapmnt and to create a link /usr/sap/trans to /
sapmnt/trans, proceed as follows:

1. Log on to the IBM i host as a user with administration rights similar to QSECOFR.
2. To move the directory trans enter the following command:
MOV OBJ('/usr/sap/trans') TOOBJ('/sapmnt')
3. To create a link pointing to /sapmnt/trans enter the following command:
ADDLNK OBJ('/sapmnt/trans') NEWLNK('/usr/sap/trans')

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
144 PUBLIC Post-Installation
If you want the directory /usr/sap/trans to point to any other host, you have to change it manually using the
following command: CHGR3SHLOC

To change the /usr/sap/trans to /sapmnt/trans of any other host, proceed as follows:

1. Log on to the IBM i host as a user with administrator rights similar to QSECOFR.
2. To link to another host enter the following command:
CHGR3SHLOC NEWHOST(<SAPTRANSHOST>)
3. Since the command CHGR3SHLOC creates a link using QFileSvr.400 to point to the SAPTRANSHOST, you
must make sure the /QFileSvr.400/<SAPTRANSHOST> directory is always available after an initial
program load (IPL).
For more information, see Adjusting Startup Program QSTRUP [page 81].
4. To create the missing users on the remote host, see SAP Note 1123501 .

7.13 Configuring the Change and Transport System

You have to perform some steps in the Transport Management System to be able to use the Change and
Transport System (TMS).

Context

Procedure

1. Call transaction STMS in the ABAP system to configure the domain controller in the Transport Management
System (TMS).

For more information, see the SAP Library at:

SAP Release and SAP Library Quick Link SAP Library Path (Continued)

○ SAP NetWeaver Process Integration 7.1

Application Help Function-Oriented View: English
http://help.sap.com/nwpi71
ABAP Technology / Application Server ABAP
○ SAP NetWeaver Process Integration 7.1 Including En
hancement Package 1 Administration Tools for AS ABAP Change and Transport

http://help.sap.com/nwpi71 System Transport Management System (BC-CTS-TMS)

Configuring TMS

○ SAP NetWeaver 7.3

Application Help Function-Oriented View: English
http://help.sap.com/nw73
Solution Life Cycle Management Software Logistics
○ SAP NetWeaver 7.3 including Enhancement Package 1
http://help.sap.com/nw731 Change and Transport System Change and Transport

○ SAP NetWeaver 7.4 System – Overview Basics of the Change and Transport
http://help.sap.com/nw74 System Transport Management System – Concept

2. In addition, you must configure the system change options.

For more information, see the SAP Library at:

SAP Release and SAP Library Quick Link SAP Library Path (Continued)

○ SAP NetWeaver Process Integration 7.1

Application Help Function-Oriented View: English
http://help.sap.com/nwpi71
ABAP Technology / Application Server ABAP
○ SAP NetWeaver Process Integration 7.1 Including En
hancement Package 1 Administration Tools for AS ABAP Change and Transport

http://help.sap.com/nwpi71 System Transport Organizer (BC-CTS-ORG)

Requirements for Working with the Transport Organizer

Setting the System Change Option

○ SAP NetWeaver 7.3

Application Help Function-Oriented View: English
http://help.sap.com/nw73
Solution Life Cycle Management Software Logistics
○ SAP NetWeaver 7.3 including Enhancement Package 1
http://help.sap.com/nw731 Change and Transport System Transport Organizer (BC-

○ SAP NetWeaver 7.4 CTS-ORG) Requirements for Working with the Transport
http://help.sap.com/nw74 Organizer Setting the System Change Option

3. Call transaction SE38 to schedule a dispatcher job for transport programs by executing report RDDIMPDP.
You schedule the transport dispatcher in the current client. This is equivalent to the execution of job
RDDNEWPP in transaction SE38

7.14 Connecting the System to SAP Solution Manager

Here you find information about how to connect your newly installed SAP system to SAP Solution Manager.

Prerequisites

An SAP Solution Manager system must be available in your system landscape. For more information, see
http://help.sap.com/solutionmanager .

SAP Solution Manager gives you central access to tools, methods, and preconfigured content that you can use
to evaluate and implement your solutions.

When your implementation is running, you can use SAP Solution Manager to manage, monitor, and update
systems and business processes in your solution landscape, and also to set up and operate your own solution
support.

Procedure

You connect a technical system to SAP Solution Manager by the following steps:
1. On the technical systems of your landscape, data suppliers are implemented, for example, with
transaction RZ70 for Application Server ABAP and with Visual Administrator for Application Server Java.

For more information, see the SAP Solution Manager Application Help:

○ If your SAP Solution Manager release is 7.1:

http://help.sap.com/solutionmanager Version 7.1 SPS <No> Application Help (English) SAP
Solution Manager Operations Managing System Landscape Information Managing Technical
System Information Register Technical Systems Automatically by Data Suppliers
○ If your SAP Solution Manager release is 7.2:
http://help.sap.com/solutionmanager Version 7.2 SPS <No> Application Help (English)
Technical Infrastructures Landscape Management Database (LMDB) Managing Technical System
Information Registering Technical Systems Automatically by Data Suppliers
2. The data suppliers send information about the hardware and installed software to a central System
Landscape Directory (SLD). Updates are sent to the SLD as well.
For more information, see the Planning Guide - System Landscape Directory in the SAP Community
Network at System Landscape Directory (SLD) - Overview
3. From the SLD, this information is regularly synchronized with SAP Solution Manager where it is managed
in the Landscape Management Database (LMDB).

For more information, see the SAP Solution Manager Application Help:

○ If your SAP Solution Manager release is 7.1:

For more information, see the SAP Solution Manager Application Help:

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
Post-Installation PUBLIC 147
○ If your SAP Solution Manager release is 7.1:
Managing Technical System Information and Managing Product System Information at http://
help.sap.com/solutionmanager Version 7.1 SPS <No> Application Help (English) SAP
Solution Manager Operations Managing System Landscape Information
○ If your SAP Solution Manager release is 7.2:
http://help.sap.com/solutionmanager Version 7.2 SPS <No> Application Help (English)
Technical Infrastructures Landscape Management Database (LMDB) Managing Technical System
Information

Next Steps

For more information, see the following pages in the SAP Community Network:

● System Landscape Directory (SLD) - Overview

● Documentation for Landscape Management Database - LMDB

7.15 Applying the Latest Kernel and Support Package

Stacks

We strongly recommend that you apply the latest kernel and Support Package stacks before you start
configuring your SAP system.

Context

Procedure

● Download and apply the latest Kernel and Support Package stacks using the Software Update Manager
(SUM) as described in the Software Update Manager documentation at: https://support.sap.com/en/
tools/software-logistics-tools/software-update-manager.html
● If you want to update the kernel manually, proceed as described below:
a. Log on as user <SAPSID>ADM to the hosts of the SAP system instances to be updated.
b. Download the latest kernel for your operating system and database platform as described in SAP Note
19466 .

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
148 PUBLIC Post-Installation
c. Apply the SAR files of the kernel Support Packages of the target SP level to a temporary directory using
the command APYSIDKRN. For more information, see SAP Note 1632755 .

7.16 Performing Post-Installation Steps for the ABAP

Application Server

This section describes the post-installation steps you have to perform for the ABAP application server.

Prerequisites

You have logged on to the ABAP application server as described in Logging On to the Application Server [page
133].

Context

You have to perform the following post-installation steps for the ABAP application server:

● Upload and set system profiles using transaction RZ10

● Configure the number of work processes
● Create logon and RFC server groups using transactions SMLG and RZ12
● Create operation modes using transaction RZ04
● Schedule standard jobs using transaction SM36
● Configuration of SLD data supplier using transaction RZ70
● Perform load generation using transaction SGEN

For more information, see the appropriate sections below.

Procedure

● Upload and Set System Profiles using Transaction RZ10

You upload system profiles, such as default profile and instance profile, from the file system into the
database of the target system using transaction RZ10.

SAP Release and SAP Library Quick Link SAP Library Path (Continued)

○ SAP NetWeaver Process Integration 7.1

Application Help Function-Oriented View: English
http://help.sap.com/nwpi71
ABAP Technology Administration Tools for AS ABAP
○ SAP NetWeaver Process Integration 7.1 Including En
hancement Package 1 Configuration in the CCMS Profiles Maintaining

http://help.sap.com/nwpi71 Profiles

○ SAP NetWeaver 7.3

Application Help Function-Oriented View: English
http://help.sap.com/nw73
Application Server Application Server ABAP
○ SAP NetWeaver 7.3 including Enhancement Package 1
http://help.sap.com/nw731 Administration of Application Server ABAP Monitoring

○ SAP NetWeaver 7.4 and Administration Tools for Application Server ABAP
http://help.sap.com/nw74 Configuration in the CCMS Profiles Maintaining

Profiles / Profile Maintenance

● Configure the number of work processes

SAP systems are installed with a minimum number of work processes. This is only an initial configuration
to get you started after the installation. It is not detailed enough for a production system because the
optimal number of each type of work process depends on the system resources and on the number of
users working in each SAP system application. For more information about how many work processes to
configure and how to set the number, see SAP Note 39412 .
● Create Logon and RFC Server Groups using Transactions SMLG and RZ12

You create the following:

○ Logon groups using transaction SMLG

○ RFC server groups using transaction RZ12

Specify the following:

○ Name of the logon or RFC server group

○ Instance name (application server)
○ Group type attributes are optional

If required, you create the RFC server group parallel_generators.

● Create Operation Modes using Transaction RZ04

You check for existing operation modes and - if required - create a new operation mode using transaction
RZ04.

Specify the following:

○ Name of the operation mode

○ Short description
○ Optional: monitoring properties variant

Select the corresponding checkbox to assign the operation mode to the following:

○ Time table (assignment only from 0-24 h)

○ Current application server instance

You schedule SAP standard jobs using transaction SM36.

If a standard job is already scheduled, it is kept. Only missing jobs are scheduled.
● Configure the SLD Data Supplier using Transaction RZ70
a. Make sure that the SLD and the SLD bridge (the receiving thread of the SLD, which runs on a Java EE
engine) are running.
b. Configure the System Landscape Directory (SLD) data supplier with default settings, using transaction
RZ70.

SLD configuration is a prerequisite for the connection of an SAP system to SAP Solution Manager.

For more information, see Connecting the System to SAP Solution Manager [page 146]
● Perform Load Generation using Transaction SGEN

You generate the ABAP loads using transaction SGEN. ABAP loads are platform-dependent programs that
are generated during runtime and stored in database tables. Using transaction SGEN you can generate
ABAP loads of a number of programs, function groups, classes, and so on.

Choose one of the following generation modes:

○ Generate All Objects

All existing objects of all software components are generated synchronously. Job RSPARGENER8M
starts the generation directly after all ABAP objects have been prepared for generation and have been
stored in table GENSETC. Be aware that this is a time-consuming process.

 Note

Make sure that you have sufficient space available on your database. The generation of all existing
objects requires around 2 - 9 GB of free space.

○ Prepare All Objects for Generation

All objects to be generated are prepared for generation and stored in table GENSETM. You can start the
generation of these objects later with transaction SGEN. Choose this strategy if object generation is to
be done outside the configuration task due to performance issues.

7.17 Installing Additional Languages and Performing

Language Transport

This section describes how to install and transport additional languages.

Context

If you have problems during the language installation, see SAP Note 2456868 .

1. Configure the language settings by using transaction I18N and choosing I18N Customizing I18N
System Configuration or by executing report RSCPINST directly.

For more information, see SAP Note 42305

2. Perform the language transport using transaction SMLT:

 Note

German is already available in the system. Do not transport it via SMLT.

a. Classify the language.

b. Schedule the language transport.
c. Schedule the language supplementation.

Next Steps

 Note

You can also install additional languages later, but if you install any Support Packages in the meantime, you
have to do one of the following:

● Install the Support Packages again.

● Use the report RSTLAN_IMPORT_OCS to extract the language-relevant information from each Support
Package.

For information about the language transport, see the SAP Library at:

SAP Release and SAP Library Quick Link SAP Library Path (Continued)

● SAP NetWeaver Process Integration 7.1

Application Help Function-Oriented View: English
http://help.sap.com/nwpi71
ABAP Technology Administration Tools for AS ABAP
● SAP NetWeaver Process Integration 7.1 Including En
Change and Transport System Change and Transport
hancement Package 1
http://help.sap.com/nwpi71 System Language Transport (BC-CTS-LAN)

● SAP NetWeaver 7.3

Application Help Function-Oriented View: English
http://help.sap.com/nw73
Solution Life Cycle Management Software Logistics
● SAP NetWeaver 7.3 including Enhancement Package 1
Change and Transport System Language Transport (BC-
http://help.sap.com/nw731
● SAP NetWeaver 7.4 CTS-LAN)

http://help.sap.com/nw74

Since SAP kernel release 7.40, the ABAP application server (AS ABAP) uses IP multicast datagrams with host
local scope to wake up the internal processes (such as dispatcher, Gateway, internet communication manager,
work processes) when dispatching requests.

Since SAP kernel release 7.40 Patch Level (PL) 46 and 7.41 PL 13, the dispatcher checks during startup
whether local IP multicast communication is working properly. You have to adjust the network configuration of
AS ABAP as described in SAP Note1931675 .

Since SAP kernel 7.41 PL 47 and 7.42 PL 14, a new event-based wake-up mechanism is available that replaces
the multicast mechanism. SAP recommends using this new mechanism in case of problems with multicast. For
details on activating the new mechanism see SAP Note 2050408 to ensure that local IP multicast
communication works properly.

7.19 Configuring the User Management

After the installation has completed, configure the user management of your SAP system.

Procedure

During the installation, the UME of your SAP system was configured to use AS ABAP as data source. For more
information, see SAP System Parameters [page 47].

For more information about changing the data source after installation and about related restrictions, see the
SAP Library at:

SAP Release and SAP Library Quick Link SAP Library Path (Continued)

○ SAP NetWeaver Process Integration 7.1

Application Help Function-Oriented View: English Security
https://help.sap.com/nwpi71
Identity Management Identity Management of the Application Server
○ SAP NetWeaver Process Integration 7.1 In
cluding Enhancement Package 1 Java Configuring Identity Management UME Data Sources
https://help.sap.com/nwpi711

○ SAP NetWeaver 7.3

Application Help SAP NetWeaver Library: Function-Oriented View
https://help.sap.com/nw73
Security Identity Management User Management of SAP
○ SAP NetWeaver 7.3 including Enhancement
Package 1 NetWeaver AS for Java Configuring User Management UME Data

https://help.sap.com/nw731 Sources
○ SAP NetWeaver 7.4
https://help.sap.com/nw74

7.20 Ensuring User Security

You need to ensure the security of the users that the installer created during the installation.

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

● Operating system users

● SAP system users

During the installation, the installer by default assigned the master password to all users created during the
installation unless you specified other passwords.

 Recommendation

In all cases, the 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.

 Caution

Make sure that you perform this procedure before the newly installed SAP system goes into production.

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

You can find the security guide in the Security section of the product page for your SAP product at https://
help.sap.com/

To change passwords at the operating system level, use the command CHGPWD or CHGUSRPRF.

After the installation, operating system users for SAP system, database, 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 installer had completed. For more information, see Operating System Users in SAP
System Parameters [page 47].

Changing Passwords of Created IBM i Users

User Profile Initial Password

<SAPSID>ADM –

 Caution

In three-tier systems, these users must have the same password on all IBM i systems.

SAP Host Agent User

User Type User Comment

Operating system user sapadm SAP Host Agent administrator is the user for central
monitoring services.

You do not need to change the password of this user

after the installation.

This user is for administration purposes only.

On IBM i, you are not able to log on as sapadm as this

user profile does not allow it.

SAP System Users

After the installation, ABAP and Java system users are available. The following table shows these users with the
SAP system clients in which they are available, together with recommendations on how you can ensure the
security of these users.

User User Name Comment

SAP system user SAP* User exists in at least SAP system clients 000, 001,
and 066.

DDIC User exists in at least SAP system clients 000 and

001.

EARLYWATCH User exists in at least SAP system client 066.

Application Server Java Admin The name that you gave this user This user exists in at least clients 000 and 001 of the
istrator during the installation or the de ABAP system and in the User Management Engine
fault name J2EE_ADMIN (see (UME) of the Java system. It has administrative per
SAP System Parameters [page missions for user management.
47])
The password of this user is stored in secure storage.
Therefore, whenever you change the password of the
administrator password, you must also change the
password in secure storage.

 Recommendation
We recommend that you use strong password
and auditing policies for this user.

Application Server Java Guest The name that you gave this user This user exists in at least clients 000 and 001 of the
during the installation or the de ABAP system and in the User Management Engine
fault name J2EE_GUEST (see (UME) of the Java system. It is used for anonymous
SAP System Parameters [page access.
47])

Communication user for Appli The name that you gave this user This user exists in at least clients 000 and 001 of the
cation Server Java during the installation or the de ABAP system and in the User Management Engine
fault name SAPJSF (see SAP Sys (UME) of the Java system. It is used for a remote
tem Parameters [page 47]) function call (RFC) between the ABAP system and
the Java system.

7.21 Performing Automated Configuration

This section provides references to documentation about how to run automated configuration tasks for the
initial configuration of SAP NetWeaver functional units.

 Caution

Do not use the functional unit configuration tool to configure functional units that have already been
enabled after:

● Upgrade

If you need to change the configuration of functional units that have already been enabled, then you must
execute the configuration steps manually.

If you want to use a functional unit that has not previously been enabled, you can either use the functional
unit configuration tool or execute the steps manually.

To initially configure an SAP NetWeaver functional unit, proceed as described in the SAP Library for the SAP
NetWeaver release your application is based on:

SAP Release and SAP Library Quick Link SAP Library Path (Continued)

● SAP NetWeaver Process Integration 7.1 Configuration Guide Configuration of SAP NetWeaver
https://help.sap.com/nwpi71 Configuration Wizard
● SAP NetWeaver Process Integration 7.1 In
cluding Enhancement Package 1
http://help.sap.com/nwpi711

● SAP NetWeaver 7.3

Application Help SAP NetWeaver Library: Function-Oriented View
https://help.sap.com/nw73
Solution Life Cycle Management SAP NetWeaver Configuration
● SAP NetWeaver 7.3 including Enhancement
Configuration Wizard
Package 1
https://help.sap.com/nw731
● SAP NetWeaver 7.4
https://help.sap.com/nw74

7.22 Production Client Considerations

A client is a self-contained unit in an SAP system with separate master records and its own set of tables. During
the installation, AS Java was configured against client 001 by default. However, in many cases your production
client must be a copy of SAP reference client 000. This section describes how you can use a client other than
the default client 001 as your production client.

Context

 Note

You do not have to perform these steps if you already completed them as configuration tasks in an
implementation project with SAP Solution Manager Content (ST-ICO).

● You install an SAP system based on AS ABAP and AS Java (dual-stack system) and then reconnect AS Java
to the ABAP server.
● You install an SAP system based on AS ABAP and AS Java (dual-stack system) and then do not reconnect
AS Java.

 Caution

If you want to change the default production client for SAP Process Integration (PI), see SAP Note 1115280
.

Procedure

1. You install the ABAP+Java system as described in this documentation.

2. You perform the client copy [page 159] using SAP reference client 000 as source client.
3. If you need the Java users in your ABAP production client, you have to manually configure the connection
of the Java part to the ABAP part.

To do this, reconnect the Java part to the production client as described in the SAP Library at:

SAP Release and SAP Library Quick Link SAP Library Path (Continued)

○ SAP NetWeaver 7.3

Application Help Function-Oriented View: English
http://help.sap.com/nw73
Security Identity Management User Management of
○ SAP NetWeaver 7.3 including Enhancement Package 1
http://help.sap.com/nw731 the Application Server Java Configuring User

○ SAP NetWeaver 7.4 Management UME Data Sources User Management of

ABAP Client for the UME After a Client Copy

Related Information

Ensuring User Security [page 154]

To get a production client, you have to perform a copy of the SAP reference client.

Context

The installer creates three ABAP clients during the installation, client 000, client 001, and client 066.

During the installation, AS Java was configured against client 001 by default. If you want to use client 001 as the
production client, you do not have to perform the client copy.

However, in many cases your production client must be a copy of the SAP reference client 000. For more
information and for exceptions, see Production Client Considerations [page 157].

 Caution

If you want to change the default production client for an SAP system with Process Integration (PI), see
SAP Note 1115280 .

Procedure

1. Maintain the new client with transaction SCC4.

2. Activate kernel user SAP*:
a. Set the profile parameter login/no_automatic_user_sapstar to 0.
b. Restart the application server.
3. Log on to the new client with kernel user SAP* and password PASS.
4. Copy the client with transaction SCCL and profile SAP_CUST.
5. Check the log files with transaction SCC3.
6. Create the required users. These users must have at least the authorizations required for user
administration and system administration. Create a user SAP* with all required authorizations for this user.
If you want to have other users for system administration, you can also create user SAP* without
authorizations.
7. Deactivate kernel user SAP*:
a. Reset login/no_automatic_user_sapstar to 1.
b. Restart the application server.

For more information about the client copy and about how to perform it, see the SAP Library at :

SAP Release and SAP Library Quick Link SAP Library Path (Continued)

● SAP NetWeaver Process Integration 7.1

Application Help Function-Oriented View: English
http://help.sap.com/nwpi71
ABAP Technology / Application Server ABAP
● SAP NetWeaver Process Integration 7.1 Including En
Administration Tools for AS ABAP Change and Transport
hancement Package 1
http://help.sap.com/nwpi711 System BC – Client Copy and Transport

● SAP NetWeaver 7.3

Application Help Function-Oriented View: English
http://help.sap.com/nw73
Application Server Application Server ABAP
● SAP NetWeaver 7.3 including Enhancement Package 1
Administration of Application Server ABAP Change and
http://help.sap.com/nw731
● SAP NetWeaver 7.4 Transport System BC – Client Copy and Transport

http://help.sap.com/nw74

7.24 SAP Systems Based on SAP NetWeaver 7.4 and Higher:

Changing Keys for the Secure Storage

The secure storage in the file system and the secure storage in the database have been encrypted with a
randomly generated individual encryption key or with a default key.

In the first case, you have made a backup of the individual key because you need this value in case of failure to
recover the data.

No matter what you chose during installation, you can change the encryption key at any time using the
respective maintenance tool.

 Recommendation

SAP recommends using an individual encryption key.

● For the secure storage in the file system, the key change is described in the SAP Library at:

SAP Release and SAP Library Quick Link SAP Library Path (Continued)

○ SAP NetWeaver 7.4

Application Help Function-Oriented View: English Security
http://help.sap.com/nw74
System Security System Security for SAP NetWeaver AS ABAP

Only Secure Storage in the File System (AS ABAP)

SAP Release and SAP Library Quick Link SAP Library Path (Continued)

○ SAP NetWeaver 7.4

Only Secure Storage (ABAP) Key Management Using

Individual Encryption Keys Generating Encryption Keys

More Information

See also the entry Individual Encryption Key for the Secure Storage in table SAP System Parameters in SAP
System Parameters [page 47].

7.25 Removing the Installer Installation Files

You use this procedure to gain disk space after the installation by deleting the installer.

On the IBM i host, you should remove the installation directory, the temporary installer files, and the copied
installation media.

 Caution

You might want to disconnect from the share TMPSAP and remove it from the IBM i. However, if you want to
start tools like the SAP NetWeaver AS for Java EE ConfigTool from the share TMPSAP on your Windows PC,
then you should keep the share.

 Caution

Do not use this procedure until all instances of the SAP system on the IBM i host have been installed.

Prerequisites

● You have completed the SAP system installation.

● The SAP system is up and running.

 Caution

Only delete the log files if you are sure that you do not need them again. Do not delete log files other than
those in the paths given here.

On IBM i:

1. If you want to remove the installer installation directory, enter the following command:
RMVDIR DIR('<Installation_Directory>') SUBTREE(*ALL)
2. Parallel to the installer in the installation directory a library SAP<SAPSID> is created containing the ILE
load tools for the database. When the installer installation directory is deleted, you can also remove this
library using the following command:
DLTLIB LIB(SAP<SAPSID>LOAD)
3. To remove temporary SAPINST files, enter the following command:
RMVDIR DIR('/tmp/sapinst_exe*') SUBTREE(*ALL)

 Note

If you have chosen one of the three variables: TEMP, TMP, or TMPDIR for your temporary directory in
section Useful Information about the Installer [page 122], you must use this temporary directory
instead of '/tmp'.

4. To remove the downloaded and/or copied installation media, enter the following command:
RMVDIR DIR('/tmp/sap/<SAPSID>') SUBTREE(*ALL)

To disconnect your mapped drive from the IBM i, enter the following command on your Windows PC:

net use <Mapped_Drive>: /DELETE

7.26 Performing a Full Backup

Use

You can use this procedure to make a full backup of your SAP system.

 Note

During the backup, your SAP system is unavailable to other users.

Procedure

1. On the IBM i command line, enter GO SAVE.

For more information, see the IBM documentation IBM i Backing Up Your System in the IBM Knowledge Center.

More Information

Restoring a Backup [page 187]

This section describes how to log on to the SAP Web Dispatcher.

Context

 Note

This step is only required if you chose to install an integrated SAP Web Dispatcher instance within the ASCS
instance.

You must log on to the SAP Web Dispatcher Management Console to do the following:

● Check whether the SAP Web Dispatcher was installed successfully,

● Change the password of the webadm user,
● Access monitoring and administration tools.

Procedure

1. Open a web browser.

2. Enter the following URL, depending on whether you use HTTP or HTTPS:

http(s)://<Webdispatcher_Host>:<HTTP(S)_PORT>/sap/wdisp/admin/public/
default.html

 Example

https://plx282:44300/sap/wdisp/admin/public/default.html

3. Log on as user webadm with the password that you entered during the input phase of the installation.

The SAP Web Dispatcher Monitor screen appears.

4. We recommend that you change the password of webadm immediately after the installation for security
reasons.

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
164 PUBLIC Post-Installation
For more information on how to change passwords of existing users using the Admin Handler, see the
SAP Library at:

SAP Release and SAP Library Quicklink SAP Library Path (Continued)

○ SAP NetWeaver Mobile 7.1

http://help.sap.com/nwmobile711 Interface Area menu Section ”HTTP Handler”

○ SAP NetWeaver 7.1 for Banking Services from SAP See the SAP NetWeaver Mobile Library.
5.0 and 6.0
○ SAP NetWeaver 7.1 including Enhancement Pack  Note
age 1 for Banking Services from SAP 5.0 and 6.0 Since the SAP NetWeaver Mobile 7.1 Library is the only
available SAP Library for ABAP systems based on SAP
NetWeaver 7.1, in this guide we always refer to it also for
SAP NetWeaver 7.1 for Banking Services from SAP 5.0
and 6.0.

○ SAP NetWeaver Process Integration 7.1

http://help.sap.com/nwpi711 Interface Area menu Section ”HTTP Handler”

○ SAP NetWeaver 7.3

http://help.sap.com/nw731 Administration of the SAP Web Dispatcher Area menu

Section ”HTTP Handler”

○ SAP NetWeaver 7.4

SAP NetWeaver Application Server SAP Web Dispatcher

Administration of the SAP Web Dispatcher Using the Web

Administration Interface Area menu Section ”HTTP

Handler”

Related Information

ASCS Instance with Integrated SAP Web Dispatcher [page 29]

After installing SAP Web Dispatcher, you must configure it to be able to use it.

 Note

This step is only required if you chose to install an integrated SAP Web Dispatcher instance within the ASCS
instance.

You can find the configuration information in the SAP Library at:

SAP Release and SAP Library Quicklink SAP Library Path (Continued)

● SAP NetWeaver Process Integration 7.1

● SAP NetWeaver 7.3

Application Help Function-Oriented View Application
http://help.sap.com/nw73
Server Application Server Infrastructure Components of
● SAP NetWeaver 7.3 including Enhancement Package
SAP NetWeaver Application Server SAP Web Dispatcher
1
http://help.sap.com/nw731
● SAP NetWeaver 7.4
http://help.sap.com/nw74

Related Information

ASCS Instance with Integrated SAP Web Dispatcher [page 29]

7.29 Gateway Configuration (Optional)

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

 Note

This step is only relevant if you installed a gateway integrated in the ASCS instance. For more information,
see ASCS Instance with Integrated Gateway [page 30].

SAP Release and SAP Library Quicklink SAP Library Path (Continued)

● SAP NetWeaver Mobile 7.1

● SAP NetWeaver Process Integration 7.1 Application Help Function-Oriented View Application
http://help.sap.com/nwpi71 Server Infrastructure Connectivity SAP Gateway
● SAP NetWeaver Process Integration 7.1 Including En
hancement Package 1
http://help.sap.com/nwpi711

● SAP NetWeaver 7.3 Application Help SAP NetWeaver Library: Function-

http://help.sap.com/nw73 Oriented View Application Server Application Server
● SAP NetWeaver 7.3 including Enhancement Package Infrastructure Connectivity Gateway
1
http://help.sap.com/nw731

● SAP NetWeaver 7.4 Application Help SAP NetWeaver Library: Function-

Related Information

ASCS Instance with Integrated Gateway [page 30]

The following sections provide additional information about optional preparation, installation, and post-
installation tasks.

There is also a section describing how to delete an SAP system.

8.1 Integration of LDAP Directory Services

This section explains the benefits of using the SAP system with the Lightweight Directory Access Protocol
(LDAP) directory and gives an overview of the configuration steps required to use an SAP system with the
directory.

LDAP defines a standard protocol for accessing directory services, which is supported by various directory
products such as Microsoft Active Directory, and OpenLDAP slapd. Using directory services enables
important information in a corporate network to be stored centrally on a server. The advantage of storing
information centrally for the entire network is that you only have to maintain data once, which avoids
redundancy and inconsistency.

If an LDAP directory is available in your corporate network, you can configure the SAP system to use this
feature. For example, a correctly configured SAP system can read information from the directory and also store
information there.

 Note

The SAP system can interact with the Active Directory using the LDAP protocol, which defines:

● The communication protocol between the SAP system and the directory
● How data in the directory is structured, accessed, or modified

If a directory other than the Active Directory also supports the LDAP protocol, the SAP system can take
advantage of the information stored there. For example, if there is an LDAP directory on a UNIX or Windows
server, you can configure the SAP system to use the information available there. In the following text,
directories other than the Active Directory that implement the LDAP protocol are called generic LDAP
directories.

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
168 PUBLIC Additional Information
This section does not provide information about the use of LDAP directories with the LDAP Connector. For
more information about using and configuring the LDAP Connector for an ABAP system, see the SAP Library
at:

SAP Release and SAP Library Quick Link SAP Library Path (Continued)

● SAP NetWeaver Mobile 7.1

Application Help Function-Oriented View Security
http://help.sap.com/nwmobile71
Identity Management Identity Management of the Application
● SAP NetWeaver Mobile 7.1 including Enhancement
Server ABAP Configuration of User and Role Administration
Package 1
http://help.sap.com/nwmobile711 Directory Services LDAP Connector

● SAP NetWeaver Process Integration 7.1

Application Help Function-Oriented View Security
http://help.sap.com/nwpi71
Identity Management Identity Management of the Application
● SAP NetWeaver Process Integration 7.1 Including En
Server ABAP Configuration of User and Role Administration
hancement Package 1
http://help.sap.com/nwpi711 Directory Services LDAP Connector

● SAP NetWeaver 7.3

Application Help Function-Oriented View: English
http://help.sap.com/nw73
Security Identity Management User and Role
● SAP NetWeaver 7.3 including Enhancement Package
Administration of Application Server ABAP Configuration of
1
http://help.sap.com/nw731 User and Role Administration Directory Services LDAP

● SAP NetWeaver 7.4 Connector

http://help.sap.com/nw74

Prerequisites

You can only configure the SAP system for Active Directory services or other LDAP directories if these are
already available on the network. As of Windows 2000 or higher, the Active Directory is automatically available
on all domain controllers. A generic LDAP directory is an additional component that you have to install
separately on a UNIX or Windows server.

In the SAP environment, you can exploit the information stored in an Active Directory or generic LDAP directory
by using:

● SAP Logon
● The SAP Microsoft Management Console (SAP MMC)
For more information about the automatic registration of SAP components in LDAP directories and the
benefits of using it in SAP Logon and SAP MMC, see the documentation SAP System Information in
Directory Services at:
https://archive.sap.com/documents/docs/DOC-14384
● The SAP Management Console (SAP MC)

SAP Logon
Instead of using a fixed list of systems and message servers, you can configure SAP Logon in the sapmsg.ini
configuration file to find SAP systems and their message servers from the directory. If you configure SAP logon
to use the LDAP directory, it queries the directory each time Server or Group selection is chosen to fetch up-to-
date information on available SAP systems.

To use LDAP operation mode, check that the sapmsg.ini file contains the following:

[Address]

Mode=LDAPdirectory

LDAPserver=

LDAPnode=

LDAPoptions=

Distinguish the following cases:

● If you use an Active Directory, you must set LDAPoptions=“DirType=NT5ADS”. For more information,
see the SAP system profile parameter ldap/options.
● You must specify the directory servers (for example, LDAPserver=pcintel6 p24709) if one of the
following is true:
○ The client is not located in the same domain forest as the Active Directory
○ The operating system does not have a directory service client (Windows NT and Windows 9X without
installed dsclient).
For more information, see the SAP system profile parameter ldap/servers.
● For other directory services, you can use LDAPnode to specify the distinguished name of the SAP root
node. For more information, see the SAP system profile parameter ldap/saproot.

SAP MMC
The SAP MMC is a graphical user interface (GUI) for administering and monitoring SAP systems from a central
location. It is automatically set up when you install an SAP system on Windows. If the SAP system has been
prepared correctly, the SAP MMC presents and analyzes system information that it gathers from various
sources, including the Active Directory.

Integrating the Active Directory as a source of information has advantages for the SAP MMC. It can read
system information straight from the directory that automatically registers changes to the system landscape.

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
170 PUBLIC Additional Information
As a result, up-to-date information about all SAP application servers, their status, and parameter settings is
always available in the SAP MMC.

If you need to administer distributed systems, we especially recommend that you use the SAP MMC together
with Active Directory services. You can keep track of significant events in all of the systems from a single SAP
MMC interface. You do not need to manually register changes in the system configuration. Instead, such
changes are automatically updated in the directory and subsequently reflected in the SAP MMC.

If your SAP system is part of a heterogeneous SAP system landscape that comprises systems or instances
both on Unix and Windows operating systems, you can also use the SAP MMC for operating and monitoring the
instances running on Unix.

SAP MC

The SAP MC is a graphical user interface (GUI) for administering and monitoring SAP systems from a central
location. The SAP MC is automatically set up when you install an SAP system on any platform. If the SAP
system has been prepared correctly, the SAP MC presents and analyzes system information that it gathers
from various sources, including a generic LDAP Directory.

Integrating a generic LDAP Directory as a source of information has advantages for the SAP MC. It can read
system information straight from the directory that automatically registers changes to the system landscape.
As a result, up-to-date information about all SAP application servers, their status, and parameter settings is
always available in the SAP MC.

For more information about the SAP MC and about how to configure it to access LDAP directories, see the
documentation SAP Management Console in the SAP Library at:

SAP Release and SAP Library Quick Link SAP Library Path (Continued)

● SAP NetWeaver 7.1 for Banking Services from SAP 5.0 See the SAP NetWeaver Mobile Library.
and 6.0
● SAP NetWeaver 7.1 including Enhancement Package 1  Note
for Banking Services from SAP 5.0 and 6.0 Since the SAP NetWeaver Mobile 7.1 Library is the only
available SAP Library for ABAP systems based on SAP
NetWeaver 7.1, in this guide we always refer to it also for
SAP NetWeaver 7.1 for Banking Services from SAP 5.0
and 6.0.

● SAP NetWeaver Process Integration 7.1

● SAP NetWeaver 7.3

Application Help Function-Oriented View: English
http://help.sap.com/nw73
Solution Life Cycle Management SAP Management
● SAP NetWeaver 7.3 including Enhancement Package 1
Console
http://help.sap.com/nw731
● SAP NetWeaver 7.4
http://help.sap.com/nw74

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
Additional Information PUBLIC 171
Configuration Tasks for LDAP Directories
This section describes the configuration tasks for the Active Directory or other (generic) LDAP directories.

● Configuration Tasks for Active Directory

To enable an SAP system to use the features offered by the Active Directory, you have to configure the
Active Directory so that it can store SAP system data.
To prepare the directory, you use the installer to automatically:
○ Extend the Active Directory schema to include the SAP-specific data types
○ Create the domain accounts required to enable the SAP system to access and modify the Active
Directory. These are the group SAP_LDAP and the user sapldap.
○ Create the root container where information related to SAP is stored
○ Control access to the container for SAP data by giving members of the SAP_LDAP group permission to
read and write to the directory
You do this by running the installer on the Windows server on which you want to use Active Directory
Services and choosing Generic Installation Options <Database> Preparations LDAP Registration
Active Directory Configuration . For more information about running the installer on Windows, see the
documentation Installation of SAP Systems Based on the Application Server <Stack> of SAP NetWeaver
<Release> on Windows: <Database> at https://support.sap.com/sltoolset System Provisioning
Installation Option of Software Provisioning Manager 1.0 .

 Note

You have to configure the directory server only once. Then all SAP systems that need to register in this
directory server can use this setup.

● Configuration Tasks for Generic LDAP Directories

To configure other LDAP directories, refer to the documentation of your directory vendor.
● Configuration Tasks for Generic LDAP Directories on Windows
To configure other LDAP directories, refer to the documentation of your directory vendor. The installer
software contains schema extensions for directory servers Netscape/iPlanet (ldregns4.txt,
ldregns5.txt) and OpenLDAP slapd (ldregslapd.schema). Both files are located in the directory
\<Unpack_Directory>\COMMON\ADS. After you have applied the schema extension, you need to create
a root container to store the SAP-related information and create a directory user that the SAP application
server can use to write information to the directory.
For more information about how to set up a Netscape/iPlanet directory server, see the documentation SAP
System Information in Directory Services at:
https://archive.sap.com/documents/docs/DOC-14384
● Enabling the SAP System LDAP Registration
Once you have correctly configured your directory server, you can enable the LDAP registration of the SAP
system by setting some profile parameters in the default profile.
To do this, run the installer [page 118] once for your system and choose:
Generic Installation Options <Database> Preparations LDAP Registration LDAP Support
If you use a directory server other than Microsoft Active Directory and/or non-Windows application
servers, you have to store the directory user and password information by using ldappasswd
pf=<any_instance_profile>. The information is encrypted for storage in DIR_GLOBAL and is therefore
valid for all application servers. After restarting all application servers and start services, the system is
registered in your directory server. The registration protocols of the components are dev_ldap*. The
registration is updated every time a component starts.

SAP on IBM i allows the installation of multiple SAP systems on a single host (provided space exists). However,
we recommend that you isolate your SAP production system as far as possible from your test and development
systems. The degree of isolation you opt for can range from running each SAP system on a separate host to
having all the environments on a single host.

If you decide to implement multiple SAP systems on a single host, you need to be aware of the risks involved.

Running multiple SAP systems on a single host is similar to MCOD. For more information, see SAP Note
443925 .

Importance of an Independent Testing Environment

If you have both your production and development or test systems on the same host, you cannot test IBM i
program temporary fixes (PTFs) and cumulative packages (CUM packages) in an independent testing
environment. The reason is that this immediately affects the production system.

The same problem applies to operating system upgrades. If upgrades initially take place in an independent test
environment, you can identify any customer-specific problems (such as problems resulting from any
modifications you might have made to the standard system) separate from the live environment.

If you have more than one SAP system on a single host, you can test SAP upgrades independently. However, if
you test an SAP upgrade on a separate host, it has the advantage that a test SAP upgrade does not take away
resources from the production system.

Possibilities for Resource Distribution

● LPAR: Logical Partitioning of the Host

You can divide your complete host into several entirely independent servers. This means that you install
different copies of the operating system on each of the servers. You can decide on the CPU, memory, and
DASD splitting. Only the serial number is the same, and all the other elements are separate and cannot
interfere with a system in another LPAR. This is the best (but most expensive) way to separate SAP
systems.
● Memory: Running SAP Instances in Separate Subsystems
Each SAP system with its associated database can have multiple instances. Each instance runs in a
separate operating system subsystem. (A subsystem is an operating environment in which the system
coordinates processing and resources.) The subsystem definition allows you to define and allocate
individual memory pools to the subsystem. These memory pools cannot be accessed by users from any
other SAP instance.
● Disks: Separate ASPs for Each SAP System
You can segment the installed disk capacity to provide a separate auxiliary storage pool (ASP) for each SAP
system. You can then allocate specific disk drives to each user ASP created. This helps to minimize the
impact of disk activity of one SAP environment on other SAP environments.
● Processors: Long-Running Tasks Can Slow Down the Production Environment

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
Additional Information PUBLIC 173
Regardless of the number of processors involved, IBM i manages them as a single entity. The operating
system dispatches tasks to the processors and balances the workload. A long-running program or other
task encountered during development or testing can have an impact on production activity if these SAP
systems are running on the same host. You can minimize the potential impact of this by running
development and test systems at a lower priority than the production system.

8.3 Creating a User for LDAP Directory Access

If you use LDAP directory services, you have to set up a user with a password on the host where the SAP
system is running. This permits the SAP system to access and modify the LDAP directory.

Prerequisites

During the SAP instance installation you chose to configure the SAP system to integrate LDAP services.

Context

For more information, see Integration of LDAP Directory Services [page 168].

Procedure

1. Log on as user <sapsid>adm.

2. Enter the following:
ldappasswd pf=<Path_and_Name_of_Instance_Profile>
3. Enter the required data.

 Example

The following is an example of an entry to create an LDAP Directory User:

CN=sapldap,CN=Users,DC=nt5,DC=sap-ag,DC=de

The SAP Host Agent is installed automatically during the installation of new SAP instances with SAP kernel 7.20
or higher (integrated installation). If you need to install the SAP Host Agent separately, use the documentation
Installation of SAP Host Agent on IBM i - Using Software Provisioning Manager 1.0 at:

https://support.sap.com/sltoolset System Provisioning Install a System using Software Provisioning

Manager Installation Option of Software Provisioning Manager 1.0 SP <Current Version> Installation
Guides - Standalone Engines and Clients SAP Host Agent

8.5 Splitting Off an ABAP Central Services Instance from

an Existing Primary Application Server Instance

With the installation option Split Off ASCS Instance from existing Primary Application Server Instance, you can
move the message server and the enqueue work process from an existing primary application server instance
to a newly installed ABAP central services instance (ASCS instance). The new ASCS instance is installed while
the split is done.

Prerequisites

The existing SAP system of the primary application server instance must meet the following requirements:

● It was upgraded from an SAP system release based on SAP NetWeaver lower than 7.1.
● It does not yet have an ASCS instance

Context

Before the Split

The ABAP stack of the primary application server instance includes:

● ABAP dispatcher and work processes (dialog, batch, spool, enqueue, or update)
● Gateway
● Internet communication manager (ICM)
● Java server processes
● Internet graphics service (IGS)
● ABAP message server

● ABAP dispatcher and work processes (dialog, batch, spool, or update)

● Gateway
● Internet communication manager (ICM)
● Java server processes
● Internet graphics service (IGS)

The newly created ABAP central services instance (ASCS instance) includes:

● ABAP message server

● ABAP standalone enqueue server
The ABAP enqueue work process is now replaced with the ABAP standalone enqueue server.

The Effect of the Split

The following graphic provides an overview of the components contained in the primary application server
instance before and after the split, along with the newly created ASCS instance:

Procedure

1. Plan the basic parameters, as described in SAP System Parameters [page 47]:
○ Choose an instance number for the ASCS instance to be created.
○ Note that the message server port is not changed during the split.

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
176 PUBLIC Additional Information
2. Check the hardware and software requirements for the ASCS instance to be created as described in
Hardware and Software Requirements [page 34].
3. Specify basic SAP System Parameters [page 47] for the ASCS instance to be created.
4. Set up the required file systems [page 64] for the ASCS instance to be created.
5. Check the prerequisites [page 115] and start the installer [page 118] on the host where the ASCS instance
is to be created.

6. On the Welcome screen, choose Generic Options <Database> Split Off ASCS Instance from Existing
Primary Application Server Instance .
7. Follow the instructions on the installer screens and enter the required parameters.

 Note

 Caution

All SAP system instances are stopped during the split procedure.

The installer starts the installation and displays the progress of the installation. When the installation has
successfully completed, the installer shows the dialog Execution of Split Off ASCS Instance from existing
Primary Application Server Instance has completed.
9. Restart the application server instances [page 177] (primary application server instance and additional
application server instances if they exist).
10. Check whether you can log on to the application servers [page 133].
11. Ensure user security [page 154] for the operating system users of the newly created ASCS instance.
12. If required, perform an installation backup [page 162].

8.6 Starting and Stopping SAP System Instances

You can start and stop SAP system instances and the diagnostics agent using the SAP Management Console
(SAP MC) (see Starting and Stopping SAP System Instances Using the SAP Management Console [page 178]).

Apart from using the SAP Management Console (SAP MC), you can also use commands to Start or stop SAP
system instances [page 181]

You can start and stop all instances of your SAP system using the SAP Management Console (SAP MC)except
the database instance.

Prerequisites

● Make sure that the host names defined in the DNS server match the names of the SAP system instance
hosts. In particular, keep in mind that host names are case-sensitive. For example, if the names of the SAP
system instance hosts are in upper case, but the same host names are defined in the DNS server in lower
case, starting and stopping the system does not work.
● If you want to start or restart remote systems or instances, make sure that you have registered them in the
SAP Management Console (SAP MC). You do not need to register SAP systems or instances installed on
the local host, because the SAP MC displays them automatically.
● The SAP Host Agent is installed on the host where the application server of the SAP system or instance
runs.
● You have installed Java Runtime Environment (JRE) 5.0 or higher.
● Your Web browser supports Java.
● Your Web browser's Java plug-in is installed and enabled to run scripting of Java applets.

Context

 Recommendation

If you experience any issues when starting or using the SAP MC, refer to SAP Note 1153713 .

● For more information about handling the SAP MC, see the SAP Library at:

SAP Release and SAP Library Quick Link SAP Library Path (Continued)

○ SAP NetWeaver 7.1 for Banking Services from SAP 5.0 See the SAP NetWeaver Mobile Library.
and 6.0
○ SAP NetWeaver 7.1 including Enhancement Package 1  Note
for Banking Services from SAP 5.0 and 6.0
Since the SAP NetWeaver Mobile 7.1 Library is the
only available SAP Library for ABAP systems based on
SAP NetWeaver 7.1, in this guide we always refer to it
also for SAP NetWeaver 7.1 for Banking Services from
SAP 5.0 and 6.0.

○ SAP NetWeaver Process Integration 7.1

Application Help Function-Oriented View
http://help.sap.com/nwpi71
Application Server Infrastructure SAP Management
○ SAP NetWeaver Process Integration 7.1 Including En
hancement Package 1 Console

http://help.sap.com/nwpi711

○ SAP NetWeaver 7.3

Application Help Function-Oriented View: English
http://help.sap.com/nw73
Solution Life Cycle Management SAP Management
○ SAP NetWeaver 7.3 including Enhancement Package 1
http://help.sap.com/nw731 Console

○ SAP NetWeaver 7.4

http://help.sap.com/nw74

● If your newly installed SAP system is part of a heterogeneous SAP system landscape comprising systems
or instances on Windows platforms, you can also start and stop it from a Windows system or instance
using the SAP Microsoft Management Console (SAP MMC).
For more information about handling the SAP MMC, see the SAP Library at:

Release SAP Library Quick Link SAP Library Path (Continued)

○ SAP NetWeaver Process Integration 7.1 See the SAP Library path for SAP NetWeaver 7.3 and
○ SAP NetWeaver Process Integration 7.1 Including En higher.
hancement Package 1

○ SAP NetWeaver 7.3

Application Help Function-Oriented View: English
http://help.sap.com/nw73
Solution Life Cycle Management SAP Microsoft
○ SAP NetWeaver 7.3 including Enhancement Package 1
http://help.sap.com/nw731 Management Console: Windows

○ SAP NetWeaver 7.4

http://help.sap.com/nw74

Procedure

● Starting the Web-Based SAP Management Console

1. Start a Web browser and enter the following URL:
http://<Host_Name>:5<Instance_Number>13

 Example

If the instance number is 53 and the host name is saphost06, you enter the following URL:

http://saphost06:55313

This starts the SAP MC Java applet.

If your browser displays a security warning message, choose the option that indicates that you
trust the applet.

2. Choose Start.
The SAP Management Console (SAP MC) appears.
By default, the instances installed on the host you have connected to are already added in the SAP MC.

 Note

If the instances have not been added or if you want to change the configuration to display systems
and instances on other hosts, you have to register your system manually. This is described in
Registering Systems and Instances in the SAP Management Console below.

● Starting SAP Systems or Instances

Similarly, you can start or restart all SAP systems and individual instances registered in the SAP MC.

1. In the navigation pane, open the tree structure and navigate to the system node that you want to start.
2. Select the system or instance and choose Start from the context menu.
3. In the Start SAP System(s) dialog box, choose the required options.
4. Choose OK.
The SAP MC starts the specified system or system instances.

 Note

The system might prompt you for the SAP system administrator credentials. To complete the
operation, you require administration permissions.

Log in as user <sapsid>adm.

Starting SAP System Instances Successively

If you need to start the instances of an SAP system successively – for example when you want to start a
distributed or a high-availability system – proceed as follows:

1. Start the database instance.

2. Start the ABAP central services instance ASCS<Instance_Number>.
3. Start the central services instance SCS<Instance_Number>.
4. Start the primary application server instance DVEBMGS<Instance_Number>.
5. Start additional application server instances D<Instance_Number>, if there are any.
● Stopping SAP Systems or Instances

Similarly, you can stop all SAP systems and individual instances registered in the SAP MC.

1. Select the system or instance you want to stop and choose Stop from the context menu.
2. In the Stop SAP System(s) dialog box, choose the required options.
3. Choose OK.
The SAP MC stops the specified system or system instances.

 Note

The system might prompt you for the SAP system administrator credentials. To complete the
operation, you require administration permissions.

Stopping SAP System Instances Successively

If you need to stop the instances of an SAP system successively – for example when you want to start a
distributed or a high-availability system – proceed as follows:

1. Stop additional application server instances D<Instance_Number>, if there are any.

2. Stop the primary application server instance DVEBMGS<Instance_Number>.
3. Stop the central services instance SCS<Instance_Number>.
4. Stop the ABAP central services instance ASCS<Instance_Number>.
5. Stop the database instance.

8.6.2 Starting and Stopping the SAP System Using

Commands

Use

The procedures below explain how to start and stop the SAP system after the installation.

Prerequisites

● You have checked the default profile /<sapmnt>/<SAPSID>/profile/DEFAULT.PFL for parameter

login/system_client and set the value to the correct productive system client. For example, the entry
must be login/system_client = 001 if your productive client is 001.

●  Note

The instance name (instance ID) of the primary application server instance is

DVEBMGS<Instance_Number>, the instance name of the central services instance is

SCS<Instance_Number>, and the instance name of an additional application server instance is
D<Instance_Number>. The instance name of the ABAP central services instance is
ASCS<Instance_Number>.

Procedure

Starting the SAP System

1. Log on to your IBM i as user <SAPSID>ADM.

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
Additional Information PUBLIC 181
2. Check that there are no active jobs for the instance that you have just installed. To do this, proceed as
follows:
1. For the central services instance, the primary application server instance and all additional application
server instances, enter the following command:
WRKACTJOB SBS(SAP<Instance_Number><SAPSID>)
2. If a job is displayed, stop it by entering the following command:
ENDSBS SBS(SAP<Instance_Number><SAPSID>) OPTION(*IMMED)
3. To start the SAP system, enter the following command and press F4 :
STARTSAP
4. Enter the SAP system ID (for example, C11) and instance number (for example, 90). Repeat this for each
instance that you want to start.

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

 Note

Make sure that the SAP system and associated AS Javas are up and running before you start or restart
additional application server instances and their AS Javas.

5. To check whether your SAP system started successfully for every installed instance, enter the following
command:
WRKACTJOB SBS(SAP<Instance_Number><SAPSID>)

 Note

Every instance runs in its own subsystem SAP<Instance_Number><SAPSID>.

Stopping the SAP System

1. Log on to your IBM i as <SAPSID>ADM.

2. To stop an SAP system, enter the following command and press F4 :
STOPSAP
3. Enter the SAP system ID (for example, C11) and instance number (for example, 90).
Repeat this for each instance that you want to stop.

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

For each stopped instance, the user you used to shut down the system receives a message from the operating
system.

Here you can find additional information about the IBM i:

● Correcting Errors in RFC Steps [page 183]

● IBM i Library Structure [page 184]
● IBM i Integrated File System [page 185]
● Restoring a Backup [page 187]
● Editing Stream Files [page 189]
● RFC SDK [page 190]

8.7.1 Correcting Errors in RFC Steps

Use

RFC steps, which have names starting with RFC such as RFCADDBDIF_IND_DB4, can fail for several reasons:

● The SAP system has not been started up correctly.

● The DDIC user has entered the wrong password.
● The jobs started by user DDIC cannot be executed.
● The SAP job cannot be started or executed in the SAP system.

Procedure

To correct an error in RFC steps, see the following table:

Errors in RFC Steps and Required User Actions

Cause of the Error User Actions

The SAP system has not been started up correctly. To check if the SAP work processes are running, enter the
following command:
This is indicated by error messages in the files dev_w* and
dev_disp. These files are located in the work directory. WRKACTJOB
SBS(SAP<Instance_Number><SAPSID>).

The DDIC user has entered the wrong password. Check whether you can log on to the SAP system as user
DDIC.

Check whether the password for DDIC is the default pass

word (19920706).

The jobs started by user DDIC cannot be executed. Monitor the jobs started by user DDIC. To do this, use trans
action SM37, paying particular attention to the job
RADDBDIF.

To look at the system log for detailed information, use trans

action SM21.

The SAP job cannot be started or executed in the SAP sys Check whether user <SAPSID>ADM has write permissions
tem. for directories /usr/sap/trans and /usr/sap/trans/
tmp.

If directory /usr/sap/trans is located on another IBM i

and if /usr/sap/trans is shared by QFileSvr.400, make
sure that the user <SAPSID>ADM exists on the remote sys
tem and has the same passwords on both systems.

 Note

Installation step RFCRADDBDIF_IND_DB4 also writes log file /usr/sap/trans/tmp/

RADDBDIF.<SAPSID>, which contains additional information about the status of the executed reports.

8.7.2 IBM i Library Structure

Definition

Libraries form the primary native organizational structure on IBM i. A library is an object that groups together
related objects.

There are three different types of library:

● System libraries, such as library QSYS for objects supplied as part of the operating system
● User libraries, such as the various libraries:

IBM i Library Structure

Library Description

SAP<SAPSID>IND Kernel Library for ILE programs and commands

SAP<SAPSID>I<Instance_Number> Instance-specific kernel library

SAP<SAPSID>IND<x> Library for menu objects

R3<SAPSID>DATA Database library

R3<SAPSID>JRN Journal receiver library

SAP<SAPSID>DB Java database library

SAP<SAPSID>JRN Java journal receiver library

R3<SAPSID>400 Library for work management objects

R3<SAPSID><XXXXX> Library for SQL packages

R3<Release>ARFC Library for RFC SDK (ASCII)

R3<Release>ACPIC Library for CPI-C SDK (ASCII)

R3* or SAP* Reserved for SAP

Q* System libraries

 Recommendation

<SAPSID> is the SAP system ID (for example PRD or TST).

<Release> is the SAP release (for example, 710).

<Instance_Number> is the instance number.

<x> is a number.

● Product libraries, such as library QPDA, which contains objects associated with the IBM i Programming
Development Manager (PDM)

 Recommendation

Some of the SAP library names might vary if you assign your own library names.

Types of objects stored in libraries include, for example, files and programs.

Files do not contain the actual data. The data is stored in members within each file. In SQL systems, such as
SAP systems, each file contains exactly one member.

8.7.3 IBM i Integrated File System

Use

Definition

The IBM i also provides a UNIX-style and PC-style integrated file system that provides enhanced capabilities
for managing new types of information processing including client/server, open systems, and multimedia.

The integrated file system (IFS) supports the use of stream files for storing and operating on data. Stream files
are files containing a continuous stream of data. This data might take the form of text files or images, for
example. Stream files are system objects with object type *STMF.

For more information about displaying or editing stream files, see Editing Stream Files [page 189].

Structure

The IBM i integrated file system has a hierarchy comparable to that used by UNIX. The integrated file system
treats the different types of support for accessing the various object types as separate file systems. These file
systems are:

IBM i Integrated File System

File System Description

“/” This file system corresponds to the UNIX root directory. This PC-style file system is
not case-sensitive.

QOpenSys The open systems file system. This UNIX-style file system is case-sensitive (not used
by the SAP system).

QSYS.LIB The library file system allowing the user to access objects residing in native IBM i libra
ries using IFS commands.

QDLS The document library services file system (not used by the SAP system).

QLANSrv The LAN Server/400 file system (not used by the SAP system).

QOPT The optical file system; this file system is mainly used during installation and contains
all media that have been inserted so far.

QFileSvr.400 This file system provides access to other file systems on remote IBM i systems. It is
used by several SAP functions, for example correction and transport, to access re
mote stream files.

 Caution

Take care with upper- and lowercase notation. The “/” file system is not case sensitive, but QOpenSys and
the contents of SAP profiles are case sensitive.

Integration

The integrated file system distinguishes between two different types of link: hard links and soft links. A link is a
named connection between a directory and an object.

Type of Link Description

Hard link, also known as link, absolute link ● Indicated by a separate directory entry
● Cannot exist unless linked to an object
● Cannot cross file systems

Soft link, also known as symbolic link ● Takes the form of a path name contained in a file
● Can exist without pointing to an existing object. (Is an
object of type *SYMLNK.)
● Can be removed without affecting the object
● Can cross file systems
● Only allowed in the IFS

 Note

To see the contents of a symbolic link, use the command WRKLNK with Detail option *EXTENDED. (This
command corresponds to the UNIX command ls -l.) Enter option 12 (Work with links).

 Note

The SAP system uses soft links by default.

8.7.4 Restoring a Backup

Use

You can restore a backup in the sequence given below.

Prerequisites

You have a full backup.

Procedure

1. Control the panel function.

2. Perform an initial program load (IPL) or Install System Menu.
3. To restore a user profile or profiles saved with the command
SAVSYS (Save System) or SAVSECDTA (Save Security Data), enter the following command:
RSTUSRPRF (Restore User Profile)

Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
Additional Information PUBLIC 187
4. To restore to the system a configuration object saved with the SAVSYS (Save System) or SAVCFG (Save
Configuration) command, enter the following command:
RSTCFG (Restore Configuration)
5. To restore libraries saved with the SAVLIB command with LIB(*NONSYS) specified, enter the following
command:
RSTLIB SAVLIB(*NONSYS) (Restore Library)
6. To restore documents, folders, and distribution objects, enter the following command:
RSTDLO (Restore Document Library Object)
7. To restore a copy of an object or objects that can be used in the Integrated File System, enter the following
command:
RST DEV('/qsys.lib/tap01.devd')
OBJ(('*' *INCLUDE) ('\qsys.lib' *OMIT) ('\qdls' *OMIT))
8. To restore saved changes in libraries, documents, and directories, enter the following command:
RSTLIB, RSTOBJ, RSTDLO, RST
9. To apply journaled changes (for a particular database file member) to recover the file, enter the following
command:
APYJRNCHG (Apply Journaled Changes)
10. To restore private authorities to user profiles, enter the following command:
RSTAUT (Restore Authority)

Restore Procedures

The Restore Objects (RSTOBJ) command can be used where the Restore Library (RSTLIB) command is
shown to restore objects.

For more information, see the IBM documentation IBM i Systems Management Recovering Your System
<Release> (SC41–5304–10) in the IBM Knowledge Center.

8.7.5 Editing Stream Files

Use

Stream files are files containing a continuous stream of data. Stream files are used, for example, to store
documents and images. On IBM i, SAP profiles are stored in stream files.

Procedure

You can access IBM i stream files and directories in a number of different ways.

● Using the Command EDTF

EDTF is an editor similar to SEU (Source Entry Unit). The prefix area of each record accepts the edit
command. To display the edit commands available, press F1 .
● Using IBM i NetServer
The IBM i NetServer is included in the operating system since V4R2M0. This provides, similar to Windows,
shares that can be mapped with every Windows client. You can configure these shares with a free-of-
charge option of the IBM i Navigator on IBM i Access for Windows and with the IBM Systems Director
Navigator for i. Since V4R4M0 you can configure a character-by-character conversion from ASCII to
EBCDIC and vice versa.
● Using IBM Systems Director Navigator for i
The IBM Systems Director Navigator for i is included in the operating system since V6R1M0. This provides
similar access to the file systems, including IBM i NetServer support, as with the IBM i Navigator on IBM i
Access for Windows.
● Using IBM i Access for Windows
If you have IBM i Navigator on IBM i Access for Windows, you can also access stream files using this
product. Using the Network Drive feature of IBM i Access for Windows and the capability of IBM i Access for
Windows to perform a character-by-character conversion from ASCII to EBCDIC and vice versa, you can
work on the IBM i IFS in the same way as on the PC file system. That is, you can create, edit, and delete files
and directories with all the restrictions that apply to IBM i Access for Windows.

 Note

To install the RFC SDK, see SAP Note 1097997 .

After you have installed the optional AddOn RFC SDK on your IBM i, the library R3<REL>RFC contains the
Remote Function Call Software Development Kit (RFC SDK) and the C++ Remote Function Call Software
Development Kit (CRFC SDK). (<REL> stands for the current SAP Release, for example 700).

The RFC SDK provides an open programming interface, which can be used to provide non-SAP-applications
direct access to SAP functions.

RFC SDK

The RFC SDK examples and test programs are no longer available in the 7.20 SDK. You must use the source
code from an older release and re-compile the programs on your own.

Activities: Compiling and Linking an RFC Program on IBM i

To create an executable, use the commands CRTMOD, CRTPGM.

How to create the executable sapinfo:

ADDLIBLE LIB(R3<REL>RFC)

CRTCMOD MODULE(SAPINFO) SRCFILE(R3<REL>RFC/C)

OUTPUT(*PRINT)

OPTION(SYSINCPATH SHOWUSR *EXPMAC)

DBGVIEW(SOURCE) DEFINE(‘SAPonOS400’) SYSIFCOPT(IFSIO)

CRTPGM PGM(SAPINFO) MODULE(SAPINFO) BNDSRVPGM(LIBRFC) DETAIL(*FULL)

 Note

For more information about RFC SDK functionality on IBM i, see SAP Note 84685 .

8.8 Uninstalling an SAP System or Single Instances

This section describes how to uninstall a complete SAP system or single SAP instances with the Uninstall
option of the installer.

Prerequisites

● You have installed your SAP system with standard SAP tools according to the installation documentation.
● You are logged on as user QSECOFR or as a user that has the same authorizations as QSECOFR.

 Caution

Do not use the <sapsid>adm user to delete the SAP system.

● Make sure that the SAP system, or single instance, or standalone engine, or optional standalone unit to be
deleted is down and that you are not logged on as one of the SAP system users. Also check that all SAP-
related processes are stopped. If there is a lock on one of the SAP system objects, the uninstall fails.

 Note

You do not have to stop the SAP Host Agent. The SAP Host Agent is stopped automatically during the
uninstall process.

● When starting the uninstall, make sure that there are no SAP system user sessions still open.
● You have completed a DMO to SAP S/4HANA 1809 and higher. Next, you want to do an SAP Uninstall to
delete your SAP source system on IBM i. The SAP Uninstall requires some manual prerequisite steps to
finish successfully. For example the profile directory must be adapted. For more information, see the SAP
Note 2957193 - IBM i: Uninstalling the SAP source system after the DMO to SAP S/4HANA 1809 and
higher.

If you run the SAP Uninstall for the SAP source system before all prerequisite steps are done, the new
already running SAP S/4HANA system could be damaged! For example the kernel executables and the
profiles of the new SAP S/4HANA system could be deleted.

Context

Note the following when deleting an SAP system or single instances:

● You cannot delete an SAP system remotely.

● If you delete network-wide users or groups in an environment with Network Information System (NIS),
other SAP installations might also be affected. Before you delete users or groups, make sure that they are
no longer required.
● During the uninstall process, all file systems and subdirectories of the selected SAP system or single
instance are deleted. Before you start uninstalling, check that you have saved a copy of all files and
directories that you want to keep to a secure location.
● The uninstall process is designed to remove as much as possible of the SAP system to be deleted. If an
item cannot be removed, a message informs you that you have to remove this item manually. You can do
this either at once or after the uninstall process has finished. As soon as you confirm the message, the
uninstall process continues.

 Note

If uninstalling a system from an independent ASP after removal ensure that the following directories
have been removed:

/<IASP_Name>/usr/sap/<SAPSID> and /<IASP_Name>/sapmnt/<SAPSID>

Procedure

1. Start the installer as described in Running the Installer [page 118].

2. On the Welcome screen, choose:

Generic Installation Options <Database> Uninstall Uninstall SAP Systems or Single Instances
3. Follow the instructions on the installer screens to delete a complete SAP system or single instances.

 Note

The following table provides information about deleting a complete system or single instances with the
installer.

Standard system You can delete a standard system (where all instances reside on the same host) in one
installer run.

 Note
The uninstall on IBM i now supports the option to leave the SAP database li
brary(ies) when deleting the entire SAP system. To activate the leave database
option, you must select the following two checkboxes in the installer dialog "Unin
stall Instances" in the section Existing SAP System Instances:
○ Uninstall all instances of this SAP system ID from this host.
○ Do not delete the data library(ies) when the SAP system is removed from this
host.

This option is only available when you are using the following kernel versions or
higher:

 Note
The uninstall only uses the SAP kernel tool DLTR3INST and DLTR3SYS. Whenever
these tools fail to delete an object on IBM i, this object is given to the user
SAPGARBAGE. SAP system objects are also given to the user SAPGARBAGE when it
is not clear if the object should be erased. Finally, check after every uninstall all
the objects of SAPGARBAGE using WRKOBJOWN and delete all objects you do not
need anymore.

For more information, see SAP Note 936965 .

Distributed system You run the installer and delete the required instances or standalone engines.

If you want to delete a distributed system, you have to run the installer to delete the
required instances locally on each of the hosts belonging to the SAP system in the fol
lowing sequence:

 Caution
Only select checkbox Uninstall all instances of the SAP system from this host when
removing the last remaining instance of the SAP system. Otherwise the contents
of mounted global directories under /<sapmnt>/<SAPSID>/ such as in
stance profiles and kernel executables, are also deleted.

1. Additional application server instances, if there are any

2. Only valid for 'Platform':
All SAP instances that are installed on IBM i.
End of 'Platform':
3. Primary application server instance
4. ABAP Central services instance (ASCS)
5. Central services instance (SCS)

 Note
Select this option if you want to drop theThe uninstall only uses the SAP kernel
tool DLTR3INST and DLTR3SYS. Whenever these tools fail to delete an object on
IBM i, this object is given to the user SAPGARBAGE. SAP system objects are also
given to the user SAPGARBAGE when it is not clear if the object should be erased.
Finally, check after every uninstall all the objects of SAPGARBAGE using
WRKOBJOWN and delete all objects you do not need anymore.

For more information, see SAP Note 936965 .

This option is only available when you are using the following kernel versions or
higher:

7.21 PL 1300, 7.22 PL 800, 7.49 PL 700 or 7.53 PL 400.

Additional application server If you want to delete additional application server instances of an existing SAP system,
you have to run the installer to delete them locally on each additional application
server instance host.

Standalone SAP Host Agent The SAP Host Agent is automatically uninstalled from a host together with the last re
maining SAP system instance.

If you want to uninstall a standalone SAP Host Agent, deselect Profiles Available and
select Uninstall Standalone SAP Host Agent on the General SAP System Parameters
screen.

4. When you have finished, delete the relevant directory structure on the global host.
5. To remove obsolete SLD data, see the following document: https://wiki.scn.sap.com/wiki/display/SL/
More+on+System+Landscape+Directory How-to Manage House-Cleaning in the System Landscape
Directory - Duplicate System Entries

8.9 Deleting an SAP System on IBM i

Use

This section describes how to delete an SAP system that is installed on IBM i. This is an alternative way to
delete an SAP system with installer.

 Caution

This description assumes that the installation of your SAP system has been performed using SAP standard
tools according to the installation documentation.

Procedure

1. Make sure that you deleted all remote instances that belong to this system. You cannot delete the SAP
system when still a remote instance exists.

 Note

You no longer have to delete all local instances first before deleting the SAP system like in the past. This
can now be done in one step.

For more information, see Deleting an SAP Instance [page 197].

2. To add the kernel library to the library list enter the following command:
ADDLIBLE LIB(SAP<SAPSID>IND)

If you want to delete a complete ABAP+Java system but not the ABAP + Java database instance, delete
all instances but do not delete the system (on the database instance host) at the end using the
command DLTR3SYS.

3. Make sure that your entire SAP system is down using the following command:
STOPSAP SID(<SAPSID>) INSTANCE(*ALL) STARTUPSRV(*ALL) XDNLISTEN(*YES) WAIT(*YES)
WAITTIME(600) ENDSBS(*YES)
4. To delete an SAP system, enter the following command:
DLTR3SYS SID(<SAPSID>)

 Note

If you want to delete the entire SAP system and all local instances, related directories, and files enter
the following command:

DLTR3SYS SID(<SAPSID>) DLTINST(YES) DLTGLB(YES) DLTHOME(*YES)

 Recommendation

We recommend that you check the parameters of DLTR3SYS. You might want to use some parameters
selectively such as DLTINST,DLTGLB, DLTHOME, or USROWNOBJ. For more information, see SAP Note
936965 .

 Note

When you encounter errors using DLTR3SYS use the command DSPJOBLOG to correct the problem.
Objects with locks usually cause an error. After deleting an object lock using the command
WRKOBJLCK, you can start DLTR3SYS again to continue deleting your system.

5. If the following directories and files exist, delete them by entering the following command:
WRKLNKSAP
○ /usr/sap/trans/cofiles/*<SAPSID>*
○ /usr/sap/trans/data/*<SAPSID>*
○ /usr/sap/trans/log/*<SAPSID>*
○ /usr/sap/trans/buffer/*<SAPSID>*
Choose 4 (Remove) on every file that is found by the command WRKLNKSAP.

 Example

For example, for directory /usr/sap/trans/data, enter the following command:

WRKLNKSAP DIR('/usr/sap/trans/data/*<SAPSID>*')

Choose 4 (Remove) on the listed files.

 Note

To limit the command WRKLNKSAP, choose Subset (in the upper right part on the screen).

6. If the following directories exist, delete them by entering the following commands:
RMVDIR DIR('/sapmnt/<SAPSID>') SUBTREE(*ALL)

 Note

If you are removing a system from an independent ASP also delete the contents from the following
directories:

RMVDIR DIR('/<IASP_Name>/usr/sap/<SAPSID>') SUBTREE(*ALL)

RMVDIR DIR('/<IASP_Name>/sapmnt/<SAPSID>') SUBTREE(*ALL)

7. If the kernel library of the system you just deleted was only used by the deleted system, you can remove it.
○ To remove the kernel library from the library list, enter the following command:
RMVLIBLE LIB(SAP<SAPSID>IND)
○ To delete the kernel library, enter the following command:
DLTLIB LIB(SAP<SAPSID>IND)

Result

The SAP system is now deleted. If you want to reinstall an SAP system, you can use the same <SAPSID> as the
one of the SAP system you deleted.

8.10 Deleting an SAP Instance on IBM i

Use

This section describes how to delete SAP instances that are installed on IBM i. This is an alternative way to
delete an SAP instance by installer.

 Caution

If you delete an entire SAP system, you have to first delete the remote instances one by one. All local
instances and the SAP system can be deleted at the same time using the command DLTR3SYS. For more
information, see Deleting an SAP System on IBM i [page 195].

 Caution

This description assumes that the installation of your SAP system has been performed using SAP standard
tools according to the installation documentation.

To delete an instance, log on to the IBM i where the SAP instance you want to delete is installed. To do this, log
on as user QSECOFR or as a user that has the same authorizations as QSECOFR.

1. To add the kernel library to the library list, enter the following command:
ADDLIBLE LIB(SAP<SAPSID>IND)
2. To make sure that the entire SAP instance is down, enter the following command:
STOPSAP SID(<SAPSID>) INSTANCE(<Instance Number>) STARTUPSRV(*ALL)
XDNLISTEN(*YES) WAIT(*YES) WAITTIME(600) ENDSBS(*YES)
3. To delete an entire SAP instance, enter the following command:
DLTR3INST SID(<SAPSID>) INST(<Instance Number>)

 Caution

If you want to delete a complete ABAP+Java system but not the ABAP + Java database instance, delete all
instances but do not delete the system (on the database instance host) at the end using the command
DLTR3SYS.

 Recommendation

We recommend that you check the parameters of DLTR3INST. You might want to use some parameters
selectively like for example DLTINST, DLTHOME or USROWNOBJ. For more information, see SAP
Note936965 .

 Note

If there is no instance of an SAP system (especially the database instance host) remaining on the IBM i
host, you can delete the rest of the file structures, the ABAP database and/or the Java database etc. of the
SAP system by using the command DLTR3SYS on the host. This will not delete any instance of the SAP
system on any other IBM i host. For more information, see Deleting an SAP System on IBM i [page 195].

 Note

When you encounter errors using DLTR3INST use the command DSPJOBLOG to correct the problem.
Objects with locks usually cause an error. After deleting an object lock using the command WRKOBJLCK,
you can start DLTR3INST again to continue deleting your instance.

A.1 Online Information from SAP

More information is available online as follows:

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 SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
200 PUBLIC Important Disclaimers and Legal Information
Installation of SAP Systems Based on the Application Server Dual-Stack (ABAP+Java) of SAP
NetWeaver 7.1 to 7.4 Support Release 2 (Out-Of-Maintenance Releases) on IBM i : IBM Db2 for
i
Important Disclaimers and Legal Information PUBLIC 201
www.sap.com/contactsap

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

Wa0006.
No ratings yet
Wa0006.
4 pages
SAP Process Refresh Session v3.0
No ratings yet
SAP Process Refresh Session v3.0
109 pages
Upgradation & Migration From ERP To HANA
No ratings yet
Upgradation & Migration From ERP To HANA
61 pages
Work Manager 5 Help Card PDF
No ratings yet
Work Manager 5 Help Card PDF
5 pages
Manual Instructions For SAP Note 3301438
No ratings yet
Manual Instructions For SAP Note 3301438
4 pages
Concur - Creating SFTP Keys With PuttyGen - 2017 PDF
No ratings yet
Concur - Creating SFTP Keys With PuttyGen - 2017 PDF
5 pages
Module 4 Irrigation Engineering
No ratings yet
Module 4 Irrigation Engineering
18 pages
Cognitive Computing For Natural Language Processing NLP and Understanding Medical Imaging Narratives
No ratings yet
Cognitive Computing For Natural Language Processing NLP and Understanding Medical Imaging Narratives
5 pages
LOI and Quatation Gudang Baja
No ratings yet
LOI and Quatation Gudang Baja
7 pages
Understanding Airplane Components
No ratings yet
Understanding Airplane Components
12 pages
Module V Hands-On Problem-Solving Using C Practical
No ratings yet
Module V Hands-On Problem-Solving Using C Practical
57 pages
Special Counter ICs UNIT 3
No ratings yet
Special Counter ICs UNIT 3
3 pages
1668887handson Quantum Machine Learning With Python Volume 1 Get Started DR Frank Zickert PDF Download
100% (3)
1668887handson Quantum Machine Learning With Python Volume 1 Get Started DR Frank Zickert PDF Download
76 pages
Interoperability Between UMTS and LTE (RAN19.0 - 01) PDF
No ratings yet
Interoperability Between UMTS and LTE (RAN19.0 - 01) PDF
1,393 pages
Apple vs. Samsung: Activity
No ratings yet
Apple vs. Samsung: Activity
2 pages
Marlyn: Advanced Surveying Drone
No ratings yet
Marlyn: Advanced Surveying Drone
8 pages
Anti-Cancer Research Paper
No ratings yet
Anti-Cancer Research Paper
8 pages
AES Cover Letter
No ratings yet
AES Cover Letter
1 page
Extrusion and Oilseed Processing: Expanders To Prepare Solvent Extraction
No ratings yet
Extrusion and Oilseed Processing: Expanders To Prepare Solvent Extraction
6 pages
Robotics & Automation Curriculum
No ratings yet
Robotics & Automation Curriculum
12 pages
iPhone Activation Process
100% (1)
iPhone Activation Process
5 pages
Hazards in Agricultural Maintenance Tasks
No ratings yet
Hazards in Agricultural Maintenance Tasks
2 pages
XtremePower 61108
No ratings yet
XtremePower 61108
10 pages
Inherently Safer Process Checklist
No ratings yet
Inherently Safer Process Checklist
6 pages
Analog & Digital Motor Control Manual
100% (2)
Analog & Digital Motor Control Manual
204 pages
Perenco PCP-2 PL2019-BR-PCP-C2-KPE-MT-Q-001 Macaé-RJ 10070-3000-T29-4-0002
No ratings yet
Perenco PCP-2 PL2019-BR-PCP-C2-KPE-MT-Q-001 Macaé-RJ 10070-3000-T29-4-0002
8 pages
Guide to Strategic Thinking Skills
No ratings yet
Guide to Strategic Thinking Skills
14 pages
2.5. Data Types
No ratings yet
2.5. Data Types
4 pages
South Africa High Court Affidavit: Judicial Review
100% (1)
South Africa High Court Affidavit: Judicial Review
51 pages
Import Cost Calculation Guide
No ratings yet
Import Cost Calculation Guide
2 pages
Dairy Farming in Amargosa Valley
No ratings yet
Dairy Farming in Amargosa Valley
2 pages
Financial Institutions & Financial Markets Module - 1: by Sanjeev Tamhane
No ratings yet
Financial Institutions & Financial Markets Module - 1: by Sanjeev Tamhane
35 pages
Solved Currently The Price Index Used To Calculate The Inflation Rate
No ratings yet
Solved Currently The Price Index Used To Calculate The Inflation Rate
1 page
Answers For Human Physiology From Cells To Systems 9th Edition Sherwood Ebook and TestBank Bundle
No ratings yet
Answers For Human Physiology From Cells To Systems 9th Edition Sherwood Ebook and TestBank Bundle
331 pages
Awareness and Utilization of Mobile Health Applications Among Teaching and Non Teaching Staff of Nnamdi Azikiwe University Awka, Anambra State
No ratings yet
Awareness and Utilization of Mobile Health Applications Among Teaching and Non Teaching Staff of Nnamdi Azikiwe University Awka, Anambra State
13 pages
Sample Division Memo
No ratings yet
Sample Division Memo
3 pages

NW71x ABAPJava

Uploaded by

NW71x ABAPJava

Uploaded by

Installation Guide | PUBLIC

Software Provisioning Manager 1.0 SP30 (Out-Of-Maintenance Releases)

Installation of SAP Systems Based on the

Of-Maintenance Releases) on IBM i : IBM Db2 for i

THE BEST RUN

2 About this Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

3 Installation Options Covered by this Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

8 Additional Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Version Date Description

○ Preparing the Installation Media [page 94] Downloading Specific Installation

Archives (Archive-Based Installation)

1.5 2013-11-28 Updated version

1.4 2013-11-13 Updated version

1.3 2013-10-28 Updated version

1.2 2013-10-27 Updated version

1.1 2013-09-25 Updated version

1.0 2012-08-06 First version for Software Provisioning Manager 1.0

For more information, see SAP Note 2980160 .

Naming Conventions [page 12]

Constraints [page 13]

Before You Start [page 14]

SAP Notes for the Installation [page 15]

New Features [page 16]

2.1 SAP Product Releases Out-Of-Maintenance, Based on

Based on the following SAP NetWeaver Re­

SAP NetWeaver 7.4 Support Release 2 SAP NetWeaver 7.4

SAP NetWeaver 7.3 SAP NetWeaver 7.3

SAP NetWeaver Process Integration 7.1 SAP NetWeaver 7.1

2.2 Naming Conventions

For more information, see SAP Note 2980160 .

2.4 Before You Start

Document Internet Address

Master Guide – SAP NetWeaver 7.4 http://help.sap.com/nw74

Installation and Upgrade

Master Guide – SAP Enhancement Package 1 for http://help.sap.com/nw731

Master Guide – SAP NetWeaver 7.3 http://help.sap.com/nw73

Installation and Upgrade

Master Guide - SAP NetWeaver PI 7.1 http://help.sap.com/nwpi71

Installation and Upgrade

2.5 SAP Notes for the Installation

SAP Notes for the Installation

SAP Note Number Title Description

886535 Downloading multispanning archives Downloading multispanning archives

2.6 New Features

Feature Description Availability

Introducing SWPM10RMSP30_<Version>.SAR replaces SWPM 1.0 SP30 (SL Toolset 1.0

LOADTOOLS.SAR The load tools in Software Provisioning Manager

For more information, see Downloading and Extracting the Soft­

For more information, see Prerequisites for Running the Installer

For more information, see Preparing the Installation Media [page

For more information, see Downloading and Extracting the Soft­

For more information, see Operating System Users in SAP System

In addition, check SAP Note 1680045 whether additional infor­

For more information, see ASCS Instance with Integrated SAP

You now have to install the Diagnostics Agent always separately.

For more information, see the Diagnostics Agent Installation

For more information, see SAP System Parameters [page 47].

For more information, see SAP Note 1979965 .

Standard System [page 22]

Distributed System [page 23]

High-Availability System [page 24]

Additional Application Server Instance [page 25]

ASCS Instance with Integrated SAP Web Dispatcher [page 29]

ASCS Instance with Integrated Gateway [page 30]

3.1 Standard System

You can install a standard system on a single host.

In a standard system, all main instances run on a single host.

There are the following instances:

● ABAP Central services instance (ASCS instance)

3.2 Distributed System

● ABAP Central services instance (ASCS instance)

3.3 High-Availability System

In a high-availability system, every instance can run on a separate host.

There are the following instances:

● ABAP central services instance (ASCS instance)

3.4 Additional Application Server Instance

Based on the following SAP NetWeaver Re

For more information, see Downloading and Extracting the Soft

For more information, see Downloading and Extracting the Soft

In addition, check SAP Note 1680045 whether additional infor

SAP System Pro /<sapmnt>/<SAPSID>/profile or /usr/sap/<SAPSID>/SYS/profile