Installation Guide | PUBLIC

Software Provisioning Manager 1.0 SP35

Document Version: 4.1 – 2022-02-14

Installation of SAP Systems Based on the

Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
© 2022 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN

Content

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

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

2.1 SAP Products Based on SAP NetWeaver 7.3 EHP1 to 7.52 Supported for Installation Using
Software Provisioning Manager 1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.2 Naming Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.3 Constraints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
2.4 Before You Start. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.5 SAP Notes for the Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.6 New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

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

3.1 Standard System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.2 Distributed System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.3 High-Availability System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.4 Additional Application Server Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.5 ASCS Instance with Integrated SAP Web Dispatcher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.6 ASCS Instance with Integrated Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

4 Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.1 Planning Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.2 Installation Using a Stack Configuration File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.3 Hardware and Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Running the Prerequisites Check in Standalone Mode (Optional). . . . . . . . . . . . . . . . . . . . . . . . 40
Requirements for the SAP System Hosts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
4.4 Planning User and Access Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
4.5 Basic Installation Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
SAP System Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
SAP System Database Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Additional Parameters when Installing SAP Process Integration 7.5 or SAP Solution Manager
7.2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Additional Parameters When Using a Stack Configuration File. . . . . . . . . . . . . . . . . . . . . . . . . . 61
Parameters for Additional Components to be Included in the ASCS Instance. . . . . . . . . . . . . . . . 63
4.6 SAP System Transport Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
4.7 Planning the Switchover Cluster for High Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

5 Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
5.1 Preparation Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
2 PUBLIC Content
5.2 Installing the SAP HANA Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
5.3 Setting Connectivity Data for the SAP HANA Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
5.4 Required File Systems and Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
SAP Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
SAP HANA Database Client Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
5.5 Using Virtual Host Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
5.6 Performing Switchover Preparations for High Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
5.7 Preparation for IBM i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Installing the Performance Library libperfstat.a for liveCache. . . . . . . . . . . . . . . . . . . . . . . . . . .80
Checking the Transport Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Qp2Term, Qp2Shell, and the Portable Application Solution Environment. . . . . . . . . . . . . . . . . . . 82
Installing the Qshell. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Checking and Adjusting Operating System Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83
Adjusting Startup Program QSTRUP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Configuring TCP/IP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Adjusting the Relational Database Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Installing English as a Secondary Language. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Preparing the SAP Installation User on IBM i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Enable the User QSECOFR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
5.8 Installing the SAP Front-End Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99
5.9 Configuring Host Names for the SAP HANA Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
5.10 Establishing Secure Connection to the SAP HANA Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Applying Self-signed Certificates while Running the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Configuring SAP HANA Encryption Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
5.11 Checking Time Zones. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
5.12 Preparing the Installation Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103
Media Required for the Installation - Listed by SAP System Instance. . . . . . . . . . . . . . . . . . . . . 103

6 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
6.1 Installation Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
6.2 Linking Global Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
6.3 Specifying the Initial Data Source of the User Management Engine. . . . . . . . . . . . . . . . . . . . . . . . .125
6.4 Prerequisites for Running the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
6.5 Running the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
6.6 Additional Information about the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Useful Information about the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132
System Provisioning Using an Input Parameter File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Interrupted Processing of the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Entries in the Services File Created by the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Troubleshooting with the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Troubleshooting During the Database Load. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Using the Step State Editor (SAP Support Experts Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Content PUBLIC 3
7 Post-Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
7.1 Post-Installation Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
7.2 Logging On to the Application Server ABAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
7.3 SAP NetWeaver 7.4 and Higher: Performing Automated Initial Setup (Optional). . . . . . . . . . . . . . . . 149
7.4 Enabling SAP EarlyWatch Alert for ABAP Systems on SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . 151
7.5 Installing the SAP License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
7.6 High Availability: Setting Up Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
7.7 Configuring the Remote Connection to SAP Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
7.8 Enabling Note Assistant to Apply Note Corrections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155
7.9 Configuring Documentation Provided on the SAP Help Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
7.10 Performing the Consistency Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
7.11 Setting Up the Transport Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
7.12 Configuring the Change and Transport System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
7.13 Connecting the System to SAP Solution Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
7.14 Running Installer Option “Check and Adjust ABAP System”. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
7.15 Applying the Latest Kernel and Support Package Stacks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
7.16 Performing Post-Installation Steps for the ABAP Application Server. . . . . . . . . . . . . . . . . . . . . . . . 165
7.17 Systems Based on SAP NetWeaver AS for ABAP 7.52 only: Switching to Standalone Enqueue
Server 2 and Enqueue Replicator 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
7.18 SAP Solution Manager 7.2, SAP Process Integration 7.5 only: Enabling HTTPS Communication for
ABAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
7.19 Installing Additional Languages and Performing Language Transport. . . . . . . . . . . . . . . . . . . . . . . 169
7.20 SAP Kernel 7.40 and Higher: IP Multicast Configuration and Wake-Up Mechanism. . . . . . . . . . . . . . 170
7.21 Configuring the User Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
7.22 Ensuring User Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172
7.23 Performing the Client Copy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175
7.24 Installation or Upgrade of SAP HANA Studio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
7.25 Backing Up the SAP HANA Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
7.26 SAP Systems Based on SAP NetWeaver 7.4 and Higher: Changing Keys for the Secure Storage
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
7.27 Removing the Installer Installation Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
7.28 Performing a Full Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
7.29 Logging on to the SAP Web Dispatcher Management Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
7.30 SAP Web Dispatcher Configuration (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
7.31 Gateway Configuration (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184

8 Additional Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

8.1 Integration of LDAP Directory Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
8.2 Multiple SAP Systems on a Single Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
8.3 Creating a User for LDAP Directory Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191
8.4 Installing the SAP Host Agent Separately. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
8.5 Starting and Stopping SAP System Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
4 PUBLIC Content
 Starting and Stopping SAP System Instances Using the SAP Management Console. . . . . . . . . . 193
Starting and Stopping the SAP System Using Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
8.6 IBM i-specific Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Correcting Errors in RFC Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
IBM i Library Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
IBM i Integrated File System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Restoring a Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Editing Stream Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
RFC SDK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205
8.7 Uninstalling an SAP System or Single Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206
8.8 Deleting an SAP System on IBM i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
8.9 Deleting an SAP Instance on IBM i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Content PUBLIC 5
1 Document History

 Note

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

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

Version Date Description

4.3 2022-06-01 Updated version for software provisioning manager 1.0 SP35 (SL Toolset 1.0 SP35)

4.2 2022-05-24 Updated version for software provisioning manager 1.0 SP35 (SL Toolset 1.0 SP35)

4.1 2022-02-14 Updated version for software provisioning manager 1.0 SP34 (SL Toolset 1.0 SP34)

4.0 2021-10-11 Updated version for software provisioning manager 1.0 SP33 (SL Toolset 1.0 SP33)

3.9 2021-06-21 Updated version for Software Provisioning Manager 1.0 SP32 (SL Toolset 1.0 SP32)

3.8 2021-02-15 Updated version for Software Provisioning Manager 1.0 SP31 (SL Toolset 1.0 SP31)

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
6 PUBLIC Document History
 Version Date Description

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

● New Features:
○ New Installer Option Download Media for a Maintenance Plan, documented in: New
Features, Downloading the Media for a Maintenance Planner Transaction
○ Validity Check for SUM*.SAR Archive, documented in: New Features, Additional Pa­
rameters When Using a Stack Configuration File (Optional)
● Information “enqueue server” versus “enqueue server 2”, “enqueue replication server”
versus “enqueue replication server 2” added: High-Availability System , System Based on
SAP NetWeaver AS for ABAP 7.52 only: Switching to Enqueue Server 2 and Enqueue Repli­
cation Server 2
● Post-installation section Systems Based on SAP NetWeaver AS for ABAP 7.52 Only: Run
Installer Option “Check and Adjust ABAP System” added

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Document History PUBLIC 7
Version Date Description

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.
○ Download Media for a Maintenance Plan, documented in: New Features, Download­
ing Media for a Maintenance Plan
○ 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
○ Simplified additional application server instance installation, documented in: New
Features, Preparing the Installation Media, Downloading SAP Kernel Archives (Ar­
chive-Based Installation)

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
Archive-based Language Installation, documented in: Additional Parameters When Using
a Stack Configuration File

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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
8 PUBLIC Document History
 Version Date Description

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

○ Preparing the Installation Media [page 103] 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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Document History PUBLIC 9
2 About this Document

This installation guide describes how to install an SAP system based on the application server ABAP of SAP
NetWeaver 7.3 EHP1 to 7.52 using the installation tool Software Provisioning Manager 1.0 SP35 (“installer” for
short), which is part of SL Toolset 1.0 SP35.

 Note

SAP products based on SAP NetWeaver 7.10 to 7.40 SR1 (with the exception of SAP Solution Manager 7.2
ABAP, which will continue to be supported ) are only supported in mainstream maintenance 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 .
The guide set attached to SAP Note 2980160 covers only the SAP product versions which have reached
end of maintenance.

 Note

SAP HANA Database is not released for SAP NetWeaver 7.3 on IBM i.

 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 Products Based on SAP NetWeaver 7.3
EHP1 to 7.52 Supported for Installation Using Software Provisioning Manager 1.0 [page 12].

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 15] before you continue with this installation guide.

The SAP HANA database is normally part of the SAP HANA appliance. It is normally pre-installed by SAP
partners before you start the installation. For more information about how to install the SAP HANA database,
see the SAP HANA Server Installation and Update Guide at https://help.sap.com/hana_platform
Installation and Upgrade . During the installation of the SAP system, SoftwareProvisioning Manager (the
“installer”) accesses the SAP HANA database remotely to perform the necessary database-specific installation
steps.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
10 PUBLIC About this Document
For SAP SCM only: If you want to use SAP liveCache on SAP HANA, you must install the LCAPPS package on
the database server. For more information, see the SAP MaxDB Administration Guide at https://help.sap.com/
maxdb Application Help

SAP Products Based on SAP NetWeaver 7.3 EHP1 to 7.52 Supported for Installation Using Software
Provisioning Manager 1.0 [page 12]
Here you can find a list of the SAP products based on SAP NetWeaver 7.3 EHP1 to 7.52 ABAP that are
supported for installation using Software Provisioning Manager 1.0, 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 14]

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

Make sure that you have read the release-specific “Master Guide” - called “Installation Guide” for SAP
S/4HANA - for your SAP Business Suite application, SAP NetWeaver application , or SAP Solution
Manager system before you continue with this installation guide.

SAP Notes for the Installation [page 16]

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

New Features [page 18]

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
About this Document PUBLIC 11
2.1 SAP Products Based on SAP NetWeaver 7.3 EHP1 to 7.52
Supported for Installation Using Software Provisioning
Manager 1.0

Here you can find a list of the SAP products based on SAP NetWeaver 7.3 EHP1 to 7.52 ABAP that are supported
for installation using Software Provisioning Manager 1.0, on the specific operating system and database
combination described in this guide.

SAP Product Based on the following SAP NetWeaver Release

SAP Business Suite 7i 2016: SAP NetWeaver 7.5

● EHP4 for SAP CRM 7.0 ABAP SAP NetWeaver 7.4 Support Release 2
● EHP8 for SAP ERP 6.0 ABAP
SAP NetWeaver 7.3 EHP1
● EHP8 for SAP ERP 6.0 ABAP including SAP S/4HANA
Finance 1605 SP03
● EHP4 for SAP SRM 7.0 ABAP
● EHP4 for SAP SCM 7.0 ABAP

SAP Business Suite 7i 2013 Support Release 2: SAP NetWeaver 7.5

● EHP3 for SAP CRM 7.0 ABAP Support Release 2 SAP NetWeaver 7.4 Support Release 2
● EHP7 for SAP ERP 6.0 ABAP Support Release 2
SAP NetWeaver 7.3 EHP1
● EHP7 for SAP ERP 6.0 ABAP including SAP Simple Fi­
nance 1.0 / 1503
● EHP3 for SAP SRM 7.0 ABAP Support Release 2
● EHP3 for SAP SCM 7.0 ABAP Support Release 2

SAP NetWeaver 7.5 SAP NetWeaver 7.5

SAP Solution Manager 7.2 Support Release 2 SAP NetWeaver 7.4 Support Release 2

AS ABAP 7.4, OEM version 1.0 SAP NetWeaver 7.4 Support Release 2

SAP NetWeaver 7.4 Support Release 2 SAP NetWeaver 7.4

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
12 PUBLIC About this Document
 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 103].
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 more information, see SAP Note 1970349 .
For more information, see New Features [page 18].
● “installer” refers to “Software Provisioning Manager”.
● “SAP system” refers to SAP system based on the application server of 7.3 including Enhancement Package
1 / Application Server ABAP 7.4 / SAP NetWeaver 7.4 / SAP NetWeaver 7.5 / SAP NetWeaver Application
Server for ABAP 7.51 innovation package / SAP NetWeaver Application Server for ABAP 7.52 .
● “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”.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
About this Document PUBLIC 13
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

SAP products based on SAP NetWeaver 7.10 to 7.40 SR1 (with the exception of SAP Solution Manager 7.2
ABAP, which will continue to be supported ) are only supported in mainstream maintenance 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 .
The guide set attached to SAP Note 2980160 covers only the SAP product versions which have reached
end of maintenance.

● The Dual Stack option, which integrates an AS ABAP and AS Java in a single system (common System ID
<SAPSID>, common startup framework, common database), is no longer supported in SAP systems based
on SAP NetWeaver 7.5. So if you want to install a new SAP NetWeaver 7.5 Process Integration (PI) system
which is based on SAP NetWeaver 7.5, do not use the documentation Installation Guide - SAP Systems
Based on the Application Server ABAP+Java of SAP NetWeaver on <OS>: <DB>. Instead, use the
Installation Guide - SAP Systems Based on the Application Server ABAP of SAP NetWeaver on <OS>: <DB>
to install the ABAP stack with its own <SAPSID> and the Installation Guide - SAP Systems Based on the
Application Server Java of SAP NetWeaver on <OS>: <DB> to install the Java stack with its own <SAPSID>.
For more information, see the implementation sequence in the Master Guide - SAP NetWeaver 7.5 at http://
help.sap.com/netweaver <Release> Installation and Upgrade .
● 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 12] 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.5 - a complete new system installation from scratch is only provided for the
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.
● Client 066 is no longer available in newly installed SAP systems based on SAP NetWeaver 7.5 or higher. For
more information, see SAP Note 1749142 .
● Client 001 is no longer available in newly installed SAP systems based on SAP S/4HANA and SAP BW/
4HANA.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
14 PUBLIC About this Document
2.4 Before You Start

Make sure that you have read the release-specific “Master Guide” - called “Installation Guide” for SAP S/
4HANA - for your SAP Business Suite application, SAP NetWeaver application , or SAP Solution Manager
system before you continue with this installation guide.

The “Master Guide” - also called “Installation Guide” for SAP S/4HANA - 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” - or “Installation 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

Installation Guide – SAP S/4HANA <Release>

https://help.sap.com/s4hana

<Release> Product Documentation Installation Guide

Master Guide - SAP BW/4HANA https://help.sap.com/viewer/p/SAP_BW4HANA

Installation and Upgrade

Master Guide – SAP NetWeaver AS for ABAP 7.52 http://help.sap.com/nw752abap

Installation and Upgrade

Master Guide – SAP NetWeaver AS for ABAP 7.51 http://help.sap.com/nw751abap

innovation package
Installation and Upgrade

Master Guide – SAP NetWeaver 7.5 http://help.sap.com/nw75

Installation and Upgrade

Master Guide – SAP Solution Manager 7.2 http://help.sap.com/solutionmanager

7.2 <SP> Installation and Upgrade

Master Guide SAP Supply Chain Management 7.0 http://help.sap.com/scm

<Including SAP Enhancement Package
<Number> Powered by SAP NetWeaver <Release> Installation and Upgrade

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
About this Document PUBLIC 15
Document Internet Address

Master Guide (Including Upgrade Information) - http://help.sap.com/crm

SAP Customer Relationship Management 7.0
<Including SAP Enhancement Package <Release> Installation and Upgrade
<Number>

Master Guide (Including Upgrade Information) - http://help.sap.com/srm

SAP Supplier Relationship Management 7.0
<Including SAP Enhancement Package <Release> Installation and Upgrade
<Number>

Master Guide - SAP Enhancement Package http://help.sap.com/erp

<Number> for SAP ERP 6.0
<Release> Installation and Upgrade

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

SAP NetWeaver 7.3
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

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

1751271 Inst. SAP Sys. Based on SAP NetWeaver 7.3 Platform-specific information about the SAP sys­
and higher: SAP HANA DB, IBM i tem installation and corrections to this documen­
tation

1830427 Installation of SCM on HANA with integrated This SAP Note contains information that is spe­
liveCache cific to the SAP system installation of SCM on
HANA with integrated liveCache

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
16 PUBLIC About this Document
 SAP Note Number Title Description

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

819722 Support Package levels for SRM installations/ Information about the ABAP Support Package
upgrades levels and kernel patch levels contained in the
current SAP SRM release

774615 Support Package levels of ERP/ECC installa­ Information about the ABAP Support Package
tions/upgrades levels and kernel patch levels contained in the
current SAP ERP release

837413 Support Package levels for CRM installations/ Information about the ABAP Support Package
upgrades levels and kernel patch levels contained in the
current SAP CRM release

850038 Support Package levels for SCM/APO installa­ Information about the ABAP Support Package
tions/upgrades levels and kernel patch levels contained in the
current SAP SCM 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.

1514967 SAP HANA: Central Note SAP HANA: Central Note

2021789 SAP HANA Revision and Maintenance Strategy SAP HANA Revision and Maintenance Strategy

1523337 SAP HANA Database: Central Note SAP HANA Database: Central Note

1793345 Sizing for SAP Suite on HANA Sizing for SAP Suite on HANA

1872170 Suite on HANA Memory Sizing Suite on HANA Memory Sizing

2235581 SAP HANA: Supported Operating Systems, SAP HANA: Supported Operating Systems, con­
contains related SAP Notes for recommended tains related SAP Notes for recommended OS
OS settings for supported Linux releases settings for supported Linux releases

886535 Downloading multispanning archives Downloading multispanning archives

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
About this Document PUBLIC 17
2.6 New Features

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

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

Feature Description Availability

Software Provision­ The new OS release IBM i 7.5 is certified for SAP Solutions since Software Provisioning Manager
ing Manager on IBM May 30, 2022. For more information, see the SAP on IBM i blog 1.0 SP35 (SL Toolset 1.0 SP35)
i now supports the entry "SAP on IBM i: IBM i 7.5 Certified for SAP Solutions ". In ad­
new OS release IBM dition, see SAP Note 1680045 , section Planning and Prepara­
i 7.5 tion : SAP System Installation on OS release IBM i V7R5.

Switch from Kernel 7.21 has reached end of maintenance. In addition, some is­ Software Provisioning Manager
7.21_EXT Kernel to 1.0 SP31 (SL Toolset 1.0 SP31)
sues have been fixed with the new 7.22_EXT kernel media.
7.22_EXT Kernel

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

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

Support of SAP Software Provisioning Manager 1.0 supports SAP HANA SSL Cer­ Software Provisioning Manager
HANA SSL Certifi- 1.0 SP29 (SL Toolset 1.0 SP29)
tificates for configuring secure access to the SAP HANA data­
cates
base.

For more information, see Establishing Secure Connection to the

SAP HANA Database [page 100].

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 SAP HANA-Specific Pro­
library cedure. In addition, the SAP Uninstall now supports the option to
leave the SAP database library(ies) when the entire SAP system is
deleted. For more information, see Uninstalling an SAP System or
Single Instances [page 206] .

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
18 PUBLIC About this Document
 Feature Description Availability

Support of Secure Software Provisioning Manager 1.0 supports configuring the SAP Software Provisioning Manager
Connection to SAP 1.0 SP26 (SL Toolset 1.0 SP26)
system to be installed to access the SAP HANA database using
HANA database.
encryption.

For more information, see Establishing Secure Connection to the

SAP HANA Database [page 100].

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

New Installer Option If you perform an installation using a stack configuration file, you Software Provisioning Manager
Download Software can now download media according to a Maintenance Plan. For 1.0 SP23 (SL Toolset 1.0 SP23)
Packages for more information, see Installation Using a Stack Configuration
Maintenance File [page 37] , Downloading Software Packages for a Mainte­
Planner Transaction nance Planner Transaction [page 112], and https://
blogs.sap.com/2018/06/01/software-provisioning-manager-
new-option-for-standalone-download-service/ .

Validity Check for If you perform an installation using a stack configuration file and Software Provisioning Manager
1.0 SP23 (SL Toolset 1.0 SP23)
SUM*.SAR Archive choose to extract the SUM*.SAR archive, the validity of this ar­
chive is now checked by the installer. For more information , see
entry Extract the SUM*.SAR Archive in Additional Parameters
When Using a Stack Configuration File [page 61].

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

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

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
About this Document PUBLIC 19
Feature Description Availability

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 Archive [page 108]

 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 125].

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

103] and Running the Installer [page 127].

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

Simplified Addi­ During an additional application server installation, SAP kernel ar­ Software Provisioning Manager
tional Application chives are only prompted if they cannot be retrieved from the pri­ 1.0 SP21 (SL Toolset 1.0 SP21)
Server Instance In­ mary application server instance of the existing SAP system. For
stallation more information, see Preparing the Installation Media [page
103].

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
20 PUBLIC About this Document
 Feature Description Availability

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
more information, see SAP Note 2472835 . 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 Archive [page 108]

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

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

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

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

In addition, check SAP Note 1680045 whether additional infor­

mation is available.

Archive-based Lan­ If you perform an installation using a stack configuration file, you Software Provisioning Manager
guage Installation can now add language archives to the download basket and use 1.0 SP19 (SL Toolset 1.0 SP19)
them for language installation. This feature is currently restricted
to the latest products only. For more information, see Additional
Parameters When Using a Stack Configuration File [page 61]

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
About this Document PUBLIC 21
Feature Description Availability

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

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.

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

● After upgrading to SAP NetWeaver 7.5 PI, you first have to

split the still existing dual stack-system before you can use
SAP NetWeaver 7.5 PI productively.
For more information, see the Upgrade Master Guide - SAP

NetWeaver 7.5 at: http://help.sap.com/nw75 Installation

and Upgrade
● SAP NetWeaver 7.5 is Unicode only
● The primary application server instance directory has been
renamed from /usr/sap/<SAPSID>/
DVEBMGS<Instance_Number> to /usr/sap/<SAPSID>/
D<Instance_Number>.
For more information, see SAP Directories [page 72].
● Declustering and depooling of tables during the installation is
enabled by default. For more information, see SAP Note
1892354 .

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
22 PUBLIC About this Document
 Feature Description Availability

System Provisioning All system provisioning tasks (installation, system copy, system Software Provisioning Manager
for SAP Solution rename) are available for the new SAP Solution Manager 7.2 re­ 1.0 SP09 (SL Toolset 1.0 SP15)
Manager 7.2 lease. Compared to previous SAP Solution Manager releases, SAP
Solution Manager 7.2 is no longer provided as a classical dual-
stack system (ABAP system with Java Add-in), but consists of a
separate ABAP and Java stack.

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.

Installation Using a You can start the installer using a stack configuration file gener­ Software Provisioning Manager
Stack Configuration ated by the Maintenance Planner. The configuration parameters 1.0 SP07 (SL Toolset 1.0 SP12)
File in this file can then be used by the installer to improve the integra­
tion with SUM and to simplify the process of installation for a new
system on target software level.

For more information, see Installation Using a Stack Configuration

File (Optional) [page 37].

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
About this Document PUBLIC 23
Feature Description Availability

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

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
24 PUBLIC About this Document
3 Installation Options Covered by this
Guide

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.

 Note

Regardless of whether you are installing a standard, distributed, or high-availability system, the SAP HANA
database is normally installed on a dedicated database server. It is normally pre-installed by SAP partners
before you start the installation of the SAP system instances. During the installation of the SAP system,
SoftwareProvisioning Manager (the “installer”) accesses the SAP HANA database remotely to perform the
necessary database-specific installation steps.

For more information about how to install the SAP HANA database, see the SAP HANA Server Installation
and Update Guide at https://help.sap.com/hana_platform Implement Installation and Upgrade .

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

Standard System [page 25]

Distributed System [page 26]

High-Availability System [page 27]

Additional Application Server Instance [page 29]

ASCS Instance with Integrated SAP Web Dispatcher [page 32]

ASCS Instance with Integrated Gateway [page 34]

3.1 Standard System

In a standard system, all main instances except the SAP HANA database instance 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 32].
○ Optionally, you can install the ASCS instance with an integrated gateway. For more information, see
ASCS Instance with Integrated Gateway [page 34].
● SAP HANA database instance (DB)
● Primary application server instance (PAS instance)

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Installation Options Covered by this Guide PUBLIC 25
 Standard ABAP System

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:

● 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 32].
○ Optionally, you can install the ASCS instance with an integrated gateway. For more information, see
ASCS Instance with Integrated Gateway [page 34].
● SAP HANA database instance (DB)
The ABAP stack uses its own database schema in the database.
● Primary application server instance (PAS)

The graphics below assume that you use the global directories of the ASCS instance as global file system. That
means that the host with the ASCS instance 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 29].

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
26 PUBLIC Installation Options Covered by this Guide
 Distributed ABAP System

3.3 High-Availability System

 Note

SAP HANA can also have HA solutions. For more information contact your hardware partner and see the
SAP HANA overview in the SAP HANA Data Center, which is available at http://www.saphana.com/docs/
DOC-2010 .

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

 Note

ASCS instance with “Standalone Enqueue Server” versus ASCS instance with new “Standalone
Enqueue Server 2”: Software Provisioning Manager 1.0 installs the “Standalone Enqueue Server” by
default for all SAP system releases in the ASCS instance. However, if you have installed the ASCS
instance for an SAP system based on SAP NetWeaver AS for ABAP 7.52, you can switch to the new
“Standalone Enqueue Server 2” after the installation has completed. For more information, see
https://help.sap.com/nw752abap Application Help SAP NetWeaver Library: Function-Oriented
View SAP NetWeaver Application Server for ABAP Components of SAP NetWeaver Application
Server for ABAP Standalone Enqueue Server 2 High Availability with Standalone Enqueue Server

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Installation Options Covered by this Guide PUBLIC 27
 2 , and Systems Based on SAP NetWeaver AS for ABAP 7.52 only: Switching to Standalone Enqueue
Server 2 and Enqueue Replicator 2 [page 168] .

○ 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 32].
○ Optionally you can install the ASCS instance with an integrated gateway. For more information, see
ASCS Instance with Integrated Gateway [page 34].
● 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.

 Note

ERS instance with “Enqueue Replication Server” versus ERS instance with new “Enqueue
Replicator 2”: Software Provisioning Manager 1.0 installs the ERS instance with the classic “Enqueue
Replication Server” by default for all SAP system releases. However, if you have installed the ERS
instance for an SAP system based on SAP NetWeaver AS for ABAP 7.52, you can switch to “ Enqueue
Replicator 2” after the installation has completed. For more information, see https://help.sap.com/
nw752abap Application Help SAP NetWeaver Library: Function-Oriented View SAP NetWeaver
Application Server for ABAP Components of SAP NetWeaver Application Server for ABAP
Standalone Enqueue Server 2 , and Systems Based on SAP NetWeaver AS for ABAP 7.52 only:
Switching to Standalone Enqueue Server 2 and Enqueue Replicator 2 [page 168].

● SAP HANA database instance (DB)

● Primary application server instance (PAS)

The graphics below each assumes that you run the ASCS instance and the ERS instance 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 the ASCS instance in a switchover cluster infrastructure.

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

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
28 PUBLIC Installation Options Covered by this Guide
 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

Additional Application Server Instance for a Standard System

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 where the primary application server instance
runs
● On dedicated hosts

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Installation Options Covered by this Guide PUBLIC 29
 Additional Application Server for a Standard System

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

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 ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
30 PUBLIC Installation Options Covered by this Guide
 Additional Application Server Instance for a Distributed System

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

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Installation Options Covered by this Guide PUBLIC 31
 Additional Application Server Instance for a High-Availability System

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

3.5 ASCS Instance with Integrated SAP Web Dispatcher

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.

 Recommendation

The integrated SAP Web Dispatcher is subject to a number of limitations. For more information, see SAP
Note 3115889 . It is a convenience option for small systems, but is not recommended for production
systems. The general recommendation is to install a standalone SAP Web Dispatcher instead.

 Note

We only recommend this option for special scenarios. For more information, see SAP Note 908097 . The
integrated SAP Web Dispatcher is subject to a number of limitations. For more information, see SAP Note
3115889 . It is a convenient option for small systems, but is not recommended for production systems.
The general recommendation is to install a standalone SAP Web Dispatcher instead. 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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
32 PUBLIC Installation Options Covered by this Guide
 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 “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 Installation of Installation of SAP Web Dispatcher for
SAP Systems Based on SAP NetWeaver 7.0 to 7.52 on <OS> which you can find at https://help.sap.com/
viewer/swpm10guides/ Installation Option of Software Provisioning Manager 1.0 Installation Option of
Software Provisioning Manager 1.0 Installation Guides - Standalone Engines and Clients - Software
Provisioning Manager 1.0 SAP Web Dispatcher .

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Installation Options Covered by this Guide PUBLIC 33
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 7.3 including Enhancement Package

Application Help Function-Oriented View Application
1
Server Application Server Infrastructure Components of
http://help.sap.com/nw731
SAP NetWeaver Application Server SAP Web Dispatcher
● SAP NetWeaver 7.4
http://help.sap.com/nw74
● SAP NetWeaver 7.5
http://help.sap.com/nw75
● SAP NetWeaver Application Server for ABAP 7.51
innovation package
https://help.sap.com/nw751abap
SAP NetWeaver AS for ABAP 7.52
https://help.sap.com/nw752abap

Related Information

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

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

 Note

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
34 PUBLIC Installation Options Covered by this Guide
 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 7.1 to 7.5x at
https://help.sap.com/viewer/swpm10guides/ Installation Option of Software Provisioning Manager 1.0
Installation Guides - Standalone Engines and Clients - Software Provisioning Manager 1.0 Standalone Gateway
Instance .

Related Information

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Installation Options Covered by this Guide PUBLIC 35
4 Planning

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 15] .
2. You have decided on your installation option (see Installation Options Covered by this Guide [page 25]).

Standard, Distributed, or High-Availability System

 Note

In a standard system [page 25], all mandatory instances except the database instance are normally
installed on one host. Therefore, if you are installing a standard system, you can ignore references to other
hosts.

The SAP HANA database is normally pre-installed by SAP partners before you start the installation. For
more information about how to install the SAP HANA database, see the SAP HANA Server Installation and
Update Guide at https://help.sap.com/hana_platform Implement Installation and Upgrade . The
database instance is remotely installed by SoftwareProvisioning Manager (the “installer”) from the primary
application server host.

1. If you want to install an SAP ABAP system along with the required Support Package stack and ABAP Add-
Ons in one implementation run, you need to plan the desired installation target using the maintenance
planner at https://apps.support.sap.com/sap/support/mp .
In the maintenance planner, a stack XML file with the desired Support Package stack and Add-On
information is generated, which you then hand over to Software Provisioning Manager (the “installer” for
short) by calling it with command line parameter
SAPINST_STACK_XML=<Absolute_Path_To_Stack_XML_File>. Included constraints and defaults
defined in the stack XML file are then used for the initial installation by Software Provisioning Manager and
for the application of Support Package stacks and Add-Ons by the Software Update Manager (SUM).
For more information, see Installation Using a Stack Configuration File (Optional) [page 37].

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
36 PUBLIC Planning
  Recommendation

We recommend that you perform the installation using a stack configuration file for all new products
such as SAP S/4HANASAP on Premise.

2. You check the hardware and software requirements [page 39] on every installation host.
3. You plan how to set up user and access management [page 47].
4. You identify Basic SAP System Installation Parameters [page 47].
5. You decide on the transport host to use [page 64].
6. You decide whether you want to integrate LDAP Directory Services in your SAP system [page 186].
7. Optionally, you decide whether you want to install multiple SAP systems on a single host [page 190].
8. Continue with Preparation [page 69].

Additional Application Server Instance

1. You check the hardware and software requirements [page 39] for every installation host on which you
want to install one or more additional application server instances.
2. You identify Basic SAP System Installation Parameters [page 47].
3. Continue with Preparation [page 69].

4.2 Installation Using a Stack Configuration File

The option to perform an installation using a stack configuration file (also called “up-to-date installation” or
“UDI” for short) improves the process of provisioning an up-to-date SAP system by creating a unified
consumption experience and a direct close collaboration between the involved tools, namely:

● The Maintenance Planner

● Software Provisioning Manager (the “installer” for short)
● Software Update Manager (abbreviated as “SUM”)

The installer then can take over more default settings that are already predefined in the Maintenance Planner.

 Recommendation

We recommend that you perform the installation using a stack configuration file for new products, such as
SAP S/4HANA or SAP Solution Manager 7.2.

 Note

During Maintenace Planner stack generation, SAP HANA and non-SAP HANA SUM archives are provided.
Exclude the SUM archive which is not applicable for the new system planning from the stack generation.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Planning PUBLIC 37
Restrictions

You cannot perform a target system installation in the context of a system copy as an installation with a stack
configuration file.

Prerequisites

● You must have an S-User with the authorization to access and use the Maintenance Planner at https://
apps.support.sap.com/sap/support/mp .
● For additional information about involved tools and supported SAP system releases, see SAP Note 2277574
.

Features

An installation using a stack configuration file provides the following features:

● You can use a stack configuration file generated by the Maintenance Planner at https://
apps.support.sap.com/sap/support/mp . The parameters contained in the stack configuration file can
then be processed by the installer to get better integrated with SUM and to simplify the process of
installation for a new system on a target software level. This makes IT administration easier by reducing the
efforts in Total Cost of Ownership (TCO). For more information, see the Best Practice Guide to Planning
Landscape Changes at https://support.sap.com/en/tools/software-logistics-tools/landscape-
management-process.html .
● When processing a stack configuration file, the installer can take over more default settings that are
already predefined in the Maintenance Planner and offers more possibilities for automation as compared
to when running without it. For more information about the benefits by comparing the existing process with
the new improved process, see Up-To-Date Installation at https://blogs.sap.com/2016/10/21/up-to-date-
installation-2/ .

 Note

The procedure and the screenshots provided in the linked document are only an example to show how
an up-to-date installation works in general for an example SAP product, and what the benefits are. This
document is not intended to serve as a detailed instruction for an up-to-date-installation of any
supported SAP product.

● You can also run an installation using a stack configuration file in unattended mode as described in
System Provisioning Using an Input Parameter File [page 134] .
● You can use the installer to directly download the installation software from SAP by providing the
Maintenance Plan to the installer while running installer option Download Software Packages for
Maintenance Planner Transaction.
For more information, see Downloading Software Packages for a Maintenance Planner Transaction [page
112].

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
38 PUBLIC Planning
Integration

For the additional input parameters that you need to specify, see Additional Parameters When Using a Stack
Configuration File (Optional). You can find the link to this section in Related Information below.

In addition, each section in this guide describing steps that are completely or at least partially automatized
when using a stack configuration files is marked with an appropriate note at the beginning. These are the
following sections as listed in the adjacent section Related Information:

Related Information

Additional Parameters When Using a Stack Configuration File [page 61]

Downloading Software Packages for a Maintenance Planner Transaction [page 112]
Running the Installer [page 127]
Configuring the Change and Transport System [page 160]
Applying the Latest Kernel and Support Package Stacks [page 164]
Installing Additional Languages and Performing Language Transport [page 169]

4.3 Hardware and Software Requirements

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.

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 40].
○ Integrated in the installation tool (mandatory) as part of the installation process

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Planning PUBLIC 39
 For more information, see Running the Installer [page 127].
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

4.3.1 Running the Prerequisites Check in Standalone Mode

(Optional)

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 Archive [page 108] .
2. Make either the separate SAPEXE<Version>.SAR archive or the complete kernel medium available as
described in Preparing the Installation Media [page 103] .
3. Start the installer as described in Running the Installer [page 127].

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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
40 PUBLIC Planning
  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.

Results

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 Archive [page 108]
Preparing the Installation Media [page 103]

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.

Related Information

General Installation Information for Your Operating System [page 42]

Hardware Requirements [page 42]
Software Requirements [page 44]
Other Requirements [page 46]

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Planning PUBLIC 41
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.

4.3.2.2 Hardware Requirements

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 103].
○ 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 109] .
○ 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.
● ○ Additional application server instance:
Minimum 2 GB (SAP NetWeaver BW server: Minimum 30 GB)
○ SAP Host Agent:
Minimum 0.5 GB

RAM 5 GB

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
42 PUBLIC Planning
 Requirement Values and Activities

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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Planning PUBLIC 43
4.3.2.3 Software Requirements

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 NetWeaver7.3 EHP1 and 7.4 are released for V7R1,
V7R2, V7R3, V7R4, and V7R5.

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

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

For more information about V7R5, see SAP Note 3152440 .

Required PTF List

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

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

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

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

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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
44 PUBLIC Planning
 Requirement Values and Activities

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,V7R4, and V7R5)

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Planning PUBLIC 45
4.3.2.4 Other Requirements

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.

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 .

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

For more information, see SAP Note 202227 .

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

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

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
46 PUBLIC Planning
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.

Before you add a newly installed SAP system to your system landscape, you must decide which kind of user
management you want to use:

● Central User Administration (CUA)

● An LDAP directory as the data source for user data

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

More Information

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 7.3 including Enhancement Package

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

● SAP NetWeaver 7.5 Services LDAP Connector

http://help.sap.com/nw75
● SAP NetWeaver Application Server for ABAP 7.51
innovation package
https://help.sap.com/nw751abap
● SAP NetWeaver AS for ABAP 7.52
https://help.sap.com/nw752abap

4.5 Basic Installation Parameters

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Planning PUBLIC 47
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 32], you must
choose Custom. Otherwise, you are not prompted for the SAP Web Dispatcher installation parameters
[page 63] during the Define Parameters phase of the ASCS instance installation.
● If you want to install an ASCS instance with an integrated Gateway [page 34], you must choose
Custom. Otherwise, you are not prompted for the SAP Gateway installation during the Define
Parameters phase of the ASCS instance installation.

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

SAP System Database Parameters [page 58]
Additional Parameters when Installing SAP Process Integration 7.5 or SAP Solution Manager 7.2 [page 60]
Additional Parameters When Using a Stack Configuration File [page 61]
Parameters for Additional Components to be Included in the ASCS Instance [page 63]

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
48 PUBLIC Planning
4.5.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.

SAP systems based on SAP NetWeaver 7.5 or higher are Unicode only.

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Planning PUBLIC 49
Parameter Description

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

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

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

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

SAP Process If you want to install the primary application server instance of the Java system on a host different from
Integration (PI) the host of the primary application server instance of the ABAP system, then you must specify the host
7.5, SAP Solu­ of the Java primary application server instance during the Define Parameters phase of the primary appli­
tion Manager cation server instance installation of the ABAP system.
7.2:
This is to set up the connection between the ABAP and the Java system.
Application
Server Gateway
Communication
Setup

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
50 PUBLIC Planning
 Parameter Description

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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Planning PUBLIC 51
Parameter Description

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.

● Secure Store key phrase
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 83] .

Additional restrictions depending on SAP HANA database:

● It must consist of at least one number, one lowercase letter, and one uppercase letter.
● It can only contain the following characters: _, a-z, A-Z, 0-9, #, @, $, ! and must not start with a
number or an underscore ( _ ).

Depending on the installation option, additional restrictions may apply.

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
52 PUBLIC Planning
 Parameter Description

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

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­ http://help.sap.com/nw75
age https://help.sap.com/nw751abap
https://help.sap.com/nw752abap

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

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
http://help.sap.com/nw75
https://help.sap.com/nw751abap
https://help.sap.com/nw752abap

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Planning PUBLIC 53
Parameter Description

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
54 PUBLIC Planning
Ports

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 .

Operating System Users

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

 Note
and in the Java system.
This user is only created during the installation of the
application server ABAP for an SAP NetWeaver 7.5 Proc­ The installer sets the user name J2EE_ADMIN and the mas­
ess Integration (PI) system or for an SAP Solution Man­ ter password by default.
ager 7.2 system.
If required, you can choose another user name and pass­
word according to your requirements.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Planning PUBLIC 55
Parameter Definition

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­
 Note ing for approval. Guest users belong to the default group
This user is only created during the installation of the Authenticated Users.
application server ABAP for an SAP NetWeaver 7.5 Proc­
The installer creates this user in the ABAP system.
ess Integration (PI) system or for an SAP Solution Man­
ager 7.2 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

 Note
the Java system
This user is only created during the installation of the
application server ABAP for an SAP NetWeaver 7.5 Proc­ This user is used for the communication between the ABAP
ess Integration (PI) system or for an SAP Solution Man­ system and the Java system.
ager 7.2 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 .

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
56 PUBLIC Planning
System Landscape Directory

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

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Planning PUBLIC 57
4.5.2 SAP System Database Parameters

Parameters Description

SYSTEM_ID
The SYSTEM_ID identifies the database instance.

This is the result of the following query:

select SYSTEM_ID from M_DATABASE

If your SAP HANA SYSTEM_ID is the same as the chosen SAP System ID
<SAPSID>, there are following restrictions:

● The ABAP system and SAP HANA database have to be installed on dif­
ferent hosts
● Database installation has to done on the ABAP host. Otherwise Data­
base installation procedure with Software Provisioning Manager
(the“ installer”) could overwrite the environment files (sapenv.*) of
the SAP HANA database and the database will not start any more after
reboot.

DATABASE_NAME, Database ID, <DBSID> The <DBSID> identifies the tenant database. This is the result of the follow­
ing query:

select DATABASE_NAME from M_DATABASE

If your database is a single database, then the DATABASE_NAME equals

the SYSTEM_ID.

Database schema The ABAP database schema is named SAP<SCHEMA_ID>. Default value:
SAPABAP1. You can either accept this default or enter another value accord­
ing to your needs.

 Recommendation
Do not choose a value that contains the <SAPSID> of your system.
Keep in mind that you cannot change the schema name retrospec­
tively. Therefore, if you change the <SAPSID> by performing a system
rename or a system copy, the schema name always remains the same
as the original one you assigned during the installation.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
58 PUBLIC Planning
 Parameters Description

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

You can assign virtual host names to the SAP HANA database instance by
starting the installer with the SAPINST_USE_HOSTNAME property. For
more information, see Running the Installer [page 127].

After the installation has completed, all application servers can use this vir­
tual host name to connect to the SAP HANA database instance. The virtual
host name is also a global host name. If you do not provide the virtual host
name, the instance is installed automatically using 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 infor­
mation, see Using Virtual Host Names [page 78].

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

Configuration of SAP liveCache withSAP Select Install SAP liveCache for SAP System if you want to configure SAP
HANA liveCache for your SAP System. You need the SAP liveCache installation
only when at least one of your applications uses it.

● Select Use SAP liveCache integrated in SAP HANA if you want your SAP
liveCache in the SAP HANA database instance. To configure it, SAP
liveCache integrated in SAP HANA (also called LCAPPS- or liveCache
Applications plugin) must be pre-installed in an existing HANA data­
base. For more information about how to install LCAPPS, see SAP Note
2979266 .For more information about SAP liveCache on SAP HANA
requirements, see the SAP HANA Master Guide at: http://

help.sap.com/hana_platform Implement Installation and

Upgrade
● Select Use external SAP liveCache based on SAP MaxDB technology if
you want to run SAP liveCache as a separate SAP MaxDB database in­
stance. This is not supported with S/4 HANA installations.
For more information about SAP MaxDB liveCache Technology require­
ments, see the SAP MaxDB liveCache Technology installation guide at:

https://help.sap.com/viewer/swpm10guides Installation Option of

Software Provisioning Manager 1.0 Installation Guides

Standalone Engines and Clients Software Provisioning Manager 1.0

SAP MaxDB liveCache Technology

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Planning PUBLIC 59
4.5.3 Additional Parameters when Installing SAP Process
Integration 7.5 or SAP Solution Manager 7.2

The parameters in this section are only required if you want to install SAP Process Integration 7.5 or SAP
Solution Manager 7.2.

Parameter Description

Communication Port for ABAP For a secure communication of connected SAP systems to the
ABAP stack you have to define the HTTPS port that is to be con­
figured in the application server instance profile. Further post-in­
stallation steps [page 168] are required to fully enable HTTPS
communication. For more information about HTTPS enable­
ment, see SAP Note 510007 .

In addition you can configure an HTTP port. However, this is not

recommended for productive SAP systems due to security rea­
sons.

 Recommendation
If you are about to install an SAP NetWeaver 7.5 Process In­
tegration system and you intend to run automated configu-
ration using the Central Technical Configuration (CTC) Wiz­
ard after the installation, it is strongly recommended that
you configure the ABAP communication port for ABAP al­
ready during the installation process, because you can only
run the CTC Wizard if the ABAP port is either completely
configured for HTTPS or optionally for HTTP. For more infor­
mation, see PI: Configuring the Process Integration System
After the Installation in Installation of SAP Systems Based on
the Application Server Java of SAP NetWeaver 7.5 and SAP
Solution Manager 7.2 SR2 Java on : <Database>.

Application Server Gateway Communication Setup If you want to install the primary application server instance of
the Java system on a host different from the host of the primary
application server instance of the ABAP system, then you must
specify the host of the Java primary application server instance
during the Define Parameters phase of the primary application
server instance installation of the ABAP system.

This is to set up the connection between the ABAP and the Java
system.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
60 PUBLIC Planning
4.5.4 Additional Parameters When Using a Stack
Configuration File

The parameters in this section are only required if you use a stack configuration file generated from the
Maintenance Planner.

Parameter Description

Transport Domain The ABAP Transport Management System (TMS) must be configured
before ABAP correction packages can be applied. You can also run the
configuration or even reconfigure the TMS after the installation has fin-
ished.

To be able to transport changes between the SAP systems in your sys­

tem landscape, you need to configure the Transport Management Sys­
tem (TMS) for all SAP systems in your system landscape and configure
one transport domain controller. To start the TMS in your ABAP system
for later reconfiguration, call transaction STMS. At least one transport
landscape with this system as transport domain controller is required
before you can apply corrections, support packages, or upgrades to the
SAP system.

The name of the Transport Domain must not contain blank characters.
You cannot change the name afterwards without reconfiguring the
transport domain controller and thereby the entire Transport Domain.

By default use DOMAIN_<SAPSID> for the Transport Domain of a single

transport landscape with this system as transport domain controller.

Directory with Transport Files Location of the ABAP transport files that are to be included after the
ABAP load during the installation. All transport files in this directory are
imported with the transport control program (tp).

Location of SPAM/SAINT Update Archive A SPAM/SAINT update contains updates and improvements to the
Support Package Manager (SPAM) and the Add-On Installation Tool
(SAINT). Provide the full path to the SPAM/SAINT update archive.

SPAM/SAINT is delivered with the ABAP load. SAP recommends that

you always use the latest version of SPAM/SAINT before applying Sup­
port Packages.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Planning PUBLIC 61
Parameter Description

Decide whether you want to prepare for the Soft­ With the Software Update Manager (SUM), you can apply support pack­
ware Update Manager run at the end of the instal­ ages stacks at the end of the installation.
lation
● Do not start SUM automatically
● Start SUM automatically at the end of the installation
Choose to start SUM automatically, if you want to have the SUM
STARTUP script called in the default <Update Directory>/SUM/
directory at the end of the installation.

 Note
To make sure you have the latest information about SUM on
IBM i, see SAP Note <SP_Version>- IBM: Additional Informa­
tion Software Update Manager

 Recommendation
On IBM i, we strongly recommend to always keep the SAP Host
Agent version up to date. For more information about how to
update and existing SAP Host Agent, see 1031096 .

Extract the SUM*.SAR Archive If you choose to extract the SUM*.SAR archive, the provided archive is
validated and extracted to the default update directory:

UNIX and IBM i: /usr/sap/<SAPSID>/

SUM HTTP port If you are running several SAP system updates on the same host, you
have to use different port numbers for each update. You can adjust the
default SUM HTTP port by entering the required port number in the
SUM HTTP Port field. When doing so you set the SUM GUI Port number
to (=<HTTP port number+2>). Dependencies See also the Soft­
ware Update Manager documentation at: https://support.sap.com/en/
tools/software-logistics-tools/software-update-manager.html

SUM Batch Input File You can specify a batch file with some default values for the update.
SUM then starts with parameter batchfile=<XML file with
input parameters>.

Enter the full path to the existing batch file.

Placeholders like @PARAMETER_VALUE@ inside the file are replaced by

values known from the installation.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
62 PUBLIC Planning
 Parameter Description

Install Additional SAP System Languages A set of default languages is delivered with the ABAP load. From the lan­
guage media delivered with your product version or - if already provided
by the Maintenance Planner for the respective product - using language
archives, you can select additional languages that you want to have in­
stalled during SAP system installation.

If you want to install additional languages, you must provide the direc­
tory with the additional language packages for the ABAP installation
load, for example with subdirectories like DATA_UNITS/ES.

For more information, see Installation Using a Stack Configuration File (Optional) [page 37].

Related Information

Installation Using a Stack Configuration File [page 37]

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

Parameters Description

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

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:

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Planning PUBLIC 63
Parameters Description

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

ASCS Instance with Integrated Gateway [page 34]

4.6 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.
○ 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 158].

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
64 PUBLIC Planning
More Information

● Setting Up File Systems [page 71]

● See the SAP Library at:

Release SAP Library Path

○ SAP NetWeaver 7.3 including Enhancement

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

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

○ SAP NetWeaver 7.5 Concept
http://help.sap.com/nw75
○ SAP NetWeaver Application Server for
ABAP 7.51 innovation package
https://help.sap.com/nw751abap
○ SAP NetWeaver AS for ABAP 7.52
https://help.sap.com/nw752abap

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

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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Planning PUBLIC 65
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.
● The ERS instance is essential for a high-availability system and should be controlled by the cluster
software. You need one ERS instance for the ASCS instance 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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
66 PUBLIC Planning
The following diagram shows the essential features of a switchover setup:

Switchover Setup with ERS Instance and ASCS Instance in Different Failover Groups (Overview)

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Planning PUBLIC 67
The following diagram shows an example of a switchover setup in more detail:

Switchover Setup with ERS Instance and ASCS Instance in Different Failover Groups (Schematic View)

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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
68 PUBLIC Planning
5 Preparation

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

 Note

In a standard system [page 25], all mandatory instances except the database instance are normally
installed on one host. Therefore, if you are installing a standard system, you can ignore references to other
hosts.

The SAP HANA database is normally pre-installed by SAP partners before you start the installation. For
more information about how to install the SAP HANA database, see the SAP HANA Server Installation and
Update Guide at https://help.sap.com/hana_platform Implement Installation and Upgrade . The
database instance is remotely installed by SoftwareProvisioning Manager (the “installer”) from the primary
application server host.

1. You make sure that the SAP HANA database is installed on the SAP HANA host [page 70].
2. You decide how to set connectivity data for your SAP HANA database [page 71].
3. You set up file systems [page 71] and make sure that the required disk space is available for the
directories to be created during the installation.
4. If you want to use virtual host names, you have to set the environment variable SAPINST_USE_HOSTNAME
[page 78] 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 127].
5. If you want to install a high-availability system, you perform switchover preparations [page 79].
6. You complete the preparation for IBM i [page 79].
7. If you want to share the transport directory [page 158] trans from another system, make this directory
available to your installation hosts.
8. You install the SAP front-end software [page 99] on the desktop of the user.
9. If required, you configure host names for the SAP HANA database [page 100].
10. To establish a secure connection to your SAP HANA, follow the instructions in Establishing Secure
Connection to the SAP HANA Database [page 100].

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Preparation PUBLIC 69
11. You check that the required installation media [page 103] are available for each installation host.
12. You copy the installation media manually to your IBM i [page 116].
13. If you decided to use a generic LDAP directory, you have to create a user for LDAP directory access [page
191].
14. You continue with Installation [page 119].

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 71] 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 78] 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 127].
3. You complete the preparation for IBM i [page 79].
4. If you want to share the transport directory [page 158] trans from another system, make this directory
available to your installation hosts.
5. You install the SAP front-end software [page 99] on the desktop of the user.
6. You check the time zones of the ABAP application server and the SAP HANA system [page 102].
7. You check that the required installation media [page 103] are available on each installation host.
8. You copy the installation media manually to your IBM i [page 116].
9. You continue with Installation [page 119].

5.2 Installing the SAP HANA Database

Make sure that the SAP HANA database has been installed before you start the SAP system installation.

For more information about how to install the SAP HANA database, see the SAP HANA Server Installation and
Update Guide at https://help.sap.com/hana_platform Implement Installation and Upgrade .

The SAP HANA database is normally part of the SAP HANA appliance. It is normally pre-installed by SAP
partners before you start the installation using Software Provisioning Manager (the “installer”). The installer
accesses the SAP HANA database remotely to perform the necessary database-specific installation steps.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
70 PUBLIC Preparation
5.3 Setting Connectivity Data for the SAP HANA Database

An SAP ABAP system needs connectivity data to log on to the SAP HANA database. This section describes
methods for setting up connectivity data.

For SAP HANA database, you can set up the connectivity data using the following methods:

● Local hdbuserstore container (default method)

The local hdbuserstore container has always been available with SAP HANA. It is used in all versions of
software provisioning manager. It is the default when you are doing an installation of SAP HANA or a
migration to SAP HANA. One hdbuserstore is created for each host for which you installing an ABAP
instance.
You can trace the connect method of R3trans by checking the log file trans.log.
The disadvantage of this method is that there is one hdbuserstore container on each SAP application
server. This means that, if you want to change the connectivity data, you have to log on to each server of
the system and change the data separately on each server.
To use this method, you need take no further action since it is the default.
● If you want to use virtual host names, you must start the installer with the SAPINST_USE_HOSTNAME
parameter.
For more information, see Running the Installer [page 127].
● ABAP secure storage in the file system (SSFS)
ABAP SSFS is a database-independent method of storing data located inside the SAP system. For more
information, see SAP Note 1639578 . This functionality is available for SAP HANA as of SAP NetWeaver
7.4.
To use this method, you start the installation with the parameter HDB_ABAP_SSFS=YES. For more
information, see Running the Installer [page 127].
Note that only SAP kernel tools can read from ABAP SSFS. This means that SAP HANA client tools such as
hdbsql cannot use ABAP SSFS. Therefore, you might want to choose one application server where you still
maintain one hdbuserstore container.

5.4 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 72]

SAP HANA Database Client Directories [page 78]

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Preparation PUBLIC 71
5.4.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

Directories of the SAP System

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 figures show the directory structure of SAP systems based on SAP NetWeaver 7.5 and the
directory structure of SAP systems based on SAP NetWeaver 7.3 EHP1 to 7.4:

● Directory Structure for an ABAP System Based on SAP NetWeaver 7.5:

In SAP systems based on SAP NetWeaver 7.5 or higher, all application server instances, including the
primary application server instance, are named D<Instance_Number>.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
72 PUBLIC Preparation
 Directory Structure for an ABAP System Based on SAP NetWeaver 7.5 or Higher
● Directory Structure for an ABAP System Based on SAP NetWeaver 7.3 EHP1 to 7.4:
In SAP systems based on SAP NetWeaver 7.3 EHP1 to 7.4 the primary application server instance is named
DVEBMGS<Instance_Number>.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Preparation PUBLIC 73
 Directory Structure for an ABAP System Based on SAP NetWeaver 7.3 EHP1 to 7.4

Every new installation of an ABAP standalone system is 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 , which is the global transport directory. /<sapmnt>/
<SAPSID>.
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
○ profile
Contains the profiles of all instances
○ exe
● 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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
74 PUBLIC Preparation
 For more information about the global transport directory, see Setting Up the Transport Directory [page
158].

Physically Shared SAP Directories

Directory Required Minimum Disk Space

/<sapmnt>/ Minimum 2.5 GB

<SAPSID>

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

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:

○ SAP systems based on SAP NetWeaver 7.3 EHP1 to 7.4:
○ The directory of the primary application server instance is called DVEBMGS<Instance_Number>.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Preparation PUBLIC 75
 ○ The directory of an additional application server instance is called D<Instance_Number>.
○ The directory of an application server instance (primary application server instance and additional
application server instances) is called D<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 the ASCS instance.

Local SAP Directories

Directory Description Required Minimum Disk Space

SAP systems based on SAP NetWeaver 7.3 Primary application server in­ ● SAP Business Warehouse server
EHP1 to 7.4: stance directory only: minimum 25 GB
● Other installations: minimum 4 GB
/usr/sap/<SAPSID>/
DVEBMGS<Instance Number>

SAP systems based on SAP NetWeaver 7.5 or

higher:

/usr/sap/<SAPSID>/D<Instance
Number>

/usr/sap/<SAPSID>/D<Instance Additional application server ● SAP Business Warehouse server

Number> instance directory only: minimum 25 GB
● Other installations: minimum 4 GB

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
76 PUBLIC Preparation
Directories of the SAP Host Agent

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Preparation PUBLIC 77
5.4.2 SAP HANA Database Client Directories

The SAP HANA database client can be installed in one of the following ways:

● As a Local Client Directory:

Then the filepath is /usr/sap/<SAPSID>/hdbclient
● As a Central Client Directory:
Then the filepath is $DIR_CT_RUN/hdbclient. In this case, sapcpe is enabled for the client software.
When the instance is restarted, the client is updated automatically.

For the space required, see the table Hardware Requirements in Hardware and Software Requirements Tables
[page 41].

5.5 Using Virtual Host Names

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

Prerequisites

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

Context

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

Procedure

Proceed as described in SAP Note 1624061 .

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
78 PUBLIC Preparation
5.6 Performing Switchover Preparations for High
Availability

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 78], 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 127].
● 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 49].

Procedure

Assign the virtual IP addresses and host names for the 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.

5.7 Preparation for IBM i

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

● Only valid for 'Software Component': SAP SCM

You install the performance library libperfstat.a for the liveCache [page 80].
End of 'Software Component': SAP SCM

● You check the transport directory [page 80].

● You check Qp2Term, Qp2Shell, and the Portable Application Solution Environment [page 82].
● You install the Qshell [page 82].
● You check and adjust system values [page 83].

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Preparation PUBLIC 79
● You adjust startup program QSTRUP [page 87].
● You configure TCP/IP [page 88].
● You adjust the relational database name [page 95].
● You install English as a secondary language [page 96].
● You prepare the SAP installation user onIBM i [page 97].
● You enable the user QSECOFR [page 98].

5.7.1 Installing the Performance Library libperfstat.a for

liveCache

This topic is only valid for 'Software Component': SAP SCM

If you want to use the liveCache client, you must install the library libperfstat.a on IBM i. To check if this
library already exists, check the path /sapdbas4/lib/libperfstat.a.

For more information, see SAP Note 1081634 .

 Caution

Although the liveCache client is installed automatically, you must install the file libperfstat.a manually.
This is different from the normal software installation process using program temporary fixes (PTFs).

End of 'Software Component': SAP SCM

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
80 PUBLIC Preparation
For more information about the CTS, see the SAP Library at :

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

● SAP NetWeaver 7.3 including Enhancement Package 1

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

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

● SAP NetWeaver Application Server for ABAP 7.51 Concept
innovation package
https://help.sap.com/nw751abap
● SAP NetWeaver AS for ABAP 7.52
https://help.sap.com/nw752abap

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.

Procedure

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 97]. For more information about how to create <SAPSID> users using
CRTSAPUSR, see SAP Note 1123501 .

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Preparation PUBLIC 81
5.7.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.

5.7.4 Installing the Qshell

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
82 PUBLIC Preparation
  Note

For more information about Qshell, see the IBM documentation.

5.7.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
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)

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Preparation PUBLIC 83
● 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.

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
84 PUBLIC Preparation
 System Value Recommended Value Description

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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Preparation PUBLIC 85
System Value Recommended Value Description

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  Note
Database server and application server: In the past the Max Act value had an influ-
ence on the database optimizer, but this has
(number of SAP work processes) * 1.20
changed.

 Caution

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

RMVENVVAR ENVVAR(QIBM_PASE_CCSID) LEVEL(*SYS)

Changing TCP buffer size:

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
86 PUBLIC Preparation
 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

5.7.6 Adjusting Startup Program QSTRUP

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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Preparation PUBLIC 87
  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. Only for Java systems: Start of the DDM-TCP/IP server
4. Automatic creation of directory entries under /QFileSvr.400
5. Start of the subsystem QUSRWRK

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

 Note

In earlier versions of this document, it was advised to also start the EDRSQL server in the startup program.
As of IBM i 7.1 and SAP kernel release 4.6D, this is no longer required . For more information, see SAP Note
1257635 .

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
88 PUBLIC Preparation
  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 .
You must then enter the following information and choose ENTER :
○ System name
○ Local network ID
○ Default local location name
The following screen appears:

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Preparation PUBLIC 89
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.

On the Create Line Desc (Ethernet) (CRTLINETH) screen, make sure the autocreate controller is set to
*yes.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
90 PUBLIC Preparation
 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).

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Preparation PUBLIC 91
 The following screen appears:

You need at least two entries: one for the loopback entry and one for the IP address of your IBM i.
The loopback address always takes the IP address 127.0.0.1, subnet mask 255.0.0.0 and line
description *LOOPBACK.
To add an entry, enter option 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).

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
92 PUBLIC Preparation
 The following screen appears:

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Preparation PUBLIC 93
 The following screen appears:

 Note

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

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

Testing the TCP/IP Connection

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

 Example

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

● ping 'as0008'

● ping 'as0008.wdf.sap.corp'

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

WRKLNK '/QFileSvr.400/<Host_Name>'

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
94 PUBLIC Preparation
Your host name should be displayed under Object link, for example, as0008 for the host in the example given
above.

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

Result

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

5.7.8 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 ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Preparation PUBLIC 95
 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.7.9 Installing English as a Secondary Language

Use

On every IBM i host where English (IBM i language feature code 2924) is not the primary language, you must
install English (feature code 2924) as the secondary language library. This is necessary for the installer on
PASE, which relies on the US English locales en_US, and also it is a prerequisite 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 the following secondary language libraries is displayed, you have
already installed English as a secondary language library: QSYS2924

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

Procedure

1. On the IBM i command line, enter GO LICPGM.

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

 Note

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

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

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

ERROR: Setting native locale failed.

Choose different Locale Environment variables LC_ALL/LC_CTYPE

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
96 PUBLIC Preparation
 You can workaround this issue by setting the environment variable LC_ALL right before you start the
sapinst:

export LC_ALL=POSIX

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

5.7.10 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.
● SCM Only:
The IBM i installation user profile must be the user QSECOFR.

 Note

This is different to other installations on IBM i. For other installations, we recommended that you create
user SAPIUSR. However for SCM, you need to use the user QSECOFR because the liveCache client
software has to be installed by this special user.

Procedure

 Note

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

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

CRTUSRPRF USRPRF(SAPIUSR) PASSWORD(SAP) USRCLS(*SECOFR) TEXT('SAP installation

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

SCM Only: To change the user QSECOFR, enter the following command:

CHGUSRPRF USRPRF(QSECOFR) OWNER(*USRPRF) LANGID(ENU) CNTRYID(US) CCSID(500)

LOCALE(*NONE)

After the installation, you can revert the user profile QSECOFR back to the old values.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Preparation PUBLIC 97
  Caution

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

RMVENVVAR ENVVAR(QIBM_PASE_CCSID) LEVEL(*SYS)

 Note

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

CHGUSRPRF USRPRF(SAPIUSR) GRPPRF(SAPINST)

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.

5.7.11 Enable the User QSECOFR

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

 Note

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

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
98 PUBLIC Preparation
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.8 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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Preparation PUBLIC 99
5.9 Configuring Host Names for the SAP HANA Database

You need to perform this procedure if you want to use virtual host names or if your SAP HANA database is
located in a separate network.

Context

During the Define Parameters phase, the installer prompts you for the parameters to connect to your SAP
HANA database. However, the database host name that you enter is not used for the user store. Instead, the
external host name of the database is determined and subsequently used. If the SAP HANA database was
installed using a virtual host name and you want this host to be used in the user store connection environment,
make sure the host can be resolved from the installation host as well.

Procedure

Make sure that the external host name of the database is correctly maintained.

For more information on how to do this, see SAP Note 1930853 or section Mapping Host Names for
Database Client Access in the SAP HANA Administration Guide, available here:

https://help.sap.com/viewer/p/SAP_HANA_PLATFORM Administration

5.10 Establishing Secure Connection to the SAP HANA

Database

You can establish a secure connection to the SAP HANA database.

You can accomplish this in one of the following ways:

● Use the installer to configure the SAP system instances to use the Transport Layer Secure (TLS)/Secure
Sockets Layer (SSL) protocol to secure connections of to the SAP HANA database.
● Configuring your SAP HANA database to force all clients to use a secured connection and to validate all
client connection.

Prerequisites

For enabling SAP HANA SSL, at least SAP HANA Client 2.0 SPS04 is required. For more information, see SAP
Note 2784500 .

Applying Self-signed Certificates while Running the Installer [page 101]

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
100 PUBLIC Preparation
 The installer can configure the SAP system instances to use the Transport Layer Secure (TLS)/Secure
Sockets Layer (SSL) protocol to secure connections of to the SAP HANA database. Self-signed
certificates are generated to setup the secure environment for your system using the SAP
Cryptographic Library CommonCryptoLib.

Configuring SAP HANA Encryption Parameters [page 101]

Depending on how you have specified parameter sslEnforce, the installer will configure the
connection of the SAP system instances to the SAP HANA database.

5.10.1 Applying Self-signed Certificates while Running the

Installer

The installer can configure the SAP system instances to use the Transport Layer Secure (TLS)/Secure Sockets
Layer (SSL) protocol to secure connections of to the SAP HANA database. Self-signed certificates are
generated to setup the secure environment for your system using the SAP Cryptographic Library
CommonCryptoLib.

Context

If you want to secure your SAP system database connection to the SAP HANA database, TLS/SSL must be
configured on both server and client side.

For more information, see section Configuring Clients for Secure Connections in the documentation SAP HANA
Client Interface Programming Reference.

Procedure

On the Database for SAP System screen, select checkbox Connect using SSL and enter the required encryption
parameters when requested by the installer. For more information, see SAP Note 2891130 .

5.10.2 Configuring SAP HANA Encryption Parameters

Depending on how you have specified parameter sslEnforce, the installer will configure the connection of the
SAP system instances to the SAP HANA database.

Context

Due to enhanced security standards, you can set up your SAP HANA database using parameter sslEnforce
in a way that SAP system instances are only allowed to access it using secured and encrypted connections.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Preparation PUBLIC 101
For more information, see the information about parameter sslEnforce in section Enforced TLS/SSL for
Client Connections in the SAP HANA Security Guide at: https://help.sap.com/viewer/p/
SAP_HANA_PLATFORM Security

Procedure

1. Start the SAP HANA Database Studio as described in the SAP HANA Administration Guide at: https://
help.sap.com/viewer/p/SAP_HANA_PLATFORM Administration
2. If not yet done, add your SAP HANA database system .
3. Log on as user SYSTEM.
4. Choose Configuration
5. Filter for the sslenforce parameter and change the value according to your requirements.

Default is false.

5.11 Checking Time Zones

Before you start the installer, you need to check time zone settings.

Context

Before you start the installer, compare the following time zone settings:

● The time zone of the target host for the ABAP application server
● The time zone of the <sid>adm user of the SAP HANA system
Check the relevant SAP HANA time zone by logging on to the system at the command line with your user
<sid>adm and then using command date.

Procedure

If the systems have different time zones, proceed as follows:

○ Change the time zone of the ABAP system (recommended solution)

○ If the time zone of the ABAP system cannot be changed, change the time zone of the SAP HANA system.
For more information, see https://help.sap.com/viewer/p/SAP_HANA_PLATFORM Installation and
Upgrade SAP HANA Server Installation and Update Guide

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
102 PUBLIC Preparation
5.12 Preparing the Installation Media

This section describes how to prepare the installation media.

Installation media are available as follows:

● The Software Provisioning Manager 1.0 archive containing the installer

You always have to download the latest version of the Software Provisioning Manager 1.0 archive.
For more information, see Downloading and Extracting the Software Provisioning Manager 1.0 Archive
[page 108].
● 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
109].
If you are performing an Installation Using a Stack Configuration File [page 37], you can directly
download the artefacts (SAR archives) as specified in the Maintenance Plan.
○ 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 103].
○ Download the complete kernel media from the SAP Software Download Center.
For more information, see Downloading Complete Installation Media [page 115].
○ 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 103].

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

5.12.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 127] ). 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 .

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Preparation PUBLIC 103
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 25] 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 116].
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.

SAP Instance
Installation Required Software Packages from Installation Media

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.

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.

○ Database client software

For enabling SAP HANA SSL, at least SAP HANA Client 2.0 SPS04 is required. For more infor­
mation, see SAP Note 2784500 .
○ Installation Export (folders EXP*)

 Note
If you want to use SAP liveCache on SAP HANA, you must install the LCAPPS package on the
database server. For more information, see the SAP MaxDB Administration Guide at https://
help.sap.com/maxdb Application Help and SAP Note 2979266 .

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
104 PUBLIC Preparation
 SAP Instance
Installation Required Software Packages from Installation Media

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.

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

Primary appli­ ○ Software Provisioning Manager 1.0 archive

cation server in­ ○ UC or NUC Kernel (folder K_<Version>_<N or U>_<OS>) where U means Unicode and N
stance 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 SCM only: SAP MaxDB liveCache

 Note
If you want to use SAP liveCache on SAP HANA, you must install the LCAPPS package on
the database server. For more information, see the SAP MaxDB Administration Guide at
https://help.sap.com/maxdb Application Help and SAP Note 2979266 .

Additional appli­ ○ Software Provisioning Manager 1.0 archive

cation server in­ ○ UC or NUC Kernel (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 SCM only: SAP MaxDB liveCache

 Note
If you want to use SAP liveCache on SAP HANA, you must install the LCAPPS package on
the database server. For more information, see the SAP MaxDB Administration Guide at
https://help.sap.com/maxdb Application Help

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Preparation PUBLIC 105
 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 Archive [page 108].
2. Use the SAP HANA database client revision matching your HANA database. You can find the correct
database client here:
http://support.sap.com/swdc Support Packages and Patches Software Downloads Support
Packages & Patches By Alphabetical Index (A-Z) H SAP HANA PLATFORM EDITION SAP HANA
PLATFORM EDIT. 1.0 Entry by Component HANA client SAP HANA CLIENT 1.00
<Application_Server_OS>
From here download and extract the correct file IMDB_CLIENT100_*.SAR.

 Note

If you are unable to download the SAP HANA database client revision matching your HANA
database from SAP Service Marketplace or if the version there is no more recent than that on the
installation medium, you can use the version of the database client from the installation medium.

3. 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
109].

 Note

If you are using a stack configuration file (see Installation Using a Stack Configuration File
[page 37]), you have the installation media defined when generating the Landscape Plan. The
media link provided in the Landscape Plan guides you to the location in the SAP Software
Download Center at https://launchpad.support.sap.com/#/softwarecenter where you can
download the installation media required for your SAP product, operating system and
database.

Using the installer, you can also directly download the artefacts (SAR archives) as specified in
the Maintenance Plan. For more information, see Downloading Software Packages for a
Maintenance Planner Transaction [page 112].

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
106 PUBLIC Preparation
 You need to copy the installation media manually to your IBM i [page 116].

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

 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
109].

 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 - are only prompted if they cannot be retrieved from the primary
application server instance or the ASCS instance of the existing SAP system.

4. 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 116].

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

Related Information

Downloading and Extracting the Software Provisioning Manager 1.0 Archive [page 108]

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Preparation PUBLIC 107
Downloading SAP Kernel Archives (Archive-Based Installation) [page 109]
Downloading Software Packages for a Maintenance Planner Transaction [page 112]
Downloading Complete Installation Media [page 115]
Copying the Installation Media Manually to Your IBM i [page 116]
Copying the Installation Media Manually to Your IBM i [page 116]

5.12.1.1 Downloading and Extracting the Software

Provisioning Manager 1.0 Archive

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

Prerequisites

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

 Note

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

Proceed as follows to get the latest version of SAPCAR:

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

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 Software Provisioning Manager archive
(SWPM10SP<Support_Package_Number>_<Version_Number>.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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
108 PUBLIC Preparation
There is no action required from your side, the installer uses the relevant loadtools automatically once you
run it from the extracted SWPM10SP<Support_Package_Number>_<Version_Number>.SAR archive. For
more information, see SAP Note 2472835 .

Procedure

1. Download the latest version of the Software Provisioning Manager 1.0 archive
SWPM10SP<Support_Package_Number>_<Version_Number>.SAR from:

https://support.sap.com/sltoolset System Provisioning Download Software Provisioning

Manager
2. If you did not do so already, make sure you have configured your TCP/IP as described in SAP Note 92589
. Afterwards, do not forget to perform an IPL to make the change effective. Otherwise, the file copying is
very slow from your local Windows optical media drive or Windows file system to the IFS on your IBM i.
3. Unpack the Software Provisioning Manager archive to a local directory on your Windows PC using the
following command:

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

\SWPM10SP<Support_Package_Number>_<Version_Number>.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 Software Provisioning Manager 1.0 to the IFS of the IBM i host. For more
information about how to do this, see the section Copying the Installation Media Manually to Your IBM i
[page 116].

5.12.1.2 Downloading SAP Kernel Archives (Archive-Based

Installation)

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.

 Note

If you are performing an installation using a stack configuration file, you can use the service Downloading
Software Packages for a Maintenance Planner Transaction [page 112].

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Preparation PUBLIC 109
Context

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

1. Download and unpack the latest version of Software Provisioning Manager as described in Downloading
and Extracting the Software Provisioning Manager 1.0 Archive [page 108].

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 S/4HANA <Release> Server , choose SAP APPLICATION COMPONENTS
SAP S/4HANA SAP S/4HANA <Release> SAP S/4HANA SERVER
○ If you want to install AS ABAP for SAP SAP S/4HANA Frontend , choose SAP NetWeaver and
complementary products AS ABAP FOR S/4HANA FRONTEND AS ABAP <Release> FOR S/4
HANA <Release>
○ If you want to install SAP BW/4HANA <Release> , choose SAP NetWeaver and complementary
products SAP BW/4HANA SAP BW/4HANA <Release> SAP BW/4HANA SERVER
○ If you want to install SAP NetWeaver AS for ABAP 7.52, choose SAP NetWeaver and complementary
products NW AS ABAP INNOVATION PKG NW AS ABAP 7.52
○ If you want to install SAP NetWeaver AS for ABAP 7.51 innovation package, choose SAP NetWeaver
and complementary products NW AS ABAP INNOVATION PKG NW AS ABAP 7.51 INNOVATION
PKG
○ If you want to install AS ABAP FOR OOEM, choose SAP NetWeaver and complementary products
SAP NETWEAVER ABAP FOR OOEM
○ If you want to install the ABAP part of an SAP Process Integration 7.5 system, choose SAP
NetWeaver and complementary products SAP NetWeaver <Release> Application Server
ABAP
○ If you want to install an SAP NetWeaver ABAP system, choose SAP NetWeaver and complementary
products SAP NetWeaver <Release> [For releases lower than 7.5: Entry by Component]
Application Server ABAP
○ If you want to install an SAP Business Suite system based on SAP NetWeaver, choose SAP
Application Components <SAP CRM | SAP ERP | SAP SCM | SAP SRM> <Release> Entry
by Component <ABAP Product Instance>

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
110 PUBLIC Preparation
 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 - are only prompted if they cannot be retrieved from the primary
application server instance or the ASCS instance of the existing SAP system.

 Caution

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

 Example

○ If SAPEXE<Version>.SAR is of version 7.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.

○ SAPEXE<Version>.SAR
SAP KERNEL <Version> <UC> <Operating System> #DATABASE INDEPENDENT
○ If you want to install an SAP system based on SAP NetWeaver AS for ABAP 7.52 or higher, you can
only choose 7.49 UNICODE for SAP KERNEL <Version>.
○ If you want to install an SAP system based on SAP NetWeaver AS for ABAP 7.51 innovation
package or higher, you can either choose or 7.53 DCK UNICODE or 7.49 UNICODE for SAP KERNEL
<Version>.
○ If you want to install an SAP system based on SAP NetWeaver 7.5, 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.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, 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 Application Server for ABAP 7.52,
choose SAP IGS <7.53 or higher> # OS independent .
○ If you want to install an SAP system based on SAP NetWeaver Application Server for ABAP 7.51
innovation package, choose SAP IGS <7.53 or higher> # OS independent .
○ If you want to install an SAP system based on SAP NetWeaver 7.5, choose SAP IGS <7.53 or
higher> # OS independent .

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Preparation PUBLIC 111
 ○ 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
○ You require the igshelper<Version>.sar.
Choose SAP IGS HELPER # OS independent
○ SAPHOSTAGENT<Version>.SAR
SAP HOST AGENT 7.22 <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 - 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 103] or by downloading them as
described in Downloading Complete Installation Media [page 115].

Related Information

Downloading Software Packages for a Maintenance Planner Transaction [page 112]

5.12.1.3 Downloading Software Packages for a Maintenance

Planner Transaction
Software Provisioning Manager (the installer) is now enabled to download all software packages that have been
defined in a Maintenance Planner Transaction.

 Note

This feature is only available if you perform an installation using a stack configuration file.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
112 PUBLIC Preparation
Prerequisites

Plan your new SAP system including the required Support Package level (applicable for SAP S/4 HANA, SAP
NetWeaver, SAP Business Suite, and SAP Financials) as available in the Maintenance Planner and run sapinst
SAPINST_STACK_XML=<stack configuration file> in order to benefit from an automated installation
process.

Procedure

1. Specify a download directory for the artifacts (SAP archives) to be downloaded.

2. Start the installer as described in Running the Installer [page 127] .

3. On the Welcome screen, choose Generic Options Download Software Packages for Maintenance
Planner Transaction
4. Follow the instructions on the installer screens.

The installer prompts you for the following input parameters:

○ Maintenance Planner Transaction ID

You can find the Maintenance Planner Transaction ID by one of the following ways:
○ In the MP_Plan_<Transaction ID>_<Generation Date>_.pdf file which you can download
during the Completed step in the Maintenance Planner by choosing the Download PDF button.
○ From the Transaction ID column in the list of transactions displayed in the Transactions panel in the
maintenance planner.
○ From the parameter mopz-transaction-id in the stack configuration file
MP_Stack_<Transaction ID>_<Generation Date>.xml which you can download during the
Download Files step in the Maintenance Planner by choosing the Download Stack XML button.

 Note

If you started the installer using a stack configuration file, the Maintenance Planner Transaction ID
is only displayed.

○ Your S-UserID and password

You call Software Provisioning Manager with command line parameter
SAPINST_STACK_XML=<Absolute_Path_To_Stack_XML_File> to get the Maintenance Planner
Transaction ID extracted from the stack configuration file.
You must perform this option directly after creating the Maintenance Planner Transaction, because the
contained download links usually expire soon.
Ensure the following for your S-User:
1. You have download permissions for all artifacts on https://launchpad.support.sap.com/#/
softwarecenter to be able to download them.
2. Consider the SAP Support Portal and the SAP ONE Support Launchpad password policies : Your
password must be the same for both of them. If the passwords are not the same, you will lock the
S-User in the SAP Support Portal. The password must meet all of the following requirements:
○ Must be exactly eight characters long
○ Contains at least one upper-case letter (A-Z)

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Preparation PUBLIC 113
 ○ Contains at least one lower-case letter (a-z)
○ Contains at least one decimal digit (0-9)
○ Contains at least one of the following special characters: ! \ @ $ % / ( { [ ] } ) + - * = ? ' ~ #
_ . , ; : <>
○ Must not start with ? or !
○ Must not contain any blanks
○ Must not begin with three identical characters
○ Must be different from the last five passwords you have already used
○ Only one password change is allowed per day
If required, request a change of your SAP Support Portal Password and of your SAP ONE Support
Password at https://support.sap.com/en/my-support/users.html .
○ Location of download folder for the installation software packages to be downloaded
○ If you have a proxy configured in your network, provide the proxy host and port.
5. You get a list of all downloadable artifacts (SAP archives) as specified in the stack configuration file along
with their file size.

You can still deselect downloadable artifacts (SAP archives) that you do not need to be downloaded.
6. Choose Next to start the download.

If you get a download error, this is the result of an unsuccessful network connection. Check your network
connection and proxy configuration. If the download of some artifacts finishes without any error, but still
with a status other than OK, you must do one of the following:
○ Create an up-to-date Maintenance Plan and perform again the download of the files which were not
downloaded successfully. In case of an error, the installer skips the download of the artifact (SAR
archive) in question and continue with the next one in the list.
○ Download the still missing files directly from the SAP Software Center at https://
launchpad.support.sap.com/#/softwarecenter .

Results

You have downloaded the artifacts (SAP archives) required for your SAP system installation with Software
Provisioning Manager (the installer) - corresponding to the archives listed in section Downloading SAP Kernel
Archives (Archive-Based Installation) [page 109] - and for applying the required kernel and support packages
using Software Update Manager (SUM) after the installation has completed.

SAP BW/4HANA 1.0 SR1 only: RDBMS and export media are not covered by this feature. You have to provide
them either as physical media or download them from the SAP Software Center as described in Downloading
Complete Installation Media [page 115] .

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
114 PUBLIC Preparation
5.12.1.4 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 Archive [page 108].
2. Create a download directory on your Windows host from where you will transfer the media to your IBM i
host (for example, C:\tmp\download)
3. You identify the required media as listed in Media Required for the Installation - Listed by SAP System
Instance [page 103] .
4. Identify all download objects that belong to one medium according to one of the following:

 Note

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

○ Download path or location:

○ To download the complete kernel media, go to https://support.sap.com/sltoolset System
Provisioning Software Provisioning Manager 1.0 SP<Current Version> Download Kernel
releases delivered for SL Toolset SL TOOLSET 1.0 (INSTALLATIONS AND UPGRADES) KERNEL
FOR INSTALLATION/SWPM .

 Note

You can only download complete kernel media for kernel release 7.22, which can only be used
for provisioning of SAP products based on SAP NetWeaver 7.3 EHP1. For all remaining SAP
products, you have to download kernel media from https://support.sap.com/swdc as
described in Downloading SAP Kernel Archives (Archive-Based Installation) [page 109].

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Preparation PUBLIC 115
  Example

51031387_1

51031387_2

...

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

Related Information

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

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
116 PUBLIC Preparation
Procedure

Creating a Binary Share on IBM i

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

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

 Note

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

mkdir /tmp/SAP
.

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

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

Copying the Installation Media Manually Using the Binary Share TMPSAP

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. Only valid for 'Software Component': SAP CRM, SAP ERP, SAP NetWeaver, SAP SRM
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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Preparation PUBLIC 117
  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 97].

End of 'Software Component': SAP CRM, SAP ERP, SAP NetWeaver, SAP SRM

6. Only valid for 'Software Component': SAP SCM

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 <QSECOFR_Password> /USER:QSECOFR
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

For more information about how to prepare the user QSECOFR, see Preparing the SAP Installation User
onIBM i [page 97].

End of 'Software Component': SAP SCM

7. To change to the new network drive, enter X: in the command prompt.

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

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

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

 Note

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

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
118 PUBLIC Preparation
6 Installation

6.1 Installation Checklist

This section includes the installation steps for the following:

● Standard system
● Distributed 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. <SAPSID>OWNER is 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.

 Note

The SAP HANA database is normally pre-installed by SAP partners before you start the installation. For
more information about how to install the SAP HANA database, see the SAP HANA Server Installation and
Update Guide at https://help.sap.com/hana_platform Implement Installation and Upgrade . The
contents of the database instance are remotely installed by SoftwareProvisioning Manager (the “installer”)
from the primary application server host.

On the Database for SAP System screen, enter the Database Host and the Instance Number for your SAP
HANA database host. If the instance does not exist, a new SAP HANA database instance will be installed
on the same host as the SAP system..

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Installation PUBLIC 119
Standard System

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

 Note

In a standard system, all mandatory instances except the database instance are installed on one host.

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

Distributed System

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 158].
2. On the ASCS instance host, you do the following:
1. You check the prerequisites [page 125] and run the installer [page 127] to install the ABAP central
services instance (ASCS instance).

 Note

If you want to install an ASCS instance with integrated SAP Web Dispatcher [page 32] or with
integrated SAP Gateway [page 34] 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 primary application server instance host, you do the following:

1. You link the global directories [page 123] in <sapmnt>/<SAPSID> from the SAP global host.
2. You check the prerequisites [page 125] and run the installer [page 127] to install the contents of the
database instance and then the primary application server instance.
4. You continue with Post-Installation [page 146].

Graphical Overview

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
120 PUBLIC Installation
The following figure shows how you install the various instances in a distributed system:

Distribution of Instances in an ABAP 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.

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 79].
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 158].
3. You set up the switchover cluster infrastructure as follows:
1. You check the prerequisites [page 125] and Running the Installer [page 127] to install the ABAP central
services instance (ASCS instance) on the primary cluster node, . Use a virtual host namehost A [page
78].

 Note

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Installation PUBLIC 121
 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 hostcheck the prerequisites [page 125] and run the installer [page 127] to install the ERS instance
for the ASCS instance on the primary cluster node, host A. Use a virtual host name [page 78].
3. 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).
4. You configure the switchover software and test that switchover functions correctly to all standby nodes
in the cluster.
5. 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 125] and run the installer [page 127] to install the ERS instance
for the ASCS instance on the standby node, host B.
4. 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.
5. You continue with Post-Installation [page 146].

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 System

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
122 PUBLIC Installation
Additional Application Server Instance

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

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

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 158].
2. On every additional application server instance host, you do the following:
1. You link the global directories [page 123] in <sapmnt>/<SAPSID> from the SAP global host.
2. You check the prerequisites [page 125] and run the installer [page 127] to install the additional
application server instance.
3. You continue with Post-Installation [page 146].

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 158].
2. On each additional application server instance host, do the following:
1. You make available the global directories [page 123] in <sapmnt>/<SAPSID> from the SAP global
host.
2. You check the prerequisites [page 125] and run the installer [page 127] to install the additional
application server instance.
3. You continue with Post-Installation [page 146].

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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Installation PUBLIC 123
Prerequisites

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

 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 158].
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 97].
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>')

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
124 PUBLIC Installation
6.3 Specifying the Initial Data Source of the User
Management Engine

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

Procedure

Using Central User Management

1. You install your SAP system as described in this installation guide.
2. Add the system to Central User Administration (CUA). For more information, see Configuring User
Management [page 171].

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

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
private browsing mode (Firefox). This is to prevent Web browser plugins and settings from interfering
with the SL Common GUI.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Installation PUBLIC 125
  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 127] . 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 132].

● 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 97].
● 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.
● 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 132].

 Note

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 47] 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 40].

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
126 PUBLIC Installation
 ● 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 190].
● 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 System Provisioning Using an Input
Parameter File [page 134] which describes an improved procedure using inifile.params.

6.5 Running the Installer

This section describes how to run the installer.

Prerequisites

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Installation PUBLIC 127
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 132].

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

 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 are using a stack configuration file (see Installation Using a Stack Configuration File (Optional)
[page 37]), you must call the sapinst executable with command line parameter
SAPINST_STACK_XML=<Absolute_Path_To_Stack_XML_File>:

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

'SAPINST_STACK_XML=<Absolute_Path_To_Stack_XML_File>')

 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>
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>')

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
128 PUBLIC Installation
 For more information, see Virtual Host Name in SAP System Parameters [page 49].

 Note

If you want to set the connectivity data for your SAP HANA database, you can add parameters when
calling sapinst as follows:

○ Global hdbuserstore container

CALL PGM(QP2TERM) PARM('./sapinst' 'HDB_USE_IDENT=SYSTEM_<SID>')
You need not set HDB_USER_IDENT to the suggested value SYSTEM_<SID>. If you prefer, you can
use the characters A-z, 0-9, or _.
○ If you want to assign virtual host names, you must start the installer with the
SAPINST_USE_HOSTNAME command line parameter:
CD DIR('<Path_To_Unpack_Directory>')
CALL PGM(QP2TERM) PARM('./sapinst'
'SAPINST_USE_HOSTNAME=<Virtual_Host_Name>')
○ ABAP secure storage in the file system (SSFS) – only available for SAP NetWeaver 7.4 and higher:
CALL PGM(QP2TERM) PARM('./sapinst' 'HDB_ABAP_SSFS=YES')
For more information, see Setting Connectivity Data for the SAP HANA Database [page 71].

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 132].
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
125]).

 Caution

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

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Installation PUBLIC 129
 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.
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 system based on SAP NetWeaver AS ABAP from scratch, choose <Product>
<Database> Installation Application Server ABAP <System_Variant> .
○ To install the application server ABAP for an SAP Process Integration system based on SAP
NetWeaver 7.5 from scratch, choose SAP NetWeaver 7.5 <Database> Installation
Application Server ABAP for SAP Process Integration <System Variant> .
○ To install the application server ABAP for an SAP Solution Manager 7.2 system from scratch,
choose SAP Solution Manager 7.2 <Support_Release> <Database> Installation
Application Server ABAP <System Variant> .
○ To install an SAP system based on SAP NetWeaver AS ABAP as target system of a system copy,
choose <Product> <Database> System Copy Target System <System_Variant>
Based on AS ABAP .
○ To install the application server ABAP for an SAP Process Integration system based on SAP
NetWeaver 7.5 as target system of a system copy, choose SAP NetWeaver 7.5 <Database>
System Copy Target System <System_Variant> Based on AS ABAP .
○ To install the application server ABAP for an SAP Solution Manager 7.2 system as target system of
a system copy, choose SAP Solution Manager 7.2 <Support_Release> <Database>
System Copy Target System <System_Variant> Based on AS ABAP .
○ 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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
130 PUBLIC Installation
 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

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.

 Note

If you want to install an ASCS instance with integrated SAP Web Dispatcher [page 32] or with
integrated SAP Gateway [page 34] 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.

 Caution

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

Note that this automatic check is only committed once and not repeated if you modify artifacts such
as SAR archives or files on the media after the initial check has been done. This means that - if you
modify artefacts later on either during the remaining Define Parameters phase or later on during the
Execute Service phase - the signature is not checked again.

For more information, see SAP Note 2393060 .

After you have entered all requested input parameters, the installer displays the Parameter Summary
screen. This screen shows both the parameters that you entered and those that the installer set by default.
If required, you can revise the parameters before starting the installation.
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 179].
9. For security reasons, we recommend that you remove the group SAPINST from the operating system users
after you have completed the installation.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Installation PUBLIC 131
  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 132].

6.6 Additional Information about the Installer

The following sections provide additional information about the installer.

Useful Information about the Installer [page 132]

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

System Provisioning Using an Input Parameter File [page 134]

Provisioning with Software Provisioning Manager (“the installer”), for example installation, of SAP
systems in unattended mode with an input parameter file.

Interrupted Processing of the Installer [page 138]

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

Troubleshooting with the Installer [page 142]

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

Troubleshooting During the Database Load [page 143]

Using the Step State Editor (SAP Support Experts Only) [page 144]
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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
132 PUBLIC Installation
 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
125].
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.
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.

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Installation PUBLIC 133
 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 (command line options) and related documentation, 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 System Provisioning Using an Input
Parameter File [page 134] which describes an improved procedure using inifile.params.

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

 Note

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

6.6.2 System Provisioning Using an Input Parameter File

Provisioning with Software Provisioning Manager (“the installer”), for example installation, of SAP systems in
unattended mode with an input parameter file.

Prerequisites

Provisioning of SAP systems can also be done in unattended mode without the user interface of the installer.
This means that, after inserting the required parameters into a parameter-file and running the sapinst
executable by providing the path to this parameter-file , the installation will run in the background and no
further user interaction is required.

Context

This section describes the steps that you need to execute in addition to the procedure described in this guide,
when running the installer in unattended mode using an input parameter file.

Since the new Web-based SL Common GUI (see Useful Information about the Installer [page 132]) was
introduced in 2017 there are two ways to run the unattended mode: “observer mode” and “non-observer
mode”.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
134 PUBLIC Installation
Observer Mode
If you are running an installation in unattended mode but you are sitting in front of the screen, you might want
to check the progress from time to time. In this case the “observer mode” makes sense.

Start the installation as described below in the Solution section, using the following parameters:

SAPINST_INPUT_PARAMETERS_URL=<path_to_your_parameterfile>
SAPINST_EXECUTE_PRODUCT_ID=<product-id for the installation>
SAPINST_SKIP_DIALOGS=true

The Software Provisioning Manager will start the installation in the background AND start a Web Dispatcher
and provide an URL to access the SL Common GUI. The user who has started the installation can now connect
to the URL and observe the progress of the installation, for example to look at the logfiles in the Web browser.
However, all parameters will be taken from the input parameter file and can not be changed in the Web browser.

Non-Observer Mode
Choose that mode if you want to run a “scripted” or by other means automated scenario, for example
overnight. In that case it is crucial that the process is started without a Web Dispatcher and therefore without a
GUI. Otherwise, the automation could be stuck if the installer encounters a situation that requires user
interaction.

Start the installation as described below in the Solution section, using the following parameters (use the same
parameters like for Observer Mode, but provide SAPINST_START_GUISERVER=false in addition):

SAPINST_INPUT_PARAMETERS_URL=<path_to_your_parameterfile>
SAPINST_EXECUTE_PRODUCT_ID=<product-id for the installation>
SAPINST_SKIP_DIALOGS=true
SAPINST_START_GUISERVER=false

This will start the installation but this time NO Web Dispatcher will be started and no URL to access the SL
Common GUI will be provided either. So the user can not follow the processing of the installation in a Web
browser and the installation will run completely in the background.

If the process runs into an error, SAPinst will abort and you have to check for the reason in the log files.

Restrictions
In exceptional cases, parameters prompted or displayed in the Software Provisioning Manager UI are not
maintainable in the input parameter file. If one of those parameters, that are only available in the GUI mode of
the Software Provisioning Manager, is needed for your unattended installations, you should create a ticket in
the best fitting component below BC-INS to get the issue analyzed.

Must Know about the Input Parameter File

● The input parameter file only contains values that you entered in the Software Provisioning Manager GUI.
● With the SAPinst 749.0.69 or by other means patch we provide a better encryption of passwords in
Software Provisioning Manager files:
If the input parameter file has parameters which are encrypted with Des25 encryption, the instkey.pkey
file available in the installation directory contains the key for the encryption. The instkey.pkey file must
be always located in the same directory as the input parameter file and is used to decrypt the values of the
encrypted parameters. If you need to copy an input parameter file to another directory, you must also copy
the instkey.pkey file to this directory.
● Not explicitly set parameters are documented as comments in the generated input parameter file.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Installation PUBLIC 135
● Each parameter has got a documentation assigned as a comment on top.

 Example

Example for a parameter that is not used and therefore commented out:

# Specify whether Software Provisioning Manager is to drop the schema if

it exists. <= Documentation
# HDB_Schema_Check_Dialogs.dropSchema = false

 Example

Example for a parameter that is used:

# The name of the database schema. <= Documentation

HDB_Schema_Check_Dialogs.schemaName = SAPABAP2

● You have to manually provide the media information, using the following convention:

SAPINST.CD.PACKAGE.<media_name>=<location>

For each media location you must manually insert a dedicated line in your input parameter file. The
Software Provisioning Manager does not automatically take over the media locations you entered while
processing the Media Browser dialog.
● Restriction: Currently you can only specify complete media, not paths to single files like *.SAR archives.
Make sure that you enter the full paths to all required media, relative paths are not sufficient:

 Example

Example on UNIX:

SAPINST.CD.PACKAGE.KERNEL = /mnt/KERNEL
SAPINST.CD.PACKAGE.LOAD = /mnt/LOAD
SAPINST.CD.PACKAGE.RDBMS = /mnt/RDBMS

 Example

Example on Windows:

SAPINST.CD.PACKAGE.KERNEL = C:\sapdvds\KERNEL
SAPINST.CD.PACKAGE.LOAD = C:\sapdvds\LOAD
SAPINST.CD.PACKAGE.RDBMS =C:\sapdvds\RDBMS

When performing a system copy, you need to add one additional media path:

SAPINST.CD.PACKAGE.MIGRATION1 = <full path to ABAP Export media>

● Caution:
If you want to use archives for your installation, you must copy all files that are to be used to a single
directory. In the input parameter file you must specify this directory as a download basket, using the
archives.downloadBasket parameter.
Make sure that there is only one version of the same archive in the directory, for example
SAPEXE_<Version>.SAR

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
136 PUBLIC Installation
Procedure

1. You plan and prepare the run as described in Planning [page 36] and Preparation [page 69].
2. Create your input parameter file as follows:
1. Start the installer as described in Running the Installer [page 127].
2. Choose the option you want to run, and follow the instructions on the screens by entering all
parameter values.
3. Stop after the Parameter Summary screen has been displayed.
4. Find the input parameter file named “inifile.params” in the installation directory.
In the same directory, you will also find the instkey.pkey file with the keys for the encrypted
parameters. For more information, see Must Know about the Input Parameter File above.
5. If required, you can rename the “inifile.params” file as you wish.
3. Adjust the values of the input parameter file as follows:
1. Edit your input parameter file and modify the parameters according to your needs.
2. Add required media or archives information line by line.
4. Identify the Product-ID:
○ To start in unattended mode, you need to know the component ID for the option that are required for
your provisioning scenario.
Proceed as follows:
1. Open the sapinst_dev.log in the installation directory.
2. Check for the “product-id”

 Example

product-id=NW_ABAP_ASCS:NW750.ADA.ABAP

○ Alternatively, you can check the header of the generated input parameter file.

 Example

product id 'NW_ABAP_ASCS:NW750.ADA.ABAP'

5. Run the installer [page 127] with the parameters required for unattended mode:
○ Make sure that the instkey.pkey file with the keys for the encrypted parameters is available in the
same directory as the input parameter file. Otherwise the encrypted parameters cannot be decrypted.
For more information, see Must Know about the Input Parameter File above.
○ In observer mode: Start the sapinst executable from an empty directory with the following
parameters:

SAPINST_INPUT_PARAMETERS_URL=<path_to_your_parameterfile>
SAPINST_EXECUTE_PRODUCT_ID=<product-id for the installation>
SAPINST_SKIP_DIALOGS=true

○ In non-observer mode: Start the sapinst executable from an empty directory with the following
parameters:

SAPINST_INPUT_PARAMETERS_URL=<path_to_your_parameterfile>
SAPINST_EXECUTE_PRODUCT_ID=<product-id for the installation>
SAPINST_SKIP_DIALOGS=true
SAPINST_START_GUISERVER=false

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Installation PUBLIC 137
6. After the installer has completed, perform follow-up activities as described in Post-Installation [page 146].

Related Information

SAP Note 2230669 Provisioning with Software Provisioning Manager - for example installation - of SAP
systems in unattended mode with an input parameter file.
SAP Note 2849054 Software Update Manager Automation with Software Provisioning Manager
SAP Note 2742212 Unattended installation fails with "Empty directory name is not allowed." message
SAP Note 2626837 'isUnicode': Radio group contains an invalid value ''. Valid values are: false|true|
SAP Note 2669183 ASCS installation failure with SWPM unattended mode (Non-Observer mode)
SAP Note 2482103 Installation with SWPM in unattended mode using input parameter file fails
SAP Note 2974889 Installation with SWPM in unattended mode fails in step getDBInfo due to missing
paramerters

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
138 PUBLIC Installation
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 127] .
2. Make sure that the installation media are still available.

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

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

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Installation PUBLIC 139
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.

...
************************************************************************
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 132].
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
125]).

 Caution

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

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

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

1. Click on the certificate area on the left hand side in the address bar of your browser, and view the
certificate.
2. Open the certificate fingerprint or thumbprint, and compare all hexadecimal numbers to the ones
displayed in the console output of the installer.
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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
140 PUBLIC Installation
 As a result, you get the server fingerprint or thumbprint from the server certificate.
3. Accept the warning to inform your browser that it can trust this site, even if the certificate could not
be verified.

The SL Common GUI opens in the browser by displaying the Welcome screen.
6. From the tree structure on the Welcome screen, select the installation option that you want to continue and
choose Next.

The What do you want to do? screen appears.

7. On the What do you want to do? screen, decide between the following alternatives and continue with Next:

Alternative Behavior

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

The following naming convention is used for the backup directory:

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Installation PUBLIC 141
  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.5 Troubleshooting with the Installer

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

Context

If an error occurs, the installer:

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

Procedure

1. Check SAP Note 2393060 for known installer issues.

2. If an error occurs during the Define Parameters or the Execute Service phase, do one of the following:

○ Try to solve the problem:

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

 Note

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

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

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
142 PUBLIC Installation
 ○ 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 138].
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.6 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

Procedure

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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Installation PUBLIC 143
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.7 Using the Step State Editor (SAP Support Experts

Only)

This section describes how to use the Step State Editor available in the installer.

 Note

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

Prerequisites

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

● Make sure that the host where you run the installer meets the requirements listed in Prerequisites for
Running the Installer [page 125].

Procedure

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
144 PUBLIC Installation
 3. Choose Next.

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

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

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

○ Choose OK to continue with this step.

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Installation PUBLIC 145
7 Post-Installation

7.1 Post-Installation Checklist

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

 Note

SAP systems based on SAP NetWeaver 7.4:

You can automate some of these post-installation steps by running task list
SAP_BASIS_SETUP_INITIAL_CONFIG in the ABAP task manager for lifecycle management automation
(transaction STC01). For more information, see SAP NetWeaver 7.4 and Higher: Performing Automated
Initial Setup (Optional) [page 149].

The sections describing these steps are marked with a corresponding note at the beginning.

● Standard, distributed, or high-availability system

● Additional application server instance

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

 Note

We highly recommend that you apply the latest Support Package as described in Applying the Latest
Kernel [page 164]. The minimum requirement for running SAP BW on the SAP HANA database is SP4.

Standard, Distributed, or High-Availability System

 Note

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

The SAP HANA database is normally pre-installed by SAP partners before you start the installation. During
the SAP system installation, the database instance was remotely installed by Software Provisioning
Manager (the “installer”) from the primary application server host.

1. If required, you perform a full backup [page 180] immediately after the installation has finished.
2. You check whether you can log on to the Application Server ABAP [page 148].
3. SAP systems based on SAP NetWeaver 7.4 and higher only: You perform the automated initial setup
[page 149].

 Note

This step is optional.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
146 PUBLIC Post-Installation
 4. If you have not enabled SAP EarlyWatch Alert in your SAP Solution Manager, you enable SAP EarlyWatch
Alert for ABAP Systems on SAP HANA [page 151].
5. You install the SAP license [page 152].
6. If you have installed a high-availability system, you set up the licenses for high availability [page 153].
7. You configure the remote connection to SAP support [page 154].
8. You enable the Note Assistant to apply note corrections [page 155].
9. You configure the documentation provided on the SAP Help Portal [page 155].
10. You perform the consistency check [page 157].
11. You set up the transport directory [page 158].
12. You configure the Transport Management System [page 160].
13. For production systems it is highly recommended that you connect the system to SAP Solution Manager
[page 161].
14. Run installer option Check and Adjust ABAP System to apply necessary configuration steps.
15. You apply the latest kernel and Support Packages [page 164].
16. You perform post-installation steps for the application server ABAP [page 165].
17. If you installed a high-availability system based on SAP NetWeaver AS for ABAP 7.52, you can decide
whether you want to switch to the new standalone enqueue server 2 and enqueue replicator 2 [page 168].
18. If you installed the ABAP part of an SAP Solution Manager 7.2 or SAP Process Integration 7.5 system,
enable HTTPS communication with the Java part of the system.
For more information, see SAP Solution Manager 7.2, SAP Process Integration 7.5 only: Enabling HTTPS
Communication for ABAP [page 168].
19. If required, you install additional languages and perform language transport [page 169].
20.SAP Kernel Release 7.4 and Higher: You perform IP Multicast Configuration [page 170].
21. You configure the user management [page 171].

 Note

This section does not apply for SAP Process Integration 7.5 and SAP Solution Manager, because for
them the user management with an external ABAP system is mandatory . For SAP Process Integration
7.5 and SAP Solution Manager you have to perform special configuration steps which are described in
the guide you have to use for the installation of the Java stack..

22. You ensure user security [page 172].

23. You perform the client copy [page 175].
24. You install or upgrade SAP HANA studio [page 177].
25. You back up the SAP HANA database [page 177].
26. SAP systems based on SAP NetWeaver 7.4 and higher only: If required, you change the keys for the
secure storage [page 178].
27. You remove the installer installation files [page 179].
28. You perform a full backup [page 180].
29. 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 182]
30.If you chose to install an integrated SAP Web Dispatcher within the ASCS instance, you configure the SAP
Web Dispatcher [page 183]
31. If you chose to install an integrated Gateway within the ASCS instance, you configure the SAP Gateway
[page 184].
32. You check the Master Guide - called “Installation Guide” for SAP S/4HANA - for your SAP Business Suite
application, SAP Solution Manager system (section Implementation Sequence) or SAP NetWeaver

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Post-Installation PUBLIC 147
 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

1. If required, you perform a full backup [page 180] immediately after the installation has finished.
2. You check whether you can log on to the Application Server ABAP [page 148].
3. You configure the documentation provided on the SAP Help Portal [page 155].
4. You ensure user security [page 172].
5. You remove the installer installation files [page 179].
6. You perform a full backup [page 180].

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.

Context

 Note

Client 066 is no longer available in newly installed SAP systems based on SAP NetWeaver 7.5 or higher. For
more information, see SAP Note 1749142 .

 Note

Client 001 is no longer available in newly installed SAP systems based on SAP S/4HANA and SAP BW/
4HANA.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
148 PUBLIC Post-Installation
 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.

7.3 SAP NetWeaver 7.4 and Higher: Performing Automated

Initial Setup (Optional)

After the installation of a new SAP system you have to configure the system to enable its usage. For example,
you have to install an SAP license, create logon groups, and configure the Transport Management System
(TMS) and security settings. If your SAP system is based on SAP NetWeaver 7.4 and higher, you can profit from
an automated initial setup which executes these steps automatically.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Post-Installation PUBLIC 149
Prerequisites

Note that the best point in time when you perform automated initial setup depends on the following:

● If you have run the installation using a stack configuration file (also called “up-to-date installation”), we
recommend that you proceed as follows:
1. Perform the complete installation and update process - that is the installation with Software
Provisioning Manager and the update with Software Update Manager.
2. Perform the automated initial setup.
By running first the update and then the automated initial setup, you can profit from latest features and
fixes in the initial setup configuration content.
Background: As of Software Logistics Toolset 1.0 SPS12, the installation procedure with Software
Provisioning Manager 1.0 SP07 and higher also includes basic configuration activities, such as initial basic
configuration of transport management, which are a prerequisite for the subsequent maintenance process.
In previous SP versions of Software Logistics Toolset 1.0, this prerequisite had to be fulfilled by running
automated initial setup before the update process.
● If you have not run the installation using a stack configuration file (also called “up-to-date installation”), we
recommend that you proceed as follows:
1. Run automated initial setup directly after the installation, using the automation content provided with
the system load.
2. Apply the Support Packages to benefit from the already performed initial configuration – for example,
using the already configured Transport Management System.
3. Consider running the automated initial setup a second time, especially if you want to benefit from the
latest improvements and fixes offered by the updated automation content provided by the applied
Support Package.

For more information about automated initial setup, see the SAP Community Network at https://
wiki.scn.sap.com/wiki/display/SL/Automated+Initial+Setup+of+ABAP-Based+Systems .

Procedure

1. Start the ABAP Task Manager by calling transaction STC01.

2. Choose task list SAP_BASIS_SETUP_INITIAL_CONFIG.
3. Select the tasks you want to get executed.

For this, the task list offers sophisticated online documentation of the comprised activities.
4. Choose Execute.

You are guided through the configuration steps where you can enter the required values.

Related Information

Installation Using a Stack Configuration File [page 37]

Installing the SAP License [page 152]
Configuring the Remote Connection to SAP Support [page 154]

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
150 PUBLIC Post-Installation
Configuring the Change and Transport System [page 160]
Applying the Latest Kernel and Support Package Stacks [page 164]
Performing Post-Installation Steps for the ABAP Application Server [page 165]
Performing the Consistency Check [page 157]

7.4 Enabling SAP EarlyWatch Alert for ABAP Systems on

SAP HANA

Context

After the installation of any new SAP ABAP system running on SAP HANA, you have to enable the SAP
EarlyWatch Alert (EWA) and send corresponding data to SAP – either by using SAP Solution Manager for SAP
EarlyWatch Alert or by performing the automated configuration described below.

The SAP EarlyWatch Alert identifies potential problems early, avoids bottlenecks, and monitors the
performance of your ABAP and Java systems and your most important business processes regularly,
automatically, and effectively. For more information, see http://support.sap.com/ewa .

If you have not enabled SAP EarlyWatch Alert in your SAP Solution Manager (for more information, see SAP
Note 1257308 ), we provide an automated procedure using our automation framework ABAP Task Manager,
which is already part of the ABAP system. The automation task list “Early Watch Alert to SAP Configuration”
sets up a periodical EWA data collection and transfers this data to SAP in Service Data Control Center
(SDCCN), when executed by the ABAP Task Manager.

The task list comprises the following detailed tasks:

1. Configuration of SAPOSS Connection (OSS1)

Creates standard RFC SAPOSS if it does not yet exist.
2. SDCC_OSS Connection
Creates an RFC SDCC_OSS by copying RFC SAPOSS and adds this RFC to the SDCCN RFC list if it does
not yet exist. This RFC is used in SDCCN to communicate with the SAP backend.
3. SDCCN Activation
Activates the SDCCN in the system if not yet activated. An hourly job /BDL/TASK_PROCESSOR is
scheduled after the activation.
4. SDCCN Refresh Service Definition
Gets the newest Service Definitions from SAP. The Service Definitions define the data to be collected for
the EWA session.
5. SDCCN Schedule EWA to SAP
Schedules a weekly EWA session (with session number 000Z*) in SDCCN, if no session exists.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Post-Installation PUBLIC 151
Procedure

1. Download the archive SAPK-74005INSTPI or higher at:

http://support.sap.com/installations Software Downloads Support Packages and Patches By

Alphabetical Index (A-Z) S ST-PI ST-PI 740 SUPPORT PACKAGES .
2. Apply the downloaded ST-PI archive via SPAM/SAINT.
For more information, see http://help.sap.com/spmanager .
3. Start the ABAP Task Manager by calling transaction STC01.
4. Choose the task list /BDL/SDCCN_EWA_CONFIG.
5. Choose Execute.
You are guided through the configuration steps.

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.

 Note

SAP systems based on SAP NetWeaver 7.4 or higher only:

You can automate this step by running task list SAP_BASIS_SETUP_INITIAL_CONFIG in the ABAP task
manager for lifecycle management automation (transaction STC01). For more information, see SAP
NetWeaver 7.4 and Higher: Performing Automated Initial Setup (Optional) [page 149].

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
.

Procedure

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
152 PUBLIC Post-Installation
 SAP Release and SAP Library Quick Link SAP Library Path (Continued)

○ SAP NetWeaver 7.3 including Enhancement Pack­

Application Help Function-Oriented View: English Solution
age 1
Life Cycle Management SAP Licenses
http://help.sap.com/nw731
○ SAP NetWeaver 7.4
http://help.sap.com/nw74
○ SAP NetWeaver 7.5
http://help.sap.com/nw75
○ SAP NetWeaver Application Server for ABAP 7.51
innovation package
https://help.sap.com/nw751abap
○ SAP NetWeaver AS for ABAP 7.52
https://help.sap.com/nw752abap

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 152] as you have cluster nodes.

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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Post-Installation PUBLIC 153
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.

 Note

SAP systems based on SAP NetWeaver 7.4 or higher only:

You can automate this step by running task list SAP_BASIS_SETUP_INITIAL_CONFIG in the ABAP task
manager for lifecycle management automation (transaction STC01). For more information, see SAP
NetWeaver 7.4 and Higher: Performing Automated Initial Setup (Optional) [page 149].

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
154 PUBLIC Post-Installation
7.8 Enabling Note Assistant to Apply Note Corrections

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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Post-Installation PUBLIC 155
  Note

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
156 PUBLIC Post-Installation
 Name Value to be entered

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.

 Note

SAP systems based on SAP NetWeaver 7.4 or higher only:

You can automate this step by running task list SAP_BASIS_SETUP_INITIAL_CONFIG in the ABAP task
manager for lifecycle management automation (transaction STC01). For more information, see SAP
NetWeaver 7.4 and Higher: Performing Automated Initial Setup (Optional) [page 149].

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Post-Installation PUBLIC 157
● You have logged on to the SAP system [page 148].

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.

The following checks are performed:

● 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 the Transport Directory

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
158 PUBLIC Post-Installation
Prerequisites

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 7.3 including Enhancement Pack­

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

● SAP NetWeaver 7.5 Management System – Concept

http://help.sap.com/nw75
● SAP NetWeaver Application Server for ABAP 7.51
innovation package
https://help.sap.com/nw751abap
● SAP NetWeaver AS for ABAP 7.52
https://help.sap.com/nw752abap

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

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Post-Installation PUBLIC 159
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 87].
4. To create the missing users on the remote host, see SAP Note 1123501 .

7.12 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).

 Note

SAP systems based on SAP NetWeaver 7.4 or higher only:

You can automate this step by running task list SAP_BASIS_SETUP_INITIAL_CONFIG in the ABAP task
manager for lifecycle management automation (transaction STC01). For more information, see SAP
NetWeaver 7.4 and Higher: Performing Automated Initial Setup (Optional) [page 149].

 Note

SAP_BASIS_SETUP_INITIAL_CONFIG only covers the configuration of TMS as single system.

 Note

If you are using a stack configuration file (see Installation Using a Stack Configuration File (Optional) [page
37]) and chose Run TMS Configuration (for Single System) during the installation, you have already
completed this step and and skip this section.

Context

Procedure

1. Call transaction STMS in the ABAP system to configure the domain controller in the Transport Management
System (TMS).

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
160 PUBLIC Post-Installation
 For more information, see the SAP Library at:

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

○ SAP NetWeaver 7.3 including Enhancement Package 1

Application Help Function-Oriented View: English
http://help.sap.com/nw731
Solution Life Cycle Management Software Logistics
○ SAP NetWeaver 7.4
http://help.sap.com/nw74 Change and Transport System Change and Transport

○ SAP NetWeaver 7.5 System – Overview Basics of the Change and Transport
http://help.sap.com/nw75 System Transport Management System – Concept
○ SAP NetWeaver Application Server for ABAP 7.51
innovation package
https://help.sap.com/nw751abap
○ SAP NetWeaver AS for ABAP 7.52
https://help.sap.com/nw752abap

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 7.3 including Enhancement Package 1

Application Help Function-Oriented View: English
http://help.sap.com/nw731
Solution Life Cycle Management Software Logistics
○ SAP NetWeaver 7.4
http://help.sap.com/nw74 Change and Transport System Transport Organizer (BC-

○ SAP NetWeaver 7.5 CTS-ORG) Requirements for Working with the Transport
http://help.sap.com/nw75 Organizer Setting the System Change Option
○ SAP NetWeaver Application Server for ABAP 7.51
innovation package
https://help.sap.com/nw751abap
○ SAP NetWeaver AS for ABAP 7.52
https://help.sap.com/nw752abap

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.13 Connecting the System to SAP Solution Manager

Here you find information about how to connect your newly installed SAP system to the SAP Solution Manager
in your system landscape.

 Note

You can skip this section if your newly installed SAP system is itself a SAP Solution Manager system.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Post-Installation PUBLIC 161
Prerequisites

An SAP Solution Manager system must be available in your system landscape. For more information, see
http://help.sap.com/solutionmanager .

Context

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.2:
http://help.sap.com/solutionmanager Version 7.2 SPS <No> Application Help (English)
Technical Infrastructures Landscape Management Database (LMDB) Setting Up the Landscape
Management Infrastructure Importing Landscape Data, CIM Model, and CR Content
○ 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
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. Alternatively, systems can send
information directly to the LMDB in SAP Solution Manager, without an SLD, as described in http://
help.sap.com/solutionmanager Version 7.2 SPS <No> Application Help (English) Technical
Infrastructures Landscape Management Database (LMDB) Setting Up the Landscape Management
Infrastructure Importing Landscape Data, CIM Model, and CR Content .
For more information, see Handling Technical Systems' Data - System Landscape Directory at https://
support.sap.com/en/tools/software-logistics-tools/landscape-management-process/system-landscape-
directory.html .
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:

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
162 PUBLIC Post-Installation
 ○ 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) Setting Up the Landscape
Management Infrastructure Importing Landscape Data, CIM Model, and CR Content
Synchronization with an SLD
○ 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 Setting Up the Landscape
Management Infrastructure Connecting LMDB to System Landscape Directory (SLD)
4. In the LMDB, you complete the information from the SLD manually.

For more information, see the SAP Solution Manager Application Help:
○ 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
○ 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

Related Information

Setting Up the Landscape Management Infrastructure

Importing Landscape Data, CIM Model, and CR Content
Synchronization with an SLD
Managing Technical System Information
Handling Technical Systems' Data - System Landscape Directory

7.14 Running Installer Option “Check and Adjust ABAP

System”

Run installer option Check and Adjust ABAP System to apply some necessary configuration steps.

Procedure

1. Start the installer as described in Running the Installer [page 127].

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Post-Installation PUBLIC 163
2. On the Welcome screen, choose installer option Generic Options SAP HANA Database Check and
Adjust ABAP System
Follow the instructions on the installer screens and enter the parameters for the ABAP system to be
checked and adjusted.

On the Check Adjust SAP System screen, select the required option:
○ HDI_CHECK_ENABLE
If your SAP system is based on SAP NetWeaver AS for ABAP 7.52 , running this option applies some
necessary configuration for the HANA Deployment Infrastructure (HDI) content. If you do not run this
option, updating the ABAP system using transaction SPAM might fail.
○ REPAIR_PRIVILEGES
With this option you can recreate the privileges for the ABAP schema user.

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.

 Note

If you are using a stack configuration file (see Installation Using a Stack Configuration File (Optional) [page
37]), you already downloaded the stack.xml file and the delta archives. If you then already called the
Software Update Manager (SUM) from the installer and applied the Support Package Stacks after the
installation had finished, you can skip this section.

Context

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 .

 Note

If you have installed an SAP Solution Manager 7.2 system, you must apply at least Support Package Stack
(SPS) 01. You cannot use SAP Solution Manager 7.2 with SPS 00.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
164 PUBLIC Post-Installation
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 .
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.

 Note

SAP systems based on SAP NetWeaver 7.4 or higher only:

You can automate this step by running task list SAP_BASIS_SETUP_INITIAL_CONFIG in the ABAP task
manager for lifecycle management automation (transaction STC01). For more information, see SAP
NetWeaver 7.4 and Higher: Performing Automated Initial Setup (Optional) [page 149].

Prerequisites

You have logged on to the ABAP application server as described in Logging On to the Application Server [page
148].

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Post-Installation PUBLIC 165
● 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.

For more information about how to maintain SAP system profiles, see the SAP Library at:

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

○ SAP NetWeaver 7.3 including Enhancement Package 1

Application Help Function-Oriented View: English
http://help.sap.com/nw731
Application Server Application Server ABAP
○ SAP NetWeaver 7.4
http://help.sap.com/nw74 Administration of Application Server ABAP

○ SAP NetWeaver 7.5

http://help.sap.com/nw75
○ SAP NetWeaver Application Server for ABAP 7.51
innovation package
https://help.sap.com/nw751abap
○ SAP NetWeaver AS for ABAP 7.52
https://help.sap.com/nw752abap

● 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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
166 PUBLIC Post-Installation
 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
● Schedule Standard Jobs using Transaction SM36

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Post-Installation PUBLIC 167
7.17 Systems Based on SAP NetWeaver AS for ABAP 7.52
only: Switching to Standalone Enqueue Server 2 and
Enqueue Replicator 2

If you installed a high-availability SAP system based on SAP NetWeaver AS for ABAP 7.52 , you can switch to
“Standalone Enqueue Server 2” and “Enqueue Replicator 2”.

When installing an SAP system based on SAP NetWeaver AS for ABAP 7.52 or lower, Software Provisioning
Manager 1.0 installs the ASCS instance with the classic “Standalone Enqueue Server” and the ERS instance
with the classic “Enqueue Replication Server” by default. However, if you installed an SAP system based on
SAP NetWeaver AS for ABAP 7.52 , you can switch to“ Standalone Enqueue Server 2” and “Enqueue Replicator
2”.

For more information, see https://help.sap.com/nw752abap Application Help SAP NetWeaver Library:
Function-Oriented View SAP NetWeaver Application Server for ABAP Infrastructure Components of SAP
NetWeaver Application Server for ABAP Standalone Enqueue Server 2 Switching to the Standalone Enqueue
Server 2 .

Related Information

High-Availability System [page 27]

7.18 SAP Solution Manager 7.2, SAP Process Integration 7.5

only: Enabling HTTPS Communication for ABAP

For secure communication between the SAP systems connected to the ABAP stack, further post-installation
steps are required to fully enable HTTPS communication.

Prerequisites

● You have installed the application server ABAP for an SAP Solution Manager 7.2 or SAP Process Integration
7.5.
● You entered the HTTPS port that is to be configured in the application server instance profile when
processing the Communication Port for ABAP screen. For more information, see Additional Parameters
when Installing SAP Process Integration 7.5 or SAP Solution Manager 7.2.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
168 PUBLIC Post-Installation
Procedure

Proceed as described in the SAP Note 510007 .

Related Information

Additional Parameters when Installing SAP Process Integration 7.5 or SAP Solution Manager 7.2 [page 60]

7.19 Installing Additional Languages and Performing

Language Transport

This section describes how to install and transport additional languages.

 Note

You do not have to perform these steps or at least some of these steps if you are using a stack
configuration file (see Installation Using a Stack Configuration File (Optional) [page 37]) and processed the
Install Additional Languages screen during the installation.

Context

If you have problems during the language installation, see SAP Note 2456868 .

Procedure

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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Post-Installation PUBLIC 169
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 7.3 including Enhancement Package 1

Application Help Function-Oriented View: English
http://help.sap.com/nw731
Solution Life Cycle Management Software Logistics
● SAP NetWeaver 7.4
Change and Transport System Language Transport (BC-
http://help.sap.com/nw74
● SAP NetWeaver 7.5 CTS-LAN)

http://help.sap.com/nw75
● SAP NetWeaver Application Server for ABAP 7.51
innovation package
https://help.sap.com/nw751abap
● SAP NetWeaver AS for ABAP 7.52
https://help.sap.com/nw752abap

7.20 SAP Kernel 7.40 and Higher: IP Multicast Configuration

and Wake-Up Mechanism

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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
170 PUBLIC Post-Installation
7.21 Configuring the User Management

After the installation has completed, configure the user management of your SAP system.

 Note

For SAP Process Integration 7.5 and SAP Solution Manager configuring the user management with an
external ABAP system is mandatory. For more information, see Preparing an External ABAP System as
Source for User Data in the Java installation guide for your operating system and database .

For SAP Process Integration 7.5 and SAP Solution Manager go to PI 7.5: Configuring the Process Integration
System After the Installation respectively Configuring an SAP Solution Manager System in the Java
installation guide for your operating system and database.

Context

For Solution Manager and Process Integration 7.5, your UME has been configured with the ABAP part of the
system during the target system installation. For other SAP system products this configuration is optional. For
more information, see Preparing an External ABAP System as Source for User Data in the Java installation guide
for your operating system and database .

Procedure

After the installation of your SAP system has finished, you must decide whether you want to do the following:
○ Add the system to Central User Administration (CUA)
○ Use Lightweight Directory Access Protocol (LDAP) synchronization

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Post-Installation PUBLIC 171
For more information, see the SAP Library at:

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

○ SAP NetWeaver 7.3 including Enhancement

Application Help Function-Oriented View: English Security
Package 1
Identity Management Identity Management for System Landscapes
https://help.sap.com/nw731
○ SAP NetWeaver 7.4 Integration of User Management in Your System Landscape

https://help.sap.com/nw74 Adding an ABAP System to Your System Landscape

○ SAP NetWeaver 7.5
https://help.sap.com/nw75
○ SAP NetWeaver Application Server for ABAP
7.51 innovation package
https://help.sap.com/nw751abap
○ SAP NetWeaver AS for ABAP 7.52
https://help.sap.com/nw752abap

7.22 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 [page 49] to all users created
during the installation unless you specified other passwords.

 Recommendation

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

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
172 PUBLIC Post-Installation
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.

Operating System and Database Users

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

Operating System and Database Users

User Type User Comment

Operating system user <sapsid>adm SAP system administrator

SAP HANA database user SAP<SAPSID> SAP HANA database owner

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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Post-Installation PUBLIC 173
SAP System Users

After the installation, ABAP 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.

 Note

Client 066 is no longer available in newly installed SAP systems based on SAP NetWeaver 7.5 or higher. For
more information, see SAP Note 1749142 .

 Note

Client 001 is no longer available in newly installed SAP systems based on SAP S/4HANA and SAP BW/
4HANA.

SAP System 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­
 Note SAP System Parameters [page missions for user management.

This user has only been cre­ 49])

The password of this user is stored in secure storage.
ated if you have installed the Therefore, whenever you change the password of the
application server ABAP for administrator password, you must also change the
an SAP Process Integration password in secure storage.
(PI) 7.5 system or for an SAP
Solution Manager 7.2 sys­  Recommendation
tem.
We recommend that you use strong password
and auditing policies for this user.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
174 PUBLIC Post-Installation
 User User Name Comment

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
 Note fault name J2EE_GUEST (see (UME) of the Java system. It is used for anonymous

This user has only been cre­ SAP System Parameters [page access.

ated if you have installed the 49])

application server ABAP for
an SAP Process Integration
(PI) 7.5 system or for an SAP
Solution Manager 7.2 sys­
tem.

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
 Note tem Parameters [page 49]) function call (RFC) between the ABAP system and

This user has only been cre­ the Java system.

ated if you have installed the

application server ABAP for
an SAP Process Integration
(PI) 7.5 system or for an SAP
Solution Manager 7.2 sys­
tem.

7.23 Performing the Client Copy

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.

 Note

Client 066 is no longer available in newly installed SAP systems based on SAP NetWeaver 7.5 or higher. For
more information, see SAP Note 1749142 .

 Note

Client 001 is no longer available in newly installed SAP systems based on SAP S/4HANA and SAP BW/
4HANA.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Post-Installation PUBLIC 175
Use client 000 as source client for the client copy.

 Note

SAP SCM: If you want to mark the client 001 as not relevant for liveCache, run report /SAPAPO/
OM_NON_LC_RELEVANT_CLT or /SLCA_NON_LC_RELEVANT_CLIENT using transaction SE38.

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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
176 PUBLIC Post-Installation
Next Steps

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 7.3 including Enhancement Package 1

Application Help Function-Oriented View: English
http://help.sap.com/nw731
Application Server Application Server ABAP
● SAP NetWeaver 7.4
Administration of Application Server ABAP Change and
http://help.sap.com/nw74
● SAP NetWeaver 7.5 Transport System BC – Client Copy and Transport

http://help.sap.com/nw75
● SAP NetWeaver Application Server for ABAP 7.51
innovation package
https://help.sap.com/nw751abap
● SAP NetWeaver AS for ABAP 7.52
https://help.sap.com/nw752abap

7.24 Installation or Upgrade of SAP HANA Studio

Here you find documentation about how to install or upgrade the SAP HANA Studio.

To install or upgrade SAP HANA studio, see the documentation SAP HANA Studio Installation and Update Guide
at https://help.sap.com/viewer/p/SAP_HANA_PLATFORM Installation and Upgrade .

7.25 Backing Up the SAP HANA Database

We recommend that you back up the SAP HANA database after the installation has completed.

Back up the SAP HANA database as described in section SAP HANA Database Backup and Recovery of the SAP
HANA Administration Guide, which you can find here:

https://help.sap.com/viewer/p/SAP_HANA_PLATFORM Administration

Alternatively, as of SAP HANA 2.0, you can use the SAP HANA cockpit to do so. For more information, see
section Backup and Recovery of the documentation SAP HANA Administration with SAP HANA Cockpit, which
you can find here:

https://help.sap.com/viewer/product/SAP_HANA_COCKPIT/ Administration

 Note

Make sure that you perform a “Complete Data Backup”.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Post-Installation PUBLIC 177
7.26 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
○ SAP NetWeaver 7.5
http://help.sap.com/nw75 Only Secure Storage in the File System (AS ABAP)

○ SAP NetWeaver Application Server for

ABAP 7.51 innovation package
https://help.sap.com/nw751abap
○ SAP NetWeaver AS for ABAP 7.52
https://help.sap.com/nw752abap

● For the secure storage in the database, 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
○ SAP NetWeaver 7.5
http://help.sap.com/nw75 Only Secure Storage (ABAP) Key Management Using

○ SAP NetWeaver Application Server for Individual Encryption Keys Generating Encryption Keys
ABAP 7.51 innovation package
https://help.sap.com/nw751abap
○ SAP NetWeaver AS for ABAP 7.52
https://help.sap.com/nw752abap

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
178 PUBLIC Post-Installation
More Information

See also the entry Individual Encryption Key for the Secure Storage in table SAP System Parameters in SAP
System Parameters [page 49].

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

Procedure

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Post-Installation PUBLIC 179
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 132], 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.28 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.

2. Enter option 21.

For more information, see the IBM documentation IBM i Backing Up Your System in the IBM Knowledge Center.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
180 PUBLIC Post-Installation
More Information

Restoring a Backup [page 202]

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Post-Installation PUBLIC 181
7.29 Logging on to the SAP Web Dispatcher Management
Console

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 ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
182 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 7.3 including Enhancement Pack­

Application Help Function-Oriented View Application
age 1
Server Application Server Infrastructure Components of
http://help.sap.com/nw731
SAP NetWeaver Application Server SAP Web Dispatcher

Administration of the SAP Web Dispatcher Area menu

Section ”HTTP Handler”

○ SAP NetWeaver 7.4

Application Help Function-Oriented View Application
http://help.sap.com/nw74
Server Application Server Infrastructure Components of
○ SAP NetWeaver 7.5
http://help.sap.com/nw75 SAP NetWeaver Application Server SAP Web Dispatcher

○ SAP NetWeaver Application Server for ABAP 7.51 Administration of the SAP Web Dispatcher Using the Web
innovation package Administration Interface Area menu Section ”HTTP
https://help.sap.com/nw751abap
Handler”
○ SAP NetWeaver AS for ABAP 7.52
https://help.sap.com/nw752abap

Related Information

ASCS Instance with Integrated SAP Web Dispatcher [page 32]

7.30 SAP Web Dispatcher Configuration (Optional)

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:

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Post-Installation PUBLIC 183
SAP Release and SAP Library Quicklink SAP Library Path (Continued)

● SAP NetWeaver 7.3 including Enhancement Package

Application Help Function-Oriented View Application
1
Server Application Server Infrastructure Components of
http://help.sap.com/nw731
SAP NetWeaver Application Server SAP Web Dispatcher
● SAP NetWeaver 7.4
http://help.sap.com/nw74
● SAP NetWeaver 7.5
http://help.sap.com/nw75
● SAP NetWeaver Application Server for ABAP 7.51
innovation package
https://help.sap.com/nw751abap
SAP NetWeaver AS for ABAP 7.52
https://help.sap.com/nw752abap

Related Information

ASCS Instance with Integrated SAP Web Dispatcher [page 32]

7.31 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 34].

You can find all relevant configuration information in the gateway documentation in the SAP Library at:

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

● SAP NetWeaver 7.3 including Enhancement Package Application Help SAP NetWeaver Library: Function-
1 Oriented View Application Server Application Server
http://help.sap.com/nw731 Infrastructure Connectivity Gateway

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
184 PUBLIC Post-Installation
 SAP Release and SAP Library Quicklink SAP Library Path (Continued)

● SAP NetWeaver 7.4 Application Help SAP NetWeaver Library: Function-

http://help.sap.com/nw74 Oriented View Application Server Application Server
● SAP NetWeaver 7.5 Infrastructure Components of SAP NetWeaver Application
http://help.sap.com/nw75 Server Gateway
● SAP NetWeaver Application Server for ABAP 7.51
innovation package
https://help.sap.com/nw751abap
● SAP NetWeaver AS for ABAP 7.52
https://help.sap.com/nw752abap

Related Information

ASCS Instance with Integrated Gateway [page 34]

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Post-Installation PUBLIC 185
8 Additional Information

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 ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
186 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 7.3 including Enhancement Package

Application Help Function-Oriented View: English
1
Security Identity Management User and Role
http://help.sap.com/nw731
Administration of Application Server ABAP Configuration of
● SAP NetWeaver 7.4
http://help.sap.com/nw74 User and Role Administration Directory Services LDAP

● SAP NetWeaver 7.5 Connector

http://help.sap.com/nw75
● SAP NetWeaver Application Server for ABAP 7.51
innovation package
https://help.sap.com/nw751abap
● SAP NetWeaver AS for ABAP 7.52
https://help.sap.com/nw752abap

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.

Features

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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Additional Information PUBLIC 187
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.
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 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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
188 PUBLIC Additional Information
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.3 including Enhancement Package 1

Application Help Function-Oriented View: English
http://help.sap.com/nw731
Solution Life Cycle Management SAP Management
● SAP NetWeaver 7.4
Console
http://help.sap.com/nw74
● SAP NetWeaver 7.5
http://help.sap.com/nw75
● SAP NetWeaver Application Server for ABAP 7.51
innovation package
https://help.sap.com/nw751abap
● SAP NetWeaver AS for ABAP 7.52
https://help.sap.com/nw752abap

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://help.sap.com/viewer/swpm10guides

 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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Additional Information PUBLIC 189
 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 127] 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.

8.2 Multiple SAP Systems on a Single Host

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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
190 PUBLIC Additional Information
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
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 186].

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Additional Information PUBLIC 191
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

8.4 Installing the SAP Host Agent Separately

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 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 193]).

Apart from using the SAP Management Console (SAP MC), you can also use commands to Start or stop SAP
system instances [page 196]

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
192 PUBLIC Additional Information
8.5.1 Starting and Stopping SAP System Instances Using the
SAP Management Console

You can start and stop all instances of your SAP system using the SAP Management Console (SAP MC).

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.

 Note

If your Web browser no longer supports Java applet technology, you can configure the SAP MC to run
locally on your PC. For more information, see section Configuring SAP MC locally in SAP Note 1014480 .

Context

 Recommendation

If you experience any issues when starting or using the SAP MC, refer to SAP Note 1153713 .

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Additional Information PUBLIC 193
● 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.3 including Enhancement Package 1

Application Help Function-Oriented View: English
http://help.sap.com/nw731
Solution Life Cycle Management SAP Management
○ SAP NetWeaver 7.4
http://help.sap.com/nw74 Console

○ SAP NetWeaver 7.5

http://help.sap.com/nw75
○ SAP NetWeaver Application Server for ABAP 7.51
innovation package
https://help.sap.com/nw751abap
○ SAP NetWeaver AS for ABAP 7.52
https://help.sap.com/nw752abap

● 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 7.3 including Enhancement Package 1

Application Help Function-Oriented View: English
http://help.sap.com/nw731
Solution Life Cycle Management SAP Microsoft
○ SAP NetWeaver 7.4
http://help.sap.com/nw74 Management Console: Windows

○ SAP NetWeaver 7.5

http://help.sap.com/nw75
○ SAP NetWeaver Application Server for ABAP 7.51
innovation package
https://help.sap.com/nw751abap
○ SAP NetWeaver AS for ABAP 7.52
https://help.sap.com/nw752abap

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
194 PUBLIC Additional Information
 This starts the SAP MC Java applet.

 Note

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 primary application server instance D[VEBMGS]<Instance_Number>.

 Note

In SAP systems based on SAP NetWeaver 7.5 or higher, the primary application server instance is
named D<Instance_Number>.

In SAP systems based on SAP NetWeaver 7.4 or lower, the primary application server instance is
named DVEBMGS<Instance_Number>.

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Additional Information PUBLIC 195
 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.

Log in as user <sapsid>adm.

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 D[VEBMGS]<Instance_Number> .

 Note

In SAP systems based on SAP NetWeaver 7.5 or higher, the primary application server instance is
named D<Instance_Number>.

In SAP systems based on SAP NetWeaver 7.4 or lower, the primary application server instance is
named DVEBMGS<Instance_Number>.

3. Stop the ABAP central services instance ASCS<Instance_Number>.

4. Stop the database instance.

8.5.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 an additional application server instance is

D<Instance_Number>.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
196 PUBLIC Additional Information
 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.

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.

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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Additional Information PUBLIC 197
8.6 IBM i-specific Information

Here you can find additional information about the IBM i:

● Correcting Errors in RFC Steps [page 198]

● IBM i Library Structure [page 199]
● IBM i Integrated File System [page 200]
● Restoring a Backup [page 202]
● Editing Stream Files [page 204]
● RFC SDK [page 205]

8.6.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).

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
198 PUBLIC Additional Information
 Cause of the Error User Actions

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Additional Information PUBLIC 199
 Library Description

R3<SAPSID>JRN 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.6.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.

Use

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
200 PUBLIC Additional Information
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 204].

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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Additional Information PUBLIC 201
Hard and Soft Links

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.6.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 ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
202 PUBLIC Additional Information
 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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Additional Information PUBLIC 203
  Note

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
204 PUBLIC Additional Information
8.6.6 RFC SDK

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Additional Information PUBLIC 205
  Example

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
206 PUBLIC Additional Information
  Caution

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

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

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.

The following table provides information about deleting a complete system or single instances with the
installer.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Additional Information PUBLIC 207
 Deletion of Remarks

Standard system

 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

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

 Note

Only the SAP systems components residing on the IBM i are deleted. This will not delete the HANA
database.

 Caution

This description assumes that the installation of your SAP system has been performed using SAP standard
tools according to the installation documentation.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
208 PUBLIC Additional Information
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 210].

2. To add the kernel library to the library list enter the following command:
ADDLIBLE LIB(SAP<SAPSID>IND)

 Caution

If you want to delete a complete ABAP system but not the ABAP database instance, delete all instances
but do not delete the system (on the database instance host) at the end.

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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Additional Information PUBLIC 209
  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)
RMVDIR DIR('/usr/sap/trans/config/<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.9 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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
210 PUBLIC Additional Information
  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 208].

 Caution

This description assumes that the installation of your SAP system has been performed using SAP standard
tools according to the installation documentation.

Procedure

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 system but not the ABAP database instance, delete all instances but
do not delete the system (on the database instance host) at the end.

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

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Additional Information PUBLIC 211
A Appendix

A.1 Online Information from SAP

More information is available online as follows:

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
212 PUBLIC Appendix
Important Disclaimers and Legal Information

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

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

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

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

Videos Hosted on External Platforms

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

Beta and Other Experimental Features

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

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

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on IBM i : SAP HANA Database
Important Disclaimers and Legal Information PUBLIC 213
www.sap.com/contactsap

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

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

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

Some software products marketed by SAP SE and its distributors

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

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

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

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

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

additional trademark information and notices.

THE BEST RUN