Installation Guide | PUBLIC

Software Provisioning Manager 1.0 SP42

Document Version: 4.8 – 2024-10-07

Installation of SAP Systems Based on the

Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
© 2024 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN

Content

1 About this Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.1 SAP Products Based on SAP NetWeaver 7.3 EHP1 to 7.52 Supported for Installation Using
Software Provisioning Manager 1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.2 Naming Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.3 Constraints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
1.4 Before You Start. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.5 SAP Notes for the Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.6 New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2 Installation Options Covered by this Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

2.1 Standard System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.2 Distributed System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.3 High-Availability System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.4 Additional Application Server Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.5 Splitting off an ABAP Central Services Instance from an Existing Primary Application Server
Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.6 ASCS Instance with Embedded SAP Web Dispatcher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
2.7 ASCS Instance with Embedded Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

3 Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3.1 Planning Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3.2 Installation Using a Stack XML File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3.3 Hardware and Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Running the Prerequisites Check in Standalone Mode (Optional). . . . . . . . . . . . . . . . . . . . . . . . 40
Requirements for the SAP System Hosts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3.4 Planning User and Access Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
3.5 Basic Installation Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
SAP System Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
SAP System Database Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Additional Parameters when Installing SAP Process Integration 7.5 or SAP Solution Manager
7.2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Additional Parameters When Using a Stack XML File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66
Parameters for Additional Components to be Included in the ASCS Instance. . . . . . . . . . . . . . . . 68
3.6 Distribution of SAP System and SAP MaxDB Components to Disks. . . . . . . . . . . . . . . . . . . . . . . . . 69
3.7 SAP MaxDB System Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
3.8 SAP System Transport Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
3.9 Planning the Switchover Cluster for High Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
2 PUBLIC Content
4 Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
4.1 Preparation Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
4.2 Creating Operating System Users and Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
4.3 Required File Systems and Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
SAP Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
SAP MaxDB Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Setting Up File Systems for a High-Availability System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89
4.4 Using Virtual Host Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
4.5 Performing Switchover Preparations for High Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
4.6 Installing the SAP Front-End Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
4.7 Preparing the Installation Media. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Media Required for the Installation - Listed by SAP System Instance. . . . . . . . . . . . . . . . . . . . . .96

5 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
5.1 Installation Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
5.2 Exporting and Mounting the Transport Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
5.3 Exporting and Mounting Global Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
5.4 Specifying the Initial Data Source of the User Management Engine. . . . . . . . . . . . . . . . . . . . . . . . . 119
5.5 Prerequisites for Running Software Provisioning Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
5.6 Running Software Provisioning Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
5.7 Additional Information about Software Provisioning Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Useful Information about Software Provisioning Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
System Provisioning Using an Input Parameter File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Restarting Interrupted Processing of Software Provisioning Manager. . . . . . . . . . . . . . . . . . . . 138
Entries in the Services File Created by Software Provisioning Manager. . . . . . . . . . . . . . . . . . . . 141
Troubleshooting with Software Provisioning Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142
Using the Step State Editor (SAP Support Experts Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

6 Post-Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
6.1 Post-Installation Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
6.2 Logging On to the Application Server ABAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
6.3 SAP NetWeaver 7.4 and Higher: Performing Automated Initial Setup (Optional). . . . . . . . . . . . . . . . 148
6.4 Installing the SAP License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
6.5 High Availability: Setting Up Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151
6.6 Configuring the Remote Connection to SAP Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
6.7 Enabling Note Assistant to Apply Note Corrections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152
6.8 Configuring Documentation Provided on the SAP Help Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
6.9 Performing the Consistency Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
6.10 Configuring the Change and Transport System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156
6.11 Connecting the System to SAP Solution Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158
6.12 Applying the Latest Kernel and Support Package Stacks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
6.13 Performing Post-Installation Steps for the ABAP Application Server. . . . . . . . . . . . . . . . . . . . . . . . 161

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Content PUBLIC 3
6.14 Systems Based on SAP NetWeaver AS for ABAP 7.52 only: Switching to Standalone Enqueue
Server 2 and Enqueue Replicator 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
6.15 SAP Solution Manager 7.2, SAP Process Integration 7.5 only: Enabling HTTPS Communication for
ABAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
6.16 Installing Additional Languages and Performing Language Transport. . . . . . . . . . . . . . . . . . . . . . . 165
6.17 Configuring the User Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
6.18 Ensuring User Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
6.19 Performing the Client Copy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172
6.20 Installing or Upgrading Database Studio for SAP MaxDB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
6.21 Secure Sockets Layer Protocol for Database Server Communication. . . . . . . . . . . . . . . . . . . . . . . 175
Configuring the SSL Communication between the Application Server and the Database Server
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176
6.22 Backing Up the SAP MaxDB Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
6.23 Updating the Database Software to the Current Release. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
6.24 Linux only: Setting Up the Teradata Bridge. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
6.25 SAP Systems Based on SAP NetWeaver 7.4 and Higher: Changing Keys for the Secure Storage
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
6.26 Performing a Full Installation Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
6.27 Logging on to the SAP Web Dispatcher Management Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
6.28 SAP Web Dispatcher Configuration (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
6.29 Gateway Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

7 Additional Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

7.1 Integration of LDAP Directory Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
7.2 Installation of Multiple Components in One Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
7.3 Creating a User for LDAP Directory Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
7.4 Exporting and Mounting Directories via NFS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Exporting and Mounting Directories via NFS for AIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194
Exporting and Mounting Directories via NFS for HP-UX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Exporting and Mounting Directories via NFS for Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Exporting and Mounting Directories via NFS for Oracle Solaris. . . . . . . . . . . . . . . . . . . . . . . . . 196
7.5 Heterogeneous SAP System Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
7.6 Installing the SAP Host Agent Separately. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198
7.7 Splitting Off an ABAP Central Services Instance from an Existing Primary Application Server
Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
7.8 Starting and Stopping SAP System Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Starting and Stopping SAP System Instances Using the SAP Management Console. . . . . . . . . . 202
Starting and Stopping SAP System Instances Using Commands. . . . . . . . . . . . . . . . . . . . . . . 205
7.9 Uninstalling an SAP System or Single Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .208
7.10 Switching to Native systemd Support for sapstartsrv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
4 PUBLIC Content
Document History

 Note

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

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

Version Date Description

4.8 2024-10-07 Updated version for software provisioning manager 1.0 SP42 (SL Toolset 1.0 SP42)

4.7 2024-05-27 Updated version for software provisioning manager 1.0 SP41 (SL Toolset 1.0 SP41)

4.6 2024-02-12 Updated version for software provisioning manager 1.0 SP40 (SL Toolset 1.0 SP40)

4.5 2023-10-09 Updated version for software provisioning manager 1.0 SP39 (SL Toolset 1.0 SP39)

Windows operating systems no longer supported for software provisioning manager

1.0 SP39 and higher, according to SAP Note 2998013 , have been removed.

4.4.1 2023-10-09 Updated version for software provisioning manager 1.0 SP38 (SL Toolset 1.0 SP38):
Last version containing information about no longer supported Windows operating
systems according to SAP Note 3346502 .

4.4 2023-05-26 Updated version for software provisioning manager 1.0 SP38 (SL Toolset 1.0 SP38)

4.3 2023-02-13 Updated version for software provisioning manager 1.0 SP37 (SL Toolset 1.0 SP37)

4.2 2022-10-10 Updated version for software provisioning manager 1.0 SP36 (SL Toolset 1.0 SP36)

Operating systems and CPU architectures no longer supported according to SAP

Note 2998013 have been removed.

4.1.1 2022-10-10 Updated version for software provisioning manager 1.0 SP35 (SL Toolset 1.0 SP35):
Last version containing information about no longer supported operating systems
and CPU architectures according to SAP Note 2998013 .

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

4.15 2022-03-25 Linux only: Updated version of the installation guide with systemd released (see
SAP Note 3139184 ).

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

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Document History PUBLIC 5
Version Date Description

3.8 2021-06-21 Updated version for software provisioning manager 1.0 SP32 (SL Toolset 1.0 SP32)

3.7 2021-02-15 Updated version for software provisioning manager 1.0 SP31 (SL Toolset 1.0 SP31)

3.6 2020-10-05 Updated version for software provisioning manager 1.0 SP30 (SL Toolset 1.0 SP30)

3.5 2020-06-08 Updated version for software provisioning manager 1.0 SP29 (SL Toolset 1.0 SP29)

3.4 2020-01-20 Updated version for software provisioning manager 1.0 SP28 (SL Toolset 1.0 SP28)

3.3 2019-09-16 Updated version for software provisioning manager 1.0 SP27 (SL Toolset 1.0 SP27)

3.2 2019-05-27 Updated version for software provisioning manager 1.0 SP26 (SL Toolset 1.0 SP26)

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

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

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

• New Features:
• New Software Provisioning Manager 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, Addi-
tional Parameters When Using a Stack XML File
• 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 Replication Server 2

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
6 PUBLIC Document History
 Version Date Description

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

• New Features:
• Digital signature check for installation archives, documented in: New Fea-
tures, Downloading SAP Kernel Archives (Archive-Based Installation) Ar-
chive-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
• Software provisioning manager Log Files Improvements, documented in:
New Features, Useful Information about the Software Provisioning Manager,
Troubleshooting with the Software Provisioning Manager
• Secure ABAP message server connection, documented in: New Features,
SAP System Parameters
• Enabling IPv6, documented in: New Features, Prerequisites for Running the
Software Provisioning Manager
• 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-UI - has been deprecated with SP22. As of SP22, SL-UI is the only available
GUI of the software provisioning manager:
• The following sections which were explicitely related to Java SDT GUI were
completely removed from this documentation: Performing a Remote Instal-
lation Remote Processing of the Software Provisioning Manager ( Java SDT
GUI only), Starting the Java SDT GUI Separately, Running the Software
Provisioning Manager in Accessibility Mode (general accessibility informa-
tion was moved to Useful Information About the Software Provisioning Man-
ager).
• The Java SDT GUI-specific information was removed from the common
software provisioning manager sections: Running the Software Provisioning
Manager, Useful Information About the Software Provisioning Manager, In-
terrupted Processing of the Software Provisioning Manager, Troubleshooting
with the Software Provisioning Manager, Deleting an SAP System or Single
Instances
• New section Using the Step State Editor (SAP Support Experts Only) was added
to section Additional Information About the Software Provisioning Manager

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Document History PUBLIC 7
Version Date Description

2.7 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 Soft-
ware Provisioning Manager, Preparing the Installation Media .
This feature implies that section Creating Kernel Archives from an Existing
SAP System has been deleted from this documentation because the re-
lated option in the software provisioning manager had to be removed.
• Download Media for a Maintenance Plan, documented in: New Features,
Downloading Media for a Maintenance Plan
• SAP Host Agent Upgrade , documented in: New Features, SAP System Pa-
rameters, Downloading SAP Kernel Archives (Archive-Based Installation)
• Load tools are now available as LOADTOOLS.SAR in the Software Provision-
ing Manager archive, documented in: New Features, Downloading and Ex-
tracting the Software Provisioning Manager Archive
• Simplified additional application server instance installation, documented
in: New Features, Preparing the Installation Media, Downloading SAP Kernel
Archives (Archive-Based Installation)

2.6 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-UI”, documented
in: Prerequisites for Running the Software Provisioning Manager, Running
the Software Provisioning Manager, Useful Information About the Software
Provisioning Manager
• Option for choosing to install an embedded 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 Instance , Post-Installation Checklist, SAP Gateway
Configuration
• Cleanup of operating system users, documented in: SAP System Parame-
ters, Creating Operating System Users and Groups

2.5 2017-02-07 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 XML File

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
8 PUBLIC Document History
 Version Date Description

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

• New Features:
Option to choose installing an embedded SAP Web Dispatcher during the ASCS
instance installation, documented in: ASCS Instance with Embedded SAP Web
Dispatcher [page 32].
Using RMOSSWPM*.SAR instead of SWPM*.SAR for outdated OS versions not

supported by SAP kernel 7.40 and higher, documented in: Introduction

Constraints

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

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

• Preparing the Installation Media [page 95] Downloading Specific

Installation Archives (Archive-Based Installation)

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

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

2.0 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 2014-11-24 Updated version for software provisioning manager 1.0 SP07 (SL Toolset 1.0 SP12)

1.7 2014-07-07 Updated version

Instead of a separate installation guide for each UNIX-based operating system,

we now deliver a single installation guide for all UNIX-based operating systems.
Sections that are only relevant for one or more specific operating systems are
highlighted accordingly.

1.6 2014-03-17 Updated version

1.5 2013-10-28 Updated version

1.4 2013-07-15 Updated version

1.3 2013-04-02 Updated version

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Document History PUBLIC 9
1 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 SP42, which is part of
SL Toolset 1.0 SP42.

This guide is valid for the operating systems AIX, HP-UX, Linux, and Solaris, and 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 11].

 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/docs/
SAP_LANDSCAPE_MANAGEMENT_ENTERPRISE .

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

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

 Caution

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

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

This section lists the naming conventions that are currently apply for the software provisioning
manager 1.0 and terms used in this documentation.

Constraints [page 12]

This section lists the naming constraints that are currently valid for the software provisioning manager
1.0 and this documentation.

Before You Start [page 14]

Make sure that you have read the release-specific “Master Guide” 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 15]

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

New Features [page 16]

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
10 PUBLIC About this Document
1.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

1.2 Naming Conventions

This section lists the naming conventions that are currently apply for the software provisioning manager 1.0
and terms used in this documentation.

• The 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 UNIX: SAP MaxDB
About this Document PUBLIC 11
 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 95].
This way, you automatically get the latest version with the latest fixes of the tool and supported
processes. For more information about the 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 .
The “SAPinst” tool has been renamed to “software provisioning manager”, but the terms “SAPinst” and
“sapinst” are still used in:
• The name of the technical framework of the software provisioning manager. For more information
about the current SAPinst Framework version, see SAP Note 3207613 (SAPinst Framework 753
Central Note).
• Texts and screen elements in the the software provisioning manager's SL-UI
• 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 16].
• “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 liveCache” refers to “SAP MaxDB liveCache”.

• “SAP liveCache client” refers to “SAP MaxDB liveCache client”.

1.3 Constraints
This section lists the naming constraints that are currently valid for the software provisioning manager 1.0 and
this documentation.

• Effective immediately, the software provisioning manager no longer supports the deprecated CPU
architectures and/or operating system versions listed in SAP Note 2998013 .

 Note

• If your current operating system is listed as deprecated in SAP Note 2998013 , we strongly
recommend that you migrate to a supported platform.
• If you continue to run Software Provisioning Manager on the deprecated CPU architectures and/or
operating system versions listed in SAP Note 2998013 , you do so at your own risk and without
support from SAP. The software provisioning manager 1.0 SP36 and higher will still run on the
deprecated CPU architectures and/or operating system versions listed in SAP Note 2998013
but it may run into an error. When you start the software provisioning manager, you will see a
warning like the following: “Platform Support : Support for SAP JVM on PPC64 big endian for Linux

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
12 PUBLIC About this Document
 ends June 30 th, 2022. See SAP note 2998013.” If you run into an issue, you must use the “frozen”
software provisioning manager 1.0 SP35 software and the related installation guide. For more
information, see SAP Note 3220901 .

• End of support for SAP products based on SAP NetWeaver 7.10, 7.11, 7.20, 7.30, 7.40 SR1

 Note

SAP products based on SAP NetWeaver 7.10, 7.11, 7.20, 7.30, 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 11] and SAP Note 1680045 to ensure that the installation
options you want to perform are already supported. For information about supported operating system
and database platforms, see the Product Availability Matrix at http://support.sap.com/pam .
• Note that a complete system installation from scratch is not available for every product. For some products
- such as SAP NetWeaver 7.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.
• The startsap and stopsap commands have been deprecated. For more information and for information
on alternatives, see Starting and Stopping SAP System Instances Using Commands [page 205].
• 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 .

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
About this Document PUBLIC 13
1.4 Before You Start

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

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

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

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

Document Internet Address

Master Guide – SAP NetWeaver 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 http://help.sap.com/scm

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

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
14 PUBLIC About this Document
 Document Internet Address

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

SAP NetWeaver 7.3
Installation and Upgrade

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

2365014 Installation of SAP Systems Based on SAP Platform-specific information about the SAP sys-
NetWeaver: SAP MaxDB tem installation (ABAP and Java) and corrections
to this documentation

820824 FAQ: SAP MaxDB/liveCache technology Frequently asked questions (FAQ) on SAP MaxDB

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

1972803 SAP on AIX: Recommendations This SAP Note contains recommendations and
clarifications for many topics relevant for SAP on
AIX.

1075118 SAP on HP-UX: FAQ This SAP Note contains information that is spe-
cific to the SAP system installation on HP-UX

2369910 SAP Software on Linux: General information This SAP Note contains Linux-specific informa-
tion about the SAP system installation

1669684 SAP on Oracle Solaris 11 This SAP Note contains information and referen-
ces to SAP Notes relevant for Solaris 11

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
About this Document PUBLIC 15
SAP Note Number Title Description

1067221 Composite SAP Note for heterogeneous instal- This SAP Note and its related SAP Notes de-
lation scribe the released operating system and data-
base combinations for heterogeneous SAP sys-
tems 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 installa- Information about the ABAP Support Package
tions/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 installa- Information about the ABAP Support Package
tions/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.

886535 Downloading multispanning archives Downloading multispanning archives

1.6 New Features

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

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
16 PUBLIC About this Document
 Feature Description Availability

SAP MaxDB: New As of SAP MaxDB version 7.9.11.07, SAP MaxDB liveCache version Software provisioning manager
structure of soft- 1.0 SP42 (SL Toolset 1.0 SP42)
7.9.11.08, a new structure for the software packages is used. For
ware packages
more information, see Media Required for the Installation - Listed
by SAP System Instance [page 96] and SAP Note 3524673 .

Linux only: Pace- As of IBM Db2 11.5 Mod Pack 8, you can install the Pacemaker Software provisioning manager
maker 1.0 SP40 (SL Toolset 1.0 SP40)
cluster software during an SAP system installation using software
provisioning manager. For more information, see Planning the
Switchover Cluster for High Availability [page 74]

New SAPinst Frame- The SAPinst framework patch level has been upgraded from ver- software provisioning manager
work Version 753 sion 749 (SAP Note 2393060 SAPinst Framework 749 Central 1.0 SP36 (SL Toolset 1.0 SP36)
Note) to 753. For more information, see SAP Note 3207613 SA-
Pinst Framework 753 Central Note.

Linux: Native sys- Linux only: Starting with SUSE Linux Enterprise Server 15, Red software provisioning manager
temd support 1.0 SP34 (SL Toolset 1.0 SP34)
Hat Enterprise Linux 8, and Oracle Linux 8, and the respective
SAP kernel patch levels, native support for the software suite sys-
temd for Linux is available for SAP systems. For more information
about Linux with systemd, see SAP Note 3139184 . When you
install SAP systems using software provisioning manager 1.0 SP
34 or higher, native systemd support is automatically activated.

Support of AIX 7.3 AIX 7.3 is now supported for all software lifecycle management software provisioning manager
options from software provisioning manager. For more informa- 1.0 SP34 (SL Toolset 1.0 SP34)
tion, see SAP Note 3104875 .

Switch from Kernel 7.21 has reached end of maintenance. In addition, some software provisioning manager
7.21_EXT Kernel to 1.0 SP31 (SL Toolset 1.0 SP31)
issues 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
53].

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

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
About this Document PUBLIC 17
Feature Description Availability

Validity Check for If you perform an installation using a Stack XML file and choose software provisioning manager
1.0 SP23 (SL Toolset 1.0 SP23)
SUM*.SAR Archive to extract the SUM*.SAR archive, the validity of this archive is
now checked by the software provisioning manager. For more
information , see entry Extract the SUM*.SAR Archive in Additional
Parameters When Using a Stack XML File [page 66].

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

software provision- software provisioning manager log files are now available immedi- software provisioning manager
ing manager Log ately after software provisioning manager has been started, that 1.0 SP22 (SL Toolset 1.0 SP22)
Files Improvements is before a product has been selected on the Welcome screen.
For more information, see Useful Information about Software Pro-
visioning Manager [page 131] and Troubleshooting with Software
Provisioning Manager [page 142].

Digital Signature The digital signature of installation archives is checked auto- software provisioning manager
matically by software provisioning manager during the Define 1.0 SP22 (SL Toolset 1.0 SP22)
Check of Installation
Parameters phase while processing the Software Package Browser
Archives
screens. As of now software provisioning manager only accepts
archives whose digital signature has been checked. For more in-
formation, see Downloading SAP Kernel Archives (Archive-Based
Installation) [page 102] .

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

 Note
This feature enhances feature LOADTOOLS.SAR archive
in Software Provisioning Manager of software provision-
ing manager 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 software provisioning manager
1.0 SP22 (SL Toolset 1.0 SP22)
using Internet Protocol Version 6 (IPv6).

For more information, see Prerequisites for Running Software Pro-

visioning Manager [page 120].

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

Media Signature The digital signature of media is checked automatically by the software provisioning manager
1.0 SP21 (SL Toolset 1.0 SP21)
Check software provisioning manager during the Define Parameters
phase while processing the Media Browser screens. The software
provisioning manager only accepts media whose digital signature
has been checked.

For more information, see Preparing the Installation Media [page

95] and Running the software provisioning manager [page 124].

SAP Host Agent Up- During the Define Parameters phase of the installation, software software provisioning manager
grade During the In- provisioning manager prompts you whether you want to upgrade 1.0 SP21 (SL Toolset 1.0 SP21)
stallation (Optional) an existing version 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 Gen-
eral Parameters table in SAP System Parameters [page 54] .

Simplified Addi- During an additional application server installation, SAP kernel software provisioning manager
tional Application archives are only prompted if they cannot be retrieved from the 1.0 SP21 (SL Toolset 1.0 SP21)
Server Instance In- primary application server instance of the existing SAP system.
stallation For more information, see Preparing the Installation Media [page
95].

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

SL-UI with SAPINST With the new software provisioning manager framework version software provisioning manager
7.49 SAPINST 7.49, you can now use the new SAPUI5-based graphical 1.0 SP20 (SL Toolset 1.0 SP20)
user interface (GUI) “SL-UI”. For more information, see Useful In-
formation about Software Provisioning Manager [page 131], Run-
ning Software Provisioning Manager [page 124] .

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)
operating system users are to be removed from group sapinst
after the execution of software provisioning manager has com-
pleted.

For more information, see Operating System Users in SAP System

Parameters [page 54].

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 Embedded Gate-
way [page 34]

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

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

In addition, check SAP Note 1680045 whether additional infor-

mation is available.

Archive-based Lan- If you perform an installation using a Stack XML file, you can now software provisioning manager
guage Installation add language archives to the download basket and use them for 1.0 SP19 (SL Toolset 1.0 SP19)
language installation. This feature is currently restricted to the
latest products only. For more information, see Additional Param-
eters When Using a Stack XML File [page 66]

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

Web Dispatcher [page 32]

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

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 Diag-
nostics Agent Setup Guide.

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

System Provision- All system provisioning tasks (installation, system copy, system software provisioning manager
ing for SAP rename) are available for the new SAP NetWeaver 7.5 release. 1.0 SP09 (SL Toolset 1.0 SP15)
NetWeaver 7.5 and
The Dual Stack option, which integrates an AS ABAP and AS
SAP NetWeaver 7.5-
Java 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 direc-
tory has been renamed from /usr/sap/<SAPSID>/
DVEBMGS<Instance_Number> to /usr/sap/<SAPSID>/
D<Instance_Number>.
For more information, see SAP Directories [page 83].
• Declustering and depooling of tables during the installation
is enabled by default. For more information, see SAP Note
1892354 .

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 1.0 SP09 (SL Toolset 1.0 SP15)
Manager 7.2 release. 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.

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

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 software provisioning manager using a Stack XML software provisioning manager
Stack XML File file generated by the Maintenance Planner. The configuration pa- 1.0 SP07 (SL Toolset 1.0 SP12)
rameters in this file can then be used by software provisioning
manager to improve the integration 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 XML File

[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 54].

Feedback Evaluation SAP SE’s aim is to provide fast and efficient procedures. To eval- software provisioning manager
Form uate the procedure you just carried out, we need information 1.0 SP07 (SL Toolset 1.0 SP12)
generated by the tool during process execution and your experi-
ence with the tool itself. A new evaluation form contains a simple
questionnaire and XML data generated during the procedure.

Port 4239 is used for displaying the feedback evaluation form.

For more information, see Prerequisites for Running Software Pro-
visioning Manager [page 120].

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

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 .

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
About this Document PUBLIC 23
2 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.

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

Standard System [page 24]

Distributed System [page 25]

High-Availability System [page 26]

Additional Application Server Instance [page 28]

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

ASCS Instance with Embedded SAP Web Dispatcher [page 32]

ASCS Instance with Embedded Gateway [page 34]

2.1 Standard System

You can install a standard system 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
In a standard
• Optionally, you can install the ASCS instance with an embedded SAP Web Dispatcher. For more
information, see ASCS Instance with Embedded SAP Web Dispatcher [page 32].
• Optionally, you can install the ASCS instance with an embedded gateway. For more information, see
ASCS Instance with Embedded Gateway [page 34].
• 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 UNIX: SAP MaxDB
24 PUBLIC Installation Options Covered by this Guide
 Standard ABAP System

2.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 embedded SAP Web Dispatcher. For more
information, see ASCS Instance with Embedded SAP Web Dispatcher [page 32].
• Optionally, you can install the ASCS instance with an embedded gateway. For more information, see
ASCS Instance with Embedded Gateway [page 34].
• 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 28].

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Installation Options Covered by this Guide PUBLIC 25
 Distributed ABAP System

2.3 High-Availability System

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

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

There are the following instances:

• ABAP central services instance (ASCS instance)

Contains the ABAP message server and the Standalone Enqueue Server

 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 2 , and
Systems Based on SAP NetWeaver AS for ABAP 7.52 only: Switching to Standalone Enqueue Server 2
and Enqueue Replicator 2 [page 164] .

• Optionally you can install the ASCS instance with an embedded SAP Web Dispatcher. For more
information, see ASCS Instance with Embedded 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 UNIX: SAP MaxDB
26 PUBLIC Installation Options Covered by this Guide
 • Optionally you can install the ASCS instance with an embedded gateway. For more information, see
ASCS Instance with Embedded 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 164].

• 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 28].

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 UNIX: SAP MaxDB
Installation Options Covered by this Guide PUBLIC 27
 High-Availability System

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

 Note

If you want to install additional application server instances running on an operating system other than the
primary application server instance, see Heterogeneous SAP System Installation [page 198]. For example,
you need to do this if your primary application server instance runs on Linux for z System but the additional
application server instance is to run on Windows.

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 on which the primary application server instance
and the database instance run

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
28 PUBLIC Installation Options Covered by this Guide
 • On dedicated hosts

Additional Application Server Instance for a Standard ABAP System

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

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 UNIX: SAP MaxDB
Installation Options Covered by this Guide PUBLIC 29
 Additional Application Server Instance for a Distributed ABAP System

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

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 UNIX: SAP MaxDB
30 PUBLIC Installation Options Covered by this Guide
 Additional Application Server Instance for a High-Availability System

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

2.5 Splitting off an ABAP Central Services Instance from an

Existing Primary Application Server Instance

The ABAP central services instance (ASCS instance) consists of the essential ABAP enqueue and message
system services only. With a separate ASCS instance, it is easier for you to later turn your SAP system into a
high-availability system.

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

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

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

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Installation Options Covered by this Guide PUBLIC 31
2.6 ASCS Instance with Embedded SAP Web Dispatcher

You can install an SAP Web Dispatcher embedded 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 embedded 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
embedded 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.

ASCS Instance with Embedded 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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
32 PUBLIC Installation Options Covered by this Guide
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://support.sap.com/
sltoolset 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 .

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Installation Options Covered by this Guide PUBLIC 33
2.7 ASCS Instance with Embedded Gateway

You can install a gateway embedded 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.

Gateway Embedded 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://support.sap.com/sltoolset Installation Option of Software Provisioning Manager 1.0
Installation Guides - Standalone Engines and Clients - Software Provisioning Manager 1.0 Standalone Gateway
Instance .

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
34 PUBLIC Installation Options Covered by this Guide
Related Information

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Installation Options Covered by this Guide PUBLIC 35
3 Planning

3.1 Planning Checklist

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

• Standard, distributed, or high-availability system

• Additional application server instance

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

Prerequisites

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

Standard, Distributed, or High-Availability System

 Note

In a standard system, all mandatory instances are installed on one host. Therefore, if you are installing
a standard system, you can ignore references to other hosts. Since an SAP system on IBM Db2 for
z/OS system is always a distributed constellation, we only offer two installation options: standard or
high-availability.

1. Installation Using a Stack XML File [page 37]:

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

 Recommendation

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
36 PUBLIC Planning
 2. Installation Using a Stack XML File [page 37]:
If you want to install an SAP Process Integration 7.5 system or an SAP Solution Manager 7.2 system
comprising ABAP and Java, both the ABAP and the Java system must be installed with the identical
Support Package (SP) level.
3. You check the hardware and software requirements [page 39] on every installation host.
4. You plan how to set up user and access management [page 52].
5. You identify Basic SAP System Installation Parameters [page 53].
6. You plan your system configuration [page 71].
7. You decide on the transport host to use [page 73].
8. You decide whether you want to integrate LDAP Directory Services in your SAP system [page 185].
9. To install a high-availability system, you read Planning the Switchover Cluster for High Availability [page
74].
10. Optionally, you decide whether you want to install multiple components in one database (MCOD) [page
190].
11. Continue with Preparation [page 77].

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 53].
3. Continue with Preparation [page 77].

3.2 Installation Using a Stack XML File

The option to perform an installation using a Stack XML 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
• Software Update Manager (abbreviated as “SUM”)

The software provisioning manager 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 XML file for new products, such as SAP
S/4HANA 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 UNIX: SAP MaxDB
Planning PUBLIC 37
Restrictions

You cannot perform a target system installation in the context of a system copy as an installation with a Stack
XML 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 XML file provides the following features:

• You can use a Stack XML file generated by the Maintenance Planner at https://
apps.support.sap.com/sap/support/mp . The parameters contained in the Stack XML file can then
be processed by software provisioning manager 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 XML file, software provisioning manager 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 XML file in unattended mode as described in System
Provisioning Using an Input Parameter File [page 133] .
• You can use software provisioning manager to directly download the installation software from SAP by
providing the Maintenance Plan to software provisioning manager while running software provisioning
manager option Download Software Packages for Maintenance Planner Transaction.
For more information, see Downloading Software Packages for a Maintenance Planner Transaction [page
105].

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
38 PUBLIC Planning
Integration

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

If you want to install an SAP Process Integration 7.5 system or an SAP Solution Manager 7.2 system comprising
ABAP and Java, consider the following additional requirements:

• Both the ABAP and the Java system must be installed with the identical Support Package (SP) level.
• The SAP system ID (SAPSID) of the ABAP system must be different from the SAPSID of the Java system.
• The installation with Stack XML file must be run separately, first for the ABAP system, then for the Java
system.

The Software Update Manager (SUM) is started by the software provisioning manager at the end of the
installation process. A browser window opens with a link to UI of the SUM that is already running. Follow the
instructions on the SUM dialogs and in the SUM Guide at https://support.sap.com/sltoolset System
Maintenance .

Each section in this guide describing steps that are completely or at least partially automatized when using a
Stack XML files is marked with an appropriate note at the beginning. These are the following sections:

• Planning Checklist [page 36]

• Additional Parameters When Using a Stack XML File [page 66]
• Downloading Software Packages for a Maintenance Planner Transaction [page 105]
• Running Software Provisioning Manager [page 124]
• Configuring the Change and Transport System [page 156]
• Applying the Latest Kernel and Support Package Stacks [page 160]
• Installing Additional Languages and Performing Language Transport [page 165]

3.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.
• Check your keyboard definitions.
• If you want to install a printer on a host other than the primary application server instance host (for
example, on a separate database instance host), check whether the printer can be accessed under UNIX.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Planning PUBLIC 39
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
For more information, see Running Software Provisioning Manager [page 124].
• The hardware and software requirements tables in Requirements for the SAP System Hosts [page
41].
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

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
40 PUBLIC Planning
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 100] .
2. Make either the separate SAPEXE<Version>.SAR archive or the complete kernel medium available as
described in Preparing the Installation Media [page 95] .
3. Start the software provisioning manager as described in Running Software Provisioning Manager [page
124].

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

Check .
5. Follow the instructions in the software provisioning manager dialogs and enter the required parameters.

 Note

To find more information on each parameter during the Define Parameters phase, position the cursor
on the required parameter input field , and choose either F1 or the HELP tab. Then the available help
text is displayed in the HELP tab.

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

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 100]
Preparing the Installation Media [page 95]

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Planning PUBLIC 41
  Note

The information here and in the following sections is not intended to replace the operating system
documentation. For more information, see your operating system documentation.

Related Information

General Installation Information for Your Operating System [page 42]

Hardware Requirements [page 43]
Software Requirements [page 47]
Other Requirements [page 51]

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

General Installation Information for Your Operating System

Operating System Information

AIX Before you start the installation, make sure that you have read SAP Note In addition to the hardware
and software requirements listed here, make sure that you also consult the hardware and software
requirements provided by IBM at 1972803 .

In addition, we also recommend that you check the information available in the SAP on AIX space on
the SAP Community Network at https://www.sap.com/community/topic/aix.html .

HP-UX In addition to the hardware and softwareBefore you start the installation, make sure that you have
read SAP Note 1075118 .

Linux Before you start the installation, make sure that you have read the SAP Notes for your Linux distribu-
tion listed in the central SAP Note 2369910 .

In addition, we also recommend that you check the information available in the SAP on Linux space
on the SAP Community Network at https://www.sap.com/community/topic/linux.html .

Solaris Before you start the installation, make sure that you have read SAP Note 1669684 .

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
42 PUBLIC Planning
3.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 Your hardware must be 64-bit capable.

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

For an ASCS instance running on a separate host: One physical or virtual processing unit
usable by the operating system image might be sufficient.

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

In a virtualized environment, ensure that adequate processor resources are available to

support the workloads of the running SAP systems.

Optical media drive ISO 9660 compatible

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Planning PUBLIC 43
Requirement Values and Activities

Hard disk space • General Requirements:

• 2 GB of temporary disk space for each required physical installation media - or
alternatively the downloaded SAP kernel archives - that you have to copy to a local
hard disk. For more information, see Preparing the Installation Media [page 95].
• 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 102] .
• 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
accordingly.
• For more information about space requirements for the file systems and directories of
the instances, see SAP Directories [page 83] and the appropriate database-specific
information listed below.
• ABAP central services instance (ASCS):
Minimum 2 GB
• If you install the ASCS instance with an embedded SAP Web Dispatcher, for the
installation as such you require at least 1 GB of hard disk space in addition. For
production use of the SAP Web Dispatcher, you need to reserve at least 5 GB.
• If you install the ASCS instance with an embedded gateway, you require at least
1 GB of hard disk space in addition.
• ERS instance for the ASCS instance (if required):
Minimum 2 GB
• Database Instance:
• Space requirements of the SAP data file systems, see the following file:
<Export_medium>/DATA_UNITS/EXPORT_1/DB/ADA/DBSIZE.XML
fDevSize, which contains the size in MB of the element indicated in the previ-
ous field, fDevName. This shows you the size of the data (DBDATADEV) and the
log (DBLOGDEV) volumes.

 Note
The values listed in DBSIZE.XML are only for guidance.

For more information about the required disk space per file system, see SAP
MaxDB Directories [page 89].
For security reasons (system failure), the file systems must be distributed
physically over at least three (but five are recommended) disks.
• Database software: 1 GB
• Primary application server instance:
Minimum 2 GB (SAP NetWeaver BW server: Minimum 30 GB)

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
44 PUBLIC Planning
 Requirement Values and Activities

• Additional application server instance:

Minimum 2 GB (SAP NetWeaver BW server: Minimum 30 GB)
• SAP Host Agent:
Minimum 0.5 GB

Only valid for 'Platform': AIX

RAM

 Note
AIX: Keep in mind that the operating system itself requires about 10% of the available
RAM.

End of 'Platform': AIX

The following lists the RAM requirements for each SAP instance.

If you install several instances on one host, you have to add up the requirements accord-
ingly.

• ABAP central services instance (ASCS instance)

Minimum 8 GB
If you install the ASCS instance with an embedded SAP Web Dispatcher, see SAP Note
2007212 for memory consumption in productive use.
• ERS instance for the ASCS instance (if required):
Minimum 8 GB
• Database Instance:
8 GB
• Primary application server instance
Minimum 8 GB
• Additional application server instance:
Minimum 8 GB
• SAP Host Agent:
Minimum 4 GB

Only valid for 'Platform': HP-UX

HP-UX: Refer to SAP Note 1112627 for the commands to display the RAM size on HP-UX.
End of 'Platform': HP-UX

Only valid for 'Platform': Linux

Linux: For more information about how to evaluate main memory consumption on Linux, see
SAP Note 1382721 .
End of 'Platform': Linux

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Planning PUBLIC 45
Requirement Values and Activities

AIX: Paging space You need hard disk drives with sufficient paging space. You can calculate the required paging
space as follows:

• Optimistic strategy:
You need at least 20 GB for the primary application server instance and at least
another 10 GB for every additional application server instance.
• Defensive strategy:
3 * RAM, at least 20 GB

In addition, for the database instance you need:

• 0.75 * RAM, if RAM is greater than 8 GB

• 1 * RAM, if RAM is less than 8 GB

For the latest information about recommended paging space, see SAP Note 1121904 .

HP-UX: Swap space You need hard disk drives with sufficient space for swap. You can calculate the required swap
space as follows:

2 * RAM, at least 20 GB

SAP NetWeaver Process Integration 7.5 or higher: 2 * RAM or 80 GB, whichever is higher

For more information about HP-UX swap space recommendations and about how to set up
swap space, see SAP Note 1112627 .

In addition, for the database instance you need:

• Recommended: 3*RAM + 4.5 GB

• Minimum: 2*RAM + 4 GB

Linux: Swap space You need hard disk drives with sufficient space for swap. We recommend that you use the
amount of swap space as described in SAP Note 1597355 . You might decide to use more
or less swap space based on your individual system configuration and your own experience
during daily usage of the SAP system.

In addition, for the database instance you need:

• Recommended: 3*RAM + 4.5 GB

• Minimum: 2*RAM + 4 GB

Oracle Solaris: Swap space You need hard disk drives with sufficient space for swap.

At least 20 GB are required. For more information, see SAP Note 570375 .

In addition, for the database instance you need:

• Recommended: 3*RAM + 4.5 GB

• Minimum: 2*RAM + 4 GB

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
46 PUBLIC Planning
 Requirement Values and Activities

Verifying paging space size To verify paging space size and kernel settings, you can execute memlimits as follows:
and kernel settings using
1. Make sure that the SAPCAR program is available on the installation host. If SAPCAR
memlimits
is not available, you can download it from https://me.sap.com/softwarecenter

SUPPORT PACKAGES & PATCHES By Category SAP TECHNOLOGY COMPONENTS

SAPCAR .
2. Make the SAPEXE.SAR archive available on the installation host. Either download it
as described in Downloading SAP Kernel Archives (Archive-Based Installation) [page
102] or take it from the kernel media, where this archive is contained in the folder
K_<Kernel_Version>_<U/N>_<OS>/DBINDEP.
3. To unpack the file memlimits, enter the following command:
SAPCAR -xvfg SAPEXE.SAR memlimits
4. Start memlimits using the following command:
./memlimits -l 20000
In case of error messages, increase the paging space and rerun memlimits until there
are no more errors.

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

Database software Check the Product Availability Matrix (PAM) at http://support.sap.com/pam for
supported database platforms.

AIX: Operating system version Your operating system platform must be 64-bit.

Check the Product Availability Matrix (PAM) at http://support.sap.com/pam for

supported operating system versions.

Contact your OS vendor for the latest OS patches.

Minimal OS requirements for the specific SAP Kernel releases are listed in SAP Note
1780629 .

You require at least AIX 7.1 TL1 SP1 to be able to run the software provisioning
manager.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Planning PUBLIC 47
Requirement Values and Activities

HP-UX: Operating system version Your operating system platform must be 64-bit.

Check the Product Availability Matrix (PAM) at http://support.sap.com/pam for

supported operating system versions.

To check the operating system version on your installation hosts, use the following
command:

uname -r

See SAP Note 939891 for information about support time frames of HP-UX.

Linux: Operating system version Your operating system platform must be 64-bit.

Check the Product Availability Matrix (PAM) at http://support.sap.com/pam for

supported operating system versions.

Contact your OS vendor for the latest OS patches.

To check the operating system version on your installation hosts, use the following
command:

cat /etc/*-release
Only valid for 'Platform': Linux

If you are installing on SUSE Linux Enterprise Server (SLES), see SAP Note
1275776 to prepare SLES for SAP environments.
End of 'Platform': Linux

Linux Secure Enabled Linux (SELi- Set Linux Secure Enabled Linux (SELinux) | SELinux mode to Permissive or Disabled
nux) Mode on all SAP System hosts for the installation procedure. For more information, see
SAP Note 3247790 .

Oracle Solaris: Operating system Your operating system platform must be 64-bit.
version
Check the Product Availability Matrix (PAM) at http://support.sap.com/pam for
supported operating system versions.

To check the operating system version on your installation hosts, use the following
command:

/bin/uname -r

SAP Kernel Releases and Versions For more information about release and roadmap information for the SAP Kernel
versions, and how this relates to SAP system support packages - including impor-
tant notes on downward compatibility and release dates - see the central SAP Kernel
notes:

AIX: Kernel parameters To adjust AIX kernel parameters, see SAP Note 628131 .

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
48 PUBLIC Planning
 Requirement Values and Activities

HP-UX: Kernel parameters To run an SAP system, make sure that you check and, if necessary, modify the
HP-UX kernel.

 Caution
We recommend that a UNIX system administrator performs all kernel modifica-
tions.

Proceed as follows:

1. Check SAP Note 172747 for recommendations on current HP-UX kernel pa-
rameters.

 Caution
If a kernel value is already larger than the one suggested in the SAP Note,
do not automatically reduce it to match the SAP requirement.

You have to analyze the exact meaning of such a parameter and, if required,
to reduce the parameter value. In some cases this might improve the per-
formance of your SAP applications.

2. If necessary, modify the kernel parameters in one of the following ways:

• Manually, as described in SAP Note 172747 .
• Interactively, using the HP-UX System Administrator Manager (SAM) or
System Management Homepage (SMH).

Linux: Kernel parameters Check SAP Note 2369910 for Linux kernel versions certified by SAP.

To check the Linux kernel parameters for your Linux distribution, see one of the
following SAP Notes:

• SLES 15: SAP Note 2578899

• SLES 12: SAP Note 1984787

• RHEL9x: SAP Note 3108316

• RHEL8x: SAP Note 2772999
• RHEL7x: SAP Note 2002167

Oracle Solaris: Kernel parameters To run an SAP system, you must check and, if necessary, modify the Oracle Solaris
kernel parameters or resource controls.

• Oracle Solaris 10: SAP Note 724713

• Oracle Solaris 11: SAP Note 1797712

HP-UX: OS patches To check the minimum required OS patches, see SAP Note 837670 .

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Planning PUBLIC 49
Requirement Values and Activities

Oracle Solaris: OS patches Check the relevant SAP Note for required Oracle Solaris patches:

• Oracle Solaris 10 on SPARC: SAP Note 832871

• Oracle Solaris 10 on x64: SAP Note 908334
• Oracle Solaris 11: SAP Note 1797712

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

HP-UX: National Language Support Make sure that National Language Support (NLS) and corresponding locales are
(NLS) installed.

You can check this as follows:

• Enter the following commands to check whether National Language Support

(NLS) is installed:
swlist -v | grep -i nls
The output should contain the string NLS-AUX ...
• Enter the following commands to check which locales are available:
locale -a
The following files must be available: de_DE.iso88591, en_US.iso88591.

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

You can check this as follows:

• Ensure that the required locales such as the following are available:
de_DE, en_US
• Check SAP Note 187864 for information about corrected operating system
locales and SAP blended Code Pages.

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

Enter the following command to check which locales are available:

locale -a

The following locale must be available: en_US.ISO8859-1

System language For the installation, you must choose English as the operating system language on
all hosts that run SAP software.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
50 PUBLIC Planning
3.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 software provisioning manager's SL-UI:

• Microsoft Internet Explorer 11 or higher

• Microsoft Edge
• Mozilla Firefox
• Google Chrome

Always use the latest version of these web browsers.

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

AIX: Additional software Make sure that the following additional file sets are installed:

• bos.adt.* – Base Application Development

• bos.perf.* – performance and diagnostics tools
• perfagent.tools – performance monitoring tools

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

For more information about the allowed host name length and characters allowed for
SAP system instance hosts, see SAP Note 611361 .
Only valid for 'Platform': HP-UX

For HP-UX, see SAP Note 1503149 in addition.

End of 'Platform': HP-UX

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Planning PUBLIC 51
Requirement Values and Activities

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

For more information, see SAP Note 202227 .

Only valid for 'Platform': HP-UX

For HP-UX, see SAP Note 1038842 in addition.

End of 'Platform': HP-UX

SAP Host Agent installation:

• Make sure that /bin/false can be used as a login shell.

• Only valid for 'Platform': AIX
AIX only: Add /bin/false to the list of valid login shells (attribute shells)
in /etc/security/login.cfg.
End of 'Platform': AIX

HP-UX: Mount and file system For recommendations about block size and mount option configuration, see SAP Note
configuration 1077887 .

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

AIX: C++ Runtime environment Minimal C++ runtime requirements for the specific SAP Kernel releases are listed in SAP
Note 1780629 .

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
52 PUBLIC Planning
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
http://help.sap.com/nw731
and 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

3.5 Basic Installation Parameters

The software provisioning manager prompts for input parameters during the Define Parameters phase of the
installation.

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

• Typical
If you choose Typical, the installation is performed with default settings. This means that the software
provisioning manager 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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Planning PUBLIC 53
  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 ASCS Instance with Embedded SAP Web Dispatcher [page 32], you must choose
Custom. Otherwise, you are not prompted for the SAP Web Dispatcher installation parameters [page
68] during the Define Parameters phase of the ASCS instance installation.
• If you want to ASCS Instance with Embedded 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 software
provisioning manager screens.

Related Information

SAP System Parameters [page 54]

SAP System Database Parameters [page 64]
Additional Parameters when Installing SAP Process Integration 7.5 or SAP Solution Manager 7.2 [page 65]
Additional Parameters When Using a Stack XML File [page 66]
Parameters for Additional Components to be Included in the ASCS Instance [page 68]

3.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 software provisioning
manager 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 software provisioning manager checks whether a non-Unicode system
exists and chooses the right executables for the system type.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
54 PUBLIC Planning
 Parameter Description

SAP System ID The SAP system ID (<SAPSID>) identifies the entire SAP system.
<SAPSID>
The software provisioning manager prompts you for the <SAPSID> when you execute the first installa-
tion option to install a new SAP system.

If there are further installation options to be executed, the software provisioning manager prompts you
for the profile directory. 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 UNIX: SAP MaxDB
Planning PUBLIC 55
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.

To find out instance numbers of SAP systems that already exist on the installation host, look for subdir-
ectories ending with <Instance Number> of local (not mounted) /usr/sap/<SAPSID> directories.

For more information about the naming of SAP system instances, see SAP Directories [page 83].
Only valid for 'Platform': AIX

 Caution
AIX only: If you are using NIM Service Handler (NIMSH), do not use 01 or 02 for the instance
number. The software provisioning manager uses the instance number for the internal message
server port 39<Instance Number>. The NIM client daemon uses reserved ports 3901 and 3902.

End of 'Platform': AIX

Only valid for 'Platform': HP-UX

 Caution
HP-UX only: Do not use:

• 75 for the instance number because this number is already used by the operating system. For
more information, see SAP Note 29972 .
• 02 as the instance number because this number is used to determine the port number for
report RSLGCOLL, which is 14<Instance Number> by default. However, port 1402 is already
used by the OS process rstlisten. If you still decide to use 02 as the instance number, the
instance fails to start during the installation process. You then have to manually change the
port number for report RSLGCOLL to continue with the installation. For more information, see
Running Software Provisioning Manager [page 124].

End of 'Platform': HP-UX

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
56 PUBLIC Planning
 Parameter Description

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 software provisioning manager
with the SAPINST_USE_HOSTNAME property. For more information, see Running Software Provi-
sioning Manager [page 124].

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

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

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

SAP Process Java system on a host If you want to install the primary application server instance of the different
Integration (PI) from the host of the primary application server instance of the ABAP system, then you must specify the
7.5, SAP Solu- host of the Java primary application server instance during the Define Parameters phase of the primary
tion Manager application 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

SAP System Pro- /<sapmnt>/<SAPSID>/profileIf you want to install the primary application server instance of the
file Directory or /usr/sap/<SAPSID>/SYS/profile

The software provisioning manager 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 software provisioning manager 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 UNIX: SAP MaxDB
Planning PUBLIC 57
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 software
provisioning manager 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.

Basic Password policy

The master password must meet the following requirements:

• It can be 8 to 30 characters long

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

Additional restrictions depending on SAP MaxDB:

• It can be 8 to 18 characters long

Windows only: When installing MaxDB in an MSCS environment, do not use a password more
than 9 characters long for the MaxDB control user. Otherwise the database installation on an
additional node will fail.
• It must not begin with a digit or an underscore
• It can only contain the following characters: @, _, #, $, a-z, A-Z, 0-9

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.

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
58 PUBLIC Planning
 Parameter Description

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
system. 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 instance.

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 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 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 UNIX: SAP MaxDB
Planning PUBLIC 59
Parameter Description

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 con-
figured in profile parameter SAPLOCALHOSTFULL. FQDN is the fully qualified domain name for an IP
address. 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 software provisioning manager
Upgrade (Op- asks you if you want to upgrade it to a newer patch level version. If you want the existing version to be
tional) upgraded, you must provide the new target version of the SAPHOSTAGENT<Version>.SAR archive.

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

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
60 PUBLIC Planning
Operating System Users

Parameter Definition

Operating System Users and Groups The software provisioning manager processes the operating system users as
follows:

• If the operating system users do not exist, the software provisioning man-
ager creates the following users:
• The SAP system administrator user <sapsid>adm
• Database administrator users
The software provisioning manager sets the master password for these
users by default. You can overwrite and change the passwords either by
using the parameter mode Custom or by changing them on the parameter
summary screen.
• If the operating system users already exist, the software provisioning man-
ager prompts you for the existing password, except if the password of these
users is the same as the master password.
• Make sure that the user ID and group ID of these operating system users are
unique and the same on each relevant application server instance host.

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

group is not available, it is created automatically as a local group. For security
reasons, we recommend removing the operating system users from the group
sapinst after the execution of the software provisioning manager has com-
pleted.

During the Define Parameters phase of the software provisioning manager, you
can specify that the operating system users are to be removed automatically
from the group sapinst after the execution of the software provisioning man-
ager has completed.

For more information about the group sapinst, see Creating Operating System
Users and Groups [page 78].

For more information about the sapinst_instdir directory, see Useful Infor-
mation about Software Provisioning Manager [page 131].

User Management Engine Parameters

Parameter Definition

Java Administrator User The software provisioning manager creates this user in the
ABAP system.
 Note
After the installation, this user is available both in the ABAP
This user is only created during the installation of the
and in the Java system.
application server ABAP for an SAP NetWeaver 7.5 Proc-
ess Integration (PI) system or for an SAP Solution Man- The software provisioning manager sets the user name
ager 7.2 system. J2EE_ADMIN and the master password by default.

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 UNIX: SAP MaxDB
Planning PUBLIC 61
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 software provisioning manager creates this user in the
ess Integration (PI) system or for an SAP Solution Man-
ager 7.2 system. ABAP system.

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

the Java system.

The software provisioning manager sets the user name

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

Communication User The software provisioning manager creates this user in the
ABAP system.
 Note
After the installation, it is available both in the ABAP and in
This user is only created during the installation of the
the Java system
application server ABAP for an SAP NetWeaver 7.5 Proc-
ess Integration (PI) system or for an SAP Solution Man- This user is used for the communication between the ABAP
ager 7.2 system. system and the Java system.

The software provisioning manager 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 UNIX: SAP MaxDB
62 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 161]

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 Directory (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
System 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 UNIX: SAP MaxDB
Planning PUBLIC 63
3.5.2 SAP System Database Parameters

Parameters Description

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

The <DBSID> can be the same as the <SAPSID>.

 Caution
Choose your database ID carefully. Renaming is difficult and requires you to reinstall the
SAP system.

• If you want to install a new database:

Make sure that your database ID:
• Is unique throughout your organization
• Consists of exactly three alphanumeric characters
• Contains only uppercase letters
• Has a letter for the first character
• Does not include any of the reserved IDs listed in SAP Note 1979280 .
• MCOD only: If you want to use an existing database system, enter exactly the database
ID of the existing database to which you want to add the system.
For more information, see Installation of Multiple Components in One Database [page
190].

 Note
If you are installing liveCache OneDB, <DBSID> is valid for both liveCache and SAP
MaxDB, which are both installed in the same database.

Database schema SAP<SAPSID>

Database operating sys- SAP MaxDB software owner (default values):

tem users and groups
• User: sdb
• Group: sdba

SAP MaxDB database owner: sqd<dbsid>

Database Users Database System Administrator: superdba

Database Manager Operator: control

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
64 PUBLIC Planning
3.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

When Using a Stack XML File: When Installation Using a Stack XML File [page 37], in addition to
the requirements listed in using a stack configuration file [page
SAP System ID <SAPSID>
54] General Parameters SAP System ID , make sure
that the SAP system ID (SAPSID) of the ABAP system must be
different from the SAPSID of the Java system.

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
configured in the application server instance profile. Further
post-installation steps [page 165] are required to fully enable
HTTPS communication. For more information about HTTPS ena-
blement, see SAP Note 510007 .

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

not recommended for productive SAP systems due to security
reasons.

 Recommendation
If you are about to install an SAP NetWeaver 7.5 Process
Integration system and you intend to run automated con-
figuration using the Central Technical Configuration (CTC)
Wizard after the installation, it is strongly recommended
that you configure the ABAP communication port for ABAP
already 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 UNIX: <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 UNIX: SAP MaxDB
Planning PUBLIC 65
3.5.4 Additional Parameters When Using a Stack XML File

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

Parameter Description

SAP Process Integration (PI) 7.5, SAP Solution In addition to the requirements listed in SAP System Parameters [page
Manager 7.2: 54] General Parameters SAP System ID , make sure that the
SAP System ID <SAPSID> SAP system ID (SAPSID) of the ABAP system must be different from
the SAPSID of the Java system.

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

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 UNIX: SAP MaxDB
66 PUBLIC Planning
 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.

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 up-
date. 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.

Install Additional SAP System Languages A set of default languages is delivered with the ABAP load. From the
language media delivered with your product version or - if already pro-
vided by the Maintenance Planner for the respective product - using
language archives, you can select additional languages that you want to
have installed 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 XML File (Optional) [page 37].

Related Information

Installation Using a Stack XML File [page 37]

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Planning PUBLIC 67
3.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
embedded 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 embedded 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 embed- When processing the screens for the ASCS instance installation, you are
ded 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
additional parameters required for the SAP Web Dispatcher installation on the
subsequent screens:

Message Server Host

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

Message Server HTTP Port

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

Password for the Internet Communication Management (ICM) user

In order to use the web administration interface for the Internet Communication
Manager (ICM) and SAP Web Dispatcher, an administration user webadm is
created by the software provisioning manager.

You have to assign a password for this user.

Related Information

ASCS Instance with Embedded SAP Web Dispatcher [page 32]

ASCS Instance with Embedded Gateway [page 34]

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
68 PUBLIC Planning
3.6 Distribution of SAP System and SAP MaxDB
Components to Disks

When you install the SAP system, the installation tools prompt you to enter drive letters for the main
components of the system. This lets you distribute components to disks in the system as required. How you do
this significantly affects system throughput and data security, so you need to plan it carefully.

The best distribution depends on your environment and must reflect factors such as the size of the
components involved, security requirements, and the expected workload.

When you work out the assignment of components to disks, you first need to obtain an overview of
the main components and their corresponding directories. On the basis of sample configurations and the
recommendations provided in this documentation, you can then choose the best setup for your particular
system.

In most situations, SAP systems are installed on RAID arrays to guarantee data redundancy. Therefore, this
documentation focuses on RAID subsystems and drives.

Features

The following graphic shows how you can distribute the main directories created during the installation to
Redundant Arrays of Independent Disks (RAID). The distribution is suitable for an average-sized production
system. Keep in mind that this is only an example and that no single solution fits all environments.

RAID Distribution

This configuration is suitable for the main host of a standard system (system with all instances running on the
same host) or the database server of a standalone database system. You can assign the components on the
left to any of the arrays shown. You do not necessarily have to place the transport directory on the primary
application server host.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Planning PUBLIC 69
Array 1 /sapdb/<DBSID>/sapdata/DISKD001

...

/sapdb/<DBSID>/sapdata/DISKD999

Array 2 /sapdb/<DBSID>/saplog/DISKL001

...

/sapdb/<DBSID>/saplog/DISKL999

/usr/sap

Array 3 /sapdb/<DBSID>/saplog/M_DISKL001

...

/sapdb/<DBSID>/saplog/M_DISKL999

This setup has the following key features:

• Security of the Logs

The security of the logs is crucial. The logs record all the changes made to the database and so provide
the information that is necessary to recover a damaged database. Therefore, it is important that they are
stored securely and that you never lose them at the same time as the database data. By placing the redo
logs on a different array to the database data, you can make sure that they are not lost if the array with the
database data is severely damaged.
• Performance
You can reduce I/O bottlenecks by placing the original logical log on a different array than the mirrored log.
Original and mirrored logs are written in parallel. If they are located on the same array, this results in a high
level of write activity that has to be handled by the same controller. By separating original and mirrored
logs, you can distribute the write activity to two different arrays, so reducing I/O bottlenecks.
• RAID
By using RAID 1 arrays for the original and mirrored logs, you obtain high data security and good
performance. The data is written to a primary disk and duplicated identically to a second disk. If one
disk fails, the data is still intact on the second disk.
The use of RAID 5 for the database ensures fault tolerance. The data is striped over all the disks in the
array together with parity information. If one disk fails, the parity information is used to automatically
reconstruct the data lost on the damaged disk.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
70 PUBLIC Planning
3.7 SAP MaxDB System Configuration

This section describes the most important aspects of SAP MaxDB system configuration.

Security Issues

• For security reasons the logs must be mirrored using the operating system or hardware.

 Caution

If a system runs without mirroring, you might lose all data since the last complete backup in the event
of a disk crash.

 Recommendation

We recommend mirroring the logs using the operating system or hardware.

If this is not possible, then mirror the logs with the database mirroring provided by SAP MaxDB.

• We recommend you to run the database with raw devices.

 Caution

Never use RAID 5 systems for database log volumes.

• Do not replace file systems by softlinks.

• Raw devices are secure in the event of a system crash.

Security Concept for Database Software Owner

As of SAP MaxDB 7.5.00 there is a new security concept for the database software owner. Authorization to
access directories and files is restricted, and a new user and user group is required:

• User is sdb (SAP MaxDB default)

• User group is sdba (SAP MaxDB default)

This user and group are the only database software owners on the host. For security reasons, the user does not
have a logon for the system, which guarantees the physical integrity of the database files. Database processes
run under this user, which makes sure that several different users cannot manipulate the database system.

Performance Issues

• Store database data files and logs on different disks

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Planning PUBLIC 71
• Since the logs are written synchronously, they produce the most I/O activity of all database files.
• It is possible to put the logs on the same disk as/sapmnt, but this is not recommended.
• Use the partitions DISKD<N> exclusively for data files of the database.
• If paging or swapping areas and log data reside on the same disk, the performance is poor.
• For database volumes, raw devices are faster than files. The slowest disk drive determines the I/O
performance of the database.

Different SAP MaxDB Systems

For performance reasons, we recommend that you do not install several database systems (for different SAP
systems) on one single host. If you still decide to do so, you must install each database as described in this
documentation.

Recommended Configuration

The following graphic shows an optimal distribution of the database data on different disks.

Optimal Distribution

For more information about the file systems for the SAP system and the SAP MaxDB database, see Required
File Systems and Directories [page 83].

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
72 PUBLIC Planning
3.8 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 software provisioning manager creates during the installation of the
SAP system by default on the global host.
The software provisioning manager 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
Exporting and Mounting the Global Transport Directory [page 115].

More Information

• Required File Systems and Directories [page 83]

• 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

http://help.sap.com/nw74 Change 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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Planning PUBLIC 73
3.9 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.

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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
74 PUBLIC Planning
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.

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 UNIX: SAP MaxDB
Planning PUBLIC 75
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 UNIX: SAP MaxDB
76 PUBLIC Planning
4 Preparation

4.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, all mandatory instances are installed on one host. Therefore, if you are installing a
standard system, you can ignore references to other hosts.

1. You check that the required Creating Operating System Users and Groups [page 78] are created.
2. You operating systemset up file systems [page 83] and make sure that the required disk space is available
for the directories to be created during the installation.
3. If you want to use virtual host names, you have to set the environment variable SAPINST_USE_HOSTNAME
[page 93].
Alternatively, you can specify a virtual host name either in the command to start the software provisioning
manager or - after the software provisioning manager has started - in the relevant field on the respective
instance screen (see Running Software Provisioning Manager [page 124]).
4. If you want to install a high-availability system, you perform switchover preparations [page 94].
5. If you want to share the transport directory trans from another system, export [page 115] this directory to
your installation hosts.
6. You install the SAP front-end software [page 94] on the desktop of the user.
7. You check that the required installation media [page 95] are available for each installation host.
8. If you decided to use a generic LDAP directory, you have to create a user for LDAP directory access [page
192].
9. You continue with Installation [page 110].

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Preparation PUBLIC 77
Additional Application Server Instance

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

1. You check that the required operating system users and groups [page 78] are created.
2. You set up file systems [page 83] and make sure that the required disk space is available for the
directories to be created during the installation.
3. If you want to use virtual host names, you have to set the environment variable SAPINST_USE_HOSTNAME
[page 93].
Alternatively you can specify a virtual host name either in the command to start the software provisioning
manager or - after the software provisioning manager has started - in the relevant field on the respective
instance screen (see Running Software Provisioning Manager [page 124]).
4. If you want to share the transport directory trans from another system, export [page 115] this directory
to your installation hosts.
5. You install the SAP front-end software [page 94] on the desktop of the user.
6. You check that the required installation media [page 95] are available on each installation host.
7. You continue with Installation [page 110].

4.2 Creating Operating System Users and Groups

During the installation, the software provisioning manager checks all required accounts (users, groups) and
services on the local machine. The software provisioning manager checks whether the required users and
groups already exist. If not, it creates new users and groups as necessary.

The sapinst_instdir directory belongs to a group named sapinst. If this group is not available, it is
created automatically as a local group.

If you do not want the software provisioning manager to create operating system users, groups, and services
automatically, you can optionally create them before the installation is started. This might be the case if you
use central user management such as Network Information System (NIS).

For distributed installations, unless you are using global accounts or NIS, you must create the target users
automatically using the software provisioning manager or manually on the operating system, before starting
the installation :

 Caution

The user ID (UID) and group ID (GID) of SAP users and groups must be identical for all servers belonging to
an SAP system.

This does not mean that all users and groups have to be installed on all SAP servers.

The software provisioning manager checks if the required services are available on the host and creates
them if necessary. See the log messages about the service entries and adapt the network-wide (NIS) entries
accordingly.

The software provisioning manager checks the NIS users, groups, and services using NIS commands. However,
the software provisioning manager does not change NIS configurations.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
78 PUBLIC Preparation
  Recommendation

For a distributed or a high-availability system, we recommend that you distribute account information
(operating system users and groups) over the network, for example by using Network Information Service
(NIS)..

If you want to use global accounts that are configured on a separate host, you can do this in one of the following
ways:

• You start the software provisioning manager and choose Generic Installation Options <Database>
Preparation Operating System Users and Groups .
For more information, see Running Software Provisioning Manager [page 124].
• You create operating system users and groups manually. Check the settings for these operating system
users.

User Settings

• Only valid for 'Platform': Oracle Solaris

Oracle Solaris: If your operating system is Oracle Solaris 10 or higher, follow the parameter
recommendations for SAP applications in SAP Note 724713 .
End of 'Platform': Oracle Solaris

• Only valid for 'Platform': AIX

AIX: Make sure that you have set the limits for operating system users as described in SAP Note
323816 .
End of 'Platform': AIX

• Only valid for 'Platform': HP-UX, Linux, Oracle Solaris

HP-UX, Oracle Solaris: Make sure that you have set the limits listed below for operating system users root,
<sapsid>adm, and your database-specific operating system users .
Linux: Starting with SUSE Linux Enterprise Server 15, Red Hat Enterprise Linux 8, and Oracle Linux 8,
and the respective SAP kernel patch levels, native support for the software suite systemd for Linux is
available for SAP systems. If you use Linux with systemd, ignore the following procedures for setting limits
because there's no need to change the limits. Make sure that polkit is installed. systemd requires polkit for
authorization checks for the <sapsid>adm user. For more information about Linux with systemd, see SAP
Note 3139184 .
If you are still using a Linux version or an SAP kernel patch that is not released for native systemd
support with SAP systems (see 3139184 ), proceed as follows: Make sure that you have set the limits
as outlined below for operating system users root, <sapsid>adm, and your database-specific operating
system users .

 Caution

Caution: the limit mechanism supports hard and soft limits. The soft limit cannot be bigger than
the hard limit. The hard limit can be set/increased by the root user like: limit -h <limit>
<new_value>, for example limit -h datasize unlimited .

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Preparation PUBLIC 79
 • Using csh shell, the output of command limit needs to be at least as follows:

 Example

The following table lists example output taken from SUSE Linux Enterprise Server 11 (x86_64).

Output Properties

cputime unlimited

filesize unlimited

datasize unlimited

stacksize 8192 KB

coredumpsize unlimited

descriptors 8192

memoryuse unlimited

• Using sh or ksh shell, the output of command ulimit -a needs to be at least as follows:

 Example

The following table lists example output taken from SUSE Linux Enterprise Server 11 (x86_64).

Output sh Output ksh Properties

cpu time (seconds) cpu time (seconds) unlimited

file size (blocks) file size (blocks) unlimited

data seg size (kbytes) data size (Kibytes) unlimited

stack size (kbytes) stack size (Kibytes) 8192 KB

core file size (blocks) core file size (blocks) unlimited

open files nofile 8192

max memory size (kbytes) max memory size (Kibytes) unlimited

End of 'Platform': HP-UX, Linux, Oracle Solaris

• All users must have identical environment settings. Any change to the environment – such as variables, or
paths – is at your own responsibility.
• If you have multiple operating system users with user ID (UID) 0, you must assign the sapinst group to all
of them.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
80 PUBLIC Preparation
 • Do not delete any shell initialization scripts in the home directory of the operating system users. This
applies even if you do not intend to use the shells that these scripts are for.
• If you create the sdb user manually, make sure that you lock it for the installation. In most cases, the
software provisioning manager locks this user after it has been created.
• If you install an SAP system with instances distributed over several hosts, make sure that the following
requirements are met:
• The user ID (UID) and group ID (GID) of each operating system user must be unique and the same on
each instance host that belongs to the same SAP system.
• Make sure that the group ID of group sapinst is always different from the group ID of any other group
(for example, of group sapsys) used during the installation.
For example, if you want to install an additional application server instance for an existing SAP system,
you must make sure that the group ID of group sapinst created on the host of the additional
application server instance is different from the group ID of any other group on the primary application
server instance host of the existing SAP system.
• If you use local operating system user accounts instead of central user management (for example,
NIS), users <sapsid>adm, sapadm, and the database operating system user must have the same
password on all hosts.
• If you create operating system users manually or use already existing operating system users, make sure
that the home directory for each of these users is not the root directory ( / ) .
• Make sure that the home directory of user <sapsid>adm is not critical for recursive changes on
permissions.
When operating system users are created by the software provisioning manager, the permissions on the
home directories of these users are changed recursively. This can cause unpredictable errors if you define
a critical home directory.
For example, the home directory must not be / or /usr/sap.
• Only valid for 'Platform': HP-UX
HP-UX: To prevent terminal query errors in the <sapsid>adm environment, comment out the line eval
'tset -s -Q -m ':?hp' in the /etc/skel/.login script. For more information, see SAP Note
1038842 .
End of 'Platform': HP-UX

Operating System Users and Groups

The software provisioning manager chooses available operating system user IDs and group IDs unless you are
installing an additional application server instance. On an additional application server instance you have to
enter the same IDs as on the host of the primary application server instance.

If you have multiple operating system users with user ID (UID) 0, you must assign the sapinst group to all of
them.

 Recommendation

For security reasons, we recommend that you remove the operating system users from the group sapinst
after the software provisioning manager has completed. For more information, see Ensuring User Security
[page 168].

We recommend that you specify this “cleanup” already during the Define Parameters phase on the Cleanup
Operating System Users screen. Then, the removal of the operating system users from the group sapinst

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Preparation PUBLIC 81
 is done automatically. For more information, see Cleanup of Operating System Users in SAP System
Parameters [page 54].

Users and Groups

User Primary Group Additional Group Description

root None sapinst Superuser of the UNIX oper-

ating system

<sapsid>adm sapsys sapinst SAP system administrator

sqd<dbsid> sapsys sapinst, sdba Owner of database instance

<DBSID>

sdb sdba Database software owner

Groups and Members

Groups Members

sapsys <sapsid>adm, sqd<dbsid>

sapinst root, <sapsid>adm, sqd<dbsid>

sdba sqd<dbsid>, sdb

SAP Host Agent:

User and Groups of the SAP Host Agent

User Primary Group Additional Group Comment

sapadm sapsys – SAP Host Agent administrator

 Note
If sapadm does not exist, it is
created during the SAP Host
Agent installation using /bin/
false shell.

Make sure that /bin/false

can be used as a login shell.
Only valid for 'Platform': AIX

AIX: Add /bin/false to the

list of valid login shells (attribute
shells) in /etc/security/
login.cfg.
End of 'Platform': AIX

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
82 PUBLIC Preparation
Groups and Members of the SAP Host Agent User

Groups Members

sapsys sapadm

sapinst sapadm

4.3 Required File Systems and Directories

The following sections describe the directory structures for the SAP system, how to set up SAP file systems for
the SAP system and, if required, raw devices 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 83]

SAP MaxDB Directories [page 89]
Setting Up File Systems for a High-Availability System [page 89]

4.3.1 SAP Directories

Depending on the installation option you have chosen, the software provisioning manager automatically
creates the directories listed in the following figures and tables. Before running the installation, you have to
set up the required file systems manually. In addition, you have to make sure that the required disk space for
the directories to be installed is available on the relevant hard disks.

The software provisioning manager creates the following types of directories:

• Physically shared directories

• Logically shared directories
• Local directories
Only valid for 'Platform': HP-UX

HP-UX only: For recommendations about block size and mount option configuration, see SAP Note
1077887 .
End of 'Platform': HP-UX

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Preparation PUBLIC 83
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 software
provisioning manager creates all directories in the root directory (/ ). A high-availability setup might influence
the file system structure. Contact your HA partner for their recommendation. For more information, see
Setting Up File Systems for a High-Availability System [page 89] .

The software provisioning manager prompts you only 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>.

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 UNIX: SAP MaxDB
84 PUBLIC Preparation
 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 reside on the global host and are shared by Network File System (NFS). The
software provisioning manager 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 Network File System (NFS) and – for a distributed system
such as a high-availability system or a system with additional application server instances – mount it from
the other installation hosts.
The software provisioning manager creates the following shared subdirectories in /<sapmnt>/<SAPSID>,
which is the during the SAP system installation. If you install an SAP system with instances distributed
over several hosts, you have to share these directories for all hosts with the same operating system (see
Exporting and Mounting Global Directories [page 117]):
• global
Contains globally shared data
• profile
Contains the profiles of all instances
• exe

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Preparation PUBLIC 85
 • Contains a folder uc and a folder nuc, each with a platform-specific subfolder:
• <sapmnt>/<SAPSID>/exe/uc/<platform> is used in Unicode systems.
Executable kernel programs are replicated from this directory to the exe directories of each
Unicode system instance.
• <sapmnt>/<SAPSID>/exe/nuc/<platform> is used in non-Unicode systems (see below).
Executable kernel programs are replicated from this directory to the exe directories of each
non-Unicode system instance (see below).
• Contains a folder jvm with the SAP JVM files
• The directory /usr/sap/trans
The /usr/sap/trans directory is physically separated from the server directories. This is to ensure that
the ability of the server to run is not affected if the /usr/sap/trans directory is full.
If you want to use an existing transport directory, you have to mount it before you install the relevant
application server instance. Otherwise, the software provisioning manager creates /usr/sap/trans
locally.

 Recommendation

We recommend that you set up your global transport directory as a shared file system.

For more information about the global transport directory, see Exporting and Mounting the Global
Transport Directory [page 115].

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),
because 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 software
provisioning manager 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 another symbolic link /usr/sap/<SAPSID>/SYS/exe/dbg in the same
directory, and symbolic link dbg finally points to /<sapmnt>/<SAPSID>/exe/uc/<platform>

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
86 PUBLIC Preparation
Whenever a local instance is started, the sapcpe program checks the executables against those in the logically
shared directories and, if necessary, replicates them to the local instance.

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Preparation PUBLIC 87
Directory Description Required Minimum Disk Space

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

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)

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
88 PUBLIC Preparation
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

4.3.2 SAP MaxDB Directories

These are the directories for the SAP MaxDB database:

SAP MaxDB Directories

Directory Name Description Space Required

/sapdb/<DBSID>/sapdata SAP MaxDB See the table Hardware Requirements in Hardware and Software
data Requirements Tables [page 41]

 Note
If the database data is installed on raw devices, you do not
need to set up /<sapdata>.

/sapdb/<DBSID>/saplog SAP MaxDB See the table Hardware Requirements in Hardware and Software
redologs Requirements Tables [page 41].

 Note
If the database data is installed on raw devices, you do not
need to set up /<sapdblog>.

/sapdb SAP MaxDB See the table Hardware Requirements in Hardware and Software
software Requirements Tables [page 41].

4.3.3 Setting Up File Systems for a High-Availability System

Third-party technology is used to make the SAP directories available to the SAP system. The technologies
of choice are NFS, shared disks, and cluster file system. If you have decided to use a high-availability (HA)
solution for your SAP system, make sure that you properly address the HA requirements of the SAP file
systems in your SAP environment with the HA partner of your choice.

Prerequisites

You have already installed the hardware – that is, hosts, disks, and network – and decided how to distribute the
database, SAP instances, and – if required – Network File System (NFS) server over the cluster nodes (that is,

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Preparation PUBLIC 89
over the host machines). For more information, see Planning the Switchover Cluster [page 74] and contact your
HA partner.

Context

From the perspective of an SAP application, there are the following types of SAP Directories [page 83]:

• Physically shared directories: /<sapmnt>/<SAPSID> and /usr/sap/trans

In an HA setup, /<sapmnt> should be a highly available file system, and /usr/sap/trans should be a
shared file system.
• Logically shared directories that are bound to a node such as /usr/sap with the following local directories:
• /usr/sap/<SAPSID>
• /usr/sap/<SAPSID>/SYS
• /usr/sap/hostctrl
In an HA Setup, no special actions are required for these local directories.
• Local directories that contain the SAP instances such as /usr/sap/<SAPSID>/ASCS<Instance
Number>.
In an HA setup, the directories of the clustered instances (/usr/sap/<SAPSID>/<Instance
Type><Instance Number>) should be mounted as cluster-controlled file systems and reside on highly
available file systems.
Only valid for 'Platform': HP-UX

HP-UX only: For recommendations about block size and mount option configuration, see SAP Note
1077887 .
End of 'Platform': HP-UX

Procedure

1. Create the file systems or raw partitions for the SAP instances you can switch over in such a way that the
content can be made available to all nodes that can run the service. .

At least the ABAP central services (ASCS) instance and the ERS instance must be part of the switchover
cluster

The SAP directories /<sapmnt>/<SAPSID> and /usr/sap/trans are usually mounted from a Network
File System (NFS). Especially for /<sapmnt>/<SAPSID> you should think of using a highly available
file system. However, an SAP instance directory /usr/sap/<SAPSID>/<Instance Type><Instance
Number> that you want to prepare for HA must always be mounted on the cluster node that is currently
running the instance.

 Caution

To start or stop an SAP instance, you have to do one of the following:

• Make the physically shared SAP directories under /<sapmnt>/<SAPSID>/ available to the server
beforehand.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
90 PUBLIC Preparation
 • Consult your HA partner to clarify the best solution for the cluster software.

2. Use the following approach for the file system for the /usr/sap/<SAPSID> directory:

The /usr/sap/<SAPSID> directory contains at least two subdirectories (see also SAP Directories [page
83]):

• SYS/sapmnt/<SAPSID>
• <Instance Type> <Instance Number> – where the name is defined by the type of services and
the application server number:
• SAP systems based on SAP NetWeaver 7.5 or higher: D<Instance Number> – which contains
data for the primary application server instance or an additional application server instance
• SAP systems based on SAP NetWeaver 7.3 EHP1 to 7.4: DVEBMGS<Instance Number> – which
contains data for the primary application server instance
• SAP systems based on SAP NetWeaver 7.3 EHP1 to 7.4: D<Instance Number> – which
contains data for an additional application server instance
• ASCS<Instance Number> – which contains data for the ABAP central services instance (ASCS
instance)
• ERS<Instance Number> – which contains the replication table, which is a copy of the lock table

Only <Instance Type><Instance Number> directories of clustered instances need to be migrated with
the SAP instances during the switchover.

Create cluster-controlled file systems for /usr/sap/<SAPSID>/<Instance Type><Instance

Number> of clustered instances.

The instance-specific directory name for the ABAP central services instance is normally ASCS<Instance
Number>. Migrating only these directories avoids mount conflicts when switching over to a node on which
another application server instance is already running. The ASCS<Instance Number> directory can join
the /usr/sap/<SAPSID> tree instead of mounting on top of it. The same is true for all other clustered
instances.

 Note

This approach becomes increasingly important when you want to cluster the central services instances
with other local instances running on the cluster hosts outside the control of the switchover software.
This applies to the ERS instance and additional ABAP application server instances. The result is a more
efficient use of resources. Use this approach for integrated installations of the application server with
ABAP stacks.

3. You assign the local (not switching) file systems to permanent mount points.
4. You assign the shared file systems as documented by your HA partner.

Example

The graphic below shows a scenario of the file systems and disks in an HA setup with an integrated NFS server.
Such a setup is not mandatory. For more information about a setup that meets your needs, consult your HA
partner.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Preparation PUBLIC 91
 File Systems and Disks in an HA Setup

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
92 PUBLIC Preparation
4.4 Using Virtual Host Names

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

Prerequisites

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

Context

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

Procedure

Assign the required virtual host names to the instance to be installed by specifying them in one of the following
ways:
• By starting the software provisioning manager with the SAPINST_USE_HOSTNAME property
For more information, see Running Software Provisioning Manager [page 124].
• Alternatively by specifying virtual host names in the <Instance Name> Host Name field of the
<Instance Name> Instance screen

For more information, see the Virtual Host Name parameter description in SAP System Parameters [page 54]
and SAP Note 962955 .

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Preparation PUBLIC 93
4.5 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 93], you must set the software provisioning manager
property SAPINST_USE_HOSTNAME to specify the required virtual host name. You can do this in one of the
following ways:

• By starting the software provisioning manager with the SAPINST_USE_HOSTNAME property

For more information, see Running Software Provisioning Manager [page 124].
• Alternatively by specifying virtual 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 54].

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.

4.6 Installing the SAP Front-End Software

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

Procedure

1. Check SAP Note 147519 for the recommended SAP front-end release.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
94 PUBLIC Preparation
 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

4.7 Preparing the Installation Media

This section describes how to prepare the installation media.

Installation media are available as follows:

• The software provisioning manager 1.0 archive containing the software provisioning manager software
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 100].
• 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:
• Make yourself familiar with current SAP Kernel releases and SAP's Kernel strategy:

Central SAP Notes

2083594 - SAP Kernel Versions and SAP Kernel Patch Levels

3116151 - SP Stack Kernel Schedule Forecast

2083594 - SAP Kernel Versions and SAP Kernel Patch Levels

1969546 - Release Roadmap for Kernel 74x and 75x

1802333 - Finding information about regressions in the SAP kernel

19466 - Downloading SAP kernel patches

2966761 - Overview of SAP Kernel Correction Archives

2966621 - Overview of Kernel-Related Software Components

953653 - Rolling Kernel Switch

The white paper Update Strategy for the Kernel of the Application Server ABAP in On Premise
Landscapes provides SAP recommendations on how to patch the SAP kernel.
• 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
102].
If you are performing an Installation Using a Stack XML 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 96].
• Download the complete kernel media from the SAP Software Download Center.
For more information, see Downloading Complete Installation Media [page 107].

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Preparation PUBLIC 95
 • 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.

 Caution

As of SAP MaxDB version 7.9.11.07, SAP MaxDB liveCache version 7.9.11.08, a new structure for
the software packages is used. For more information, see SAP Note 3524673 .

• 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 96].

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

4.7.1 Media Required for the Installation - Listed by SAP

System Instance

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

The digital signature of installation media is checked automatically by the software provisioning manager
during the Define Parameters phase while the Media Browser screens are processed (see also Running
Software Provisioning Manager [page 124] ). The software provisioning manager only accepts media whose
digital signature has been checked.

For more information about which kernel version to use, see the following information sources::

Central SAP Notes

2083594 - SAP Kernel Versions and SAP Kernel Patch Levels

3116151 - SP Stack Kernel Schedule Forecast

2083594 - SAP Kernel Versions and SAP Kernel Patch Levels

1969546 - Release Roadmap for Kernel 74x and 75x

1802333 - Finding information about regressions in the SAP kernel

19466 - Downloading SAP kernel patches

2966761 - Overview of SAP Kernel Correction Archives

2966621 - Overview of Kernel-Related Software Components

953653 - Rolling Kernel Switch

The white paper Update Strategy for the Kernel of the Application Server ABAP in On Premise Landscapes
provides SAP recommendations on how to patch the SAP kernel.

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 UNIX: SAP MaxDB
96 PUBLIC Preparation
For more information about release and roadmap information for the SAP Kernel versions, and how this relates
to SAP system support packages - including important notes on downward compatibility and release dates -
see the central SAP Kernel notes:

Proceed as follows to make the media available:

1. Identify the required media for your installation [page 24] as listed below.

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 software

 Caution
As of SAP MaxDB version 7.9.11.07, SAP MaxDB liveCache version 7.9.11.08, a new structure
for the software packages is used. For more information, see SAP Note 3524673 .

• Installation Export (folders EXP*)

 Note
For an MCOD system you require the database client software instead of the database software
and the database patches (if available).

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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Preparation PUBLIC 97
 SAP Instance
Installation Required Software Packages from Installation Media

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
• Database Client Software

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 software provisioning manager checks whether a non-Unicode system exists
and chooses the right executables for the system type.

• SAP SCM only: SAP MaxDB liveCache

• Database Client Software

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 each installation host 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 100].
2. Make the kernel media available.
You can do this in one of the following ways:
• Download the dedicated kernel archives - this is the recommended way.
For more information, see Downloading SAP Kernel Archives (Archive-Based Installation) [page
102].

 Note

If you are using a Stack XML file (see Installation Using a Stack XML 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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
98 PUBLIC Preparation
 Center at https://me.sap.com/softwarecenter where you can download the installation
media required for your SAP product, operating system and database.

Using the software provisioning manager, 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 105].

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

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

 Note

Even if you use the complete kernel media, the software provisioning manager 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 software provisioning manager 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://me.sap.com/
softwarecenter following the instructions in Downloading SAP Kernel Archives (Archive-Based
Installation) [page 102].

 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. The release and
patch versions must match those used for the primary application server instance and the ASCS
instance.

3. Make the RDBMS and export media. available.

You can do this in one of the following ways:
• Copy the required media folders directly to the installation hosts.
• Mount the media on a central media server that can be accessed from the installation hosts.

 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/en/my-support/keys.html .

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Preparation PUBLIC 99
Related Information

Downloading and Extracting the Software Provisioning Manager 1.0 Archive [page 100]
Downloading SAP Kernel Archives (Archive-Based Installation) [page 102]
Downloading Software Packages for a Maintenance Planner Transaction [page 105]
Downloading Complete Installation Media [page 107]

4.7.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 are logged on as a user with root authorizations, and that the download directory has
at least the permissions 755.
• Make sure that you use the latest version of the SAPCAR tool when manually extracting the software
provisioning manager archive. You need the SAPCAR tool to be able to unpack and verify software
component archives (*.SAR files). *.SAR is the format of software lifecycle media and tools that you can
download from the SAP Software Download Center.

 Note

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

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

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
100 PUBLIC Preparation
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 (software
provisioning manager10SP<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 software provisioning
manager10SP<Support_Package_Number>_<Version_Number>.SAR are used automatically instead
of the loadtools available in the SAPEXEDB_<...>.SAR archive of the kernel media. There
is no action required from your side, the software provisioning manager uses the
relevant loadtools automatically once you run it from the extracted software provisioning
manager10SP<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. Using the latest version of SAPCAR, you can verify the digital signature of the downloaded
SWPM10SP<Support_Package_Number>_<Version_Number>.SAR archive as follows:
a. Get the latest version of the SAPCRYPTOLIB archive to your installation host as follows:

1. Go to https://me.sap.com/softwarecenter SUPPORT PACKAGES & PATCHES and search

for “sapcryptolib”.
2. Select the archive file for your operating system and download it to the same directory where you
have put the SAPCAR executable.
3. Use the following command to extract the SAPCRYPTOLIB archive to the same directory where
you have put the SAPCAR executable:
SAPCAR –xvf sapcryptolibp_84…sar –R <target directory>
4. Download the Certificate Revocation List from https://tcs.mysap.com/crl/crlbag.p7s and move
it to the same directory.
b. Verify the digital signature of the downloaded
SWPM10SP<Support_Package_Number>_<Version_Number>.SAR archive by executing the
following command:

 Note

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

/<Path to SAPCAR>/SAPCAR -tvVf <Path to Download Directory>/

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Preparation PUBLIC 101
3. Unpack the Software Provisioning Manager archive to a local directory using the following command:

/<Path to SAPCAR>/sapcar -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
Software Provisioning Manager archive.

 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.7.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 XML file, you can use the service Downloading Software
Packages for a Maintenance Planner Transaction [page 105].

Context

The digital signature of installation archives is checked automatically by the software provisioning manager
[page 124] during the Define Parameters phase while processing the Software Package Browser screens. The
software provisioning manager only accepts archives whose digital signature has been checked. After scanning
the archives and verifying the digital 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.

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
102 PUBLIC Preparation
 2. Make yourself familiar with current SAP Kernel releases and SAP's Kernel strategy:

Central SAP Notes

2083594 - SAP Kernel Versions and SAP Kernel Patch Levels

3116151 - SP Stack Kernel Schedule Forecast

2083594 - SAP Kernel Versions and SAP Kernel Patch Levels

1969546 - Release Roadmap for Kernel 74x and 75x

1802333 - Finding information about regressions in the SAP kernel

19466 - Downloading SAP kernel patches

2966761 - Overview of SAP Kernel Correction Archives

2966621 - Overview of Kernel-Related Software Components

953653 - Rolling Kernel Switch

The white paper Update Strategy for the Kernel of the Application Server ABAP in On Premise
Landscapes provides SAP recommendations on how to patch the SAP kernel.
3. To get all downloadable software component archives required for your SAP product, go to https://
me.sap.com/softwarecenter SUPPORT PACKAGES & PATCHES By Category

You can also search for dedicated software component archives by choosing SUPPORT PACKAGES &
PATCHES By Downloads Search
4. Choose the required software component, release, and technical stack:

• 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 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 UNIX: SAP MaxDB
Preparation PUBLIC 103
5. 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. The release and patch
versions must match those used for the primary application server instance and the ASCS instance.

 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 64-BIT UNICODE, then SAPEXEDB<Version>.SAR

must also be of version 64-BIT UNICODE.

• SAPEXE<Version>.SAR
SAP KERNEL <Version> <UC | NUC> <Operating System> #DATABASE INDEPENDENT

 Note

SAP KERNEL <Version> <NUC> is only available for SAP systems based on SAP NetWeaver 7.4 or
lower.

• SAPEXEDB<Version>.SAR
Choose the version corresponding to the SAPEXE<Version>.SAR from SAP KERNEL <Version>
<UC | NUC> <Operating System> <DATABASE>

 Note

SAP KERNEL <Version> <NUC> is only available for SAP systems based on SAP NetWeaver 7.4 or
lower.

• igsexe<Version>.sar
SAP IGS <Version> <Operating System>
• 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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
104 PUBLIC Preparation
  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.

6. 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://me.sap.com/softwarecenter Support Packages and Patches By Category Additional

Components SAPCRYPTOLIB COMMONCRYPTOLIB<Version> <Operating System>
7. 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 96] or by downloading them as
described in Downloading Complete Installation Media [page 107].

Related Information

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

4.7.1.3 Downloading Software Packages for a Maintenance

Planner Transaction

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

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 XML file> in order to benefit from an automated installation process.

Procedure

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Preparation PUBLIC 105
2. Start the software provisioning manager as described in Running Software Provisioning Manager [page
124] .

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

The software provisioning manager 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 XML 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 software provisioning manager using a Stack XML 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 XML 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://me.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)
• 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 .

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
106 PUBLIC Preparation
 • 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 XML 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 software provisioning manager 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://me.sap.com/
softwarecenter .

Results

You have downloaded the artifacts (SAP archives) required for your SAP system installation with the software
provisioning manager - corresponding to the archives listed in section Downloading SAP Kernel Archives
(Archive-Based Installation) [page 102] - 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 107] .

4.7.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 100].
2. Create a download directory on the host where you want to run the software provisioning manager.
3. You identify the required media as listed in Media Required for the Installation - Listed by SAP System
Instance [page 96] .
4. Identify all download objects that belong to one medium according to one of the following:

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Preparation PUBLIC 107
  Note

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

• Download path or location:

• To download the complete kernel media, go to https://me.sap.com/softwarecenter/
SUPPORT PACKAGES & PATCHES By Category ADDITIONAL COMPONENTS SAP KERNEL
SAP KERNEL 64-BIT UNICODE SAP KERNEL <Version> 64-BIT UNICODE <Select your
OS> .
• Select #DATABASE INDEPENDENT to download the database-independent parts of the
kernel.

 Example

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

SAPEXE_1118-80002612.SAR

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

 Example

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

 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://me.sap.com/softwarecenter/ as
described in Downloading SAP Kernel Archives (Archive-Based Installation) [page 102].

• To download the remaining media required for your SAP product, you can use one of the following
navigation paths:
• https://me.sap.com/softwarecenter INSTALLATIONS & UPGRADES By Category SAP
NETWEAVER AND COMPLEMENTARY PRODUCTS <Product> <Product Release>
• https://me.sap.com/softwarecenter INSTALLATIONS & UPGRADES By Alphabetical
Index (A-Z) <First Letter of Product> <Product> <Product Release>
• Material number
All download objects that are part of an installation medium have the same material number and an
individual sequence number:
<Kernelpart>_<Sequence Number>-<Material Number>

 Example

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
108 PUBLIC Preparation
 SAPEXE_1112-80002623.SAR
Kernel Part I (753) (*)

 Example

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

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Preparation PUBLIC 109
5 Installation

5.1 Installation Checklist

This section includes the installation steps for the following:

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

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

Standard System

 Note

1. You check the prerequisites [page 120] and run the software provisioning manager [page 124] to install the
SAP system.

 Note

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

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

Distributed System

1. If you want to share the transport directory trans from another system, you have to mount [page 115] it
from this system. Otherwise, we recommend that you share the trans directory that is created during the
installation of the primary application server instance.
2. On the ASCS instance host, you do the following:
1. You check the prerequisites [page 120] and run the software provisioning manager [page 124] to install
the ABAP central services instance (ASCS instance).

 Note

If you want to install an ASCS instance with embedded SAP Web Dispatcher [page 32] or with
embedded 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 UNIX: SAP MaxDB
110 PUBLIC Installation
 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 export global directories [page 117] in <sapmnt>/<SAPSID> to the database and primary
application server instance host.
3. On the database instance host, you do the following:
1. You mount the global directories [page 117] in <sapmnt>/<SAPSID> that you exported from the
SAP global host and – optionally – the trans directory that you exported [page 115] from the SAP
transport host.
2. You check the prerequisites [page 120] and run the software provisioning manager [page 124] to install
the database instance.
4. On the primary application server instance host, you do the following:
1. You mount the global directories [page 117] in <sapmnt>/<SAPSID> that you exported from the SAP
global host.
2. You check the prerequisites [page 120] and run the software provisioning manager [page 124] to install
the primary application server instance.
3. If you want to use the shared transport directory trans from another system, you also mount [page
115] this directory.
5. You continue with Post-Installation [page 145].

Graphical Overview

The following figure shows how you install the various instances in a distributed system:

Distribution of Instances in an ABAP System

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Installation PUBLIC 111
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).
This is described in Performing Switchover Preparations for High Availability [page 94] and Setting Up File
Systems for a High Availability System [page 89]
2. If you want to share the transport directory trans from another system, you have to mount [page 115] it
from this system. Otherwise we recommend that you share the trans directory that is created during the
installation of the primary application server instance (see below).
3. You set up the switchover cluster infrastructure as follows:
1. You check the prerequisites [page 120] and Running Software Provisioning Manager [page 124] to
install the ABAP central services instance (ASCS instance) on the primary cluster node, . Use a virtual
host namehost A [page 93].

 Note

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

2. You hostcheck the prerequisites [page 120] and run the software provisioning manager [page 124] to
install the ERS instance for the ASCS instance on the primary cluster node, host A. Use a virtual host
name [page 93].
3. You export global directories [page 117] in <sapmnt>/<SAPSID> to the database host and to the
primary application server instance host.
4. You prepare the standby cluster node, host B, making sure that it meets the hardware and software
requirements [page 39] and it has all the necessary file systems [page 89], mount points, and (if
required) Network File System (NFS).
5. You set up the user environment on the standby node, host B:
• You use the same user and group IDs, and OS specific files (such as etc/services) as on the
primary node.
• You create the home directories of users and copy all files from the home directory of the primary
node.
For more information about the required operating system users and groups, see Creating Operating
System Users [page 78].
6. You configure the switchover software and test that switchover functions correctly to all standby nodes
in the cluster.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
112 PUBLIC Installation
 7. You repeat the following steps until you have finished installing the ERS instance on all nodes in the
cluster:
1. You perform the switchover to a node where you want to install the ERS instance for the ASCS
instance.
2. You check the prerequisites [page 120] and run the software provisioning manager [page 124] to
install the ERS instance for the ASCS instance on the standby node, host B.
4. On the database instance host, you do the following:

 Recommendation

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

1. You make available the global directories in <sapmnt>/<SAPSID> from the switchover cluster
infrastructure and – optionally – from the SAP transport host.
2. You check the prerequisites [page 120] and run the software provisioning manager [page 124] to install
the database instance on the database instance host.
5. On the primary application server instance host, you do the following:

 Note

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

1. You mount the global directories [page 117] in <sapmnt>/<SAPSID> that you exported from the
switchover cluster infrastructure.
2. You check the prerequisites [page 120] and run the software provisioning manager [page 124] to install
the primary application server instance.
3. If you want to use the shared transport directory trans from another system, you also mount [page
115] this directory (see above).
6. We recommend you to install additional application server (AS) instances to create redundancy.
The AS instances are not a SPOF. Therefore, do not include these instances in the cluster.
7. You continue with Post-Installation [page 145].

Graphical Overview

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Installation PUBLIC 113
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

Additional Application Server Instance

1. If you want to install additional application server instances on a host different from the SAP system host,
you export global directories in <sapmnt>/<SAPSID> to the hosts on which you want to install additional
application server instances.
2. On every additional application server instance host, you do the following:
1. If you want to install additional application server instances on a host different from the SAP system
host, you mount the global directories [page 117] in <sapmnt>/<SAPSID> that you exported from the
SAP system host.
2. You check the prerequisites [page 120] and run the software provisioning manager [page 124] to install
the additional application server instance.
3. You continue with Post-Installation [page 145].

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 mount [page 115] it
from this system. Otherwise, we recommend that you share the trans directory that is created during the
installation of the primary application server instance.
2. On the SAP global host, you export global directories in <sapmnt>/<SAPSID> to the hosts on which you
want to install additional application server instances.
3. On every additional application server instance host, you do the following:
1. You mount the global directories [page 117] in <sapmnt>/<SAPSID> that you exported from the SAP
global host.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
114 PUBLIC Installation
 2. You check the prerequisites [page 120] and run the software provisioning manager [page 124] to install
the additional application server instance.
3. If you want to use the shared transport directory trans from another system, also mount [page 115]
this directory.
4. You continue with Post-Installation [page 145].

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

1. If you want to share the transport directory trans from another system, you have to mount [page 115] it
from this system. Otherwise, we recommend that you share the trans directory that is created during the
installation of the primary application server instance.
2. On the primary node, host A, of the switchover cluster infrastructure, you export global directories in
<sapmnt>/<SAPSID> to the hosts on which you want to install additional application server instances.
3. On each additional application server instance host, do the following:
1. You mount the global directories [page 117] in <sapmnt>/<SAPSID> that you exported from the SAP
global host.
2. You check the prerequisites [page 120] and run the software provisioning manager [page 124] to install
the additional application server instance.
3. If you want to use the shared transport directory trans from another system, you also mount [page
115] this directory.
4. You continue with Post-Installation [page 145].

5.2 Exporting and Mounting the Transport Directory

Every SAP system must be assigned to a transport directory. All application server instances of an SAP system
must point to the same transport directory.

Context

Multiple SAP system can use the same transport directory. However, it is not required to have one global
transport directory in your SAP system landscape. Depending on your security requirements, you must decide
how you want to set up the transport directories in your landscape. Systems with lower security requirements
can share a transport directory (DEV, QA, for example). For systems with higher security requirements (PROD,
for example), you might want to have a separate transport directory.

The transport directory is used by the Change and Transport System (CTS). The CTS helps you to organize
development projects, 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 UNIX: SAP MaxDB
Installation PUBLIC 115
For more information, see the SAP Library at:

Release SAP Library Path

• SAP NetWeaver 7.3 including Enhancement Package 1

Application Help Function-Oriented View Application
http://help.sap.com/nw731
Server Application Server ABAP Administration of
• SAP NetWeaver 7.4
Application Server ABAP Change and Transport System
http://help.sap.com/nw74
• SAP NetWeaver 7.5 Change and Transport System - Overview Basics of

http://help.sap.com/nw75 the Change and Transport System Transport Management

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

Consider the following:

• If the transport directory already exists, make sure that it is exported on the transport directory host and
mount it on the SAP instance installation host.
• If the transport directory does not exist, proceed as follows:
• Create the transport directory (either on the host where the primary application server instance is
running or on a file server).
• Export it on the transport directory host.
• If you did not create the transport directory on your SAP instance installation host, mount it there.

Procedure

1. Exporting the Transport Directory

a. Log on as user root to the host where the transport directory /usr/sap/trans resides.
b. Make sure that /usr/sap/trans belongs to the group sapsys and to the user root.
c. If not already done, export the directory using Network File System (NFS).
2. Mounting the Transport Directory

 Note

If the transport directory resides on your local SAP instance installation host, you do not need to mount
it.

a. Log on as user root to the host of the primary or additional application server instance,
where /usr/sap/trans is to be mounted.
b. Create the mount point /usr/sap/trans.
c. Mount /usr/sap/trans using Network File System (NFS) from the exporting host.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
116 PUBLIC Installation
Related Information

Exporting and Mounting Directories via NFS for Linux [page 196]
Exporting and Mounting Directories via NFS for AIX [page 194]
Exporting and Mounting Directories via NFS for Oracle Solaris [page 196]
Exporting and Mounting Directories via NFS for HP-UX [page 195]

5.3 Exporting and Mounting Global Directories

If you install a database or an additional application server instance on a host other than the SAP global host,
mount global directories from the SAP global host.

Prerequisites

If you want to install the executables locally instead of sharing them, do not mount the exe directory with
Network File System (NFS). Instead, create <sapmnt>/<SAPSID>/exe as a local directory (not a link) with a
minimum of 1.5 GB free space.

Context

There is no need to create the directories before the installation when you install a primary application server
instance. The global directories must be exported only if you install additional application server instances.

 Example

You install an SAP system distributed over several hosts. You decide that the host with theABAP central
services instance (ASCS instance) is the SAP global host. You then install the ASCS instance with the
physical global directories on the SAP global host. Before you install the remaining instances (primary
application server instance, a database instance, additional application server instances), you have to
export the global directories from the SAP global host and mount them on the installation hosts for the
remaining instances.

Choose one of the following ways to proceed, depending on whether you are performing a homogeneous or
heterogeneous installation:

Procedure

• Exporting and Mounting Global Directories for a Homogeneous Installation

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Installation PUBLIC 117
 a. Log on to the SAP global host as user root and export the following directories with read/write access
for the root user to the host where you want to install the new instance:

<sapmnt>/<SAPSID>/exe

<sapmnt>/<SAPSID>/profile

<sapmnt>/<SAPSID>/global

Make sure that the user root of the host where you want to install the new instance can access the
exported directories.

 Caution

Make sure that the transport directory is mounted on every host where you want to install an SAP
instance. Otherwise, the installation fails.

For more information, see Exporting and Mounting the Transport Directory [page 115].

b. Log on to the host of the new instance that you want to install as user root.
c. Create the following mount points and mount them from the SAP global host:

<sapmnt>/<SAPSID>/exe

<sapmnt>/<SAPSID>/profile

<sapmnt>/<SAPSID>/global

 Caution

Make sure that the mount points under /<sapmnt>/<SAPSID>/ are permanent. Otherwise,
automatic start of the instance services does not work when you reboot the system.

• Exporting and Mounting Global Directories for a Heterogeneous Installation

With a heterogeneous installation, the instances of an SAP system are installed on hosts with different
UNIX operating systems. If you need information about the installation of application servers on Windows
in a UNIX environment, see Heterogeneous SAP System Installations [page 198].

 Note

Mounting the directories between different system types, for example mounting a Windows file system
on a Linux host, requires a 3rd party product such as Samba. The installation and configuration of
Samba is not covered by in this guide.

Proceed as follows for a heterogeneous installation with different UNIX operating systems:
a. Log on to the SAP global host as user root and export the following directories with root access to
the host on which you want to install the new instance:

<sapmnt>/<SAPSID>/exe

<sapmnt>/<SAPSID>/profile

<sapmnt>/<SAPSID>/global

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
118 PUBLIC Installation
  Caution

Make sure that the global transport directory is mounted on every host where you want to install
an SAP instance. For more information, see Exporting and Mounting the Transport Directory [page
115]. Otherwise, the installation fails.

b. Log on to the host of the new instance as user root.

c. Create the following mount points and mount them from the SAP global host:

<sapmnt>/<SAPSID>/exe

<sapmnt>/<SAPSID>/profile

<sapmnt>/<SAPSID>/global

 Caution

Make sure that these mount points are permanent. Otherwise automatic start of the instance
services does not work when you reboot the system.

Related Information

Exporting and Mounting Directories via NFS for Linux [page 196]
Exporting and Mounting Directories via NFS for AIX [page 194]
Exporting and Mounting Directories via NFS for Oracle Solaris [page 196]
Exporting and Mounting Directories via NFS for HP-UX [page 195]

5.4 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 52].

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Installation PUBLIC 119
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 167].

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

5.5 Prerequisites for Running Software Provisioning

Manager

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

• For the SL-UI, make sure that the following web browser requirements are met:
• You have one of the following supported browsers on the device where you want to run the SL-UI:
• Google Chrome (recommended)
• Mozilla Firefox
• Microsoft Edge
• Microsoft Internet Explorer 11 or higher.
Always use the latest version of these web browsers.
• If you copy the SL-UI URL manually in the browser window, make sure that you open a new Web
browser window in private browsing mode (Internet Explorer), incognito mode (Chrome) or private
browsing mode (Firefox). This is to prevent Web browser plugins and settings from interfering with the
SL-UI.

 Caution

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

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

• 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 software provisioning

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
120 PUBLIC Installation
 manager. While running the software provisioning manager, 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.

• The software provisioning manager uses shell scripts to obtain the environment for user <sapsid>adm.
• If user <sapsid>adm does not yet exist, a working /bin/csh must be available on the host where
you run the software provisioning manager. For more information about recommended login shells, see
SAP Note 202227 .
• If user <sapsid>adm already exists and uses csh, before you start the software provisioning manager,
execute the following command as user <sapsid>adm to make sure that the csh scripts are up-to-
date, depending on your UNIX OS platform:
/bin/csh -c "source /home/<sapsid>adm/.cshrc;env" or /bin/csh -c "source /home/
<sapsid>adm/.login;env"
• 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 the temporary directory has the permissions 755.
• Make sure that you have at least 700 MB of free space in the installation directory for each installation
option. In addition, you need 700 MB free space for the software provisioning manager executables. If you
cannot provide 700 MB free space in the temporary directory, you can set one of the environment variables
TEMP, TMP, or TMPDIR to another directory with 700 MB free space for the software provisioning manager
executables.
You can set values for the TEMP, TMP, or TMPDIR environment variable to an alternative installation
directory as described in section Useful Information about Software Provisioning Manager [page 131].

 Note

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

• Make sure that umask is set to 022 for the user with root permissions that you want to use for running the
software provisioning manager.
As the user with root permissions that you want to use for running the software provisioning manager,
enter the following command: umask 022
• Only valid for 'Platform': AIX
AIX: Make sure that you have set the limits for operating system users as described in SAP Note
323816 .
End of 'Platform': AIX

• Only valid for 'Platform': HP-UX, Linux, Oracle Solaris

Linux: On Linux, starting with SLES 15, RHEL 8 and Oracle Linux 8, and respective recent SAP kernel
patch levels, there is native integration into systemd. In this case, limits for operating system users root,
<sapsid>adm, and your database-specific operating system users do not need to be set any longer. Make
sure that polkit is installed. systemd requires polkit for authorization checks for the <sapsid>adm user.
For older Linux versions and SAP kernel patch levels, however, you must still set these limits. For more
information about how to proceed for older Linux versions, see the following instructions. For more
information about Linux with systemd and the relevant SAP kernel patch levels, see SAP Note 3139184 .

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Installation PUBLIC 121
 HP-UX, Oracle-Solaris, Linux (versions lower than SLES 15, RHEL 8 and Oracle Linux 8 or lower
SAP kernel patch levels): Make sure that you have set the limits for operating system users root,
<sapsid>adm, and your database-specific operating system users (see also sections Creating Operating
System Users and Groups [page 78] and Running Software Provisioning Manager [page 124].

 Caution

Caution: the limit mechanism supports hard- and soft-limits. The soft-limit cannot be bigger than
the hard-limit. The hard-limit can be set/increased by the root user like: limit -h <limit>
<new_value>, for example limit -h datasize unlimited .

• Using csh shell, the output of command limit needs to be at least as follows:

 Example

The following table lists example output taken from SUSE Linux Enterprise Server 15 (x86_64).

Output Properties

cputime unlimited

filesize unlimited

datasize unlimited

stacksize 8192 KB

coredumpsize unlimited

descriptors 8192

memoryuse unlimited

• Using sh or ksh shell, the output of command ulimit -a needs to be at least as follows:

 Example

The following table lists example output taken from SUSE Linux Enterprise Server 15 (x86_64).

Output sh Output ksh Properties

cpu time (seconds) cpu time (seconds) unlimited

file size (blocks) file size (blocks) unlimited

data seg size (kbytes) data size (Kibytes) unlimited

stack size (kbytes) stack size (Kibytes) 8192 KB

core file size (blocks) core file size (blocks) unlimited

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
122 PUBLIC Installation
 Output sh Output ksh Properties

open files nofile 8192

max memory size (kbytes) max memory size (Kibytes) unlimited

End of 'Platform': HP-UX, Linux, Oracle Solaris

• Make sure that you have defined the most important SAP system parameters as described in Basic
Installation Parameters [page 53] 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].
• If you are installing a second or subsequent SAP system in an existing database (MCOD), make sure that
the database is up and running before starting the installation.
For more information, see Installation of Multiple Components in One Database [page 190].
• 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.

• Make sure that the following ports are not used by other processes:
• Port 4237 is used by default as HTTPS port for communication between the software provisioning
manager and the SL-UI.
If this port cannot be used, you can assign a free port number by executing sapinst with the following
command line parameter:
SAPINST_HTTPS_PORT=<Free Port Number>
• Port 4239 is used by default for displaying the feedback evaluation form at the end of the software
provisioning manager processing.
The filled-out evaluation form is then sent to SAP using HTTPS.
If this port cannot be used, you can assign a free port number by executing sapinst with the following
command line parameter:
SAPINST_HTTP_PORT=<Free Port Number>
• If you want to perform the installation in unattended mode, see System Provisioning Using an Input
Parameter File [page 133] which describes an improved procedure using inifile.params.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Installation PUBLIC 123
5.6 Running Software Provisioning Manager

This section describes how to run the software provisioning manager.

Prerequisites

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

Context

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

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

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

Procedure

1. Log on to the installation host as a user with root permissions.

 Caution

Make sure that the user with root permissions that you want to use for running the software
provisioning manager has not set any environment variables for a different SAP system or database.

If your security policy requires that the person running the software provisioning manager is not
allowed to know the credentials of a user with root permissions on the installation host, you
can specify another operating system user for authentication purposes. You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting the sapinst executable from the command
line. You must confirm that the user is a trusted one. For more information, see SAP Note 1745524 .
2. Make the installation media available.

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

 Note

Even if you use the complete SAP kernel media, the software provisioning manager 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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
124 PUBLIC Installation
 <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 must download the required PL from https://me.sap.com/
softwarecenter following the instructions given in Downloading SAP Kernel Archives (Archive-Based
Installation) [page 102].

 Recommendation

Make the installation media available locallyFor example: The software provisioning manager might
require a certain PL . For example, if you use Network File System (NFS), reading from media mounted
with NFS might fail.

Only valid for 'Platform': Oracle Solaris

 Note

Oracle Solaris: If you mount installation media, make sure that you do this with option nomaplcase.

End of 'Platform': Oracle Solaris

3. Start the software provisioning manager from the directory to which you unpacked the Software
Provisioning Manager archive by entering the following command:

<Path_To_Unpack_Directory>/sapinst

 Note

If you are using a Stack XML file (see Installation Using a Stack XML File
[page 37]), you must call the sapinst executable with command line parameter
SAPINST_STACK_XML=<Absolute_Path_To_Stack_XML_File>:

/<Path_To_Unpack Directory>/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 by specifying it as an input parameter on the <Instance Name> Instance screen, you can assign
a virtual host name by starting the software provisioning manager with the SAPINST_USE_HOSTNAME
property:

<Path_To_Unpack_Directory>/sapinst SAPINST_USE_HOSTNAME=<Virtual_Host_Name>

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

 Note

If you are running a system copy with parallel export/import using the Migration Monitor and started
the export with command line option SUPPORT_DECLUSTERING=false, you must start the software
provisioning manager for the installation of the target database instance with command line option
SUPPORT_DECLUSTERING=true for the import during the target system installation.

For more information, see the system copy guides for Product Release “SAP NetWeaver 7.X-based”
at https://help.sap.com/viewer/swpm10guides System Copy Option of Software Provisioning
Manager 1.0 System Copy Guides - Software Provisioning Manager 1.0 or http://support.sap.com/

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Installation PUBLIC 125
 sltoolset System Provisioning System Provisioning Scenarios Copy a System using Software
Provisioning Manager System Copy Guides - Software Provisioning Manager 1.0

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

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

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

 Note

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

If you have a supported web browser (see Prerequisites for Running Software Provisioning Manager [page
120]) installed on the host where you run the software provisioning manager, you can open this URL
directly in the shell. Otherwise, open the URL in a supported web browser that runs on another device.

 Caution

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

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

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

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
126 PUBLIC Installation
 The SL-UI opens in the browser by displaying the Welcome screen.
5. 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
Go to Generic Options <Database> and choose the required task.
6. Choose Next.

 Note

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

7. Follow the instructions on the software provisioning manager screens and enter the required parameters.

 Note

To find more information on each parameter during the Define Parameters phase, position the cursor
on the required parameter input field , and choose either F1 or the HELP tab. Then the available help
text is displayed in the HELP tab.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Installation PUBLIC 127
  Note

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

 Note

If you are performing the target system installation in the context of a system copy with parallel export/
import using the Migration Monitor and the target database is declustered - that is you started the
software provisioning manager for the target database instance installation with command line option
SUPPORT_DECLUSTERING=true as described above - add the following load options parameter in the
SAP System Advanced Load Configuration screen:

-datacodepage <datacodepage_of_source_system>

The advanced screen for load configuration only appears if you run the software
provisioning manager in Custom parameter mode. You can check the parameter within the
import_monitor_cmd.properties file located in the installation directory, in the loadArgs entry.

For more information, see the system copy guides at http://support.sap.com/sltoolset System
Provisioning System Copy Option Guide for Systems Based on SAP NetWeaver 7.1 & Higher .

 Caution

The digital 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 digital signature is not checked again.

For more information, see SAP Note 2393060 .

After you have entered all requested input parameters, the software provisioning manager displays the
Parameter Summary screen. This screen shows both the parameters that you entered and those that the
software provisioning manager set by default. If required, you can revise the parameters before starting the
installation.
8. To start the installation, choose Next.

The software provisioning manager starts the installation and displays the progress of the installation.
When the installation has finished, the software provisioning manager shows the message: Execution of
<Option_Name> has completed.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
128 PUBLIC Installation
 Only valid for 'Platform': HP-UX

 Caution

HP-UX only: If you decided to use 02 as the instance number, the instance fails to start during the
installation process. For more information about the cause, see SAP System Parameters [page 54] .
You must manually change the port number for report RSLGCOLL to continue with the installation.

Proceed as follows:
1. Go to directory /<sapmnt>/<SAPSID>/profile.
2. Edit DEFAULT.PFL.
3. Set the parameter rslg/collect_daemon/listen_port to a free port number.

End of 'Platform': HP-UX

During the installation of an Application Server ABAP for SAP Process Integration 7.5 or SAP Solution
Manager 7.2, the following is automatically accomplished by the software provisioning manager:
• The Java users for the Application Server Java for SAP Process Integration or SAP Solution Manager
are created, which you have to install once the installation of the Application Server ABAP for SAP
Process Integration or SAP Solution Manager is complete.
• The Application Server ABAP for SAP Process Integration or SAP Solution Manager is prepared for
connection to the Application Server Java for SAP Process Integration or SAP Solution Manager.
For details on these users, see the Preparing an External ABAP System as Source for User Data chapter
of the Installation of SAP Systems Based on the Application Server Java of SAP NetWeaver 7.5 and SAP
Solution Manager 7.2 SR2 Java on <OS>: <DB> documentation, which you must use anyway to install
the Application Server Java for SAP Process Integration 7.5 or SAP Solution Manager 7.2 after you have
installed the Application Server ABAP.

If you are performing an Installation Using a Stack XML File [page 37], the Software Update Manager
(SUM) is started by the software provisioning manager at the end of the installation process. A browser
window opens with a link to UI of the SUM that is already running. Follow the instructions on the SUM
dialogs and in the SUM Guide at https://support.sap.com/sltoolset System Maintenance .
9. If required, delete directories with the name sapinst_exe.xxxxxx.xxxx after the software provisioning
manager has finished. Sometimes these directories remain in the temporary directory.

 Recommendation

Keep all installation directories until you are sure that the system, including all instances, is completely
and correctly installed. Once the system is completely and correctly installed, make a copy of the
installation directories with all their contents and save it to a physically separate medium, such
as an optical medium or a USB drive separate from your installation hosts. This might be useful
for analyzing issues occurring later when you use the system. For security reasons, do not keep
installation directories on installation hosts, but make sure that you delete them after saving them
separately.

10. If you copied the software provisioning manager software to your hard disk, you can delete these files when
the installation has successfully completed.
11. For security reasons, we recommend that you remove the operating system users from the group sapinst
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 UNIX: SAP MaxDB
Installation PUBLIC 129
  Note

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

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

<User_Home>/.sapinst/
13. The software provisioning manager log files contain IP addresses and User IDs such as the ID of your
S-User. For security, data protection, and privacy-related reasons we strongly recommend that you delete
these log files once you do not need them any longer.
You find the software provisioning manager log files in the sapinst_instdir directory. For more
information, see Useful Information about Software Provisioning Manager [page 131].

5.7 Additional Information about Software Provisioning

Manager

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

Useful Information about Software Provisioning Manager [page 131]

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

System Provisioning Using an Input Parameter File [page 133]

Provisioning with software provisioning manager, for example installation, of SAP systems in
unattended mode with an input parameter file.

Restarting Interrupted Processing of Software Provisioning Manager [page 138]

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

Entries in the Services File Created by Software Provisioning Manager [page 141]

Troubleshooting with Software Provisioning Manager [page 142]

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

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
130 PUBLIC Installation
5.7.1 Useful Information about Software Provisioning
Manager

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

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

• The software provisioning manager has the web browser-based “SL-UI of the software provisioning
manager” - “SL-UI” for short.
The SL-UI uses the SAP UI Development Toolkit for HTML5 - also known as SAPUI5 - a client-side HTML5
rendering library based on JavaScript. The benefits of this new user interface technology for the user are:
• Zero foot print, since only a web browser is required on the client
• New controls and functionality, for example, view logs in web browser.
As of version 1.0 SP24 Patch Level (PL) 5, the software provisioning manager comes with a new look and
feel of the SL-UI. For more information, see https://blogs.sap.com/2018/11/10/new-look-for-software-
provisioning-manager/ .
The SL-UI connects the web browser on a client with the sapinst executable - which is part of software
provisioning manager - running on the installation host using the standard protocol HTTPS.
For the SL-UI the software provisioning manager provides a pre-generated URL at the bottom of the shell
from which you are running the software provisioning manager . If you have a supported web browser
installed on the host where you run the software provisioning manager, you can start the SL-UI directly
from this URL. Otherwise, open a web browser supported by the SL-UI on any device and run the URL from
there.
For more information about supported web browsers see Prerequisites for Running Software Provisioning
Manager [page 120].
If you need to run the SL-UI in accessibility mode, apply the standard accessibility functions of your web
browser.

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Installation PUBLIC 131
 Shell Used Command

Bourne shell (sh) TEMP=<Directory>

export TEMP

C shell (csh) setenv TEMP <Directory>

Korn shell (ksh) export TEMP=<Directory>

 Caution

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

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

 Recommendation

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

• The software provisioning manager extracts itself to the temporary directory. These executables are
deleted again after the software provisioning manager has stopped running.
Directories called sapinst_exe.xxxxxx.xxxx sometimes remain in the temporary directory after the
software provisioning manager 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 software provisioning manager, which might be useful if an error occurs.

 Caution

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

• To see a list of all available software provisioning manager properties (command line options) and related
documentation, start the software provisioning manager as described above with command line parameter
-p:
./sapinst -p
• If you want to perform the installation in unattended mode, see System Provisioning Using an Input
Parameter File [page 133] which describes an improved procedure using inifile.params.

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

 Note

If you need to terminate the software provisioning manager, press Ctrl + C .

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
132 PUBLIC Installation
5.7.2 System Provisioning Using an Input Parameter File

Provisioning with software provisioning manager, 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 software
provisioning manager. 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 software provisioning manager in unattended mode using an input parameter file.

Since the new Web-based SL-UI (see Useful Information about Software Provisioning Manager [page 131]) was
introduced in 2017 there are two ways to run the unattended mode: “observer mode” and “non-observer
mode”.

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-UI. 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
the software provisioning manager's SL-UI. Otherwise, the automation could be stuck if software provisioning
manager 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>

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Installation PUBLIC 133
 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-UI
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, the software provisioning manager 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 UI 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's
SL-UI.
• 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.
• 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.<unique_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.
• For <media_name> you can choose any value, but the <location> must be unique.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
134 PUBLIC Installation
 • To find out the required media entries, open the summary.html file which you can find in the
installation directory and go to the Dialog "Media" section.
• 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

• If one media contains several subfolders, you can specify it in one of the following ways:

 Example

The SAP Export DVDs/media:

Installation Master /usr/local/TESI/SWPM/slinst_d_stream/

IM_OS400_PPC64
Installation Export NW73 (folder EXP1) /sapmnt/mediaserver2/
arch04_6/51042309/DATA_UNITS/EXP1
Installation Export NW73 (folder EXP3) /sapmnt/mediaserver2/
arch04_6/51042309/DATA_UNITS/EXP3
Installation Export NW73 (folder EXP2) /sapmnt/mediaserver2/
arch04_6/51042309/DATA_UNITS/EXP2

• By specifying each subfolder:

SAPINST.CD.PACKAGE.ExportNW73EXP1=/sapmnt/mediaserver2/
arch04_6/51042309/DATA_UNITS/EXP1

SAPINST.CD.PACKAGE.ExportNW73EXP2=/sapmnt/mediaserver2/
arch04_6/51042309/DATA_UNITS/EXP3

SAPINST.CD.PACKAGE.ExportNW73EXP3=/sapmnt/mediaserver2/
arch04_6/51042309/DATA_UNITS/EXP3

• By specifying only the root-folder:

SAPINST.CD.PACKAGE.ExportNW73=/sapmnt/mediaserver2/arch04_6/51042309

• Restriction: Currently you can only specify complete media, not paths to single files like *.SAR
archives.
• When performing a system copy, you need to add one additional media path:

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Installation PUBLIC 135
 • 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

Procedure

1. You plan and prepare the run as described in Planning [page 36] and Preparation [page 77].
2. Create your input parameter file as follows:
1. Start software provisioning manager as described in Running Software Provisioning Manager [page
124].
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.
• In the same directory, you will also find the summary.html file with the required media locations.
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 software provisioning manager [page 124] 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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
136 PUBLIC Installation
 • 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

6. After software provisioning manager has completed, perform follow-up activities as described in Post-
Installation [page 145].

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 Software Provisioning Manager unattended mode (Non-
Observer mode)
SAP Note 2482103 Installation with Software Provisioning Manager in unattended mode using input parameter
file fails
SAP Note 2974889 Installation with Software Provisioning Manager in unattended mode fails in step getDBInfo
due to missing paramerters

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Installation PUBLIC 137
5.7.3 Restarting Interrupted Processing of Software
Provisioning Manager

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

Context

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

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

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

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

 Caution

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

The following table describes the options in the dialog box:

Option Definition

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

This is possible because the software provisioning manager records its progress in
the keydb.xml file.

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

If the same or a different error occurs, the software provisioning manager displays
the same dialog box again.

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

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

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

View Log Access installation log files.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
138 PUBLIC Installation
  Note

You can also terminate the software provisioning manager by choosing Ctrl + C but we do not
recommend this because it kills the process immediately.

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

Procedure

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

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

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

Only valid for 'Platform': Oracle Solaris

 Note

Oracle Solaris: If you mount installation media, make sure that you do this with option nomaplcase.

End of 'Platform': Oracle Solaris

3. Restart the software provisioning manager from the directory to which you unpacked the Software
Provisioning Manager archive by executing the following command:
<Path_To_Unpack_Directory>/sapinst
4. The software provisioning manager is restarting.

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

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

 Note

If the host specified by <hostname> cannot be reached due to a special network configuration,
proceed as follows:
1. Terminate the software provisioning manager as described in Useful Information about Software
Provisioning Manager [page 131].

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Installation PUBLIC 139
 2. Restart the software provisioning manager from the command line with the
SAPINST_GUI_HOSTNAME=<hostname> property.
You can use a fully-qualified host name.

If you have a supported web browser (see Prerequisites for Running Software Provisioning Manager [page
120]) installed on the host where you run the software provisioning manager, you can open this URL
directly in the shell. Otherwise, open the URL in a supported web browser that runs on another device.

 Caution

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

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

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

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

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

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

The What do you want to do? screen appears.

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
140 PUBLIC Installation
 Alternative Behavior

Perform a new run The software provisioning manager does not continue the interrupted installa-
tion option. Instead, it moves the content of the old software provisioning man-
ager directory and all software provisioning manager-specific files to a backup
directory. Afterwards, you can no longer continue the old option.

The following naming convention is used for the backup directory:

log_<Day>_<Month>_<Year>_<Hours>_<Minutes>_<Seconds>

 Example
log_01_Oct_2016_13_47_56

 Note
All actions taken by the installation before you stopped it (such as creating
directories or users) are not revoked.

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

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

5.7.4 Entries in the Services File Created by Software

Provisioning Manager

After the installation has finished successfully, the software provisioning manager has created the following
entries in /etc/services:

sapdp<Instance_Number> = 32<Instance_Number>/tcp

sapdp<Instance_Number>s = 47<Instance_Number>/tcp

sapgw<Instance_Number> = 33<Instance_Number>/tcp

sapgw<Instance_Number>s = 48<Instance_Number>/tcp

sapms<SAPSID> = 36<Instance_Number>/tcp (unless you specified another value during the installation)

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
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.

5.7.5 Troubleshooting with Software Provisioning Manager

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

Context

If an error occurs, the software provisioning manager:

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

Procedure

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

• Try to solve the problem:

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

 Note

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

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

For more information, see Useful Information about Software Provisioning Manager [page 131].

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
142 PUBLIC Installation
 • To check the log and trace files of the software provisioning manager's SL-UI for errors, go to the
directory <User_Home>/.sapinst/
• Then continue by choosing Retry.
• If required, abort the software provisioning manager by choosing Cancel in the tool menu and restart
the software provisioning manager. For more information, see Restarting Interrupted Processing of
Software Provisioning Manager [page 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 .

5.7.6 Using the Step State Editor (SAP Support Experts Only)

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

 Note

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

Prerequisites

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

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

Procedure

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

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

• Mark the checkbox in front of the Break option of the steps where you want the software provisioning
manager to pause.
• Mark the checkbox in front of the Skip option of the steps which you want the software provisioning
manager to skip.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Installation PUBLIC 143
4. After you have marked all required steps with either the Break or the Skip option, choose OK on the Step
State Editor dialog.

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

• Choose OK to continue with this step.

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
144 PUBLIC Installation
6 Post-Installation

6.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 148].

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.

Standard, Distributed, or High-Availability System

 Note

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

1. If required, you perform a full installation backup [page 179] immediately after the installation has finished.
2. You check and if necessary modify the settings for the operating system users for your SAP system if they
were created by the software provisioning manager.
For more information, see Creating Operating System Users and Groups [page 78].
3. You check whether you can log on to the Application Server ABAP [page 147].
4. SAP systems based on SAP NetWeaver 7.4 and higher only: You perform the automated initial setup
[page 148].

 Note

This step is optional.

5. You install the SAP license [page 149].

6. If you have installed a high-availability system, you set up the licenses for high availability [page 151].
7. You configure the remote connection to SAP support [page 152].

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Post-Installation PUBLIC 145
8. You enable the Note Assistant to apply note corrections [page 152].
9. You configure the documentation provided on the SAP Help Portal [page 153].
10. You perform the consistency check [page 155].
11. You configure the Transport Management System [page 156].
12. For production systems it is highly recommended that you connect the system to SAP Solution Manager
[page 158].
13. You apply the latest kernel and Support Packages [page 160].
14. You perform post-installation steps for the application server ABAP [page 161].
15. 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 164].
16. 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 165].
17. If required, you install additional languages and perform language transport [page 165].
18. You configure the user management [page 167].

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

19. You ensure user security [page 168].

20.You perform the client copy [page 172].
21. If required, you install Database Studio [page 173].
22. If required, you generate the personal security environment (PSE) for SAP MaxDB [page 175].
23. You back up the MaxDB database [page 176].
24. You update the database software to the current release [page 177].
25. Only valid for 'Platform': Linux
On Linux, you set up the Teradata bridge [page 177].
End of 'Platform': Linux

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 perform a full installation backup [page 179].
28. If you chose to install an embedded SAP Web Dispatcher within the ASCS instance, you log on to the SAP
Web Dispatcher Management Console [page 181]
29. If you chose to install an embedded SAP Web Dispatcher within the ASCS instance, you configure the SAP
Web Dispatcher [page 182]
30.If you chose to install an embedded Gateway within the ASCS instance, you configure the SAP Gateway
[page 183].
31. You check the Master Guide for your SAP Business Suite application, SAP Solution Manager system
(section Implementation Sequence) or SAP NetWeaver application (section Configuration of Systems and
Follow-Up Activities) for additional implementation and configuration steps, such as language installation,
monitoring, work processes, transports, SAP license, printers, system logs, and connectivity to system
landscape directory (SLD).

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
146 PUBLIC Post-Installation
Additional Application Server Instance

1. If required, you perform an installation backup [page 179] immediately after the installation has finished.
2. You check and if necessary modify the settings for the operating system users for your SAP system if they
were created by the software provisioning manager.
For more information, see Creating Operating System Users and Groups [page 78].
3. You check whether you can log on to the Application Server ABAP [page 147].
4. You configure the documentation provided on the SAP Help Portal [page 153].
5. You ensure user security [page 168].
6. You perform a full installation backup [page 179].

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

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

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

User User Name Client

SAP system user SAP* 000, 001, 066

DDIC 000, 001

You access the application server ABAP using SAP Logon.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Post-Installation PUBLIC 147
Procedure

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

• SAP GUI for Windows:

On the host where you have installed the front end, choose:
Start Programs SAP Front End<Release> SAPlogon
• SAP GUI for Java:
Enter the following command from the GUI installation directory:
guilogon
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.

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

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
148 PUBLIC Post-Installation
 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 XML File [page 37]

Installing the SAP License [page 149]
Configuring the Remote Connection to SAP Support [page 152]
Configuring the Change and Transport System [page 156]
Applying the Latest Kernel and Support Package Stacks [page 160]
Performing Post-Installation Steps for the ABAP Application Server [page 161]
Performing the Consistency Check [page 155]

6.4 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 148].

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Post-Installation PUBLIC 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:

 Note

If you have installed a high-availability system, proceed as described in High Availability: Setting Up
Licenses [page 151].

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

• SAP NetWeaver 7.3 including Enhancement Pack-

Application Help Function-Oriented View Solution Life
age 1
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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
150 PUBLIC Post-Installation
6.5 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 149] 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.

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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Post-Installation PUBLIC 151
Results

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

6.6 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_CONFIG_OSS_COMM 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 148].

For more information about configuring the remote connection to SAP Support, see the SAP Support Portal at
https://support.sap.com/remote-support.html .

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
152 PUBLIC Post-Installation
6.8 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.

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Post-Installation PUBLIC 153
 Name Value to be entered

Variant Enter a name for the variant.

Platform Select the platform relevant for your implementation from

the list of available platforms, for example, WN32.

Area Select Documentation from the list; this will display as

IWBHELP in the table.

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

Path <product/version>

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

Language Select the language you need from the list.

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

Name Value to be entered

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

Platform Select the platform relevant for your implementation from

the list of available platforms, for example, WN32.

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

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

Path <product/version>

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

Language Select the language you need from the list.

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

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

Results

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

Related Information

Installation of SAP Library

SAP Note 2149786
SAP Note 2652009

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
154 PUBLIC Post-Installation
6.9 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 148].

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 201].
• You have logged on to the SAP system [page 147].

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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Post-Installation PUBLIC 155
 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 .

6.10 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 148].

 Note

SAP_BASIS_SETUP_INITIAL_CONFIG only covers the configuration of TMS as single system.

 Note

If you are using a Stack XML file (see Installation Using a Stack XML File [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 UNIX: SAP MaxDB
156 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 Solution
http://help.sap.com/nw731
Life Cycle Management Software Logistics Change
• SAP NetWeaver 7.4
http://help.sap.com/nw74 and Transport System Change and Transport System –

• SAP NetWeaver 7.5 Overview Basics of the Change and Transport System
http://help.sap.com/nw75 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 Solution
http://help.sap.com/nw731
Life Cycle Management Software Logistics Change
• SAP NetWeaver 7.4
http://help.sap.com/nw74 and Transport System Transport Organizer (BC-CTS-

• SAP NetWeaver 7.5 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. Schedule a job for the transport dispatcher program (RDDIMPDP).

You schedule the job by executing program RDDNEWPP2 in client 000 using a user that is different from the
DDIC user. For more information, see the program documentation of RDDNEWPP2.

 Note

Note that it is sufficient to schedule the job in client 000.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Post-Installation PUBLIC 157
6.11 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.

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
158 PUBLIC Post-Installation
 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:
• 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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Post-Installation PUBLIC 159
6.12 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 XML file (see Installation Using a Stack XML File [page 37]), you already
downloaded the MP_Stack_<Transaction ID>_<Generation Date>_.xml file and the delta archives.
If you then already called the Software Update Manager (SUM) from the software provisioning manager
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 SAP Kernel versions, and how this relates
to SAP system support packages - including important notes on downward compatibility and release dates -
see the central SAP Kernel notes:

Central SAP Notes

2083594 - SAP Kernel Versions and SAP Kernel Patch Levels

3116151 - SP Stack Kernel Schedule Forecast

2083594 - SAP Kernel Versions and SAP Kernel Patch Levels

1969546 - Release Roadmap for Kernel 74x and 75x

1802333 - Finding information about regressions in the SAP kernel

19466 - Downloading SAP kernel patches

2966761 - Overview of SAP Kernel Correction Archives

2966621 - Overview of Kernel-Related Software Components

953653 - Rolling Kernel Switch

The white paper Update Strategy for the Kernel of the Application Server ABAP in On Premise Landscapes
provides SAP recommendations on how to patch the SAP kernel.

 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 UNIX: SAP MaxDB
160 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. Back up the kernel directory that is specified by the profile parameter DIR_CT_RUN.
d. Extract the SAR files of the kernel Support Packages of the target SP level to a temporary directory
using the SAPCAR tool.
e. Copy or move the extracted programs from the temporary directory to the local kernel directory.
f. Adjust the ownership and permissions of the kernel binaries by entering the following command
sequence (Execute the saproot.sh script that is located in the kernel directory):

su - root

cd <Kernel_Directory>

./saproot.sh <SAPSID>

exit

6.13 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 148].

Prerequisites

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Post-Installation PUBLIC 161
Context

You have to perform the following post-installation steps for the ABAP application server:

• Upload and set system profiles using transaction RZ10

• Configure the number of work processes
• Create logon and RFC server groups using transactions SMLG and RZ12
• Create operation modes using transaction RZ04
• Schedule standard jobs using transaction SM36
• Configuration of SLD data supplier using transaction RZ70
• Perform load generation using transaction SGEN

For more information, see the appropriate sections below.

Procedure

• Upload and Set System Profiles using Transaction RZ10

You upload system profiles, such as default profile and instance profile, from the file system into the
database of the target system using transaction RZ10.

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
162 PUBLIC Post-Installation
 You create the following:
• Logon groups using transaction SMLG
• RFC server groups using transaction RZ12

Specify the following:

• Name of the logon or RFC server group
• Instance name (application server)
• Group type attributes are optional

If required, you create the RFC server group parallel_generators.

• Create Operation Modes using Transaction RZ04

You check for existing operation modes and - if required - create a new operation mode using transaction
RZ04.

Specify the following:

• Name of the operation mode
• Short description
• Optional: monitoring properties variant

Select the corresponding checkbox to assign the operation mode to the following:
• Time table (assignment only from 0-24 h)
• Current application server instance
• 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 158]
• 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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Post-Installation PUBLIC 163
  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.

6.14 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 26]

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

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

6.16 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 XML file (see
Installation Using a Stack XML File [page 37]) and processed the Install Additional Languages screen during
the installation.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Post-Installation PUBLIC 165
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

AIX: If you wish to use the Turkish locale with SAP on AIX, you must install the Turkish locale supplied by
SAP instead of the one supplied with the operating system. For more information, see SAP Note 39718 .
2. Perform the language transport using transaction SMLT:

 Note

German is already available in the system. Do not transport it via SMLT.

a. Classify the language.

b. Schedule the language transport.
c. Schedule the language supplementation.

Next Steps

 Note

You can also install additional languages later, but if you install any Support Packages in the meantime, you
have to do one of the following:

• Install the Support Packages again.

• Use the report RSTLAN_IMPORT_OCS to extract the language-relevant information from each Support
Package.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
166 PUBLIC Post-Installation
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 Solution
http://help.sap.com/nw731
Life Cycle Management Software Logistics Change and
• SAP NetWeaver 7.4
Transport System Language Transport (BC-CTS-LAN)
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

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Post-Installation PUBLIC 167
• Add the system to Central User Administration (CUA)
• Use Lightweight Directory Access Protocol (LDAP) synchronization

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

6.18 Ensuring User Security

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

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

• Operating system users

• SAP system users

During the installation, the software provisioning manager by default assigned the master password [page 54]
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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
168 PUBLIC Post-Installation
  Caution

Make sure that you perform this procedure before the newly installed SAP system goes into production.

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

You can find the security guide in the Security section of the product page for your SAP product at https://
help.sap.com/

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 operating system users from the group sapinst
after you have completed the installation of your SAP system.

You do not have to do this if you specified this “cleanup” already during the Define Parameters phase on
the Cleanup Operating System Users screen. Then the removal had already been done automatically when
the processing of the software provisioning manager had completed. For more information, see Operating
System Users in SAP System Parameters [page 54].

Operating System and Database Users

User Type User Comment

Operating system user <sapsid>adm SAP system administrator

sqd<dbsid> SAP MaxDB database administrator

SAP MaxDB database users SAP<SAPSID> SAP MaxDB database owner

CONTROL SAP MaxDB database manager opera-

tor

SUPERDBA SAP MaxDB database system adminis-

trator

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Post-Installation PUBLIC 169
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.

You are not able to log on as sapadm as this user is

locked.

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 .

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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
170 PUBLIC Post-Installation
 User User Name Comment

Application Server Java Admin- The name that you gave this This user exists in at least clients 000 and 001 of the
istrator user during the installation or the ABAP system and in the User Management Engine
default 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- 54])

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  Recommendation
system.
We recommend that you use strong password
and auditing policies for this user.

Application Server Java Guest The name that you gave this This user exists in at least clients 000 and 001 of the
user during the installation or the ABAP system and in the User Management Engine
 Note default 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 54])

application server ABAP for

an SAP Process Integration
(PI) 7.5 system or for an
SAP Solution Manager 7.2
system.

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 54]) 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
system.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Post-Installation PUBLIC 171
6.19 Performing the Client Copy

To get a production client, you have to perform a copy of the SAP reference client.

Context

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

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 UNIX: SAP MaxDB
172 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 Application
http://help.sap.com/nw731
Server Application Server ABAP Administration of
• SAP NetWeaver 7.4
Application Server ABAP Change and Transport System
http://help.sap.com/nw74
• SAP NetWeaver 7.5 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

6.20 Installing or Upgrading Database Studio for SAP

MaxDB

This section describes how to install or upgrade Database Studio for SAP MaxDB and SAP liveCache. Database
Studio is the database administration tool for SAP MaxDB. With Database Studio you can administer MaxDB
databases version 7.6 and newer.

Prerequisites

• You can install Database Studio on Linux or Windows in your network, even if your database runs on a
different operating system. You can then remotely administer the database on a different host.
The instructions below refer mainly to the Windows version.

 Note

To run Database Studio on Linux, you need to meet the requirements for the SAP MaxDB database
server.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Post-Installation PUBLIC 173
• Your PC must meet the following minimum requirements:
• Software requirements:

Operating System Requirements for Database Studio 7.9 and higher

Operating System Database Studio 7.9.08 Database Studio 7.9.09 and Higher

Windows Server X64 X64

Linux Server X64 X64

• Hardware requirements:
• RAM: 512 MB ( recommended RAM: 1 GB)
• Processor speed: 1.5 GHz
• Free disk space: 200 MB
• Monitor: 1024x768 pixels, 256 colors

• You can obtain the required files by downloading them from:

https://me.sap.com/softwarecenter Databases SAP MaxDB Database Patches MAXDB GUI
COMPONENTS/TOOLS MAXDB DATABASE STUDIO 7.9
• Database Studio 7.9.09 comes with the SAP Java Runtime SAPJVM.
You no longer need to download the Java runtime.
• Database Studio 7.9.08 is still available for downloading.
To check your Java version, enter the following command:
java -version
To download Java, go to http://java.com/en/download .

Context

For more information about Database Studio, see https://help.sap.com/maxdb <Version> Application
Help SAP MaxDB Library Tools Database Studio .

 Note

Database Studio replaces Database Manager GUI and SQL Studio, which were available in previous
releases.

For up-to-date information about installing Database Studio, see SAP Note 1097311 .

For more information about Database Studio, including troubleshooting, see SAP Note 1097311 and
1795588 .

Procedure

1. Start the installation or upgrade by simply executing the downloaded SDBSETUP.EXE (Windows clients) or
SDBSETUP (Linux clients) file.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
174 PUBLIC Post-Installation
 The Installation Manager starts.
2. Follow the Installation Manager steps to install or upgrade Database Studio.
3. If you are prompted to restart your computer after the installation, make sure that you first shut down any
databases that are running.

6.21 Secure Sockets Layer Protocol for Database Server

Communication

The SAP MaxDB database server supports the Secure Sockets Layer (SSL) / Transport Layer Security (TLS)
protocol. You can use this protocol to communicate between the database server and its client, here the
Application Server (AS).

SSL guarantees encrypted data transfer between the SAP MaxDB database server and its client applications.
In addition, the server authenticates itself to the client. You need to install SAP’s cryptographic library -
SAPCRYPTOLIB.

For more information on software versions, see SAP Note 2243688 .

 Caution

There is a performance cost for SSL since the data has to be encrypted, which requires time and
processing power.

Procedure

To use SSL you need to perform the following steps:

• Install the SAP Cryptographic Library.

• Generate the Personal Security Environment.
• Import server certificate as described in SAP MaxDB SSL Client PSE.
• Configure the SSL communication between the application server and the database server [page 176].

Related Information

Installing the SAP Cryptographic Library

Generating the Personal Security Environment
SAP MaxDB SSL Server PSE
SAP MaxDB SSL Client PSE
Configuring the SSL Communication between the Application Server and the Database Server [page 176]

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Post-Installation PUBLIC 175
6.21.1 Configuring the SSL Communication between the
Application Server and the Database Server

Set the connection information for each database connection for which SSL is to be used.

Procedure

Using transaction dbco, set the connection information for each database connection for which SSL is to be
used as follows:
• Connection information for database connection <name>
maxdb:remotes://<host>/database/<SID>-<SID>
• Connection information for database connection <name>+
@DBM_SSL:<host>-<SID>

For more information, see SAP Note 2190094 .

Example

Database connection: Test

<host>: lu12345

<SID>: WB9

Connection information for database connection Test:

maxdb:remotes://lu12345/database/WB9-WB9

Connection information for Test+:

@DBM_SSL:lu12345-WB9

6.22 Backing Up the SAP MaxDB Database

You need to define backup media and back up the SAP MaxDB database using Database Manager GUI
(DBMGUI).

Prerequisites

• You have finished client maintenance.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
176 PUBLIC Post-Installation
 • You have installed Database Studio [page 173].
• You can find more information on backing up the database at:
http://help.sap.com/maxdb SAP MaxDB 7.9 SAP MaxDB Library Glossary Backup

Procedure

1. Define the backup template as described in Glossary Backup Templates in the above
documentation.

2. Back up the database as described in Glossary Data Backup and Log Backup in the above
documentation.

6.23 Updating the Database Software to the Current Release

After the installation and before you start production operation, we strongly recommend you to update the
database software.

Procedure

Download the latest SAP MaxDB patches from https://me.sap.com/softwarecenter/ Databases SAP
MaxDB .
For more information about upgrading to a SAP MaxDB patch from a SWDC Support Package, see SAP Note
735598 .

6.24 Linux only: Setting Up the Teradata Bridge

This section tells you how to set up the Teradata bridge on Linux.

Procedure

1. Follow the instructions in the following SAP Notes:

a. Set up the Teradata data source, as described in SAP Note 1401595 .
b. Integrate Teradata backup, as described in SAP Note 1401599 .
This is important so that SAP MaxDB and Teradata are both backed up in a consistent way.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Post-Installation PUBLIC 177
 c. Install user-defined functions on Teradata, as described in SAP Note 1401600 .

 Caution

Before you perform the following step, make sure that you have already set up the Teradata data
source, as described in the SAP Note above.

2. Execute the report RSDU_MOVE_BI_TABLES_TO_DS to move the SAP Business Warehouse tables to
Teradata.
No parameters are required for the report. You can execute the report in dialog mode since there are only a
few empty tables to be moved.

6.25 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 Security System
http://help.sap.com/nw74
Security System Security for SAP NetWeaver AS ABAP Only
• SAP NetWeaver 7.5
http://help.sap.com/nw75 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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
178 PUBLIC Post-Installation
 • 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 Security System
http://help.sap.com/nw74
Security System Security for SAP NetWeaver AS ABAP Only
• SAP NetWeaver 7.5
http://help.sap.com/nw75 Secure Storage (ABAP) Key Management Using Individual

• SAP NetWeaver Application Server for 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

More Information

See also the entry Individual Encryption Key for the Secure Storage in table SAP System Parameters in SAP
System Parameters [page 54].

6.26 Performing a Full Installation Backup

You must perform a full offline backup after the configuration of your SAP system. If required, you can also
perform a full offline backup after the installation (recommended). In addition, we recommend you to regularly
back up your database.

The UNIX commands used in this procedure work on all hardware platforms. For more information about
operating system-specific backup tools, see your operating system documentation.

You need to back up the following directories and files:

• All SAP-specific directories:

• /usr/sap/<SAPSID>
• You have logged on as user as
/usr/sap/trans
• <sapmnt>/<SAPSID>
• Home directory of the user <sapsid>adm
• All database-specific directories
• The root file system
This saves the structure of the system and all configuration files, such as file system size, logical volume
manager configuration, and database configuration data.

 Note

This list is only valid for a standard installation.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Post-Installation PUBLIC 179
Prerequisites

You have logged on as user <sapsid>adm and stopped the SAP system and database [page 201].

Use the backup tool of your choice and refer to the backup software documentation. You can also use the
standard UNIX commands as described below.

Backing Up the Installation

1. Log on as user root.

2. Manually create a compressed tar archive that contains all installed files:
• Saving to tape:
tar -cf - <file_system> | compress -c > <tape_device>
• Saving to the file system:
tar -cf - <file_system> | compress -c > ARCHIVENAME.tar.Z

 Note

Linux only: You can also execute the following command to manually create a compressed GNU tar
archive that contains all installed files and save it to the file system:

tar -czf <ARCHIVENAME>.tgz <file_system>

Restoring Your Backup

If required, you can restore the data that you previously backed up.

 Caution

Check for modifications in the existing parameter files before you overwrite them when restoring the
backup.

1. Log on as user root.

2. Go to the location in your file system where you want to restore the backup image.
3. Restore the data with the following commands:
• From tape:
cat <tape_device> | compress -cd | tar -xf -
• From the file system:
cat ARCHIVENAME.tar.Z | compress -cd | tar -xf -

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
180 PUBLIC Post-Installation
 Only valid for 'Platform': Linux

 Note

Linux only: If you want to restore the data from a GNU tar archive, you have to execute the following
command:

tar -xzf <ARCHIVENAME>.tgz

End of 'Platform': Linux

6.27 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 embedded 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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Post-Installation PUBLIC 181
4. We recommend that you change the password of webadm immediately after the installation for security
reasons.

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
innovation package Web 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 Embedded SAP Web Dispatcher [page 32]

6.28 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 embedded 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 UNIX: SAP MaxDB
182 PUBLIC Post-Installation
 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 Embedded SAP Web Dispatcher [page 32]

6.29 Gateway Configuration

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

 Note

This step is only relevant if you installed a gateway embedded in the ASCS instance. For more information,
see ASCS Instance with Embedded 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 UNIX: SAP MaxDB
Post-Installation PUBLIC 183
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 Embedded Gateway [page 34]

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
184 PUBLIC Post-Installation
7 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.

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

 Caution

SAP recommends that you no longer use the LDAP configuration options provided by the software
provisioning manager, because current security guidelines make it unsafe to run SAP applications on a
domain controller. Instead, SAP recommends that you follow the instructions in SAP Note 3251648 to
enable LDAP directory service integration of your SAP system with Active 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 UNIX: SAP MaxDB
Additional Information PUBLIC 185
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 Security
1
Identity Management User and Role Administration of
http://help.sap.com/nw731
Application Server ABAP Configuration of User and Role
• SAP NetWeaver 7.4
http://help.sap.com/nw74 Administration Directory Services LDAP Connector

• 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

Prerequisites

You can only configure the SAP system for Active Directory services or other LDAP directories if these are
already available on the network. 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.

• You can only configure the SAP system for Active Directory services or other LDAP directories if these are
already available on the network. 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.
• Make sure that the required software is installed:

Operating System Required Software

AIX IBM Tivoli Directory Server client packages

HP-UX The LDAP libraries listed in SAP Note 541344

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
186 PUBLIC Additional Information
 Operating System Required Software

Linux You must have at least the following RPM packages installed:

• Oracle Linux:
openldap2
• Red Hat Linux:
openldap2
• SUSE LINUX
openldap2
openldap2-client

Solaris You must have at least the libldap.so library installed.

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.

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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Additional Information PUBLIC 187
• 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 you need to administer distributed systems, we especially recommend that you use the SAP MMC together
with Active Directory services. You can keep track of significant events in all of the systems from a single
SAP MMC interface. You do not need to manually register changes in the system configuration. Instead, such
changes are automatically updated in the directory and subsequently reflected in the SAP MMC.

If your SAP system is part of a heterogeneous SAP system landscape that comprises systems or instances
both on Unix and Windows operating systems, you can also use the SAP MMC for operating and monitoring the
instances running on Unix.

SAP MC
The SAP MC is a graphical user interface (GUI) for administering and monitoring SAP systems from a central
location. The SAP MC is automatically set up when you install an SAP system on any platform. If the SAP
system has been prepared correctly, the SAP MC presents and analyzes system information that it gathers
from various sources, including a generic LDAP Directory.

Integrating a generic LDAP Directory as a source of information has advantages for the SAP MC. It can read
system information straight from the directory that automatically registers changes to the system landscape.
As a result, up-to-date information about all SAP application servers, their status, and parameter settings is
always available in the SAP MC.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
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 Solution Life
http://help.sap.com/nw731
Cycle Management SAP Management Console
• 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

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 software provisioning manager to automatically:

 Caution

SAP recommends that you no longer use the LDAP configuration options provided by the software
provisioning manager, because current security guidelines make it unsafe to run SAP applications on a
domain controller. Instead, SAP recommends that you follow the instructions in SAP Note 3251648
to enable LDAP directory service integration of your SAP system with Active Directory.

• 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 software provisioning manager 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 software
provisioning manager 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/docs/SOFTWARE_PROVISIONING_MGR_10/159a36e76fe84e54a703f846b08ae1f6/
c8ed609927fa4e45988200b153ac63d1.html

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Additional Information PUBLIC 189
• 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 software
provisioning manager software contains schema extensions for directory servers Netscape/iPlanet
(ldregns4.txt, ldregns5.txt) and OpenLDAP slapd (ldregslapd.schema). Both files are located
in the directory \<Unpack_Directory>\COMMON\ADS. After you have applied the schema extension, you
need to create a root container to store the SAP-related information and create a directory user that the
SAP application server can use to write information to the directory.
For more information about how to set up a Netscape/iPlanet directory server, see the documentation SAP
System Information in Directory Services at:
https://archive.sap.com/documents/docs/DOC-14384
• Enabling the SAP System LDAP Registration
Once you have correctly configured your directory server, you can enable the LDAP registration of the SAP
system by setting some profile parameters in the default profile.
To do this, run the software provisioning manager [page 124] once for your system and choose:

 Caution

SAP recommends that you no longer use the LDAP configuration options provided by the software
provisioning manager, because current security guidelines make it unsafe to run SAP applications on a
domain controller. Instead, SAP recommends that you follow the instructions in SAP Note 3251648
to enable LDAP directory service integration of your SAP system with Active Directory.

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.

7.2 Installation of Multiple Components in One Database

You can install multiple SAP systems in a single database. This is called Multiple Components in One Database
(MCOD).

 Recommendation

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

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

The major drawbacks are as follows:

• Previous-point-in-time (PPT) recovery of a single system within an MCOD installation becomes a highly
complex and time-consuming procedure.
• SAP Landscape Management (LaMa) is generally not supported for MCOD installations. For more
information, see SAP Note 1709155 .

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
190 PUBLIC Additional Information
 • There are strong dependencies, for example on the database version used for the MCOD system.
• Downtime - planned or unplanned - always affects all systems sharing the same database.

Exception: In case of a dual-stack split you can use the “Keep Database” option thus keeping ABAP and
Java stack in one database. There, the PPT recovery problem does not apply because both stacks belong
logically together and would always be recovered jointly anyhow. However, keep in mind that even for this
specific case the introduction of SAP Landscape Management would require a split into separate database
subsystems.

Additional information is available in SAP Note 2146542 .

MCOD is available with all SAP components and all the major databases for the SAP system. No extra effort
is required because the MCOD installation is fully integrated into the standard installation procedure. MCOD is
not an additional installation option. Instead, it is an option of the database instance installation.

With MCOD we distinguish two scenarios:

• The installation of an SAP system in a new database

• The installation of an additional SAP system in an existing database (MCOD)

Prerequisites

• For more information about MCOD and its availability on different platforms, see Multiple Components in
One Database (MCOD) at: https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=448466580 .
• Since SAP does not support mixed solutions with MCOD, your SAP system must contain Unicode SAP
instances only.
• Improved sizing required
You calculate the CPU usage for an MCOD database by adding up the CPU usage for each individual SAP
system. You can do the same for memory resources and disk space.
You can size multiple components in one database by sizing each individual component using the Quick
Sizer tool and then adding the requirements together. For more information about the Quick Sizer, see
http://sap.com/sizing .

Features

• Reduced administration effort

• Consistent system landscape for backup, system copy, administration, and recovery
• Increased security and reduced database failure for multiple SAP systems due to monitoring and
administration of only one database
• Independent upgrade
In an MCOD landscape, you can upgrade a single component independently from the other components
running in the same database, assuming that the upgraded component runs on the same database
version. However, if you need to restore a backup, be aware that all other components are also affected.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Additional Information PUBLIC 191
  Note

Special MCOD considerations and differences from the standard procedure are listed where relevant in the
installation documentation.

Constraints

• We strongly recommend that you test MCOD in a test or development system. We recommend that you
run MCOD systems in the same context. We do not recommend that you mix test, development, and
production systems in the same MCOD.
• In the event of database failure, all SAP systems running on the single database are affected.
• Automated support in an MCOD landscape for the following administrative tasks depends on your
operating system and database:
• Copying a single component from an MCOD landscape to another database at database level.
• Uninstalling a single component from an MCOD landscape requires some additional steps. You can
use a remote connection to SAP support to request help with these tasks. For more information, see
http://support.sap.com/remoteconnection .
• You cannot install a Unicode ABAP system with a non-Unicode ABAP system in one database.
• For the first SAP system, the database system ID can be different from the SAP system ID.
• For the second SAP system, you must use the same <DBSID> as for the first SAP system.
• If you decide to turn off database logging during the database load phase of the installation, you need to
plan downtime for all MCOD systems sharing the database.

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

 Caution

SAP recommends that you no longer use the LDAP configuration options provided by the software
provisioning manager, because current security guidelines make it unsafe to run SAP applications on a
domain controller. Instead, SAP recommends that you follow the instructions in SAP Note 3251648 to
enable LDAP directory service integration of your SAP system with Active Directory.

Prerequisites

During the SAP instance installation you chose to configure the SAP system to integrate LDAP services.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
192 PUBLIC Additional Information
Context

For more information, see Integration of LDAP Directory Services [page 185].

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

7.4 Exporting and Mounting Directories via NFS

Related Information

Exporting and Mounting Directories via NFS for Linux [page 196]
Exporting and Mounting Directories via NFS for AIX [page 194]
Exporting and Mounting Directories via NFS for Oracle Solaris [page 196]
Exporting and Mounting Directories via NFS for HP-UX [page 195]

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Additional Information PUBLIC 193
7.4.1 Exporting and Mounting Directories via NFS for AIX

This topic is only valid for 'Platform': AIX

This procedure describes how to export and mount directories via NFS for AIX using the command line.

Context

This section only provides the basic procedure. If you need more detailed information, check your OS vendor's
documentation.

For a general documentation about NFS on AIX, see:

Network File System ( https://www.ibm.com/docs/en/aix/7.3?topic=management-network-file-system )

Documentation for basically setting up an NFS server can be found at

Configuring an NFS server (https://www.ibm.com/docs/en/aix/7.3?topic=system-configuring-nfs-server )

Documentation for basically setting up an NFS client can be found at

Configuring an NFS client ( https://www.ibm.com/docs/en/aix/7.3?topic=system-configuring-nfs-client )

Procedure

On the host where you want to export directories (the NFS server) do the following:
1. First of all verify that NFS is running by typing the command:

lssrc -g nfs

Verify that the nfsd and the rpc.mountd daemons are reported as active.

If they are not, start NFS using the instructions in Starting the NFS daemons .
2. Export directories in one of the following ways:

• Variant 1 - using smit:

1. Call
smit mknfsexp
2. Then specify all the necessary values.
When finished, smit updates /etc/exports and exports the corresponding directory.
• Variant 2 - using text editor and explicit commands:
1. Open the file /etc/exports with your favorite text editor.
2. Create an entry for each directory to be exported.
3. Save and close the /etc/exports file.
4. Export the directory(s) with:
/usr/sbin/exportfs -a
On the host (the NFS client) where you want to mount the directories you exported in the previous step, do the
following

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
194 PUBLIC Additional Information
 3. Verify that the NFS server has exported the directory with:

showmount -e ServerName
4. Create a local mount point with:

mkdir /local/directory
5. Mount the NFS directory to that local mount point:

mount ServerName:/remote/directory /local/directory

6. To persist the NFS mount (that means automatically mount it when the system is started), call:

smit mknfsmnt

Enter or change the appropriate values.

 Note

Not all values are required.

When finished, smit mounts the NFS directory.

You can check that the NFS filesystem is mounted with:

df -g /local/directory
End of 'Platform': AIX

7.4.2 Exporting and Mounting Directories via NFS for HP-UX

This topic is only valid for 'Platform': HP-UX

This section describes how to export and mount directories via NFS for HP-UX manually.

Context

This section only provides the basic procedure. If you need more detailed information, check your OS vendor's
documentation.

Procedure

1. On the host where you want to export directories do the following:

a. Add the file system that you want to export to the file /etc/dfs/dfstab using the following syntax:

share –F nfs –o root= <client_1>:<client_n> access= <client_1>:<client_n>

<file system to share>

share –F nfs –o root=hw5111:hw5115, access=hw511:hw5115 /sapmnt/C11/exe.

If you encounter problems, try using the FQDN (Fully Qualified Domain Name).

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Additional Information PUBLIC 195
 b. To make the file system available to NFS clients, enter the following command:

/usr/sbin/shareall
2. On the host where you want to mount the directories you exported in the previous step, do the following:
a. Add the remote file system to /etc/fstab.

hw5115:/sapmnt/C11 /sapmnt/C11 nfs defaults 0 0

b. Mount the file system.

mount -a
End of 'Platform': HP-UX

7.4.3 Exporting and Mounting Directories via NFS for Linux

This topic is only valid for 'Platform': Linux

To export directories via NFS, perform the following steps.

Context

The following procedure assumes that the central instance host is the NFS server.

Procedure

• To export and mount directories via NFS, consult the documentation of your Linux vendor.
End of 'Platform': Linux

7.4.4 Exporting and Mounting Directories via NFS for Oracle

Solaris

This topic is only valid for 'Platform': Oracle Solaris

To mount directories via NFS from the host where the directory resides that you want to mount, log on as user
root and proceed as follows.

Context

This section only provides the basic procedure. If you need more detailed information, check your OS vendor's
documentation.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
196 PUBLIC Additional Information
Procedure

• On the host on which the directory to be mounted resides:

a. Enter the following command:

/usr/sbin/share
b. To add file systems shared via NFS, edit file /etc/dfs/dfstab:

vi /etc/dfs/dfstab

Add the following line for each file system:

share -F nfs -o root=<nfsclient1>:<nfsclient2>,anon=0 -d "description"

<file_system_to_be_shared>

 Note

Depending on your configuration, a full qualified name may be required for nfsclient, for
example, myclient.mydomain.com.

 Caution

After your SAP system has been installed successfully, in the above line you have to change -o
root to -o rw (or remove anon=0, respectively) for all exported directories:

share -F nfs -o rw=<nfsclient1>:<nfsclient2> -d "description"

<file_system_to_be_shared>

c. If the /etc/dfs/dfstab was empty, the NFS server is not active.

• On Solaris 10 or higher, start the NFS server with the following command:
svcadm enable svc:/network/nfs/server:default
• On Solaris 11 or higher, you can alternatively use the local ZFS (Zettabyte) file system.
d. To see if the NFS server is active and which partitions are mountable, enter the command:

showmount -e <NFS-server>
• On the host on which the additional instance runs:
a. If you are mounting NFS disks for the first time, the NFS client software is not active.
• On Solaris 10, start the NFS server with the following command:
svcadm enable svc:/network/nfs/client:default
• On Solaris 11 or higher, you can alternatively use the local ZFS (Zettabyte) file system. For more
information, see the Oracle Solaris documentation .
b. Edit the file /etc/vfstab to mount the directory:

Edit the file /etc/vfstab to mount the directory:

vi /etc/vfstab

Add the following line for each file system:

<host_name_where_directory_resides>:<file_system_to_be_shared> - <mount
point> nfs - yes -

If the mount point exists, mount <file_system_to_be_shared> with the command:

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Additional Information PUBLIC 197
 mount <mount point>
End of 'Platform': Oracle Solaris

7.5 Heterogeneous SAP System Installation

This section provides information on the installation of an SAP system in a heterogeneous system landscape.
“Heterogeneous system landscape” means that application servers run on different operating systems.

See SAP Note 1067221 for more information on:

• Supported combinations of operating systems and database systems

• How to install an application server on Windows in a heterogeneous (UNIX) SAP system environment
• Heterogeneous SAP system landscapes with different UNIX operating systems

7.6 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 (embedded installation). If you need to install the SAP Host Agent separately, use the documentation
Installation of SAP Host Agent on UNIX - 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

7.7 Splitting Off an ABAP Central Services Instance from

an Existing Primary Application Server Instance

With the installation option Split Off ASCS Instance from existing Primary Application Server Instance, you can
move the message server and the enqueue work process from an existing primary application server instance
to a newly installed ABAP central services instance (ASCS instance). The new ASCS instance is installed while
the split is done.

Prerequisites

The existing SAP system of the primary application server instance must meet the following requirements:

• It was upgraded from an SAP system release based on SAP NetWeaver lower than 7.1.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
198 PUBLIC Additional Information
 • It does not yet have an ASCS instance

Context

Before the Split

The primary application server instance includes:

• ABAP dispatcher and work processes (dialog, batch, spool, enqueue, or update)
• Gateway
• Internet communication manager (ICM)
• Internet graphics service (IGS)
• ABAP message server

After the Split

An ABAP central services instance (ASCS instance) has been split off from the existing primary application
server instance.

The primary application server instance now includes:

• ABAP dispatcher and work processes (dialog, batch, spool, or update)

• Gateway
• Internet communication manager (ICM)
• Internet graphics service (IGS)

The newly created ABAP central services instance (ASCS instance) includes:

• ABAP message server

• ABAP standalone enqueue server
The ABAP enqueue work process is now replaced with the ABAP standalone enqueue server.

 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 2 , and
Systems Based on SAP NetWeaver AS for ABAP 7.52 only: Switching to Standalone Enqueue Server 2
and Enqueue Replicator 2 [page 164] .

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Additional Information PUBLIC 199
The Effect of the Split
The following graphic provides an overview of the components contained in the primary application server
instance before and after the split, along with the newly created ASCS instance:

Procedure

1. Plan the basic parameters, as described in SAP System Parameters [page 54]:
• Choose an instance number for the ASCS instance to be created.
• Note that the message server port is not changed during the split.
2. Check the hardware and software requirements for the ASCS instance to be created as described in
Hardware and Software Requirements [page 39].
3. Specify basic SAP System Parameters [page 54] for the ASCS instance to be created.
4. Set up the required file systems [page 83] for the ASCS instance to be created.
5. Check the prerequisites [page 120] and start the software provisioning manager [page 124] on the host
where the ASCS instance is to be created.

6. On the Welcome screen, choose Generic Options <Database> Split Off ASCS Instance from Existing
Primary Application Server Instance .
7. Follow the instructions on the software provisioning manager screens 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 UNIX: SAP MaxDB
200 PUBLIC Additional Information
  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 entered all requested input parameters, the software provisioning manager displays the
Parameter Summary screen. This screen shows both the parameters that you entered and those that the
software provisioning manager set by default. If required, you can revise the parameters before starting the
installation.
8. To start the installation, choose Start.

 Caution

All SAP system instances are stopped during the split procedure.

The software provisioning manager starts the installation and displays the progress of the installation.
When the installation has successfully completed, the software provisioning manager shows the dialog
Execution of Split Off ASCS Instance from existing Primary Application Server Instance has completed.
9. You check and if necessary modify the settings for the operating system users for your SAP system if they
were created by the software provisioning manager.
For more information, see Creating Operating System Users and Groups [page 78].
10. Restart the application server instances [page 201] (primary application server instance and additional
application server instances if they exist).
11. Check whether you can log on to the application servers [page 147].
12. Ensure user security [page 168] for the operating system users of the newly created ASCS instance.
13. 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 standalone enqueue server 2 and enqueue replication server .
14. If required, perform an installation backup [page 179].

7.8 Starting and Stopping SAP System Instances

Start or stop SAP system instances in one of the following ways:

• Using the SAP Management Console (SAP MC) [page 202]

• Using commands [page 205].

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Additional Information PUBLIC 201
7.8.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 UNIX: SAP MaxDB
202 PUBLIC Additional Information
 • 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 Solution
http://help.sap.com/nw731
Life Cycle Management SAP Management Console
• 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

• 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 Solution
http://help.sap.com/nw731
Life Cycle Management SAP Microsoft Management
• SAP NetWeaver 7.4
http://help.sap.com/nw74 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

Only valid for 'Platform': Linux

 Note

Linux only: If your server runs on a Linux distribution using systemd version 234 or later, it's technically
possible that you use systemd commands on operating system level to start and stop SAP systems.
However, we recommend that you do not use these systemd commands. For example, using systemd to
restart or stop the systemd unit will not only stop the start service, but the entire related SAP instance
with time limits for the processes to shut down. This might end in unexpected results. To start and stop
SAP instances, we recommend that you use the SAP Management Console, as outlined here, or the
sapcontrol commands (see also Starting and Stopping SAP System Instances Using Commands [page
205]). For more information about systemd, see SAP Note 3139184 .

End of 'Platform': Linux

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Additional Information PUBLIC 203
Procedure

• Starting the Web-Based SAP Management Console

1. Start a Web browser and enter the following URL:
http://<Host_Name>:5<Instance_Number>13

 Example

If the instance number is 53 and the host name is saphost06, you enter the following URL:

http://saphost06:55313

This starts the SAP MC Java applet.

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
204 PUBLIC Additional Information
  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.
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.

7.8.2 Starting and Stopping SAP System Instances Using

Commands

Prerequisites

You are logged on to the SAP system host as user <sapsid>adm.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Additional Information PUBLIC 205
Context

 Note

The startsap and stopsap commands are deprecated. SAP recommends that you do not use them any
longer. For more information, see SAP Notes 1763593 and 809477 .

Only valid for 'Platform': Linux

Linux only: If your server runs on a Linux distribution using systemd version 234 or later, it's technically
possible that you use systemd commands on operating system level to start and stop SAP systems.
However, we recommend that you do not use these systemd commands. For example, using systemd to
restart or stop the systemd unit will not only stop the start service, but the entire related SAP instance with
time limits for the processes to shut down. This might end in unexpected results. To start and stop SAP
instances, we recommend that you use the sapcontrol commands or the SAP Management Console (see
also Starting and Stopping SAP System Instances Using the SAP Management Console [page 202]). For
more information about systemd, see SAP Note 3139184 .
End of 'Platform': Linux

This section only lists the basic commands how to start or stop an SAP system. You can find a detailed list of all
SAPControl options and features in the command line help, which you can call as follows:

/usr/sap/<SAPSID>/<INSTANCE><NUMBER>/exe/sapcontrol --help

 Example

/usr/sap/GB1/D00/exe/sapcontrol --help

Procedure

• Starting an SAP System or Instance

• Starting an SAP System:

You can start an SAP system by executing the following commands from the command line
(<Instance_Number> can be the number of any instance of the SAP system):
/usr/sap/<SAPSID>/<INSTANCE><NUMBER>/exe/sapcontrol -nr <instance_number>
-function StartSystem

 Example

/usr/sap/GB1/D00/exe/sapcontrol -nr 01 -function StartSystem

• Starting an SAP System Instance

You can start an SAP system instance by executing the following commands from the command line:
/usr/sap/<SAPSID>/<INSTANCE><NUMBER>/exe/sapcontrol -nr <instance_number>
-function Start

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
206 PUBLIC Additional Information
  Example

Starting an instance with <instance_number> 02: /usr/sap/GB1/D00/exe/sapcontrol -nr

02 -function Start

For remote instances, the syntax is slightly different, because you also have to apply the -host and
-user parameters:
/usr/sap/<SAPSID>/<INSTANCE><NUMBER>/exe/sapcontrol –nr <instance_number>
-host <remote host> –user <sapsid>adm <password> -function Start

 Example

Starting a remote instance with <instance_number> 02: /usr/sap/GB1/D00/exe/

sapcontrol -nr 02 -host myremotehost –user gb1adm -function Start

• Stopping an SAP System or Instance

• Stopping an SAP System

You can stop an SAP system by executing the following commands from the command line
(<Instance_Number> can be the number of any instance of the SAP system):
/usr/sap/<SAPSID>/<INSTANCE><NUMBER>/exe/sapcontrol -nr <instance_number>
-function StopSystem

 Example

/usr/sap/GB1/D00/exe/sapcontrol -nr 01 -function StopSystem

• Stopping an SAP System Instance

You can stop an SAP system instance by executing the following commands from the command line:
/usr/sap/<SAPSID>/<INSTANCE><NUMBER>/exe/sapcontrol -nr <instance_number>
-function Stop

 Example

Stopping an instance with <instance_number> 02: /usr/sap/GB1/D00/exe/sapcontrol

-nr 02 -function Stop

For remote instances, the syntax is slightly different, because you also have to apply the -host and
-user parameters:
/usr/sap/<SAPSID>/<INSTANCE><NUMBER>/exe/sapcontrol –nr <instance_number>
-host <remote host> –user <sapsid>adm <password> -function Stop

 Example

Stopping a remote instance with <instance_number> 02: /usr/sap/GB1/D00/exe/

sapcontrol -nr 02 -host myremotehost –user gb1adm -function Stop

 Note

The database is not stopped by these commands. You have to stop the database using database-
specific tools or commands.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Additional Information PUBLIC 207
• Checking System Instance and Processes

• With the following command you get a list of system instances, their status, and the ports used by
them (<Instance_Number> can be the number of any instance of the SAP system):
/usr/sap/<SAPSID>/<INSTANCE><NUMBER>/exe/sapcontrol –nr <instance_number>
-host <remote host> –user <sapsid>adm <password> -function
GetSystemInstanceList

 Example

/usr/sap/GB1/D00/exe/sapcontrol -nr 02 -host myremotehost –user gb1adm

-function GetSystemInstanceList

• With the following command you get a list of instance processes and their status:
/usr/sap/<SAPSID>/<INSTANCE><NUMBER>/exe/sapcontrol –nr <instance_number>
-host <remote host> –user <sapsid>adm <password> -function GetProcessList

 Example

/usr/sap/GB1/D00/exe/sapcontrol -nr 02 -host myremotehost –user gb1adm

-function GetProcessList

• Troubleshooting

If you get an error like "FAIL: NIECONN_REFUSED", execute sapcontrol -nr <Instance_Number>
-function StartService <SAPSID> to ensure that sapstartsrv is running. Then execute again the
start or stop command.

7.9 Uninstalling an SAP System or Single Instances

Uninstalling an SAP system or single instances is described in this section. It includes prerequisites, manual
steps, and recommendations for deleting the system or instances using the software provisioning manager. It
also provides information on deleting database content and other related considerations.

Prerequisites

• You have installed your SAP system with standard SAP tools according to the installation documentation.
• You are logged on as a user with root permissions.

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
208 PUBLIC Additional Information
  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.

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, groups or service entries in an environment with Network Information
System (NIS), other SAP installations might also be affected. Make sure that the users, groups, and service
entries to be deleted 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.

Procedure

1. Start the software provisioning manager as described in Running Software Provisioning Manager [page
124].
2. On the Welcome screen, choose:

Generic Installation Options <Database> Uninstall Uninstall SAP Systems or Single Instances
3. Follow the instructions on the software provisioning manager 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
software provisioning manager.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Additional Information PUBLIC 209
 Deletion of Remarks

Standard system You can delete a standard system (where all instances reside on the same host) in one
software provisioning manager run.

Distributed or high-availability If you want to delete a distributed or high-availability system, you have to run the
system software provisioning manager to delete the required instances locally on each of the
hosts belonging to the SAP system in the following sequence:

 Caution
Only select checkbox Uninstall all instances of the SAP system from this host when
removing the last remaining instance of the SAP system. Otherwise the contents
of mounted global directories under /<sapmnt>/<SAPSID>/ such as instance
profiles and kernel executables, are also deleted.

1. Additional application server instances, if there are any

2. Primary application server instance
3. Database instance
Since the software provisioning manager only stops local instances automati-
cally, make sure that before deleting the database instance of a distributed
system, you stop all remaining instances. You must stop the instance with the
message server only after having entered all software provisioning manager pa-
rameters for the deletion of the database instance.
Choose whether you want to drop the entire database or only one or more
database schemas. If you drop the entire database, the software provisioning
manager also asks whether you want to remove the database software.
4. ABAP Central services instance (ASCS)

 Note
To delete system directories mounted from an NFS server, you have to run the
software provisioning manager on the NFS server.

Additional application server If you want to delete additional application server instances of an existing SAP system,
you have to run the software provisioning manager 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
remaining 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. If you created the directories /usr/sap/<SAPSID> and /<sapmnt>/<SAPSID> as mount points, but not
as directories on the local file system, you have to remove them manually.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
210 PUBLIC Additional Information
 6. 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
7. If the following directories and files exist, delete them by entering the following command:

WRKLNKSAP

• /usr/sap/trans/cofiles/*<SAPSID>*
• /usr/sap/trans/data/*<SAPSID>*
• /usr/sap/trans/log/*<SAPSID>*
• /usr/sap/trans/buffer/*<SAPSID>*

Choose 4 (Remove) on every file that is found by the command WRKLNKSAP.

 Example

For example, for directory /usr/sap/trans/data, enter the following command:

WRKLNKSAP DIR('/usr/sap/trans/data/*<SAPSID>*')

Choose 4 (Remove) on the listed files.

 Note

To limit the command WRKLNKSAP, choose Subset (in the upper right part on the screen).

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

9. If the library SAPSLT<SAPSID> still exists, you must delete it. The library SAPSLT<SAPSID> is a leftover
of an SAP upgrade.

It should have been deleted after the SAP upgrade, already. Use the following command to delete the
library SAPSLT<SAPSID>, now:

DLTLIB LIB(SAPSLT<SAPSID>)

Results

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.

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Additional Information PUBLIC 211
7.10 Switching to Native systemd Support for sapstartsrv

This topic is only valid for 'Platform': Linux

Learn how you can switch from the SysV init mode to native systemd support in SAP systems running on Linux.

Prerequisites

Make sure polkit is installed. The software suite systemd requires polkit for authorization checks for the
<sapsid>adm user.

Context

An SAP system is not directly managed by the operating system init system, but you start and stop an SAP
system using the SAP startup framework. The sapstartsrv daemon provides an external interface for clients
to initiate different tasks, like start/stop of the system or more complex operations related to high availability
solutions.

For previous kernel versions and older Linux releases, sapstartsrv used the SysV init system, which, in
combination with systemd, results in the systemd compatibility mode as its technical basis in Linux operation
systems.

Starting with SUSE Linux Enterprise Server 15, Red Hat Enterprise Linux 8, and Oracle Linux 8, and the
respective SAP kernel patch levels, native support for the software suite systemd for Linux is available for
SAP systems. When you install SAP systems using software provisioning manager, native systemd support
is automatically activated. Existing SAP systems, however, are not automatically switched to native systemd
support, but you can perform the switch manually.

Procedure

1. In SAP Note 3139184 , check whether systemd is supported for your kernel version and Linux
distribution and operating system version.
2. If you want to switch from systemd compatibility mode to native systemd support for sapstrtsrv, follow
the steps in SAP Note 3115048 .
End of 'Platform': Linux

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
212 PUBLIC Additional Information
Important Disclaimers and Legal Information

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

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

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

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

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

Videos Hosted on External Platforms

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

Beta and Other Experimental Features

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

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

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

Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX: SAP MaxDB
Important Disclaimers and Legal Information PUBLIC 213
www.sap.com/contactsap

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

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

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

Some software products marketed by SAP SE and its distributors

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

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

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

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

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

additional trademark information and notices.

THE BEST RUN