Installation Guide
Software Provisioning Manager 1.0 SP22
Document Version: 2.9 – 2018-01-15
Installation of SAP Systems Based on the
Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
PUBLIC
Content
1
About this Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.1
Naming Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.2
Constraints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.3
Before You Start. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.4
SAP Notes for the Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.5
New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
New Features - Software Provisioning Manager 1.0 SP22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
New Features - Software Provisioning Manager 1.0 SP21 and Lower. . . . . . . . . . . . . . . . . . . . . . . 17
2
Installation Options Covered by this Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.1
Standard System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.2
Distributed System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.3
High-Availability System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.4
Additional Application Server Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.5
Splitting off an ABAP Central Services Instance from an Existing Primary Application Server
Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.6
ASCS Instance with Integrated SAP Web Dispatcher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.7
ASCS Instance with Integrated Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.8
SAP Host Agent as a Separate Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
3
Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.1
Planning Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.2
Changed File System Structure and Profiles for SAP Systems Based on SAP NetWeaver 7.1 and
Higher. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.3
Installation Using a Stack Configuration File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3.4
Hardware and Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Running the Prerequisites Check in Standalone Mode (Optional). . . . . . . . . . . . . . . . . . . . . . . . 39
Requirements for the SAP System Hosts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3.5
Planning User and Access Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
3.6
Basic Installation Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
SAP System Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
SAP System Database Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Additional Parameters when Installing SAP Process Integration 7.5 or SAP Solution Manager
7.2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Additional Parameters When Using a Stack Configuration File (Optional). . . . . . . . . . . . . . . . . . 69
Parameters for Additional Components to be Included in the ASCS Instance (Optional). . . . . . . . 71
3.7
Distribution of SAP System and Oracle Database Components to Disks. . . . . . . . . . . . . . . . . . . . . . 72
3.8
SAP System Transport Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
2
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Content
3.9
Planning the Switchover Cluster for High Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
4
Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
4.1
Preparation Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
4.2
Creating Operating System Users and Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
4.3
Required File Systems and Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
SAP Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Oracle Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Setting Up File Systems for a High-Availability System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
4.4
Using Virtual Host Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
4.5
Performing Switchover Preparations for High Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
4.6
Installing the SAP Front-End Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
4.7
Preparing the Installation Media. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Downloading and Extracting the Software Provisioning Manager 1.0 Archive. . . . . . . . . . . . . . . 102
Using the Physical Media from the Installation Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Downloading SAP Kernel Archives (Archive-Based Installation). . . . . . . . . . . . . . . . . . . . . . . . .107
Downloading Complete Installation Media. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110
5
Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
5.1
Installation Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
5.2
Exporting and Mounting the Transport Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119
5.3
Exporting and Mounting Global Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
5.4
Specifying the Initial Data Source of the User Management Engine. . . . . . . . . . . . . . . . . . . . . . . . .122
5.5
Prerequisites for Running the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
5.6
Running the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
5.7
Additional Information About the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Useful Information About the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131
Interrupted Processing of the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Entries in the Services File Created by the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Troubleshooting with the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137
Using the Step State Editor (SAP Support Experts Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
5.8
Oracle Database Software Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Oracle 11 Database Software Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139
Oracle 12 Database Software Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
6
Post-Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
6.1
Post-Installation Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
6.2
Logging On to the Application Server ABAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
6.3
SAP NetWeaver 7.4 and Higher: Performing Automated Initial Setup (Optional). . . . . . . . . . . . . . . . 153
6.4
Installing the SAP License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
6.5
High Availability: Setting Up Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
6.6
Configuring the Remote Connection to SAP Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Content
PUBLIC
3
6.7
Installing SAP Online Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
6.8
Performing the Consistency Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
6.9
Configuring the Change and Transport System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
6.10
Connecting the System to SAP Solution Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162
6.11
Applying the Latest Kernel and Support Package Stacks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
6.12
Performing Post-Installation Steps for the ABAP Application Server. . . . . . . . . . . . . . . . . . . . . . . . 165
6.13
SAP Solution Manager 7.2, SAP Process Integration 7.5 only: Enabling HTTPS Communication for
ABAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
6.14
Installing Additional Languages and Performing Language Transport. . . . . . . . . . . . . . . . . . . . . . . 169
6.15
SAP Kernel 7.40 and Higher: IP Multicast Configuration and Wake-Up Mechanism. . . . . . . . . . . . . . 171
6.16
PI 7.5 Only: Configuring the Process Integration System After the Installation. . . . . . . . . . . . . . . . . 171
6.17
Configuring the User Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
6.18
Ensuring User Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173
6.19
Performing the Client Copy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177
6.20
Performing Oracle-Specific Post-Installation Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
6.21
SAP Systems Based on SAP NetWeaver 7.4 and Higher: Changing Keys for the Secure Storage
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
6.22
Performing a Full Installation Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182
6.23
Logging on to the SAP Web Dispatcher Management Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
6.24
SAP Web Dispatcher Configuration (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
6.25
Gateway Configuration (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188
7
Additional Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
7.1
Integration of LDAP Directory Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
7.2
Installation of Multiple Components in One Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
7.3
Creating a User for LDAP Directory Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197
7.4
Exporting and Mounting Directories via NFS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Exporting and Mounting Directories via NFS for AIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198
Exporting and Mounting Directories via NFS for HP-UX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Exporting and Mounting Directories via NFS for Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Exporting and Mounting Directories via NFS for Oracle Solaris. . . . . . . . . . . . . . . . . . . . . . . . . 202
7.5
Heterogeneous SAP System Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
7.6
Installing Oracle Real Application Clusters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204
7.7
Database Instance Installation on Oracle Automatic Storage Management. . . . . . . . . . . . . . . . . . . 207
7.8
Implementing Oracle Database Vault with the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
7.9
Oracle Database 12c Multitenant Database Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209
Installing the Container Database and a Pluggable Database. . . . . . . . . . . . . . . . . . . . . . . . . . 210
Installing a Distributed Application Server Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Installing an Additional Pluggable Database in a Pre-Installed Container Database. . . . . . . . . . . 211
7.10
Installing the SAP Host Agent Separately. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
7.11
Splitting Off an ABAP Central Services Instance from an Existing Primary Application Server
Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
4
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Content
7.12
Starting and Stopping SAP System Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Starting and Stopping SAP System Instances Using the SAP Management Console. . . . . . . . . . 218
Starting and Stopping SAP System Instances Using Commands. . . . . . . . . . . . . . . . . . . . . . . 222
7.13
Deleting an SAP System or Single Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
7.14
Oracle Database Software Uninstallation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Uninstalling the Oracle 11 Database Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Uninstalling the Oracle 12 Database Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Content
PUBLIC
5
Document History
The following table provides an overview on the most important document changes.
Note
Before you start the implementation, make sure you have the latest version of this document, which is
available at https://support.sap.com/sltoolset
Provisioning Manager
System Provisioning
Installation Option of Software
.
Table 1:
Version
Date
Description
2.9
2018-01-15
Updated version for software provisioning manager 1.0 SP22 (SL Toolset 1.0 SP22)
●
New Features:
○
Signature check for installation archives, documented in: New Features, Downloading
SAP Kernel Archives (Archive-Based Installation) Archive-Based Installation for Diagnos­
tics Agent, Downloading the SAP Kernel Archives Required for the Dual-Stack Split (With­
out Operating System and Database Migration), Downloading the SAP Kernel Archives
Required for Operating System and Database Migration
○
Installer Log Files Improvements, documented in: New Features, Useful Information
about the Installer, Troubleshooting with the Installer
○
Secure ABAP message server connection, documented in: New Features, SAP System
Parameters
○
●
Enabling IPv6, documented in: New Features, Prerequisites for Running the Installer
New Features section restructured: As of SP22, a dedicated subsection for each new SP has
been created. New features below SP22 remain in a common table.
●
The Java SDT GUI - which was in the SP21 version still available in parallel to the SL Common
GUI - has been deprecated with SP22. As of SP22, SL Common GUI is the only available in­
staller GUI:
○
The following sections which were explicitely related to Java SDT GUI were completely
removed from this documentation: Performing a Remote Installation Remote Processing
of the Installer ( Java SDT GUI only), Starting the Java SDT GUI Separately, Running the
Installer in Accessibility Mode (general accessibility information was moved to Useful In­
formation About the Installer).
○
The Java SDT GUI-specific information was removed from the common installer sec­
tions: Running the Installer, Useful Information About the Installer, Interrupted Process­
ing of the Installer, Troubleshooting with the Installer, Deleting an SAP System or Single
Instances
●
6
PUBLIC
New section Using the Step State Editor (SAP Support Experts Only) was added to section
Additional Information About the Installer
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Document History
Version
Date
Description
2.8
2017-09-11
Updated version for software provisioning manager 1.0 SP21 (SL Toolset 1.0 SP21)
●
New Features:
○
Media Signature Check, documented in: New Features, Running the Installer, 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 related option in the installer
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 Parameters,
Downloading SAP Kernel Archives (Archive-Based Installation)
○
Load tools are now available as LOADTOOLS.SAR in the Software Provisioning Manager
archive, documented in: New Features, Downloading and Extracting the Software Provi­
sioning Manager Archive
○
Simplified additional application server instance installation, documented in: New Fea­
tures, Preparing the Installation Media, Downloading SAP Kernel Archives (Archive-Based
Installation)
2.7
2017-05-22
○
Support of Oracle 12.2, documented in: New Features, Installing the Oracle 12c Database
Software
○
Support of Oracle Database Vault, documented in: New Features, Planning Checklist,
SAP System Database Parameters, Preparation Checklist, Post-Installation Checklist, Im­
plementing Oracle Database Vault Using the Installer
Updated version for software provisioning manager 1.0 SP20 (SL Toolset 1.0 SP20)
●
New Features:
○
New SAPUI5-based graphical user interface (GUI) “SL Common GUI”, documented in:
Prerequisites for Running the Installer, Running the Installer, Useful Information About
the Installer
○
Option for choosing to install an integrated SAP Gateway during the ASCS instance in­
stallation, documented in: Installation Options Covered by this Guide, SAP System Pa­
rameters, 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 Parameters, Creating
Operating System Users and Groups
2.6
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 Configuration File
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Document History
PUBLIC
7
Version
Date
Description
2.5
2016-10-07
Updated version for software provisioning manager 1.0 SP18 (SL Toolset 1.0 SP18)
●
New Features:
Option to choose installing an integrated SAP Web Dispatcher during the ASCS instance in­
stallation, documented in: ASCS Instance with Integrated SAP Web Dispatcher [page 29].
Oracle Multitenant Installation, documented in: Oracle Database 12c Multitenant Database
Installation [page 209]
Using RMOSSWPM*.SAR instead of SWPM*.SAR for outdated OS versions not supported by
SAP kernel 7.40 and higher, documented in:
2.4
2016-06-06
Introduction
Constraints
Updated version for software provisioning manager 1.0 SP17 (SL Toolset 1.0 SP17):
●
New Features:
“ Archive-Based Installation”, documented in:
○
New Features [page 15]
○
Preparing the Installation Media [page 100]
Downloading Specific Installation
Archives (Archive-Based Installation)
2.3
2016-02-15
Updated version for software provisioning manager 1.0 SP10 (SL Toolset 1.0 SP16)
2.21
2015-10-29
Updated version for software provisioning manager 1.0 SP09 (SL Toolset 1.0 SP15)
2.2
2015-10-12
Updated version for software provisioning manager 1.0 SP09 (SL Toolset 1.0 SP15)
2.1
2015-09-14
Updated version for software provisioning manager 1.0 SP09 (SL Toolset 1.0 SP14)
2.0
2015-04-27
Updated version for software provisioning manager 1.0 SP08 (SL Toolset 1.0 SP13)
1.9
2014-11-24
Updated version for software provisioning manager 1.0 SP07 (SL Toolset 1.0 SP12)
1.8
2014-09-24
Updated version for software provisioning manager 1.0 SP06 (SL Toolset 1.0 SP11)
Updates for migration to SAP HANA database added
1.7
2014-07-07
Updated version for software provisioning manager 1.0 SP06 (SL Toolset 1.0 SP11)
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 for software provisioning manager 1.0 SP05 (SL Toolset 1.0 SP10)
1.5
2013-10-28
Updated version
1.4
2013-07-15
Updated version
1.3
2013-04-02
Updated version
1.2
2012-11-27
Updated version
8
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Document History
Version
Date
Description
1.1
2012-09-25
Updated version
1.0
2012-08-06
Initial version
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
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.1 to 7.5x using the installation tool Software Provisioning Manager 1.0 SP22 (“installer” for short),
which is part of SL Toolset 1.0 SP22.
Note
As an alternative to using Software Provisioning Manager, you can install your system with a completely
automated end-to-end framework available using SAP Landscape Management. For more information, see
SAP Note 1709155
and https://help.sap.com/lama .
This guide is valid for the operating systems AIX, HP-UX, Linux, and Solaris, and covers the SAP system
products and releases listed in SAP Note 1680045 .
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 12] before you continue with this installation guide.
Related Information
Naming Conventions [page 10]
Constraints [page 11]
Before You Start [page 12]
SAP Notes for the Installation [page 13]
New Features [page 15]
1.1
Naming Conventions
● Software Provisioning Manager 1.0 is the successor of the product- and release-specific delivery of
provisioning tools, such as “SAPinst”.
Before you perform an installation from scratch or a target system installation in the context of a system
copy, we strongly recommend that you always download the latest version of the Software Provisioning
Manager 1.0 which is part of the Software Logistics Toolset 1.0 (“SL Toolset” for short). For more
information, see Preparing the Installation Media [page 100].
This way, you automatically get the latest version with the latest fixes of the tool and supported processes.
For more information about Software Provisioning Manager 1.0 as well as products and releases supported
10
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
About this Document
by it, see SAP Note 1680045
and https://wiki.scn.sap.com/wiki/display/SL/Software+Provisioning
+Manager+1.0 .
“SAPinst” has been renamed to “Software Provisioning Manager” (“installer” for short) in this
documentation, but the terms “SAPinst” and “sapinst” are still used in:
○ The name of the technical framework of Software Provisioning Manager. For more information about
the SAPinst Framework, see SAP Note 2393060 .
○ Texts and screen elements in the Software Provisioning Manager GUI
○ Names of executables, for example sapinst
○ Names of command line parameters, for example SAPINST_USE_HOSTNAME
○ Names of operating system user groups, such as the additional group sapinst
● “usage type”, “technical usage”, and “product instance”
As of Software Provisioning Manager 1.0 SP07 (SL Toolset 1.0 SP12), the term “product instance” replaces
the terms “ usage type” and “technical usage” for SAP systems based on SAP NetWeaver 7.3 including
enhancement package 1 and higher. For more information, see SAP Note 1970349 . Note that there is no
terminology change for older releases and all mentioned terms can be used as synonyms. As this guide is a
generic document, the currently used terms remain but only “product instance” is used from now on when
referring to SAP NetWeaver 7.3 EHP1 and higher.
For more information, see New Features [page 15].
● “installer” refers to “Software Provisioning Manager”.
● “SAP system” refers to SAP system based on the application server of SAP NetWeaver Mobile / Banking
7.1 / 7.1 including Enhancement Package 1 / SAP NetWeaver 7.3 / 7.3 including Enhancement Package 1 /
SAP NetWeaver Application Server for 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 .
● “ABAP system” refers to SAP system based on the application server ABAP of SAP NetWeaver Mobile /
Banking 7.1 / 7.1 including Enhancement Package 1 / SAP NetWeaver 7.3 / 7.3 including Enhancement
Package 1 / SAP NetWeaver Application Server for ABAP 7.4 / SAP NetWeaver 7.4 / 7.4 SR1.
● “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.
1.2
Constraints
● 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
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
About this Document
PUBLIC
11
check SAP Note 1680045
to ensure that the installation options you want to perform are already
supported. For information about supported operating system and database platforms, see the Product
Availability Matrix at http://support.sap.com/pam .
● Note that a complete system installation from scratch is not available for every product. For some products
- such as SAP NetWeaver 7.4 - a complete new system installation from scratch is only provided for the
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 222].
● Client 066 is no longer available in newly installed SAP systems based on SAP NetWeaver 7.5. For more
information, see SAP Note 1749142 .
1.3
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 the Master Guide in your installation package or you can download the latest
version from http://help.sap.com.
The following table lists the Master Guides of the SAP system applications for which you can use this
installation guide, along with the available quick link or path to the appropriate download location:
Table 2:
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>
12
PUBLIC
Installation and Upgrade
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
About this Document
Document
Internet Address
Master Guide – SAP NetWeaver 7.4
http://help.sap.com/nw74
Installation and Upgrade
Master Guide SAP Supply Chain Management 7.0
http://help.sap.com/scm
<Including SAP Enhancement Package
<Number> Powered by SAP NetWeaver
Master Guide (Including Upgrade Information) -
<Release>
Installation and Upgrade
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>
Master Guide – SAP Enhancement Package 1 for
Installation and Upgrade
http://help.sap.com/nw731
SAP NetWeaver 7.3
Installation and Upgrade
Master Guide – SAP NetWeaver 7.3
http://help.sap.com/nw73
Installation and Upgrade
Master Guide - SAP NetWeaver Mobile 7.1
http://help.sap.com/nwmobile711
Installation and Upgrade
Master Guide – SAP for Banking Release 5.0 or 6.0 http://help.sap.com/bankingservices
<Release>
1.4
Installation and Upgrade
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 .
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
About this Document
PUBLIC
13
Table 3: SAP Notes for the Installation
SAP Note Number
1680045
Title
Description
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
2378874
2172935
Install SAP Solutions on Linux on IBM Power
Information about how to install SAP solutions on
Systems (little endian)
Linux on IBM Power Systems (little endian)
Installation - SAP Systems based on SAP
Oracle-specific information about the SAP sys­
NetWeaver on Oracle
tem installation and corrections to this documen­
tation
2396282
1431800
Installation, System Copy, and Rename of NW
7.3x and NW 7.2x AS Java Systems with Oracle
12c
Since the Java DVD containing open*sql.jar does
not support Oracle 12c, this note describes a
workaround for the installation, system copy, and
system rename with Oracle 12x, which is neces­
sary for the installation, system copy or rename
directly with Oracle12c.
Oracle 11.2.0: Central Technical Note
Information about Oracle 11g with multiple links
to notes on Oracle 11g
2470660
Central Technical Note for Oracle Database
12c Release 2 (12.2)
Information about Oracle 12c Release 2 (12.2)
with multiple links to notes on Oracle 12c Release
2 (12.2)
1914631
Central Technical Note for Oracle Database
Information about Oracle 12c Release 1 (12.1) with
12c Release 1 (12.1)
multiple links to notes on Oracle 12c Release 1
(12.1)
Installing two Oracle databases on a host
98252
This SAP Note is only required if you plan to in­
stall more than one Oracle database on the same
host
Supported Languages and Code Pages
73606
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
14
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
About this Document
SAP Note Number
Title
Description
Composite SAP Note for heterogeneous instal­ This SAP Note and its related SAP Notes describe
1067221
lation
the released operating system and database
combinations for heterogeneous SAP systems
landscapes.
Support Package levels for SAP NetWeaver in­
789220
stallations/upgrades
Information about the ABAP Support Package
levels and kernel patch levels contained in the
current SAP NetWeaver release
819722
Support Package levels for SRM installations/
Information about the ABAP Support Package
upgrades
levels and kernel patch levels contained in the
current SAP SRM release
Support Package levels of ERP/ECC installa­
774615
tions/upgrades
Information about the ABAP Support Package
levels and kernel patch levels contained in the
current SAP ERP release
Support Package levels for CRM installations/
837413
upgrades
Information about the ABAP Support Package
levels and kernel patch levels contained in the
current SAP CRM release
Support Package levels for SCM/APO installa­
850038
tions/upgrades
Information about the ABAP Support Package
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.
1.5
New Features
The sections below provide an overview of the new features in Software Provisioning Manager 1.0
(the“ installer” for short).
Make sure that you also read the Release Notes for your SAP product at https://help.sap.com
your SAP Product>
<Select your SAP Product Version>
What’s New
<Search
.
New Features - Software Provisioning Manager 1.0 SP22 [page 16]
The table in this section provides an overview of the new features in Software Provisioning Manager 1.0
available as of SP22 (SL Toolset 1.0 SP22).
New Features - Software Provisioning Manager 1.0 SP21 and Lower [page 17]
The table in this section provides an overview of the new features in Software Provisioning Manager 1.0
available as of SP21 (SL Toolset 1.0 SP21) and lower.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
About this Document
PUBLIC
15
1.5.1 New Features - Software Provisioning Manager 1.0 SP22
The table in this section provides an overview of the new features in Software Provisioning Manager 1.0
available as of SP22 (SL Toolset 1.0 SP22).
Make sure that you also read the Release Notes for your SAP product at https://help.sap.com
your SAP Product>
<Select your SAP Product Version>
What’s New
<Search
.
Table 4:
Feature
Description
Secure ABAP Message Server Connection
The installer now uses secure connections to the ABAP message server
of the SAP system being installed. For more information, see the ABAP
Message Server Port entry within the Ports table in SAP System Parame­
ters [page 56].
Installer Log Files Improvements
Installer log files are now available immediately after the installer has
been started, that is before a product has been selected on the Welcome
screen. For more information, see Useful Information About the Installer
[page 131] and Troubleshooting with the Installer [page 137].
Signature Check of Installation Archives
The signature of installation archives is checked automatically by the in­
staller during the Define Parameters phase while processing the Software
Package Browser screens. As of now the installer only accepts archives
whose signature has been checked. For more information, see Download­
ing SAP Kernel Archives (Archive-Based Installation) [page 107] .
LOADTOOLS.SAR archive in Software Provi­
The load tools in
sioning Manager enabled for NUC
SWPM10SP<Support_Package_Number>_<Version_Number>.SAR
are now also enabled for an installation using non-Unicode (NUC) kernel
version 7.40 or higher.
For more information, see Downloading and Extracting the Software Pro­
visioning Manager 1.0 Archive [page 102]
Note
This feature enhances feature LOADTOOLS.SAR archive in Software
Provisioning Manager of Software Provisioning Manager 1.0 SP21 (SL
Toolset 1.0 SP21) (see entry LOADTOOLS.SAR archive in Software
Provisioning Manager in New Features - Software Provisioning Man­
ager 1.0 SP21 and Lower [page 17]).
Enabling IPv6
You can now set up a new SAP system or SAP system instance using In­
ternet Protocol Version 6 (IPv6).
For more information, see Prerequisites for Running the Installer [page
122].
16
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
About this Document
1.5.2 New Features - Software Provisioning Manager 1.0 SP21
and Lower
The table in this section provides an overview of the new features in Software Provisioning Manager 1.0
available as of SP21 (SL Toolset 1.0 SP21) and lower.
Make sure that you also read the Release Notes for your SAP product at https://help.sap.com
your SAP Product>
<Select your SAP Product Version>
What’s New
<Search
.
Table 5:
Feature
Description
Availability
Media Signature
The signature of media is checked automatically by the installer
Check
during the Define Parameters phase while processing the Media
Software Provisioning Manager
1.0 SP21 (SL Toolset 1.0 SP21)
Browser screens. As of now the installer only accepts media
whose signature has been checked. See also the description of
this new security feature in SAP Note 2393060
.
For more information, see Preparing the Installation Media [page
100] and Running the Installer [page 125].
SAP Host Agent Up­ During the Define Parameters phase of the installation, the instal­
grade During the In­ ler prompts you whether you want to upgrade an existing version
stallation (Optional) of the SAP Host Agent on the installation host. If there is no SAP
Host Agent on the installation host, it is installed automatically
without prompt. For more information, see the General Parame­
ters table in SAP System Parameters [page 56] .
Software Provisioning Manager
1.0 SP21 (SL Toolset 1.0 SP21)
Simplified Addi­
tional Application
Server Instance In­
stallation
During an additional application server installation, kernel ar­
chives are only prompted if they cannot be retrieved from the pri­
mary application server instance of the existing SAP system. For
more information, see Preparing the Installation Media [page
100].
Software Provisioning Manager
1.0 SP21 (SL Toolset 1.0 SP21)
LOADTOOLS.SAR
An up-to-date version of the load tools - such as R3load,
Software Provisioning Manager
R3szchk, R3ldctl, SAPuptool - which were available so far only 1.0 SP21 (SL Toolset 1.0 SP21)
in the SAPEXEDB.SAR archive of the kernel media, has now been
made available in the Software Provisioning Manager archive. For
an installation using Unicode kernel version 7.40 or higher, the
load tools from the
SWPM10SP<Support_Package_Number>_<Version_Number>
.SAR are used automatically.
archive in Software
Provisioning Man­
ager
For more information, see Downloading and Extracting the Soft­
ware Provisioning Manager 1.0 Archive [page 102]
Support of Oracle
Oracle Database Vault 12c has been certified for SAP products
Database Vault
that are based on SAP NetWeaver technology.
Software Provisioning Manager
1.0 SP21 (SL Toolset 1.0 SP21)
You can now install a new SAP system with Oracle Database 12c
and configure Oracle Database Vault in its database.
For more information, see Implementing Oracle Database Vault
with the Installer [page 208].
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
About this Document
PUBLIC
17
Feature
Description
Availability
Support of Oracle
Software Provisioning Manager (the “installer”) now supports
12.2
SAP system installations with Oracle 12.2. For more information,
Software Provisioning Manager
1.0 SP21 (SL Toolset 1.0 SP21)
see Oracle 12 Database Software Installation [page 144].
SL Common GUI
with SAPINST 7.49
With the new installer framework version SAPINST 7.49, you can
now use the new SAPUI5-based graphical user interface (GUI)
“SL Common GUI”. For more information, see Useful Information
About the Installer [page 131], Running the Installer [page 125] .
Software Provisioning Manager
1.0 SP20 (SL Toolset 1.0 SP20)
Cleanup of Operat­
ing System Users
You can now specify during the Define Parameters phase that the
Software Provisioning Manager
1.0 SP20 (SL Toolset 1.0 SP20)
operating system users are to be removed from group sapinst
after the execution of the installer has completed.
For more information, see Operating System Users in SAP System
Parameters [page 56].
Option to install an
SAP Gateway in an
ASCS instance
You can now install an SAP Gateway in an ASCS instance. You can
choose this option while running the ASCS instance installation.
Software Provisioning Manager
1.0 SP20 (SL Toolset 1.0 SP20)
For more information, see ASCS Instance with Integrated Gate­
way [page 31]
Verification of Integ­ The integrity of data units extracted from the Software Provision­
rity of Data Units in
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 102] .
In addition, check SAP Note 1680045
Software Provisioning Manager
1.0 SP19 (SL Toolset 1.0 SP19)
whether additional infor­
mation is available.
Support of Linux on
IBM Power Systems
(little endian)
Software Provisioning Manager supports as of now Linux on IBM
Power Systems (little endian) as operating system platform for
SAP systems based on SAP NetWeaver 7.5 and higher. For more
information, see SAP Note 2378874
Software Provisioning Manager
1.0 SP19 (SL Toolset 1.0 SP19)
.
Software Provisioning Manager
1.0 SP19 (SL Toolset 1.0 SP19)
Archive-based Lan­
guage Installation
If you perform an installation using a stack configuration file, you
can now add language archives to the download basket and use
them for language installation. This feature is currently restricted
to the latest products only. For more information, see Additional
Parameters When Using a Stack Configuration File (Optional)
[page 69]
Oracle Multitenant
Installation
The multitenant option introduced in Oracle Database 12c allows Software Provisioning Manager
a single container database (CDB) to host multiple separate plug­ 1.0 SP18 (SL Toolset 1.0 SP18)
gable databases (PDB). In the Software Provisioning Manager you
can create a CDB, PDB, and also a new pluggable database in an
existing container database.
For more information, see Oracle Database 12c Multitenant Data­
base Installation [page 209].
18
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
About this Document
Feature
Description
Availability
Option to install an
SAP Web Dis­
patcher in an ASCS
instance
You can now install an SAP Web Dispatcher in an ASCS instance.
You can choose this option while running the ASCS instance in­
stallation.
Software Provisioning Manager
1.0 SP18 (SL Toolset 1.0 SP18)
For more information, see ASCS Instance with Integrated SAP
Web Dispatcher [page 29]
Archive-Based In­
stallation
You can now download the required installation archives instead
of the complete SAP kernel installation media. For more informa­
tion, see section Downloading Specific Installation Archives (Ar­
chive-Based Installation) in Preparing the Installation Media [page
100] .
Software Provisioning Manager
1.0 SP17 (SL Toolset 1.0 SP17)
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
, and to SAP Note 1858920
, to SAP Note 1833501
and the attached Diagnostics
Agent Setup Guide.
System Provisioning All system provisioning tasks (installation, system copy, system
Software Provisioning Manager
for SAP NetWeaver
1.0 SP09 (SL Toolset 1.0 SP15)
7.5 and SAP
NetWeaver 7.5based Products
rename) are available for the new SAP NetWeaver 7.5 release.
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.
●
After upgrading to SAP NetWeaver 7.5 PI, you first have to
split the still existing dual stack-system before you can use
SAP NetWeaver 7.5 PI productively.
For more information, see the Upgrade Master Guide - SAP
NetWeaver 7.5 at: http://help.sap.com/nw75
Installation and Upgrade
●
●
SAP NetWeaver 7.5 is Unicode only
The primary application server instance directory has been
renamed from /usr/sap/<SAPSID>/
DVEBMGS<Instance_Number> to /usr/sap/<SAPSID>/
D<Instance_Number>.
For more information, see SAP Directories [page 86].
●
Declustering and depooling of tables during the installation is
enabled by default. For more information, see SAP Note
1892354
.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
About this Document
PUBLIC
19
Feature
Description
Availability
System Provisioning All system provisioning tasks (installation, system copy, system
Software Provisioning Manager
for SAP Solution
1.0 SP09 (SL Toolset 1.0 SP15)
Manager 7.2
rename) are available for the new SAP Solution Manager 7.2 re­
lease. Compared to previous SAP Solution Manager releases, SAP
Solution Manager 7.2 is no longer provided as a classical dualstack system (ABAP system with Java Add-in), but consists of a
separate ABAP and Java stack.
Creating Kernel Ar­
You can reuse the binaries of a dedicated SAP system for a new
Software Provisioning Manager
chives from existing
SAP system installation or target system installation in the con­
1.0 SP09 (SL Toolset 1.0 SP14)
SAP System
text of a system copy by creating *.SAR archives based on the
*.lst files from the executable (exe) directories of the source
SAP system.
Note
This feature is only available for Unicode systems.
Caution
This feature has been deprecated with Software Provisioning
Manager 1.0 SP21 (SL Toolset 1.0 SP21) and the related option
has been removed from the Welcome screen. This deprecation
has been accomplished to ensure compliancy with the new
feature “Media Signature Check” of Software Provisioning
Manager 1.0 SP21 (SL Toolset 1.0 SP21) described above in
this table.
Support of Oracle 12 You can now perform all Software Provisioning Manager 1.0 tasks
Software Provisioning Manager
Database
1.0 SP08 (SL Toolset 1.0 SP13)
(installation, system copy, system rename, dual-stack split) for
SAP systems with the Oracle 12 database.
For more information, see http://support.sap.com/pam
Usage Type Library
.
Software Provisioning Manager 1.0 no longer uses the “Usage
Deprecation for SAP Types” definitions in its business logic for SAP systems based on
Systems Based on
SAP NetWeaver 7.3 EHP1 and higher. This is done to unify model­
SAP NetWeaver 7.3
ing and terminology across all SAP tools used during the plan­
EHP1 and Higher
ning, installation and maintenance activities. The “Product In­
Software Provisioning Manager
1.0 SP07 (SL Toolset 1.0 SP12)
stance” definition replaces “Usage Types” regarding product
modeling. For more information, see SAP Notes 1970349
1877731
20
PUBLIC
and
.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
About this Document
Feature
Description
Availability
Installation Using a
You can start the installer using a stack configuration file gener­
Software Provisioning Manager
Stack Configuration
ated by the Maintenance Planner. The configuration parameters
1.0 SP07 (SL Toolset 1.0 SP12)
File
in this file can then be used by the installer to improve the integra­
tion with SUM and to simplify the process of installation for a new
system on target software level.
For more information, see Installation Using a Stack Configuration File (Optional) [page 36].
Adaptive Installation You can assign virtual host names to SAP system instances dur­
ing the input phase of the installation directly on the screens
Software Provisioning Manager
1.0 SP07 (SL Toolset 1.0 SP12)
where you define the instance parameters.
Feedback Evaluation SAP SE’s aim is to provide fast and efficient procedures. To evalu­
Software Provisioning Manager
Form
1.0 SP07 (SL Toolset 1.0 SP12)
ate the procedure you just carried out, we need information gen­
erated by the tool during process execution and your experience
with the tool itself. A new evaluation form contains a simple ques­
tionnaire and XML data generated during the procedure.
Port 4239 is used for displaying the feedback evaluation form. For
more information, see Prerequisites for Running the Installer
[page 122].
Option Verify Signed The digital signature ensures that the signatory of a digital docu­
Software Provisioning Manager
Media
1.0 SP06 (SL Toolset 1.0 SP11)
ment can be identified unambiguously and signatory’s name is
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.1 to
7.5x on UNIX : Oracle
About this Document
.
PUBLIC
21
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 34].
Related Information
Standard System [page 22]
Distributed System [page 23]
High-Availability System [page 24]
Additional Application Server Instance [page 25]
Splitting off an ABAP Central Services Instance from an Existing Primary Application Server Instance [page
28]
ASCS Instance with Integrated SAP Web Dispatcher [page 29]
ASCS Instance with Integrated Gateway [page 31]
SAP Host Agent as a Separate Installation [page 32]
2.1
Standard System
You can install a standard system on a single host.
In a standard system, all main instances run on a single host.
There are the following instances:
● ABAP Central services instance (ASCS instance)
○ Optionally, you can install the ASCS instance with an integrated SAP Web Dispatcher. For more
information, see ASCS Instance with Integrated SAP Web Dispatcher [page 29].
○ Optionally, you can install the ASCS instance with an integrated gateway. For more information, see
ASCS Instance with Integrated Gateway [page 31].
● Database instance (DB)
● Primary application server instance (PAS instance)
22
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation Options Covered by this Guide
Figure 1: Standard ABAP System
2.2
Distributed System
You can install a system distributed over several hosts.
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)
○ Optionally, you can install the ASCS instance with an integrated SAP Web Dispatcher. For more
information, see ASCS Instance with Integrated SAP Web Dispatcher [page 29].
○ Optionally, you can install the ASCS instance with an integrated gateway. For more information, see
ASCS Instance with Integrated Gateway [page 31].
● 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 25].
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation Options Covered by this Guide
PUBLIC
23
Figure 2: 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)
○ Optionally you can install the ASCS instance with an integrated SAP Web Dispatcher. For more
information, see ASCS Instance with Integrated SAP Web Dispatcher [page 29].
○ Optionally you can install the ASCS instance with an integrated gateway. For more information, see
ASCS Instance with Integrated Gateway [page 31].
● Enqueue replication server instance (ERS instance) for the ASCS instance (mandatory)
● Database instance (DB)
● Primary application server instance (PAS)
The graphics below assume that you run the ASCS 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.
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.
We recommend that you run the ASCS instance in a switchover cluster infrastructure. The ASCS instance must
have its own ERS instance.
24
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation Options Covered by this Guide
To increase high availability by creating redundancy, we recommend that you install additional application
server instances on hosts different from the primary application server instance host. For more information,
see Installation of an Additional Application Server Instance [page 25].
The following figures show examples for the distribution of the SAP instances in a high-availability system.
Figure 3: 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 203]. 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.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation Options Covered by this Guide
PUBLIC
25
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
● On dedicated hosts
Figure 4: Additional Application Server Instance for a Standard ABAP System
For more information, see Standard System [page 22].
Additional Application Server Instance for a Distributed System
The following figure shows a distributed system with additional application server instances that run:
● On the main host of the SAP system, that is, on the host on which the primary application server instance
runs
● On dedicated hosts
We do not recommend installing additional application server instances on the SAP global host.
26
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation Options Covered by this Guide
Figure 5: Additional Application Server Instance for a Distributed ABAP System
For more information, see Distributed System [page 23].
Additional Application Server Instance for a High-Availability System
The following figure shows a high-availability system with additional application server instances that run:
● On the host of the primary application server instance
● On dedicated hosts
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation Options Covered by this Guide
PUBLIC
27
Figure 6: Additional Application Server Instance for a High-Availability System
For more information, see High-Availability System [page 24].
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 enqueue and message system
services only. With a separate ASCS instance, it is easier for you to later turn your SAP system into a highavailability 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 215] 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).
28
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation Options Covered by this Guide
2.6
ASCS Instance with Integrated SAP Web Dispatcher
You can install an SAP Web Dispatcher integrated in the ASCS instance.
If you select this option, an SAP Web Dispatcher is installed running within the ASCS instance. No separate SAP
Web Dispatcher instance and no dedicated <SAPSID> are created for the SAP Web Dispatcher. We recommend
this if you want to use the SAP Web Dispatcher for the system to which the ASCS instance belongs.
Note
We only recommend this option for special scenarios. For more information, see SAP Note 908097 . For
an SAP Web Dispatcher installation, a standalone installation (see below) continues to be the default
scenario.
Figure 7: ASCS Instance with Integrated SAP Web Dispatcher
The SAP Web Dispatcher is located between the Web client (browser) and your SAP system that is running the
Web application.
It acts as single point of entry for incoming requests (HTTP, HTTPS), defined by the IP address, port, and URL,
and forwards them in turn to the application server (AS) of the SAP system.
The SAP Web Dispatcher receives information about the SAP system that it needs for load distribution (load
balancing) from the message server and application server via HTTP.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation Options Covered by this Guide
PUBLIC
29
Installation of “Standalone” SAP Web Dispatcher with its own <SAPSID> and
Instance
If you want to install an SAP Web Dispatcher for another system - that is not for the system for which you use
the ASCS instance and with its own SAP system ID and instance number - you have to install SAP Web
Dispatcher separately as described in the documentation which you can find under http://support.sap.com/
sltoolset
System Provisioning
Installation Option of Software Provisioning Manager
Guide for SAP
Web Dispatcher for SAP NetWeaver 7.0 or Higher .
More Information
For more information about the architecture and the functions of SAP Web Dispatcher, see the SAP Web
Dispatcher documentation in the SAP LibrarySAP Library at:
Table 6:
SAP Release and SAP Library Quicklink
●
SAP Library Path (Continued)
SAP NetWeaver Mobile 7.1
Application Help
http://help.sap.com/nwmobile71
●
Server Infrastructure
SAP NetWeaver Mobile 7.1 including Enhancement
Application Server
Package 1
Function-Oriented View
Application
Components of SAP NetWeaver
SAP Web Dispatcher
http://help.sap.com/nwmobile711
●
SAP NetWeaver 7.1 for Banking Services from SAP
See the SAP NetWeaver Mobile Library.
5.0 and 6.0
●
SAP NetWeaver 7.1 including Enhancement Package
1 for Banking Services from SAP 5.0 and 6.0
●
Since the SAP NetWeaver Mobile 7.1 Library is the only avail­
able SAP Library for ABAP systems based on SAP
NetWeaver 7.1, in this guide we always refer to it also for SAP
NetWeaver 7.1 for Banking Services from SAP 5.0 and 6.0.
SAP NetWeaver Process Integration 7.1
Application Help
http://help.sap.com/nwpi71
●
Note
SAP NetWeaver Process Integration 7.1 Including En­
Server Infrastructure
Function-Oriented View
Application
SAP Web Dispatcher
hancement Package 1
http://help.sap.com/nwpi711
30
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation Options Covered by this Guide
SAP Release and SAP Library Quicklink
●
SAP NetWeaver 7.3
http://help.sap.com/nw73
●
SAP NetWeaver 7.3 including Enhancement Package
1
SAP Library Path (Continued)
Application Help
Function-Oriented View
Server Infrastructure
Application Server
Application
Components of SAP NetWeaver
SAP Web Dispatcher
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
Related Information
Parameters for Additional Components to be Included in the ASCS Instance (Optional) [page 71]
2.7
ASCS Instance with Integrated Gateway
You can install a gateway integrated in the ASCS instance.
If you select this option, a gateway is installed within the ASCS instance.
Note
No separate standalone gateway instance and no dedicated <SAPSID> are created for the gateway.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation Options Covered by this Guide
PUBLIC
31
Figure 8: Gateway Integrated in the ASCS Instance
The gateway enables communication between work processes and external programs, as well as
communication between work processes from different instances or SAP systems.
You can also install a standalone gateway instance. For more information, see the documentation Installation
Guide – Installation of a Standalone Gateway Instance for SAP Systems Based on SAP NetWeaver <Release> at
http://support.sap.com/sltoolset
System Provisioning
Installation Option .
Related Information
Parameters for Additional Components to be Included in the ASCS Instance (Optional) [page 71]
2.8
SAP Host Agent as a Separate Installation
Under certain circumstances you need to install SAP Host Agent separately.
SAP Host Agent is an agent that can accomplish several life-cycle management tasks, such as operating
system monitoring, database monitoring, system instance control and provisioning. When you install a new
SAP system or instance, the SAP Host Agent is in most cases installed automatically on the SAP system or
instance host.
32
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation Options Covered by this Guide
It is only required to install the SAP Host Agent separately if one of the following is true:
● There is no SAP system or instance on the host.
● The SAP system or instance running on the host has a kernel release lower than SAP kernel 7.20 and the
host does not yet have an SAP Host Agent. During the installation of new SAP instances with SAP kernel
7.20 or higher, the SAP Host Agent is installed automatically (integrated installation).
● You have upgraded your SAP system to a release with a kernel release lower than SAP kernel 7.20 and the
host of the upgraded system or instance does not yet have an SAP Host Agent.
The section Installing the SAP Host Agent Separately [page 212] describes how to perform the installation.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation Options Covered by this Guide
PUBLIC
33
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 12] .
2. You have decided on your installation option (see Installation Options Covered by this Guide [page 22]).
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. Make yourself familiar with the changed file system structure and profiles for SAP systems based on SAP
NetWeaver 7.1 and higher compared to SAP systems based on lower SAP NetWeaver releases. For more
information, see Changed File System Structure and Profiles for SAP Systems Based on SAP NetWeaver
7.1 and Higher [page 35].
2. If you want to install an SAP ABAP system along with the required Support Package stack and ABAP AddOns in one implementation run, you need to plan the desired installation target using the maintenance
planner at https://apps.support.sap.com/sap/support/mp .
In the maintenance planner, a stack XML file with the desired Support Package stack and Add-On
information is generated, which you then hand over to Software Provisioning Manager (the “installer” for
short) by calling it with command line parameter
SAPINST_STACK_XML=<Absolute_Path_To_Stack_XML_File>. Included constraints and defaults
defined in the stack XML file are then used for the initial installation by Software Provisioning Manager and
for the application of Support Package stacks and Add-Ons by the Software Update Manager (SUM).
For more information, see Installation Using a Stack Configuration File (Optional) [page 36].
34
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
Recommendation
We recommend that you perform the installation using a stack configuration file for all new products
such as SAP S/4HANASAP on Premise.
3. You check the hardware and software requirements [page 38] on every installation host.
4. You plan how to set up user and access management [page 53].
5. You identify Basic SAP System Installation Parameters [page 55].
6. For the database installation, we recommend that you check the information available in the SAP on Oracle
Knowledge Center at https://www.sap.com/community/topic/oracle.html .
7. For the database installation, you decide on how to distribute your database components to disk [page
72].
8. If your database release is Oracle 12c and you want to install it as a pluggable database in a container
database (multitenant database installation), consider the additional steps described in Oracle Database
12c Multitenant Database Installation [page 209].
9. You decide on the transport host to use [page 74].
10. You decide whether you want to integrate LDAP Directory Services in your SAP system [page 190].
11. To install a high-availability system, you read Planning the Switchover Cluster for High Availability [page
76].
12. Optionally, you decide whether you want to install multiple components in one database (MCOD) [page
195].
13. If you want to implement Oracle Database Vault, make sure that you have read section Implementing
Oracle Database Vault with the Installer [page 208].
14. Continue with Preparation [page 79].
Additional Application Server Instance
1. You check the hardware and software requirements [page 38] 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 55].
3. Continue with Preparation [page 79].
3.2
Changed File System Structure and Profiles for SAP
Systems Based on SAP NetWeaver 7.1 and Higher
File system structure
● For SAP system releases based on SAP NetWeaver 7.1 and higher, the directory structure was changed
compared to SAP NetWeaver 7.0, in order to support heterogeneous system installations and updates
more efficiently.
For more information about how to configure upgraded SAP systems for the new directory structure, see
SAP Note 1104735 .
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
PUBLIC
35
Caution
The directory structure of systems based on SAP NetWeaver 7.1 or higher is not supported on systems
based on SAP NetWeaver 7.0 including Enhancement Packages.
● For a manual switch, see the details about targeted file system structure in this documentation and adjust
your file system accordingly to avoid later issues for system transformation such as system copy and
system rename.
Profiles
● As of SAP NetWeaver 7.3, the start profile as separate file has been removed. In earlier versions of SAP
NetWeaver there was one default profile per SAP system, one start profile per Instance and one Instance
profile per instance. Now the start profile contents are merged with the instance profile. With the help of
the new instance profile, SAP processes are started and at the same time instance-specific parameters are
read. This reduces the total number of profile files to one default profile per SAP System, and one instance
profile per instance.
For more information, see the SCN blog What's new in SAP NetWeaver 7.3 - A Basis perspective at: https://
blogs.sap.com/2012/05/22/whats-new-in-sap-netweaver-73-a-basis-perspective/ .
Caution
The merged profiles are not supported for SAP NetWeaver 7.0 including Enhancement Packages
because this could lead to issues for SAP system copy. If you are not sure which SAP NetWeaver
product version you have, see SAP Note 1877731
for more information.
● Concatenate instance profile and start profile entries and remove the start profile from the profile
directory. For more information, see SAP Note 1898687 .
● Adjust the /usr/sap/sapservices profile file by replacing the start profile with the instance profiles for
starting the sapstartsrv process, and then restart the SAP start service.
● Additional application server instances: Double-check the values with the profile values from the primary
application server - for example for parameters DIR_CT_RUN , DIR_EXECUTABLE, DIR_SAPJVM - to avoid
startup issues.
3.3
Installation Using a Stack Configuration File
The option to perform an installation using a stack configuration file (also called “up-to-date installation”)
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:
● Maintenance Planner, accessible at https://apps.support.sap.com/sap/support/mp
● LMDB in SAP Solution Manager
● Software Provisioning Manager (the “installer” for short)
● Software Update Manager (“SUM”)
The installer then can take over more default settings that are already predefined in the Maintenance Planner.
36
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
Recommendation
We recommend to perform the installation using a stack configuration file for new products, such as SAP S/
4HANA or SAP Solution Manager 7.2.
Prerequisites
● To be able to use the Maintenance Planner at https://apps.support.sap.com/sap/support/mp , your SAP
Solution Manager system must have at least one of the following release and Support Package (SP) level:
○ SAP Solution Manager 7.2
○ SAP Solution Manager 7.1 SP06 or higher
○ SAP Solution Manager 7.0 SP 23 and you must have applied the following SAP Notes: 1646604
1783371 , 1743695
● You must have implemented SAP Note 1940845
,
in your SAP Solution Manager system.
● For additional information about involved tools and supported SAP system releases, see SAP Note 2277574
for additional information about involved tools and supported SAP system releases.
Features
An installation using a stack configuration file provides the following features:
● You can use a stack configuration file generated by the Maintenance Planner at https://
apps.support.sap.com/sap/support/mp . The parameters contained in the stack configuration file can
then be processed by the installer to get better integrated with SUM and to simplify the process of
installation for a new system on a target software level. This makes IT administration easier by reducing the
efforts in Total Cost of Ownership (TCO). For more information, see the Best Practice Guide to Planning
Landscape Changes at https://wiki.scn.sap.com/wiki/display/SL/Landscape+Management+-+the
+Process .
● When processing a stack configuration file, the installer can take over more default settings that are
already predefined in the Maintenance Planner and offers more possibilities for automation as compared
to when running without it. For more information about the benefits by comparing the existing process with
the new improved process, see Up-To-Date Installation at https://blogs.sap.com/2016/10/21/up-to-dateinstallation-2/ .
Integration
For the additional input parameters that you need to specify, see Additional Parameters When Using a Stack
Configuration File (Optional). You can find the link to this section in Related Information below.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
PUBLIC
37
In addition, each section in this guide describing steps that are completely or at least partially automatized
when using a stack configuration files is marked with an appropriate note at the beginning. These are the
following sections as listed in the adjacent section Related Information:
Related Information
Additional Parameters When Using a Stack Configuration File (Optional) [page 69]
Preparing the Installation Media [page 100]
Running the Installer [page 125]
Configuring the Change and Transport System [page 160]
Applying the Latest Kernel and Support Package Stacks [page 164]
Installing Additional Languages and Performing Language Transport [page 169]
3.4
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.
Procedure
1. Check the Product Availability Matrix at http://support.sap.com/pam
releases.
for supported operating system
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 39].
○ Integrated in the installation tool (mandatory) as part of the installation process
For more information, see Running the Installer [page 125].
○ The hardware and software requirements tables in Requirements for the SAP System Hosts [page
40].
38
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
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.4.1 Running the Prerequisites Check in Standalone Mode
(Optional)
This section describes how to run the prerequisites check in standalone mode. Running the prerequisites
check in standalone mode is optional.
Context
When you install an SAP system, the installer automatically starts the prerequisites check and checks the
hardware and software requirements in the background. As an optional step during planning, you can also run
the prerequisites check in standalone mode to check the hardware and software requirements for your
operating system and the SAP instances before the actual installation.
Recommendation
We recommend that you use both the prerequisites check and the requirements tables for reference.
Procedure
1. Download and unpack the Software Provisioning Manager archive to a local directory as described in
Downloading and Extracting the Software Provisioning Manager 1.0 Archive [page 102] .
2. Make either the separate SAPEXE<Version>.SAR archive or the complete kernel medium available as
described in Preparing the Installation Media [page 100] .
3. Start the installer as described in Running the Installer [page 125].
4. On the Welcome screen, choose
<SAP_Product>
<Database>
Preparations
Prerequisites
Check .
5. Follow the instructions in the installer dialogs and enter the required parameters.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
PUBLIC
39
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 102]
Preparing the Installation Media [page 100]
3.4.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.
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 41]
Hardware Requirements [page 42]
Software Requirements [page 48]
Other Requirements [page 52]
40
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
3.4.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.
Table 7: General Installation Information for Your Operating System
Operating System
Information
AIX
Before you start the installation, make sure that you have read SAP Note 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
Before you start the installation, make sure that you have read SAP Note 1075118
.
.
In addition, we also recommend that you check the information available in the SAP on HP-UX Best
Practices space on the SAP Community Network at https://www.sap.com/community/topic/hpux.html
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
.
.
In addition, we also recommend that you check the information available in the SAP on Oracle Solaris
space on the SAP Community Network at https://www.sap.com/community/topic/oracle-so­
laris.html
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
PUBLIC
41
3.4.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.
Table 8: Hardware Requirements
Requirement
Values and Activities
Distribution of the Oracle
We recommend using a redundant storage solution such as RAID5 for data security reasons.
database
To calculate how much storage is required for your Oracle database, see section Database
System Configuration in the SAP Library at:
●
SAP NetWeaver Mobile 7.1 and SAP NetWeaver for Banking Services from SAP 5.0:
http://help.sap.com/nwmobile71
Databases
●
Configuration Guide
Configuration of
Database Configuration for Oracle
SAP NetWeaver Mobile 7.1 EHP1 and SAP NetWeaver for Banking Services from SAP 5.0
and 6.0:
http://help.sap.com/nwmobile711
Databases
●
Configuration Guide
Configuration of
Database Configuration for Oracle
SAP NetWeaver 7.3:
http://help.sap.com/nw73
Database Administration
Application Help
Function-Oriented View
Database Administration for Oracle
SAP Database Guide:
Oracle
●
SAP NetWeaver 7.3 EHP1:
http://help.sap.com/nw731
Database Administration
Application Help
Function-Oriented View
Database Administration for Oracle
SAP Database Guide:
Oracle
●
SAP NetWeaver 7.4:
http://help.sap.com/nw74
Database Administration
Oracle
●
Application Help
Database Administration for Oracle
Getting Started with Oracle and the SAP System
Database Administration
Oracle
Application Help
SAP Database Guide:
Getting Started with Oracle and the SAP System
SAP NetWeaver Application Server for ABAP 7.51 innovation package:
Database Administration
Oracle
PUBLIC
Function-Oriented View
Database Administration for Oracle
https://help.sap.com/nw751abap
42
SAP Database Guide:
SAP NetWeaver 7.5:
http://help.sap.com/nw75
●
Function-Oriented View
Application Help
Function-Oriented View
Database Administration for Oracle
SAP Database Guide:
Getting Started with Oracle and the SAP System
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
Requirement
Values and Activities
●
SAP NetWeaver AS for ABAP 7.52:
https://help.sap.com/nw752abap
Database Administration
Oracle
Application Help
Function-Oriented View
Database Administration for Oracle
SAP Database Guide:
Getting Started with Oracle and the SAP System
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 sup­
port 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.1 to
7.5x on UNIX : Oracle
Planning
PUBLIC
43
Requirement
Hard disk space
Values and Activities
●
General Requirements:
○
2 GB of temporary disk space for each required physical installation media - or al­
ternatively the downloaded SAP kernel archives - that you have to copy to a local
hard disk. For more information, see Preparing the Installation Media [page 100].
○
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 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 107] .
○
2 GB of temporary disk space for the installation.
○
If an advanced disk array is available (for example, RAID), contact your hardware
vendor to make sure that the data security requirements are covered by this tech­
nology.
●
Instance-Specific Requirements:
If you install several instances on one host, you have to add up the requirements ac­
cordingly.
For more information about space requirements for the file systems and directories of
the instances, see SAP Directories [page 86] and the appropriate database-specific in­
formation listed below.
○
ABAP central services instance (ASCS):
Minimum 2 GB
○
If you install the ASCS instance with an integrated SAP Web Dispatcher, for the
installation as such you require at least 1 GB of hard disk space in addition. For
production use of the SAP Web Dispatcher, you need to reserve at least 5 GB.
○
If you install the ASCS instance with an integrated SAP Gateway, you require at
least 1 GB of hard disk space in addition.
○
Enqueue replication server instance for the ASCS (if required):
○
Database Instance:
Minimum 2 GB
○
SAP ERP: Minimum 75 GB
○
SAP CRM: Minimum 50 GB
○
SAP SRM: Minimum 55 GB
○
SAP SCM: Minimum 50 GB
○
SAP NetWeaver: Minimum 40 GB
For more information about space requirements for the separate file systems and
directories, see Oracle Directories [page 92].
Oracle Database 12c Multitenant Database Installation [page 209]:
○
44
PUBLIC
For a container database (CDB), you need additional disk space for the follow­
ing tablespaces:
○
SYSTEM DEFAULT: 2x* 350 MB
○
PSAPTEMP DEFAULT: 2x* 350 MB
○
SYSAUX DEFAULT: 2x* 200MB
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
Requirement
Values and Activities
Note
* These tablespaces are created two times in the CDB, because all further
pluggable databases (PDB) are created out of them.
○
○
For each further PDB, you need the same disk space as for a normal single da­
tabase instance installation.
Primary application server instance:
Minimum 2 GB (SAP NetWeaver BW server: Minimum 30 GB)
○
Additional application server instance:
Minimum 2 GB (SAP NetWeaver BW server: Minimum 30 GB)
○
SAP Host Agent:
Minimum 0.5 GB
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
PUBLIC
45
Requirement
Values and Activities
RAM
Only valid for 'Platform': AIX
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 1 GB
If you install the ASCS instance with an integrated SAP Web Dispatcher, see SAP Note
2007212
●
for memory consumption in productive use.
Enqueue replication server instance for the ASCS instance (if required)
Minimum 1 GB
●
Database Instance:
Minimum 2 GB
Note
The default value used by the installer is 50 percent of the entire RAM.
●
Primary application server instance:
Minimum 3 GB (BW server: Minimum 2 GB)
●
Additional application server instance:
Minimum 3 GB
●
SAP Host Agent:
Minimum 1 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: Refer to SAP Note 1382721
for the commands to display the RAM size on Linux.
End of 'Platform': Linux
46
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
Requirement
AIX: Paging space
Values and Activities
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 an­
other 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
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.
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
Verifying paging space size
and kernel settings using
memlimits
.
To verify paging space size and kernel settings, you can execute memlimits as follows:
1.
Make sure that the SAPCAR program is available on the installation host. If SAPCAR is not
available, you can download it from https://launchpad.support.sap.com/#/software­
center
.
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 107]
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.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
PUBLIC
47
3.4.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.
Table 9: 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 6.1 TL7 SP10 to be able to run the installer.
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
Linux: Operating system version
for information about support time frames of HP-UX.
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 Oracle 12c with the operating system SUSE Linux Enterprise
Server (SLES) 12, see SAP Note 1984787
.
End of 'Platform': Linux
48
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
Requirement
Values and Activities
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 kernel versions
and how this relates to SAP NetWeaver support packages, including important notes
on downward compatibility and release dates, see the document Understanding Ker­
nel Releases for the SAP NetWeaver AS ABAP at https://archive.sap.com/docu­
ments/docs/DOC-54170
.
To use regular Software Provisioning Manager (SWPM10<Version>.SAR) with SAP
kernel 7.49 or higher on RHEL 6 or SLES 11 or Oracle Linux 6, you must install the
required libstdc++ RPM packages. For more information, see SAP Note 2195019
.
AIX: Kernel parameters
HP-UX: Kernel parameters
To adjust AIX Virtual Memory Management settings, see SAP Note 973227
.
To run an SAP system, make sure that you check and, if necessary, modify the HPUX kernel.
Caution
We recommend that a UNIX system administrator performs all kernel modifications.
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).
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
PUBLIC
49
Requirement
Values and Activities
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 fol­
lowing SAP Notes:
Oracle Solaris: Kernel parameters
●
Oracle Linux: SAP Note 1565179
●
RHEL4: SAP Note 722273
●
RHEL5: SAP Note 1048303
●
RHEL6: SAP Note 1496410
●
RHEL7: SAP Note 2002167
●
SLES9: SAP Note 797084
●
SLES10: SAP Note 958253
●
SLES 11: SAP Note 1310037
●
SLES 12: SAP Note 1984787
To run an SAP system, you must check and, if necessary, modify the Oracle Solaris
kernel parameters or resource controls.
●
Oracle Solaris 9: SAP Note 395438
●
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
Oracle Solaris: OS patches
Check the relevant SAP Note for required Oracle Solaris patches:
●
Sun Solaris 9 on SPARC: SAP Note 550585
●
Sun 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.
50
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
Requirement
Values and Activities
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.
HP-UX: Language libraries
To make sure that the file set LANG-MIN is installed, enter the following command:
swlist -v | grep -i lang-min
If nothing is displayed, the file set is not available, and needs to be installed.
SAP Kernel 7.40 and Higher:
IP Multicast Configuration
Make sure that you have applied the operating system patches required for IP Multi­
cast Configuration. For more information, see SAP Note 1931675
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
.
PUBLIC
51
3.4.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.
Table 10: Other Requirements
Requirement
Values and Activities
Minimum Web Browser
Make sure that you have at least one of the following web browsers installed on the host
where you run the installer GUI:
●
Microsoft Internet Explorer 11 or higher
●
Microsoft Edge
●
Mozilla Firefox
●
Google Chrome
Always use the latest version of these web browsers.
You need a web browser to be able to run the SL Common GUI, and to display the Evalua­
tion Form and send it to SAP.
AIX: Additional software
Host name
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
●
bos.perf.libperfstat – Performance Statistics Library
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
52
PUBLIC
.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
Requirement
Login shell
Values and Activities
The installer only prompts you for this parameter if you use a login shell other than the
recommended 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 instal­
tralized systems
led, 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
Linux: C compiler
3.5
.
Make sure that the C compiler gcc is installed.
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 122].
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
PUBLIC
53
More Information
For more information about configuring the user management of your SAP system to be installed, see the SAP
Library at:
Table 11:
SAP Release and SAP Library Quicklink
●
SAP Library Path (Continued)
SAP NetWeaver Mobile 7.1
Application Help
http://help.sap.com/nwmobile71
●
Oriented View
SAP NetWeaver Mobile 7.1 including Enhancement
SAP NetWeaver Library: Function-
Security
Identity Management
Identity
Management of the Application Server ABAP
Package 1
http://help.sap.com/nwmobile711
●
SAP NetWeaver 7.1 for Banking Services from SAP
See the SAP NetWeaver Mobile Library.
5.0 and 6.0
●
SAP NetWeaver 7.1 including Enhancement Package
1 for Banking Services from SAP 5.0 and 6.0
Note
Since the SAP NetWeaver Mobile 7.1 Library is the only avail­
able SAP Library for ABAP systems based on SAP
NetWeaver 7.1, in this guide we always refer to it also for SAP
NetWeaver 7.1 for Banking Services from SAP 5.0 and 6.0.
●
SAP NetWeaver Process Integration 7.1
Application Help
http://help.sap.com/nwpi71
●
SAP NetWeaver Process Integration 7.1 Including En­
hancement Package 1
Oriented View
SAP NetWeaver Library: Function-
Security
Identity Management
Identity
Management of the Application Server ABAP
http://help.sap.com/nwpi711
●
SAP NetWeaver 7.3
Application Help
http://help.sap.com/nw73
●
SAP NetWeaver 7.3 including Enhancement Package
1
●
Oriented View
SAP NetWeaver Library: Function-
Security
Identity Management
User and
Role Administration of Application Server ABAP
http://help.sap.com/nw731
Configuration of User and Role Administration
SAP NetWeaver 7.4
Services
Directory
LDAP Connector
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
54
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
3.6
Basic Installation Parameters
The installer prompts for input parameters during the Define Parameters phase of the installation.
You can install your SAP system either in Typical or Custom mode:
● Typical
If you choose Typical, the installation is performed with default settings. This means that the installer
prompts you only for a small selection of installation parameters. These parameters include at least the
following:
○ SAP system ID and database connectivity parameters
○ Master password
○ SAP system profile directory – only for systems with instances on separate hosts
○ SAP systems based on SAP NetWeaver 7.40 and higher: Individual encryption key for the secure
storage
For more information about the installation parameters, see the corresponding tables below in this
document. If you want to change any of the default settings, you can do so on the Parameter Summary
screen.
● Custom
If you choose Custom, you are prompted for all parameters. At the end, you can still change any of these
parameters on the Parameter Summary screen.
Note
You cannot change from Custom to Typical mode or from Typical to Custom mode on the Parameter
Summary screen.
Note
● If you want to install an ASCS instance with an integrated SAP Web Dispatcher [page 29], you must
choose Custom. Otherwise, you are not prompted for the SAP Web Dispatcher installation parameters
[page 71] during the Define Parameters phase of the ASCS instance installation.
● If you want to install an ASCS instance with an integrated Gateway [page 31], you must choose Custom.
Otherwise, you are not prompted for the SAP Gateway installation during the Define Parameters phase
of the ASCS instance installation.
The tables in the sections below list the basic SAP system installation parameters that you need to specify
before installing your SAP system. For all other installation parameters, use the tool help on the installer
screens.
Related Information
SAP System Parameters [page 56]
SAP System Database Parameters [page 66]
Additional Parameters when Installing SAP Process Integration 7.5 or SAP Solution Manager 7.2 [page 68]
Additional Parameters When Using a Stack Configuration File (Optional) [page 69]
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
PUBLIC
55
Parameters for Additional Components to be Included in the ASCS Instance (Optional) [page 71]
3.6.1 SAP System Parameters
The tables in this section lists the basic SAP system installation parameters that you need to specify before
installing your SAP system. For all other installation parameters, use the tool help on the installer screens.
Table 12: General Parameters
Parameter
Description
Unicode System
Every new installation of an SAP system is Unicode.
SAP systems based on SAP NetWeaver 7.1 to 7.4:
You can only deselect this option if you perform the target system installation in the context of a system
copy for a non-Unicode SAP system that has been upgraded to the current release.
SAP systems based on SAP NetWeaver 7.5 or higher are Unicode only.
If you install an additional application server instance in an existing non-Unicode system (that has been
upgraded to the current release), the additional application server instance is installed automatically as
a non-Unicode instance. The installer checks whether a non-Unicode system exists and chooses the
right executables for the system type.
56
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
Parameter
Description
SAP System ID
The SAP system ID <SAPSID> identifies the entire SAP system.
<SAPSID>
The installer prompts you for the <SAPSID> when you execute the first installation option to install a
new SAP system.
If there are further installation options to be executed, the installer prompts you for the profile direc­
tory. For more information, see the description of the parameter SAP System Profile Directory.
Example
This prompt appears when you install the ASCS instance, which is the first instance to be installed in
a distributed system.
Caution
Choose your SAP system ID carefully since renaming requires considerable effort.
Make sure that your SAP system ID:
●
Is unique throughout your organization. Do not use an existing <SAPSID> when installing a new
●
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
SAP system.
.
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.1 to
7.5x on UNIX : Oracle
Planning
PUBLIC
57
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 86].
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 num­
ber. The installer 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 re­
port 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 Run­
ning the Installer [page 125].
End of 'Platform': HP-UX
58
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
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 provide a virtual host name in the <Instance_Name> Virtual Host field on the installer
screen of the relevant instance. Then this instance is installed with the given virtual host name.
●
Alternatively you can assign virtual host names also by starting the installer with the
SAPINST_USE_HOSTNAME property. For more information, see Running the Installer [page 125].
After the installation has completed, all application servers can use this virtual host name to connect to
the instance. The virtual host name is also a global host name. If you do not provide the virtual host
name, the instance is installed automatically using its physical host name.
You must have already reserved the virtual host name (network name) and its IP address on a DNS
server before you run the installer. For more information, see Using Virtual Host Names [page 99].
Note
Fully qualified host names, IPv4, IPv6 are not accepted as virtual host names.
SAP Process
If you want to install the primary application server instance of the Java system on a host different from
Integration (PI)
the host of the primary application server instance of the ABAP system, then you must specify the host
7.5, SAP Solu­
of the Java primary application server instance during the Define Parameters phase of the primary appli­
tion Manager
cation server instance installation of the ABAP system.
7.2:
This is to set up the connection between the ABAP and the Java system.
Application
Server Gateway
Communication
Setup
SAP System Pro­ /<sapmnt>/<SAPSID>/profile or /usr/sap/<SAPSID>/SYS/profile
file Directory
The installer retrieves parameters from the SAP system profile directory of an existing SAP system.
SAP profiles are operating system files that contain instance configuration information.
The installer prompts you to enter the location of the profile directory when the installation option
that you execute is not the first one belonging to your SAP system installation, for example if you are
installing a distributed system or an additional application server instance to an existing SAP system.
See also the description of the parameters SAP System ID and Database ID.
/usr/sap/<SAPSID>/SYS/profile is the soft link referring to /<sapmnt>/<SAPSID>/profile.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
PUBLIC
59
Parameter
Description
Master Pass­
Common password for all users that are created during the installation:
word
●
Operating system users (for example <sapsid>adm)
Caution
If you did not create the operating system users manually before the installation, the installer
creates them with the common master password (see Operating System Users). In this case,
make sure that the master password meets the requirements of your operating system.
●
ABAP users: SAP*, DDIC, and EARLYWATCH.
●
Secure Store key phrase
SAP systems based on SAP NetWeaver 7.4 and Higher: For more information, see line Key Phrase
for Secure Store Settings and line Individual Encryption Key for the Secure Storage in this table.
Basic Password policy
The master password must meet the following requirements:
●
It must be 8 to 14 characters long
●
It must contain at least one letter (a-z, A-Z)
●
It must contain at least one digit (0-9)
●
It must not contain \ (backslash) or " (double quote).
Additional restrictions depending on the Oracle database:
●
It must not begin with a digit or an underscore
●
It can contain the following characters: _, #, $, ., a-z, A-Z, 0-9
Depending on the installation option, additional restrictions may apply.
Message Server
Access Control
List
You can specify if you want to have a message server Access Control List (ACL) created.
The ACL is created as a file in the /<sapmnt>/<SAPSID>/global directory. If it exists, it defines the
hosts from which the message server accepts requests.
Caution
Only trigger the creation of this file if you do not plan to install any additional instances for this sys­
tem. With the creation of this ACL, you overwrite existing settings and prevent instances from being
installed on additional hosts. If you decide to install an additional instance later, you need to remove
this file manually before the installation and create it again after the installation of the additional in­
stance.
For more information, see the information about ms/acl_info in SAP Notes 1495075
and 826779
.
60
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
Parameter
Description
SAP systems
You can set a randomly generated individual encryption key for the secure storage in the file system and
based on SAP
the secure storage in the database. If you skip this step, the system is installed with a default key which
NetWeaver 7.4
provides obfuscation only, but it can be changed later.
and Higher only:
●
For more information on the secure storage in the file system, see the SAP Library - depending on
Individual En­
the SAP NetWeaver release your SAP system is based on - at:
cryption Key for
http://help.sap.com/nw74
the Secure Stor­
http://help.sap.com/nw75
age
https://help.sap.com/nw751abap
https://help.sap.com/nw752abap
Application Help
Function-Oriented View: English
Security for SAP NetWeaver AS ABAP Only
●
Security
System Security
System
Secure Storage in the File System (AS ABAP)
For more information on the secure storage in the database, see the SAP Library - depending on the
SAP NetWeaver release your SAP system is based on - at:
http://help.sap.com/nw74
http://help.sap.com/nw75
https://help.sap.com/nw751abap
https://help.sap.com/nw752abap
Application Help
Function-Oriented View: English
Security for SAP NetWeaver AS ABAP Only
Individual Encryption Keys
Security
System Security
Secure Storage (ABAP)
System
Key Management
Using
Generating Encryption Keys
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 configured in profile parameter SAPLOCALHOSTFULL. FQDN is the fully qualified domain name for an IP ad­
dress. It consists of the host name and the domain name:
<Host_Name>.<Domain_Name>
The DNS Domain Name is needed to define the URLs for the ABAP application servers. It is appended to
the server name to calculate the FQDN.
Example
If your application server host is called kirk.wdf.sap.com, the DNS Domain Name is
wdf.sap.com.
SAP Host Agent
If there already exists an SAP Host Agent on the installation host, the installer asks you if you want to
Upgrade (Op­
upgrade it to a newer patch level version. If you want the existing version to be upgraded, you must pro­
tional)
vide the new target version of the SAPHOSTAGENT<Version>.SAR archive.
For more information, see Downloading SAP Kernel Archives (Archive-Based Installation) [page 107]
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
PUBLIC
61
Table 13: Ports
Parameter
ABAP Message Server Port
Description
Caution
The message server port number must be unique on the host where the message server
for the SAP system is running. If there are several message servers running on one host,
the message server ports must all be unique.
If you do not specify a value, the default port number is used.
ABAP Message Server Port
There is an external messagev server port and an internal message server port.
The ABAP message server uses both the internal and the external message server ports.
The default profile contains the configuration for both message server ports.
The external message server port uses the parameter rdisp/msserv with default value
36<ABAP_Message_Server_Instance_Number>.
The internal message server port uses the parameter rdisp/msserv_internal with de­
fault value 39<ABAP_Message_Server_Instance_Number>.
During the installation of an SAP system from scratch or an additional application server
instance to an existing SAP system , the message server is configured to only accept se­
cure 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
62
PUBLIC
.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
Table 14: Operating System Users
Parameter
Definition
Operating System Users and Groups
The installer processes the operating system users as follows:
●
If the operating system users do not exist, the installer creates the following
users:
○
The SAP system administrator user <sapsid>adm
○
Database administrator users
The installer 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 installer 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 installer has completed.
During the Define Parameters phase of the installer, you can specify that the op­
erating system users are to be removed automatically from the group sapinst
after the execution of the installer has completed.
For more information about the group sapinst, see Creating Operating System
Users and Groups [page 80].
For more information about the sapinst_instdir directory, see Useful Infor­
mation About the Installer [page 131].
Table 15: User Management Engine Parameters
Parameter
Definition
Java Administrator User
The installer creates this user in the ABAP system.
Note
This user is only created during the installation of the ap­
plication server ABAP for an SAP NetWeaver 7.5 Process
Integration (PI) system or for an SAP Solution Manager
7.2 system.
After the installation, this user is available both in the ABAP
and in the Java system.
The installer sets the user name J2EE_ADMIN and the mas­
ter password by default.
If required, you can choose another user name and pass­
word according to your requirements.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
PUBLIC
63
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 ap­
plication server ABAP for an SAP NetWeaver 7.5 Process
Integration (PI) system or for an SAP Solution Manager
7.2 system.
Authenticated Users.
The installer creates this user in the ABAP system.
After the installation, it is available both in the ABAP and in
the Java system.
The installer sets the user name J2EE_GUEST and the mas­
ter password by default.
If required, you can choose another user name and pass­
word according to your requirements.
For more information about supported UME data sources
and change options, see SAP Note 718383
Communication User
.
The installer creates this user in the ABAP system.
After the installation, it is available both in the ABAP and in
Note
the Java system
This user is only created during the installation of the ap­
plication server ABAP for an SAP NetWeaver 7.5 Process
Integration (PI) system or for an SAP Solution Manager
7.2 system.
This user is used for the communication between the ABAP
system and the Java system.
The installer sets the user name SAPJSF and the master
password by default.
If required, you can choose another user name and pass­
word according to your requirements.
For more information about supported UME data sources
and change options, see SAP Note 718383
64
PUBLIC
.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
Table 16: System Landscape Directory
Parameter
Definition
SLD Destination for the System
The System Landscape Directory (SLD) registers the systems and the installed software
of your entire system landscape.
You can choose between the following options:
●
Register in existing SLD
Choose this option to register the SAP system you are installing in an existing SAP
System Landscape Directory (SLD) by specifying the SLD connection parameters
listed below in this table.
●
No SLD destination
Choose this option if you do not want to register the SAP system you are installing
in an existing SAP System Landscape Directory (SLD).
You then have to configure the SLD destination manually after the installation has
finished.
For more information, see Performing Post-Installation Steps for the ABAP Application
Server [page 165]
SLD Host
The host name of the existing SLD.
SLD HTTP(S) Port
HTTP port of the SAP system based on AS Java on which the System Landscape Direc­
tory (SLD) resides. The following naming convention applies:
5<Primary_Application_Server_Instance_Number>00.
Example
If the primary application server instance number of the AS Java on which the Sys­
tem Landscape Directory (SLD) resides is 01, the SLD HTTP Port is 50100.
SLD Data Supplier User and
The existing SLD Data Supplier user and password of the existing SLD
password
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
PUBLIC
65
3.6.2 SAP System Database Parameters
Table 17:
Parameters
Description
Database ID <DBSID>
The <DBSID> identifies the database instance. The installer prompts you for the <DBSID>
when you are installing the database instance.
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
195].
●
If you want to perform a Multitenant Database installation,you have to specify one data­
base system ID (<DBSID>) for the container database (CDB) and one <PDBSID> for each
pluggable database (PDB).
SAP
A <PDBSID> cannot be equal to the assigned <DBSID>.
The <DBSID> must be different from the <SAPSID>, because the default and recom­
mended value for the <PDBSID> is the <SAPSID> of the SAP system running with the
PDB.
For more information, see Oracle Database 12c Multitenant Database Installation [page
209].
66
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
Parameters
Description
Database schema, Pass­
The ABAP database schema is named SAP<SCHEMA_ID>.
word
Default name is SAPSR3.
Recommendation
Choose a <SCHEMA_ID> that is different from your <SAPSID>.
It might cause problems when you copy a system where <SCHEMA_ID> is the same as
<SAPSID>, and the database-specific method used for the copy does not allow you to re­
name the database schemas. In certain situations, you might create a system copy with a
new <SAPSID>, but where the database schema has the old <SAPSID>. This is not a tech­
nical problem but it might confuse the system administrator.
Oracle Listener Name,
●
If you install the database instance on a host where no other Oracle database is installed,
Oracle Listener Port,
you normally do not have to change the default values for Listener Name and Listener
Oracle Listener Domain
Port.
●
If there is already an Oracle database installed on your installation host, you can either
use one listener for both databases or you have to specify an unused Listener Name and
an unused Listener Port for the new listener. For more information if you use one listener
for both databases, see SAP Note 98252
●
.
All additional application server instances of an SAP system must use the same Listener
Port than the database instance.
●
Tablespaces, Datafiles
The default domain in the network configuration files is WORLD.
An Oracle database consists of one or more logical storage units called tablespaces, which
collectively store all of the database's data.
Each tablespace in an Oracle database consists of one or more files called datafiles,
which are physical structures that conform to the operating system in which Oracle is running.
MaxDatafileSize is the initial size of the tablespace datafile and its mapping to the new
tablespace layout while importing the external file DBSIZE.XML.
The installer prompts you to enter MaxDatafileSize in MB:
●
0: Datafile size defined in DBSIZE.XML is not changed.
●
2000: Default datafile size.
●
10000: Maximum datafile size.
For more information about space requirements of the SAP datafiles (sapdata 1 - 4), see
Hardware and Software Requirements Tables [page 40].
Install Oracle Database
If you want to implement Oracle Database Vault, make sure that you specify this when enter­
Vault
ing the Oracle Database parameters. For more information, see Implementing Oracle Data­
base Vault with the Installer [page 208]
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
PUBLIC
67
Parameters
Description
User Accounts for Oracle
If you want to implement Oracle Database Vault, make sure that you specify the passwords for
Database Vault
the Oracle Database Vault user accounts secadmin and secacctmgr to be created . For more
information, see Implementing Oracle Database Vault with the Installer [page 208]
3.6.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.
Table 18:
Parameter
Communication Port for ABAP
Description
For a secure communication of connected SAP systems to the
ABAP stack you have to define the HTTPS port that is to be con­
figured in the application server instance profile. Further post-in­
stallation steps [page 168] are required to fully enable HTTPS
communication. For more information about HTTPS enable­
ment, see SAP Notes 1527879
and 510007
.
In addition you can configure an HTTP port. However, this is not
recommended for productive SAP systems due to security rea­
sons.
Recommendation
If you are about to install an SAP NetWeaver 7.5 Process In­
tegration system and you intend to run automated configuration 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 (see also PI: Configuring the
Process Integration System After the Install [page 171]).
68
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
Parameter
Description
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.
3.6.4 Additional Parameters When Using a Stack
Configuration File (Optional)
The parameters in this section are only required if you use a stack configuration file generated from the
Maintenance Planner.
Table 19:
Parameter
Transport Domain
Description
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).
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
PUBLIC
69
Parameter
Description
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.
Decide whether you want to prepare for the Soft­
With the Software Update Manager 1.0 (SUM), you can apply support
ware Update Manager run at the end of the instal­ packages 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
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: http://support.sap.com/
sltoolset
System Maintenance
(SUM) 1.0 SPS<Number>
SUM Batch Input File
Software Update Manager
Guides for SUM 1.0 SP <Number>
You can specify a batch file with some default values for the update.
SUM then starts with parameter batchfile=<XML file with
input parameters>.
Enter the full path to the existing batch file.
Placeholders like @PARAMETER_VALUE@ inside the file are replaced by
values known from the installation.
Install Additional SAP System Languages
A set of default languages is delivered with the ABAP load. From the lan­
guage media delivered with your product version or - if already provided
by the Maintenance Planner for the respective product - using language
archives, you can select additional languages that you want to have in­
stalled during SAP system installation.
If you want to install additional languages, you must provide the direc­
tory with the additional language packages for the ABAP installation
load, for example with subdirectories like DATA_UNITS/ES.
70
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
For more information, see Installation Using a Stack Configuration File (Optional) [page 36].
Related Information
Installation Using a Stack Configuration File [page 36]
3.6.5 Parameters for Additional Components to be Included
in the ASCS Instance (Optional)
You only need to specify the following parameters during the ASCS instance installation if you perform an
integrated installation of additional components.
Note
You must choose Custom parameter mode. Otherwise you are not prompted for the parameters related to
these additional components during the Define Parameters phase.
Table 20:
Parameters
Description
Install a gateway integrated in the ASCS
instance
When processing the screens for the ASCS instance installation, you are
prompted to mark this checkbox on the screen Additional Components to be
Included in the ASCS Instance.
Install an SAP Web Dispatcher inte­
grated in the ASCS instance
When processing the screens for the ASCS instance installation, you are
prompted to mark this checkbox on the screen Additional Components to be
Included in the ASCS Instance.
If you mark the checkbox for SAP Web Dispatcher, you are prompted for the ad­
ditional parameters required for the SAP Web Dispatcher installation on the sub­
sequent screens:
Message Server Host
The name of the host on which the message server is located (profile parameter
rdisp/mshost)
Message Server HTTP Port
HTTP port of the message server (profile parameter ms/server_port_<xx>)
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
PUBLIC
71
Parameters
Description
Password for the Internet Communication Management (ICM) user
In order to use the web administration interface for the Internet Communication
Manager (ICM) and SAP Web Dispatcher, an administration user webadm is cre­
ated by the installer.
You have to assign a password for this user.
Related Information
ASCS Instance with Integrated SAP Web Dispatcher [page 29]
ASCS Instance with Integrated Gateway [page 31]
3.7
Distribution of SAP System and Oracle Database
Components to Disks
When you install the SAP system, the main directories required for the system are automatically created.
However, during the installation procedure, the installer prompts you to enter drive letters for the main
components of the system. This gives you the opportunity to distribute components to disks in the system as
you wish.
How you do this significantly affects system throughput and data security, and must therefore be carefully
planned. The best distribution depends on your specific environment and must take into consideration 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 get an overview of the main
components and their corresponding directories. Then, on the basis of sample configurations and the
recommendations provided in this documentation, you can decide which assignment is best for your particular
system.
SAP systems are normally installed on RAID arrays that ensure data redundancy. This documentation
therefore focuses on RAID subsystems and drives.
Minimal Configuration
The following figure illustrates an example for a disk configuration for a small test or demo system. Since
security and performance play a less crucial role in this type of system, many different configurations are
feasible.
72
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
Caution
Use the illustrated configuration exclusively for test or demo systems. It is unsuitable for production
systems because it only minimally satisfies security and performance requirements.
Figure 9: Configuration for Test or Demo System
Distribution of Database Directories to Disks
Table 21:
Disk
Directories
Disk 1
/oracle/<DBSID>/1120<x> (Oracle 11g)
/<Oracle 12g path> (Oracle 12g, user-defined directory)
/oracle/<DBSID>/origlogA
/oracle/<DBSID>/origlogB
/oracle/<DBSID>/sapdata1
/oracle/<DBSID>/sapdata2
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
PUBLIC
73
Disk
Directories
Disk 2
/oracle/<DBSID>/mirrlogA
/oracle/<DBSID>/mirrlogB
/oracle/<DBSID>/sapreorg
/oracle/<DBSID>/saptrace
/oracle/<DBSID>/saparch
/oracle/<DBSID>/sapbackup
/oracle/<DBSID>/sapcheck
/oracle/<DBSID>/sapdata3
/oracle/<DBSID>/sapdata4
/oracle/<DBSID>/sapprof
Disk 3
/oracle/<DBSID>/oraarch
Note
● The configuration ensures that no data can be lost, but the process for recovering a damaged database
is complicated and time-consuming.
● The redo logs and database files are located on the same disks. This means that a single disk failure can
result in the loss of both the redo logs and database data.
● The I/O-intensive redo logs are on the same disk volumes as the data files. This can impede
performance.
● An equally good alternative would be to simply place all components on a single RAID 5 array.
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 installer creates during the installation of the SAP system by default on
the global host.
The installer by default creates the transport directory on the global host in /usr/sap/trans.
● Use a transport directory located on a host other than the default host:
○ You can use an existing transport directory and host in your SAP system landscape.
○ You can set up a new transport directory on a different host.
74
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
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 119].
More Information
● Required File Systems and Directories [page 86]
● See the SAP Library at:
Table 22:
Release
○
SAP NetWeaver Mobile 7.1
http://help.sap.com/nwmobile71
○
○
SAP NetWeaver 7.1 for Banking Services
SAP Library Path
Application Help
Function-Oriented View
Application Server ABAP
ABAP Technology /
Administration Tools for AS ABAP
from SAP 5.0 and 6.0 (use the SAP Library
Change and Transport System
for SAP NetWeaver Mobile 7.1)
Change and Transport System –
Overview
SAP NetWeaver Mobile 7.1 including En­
Transport Management System – Concept
Basics of the Change and Transport System
hancement Package 1
http://help.sap.com/nwmobile711
○
SAP NetWeaver 7.1 including Enhancement
Package 1 for Banking Services from SAP
5.0 and 6.0 (use the SAP Library for SAP
NetWeaver Mobile 7.1 including Enhance­
ment Package 1)
○
SAP NetWeaver 7.3
http://help.sap.com/nw73
○
SAP NetWeaver 7.3 including Enhancement
Package 1
○
Application Help
Management
Function-Oriented View
Software Logistics
Change and Transport System
Change and Transport System – Overview
http://help.sap.com/nw731
and Transport System
SAP NetWeaver 7.4
Concept
Solution Life Cycle
Basics of the Change
Transport Management System –
http://help.sap.com/nw74
○
SAP NetWeaver 7.5
○
SAP NetWeaver Application Server for
http://help.sap.com/nw75
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.1 to
7.5x on UNIX : Oracle
Planning
PUBLIC
75
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 information and the installation guides that are available at https://wiki.scn.sap.com/wiki/
display/SI/SAP+High+Availability .
● The enqueue replication server (ERS) is essential for a high-availability system. You need one ERS for the
ASCS installed in your system.
76
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
Features
The following graphic shows the essential features of a switchover setup:
Figure 10: Switchover Setup
Note
This figure and the figures in this section are only examples. Only the instances relevant to the switchover
are shown – for example, the primary application server instance is not shown.
These graphics summarize the overall setup and do not show the exact constellation for an installation
based on one of the available technologies (ABAP, dual-stack, or Java).
You need to discuss your individual HA setup with your HA partner.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Planning
PUBLIC
77
The following graphic shows an example of a switchover cluster in more detail:
Figure 11: Switchover Cluster
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.
78
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
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 operating system users and groups [page 80] are created.
2. You set up file systems [page 86] 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 99].
Alternatively you can specify a virtual host name either in the command to start the installer or - after the
installer has started - in the relevant field on the respective instance screen (see Running the Installer
[page 125]).
4. If you want to install a high-availability system, you perform switchover preparations [page 99].
5. If you want to share the transport directory trans from another system, export [page 119] this directory
to your installation hosts.
6. You install the SAP front-end software [page 100] on the desktop of the user.
7. You check that the required installation media [page 100] are available on each host.
8. If you decided to use a generic LDAP directory, you have to create a user for LDAP directory access [page
197].
9. If you want to implement Oracle Database Vault, make sure that you have completed the required
preparation steps. For more information, see Implementing Oracle Database Vault with the Installer [page
208].
10. You continue with Installation [page 112].
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Preparation
PUBLIC
79
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 80] are created.
2. You set up file systems [page 86] 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 99].
Alternatively you can specify a virtual host name either in the command to start the installer or - after the
installer has started in the relevant field on the respective instance screen (see Running the Installer [page
125]).
4. If you want to share the transport directory trans from another system, export [page 119] this directory
to your installation hosts.
5. You install the SAP front-end software [page 100] on the desktop of the user.
6. You check that the required installation media [page 100] are available.
7. You continue with Installation [page 112].
4.2
Creating Operating System Users and Groups
During the installation, the installer checks all required accounts (users, groups) and services on the local
machine. The installer 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 installer 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 installer 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 installer 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 installer checks the NIS users, groups, and services using NIS commands. However, the installer does not
change NIS configurations.
80
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
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 installer and choose
Generic Installation Options
<Database>
Preparation
Operating
System Users and Groups .
For more information, see Running the Installer [page 125].
● 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, Linux, Oracle Solaris: Make sure that you have set the limits for operating system users root,
<sapsid>adm, and your database-specific operating system users (see also section "Creating Operating
System Users and Groups" and "Running the Installer" in the installation guide).
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 11 (x86_64).
Table 23:
Output
Properties
cputime
unlimited
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Preparation
PUBLIC
81
Output
Properties
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).
Table 24:
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.
● 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 use NFS-V4 file system, you have to create the ora<dbsid> user and - if your database release is
Oracle 12 - the oracle user on the NFS server. You can do this either manually or by running Operating
System Users and Groups. This user must have the same user ID as the ora<dbsid> user and - if your
database release is Oracle 12 - the oracle user on the database server.
82
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Preparation
Otherwise, you see the error message FSL-02098 Could not change owner of ... during the
installation of the database instance.
● 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 use local operating system user accounts, make sure that you install your SAP system in Custom
mode and specify suitable IDs for user <sapsid>adm and group sapsys on all hosts. The IDs have to
be the same on all hosts. If you choose Typical mode, you are not asked to specify the user and group
IDs.
● 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 installer, 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 installer chooses available operating system user IDs and group IDs unless you are installing an additional
application server instance. On anadditional 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 installer has completed. For more information, see Ensuring User Security [page 173].
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 is
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Preparation
PUBLIC
83
done automatically. For more information, see Cleanup of Operating System Users in SAP System
Parameters [page 56].
Table 25: SAP System Users and Groups
User
Primary Group
Additional Groups
Comment
root
No primary group assigned by
sapinst
Superuser of the UNIX operat­
the installer.
<sapsid>adm
sapsys
ing system
oper, dba, sapinst
The following groups are always
required for Oracle 12, but for
SAP system administrator and
for Oracle 12 the default data­
base administrator
Oracle 11 only if you want to use
Oracle ASM: asmoper, asmdba
ora<dbsid>
dba
oper, sapinst, oinstall
Database administrator
This user is only required on the
host where the database in­
stance runs.
oracle
dba
oper, sapinst, asmoper,
Oracle Software Owner and da­
asmadmin, asmdba, oinstall
tabase administrator
This user is only required on the
host where the database in­
stance runs.
This user is only required for
Oracle 12 or Oracle 11 with
ASM/Exadata.
Table 26: SAP System Groups and Members
Groups
Members
sapsys
<sapsid>adm
oper
<sapsid>adm, ora<dbsid>, oracle (always required for
Oracle 12; for Oracle 11 only required if you want to use
Oracle ASM)
<sapsid>adm, ora<dbsid>, oracle (always required for
dba
Oracle 12; for Oracle 11 only required if you want to use
Oracle ASM)
sapinst
root, <sapsid>adm, ora<dbsid>, oracle (always re­
quired for Oracle 12; for Oracle 11 only required if you want to
use Oracle ASM)
84
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Preparation
Groups
Members
asmoper
<sapsid>adm (always required for Oracle 12; for Oracle 11
only required if you want to use Oracle ASM), Oracle
oracle (always required for Oracle 12; for Oracle 11 only re­
asmadmin
quired if you want to use Oracle ASM)
<sapsid>adm (always required for Oracle 12; for Oracle 11
asmdba
only required if you want to use Oracle ASM), Oracle
oinstall (always required for Oracle 12; for Oracle 11 only
oracle (always required for Oracle 12; for Oracle 11 only re­
required if you want to use Oracle ASM)
quired if you want to use Oracle ASM), ora<dbsid>
SAP Host Agent:
Table 27: 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 cre­
ated 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
Table 28: Groups and Members of the SAP Host Agent User
Groups
Members
sapsys
sapadm
sapinst
sapadm
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Preparation
PUBLIC
85
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 86]
Oracle Directories [page 92]
Setting Up File Systems for a High-Availability System [page 95]
4.3.1 SAP Directories
Depending on the installation option you have chosen, the installer automatically creates the directories listed
in the following figures and tables. Before running the installation, you have to set up the required file systems
manually. In addition, you have to make sure that the required disk space for the directories to be installed is
available on the relevant hard disks.
The installer creates the following types of directories:
● Physically shared directories
● Logically shared directories
● Local directories
Only valid for 'Platform': HP-UX
HP-UX: For recommendations about block size and mount option configuration, see SAP Note 1077887
.
End of 'Platform': HP-UX
Directories of the SAP System
The figure below assumes that you have set up one file system for the SAP system mount directory <sapmnt>
and one file system for the /usr/sap directory. However, you have to decide for which directories you want to
set up separate file systems. If you do not set up any file system on your installation host, the installer creates
all directories in the root directory (/ ).
The installer prompts you only for the <sapmnt> directory during the installation.
86
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Preparation
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.1 to 7.4:
● Directory Structure for an ABAP System Based on SAP NetWeaver 7.5:
In SAP systems based on SAP NetWeaver 7.5, all application server instances, including the primary
application server instance, are named D<Instance_Number>.
Figure 12: Directory Structure for an ABAP System Based on SAP NetWeaver 7.5
● Directory Structure for an ABAP System Based on SAP NetWeaver 7.1 to 7.4:
In SAP systems based on SAP NetWeaver 7.1 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.1 to
7.5x on UNIX : Oracle
Preparation
PUBLIC
87
Figure 13: Directory Structure for an ABAP System Based on SAP NetWeaver 7.1 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
installer creates the following directories:
● The directory /<sapmnt>/<SAPSID>, which contains SAP kernel and related files, is created on the first
installation host. Normally, the first installation host is the host on which the central services instance is to
run, but you can also choose another host for /<sapmnt>/<SAPSID>.
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 installer creates the following shared subdirectories in /<sapmnt>/<SAPSID> 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 120]):
○ global
Contains globally shared data
○ profile
Contains the profiles of all instances
○ exe
○ Contains a folder uc and a folder nuc, each with a platform-specific subfolder:
○ <sapmnt>/<SAPSID>/exe/uc/<platform> is used in Unicode systems.
88
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Preparation
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, which is the global transport directory.
If you want to use an existing transport directory, you have to mount it before you install the relevant
application server instance. Otherwise, the installer creates /usr/sap/trans locally.
For more information, see Exporting and Mounting the Global Transport Directory [page 119].
Table 29: Physically Shared SAP Directories
Directory
Required Minimum Disk Space
/<sapmnt>/
Minimum 2.5 GB
<SAPSID>
/usr/sap/trans
This value heavily depends on the use of your SAP system.
For production systems, we recommend to use as much free space as available (at least 2 GB), be­
cause the space requirement normally grows dynamically.
For the installation, it is sufficient to use 2 GB for each SAP system instance. You can enlarge the file
system afterwards.
Logically Shared Directories (SAP System)
Logically shared directories reside on the local hosts with symbolic links to the global host. The installer creates
the directory /usr/sap/<SAPSID>/SYS on each host.
This directory contains the following symbolic links to physically shared directories:
● Symbolic link profile points to /<sapmnt>/<SAPSID>/profile
● Symbolic link global points to /<sapmnt>/<SAPSID>/global
This directory contains the exe subdirectory with symbolic links pointing to the corresponding subdirectories
of /<sapmnt>/<SAPSID>/exe on the SAP global host:
● Symbolic link uc (for Unicode) points to /<sapmnt>/<SAPSID>/exe/uc
● Symbolic link nuc (for non-Unicode) points to /<sapmnt>/<SAPSID>/exe/nuc
● Symbolic link run points to 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>
Whenever a local instance is started, the sapcpe program checks the executables against those in the logically
shared directories and, if necessary, replicates them to the local instance.
The installer uses sapcpe to replicate the kernel automatically from /usr/sap/<SAPSID>/SYS/exe/run/
DIR_CT_RUN to /usr/sap/<SAPSID>/<INSTANCE>/exe/DIR_EXECUTABLE for each SAP system instance.
Local Directories (SAP System)
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Preparation
PUBLIC
89
The installer also creates local directories that reside on the local hosts. The directory /usr/sap/<SAPSID>
contains files for the operation of a local instance as well as symbolic links to the data for one system. This
directory is physically located on each host in the SAP system and contains the following subdirectories:
● SYS
Note
The subdirectories of /usr/sap/<SAPSID>/SYS have symbolic links to the corresponding
subdirectories of /<sapmnt>/<SAPSID>, as shown in the figure above.
● Instance-specific directories with the following names:
○ SAP systems based on SAP NetWeaver 7.1 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 enqueue replication server instance (ERS) instance is called ERS<Instance_Number>.
If you install a high-availability system, you must install an ERS instance for the ASCS instance.
Table 30: Local SAP Directories
Directory
Description
SAP systems based on SAP NetWeaver 7.1 to
Primary application server in­
7.4:
stance directory
/usr/sap/<SAPSID>/
Required Minimum Disk Space
●
SAP Business Warehouse server
only: minimum 25 GB
●
Other installations: minimum 4 GB
●
SAP Business Warehouse server
●
Other installations: minimum 4 GB
DVEBMGS<Instance_Number>
SAP systems based on SAP NetWeaver 7.5:
/usr/sap/<SAPSID>/D<Instance_Number>
/usr/sap/<SAPSID>/D<Instance_Number>
Additional application server
only: minimum 25 GB
instance directory
/usr/sap/<SAPSID>/
ABAP central services (ASCS) Minimum 2 GB
ASCS<Instance_Number>
instance directory (high avail­
ability only)
/usr/sap/<SAPSID>/
Enqueue replication server
ERS<Instance_Number>
(ERS) instance directory for
Minimum 2 GB
the ASCS (high availability
only)
90
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Preparation
Directories of the SAP Host Agent
The SAP Host Agent has only local directories as shown in the following figure:
Figure 14: Directory Structure for the SAP Host Agent
Local Directories (SAP Host Agent)
The SAP Host Agent directory /usr/sap/hostctrl requires 100 MB of disk space. It contains the following
subdirectories:
● exe
Contains the profile host_profile
● work
Working directory of the SAP Host Agent
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Preparation
PUBLIC
91
4.3.2 Oracle Directories
The figure below assumes that you have set up one file system for the Oracle directory. However, you have to
decide yourself for which directories you want to set up separate file systems. If you do not set up any file
system on your installation host, the installer creates all directories in the root directory /.
Set up the required file system nodes for the Oracle database before the installation.
Note
The graphics and the table below only list the directories you need to take into consideration for your SAP
system installation. They do not provide a complete list of all Oracle directories.
Figure 15: Oracle Directories (Graphical Overview)
The following table provides more information about the Oracle directories in detail, such as about their usage
and disk space requirements.
92
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Preparation
Table 31: Oracle Directories in Detail
Directory
Description
Required Minimum Disk Space
/oracle
Oracle base directory
37 GB
Make sure that the /oracle file system has the per­
missions 755.
/oracle/client/
<DB_Release>
File system for Oracle client software
100 MB
The installer creates directory /oracle/client/
<DB_Release>/instantclient during the installa­
tion.
Example
Oracle 11: /oracle/client/11x_64
Oracle 12: /oracle/client/12x
/oracle/stage/
Installation and upgrade directory for database soft­
<DB_Release>
ware (staging area)
11 GB
This directory is also used for Oracle upgrades. We
recommend that you do not delete it after the instal­
lation.
Example
Oracle 11.2: /oracle/stage/112_64
Oracle 12.2: /oracle/stage/122
Oracle 11 only:
Home directory of user ora<dbsid>
/oracle/<DBSID>
We recommend that /oracle/<DBSID> does not
reside in the root directory. It must reside in a file sys­
100 MB for files of user
ora<dbsid> (for example, log
files)
tem with support for large files.
Therefore, either create /oracle/<DBSID> as a
separate file system with support for large files or
create /oracle as a file system with support for
large files and create /oracle/<DBSID> as a di­
rectory in /oracle.
Oracle 12 only:
/home/oracle
Home directories of user oracle and user
100 MB for files of user
ora<dbsid>
ora<dbsid> (for example, log
/home/ora<dbsid>
files)
100 MB for files of user oracle
(for example, log files)
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Preparation
PUBLIC
93
Directory
Description
/oracle/<DBSID>/
Home directory for Oracle instance <DBSID>
<DB_Release>
Required Minimum Disk Space
(<ORACLE_HOME>).
●
Database instance: 4.0 GB
●
All other instances: 200 MB
Example
Oracle 11.2: /oracle/KB1/112_64
Oracle 12.2: /oracle/KB1/122
Oracle 11 with ASM and
If your database version is Oracle 12 or if you have
Oracle 12 only:
Oracle 11 with ASM, in this directory the
/oracle/<DBSID>/
sapprof
Oracle 11 without ASM only:
/oracle/<DBSID>/dbs
1 MB
init<DBSID>.ora and the spfile<DBSID>.ora
files are stored, and the init<DBSID>.sap profile
for the Oracle dba tools.
If your database version is Oracle 11 and you do not
1 MB
have ASM, in this directory the init<DBSID>.ora
and the spfile<DBSID>.ora files are stored, and
the init<DBSID>.sap profile for the Oracle dba
tools.
Original set A of redo logs
200 MB
Original set B of redo logs
200 MB
Mirrored set A of redo logs
200 MB
Mirrored set B of redo logs
200 MB
/oracle/<DBSID>/
New standard backup file system for Oracle offline
For the installation, the archive di­
oraarch
redo logs
rectory /oracle/<DBSID>/
/oracle/<DBSID>/
origlogA
/oracle/<DBSID>/
origlogB
/oracle/<DBSID>/
mirrlogA
/oracle/<DBSID>/
mirrlogB
Use a separate disk for the file system /oracle/
<DBSID>/oraarch.
oraarch requires at least 400
MB free disk space. For the opera­
tion of your SAP system, we rec­
The file system /oracle/<SAPSID>/saparch
ommend that the archive direc­
still remains but now only contains brbackup log
tory provides enough space for ar­
files. /oracle/<SAPSID>/saparch is automati­ chives between two backups. In a
cally created by the installer.
production system, the amount
archived each day is between 300
MB and 1 GB.
94
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Preparation
Directory
Description
Required Minimum Disk Space
/oracle/<DBSID>/
Working directory for database administration
1.5 GB
SAP data
24 GB
sapreorg
/oracle/<DBSID>/
sapdata1
/oracle/<DBSID>/
For details, see the DBSIZE.XML
SAP data
sapdata2
/oracle/<DBSID>/
ORA/)
SAP data
sapdata3
/oracle/<DBSID>/
file at the medium for the installa­
tion export (folder EXP1/DB/
See also the Pre-Installation sec­
tion in SAP Note 2172935
.
SAP data
sapdata4
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,
over the host machines). For more information, see Planning the Switchover Cluster [page 76] and contact
your HA partner.
Context
From the perspective of an SAP application, there are the following types of SAP Directories [page 86]:
● Physically shared directories: /<sapmnt>/<SAPSID> and /usr/sap/trans
● 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
● Local directories that contain the SAP instances such as /usr/sap/<SAPSID>/
ASCS<Instance_Number>
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Preparation
PUBLIC
95
Only valid for 'Platform': HP-UX
HP-UX: 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 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). However, an SAP instance directory /usr/sap/<SAPSID>/
<Instance_Type><Instance_Number> that you want to prepare for HA has always to be mounted on
the cluster node currently running the instance. Do not mount such directories with NFS.
Therefore, if the host running the primary application server instance is not the NFS server host, you might
have to mount the file systems for /sapmnt/<SAPSID> and /usr/sap/trans on different physical disks
from the file system for /usr/sap/<SAPSID>/<Instance_Type><Instance_Number>.
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.
○ Replace the links in /usr/sap/<SAPSID>/SYS by a physical copy.
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
86]):
○ SYS, which contains links to the central directory /sapmnt/<SAPSID>
○ <Instance_Type> <Instance_Number> – where the name is defined by the type of services and
the application server number:
○ DVEBMGS<Instance Number> – which contains data for the primary application server instance
○ D<Instance_Number> – which contains data for an additional application server instance
○ ASCS<Instance_Number> – which contains data for the ABAP central services instance
Only <Instance_Type><Instance_Number> directories need to be migrated with the SAP instances
during the switchover.
Therefore, instead of /usr/sap/<SAPSID>, create a file system for /usr/sap/<SAPSID>/
<Instance_Type><Instance_Number> with the usual < > substitutions.
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.
96
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Preparation
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 Enqueue Replication Server (ERS) and additional ABAP or Java application server
instances. The result is a more efficient use of resources. Use this approach for integrated installations
of the application server with ABAP and Java 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 an example of the file systems and disks in an HA setup
Note that this is only an example. For more information on a setup that meets your needs, consult your HA
partner.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Preparation
PUBLIC
97
Figure 16: File Systems and Disks in an HA Setup
98
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
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 24], you need the virtual host name when you install
the ASCS instance in a cluster.
Procedure
Proceed as described in SAP Note 962955
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 99], you have to set the installer property
SAPINST_USE_HOSTNAME to specify the required virtual host name before you start the installer. Alternatively,
you can specify the virtual host name in the relevant field on the respective instance screen.
For more information, see SAP System Parameters [page 56].
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Preparation
PUBLIC
99
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.
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 installer
You always have to download the latest version of the Software Provisioning Manager 1.0 archive.
● The complete media or dedicated installation archives (SAR files) containing the software to be installed,
which are available as follows:
○ You can use the physical installation media as part of the installation package as described in Using the
Physical Media from the Installation Package [page 104].
○ You download the complete installation media as described in Downloading Complete Installation
Media [page 110].
○ As an alternative to downloading the complete SAP kernel media, you can do one of the following:
○ Download the SAP kernel archives (SAR files). For more information, see Downloading SAP Kernel
Archives (Archive-Based Installation) [page 107].
100
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Preparation
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.
Note
Even if you use the complete SAP kernel media, the installer might prompt you during the provisioning
process for additional archives (*.SAR files) due to special Patch Level (PL) requirements depending on
categories such as the product, operating system, and database platform at the end of this section.
For example: The installer might require a certain PL of <X> of the SAPEXEDB.SAR (for DBTYPE <Y>),
but this PL of the SAPEXEDB.SAR is not contained in the SAP kernel media . In this case you have to
following the
download the required PL from https://launchpad.support.sap.com/#/softwarecenter
instructions in Downloading SAP Kernel Archives (Archive-Based Installation) [page 107].
Note
If you are using a stack configuration file (see Installation Using a Stack Configuration File [page 36]),
you have the installation media defined when generating the Landscape Plan. The media link provided in
the Landscape Plan guides you to the location in the SAP Software Download Center at https://
launchpad.support.sap.com/#/softwarecenter
where you can download the installation media
required for your SAP product, operating system and database.
For more information about which kernel version to use, see SAP Note 1680045
Product Availability Matrix at: http://support.sap.com/pam .
. In addition, check the
The installer requests the related kernel media during the corresponding procedure. For more information
about release and road map information around the kernel versions and their relationship to SAP NetWeaver
support packages including important notes on downward compatibility and release dates, see the document
Understanding Kernel Releases for the SAP NetWeaver AS ABAP at http://scn.sap.com/docs/DOC-54170 .
Related Information
Downloading and Extracting the Software Provisioning Manager 1.0 Archive [page 102]
Using the Physical Media from the Installation Package [page 104]
Downloading SAP Kernel Archives (Archive-Based Installation) [page 107]
Downloading Complete Installation Media [page 110]
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Preparation
PUBLIC
101
4.7.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.
Context
You require the latest version of the SAPCAR tool to be able to unpack and verify software component archives
(*.SAR files). *.SAR is the format of software lifecycle media and tools that you can download from the SAP
Software Download Center. For more information about how to get this tool, see the Procedure section below.
An up-to-date version of the load tools - such as R3load, R3szchk, R3ldctl, SAPuptool - which were
available so far only in the SAPEXEDB.SAR archive of the kernel media, has now been made available in the
Software Provisioning Manager archive
(SWPM10SP<Support_Package_Number>_<Version_Number>.SAR), in a sub-archive named
LOADTOOLS.SAR, located in the COMMON/LOADTOOLS folder. For an installation using kernel version 7.40 or
higher, the load tools from the SWPM10SP<Support_Package_Number>_<Version_Number>.SAR are used
automatically instead of the loadtools available in the SAPEXEDB.SAR archive of the kernel media. There is no
action required from your side, the installer uses the relevant loadtools automatically once you run it from the
extracted SWPM10SP<Support_Package_Number>_<Version_Number>.SAR archive.
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. Make sure that you use the latest version of the SAPCAR tool when manually extracting the Software
Provisioning Manager archive.
Note
An older SAPCAR version might extract archive files in a wrong way and this could prevent the installer
from working consistently.
Proceed as follows to get the latest version of SAPCAR:
a. Go to https://launchpad.support.sap.com/#/softwarecenter
PATCHES
SUPPORT PACKAGES &
and search for “sapcar”.
b. Select the archive file for your operating system and download it to an empty directory.
c. Rename the executable to sapcar.exe.
For more information about SAPCAR, see SAP Note 212876
102
PUBLIC
.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Preparation
3. Using the latest version of SAPCAR, you can verify the 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://launchpad.support.sap.com/#/softwarecenter
PATCHES
SUPPORT PACKAGES &
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
it to the same directory.
and move
b. Verify the 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>
4. 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 <Path to Unpack Directory>
Note
Make sure that all users have read permissions for the directory where you want to unpack the installer.
Caution
Make sure that you unpack the Software Provisioning Manager archive to a dedicated folder. Do not
unpack it to the same folder as other installation media.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Preparation
PUBLIC
103
4.7.2 Using the Physical Media from the Installation Package
This section describes how you use the physical installation media as part of the installation package.
Context
The signature of media is checked automatically by the installer during the Define Parameters phase while the
Media Browser screens are processed (see also Running the Installer [page 125] ). The installer only accepts
media whose signature has been checked. For more information, see SAP Note 2393060 .
Procedure
1. Identify the required media for your installation [page 22] as listed below.
Table 32:
SAP Instance
Required Software Packages from Installation Media
Installation
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
instance)
means non-Unicode.
Note
Every new installation of an SAP system is Unicode. You can only use the non-Unicode kernel
if you perform the system copy for a non-Unicode SAP system that has been upgraded to
the current release.
104
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Preparation
SAP Instance
Required Software Packages from Installation Media
Installation
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 kernel
if you perform the system copy for a non-Unicode SAP system that has been upgraded to
the current release.
○
Database software
○
Database patches (if available)
○
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 kernel
if you perform the system copy for a non-Unicode SAP system that has been upgraded to
the current release.
Primary appli­
○
Software Provisioning Manager 1.0 archive
cation server in­
○
UC or NUC Kernel (folder K_<Version>_<N or U>_<OS>) where U means Unicode and N
means non-Unicode.
stance
Note
Every new installation of an SAP system is Unicode. You can only use the non-Unicode kernel
if you perform the system copy for a non-Unicode SAP system that has been upgraded to
the current release.
○
SAP SCM only: SAP liveCache
○
Database Client Software
○
CLI Driver / JDBC Driver
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Preparation
PUBLIC
105
SAP Instance
Required Software Packages from Installation Media
Installation
Additional ap­
○
Software Provisioning Manager 1.0 archive
plication server
○
UC or NUC Kernel (folder K_<Version>_<N or U>_<OS>) where U means Unicode and N
means non-Unicode.
instance
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 instance.
The installer checks whether a non-Unicode system exists and chooses the right executa­
bles for the system type.
○
SAP SCM only: SAP liveCache
○
Database Client Software
Table 33: 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:
a. Download and unpack the latest version of Software Provisioning Manager as described in
Downloading and Extracting the Software Provisioning Manager 1.0 Archive [page 102].
b. Make the media containing the software to be installed 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 http://support.sap.com/migrationkey .
Related Information
Downloading and Extracting the Software Provisioning Manager 1.0 Archive [page 102]
106
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Preparation
4.7.3 Downloading SAP Kernel Archives (Archive-Based
Installation)
As an alternative to downloading the complete SAP kernel media, you can also download exactly the SAP
kernel archives that are required for your installation. During the installation, you can either specify the path to
each archive separately, or provide the path to a download basket with all downloaded archives.
Context
The signature of installation archives is checked automatically by the installer [page 125] during the Define
Parameters phase while processing the Software Package Browser screens. The installer only accepts archives
whose signature has been checked. After scanning the archives and verifying the signature, an info file is
written where you can find detailed information about matching and non-matching archive files. You can access
this info file by choosing the info file link in the Archive Scanning Result section of the Software Package
Browser screen. The info file contains only the results of the latest archive scan. For more information, see SAP
Note 2393060 .
Procedure
1. Download and unpack the latest version of Software Provisioning Manager as described in Downloading
and Extracting the Software Provisioning Manager 1.0 Archive [page 102].
2. Go to https://launchpad.support.sap.com/#/softwarecenter
SUPPORT PACKAGES & PATCHES
By Category
3. Choose the required software component, release, and technical stack:
○ If you want to install SAP NetWeaver AS for ABAP 7.52, choose
products
NW AS ABAP INNOVATION PKG
SAP NetWeaver and complementary
NW AS ABAP 7.52
○ If you want to install SAP NetWeaver AS for ABAP 7.51 innovation package, choose
and complementary products
NW AS ABAP INNOVATION PKG
SAP NetWeaver
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 SAP NetWeaver Mobile 7.1, choose
products
SAP NETWEAVER MOBILE
<Release>
SAP NetWeaver and complementary
Entry by Component
○ If you want to install an SAP NetWeaver ABAP system, choose
products
SAP NetWeaver
<Release>
SAP NetWeaver and complementary
[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
Application Components
by Component
<SAP CRM | SAP ERP | SAP SCM | SAP SRM>
SAP
<Release>
Entry
<ABAP Product Instance>
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Preparation
PUBLIC
107
4. Choose the required package:
Note
If you perform an additional application server installation, kernel archives - such as
SAPEXE<Version>.SAR, SAPEXEDB<Version>.SAR, IGSEXE<Version>.SAR,
igshelper<version>.sar - are only prompted if they cannot be retrieved from the primary
application server instance or the ASCS instance of the existing SAP system.
Caution
○ Make sure that you always use the highest available patch level unless special patch levels are
specified for the relevant package in SAP Note 1680045
.
○ Make sure that you always choose SAPEXE<Version>.SAR, SAPEXEDB<Version>.SAR of the
same SAP kernel release and extension.
Example
○ If SAPEXE<Version>.SAR is of version 7.42 EXT, then SAPEXEDB<Version>.SAR must
also be of version 7.42 EXT.
○ If SAPEXE<Version>.SAR is of version 7.45, then SAPEXEDB<Version>.SAR must also be
of version 7.45.
○ If you provide the archives in one download folder, and there is more than one version of the same
archive available - for example SAPEXE<Version>.SAR - and these versions match the productspecific requirements, the installer selects one of these archive versions. If you want a specific
archive version to be used, make sure that this is the only version available in the download folder.
When running system provisioning in GUI mode, you can also check in the GUI which archive is
being used. So even if there is more than one version of the same archive available in the download
folder, you can select the exact archive version you want to use and enter the exact path to the
required archive file.
○ SAPEXE<Version>.SAR
SAP KERNEL <Version> <UC | NUC>
<Operating System>
#DATABASE INDEPENDENT
Note
SAP KERNEL <Version> <NUC> is only available for SAP systems based on SAP NetWeaver 7.4 or
lower.
○ If you want to install an SAP system based on SAP NetWeaver AS for ABAP 7.52 or higher, you can
only choose 7.49 UNICODE for SAP KERNEL <Version>.
○ If you want to install an SAP system based on SAP NetWeaver AS for ABAP 7.51 innovation
package or higher, you can either choose 7.45 or 7.49 UNICODE for SAP KERNEL <Version>.
○ If you want to install an SAP system based on SAP NetWeaver 7.5, you can either choose 7.45 or
7.49 UNICODE for SAP KERNEL <Version>.
○ If you want to install an SAP system based on SAP NetWeaver 7.4, you can choose either 7.45 or
7.42 for SAP KERNEL <Version>.
○ If you want to install an SAP system based on SAP NetWeaver 7.3 EHP1 or lower, choose 7.21 EXT
for SAP KERNEL <Version>.
108
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Preparation
○ SAPEXEDB<Version>.SAR
Choose the version corresponding to the SAPEXE<Version>.SAR from
<UC | NUC>
<Operating System>
SAP KERNEL <Version>
<DATABASE>
Note
SAP KERNEL <Version> <NUC> is only available for SAP systems based on SAP NetWeaver 7.4 or
lower.
○ DBATOOLS<Version>.SAR
SAP KERNEL <Version> <UC | NUC>
<Operating System>
Oracle
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>
○ If you want to install an SAP system based on SAP NetWeaver Application Server for ABAP 7.52,
SAP IGS <7.49 or 7.53>
choose
# OS independent
○ If you want to install an SAP system based on SAP NetWeaver Application Server for ABAP 7.51
innovation package, choose
SAP IGS <7.45 or 7.49>
# OS independent
, depending on
your SAPEXE<Version>.SAR version.
○ If you want to install an SAP system based on SAP NetWeaver 7.5, choose
7.49>
# OS independent
SAP IGS <7.45 or
, depending on your SAPEXE<Version>.SAR version.
○ If you want to install an SAP system based on SAP NetWeaver 7.4 and your
SAPEXE<Version>.SAR is of version <7.45 or 7.49>, then choose
7.49>
# OS independent
choose
SAP IGS <7.45 or
, depending on your SAPEXE<Version>.SAR version.. Otherwise,
SAP IGS 7.20_EXT
# OS independent
○ If you want to install an SAP system based on SAP NetWeaver 7.3 EHP1, choose
7.20_EXT
SAP IGS
# OS independent
○ If you want to install an SAP system based on SAP NetWeaver 7.3 or lower and use SAP kernel
7.21_EXT, choose
SAP IGS 7.20_EXT
<Operating System>
○ If you want to install an SAP system based on SAP NetWeaver 7.3 or lower and use SAP kernel 7.21,
choose
SAP IGS 7.20
<Operating System>
○ igshelper<version>.sar
○ If you want to install an SAP system based on SAP NetWeaver 7.3 EHP1 or higher, choose
IGS HELPER
SAP
# OS independent
○ If you want to install an SAP system based on SAP NetWeaver 7.3 or lower, choose
SAP IGS 7.20
<Operating System>
○ SAPHOSTAGENT<Version>.SAR
SAP HOST AGENT 7.21
<Operating System>
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Preparation
PUBLIC
109
Recommendation
It is highly recommended that you always choose the highest SP version of the SAPHOSTAGENT<SPversion>.SAR archive.
Note
The SAPHOSTAGENT<Version>.SAR archive is only prompted if there is either no SAP Host Agent
available on the installation host or you specified during the Define Parameters phase that you want
to upgrade an existing version of the SAP Host Agent already available on the installation host. In
the latter case, you must specify a higher version of the SAPHOSTAGENT<Version>.SAR .Otherwise
the existing SAP Host Agent is not upgraded.
5. If you want to install an SAP system based on SAP NetWeaver 7.3 EHP1 or lower - that is you have to use
SAP kernel 7.21 - download the latest patch level of SAPCRYPTOLIB <Version>.SAR from the following
path:
https://launchpad.support.sap.com/#/softwarecenter
Additional Components
SAPCRYPTOLIB
Support Packages and Patches
COMMONCRYPTOLIB<Version>
By Category
<Operating
System>
6. Make the physical media required for the database installation available either by using physical media as
described in Using the Physical Media from the Installation Package [page 104] or by downloading them as
described in Downloading Complete Installation Media [page 110].
4.7.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 102].
2. Create a download directory on the host where you want to run the installer.
3. You identify the required media als listed in Using the Physical Media from the Installation Package [page
104] .
4. Identify all download objects that belong to one medium according to one of the following:
Note
Installation media might be split into several files. In this case, you have to reassemble the required files
after the download.
110
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Preparation
○ Download path or location:
○ To download the complete kernel media, go to https://support.sap.com/sltoolset
Provisioning
Software Provisioning Manager 1.0 SP<Current Version>
releases delivered for SL Toolset
System
Download Kernel
SL TOOLSET 1.0 (INSTALLATIONS AND UPGRADES)
KERNEL
FOR INSTALLATION/SWPM .
○ To download all media required for your SAP product, you can use one of the following navigation
paths:
○ https://launchpad.support.sap.com/#/softwarecenter
By Category
INSTALLATIONS & UPGRADES
SAP NETWEAVER AND COMPLEMENTARY PRODUCTS
<Product>
<Product Release>
○ https://launchpad.support.sap.com/#/softwarecenter
By Alphabetical Index (A-Z)
INSTALLATIONS & UPGRADES
<First Letter of Product>
<Product>
<Product
Release>
○ Material number
All download objects that are part of an installation medium have the same material number and an
individual sequence number:
<Material_Number>_<Sequence_Number>
Example
51031387_1
51031387_2
...
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.1 to
7.5x on UNIX : Oracle
Preparation
PUBLIC
111
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
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 the prerequisites [page 122] and run the installer [page 125] to install the SAP system.
Note
In a standard system, all mandatory instances are installed on one host in one installation run.
Note
If your database release is Oracle 12c and you want to install it as a container database (CDB) or as a
pluggable database PDB in an existing CDB (multitenant database installation), perform the additional
steps as described in Oracle Database 12c Multitenant Database Installation [page 209].
2. You continue with Post-Installation [page 150].
Distributed System
1. If you want to share the transport directory trans from another system, you have to mount [page 119] 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.
112
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
2. On the ASCS instance host, you do the following:
1. You check the prerequisites [page 122] and run the installer [page 125] to install the ABAP central
services instance (ASCS instance).
2. You export global directories [page 120] 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 120] in <sapmnt>/<SAPSID> that you exported from the SAP
global host and – optionally – the trans directory that you exported [page 119] from the SAP
transport host.
2. You check the prerequisites [page 122] and run the installer [page 125] to install the database instance.
Note
If your database release is Oracle 12c and you want to install it as a container database (CDB) or as
a pluggable database PDB in an existing CDB (multitenant database installation), perform the
additional steps as described in Oracle Database 12c Multitenant Database Installation [page 209].
3. If you want to install Oracle Real Application Clusters (RAC), proceed as described in Installing Oracle
Real Application Clusters [page 204].
4. If you want to install the database instance on Oracle Automatic Storage Management (ASM), proceed
as described in Installing Database Instance on Oracle Automatic Storage Management [page 207].
4. On the primary application server instance host, you do the following:
1. You mount the global directories [page 120] in <sapmnt>/<SAPSID> that you exported from the SAP
global host.
2. You check the prerequisites [page 122] and run the installer [page 125] to install the primary
application server instance.
Note
If your database release is Oracle 12c, during the installation you need to specify how the application
server instance is to connect to a pluggable database or a “normal” database. For more information,
see Installing a Distributed Application Server Instance [page 211].
3. If you have installed Oracle Real Application Clusters (RAC), perform the required additional steps for
the primary application server instance as described in Installing Oracle Real Application Clusters
[page 204].
4. If you want to use the shared transport directory trans from another system, you also mount [page
119] this directory.
5. You continue with Post-Installation [page 150].
Graphical Overview
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
PUBLIC
113
The following figure shows how you install the various instances in a distributed system:
Figure 17: Distribution of Instances in an ABAP System
High-Availability System
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 99] and Setting Up File
Systems for a High Availability System [page 95]
2. If you want to share the transport directory trans from another system, you have to mount [page 119] 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:
Note
The following procedure is an example. In this example, we use only one primary cluster node, host A,
and one standby cluster node, host B.
If required, you can also install the ASCS instance and the SCS instance on different hosts.
In this case, you require:
○ At least one primary cluster node, host A1, for the primary node with the ASCS instance, and at
least one primary cluster node, host A2, for the primary node with the SCS instance.
○ At least one standby node, host B1, for the primary node with the ASCS instance, and at least one
standby node, host B2, for the primary node with the SCS instance.
1. You check the prerequisites [page 122] and run the installer [page 125] to install the ABAP central
services instance (ASCS instance) on the primary cluster node, host A. Use a virtual host name [page
99].
114
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
Note
If you want to install an ASCS instance with integrated SAP Web Dispatcher [page 29] or with
integrated SAP Gateway [page 31] or both, you must choose the Custom parameter mode.
When processing the screens for the ASCS instance installation, you are prompted to mark the
corresponding checkbox on the screen Additional Components to be Included in the ASCS Instance.
If you mark the checkbox for SAP Web Dispatcher, you are prompted for the additional parameters
required for the SAP Web Dispatcher installation on the subsequent screens.
2. You check the prerequisites [page 122] and run the installer [page 125] to install the enqueue
replication server instance (ERS instance) for the ASCS instance on the primary cluster node, host A.
Use a virtual host name [page 99].
3. You export global directories [page 120] 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 38] and it has all the necessary file systems [page 95], 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 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 80].
6. You configure the switchover software and test that switchover functions correctly to all standby nodes
in the cluster.
7. You repeat the following steps until you have finished installing the enqueue replication server (ERS
instance) on all nodes in the cluster:
1. You perform the switchover to a node where you want to install the enqueue replication server
instance (ERS instance) for the ASCS instance.
2. You check the prerequisites [page 122] and run the installer [page 125] to install the enqueue
replication server instance (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 122] and run the installer [page 125] to install the database instance
on the database instance host.
Note
If your database release is Oracle 12c and you want to install it as a container database (CDB) or as
a pluggable database PDB in an existing CDB (multitenant database installation), perform the
additional steps as described in Oracle Database 12c Multitenant Database Installation [page 209].
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
PUBLIC
115
3. If you want to install Oracle Real Application Clusters (RAC), proceed as described in Installing Oracle
Real Application Clusters [page 204].
4. If you want to install the database instance on Oracle Automatic Storage Management (ASM), proceed
as described in Installing Database Instance on Oracle Automatic Storage Management [page 207].
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 120] in <sapmnt>/<SAPSID> that you exported from the
switchover cluster infrastructure.
2. You check the prerequisites [page 122] and run the installer [page 125] to install the primary
application server instance.
Note
If your database release is Oracle 12c, during the installation you need to specify how the application
server instance is to connect to a pluggable database or a “normal” database. For more information,
see Installing a Distributed Application Server Instance [page 211].
3. If you have installed Oracle Real Application Clusters (RAC), perform the required additional steps for
the primary application server instance as described in Installing Oracle Real Application Clusters
[page 204].
4. If you want to use the shared transport directory trans from another system, you also mount [page
119] 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 150].
Graphical Overview
116
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
The following figure provides an overview of how you install the various instances in a high-availability
installation:
Figure 18: Distribution of Instances in a High-Availability ABAP System
Additional Application Server Instance
Installation Steps for Additional Application Server Instances for a Standard System
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 120] in <sapmnt>/<SAPSID> that you exported from the
SAP system host.
2. You check the prerequisites [page 122] and run the installer [page 125] to install the additional
application server instance.
Note
If your database release is Oracle 12c, during the installation you need to specify how the application
server instance is to connect to a pluggable database or a “normal” database. For more information,
see Installing a Distributed Application Server Instance [page 211].
3. If you have installed Oracle Real Application Clusters (RAC), perform the required additional steps for
the primary application server instance as described in Installing Oracle Real Application Clusters
[page 204].
3. You continue with Post-Installation [page 150].
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
PUBLIC
117
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 119] 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 120] in <sapmnt>/<SAPSID> that you exported from the SAP
global host.
2. You check the prerequisites [page 122] and run the installer [page 125] to install the additional
application server instance.
Note
If your database release is Oracle 12c, during the installation you need to specify how the application
server instance is to connect to a pluggable database or a “normal” database. For more information,
see Installing a Distributed Application Server Instance [page 211].
3. If you have installed Oracle Real Application Clusters (RAC), perform the required additional steps for
the additional application server instance as described in Installing Oracle Real Application Clusters
[page 204].
4. If you want to use the shared transport directory trans from another system, also mount [page 119]
this directory.
4. You continue with Post-Installation [page 150].
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 119] 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 120] in <sapmnt>/<SAPSID> that you exported from the SAP
global host.
2. You check the prerequisites [page 122] and run the installer [page 125] to install the additional
application server instance.
Note
If your database release is Oracle 12c, during the installation you need to specify how the application
server instance is to connect to a pluggable database or a “normal” database. For more information,
see Installing a Distributed Application Server Instance [page 211].
3. If you have installed Oracle Real Application Clusters (RAC), perform the required additional steps for
the additional application server instance as described in Installing Oracle Real Application Clusters
[page 204].
4. If you want to use the shared transport directory trans from another system, you also mount [page
119] this directory.
4. You continue with Post-Installation [page 150].
118
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
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.
For more information, see the SAP Library at:
Table 34:
Release
●
SAP NetWeaver 7.3
http://help.sap.com/nw73
●
SAP NetWeaver 7.3 including Enhancement Package 1
http://help.sap.com/nw731
SAP Library Path
Application Help
Application Server
Function-Oriented View: English
Application Server ABAP
Administration of Application Server ABAP
SAP NetWeaver 7.4
Transport System
http://help.sap.com/nw74
Overview
●
SAP NetWeaver 7.5
Transport Management System - Concept
●
SAP NetWeaver Application Server for ABAP 7.51
●
Change and
Change and Transport System -
Basics of the Change and Transport System
http://help.sap.com/nw75
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.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
PUBLIC
119
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.
Related Information
Exporting and Mounting Directories via NFS for Linux [page 200]
Exporting and Mounting Directories via NFS for AIX [page 198]
Exporting and Mounting Directories via NFS for Oracle Solaris [page 202]
Exporting and Mounting Directories via NFS for HP-UX [page 199]
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.
120
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
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.
Procedure
1. 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 119].
2. Log on to the host of the new instance that you want to install as user root.
3. 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.
Related Information
Exporting and Mounting Directories via NFS for Linux [page 200]
Exporting and Mounting Directories via NFS for AIX [page 198]
Exporting and Mounting Directories via NFS for Oracle Solaris [page 202]
Exporting and Mounting Directories via NFS for HP-UX [page 199]
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
PUBLIC
121
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 53].
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 172].
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 172].
5.5
Prerequisites for Running the Installer
Make sure you fulfil the following prerequisites before running the installer.
● For the SL Common GUI, make sure that the following web browser requirements are met:
○ You have one of the following supported browsers on the device where you want to run the SL
Common GUI: Google Chrome, Mozilla Firefox, Microsoft Edge, or Microsoft Internet Explorer 11.
Always use the latest version of these web browsers.
Recommendation
We recommend using Google Chrome.
○ If you copy the SL Common GUI URL manually in the browser window, make sure that you open a new
Web browser window in private browsing mode (Internet Explorer), incognito mode (Chrome) or
private browsing mode (Firefox). This is to prevent Web browser plugins and settings from interfering
with the SL Common GUI.
122
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
For more information about the SL Common GUI, see Useful Information About the Installer [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 installer. While running the
installer, this setting is then also added to the environment of the <sapsid>adm user.
Note
By applying this setting the SAP system administrator is responsible for configuring the IP version on
each host of the system landscape, before installing any additional instance to it.
● We recommend that you use the csh shell for the installation. If you want to use another shell, make sure
that you have read SAP Note 202227 .
The installer uses csh scripts during the installation to obtain the environment for user <sapsid>adm.
This is also true if user <sapsid>adm already exists from an earlier SAP system installation, and the shell
of this user is not csh. Before you start the installer, execute the following command as user <sapsid>adm
to make sure that the csh scripts are up-to-date:
/bin/csh -c "source /home/<sapsid>adm/.cshrc;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 777.
● Make sure that you have at least 300 MB of free space in the installation directory for each installation
option. In addition, you need 300 MB free space for the installer executables. If you cannot provide 300 MB
free space in the temporary directory, you can set one of the environment variables TEMP, TMP, or TMPDIR
to another directory with 300 MB free space for the installer executables.
You can set values for the TEMP, TMP, or TMPDIR environment variable to an alternative installation
directory as described in section Useful Information About the Installer [page 131].
● Make sure that umask is set to 022 for the user with root permissions that you want to use for running the
installer.
As the user with root permissions that you want to use for running the installer, 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
HP-UX, Linux, Oracle-Solaris: Make sure that you have set the limits for operating system users root,
<sapsid>adm, and your database-specific operating system users (see also section "Creating Operating
System Users and Groups" and "Running the Installer" in the installation guide).
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.1 to
7.5x on UNIX : Oracle
Installation
PUBLIC
123
○ 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).
Table 35:
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).
Table 36:
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
● Make sure that you have defined the most important SAP system parameters as described in Basic
Installation Parameters [page 55] before you start the installation.
● Check that your installation host meets the requirements for the installation options that you want to
install.
124
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
For more information, see Running the Prerequisite Checker [page 39].
● 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.
Check that the SYSTEM tablespace contains at least 400 MB of free space. If there is not enough space
left, increase the size of this tablespace with BRSPACE or BRTOOLS.
For more information, see Installation of Multiple Components in One Database [page 195].
● 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 installer and the SL
Common GUI.
If this port cannot be used, you can assign a free port number by executing sapinst with the following
command line parameter:
SAPINST_HTTPS_PORT=<Free Port Number>
○ Port 4239 is used by default for displaying the feedback evaluation form at the end of the installer
processing.
The filled-out evaluation form is then sent to SAP using HTTPS.
If this port cannot be used, you can assign a free port number by executing sapinst with the following
command line parameter:
SAPINST_HTTP_PORT=<Free Port Number>
5.6
Running the Installer
This section describes how to run the installation tool Software Provisioning Manager (the “installer” for short).
Prerequisites
For more information, see Prerequisites for Running the Installer [page 122].
Context
Software Provisioning Manager (the “installer” for short) has a web browser-based GUI named “SL Common
GUI of the Software Provisioning Manager” - “SL Common GUI” for short.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
PUBLIC
125
This procedure describes an installation where you run the installer and use the SL Common GUI, that is you
can control the processing of the installer from a browser running on any device.
For more information about the SL Common GUI, see Useful Information About the Installer [page 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 installer has not set
any environment variables for a different SAP system or database.
If your security policy requires that the person running the installer 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 have to confirm that the user is a trusted one. For
more information, see SAP Note 1745524
.
2. Make the installation media available.
For more information, see Preparing the Installation Media [page 100] .
Note
Even if you use the complete SAP kernel media, the installer might prompt you during the provisioning
process for additional archives (*.SAR files) due to special Patch Level (PL) requirements depending on
categories such as the product, operating system, and database platform.
For example: The installer might require a certain PL of <X> of the SAPEXEDB.SAR (for DBTYPE <Y>),
but this PL of the SAPEXEDB.SAR is not contained in the SAP kernel media . In this case you have to
following the
download the required PL from https://launchpad.support.sap.com/#/softwarecenter
instructions given in Downloading SAP Kernel Archives (Archive-Based Installation) [page 107].
Recommendation
Make the installation media available locally . 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 installer from the directory to which you unpacked the Software Provisioning Manager archive by
entering the following commands:
126
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
<Path_To_Unpack_Directory>/sapinst
Note
If you are using a stack configuration file (see Installation Using a Stack Configuration File (Optional)
[page 36]), you have to 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 a virtual host name to the instance to be installed and you do not want to assign it
by entering it as a parameter using the installer screens (see SAP System Parameters [page 56]), you
can alternatively assign it by starting the installer with the SAPINST_USE_HOSTNAME property:
<Path_To_Unpack_Directory>/sapinst SAPINST_USE_HOSTNAME=<Virtual_Host_Name>
For more information, see Using Virtual Host Names [page 99].
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 have to start the installer 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 at http://support.sap.com/sltoolset
Provisioning
System Copy Option
System
Guide for Systems Based on SAP NetWeaver 7.1 & Higher
4. The installer is starting up.
The installer now starts and waits for the connection with the SL Common GUI.
You can find the URL you require to access the SL Common GUI at the bottom of the shell from which you
are running the installer.
...
************************************************************************
Open your browser and paste the following URL address to access the GUI
https://[<hostname>]:4237/sapinst/docs/index.html
Logon users: [<users>]
************************************************************************
...
If you have a supported web browser (see Prerequisites for Running the Installer [page 122]) installed on
the host where you run the installer, you can open this URL directly in the shell. Otherwise open the URL in
a supported web browser that runs on another device.
The SL Common GUI opens in the browser by displaying the Welcome screen.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
PUBLIC
127
Note
Before you reach the Welcome screen, your browser might warn you that the certificate of the sapinst
process on this computer could not be verified. Accept this warning to inform your browser that it can
trust this site, even if the certificate could not be verified.
5. On the Welcome screen, choose the required option:
○ Perform preparations
Go to
Generic Options
Preparations
<Database>
and choose the required task.
○ Install an SAP system:
○ To install an SAP system based on SAP NetWeaver Application Server for ABAP, 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, choose
SAP NetWeaver 7.5
ABAP for SAP Process Integration
<Database>
Installation
Application Server
<System Variant> .
○ To install the application server ABAP for an SAP Solution Manager 7.2 system, choose
Solution Manager 7.2 <Support_Release>
<Support_Release>
<Database>
SAP
SAP Solution Manager 7.2 ABAP
SAP System
Application Server ABAP
<System
Variant> .
○ Install an additional application server 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 installer, you can find the log file
dev_selfex.out in the temporary directory.
7. Follow the instructions on the installer screens and enter the required parameters.
Note
To find more information on each parameter during the Define Parameters phase, position the cursor on
the required parameter input field , and choose either F1 or the HELP tab. Then the available help text
is displayed in the HELP tab.
Note
If you want to install an ASCS instance with integrated SAP Web Dispatcher [page 29] or with integrated
SAP Gateway [page 31] 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.
128
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
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
installer 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 installer 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
Provisioning
System Copy Option
System
Guide for Systems Based on SAP NetWeaver 7.1 & Higher
Caution
The signature of 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.
Keep in mind that this automatic check is only committed once and not repeated if you modify artefacts
such as SAR archives or files on the media after the initial check has been done. This means that - if you
modify artefacts later on either during the remaining Define Parameters phase or later on during the
Execute Service phase - the signature is not checked again.
See also the description of this new security feature in SAP Note 2393060
.
After you have entered all requested input parameters, the installer displays the Parameter Summary
screen. This screen shows both the parameters that you entered and those that the installer set by default.
If required, you can revise the parameters before starting the installation.
8. To start the installation, choose Next.
The installer starts the installation and displays the progress of the installation. When the installation has
finished, the installer shows the message: Execution of <Option_Name> has completed.
Note
○ During the installation of the Oracle database instance, the installer stops the installation and
prompts you to install the Oracle database software [page 139].
This action is not required if you install a system into an existing database (MCOD).
After you have finished the installation of the Oracle database, you continue the database instance
installation by choosing OK in the GUI of the database instance installation.
○ Check SAP Note 1431800
environments.
for technical information about Oracle Release 11 in SAP
○ Check SAP Note 1914631
for technical information about Oracle Release 12 in SAP environments.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
PUBLIC
129
○ If you want to install Oracle Real Application Clusters (RAC), proceed as described in Installing
Oracle Real Application Clusters [page 204] after the Software Provisioning Manager has
completed the installation of the database instance.
○ If you want to install the database instance on Oracle Automatic Storage Management (ASM),
proceed as described in Installing Database Instance on Oracle Automatic Storage Management
[page 207] after the Software Provisioning Manager has completed the installation of the database
instance.
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 56] . You
have to 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
9. If required, delete directories with the name sapinst_exe.xxxxxx.xxxx after the installer 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 media 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. For security reasons, we recommend that you delete the .sapinst directory within the home directory of
the user with which you ran the installer:
<User_Home>/.sapinst/
11. If you copied the installer software to your hard disk, you can delete these files when the installation has
successfully completed.
12. For security reasons, we recommend that you remove the operating system users from the group sapinst
after you have completed the installation.
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 installer has
completed.
130
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
5.7
Additional Information About the Installer
The following sections provide additional information about the installer.
Useful Information About the Installer [page 131]
This section contains some useful technical background information about the installer and the
installer GUI.
Interrupted Processing of the Installer [page 133]
Here you find information about how to restart the installer if its processing has been interrupted.
Entries in the Services File Created by the Installer [page 136]
Troubleshooting with the Installer [page 137]
This section tells you how to proceed when errors occur while the installer is running.
Using the Step State Editor (SAP Support Experts Only) [page 138]
This section describes how to use the Step State Editor available in the installer.
5.7.1 Useful Information About the Installer
This section contains some useful technical background information about the installer and the installer GUI.
● Software Provisioning Manager (the “installer” for short) has the web browser-based “SL Common GUI of
the Software Provisioning Manager” - “SL Common GUI” for short.
The SL Common GUI uses the SAP UI Development Toolkit for HTML5 - also known as SAPUI5 - a clientside 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.
The SL Common GUI connects the web browser on a client with the sapinst executable - which is part of
Software Provisioning Manager - running on the installation host using the standard protocol HTTPS.
For the SL Common GUI the installer provides a pre-generated URL at the bottom of the shell from which
you are running the installer . If you have a supported web browser installed on the host where you run the
installer, you can start the SL Common GUI directly from this URL. Otherwise, open a web browser
supported by the SL Common GUI on any device and run the URL from there.
For more information about supported web browsers see Prerequisites for Running the Installer [page
122].
If you need to run the SL Common GUI in accessibility mode, apply the standard accessibility functions of
your web browser.
● As soon as you have started the sapinst executable, the installer creates a .sapinst directory
underneath the /home/<User> directory where it keeps its log files. <User> is the user with which you
have started the installer.
After you have reached the Welcome screen and selected the relevant installer option for the SAP system
or instance to be installed , the installer creates a directory sapinst_instdir where it keeps its log files,
and which is located directly below the temporary directory. The installer finds the temporary directory by
checking the value of the TEMP, TMP, or TMPDIR environment variable. If no value is set for these variables,
the installer uses /tmp by default.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
PUBLIC
131
All log files which have been stored so far in the .sapinst folder are moved to the sapinst_instdir
directory as soon as the latter has been created.
If you want the sapinst_instdir directory to be created in another directory than /tmp, set the
environment variable TEMP, TMP, or TMPDIR to this directory before you start the installer.
Table 37:
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.
Recommendation
We recommend that you keep all installation directories until the system is completely and correctly
installed.
● The installer extracts itself to the temporary directory. These executables are deleted again after the
installer has stopped running.
Directories called sapinst_exe.xxxxxx.xxxx sometimes remain in the temporary directory after the
installer has finished. You can safely delete them.
The temporary directory also contains the log file dev_selfex.out from the self-extraction process of
the installer, which might be useful if an error occurs.
Caution
If the installer cannot find a temporary directory, the installation terminates with the error FCO-00058.
● To see a list of all available installer properties, start the installer as described above with the option -p:
./sapinst -p
● If you want to perform an installation in unattended mode, see SAP Note 2230669
improved procedure using inifile.params.
which describes an
● If required, stop the installer by choosing the Cancel button.
Note
If you need to terminate the installer, press Ctrl + C .
132
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
5.7.2 Interrupted Processing of the Installer
Here you find information about how to restart the installer if its processing has been interrupted.
Context
The processing of the installer might be interrupted for one of the following reasons:
● An error occurred during the Define Parameters or Execute phase:
The installer does not abort the installation in error situations. If an error occurs, the installation pauses
and a dialog box appears. The dialog box contains a short description of the choices listed in the table
below as well as a path to a log file that contains detailed information about the error.
● You interrupted the processing of the installer by choosing Cancel in the SL Common GUI.
Caution
If you stop an option in the Execute phase, any system or component installed by this option is
incomplete and not ready to be used. Any system or component uninstalled by this option is not
completely uninstalled.
The following table describes the options in the dialog box:
Table 38:
Option
Definition
Retry
The installer retries the installation from the point of failure without repeating any of
the previous steps.
This is possible because the installer records the installation progress in the
keydb.xml file.
We recommend that you view the entries in the log files, try to solve the problem, and
then choose Retry.
If the same or a different error occurs, the installer displays the same dialog box
again.
Stop
The installer stops the installation, closing the dialog box, the installer GUI, and the
GUI server.
The installer records the installation progress in the keydb.xml file. Therefore, you
can continue the installation from the point of failure without repeating any of the
previous steps. See the procedure below.
Continue
The installer continues the installation from the current point.
View Log
Access installation log files.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
PUBLIC
133
Note
You can also terminate the installer 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 the Installer
[page 125] .
2. Make sure that the installation media are still available.
For more information, see Preparing the Installation Media [page 100] .
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. Make sure that the installation media are still available.
For more information, see Preparing the Installation Media [page 100] .
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
4. Restart the installer from the directory to which you unpacked the Software Provisioning Manager archive
by executing the following command:
<Path_To_Unpack_Directory>/sapinst
134
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
5. The installer is restarting.
The installer now starts and waits for the connection with the SL Common GUI.
You can find the URL you require to access the SL Common GUI at the bottom of the shell from which you
are running the installer.
...
************************************************************************
Open your browser and paste the following URL address to access the GUI
https://[<hostname>]:4237/sapinst/docs/index.html
Logon users: [<users>]
************************************************************************
...
If you have a supported web browser (see Prerequisites for Running the Installer [page 122]) installed on
the host where you run the installer, you can open this URL directly in the shell. Otherwise open the URL in
a supported web browser that runs on another device.
The SL Common GUI opens in the browser by displaying the Welcome screen.
Note
Before you reach the Welcome screen, your browser might warn you that the certificate of the sapinst
process on this computer could not be verified. Accept this warning to inform your browser that it can
trust this site, even if the certificate could not be verified.
6. From the tree structure on the Welcome screen, select the installation option that you want to continue and
choose Next.
The What do you want to do? screen appears.
7. On the What do you want to do? screen, decide between the following alternatives and continue with Next:
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
PUBLIC
135
Table 39:
Alternative
Behavior
Perform a new run
The installer does not continue the interrupted installation option. Instead, it
moves the content of the old installer directory and all installer-specific files to
a backup directory. Afterwards, you can no longer continue the old option.
The following naming convention is used for the backup directory:
log_<Day>_<Month>_<Year>_<Hours>_<Minutes>_<Seconds>
Example
log_01_Oct_2016_13_47_56
Note
All actions taken by the installation before you stopped it (such as creating
directories or users) are not revoked.
Caution
The installer moves all the files and folders to a new log directory, even if
these files and folders are owned by other users. If there are any processes
currently running on these files and folders, they might no longer function
properly.
Continue with the existing one
The installer continues the interrupted installation from the point of failure.
5.7.3 Entries in the Services File Created by the Installer
After the installation has finished successfully, the installer 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)
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
136
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
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.4 Troubleshooting with the Installer
This section tells you how to proceed when errors occur while the installer is running.
Context
If an error occurs, the installer:
● Stops processing
● Displays a dialog informing you about the error
Procedure
1. Check SAP Note 1548438
for known installer issues.
2. If an error occurs during the Define Parameters or the Execute Service phase, do one of the following:
○ Try to solve the problem:
○ To check the installer log files (sapinst.log and sapinst_dev.log) for errors, choose the LOG
FILES tab.
Note
The LOG FILES tab is only available if you have selected on the Welcome screen the relevant
installer option for the SAP product to be installed .
If you need to access the log files before you have done this selection, you can find them in
the .sapinst directory underneath the /home/<User> directory, where <User> is the user
which you used to start the installer.
Fore more information, see Useful Information About the Installer [page 131].
○ To check the log and trace files of the installer GUI for errors, go to the directory
<User_Home>/.sapinst/
○ Then continue by choosing Retry.
○ If required, abort the installer by choosing Cancel in the tool menu and restart the installer. For more
information, see Interrupted Processing of the Installer [page 133].
3. If you cannot resolve the problem, report an incident using the appropriate subcomponent of BC-INS*.
For more information about using subcomponents of BC-INS*, see SAP Note 1669327
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
.
PUBLIC
137
5.7.5 Using the Step State Editor (SAP Support Experts Only)
This section describes how to use the Step State Editor available in the installer.
Note
Only use the Step State Editor if SAP Support requests you to do so, for example to resolve a customer
incident.
Prerequisites
● SAP Support requests you to use theStep State Editor.
● Make sure that the host where you run the installer meets the requirements listed in Prerequisites for
Running the Installer [page 122].
Procedure
1. Start the installer from the command line as described in Running the Installer [page 125] with the
additional command line parameter SAPINST_SET_STEPSTATE=true
2. Follow the instructions on the installer screens and fill in the parameters prompted during the Define
Parameters phase until you reach the Parameter Summary screen.
3. Choose Next.
The Step State Editor opens as an additional dialog. Within this dialog you see a list of all steps to be
executed by the installer during the Execute Service phase. By default all steps are in an initial state.
Underneath each step, you see the assigned installer component. For each step you have a Skip and a
Break option.
○ Mark the checkbox in front of the Break option of the steps where you want the installer to pause.
○ Mark the checkbox in front of the Skip option of the steps which you want the installer to skip.
4. After you have marked all required steps with either the Break or the Skip option, choose OK on the Step
State Editor dialog.
The installer starts processing the Execute Service phase and pauses one after another when reaching
each step whose Break option you have marked. You can now choose one of the following:
○ Choose OK to continue with this step.
○ Choose Step State Editor to return to the Step State Editor and make changes, for example you can
repeat the step by marking the checkbox in front of the Repeat option.
○ Choose Cancel to abort the installer.
5. Continue until you have run through all the steps of the Execute Service phase of the installer.
138
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
5.8
Oracle Database Software Installation
Continue with the section relevant for the release of the Oracle database that you want to install:
Oracle 11 Database Software Installation [page 139]
Proceed as follows to install the Oracle 11 database software.
Oracle 12 Database Software Installation [page 144]
Proceed as follows to install the Oracle 12 database software.
5.8.1 Oracle 11 Database Software Installation
Proceed as follows to install the Oracle 11 database software.
Context
The installer prompts you to install the Oracle 11 database software.
Procedure
1. You update the Oracle installation scripts [page 139].
2.
Only valid for 'Platform': AIX
AIX only: You perform steps for the AIX operating system [page 140]
End of 'Platform': AIX
3. You run the Oracle Universal Installer [page 141].
4. You install the required SAP bundle patch [page 143].
5.8.1.1
Updating the RUNINSTALLER Scripts
You need to update the installation scripts before you start the installation as such.
Prerequisites
The SAP-specific installation scripts RUNINSTALLER, RUNINSTALLER_CHECK, and 11ginstall.sh are
located in directory SAP in the Oracle database software stage.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
PUBLIC
139
Context
If a newer version is available, we recommend that you update the Oracle Installation scripts, which are
attached to SAP Note 1524205 . From there you can download the relevant package for your release. After
you have extracted the Oracle software to the staging area, you need to update the installation scripts.
Procedure
1. Check SAP Note 1524205
installation medium.
to see if there is a more recent version of the installation scripts than on the
2. If required, download the new version attached to the SAP Note, following the instructions there.
5.8.1.2
Performing Pre-Installation Steps for the AIX
Operating System
This topic is only valid for 'Platform': AIX
To install the Oracle database software on the AIX operating system, you need to run the rootpre.sh script to
adapt the AIX kernel and also execute a command as the root user.
Prerequisites
● If several Oracle instances run on one computer, you must shut these down before adapting the kernel.
● Make sure that the ORACLE_HOME and ORACLE_SID environment variables are set.
Procedure
Run the rootpre.sh script as follows:
1. Log on to the system with user ora<dbsid> if you are not already logged on.
2. Change to the directory /oracle/stage/112_64/database using the following command:
cd /oracle/stage/112_64/database
3. Make sure that the user root is assigned the environment of ora<dbsid>:
su root
4. Call the script rootpre.sh:
./rootpre.sh
5. Log off with the user root:
140
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
exit
End of 'Platform': AIX
5.8.1.3
Installing the Oracle Database Software
Proceed as follows to install the Oracle 11g database software.
Prerequisites
A graphical user interface (GUI), for example X11, is required for the Oracle database software installation with
runInstaller. For more information, see the documentation of your operating system.
Context
Starting with the first patch set for Oracle Database 11g Release 2 (11.2.0.2), Oracle Database patch sets are full
installations of the Oracle database software. You only need to install the current Oracle database patch set. For
more information about the current patch set, see SAP Note 1431799 .
For more information about how to install Oracle database 11.2 software, see SAP Note 1524205
Troubleshooting the installation is described in SAP Note 1431796 .
.
Caution
Before starting to install the Oracle software, make sure that you have updated the installation scripts as
described in Updating the Oracle Installation Scripts [page 145].
Procedure
1. Log on as the Oracle database software owner <ora_sw_owner>.
If you are already logged on as user root, you can switch to the Oracle database software owner, user
<ora_sw_owner>, by entering the following command:
su - <ora_sw_owner>
2. Change to the stage directory:
cd /oracle/stage/112_64/database/SAP
3. Make sure that umask is set to 022 by entering the following command:
umask 022
4. Make sure that the DISPLAY environment variable is set to <Host_Name>:0.0, where <Host_Name> is
the host on which you want to display the GUI of the Oracle Universal Installer (OUI).
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
PUBLIC
141
Table 40:
Shell Used
Command
Bourne shell (sh)
DISPLAY=<Host_Name>:0.0
export DISPLAY
C shell (csh)
setenv DISPLAY <Host_Name>:0.0
Korn shell (ksh)
export DISPLAY=<Host_Name>:0.0
5. Start the OUI with the Oracle database software owner, user <ora_sw_owner>, as follows:
./RUNINSTALLER
For silent operation, enter this command:
./RUNINSTALLER -silent
For more information on further options, see SAP Note 1524205
.
6. Respond to the OUI as follows:
Table 41:
Prompt or Condition
Action
Configure Security Updates
Do not select the checkbox.
The runInstaller issues a warning.
Choose OK and then Next.
Select Installation Option
Confirm the default selections by choosing Next.
Grid Installation Options
Confirm the default selection Single Instance Installation
and then choose Next.
Select Product Language
Confirm the default option English and then choose Next.
Select Database Edition
Confirm the default option Enterprise Edition and then
choose Next.
Specify Installation Location
This screen displays the value for ORACLE_BASE which is
set in the environment. It also displays the value for
ORACLE_HOME, which should be /oracle/DBSID/
<release>.
See SAP Note 1521371
to set ORACLE_BASE for your
configuration.
Select this option and then Next.
Privileged OS Groups
This screen displays the operating system groups for the
DBA and the operator. Normally, these are dba and oper.
142
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
Prompt or Condition
Action
Perform Prerequisite Checks
This screen checks if all the required system prerequisites
for installation of the database software have been met. If
some of the checks are displayed as Failed, you can fix
these problems (either by installing the missing patches
or configuring the kernel parameters) and run the check
again by choosing Check Again.
Recommendation
We strongly recommend you to make sure that there
are no failed checks before starting the software instal­
lation.
Summary
Review the information displayed on this screen and
choose Finish.
Finish
Finish the software installation by executing the root.sh
script as the root user from another session.
7. To exit the OUI, choose Exit and confirm the dialog box that appears.
Results
The patch set software is now installed in the installation Oracle home. This is referred to – for example, in SAP
Notes – as <IHRDBMS>.
Example
/oracle<DBSID>/11204
You now have to install the required SAP bundle patch [page 149].
5.8.1.4
Installing the Required SAP Bundle Patch
After the Oracle database software installation, you need to install the required SAP bundle patch.
Prerequisites
Check SAP Note 1431800
to be installed.
to find a cross-reference to the current SAP Note with the list of required patches
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
PUBLIC
143
Context
You must install the SAP bundle patch using the Oracle tool MOPatch, which you can find at SAP Note 1027012
.
You only need to install the latest SAP bundle patch because these patches are cumulative.
The SAP bundle patch also delivers a set of upgrade scripts that automate most of the pre-upgrade and postupgrade tasks. For more information, see SAP Note 1431793 .
Procedure
1. Log on at the operating system level as the Oracle database software owner, user <ora_sw_owner>.
2. Install the SAP bundle patch according to the instructions in the SAP bundle patch README file.
5.8.2 Oracle 12 Database Software Installation
Proceed as follows to install the Oracle 12 database software.
Context
The installer prompts you to install the Oracle 12 database software.
Procedure
1. You update the SAP RUNINSTALLER scripts [page 145].
2. You install the current Oracle Database Patch Set [page 145].
3. You install the SAP Bundle Patch [page 149].
144
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
5.8.2.1
Updating the RUNINSTALLER Scripts
You need to update the installation scripts before you start the installation as such.
Context
The SAP-specific installation scripts RUNINSTALLER and 12cinstall.sh are located in directory SAP in the
Oracle database software stage (that is, /oracle/stage/122/database/SAP).
You need to check the patch level of the RUNINSTALLER and check in SAP Note 1915301
whether a higher
version is available. If a higher version is available, we recommend that you update the Oracle installation
scripts, which are attached to SAP Note 1915301 . From there you can download the relevant package for
your release. After you have extracted the Oracle software to the staging area, you need to update the
installation scripts.
Procedure
1. Check the current version of RUNINSTALLER as the database software owner, that is the oracle user.
If you install Oracle 1.22, execute the following commands:
cd /oracle/stage/122/database/SAP
./RUNINSTALLER -version
If you install Oracle 1.21, execute the following commands:
cd /oracle/stage/121/database/SAP
./RUNINSTALLER -version
2. If a higher patch level is available, download the newer version in SAP Note 1915301
instructions there.
5.8.2.2
, following the
Installing the New Oracle Database 12c Software
Proceed as follows to install the Oracle 12c database software.
Prerequisites
A graphical user interface (GUI), for example X11, is required for the Oracle database software installation with
runInstaller. For more information, see the documentation of your operating system.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
PUBLIC
145
Context
For more information about the current patch set, see SAP Note 1915313
.
For more information about how to install Oracle Database 12c software, see SAP Note 1915301
.
During the software installation of Oracle 12c use the new recommended ORACLE_BASE/oracle/<DBSID>.
Procedure
1. Log on as the Oracle database software owner, that is the oracle user.
2. Change to the stage directory:
If you install Oracle 1.22, execute the following commands:
cd /oracle/stage/12202/database/SAP
If you install Oracle 1.21, execute the following commands:
cd /oracle/stage/12102/database/SAP
3. Make sure that umask is set to 022 by entering the following command:
umask 022
4. Make sure that the DISPLAY (for dialog mode) is set in the environment.
5. Start the OUI with the Oracle database software owner, user oracle, as follows:
./RUNINSTALLER
For silent operation, enter this command:
./RUNINSTALLER -oracle_base /oracle/<DBSID> -silent -nocheck
For more information on further options, see SAP Note 1915301
.
6. Respond to the OUI as follows:
Table 42:
Prompt or Condition
Action
Configure Security Updates
Do not select the checkbox.
The run Installer issues a warning.
Choose Next and then Yes.
Installation Option
Confirm the pre-selected default Install database software only by
choosing Next.
Database Installation Options
Confirm the default selection Single Instance database installation and
then choose Next.
Database Edition
146
PUBLIC
Confirm the default option Enterprise Edition and then choose Next.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
Prompt or Condition
Action
Installation Location
This screen displays the value of ORACLE_HOME that should be:
/oracle/<DBSID>/<release>, and
ORACLE_BASE that should be:
/oracle/<DBSID>
For more information on setting ORACLE_BASE for your configuration,
see SAP Note 1521371
.
Choose Next.
If you see the following error message from the OUI, you can safely ig­
nore it and continue with the installation:
[INS-32008] Oracle base location can't be same
as user home directory
Operating System Groups
This screen displays the operating system groups:
○
OSDBA:dba
○
OSOPER:oper
○
OSBACKUPDBA:oper
○
OSDGDBA:dba
○
OSKMDBA:dba
○
OSRACDBA:dba
Leave the default and continue with Next.
Prerequisite Checks
This screen checks if all the required system prerequisites for installa­
tion of the database software have been met. If some of the checks are
displayed as Failed, you can fix these problems by choosing Fix & Check
Again.
Recommendation
We strongly recommend you to make sure that there are no failed
checks before starting the software installation.
If not all prerequisites are met and you decide to ignore the warnings
about failed checks, you later see the OUI warning [INS-13016].
Summary
Review the information displayed on this screen and choose Install to
start the installation.
Install Product
Here you can now monitor the installation progress.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
PUBLIC
147
Prompt or Condition
Action
Install Product Finish
Here you can now monitor the installation progress.
Finish at the end of the software installation execute the Root Scripts as
indicated as the root user from another session.
If root.sh prompts you that a file (dbhome, oraenv, coraenv) already
exists, allow root.sh to overwrite it so that the new version is copied.If
this is the first Oracle product you have installed on this host, also run
the oraInstroot.sh script from the central inventory as follows:
$Oracle_Home/oraInventory/oraInstRoot.shExample If
you are using sudo to change to a root user, you run the following com­
mand:/usr/local/bin/sudo $ORACLE_HOME/
oraInventory/
Finish
On the Finish screen you should see The installation of
Oracle Database was successful.
Click Close to exit from OUI
.
7. To exit the OUI, choose Close and confirm the dialog box that appears.
In the event of error during the software installation, see the troubleshooting information in SAP Note
1915299 .
Results
The Oracle Database 12c software is now installed . The installation location is referred to – for example, in SAP
Notes – as Installation Oracle Home <IHRDBMS>. Also the link 122 -> 12201 under /oracle/<DBSID> is
created.
Example
/oracle/<DBSID>/12201
You now have to install the required SAP bundle patch [page 149].
148
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
5.8.2.3
Installing the Current SAP Bundle Patch
After the installation of the Oracle Database software, you need to install the current (that is, the latest) SAP
bundle patch (SBP) into the new Oracle home.
Prerequisites
Check SAP Note 2470660
to find a cross-reference to the current SAP Note with the list of required patches
to be installed. You must install the SBP using the Oracle tool MOPatch. For more information about MOPatch,
see SAP Note 1027012 .
Context
The SBP also delivers a set of upgrade scripts that later automate most of the pre-upgrade and post-upgrade
tasks.
Only valid for 'Platform': AIX
Caution
AIX only: Make sure that you install the latest SAP Bundle Patch (SBP) immediately after the Oracle
software installation. For more information, see SAP Note 1915316 . Otherwise you might have problems
during the Create Database phase of the database instance installation.
End of 'Platform': AIX
Procedure
1. Download the required patches.
2. Log on as the Oracle database software owner, that is the oracle user.
3. Install the SBP into the new Oracle home according to the instructions in the SBP README file.
Note
The installation of the SBP consists of these steps:
1. The installation of the SBP software into the Oracle home.
This step must be completed before the database is upgraded.
2. The change of the database structure and database properties (dictionary, parameter, and
properties)
This step must be done immediately after the database has been upgraded. For more information,
see Performing SAP Bundle Patch Post-Installation Steps.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Installation
PUBLIC
149
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 and higher only:
You can skip some of these post-installation steps if you have already completed them as a step in task list
SAP_BASIS_SETUP_INITIAL_CONFIG when running the ABAP task manager for lifecycle management
automation (transaction STC01) immediately after the installation was completed. For more information,
see SAP NetWeaver 7.4 and Higher: Performing Automated Initial Setup (Optional) [page 153].
The sections describing these steps are marked with a corresponding note at the beginning.
● 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. If required, you perform a full installation backup [page 182] 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 installer.
For more information, see Creating Operating System Users and Groups [page 80].
3. You check whether you can log on to the Application Server ABAP [page 152].
4. SAP systems based on SAP NetWeaver 7.4 and higher only: You perform the automated initial setup
[page 153].
Note
This step is optional.
5. You install the SAP license [page 154].
150
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
6. If you have installed a high-availability system, you set up the licenses for high availability [page 156].
7. You configure the remote connection to SAP support [page 157].
8. You install the SAP online documentation [page 158].
9. You perform the consistency check [page 158].
10. You configure the Transport Management System [page 160].
11. For production systems it is highly recommended that you connect the system to SAP Solution Manager
[page 162].
12. You apply the latest kernel and Support Packages [page 164].
13. You perform post-installation steps for the application server ABAP [page 165].
14. If you installed the ABAP part of an SAP Solution Manager 7.2 or SAP Process Integration 7.5 system,
enable HTTPS communication with the Java part of the system.
For more information, see SAP Solution Manager 7.2, SAP Process Integration 7.5 only: Enabling HTTPS
Communication for ABAP [page 168].
15. If required, you install additional languages and perform language transport [page 169].
16. SAP Kernel Release 7.4 and Higher: You perform IP Multicast Configuration [page 171].
17. You configure the Process Integration system after installation [page 171].
Note
This post-installation step is only relevant if you have installed an SAP NetWeaver 7.5 Process
Integration (PI) system.
18. You configure the user management [page 172].
19. You ensure user security [page 173].
20.You perform the client copy [page 177].
21. On the database instance host, you perform Oracle-specific post-installation steps [page 179].
22. If you have chosen to enable Oracle Database Vault, make sure that you perform the required configuration
steps. For more information, see Implementing Oracle Database Vault with the Installer [page 208].
23. SAP systems based on SAP NetWeaver 7.4 and higher only: If required, you change the keys for the
secure storage [page 181].
24. You perform a full installation backup [page 182].
25. If you chose to install an integrated SAP Web Dispatcher within the ASCS instance, you log on to the SAP
Web Dispatcher Management Console [page 185]
26. If you chose to install an integrated SAP Web Dispatcher within the ASCS instance, you configure the SAP
Web Dispatcher [page 187]
27. If you chose to install an integrated Gateway within the ASCS instance, you configure the SAP Gateway
[page 188].
28. You check the Master Guide for your SAP Business Suite application or SAP NetWeaver application
(chapter Configuration of Systems and Follow-Up Activities) for further implementation and configuration
steps, such as language installation, monitoring, work processes, transports, SAP license, printers, system
logs, and connectivity to system landscape directory (SLD).
Additional Application Server Instance
1. If required, you perform an installation backup [page 182] immediately after the installation has finished.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
PUBLIC
151
2. You check and if necessary modify the settings for the operating system users for your SAP system if they
were created by the installer.
For more information, see Creating Operating System Users and Groups [page 80].
3. You check whether you can log on to the Application Server ABAP [page 152].
4. You install the SAP online documentation [page 158].
5. You ensure user security [page 173].
6. You perform a full installation backup [page 182].
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. For more
information, see SAP Note 1749142 .
Table 43:
User
User Name
Client
SAP system user
SAP*
000, 001, 066
DDIC
000, 001
You access the application server ABAP using SAP Logon.
152
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
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 configuration file (also called “up-to-date installation”), we
recommend that you proceed as follows:
1. Perform the complete installation and update process - that is the installation with Software
Provisioning Manager and the update with Software Update Manager.
2. Perform the automated initial setup.
By running first the update and then the automated initial setup, you can profit from latest features and
fixes in the initial setup configuration content.
Background: As of Software Logistics Toolset 1.0 SPS12, the installation procedure with Software
Provisioning Manager 1.0 SP07 and higher also includes basic configuration activities, such as initial basic
configuration of transport management, which are a prerequisite for the subsequent maintenance process.
In previous SP versions of Software Logistics Toolset 1.0, this prerequisite had to be fulfilled by running
automated initial setup before the update process.
● If you have not run the installation using a stack configuration file (also called “up-to-date installation”), we
recommend that you proceed as follows:
1. Run automated initial setup directly after the installation, using the automation content provided with
the system load.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
PUBLIC
153
2. Apply the Support Packages to benefit from the already performed initial configuration – for example,
using the already configured Transport Management System.
3. Consider running the automated initial setup a second time, especially if you want to benefit from the
latest improvements and fixes offered by the updated automation content provided by the applied
Support Package.
For more information about automated initial setup, see the SAP Community Network at https://
wiki.scn.sap.com/wiki/display/SL/Automated+Initial+Setup+of+ABAP-Based+Systems .
Procedure
1. Start the ABAP Task Manager by calling transaction STC01.
2. Choose task list SAP_BASIS_SETUP_INITIAL_CONFIG.
3. Select the tasks you want to get executed.
For this, the task list offers sophisticated online documentation of the comprised activities.
4. Choose Execute.
You are guided through the configuration steps where you can enter the required values.
Related Information
Installation Using a Stack Configuration File [page 36]
Installing the SAP License [page 154]
Configuring the Remote Connection to SAP Support [page 157]
Configuring the Change and Transport System [page 160]
Applying the Latest Kernel and Support Package Stacks [page 164]
Performing Post-Installation Steps for the ABAP Application Server [page 165]
Performing the Consistency Check [page 158]
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 skip this task if you have already completed it as a step in task list
SAP_BASIS_SETUP_INITIAL_CONFIG when running the ABAP task manager for lifecycle management
automation (transaction STC01) immediately after the installation was completed. For more information,
see SAP NetWeaver 7.4 and Higher: Performing Automated Initial Setup (Optional) [page 153].
154
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
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 156].
Table 44:
SAP Release and SAP Library Quick Link
SAP Library Path (Continued)
○
SAP NetWeaver 7.1 for Banking Services from SAP See the SAP NetWeaver Mobile Library
5.0 and 6.0
○
SAP NetWeaver 7.1 including Enhancement Pack­
age 1 for Banking Services from SAP 5.0 and 6.0
Note
Since the SAP NetWeaver Mobile 7.1 Library is the only availa­
ble SAP Library for ABAP systems based on SAP NetWeaver
7.1, in this guide we always refer to it also for SAP NetWeaver 7.1
for Banking Services from SAP 5.0 and 6.0.
○
SAP NetWeaver Mobile 7.1
http://help.sap.com/nwmobile71
○
SAP NetWeaver Mobile 7.1 including Enhancement
Package 1
Application Help
Library
SAP Library
Administrator’s Guide
Configuration Tasks
SAP NetWeaver Mobile
Configuration
General
License Configuration
http://help.sap.com/nwmobile711
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
PUBLIC
155
SAP Release and SAP Library Quick Link
○
SAP NetWeaver 7.3
http://help.sap.com/nw73
○
SAP NetWeaver 7.3 including Enhancement Pack­
SAP Library Path (Continued)
Application Help
Function-Oriented View: English
Life Cycle Management
Solution
SAP Licenses
age 1
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
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 154] 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.
156
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
Procedure
1. To find the hardware ID of the primary host, log on to any application server instance of the SAP system
and call transaction SLICENSE.
2. Perform a switchover of the ABAP central services instance (ASCS) to another node in the cluster and
repeat the previous step.
Repeat this for all remaining nodes in the cluster.
3. To obtain the two license keys, enter the hardware IDs for each cluster node, where message server is
enabled to run: http://support.sap.com/licensekey
4. To import the files containing the two licenses, log on to any application server instance of the SAP system
and call transaction SLICENSE.
5. Perform a switchover of the ABAP central services instance (ASCS) to another node in the cluster and
repeat the previous step.
Repeat this for all remaining nodes in the cluster.
Results
The license is no longer a problem during switchover. This means you do not need to call saplicense in your
switchover scripts.
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 skip this task if you have already completed it as a step in task list
SAP_BASIS_SETUP_INITIAL_CONFIG when running the ABAP task manager for lifecycle management
automation (transaction STC01) immediately after the installation was completed. For more information,
see SAP NetWeaver 7.4 and Higher: Performing Automated Initial Setup (Optional) [page 153].
For more information, see SAP Support Portal at https://support.sap.com/remote-support.html
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
.
PUBLIC
157
6.7
Installing SAP Online Documentation
You can install SAP online documentation as application help.
Context
SAP currently provides an HTML-based solution for the online documentation, including the Application Help,
Glossary, Implementation Guide (IMG), and Release Notes. You can display the documentation with a Javacompatible Web browser on all front-end platforms supported by SAP.
Procedure
Install the application help in your SAP system as described in the README.TXT file contained in the root
directory of the application help media.
Online documentation media are delivered as part of the installation package. You can also download them
from https://launchpad.support.sap.com/#/softwarecenter
<Product>
<Product Version>
Installations & Upgrades
By Category
APPLICATION HELP (SAP LIBRARY) .
https://launchpad.support.sap.com/#/softwarecenter
NETWEAVER AND COMPLEMENTARY PRODUCTS
Installations & Upgrades
SAP NETWEAVER
By Category
SAP NETWEAVER 7.5
SAP
APPLICATION
HELP (SAP LIBRARY)
6.8
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 skip this task if you have already completed it as a step in task list
SAP_BASIS_SETUP_INITIAL_CONFIG when running the ABAP task manager for lifecycle management
automation (transaction STC01) immediately after the installation was completed. For more information,
see SAP NetWeaver 7.4 and Higher: Performing Automated Initial Setup (Optional) [page 153].
158
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
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 218].
● You have logged on to the SAP system [page 152].
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 enqueue server and the update service
Procedure
1. Perform a system check:
Call transaction SICK.
You should see the entry SAP System Check | no errors reported
2. Perform a database check:
In the DBA Cockpit (transaction DBACOCKPIT), check for missing tables or indexes by choosing
Diagnostics
Missing Tables and Indexes .
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
PUBLIC
159
6.9
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
You can skip this task if one of the following is true:
● Only valid for SAP systems based on SAP NetWeaver 7.4 and higher: You already completed these
steps as part of task list SAP_BASIS_SETUP_INITIAL_CONFIG have to perform these steps or at least
some of these steps when running the ABAP task manager for lifecycle management automation
(transaction STC01) immediately after the installation had completed.
Note that SAP_BASIS_SETUP_INITIAL_CONFIG only covers the configuration of TMS as single
system.
● You are using a stack configuration file (see Installation Using a Stack Configuration File (Optional)
[page 36]) and chose Run TMS Configuration (for Single System) during the installation.
Context
Procedure
1. Call transaction STMS in the ABAP system to configure the domain controller in the Transport Management
System (TMS).
For more information, see the SAP Library at:
Table 45:
SAP Release and SAP Library Quick Link
○
SAP Library Path (Continued)
SAP NetWeaver 7.1 for Banking Services from SAP
See the SAP NetWeaver Mobile Library
5.0 and 6.0
○
SAP NetWeaver 7.1 including Enhancement Package 1
for Banking Services from SAP 5.0 and 6.0
160
PUBLIC
Note
Since the SAP NetWeaver Mobile 7.1 Library is the only
available SAP Library for ABAP systems based on SAP
NetWeaver 7.1, in this guide we always refer to it also
for SAP NetWeaver 7.1 for Banking Services from SAP
5.0 and 6.0.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
SAP Release and SAP Library Quick Link
○
SAP NetWeaver Mobile 7.1
http://help.sap.com/nwmobile71
○
SAP Library Path (Continued)
SAP NetWeaver Mobile 7.1 including Enhancement
Application Help
Function-Oriented View: English
Application Server ABAP / ABAP Technology
Package 1
Administration Tools for AS ABAP
http://help.sap.com/nwmobile711
System
Change and Transport
Transport Management System (BC-CTS-TMS)
Configuring TMS
○
SAP NetWeaver 7.3
http://help.sap.com/nw73
○
○
SAP NetWeaver 7.3 including Enhancement Package
Application Help
Function-Oriented View: English
Solution Life Cycle Management
1
Change and Transport System
http://help.sap.com/nw731
System – Overview
SAP NetWeaver 7.4
System
Software Logistics
Change and Transport
Basics of the Change and Transport
Transport Management System – Concept
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
2. In addition, you must configure the system change options.
For more information, see the SAP Library at:
Table 46:
SAP Release and SAP Library Quick Link
○
SAP NetWeaver 7.1 for Banking Services from SAP
SAP Library Path (Continued)
See the SAP NetWeaver Mobile Library
5.0 and 6.0
○
Note
SAP NetWeaver 7.1 including Enhancement Package 1
for Banking Services from SAP 5.0 and 6.0
Since the SAP NetWeaver Mobile 7.1 Library is the only
available SAP Library for ABAP systems based on SAP
NetWeaver 7.1, in this guide we always refer to it also
for SAP NetWeaver 7.1 for Banking Services from SAP
5.0 and 6.0.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
PUBLIC
161
SAP Release and SAP Library Quick Link
○
SAP Library Path (Continued)
SAP NetWeaver Mobile 7.1
Application Help
http://help.sap.com/nwmobile71
○
SAP NetWeaver Mobile 7.1 including Enhancement
Function-Oriented View: English
Application Server ABAP / ABAP Technology
Package 1
Administration Tools for AS ABAP
http://help.sap.com/nwmobile711
System
Change and Transport
Transport Organizer (BC-CTS-ORG)
Requirements for Working with the Transport Organizer
Setting the System Change Option
○
SAP NetWeaver 7.3
Application Help
http://help.sap.com/nw73
○
○
SAP NetWeaver 7.3 including Enhancement Package
Function-Oriented View: English
Solution Life Cycle Management
1
Change and Transport System
http://help.sap.com/nw731
CTS-ORG)
SAP NetWeaver 7.4
Organizer
Software Logistics
Transport Organizer (BC-
Requirements for Working with the Transport
Setting the System Change Option
http://help.sap.com/nw74
○
SAP NetWeaver 7.5
○
SAP NetWeaver Application Server for ABAP 7.51
http://help.sap.com/nw75
innovation package
https://help.sap.com/nw751abap
○
SAP NetWeaver AS for ABAP 7.52
https://help.sap.com/nw752abap
3. Call transaction SE38 to schedule a dispatcher job for transport programs by executing report RDDIMPDP.
You schedule the transport dispatcher in the current client. This is equivalent to the execution of job
RDDNEWPP in transaction SE38
6.10 Connecting the System to SAP Solution Manager
Here you find information about how to connect your newly installed SAP system to SAP Solution Manager.
Prerequisites
An SAP Solution Manager system must be available in your system landscape. For more information, see
http://help.sap.com/solutionmanager .
162
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
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.1:
http://help.sap.com/solutionmanager
Solution Manager Operations
System Information
Version 7.1 SPS <No>
Application Help (English)
Managing System Landscape Information
SAP
Managing Technical
Register Technical Systems Automatically by Data Suppliers
○ If your SAP Solution Manager release is 7.2:
http://help.sap.com/solutionmanager
Technical Infrastructures
Information
Version 7.2 SPS <No>
Application Help (English)
Landscape Management Database (LMDB)
Managing Technical System
Registering Technical Systems Automatically by Data Suppliers
2. The data suppliers send information about the hardware and installed software to a central System
Landscape Directory (SLD). Updates are sent to the SLD as well.
For more information, see the Planning Guide - System Landscape Directory in the SAP Community
Network at System Landscape Directory (SLD) - Overview
3. From the SLD, this information is regularly synchronized with SAP Solution Manager where it is managed
in the Landscape Management Database (LMDB).
For more information, see the SAP Solution Manager Application Help:
○ If your SAP Solution Manager release is 7.1:
http://help.sap.com/solutionmanager
Solution Manager Operations
Management Infrastructure
Version 7.1 SPS <No>
Application Help (English)
Managing System Landscape Information
SAP
Setting Up the Landscape
Connecting LMDB to System Landscape Directory (SLD)
○ If your SAP Solution Manager release is 7.2:
http://help.sap.com/solutionmanager
Technical Infrastructures
Version 7.2 SPS <No>
Landscape Management Database (LMDB)
Management Infrastructure
Application Help (English)
Setting Up the Landscape
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:
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
PUBLIC
163
○ If your SAP Solution Manager release is 7.1:
Managing Technical System Information and Managing Product System Information at http://
help.sap.com/solutionmanager
Solution Manager Operations
Version 7.1 SPS <No>
Application Help (English)
SAP
Managing System Landscape Information
○ If your SAP Solution Manager release is 7.2:
http://help.sap.com/solutionmanager
Technical Infrastructures
Version 7.2 SPS <No>
Application Help (English)
Landscape Management Database (LMDB)
Managing Technical System
Information
Next Steps
For more information, see the following pages in the SAP Community Network:
● System Landscape Directory (SLD) - Overview
● Documentation for Landscape Management Database - LMDB
6.11
Applying the Latest Kernel and Support Package
Stacks
We strongly recommend that you apply the latest kernel and Support Package stacks before you start
configuring your SAP system.
Note
If you are using a stack configuration file (see Installation Using a Stack Configuration File (Optional) [page
36]), you already downloaded the stack.xml file and the delta archives using the Maintenance Optimizer in
your SAP Solution Manager. If you then already called the Software Update Manager (SUM) from the
installer and applied the Support Package Stacks after the installation had finished, you can skip this
section.
Context
For more information about release and roadmap information for the kernel versions and how this relates to
SAP NetWeaver support packages, including important notes on downward compatibility and release dates,
see the document Understanding Kernel Releases for the SAP NetWeaver AS ABAP at http://scn.sap.com/
docs/DOC-54170 .
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.
164
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
Procedure
● Download and apply the latest Kernel and Support Package stacks using the Software Update Manager
(SUM) as described in the documentation Updating SAP Systems Using Software Update Manager
<Release> available at https://support.sap.com/sltoolset
Manager (SUM) scenarios
System Maintenance
Software Update
Software Update/Upgrade with SUM <Release>
● 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.12 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 skip this task if you have already completed it as a step in task list
SAP_BASIS_SETUP_INITIAL_CONFIG when running the ABAP task manager for lifecycle management
automation (transaction STC01) immediately after the installation was completed. For more information,
see SAP NetWeaver 7.4 and Higher: Performing Automated Initial Setup (Optional) [page 153].
Prerequisites
You have logged on to the ABAP application server as described in Logging On to the Application Server [page
152].
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
PUBLIC
165
Context
You have to perform the following post-installation steps for the ABAP application server:
● Upload and set system profiles using transaction RZ10
● 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:
Table 47:
SAP Release and SAP Library Quick Link
○
SAP Library Path (Continued)
SAP NetWeaver 7.1 for Banking Services from SAP
See the SAP NetWeaver Mobile Library
5.0 and 6.0
○
SAP NetWeaver 7.1 including Enhancement Package 1
for Banking Services from SAP 5.0 and 6.0
Note
Since the SAP NetWeaver Mobile 7.1 Library is the only
available SAP Library for ABAP systems based on SAP
NetWeaver 7.1, in this guide we always refer to it also
for SAP NetWeaver 7.1 for Banking Services from SAP
5.0 and 6.0.
○
SAP NetWeaver Mobile 7.1
Application Help
http://help.sap.com/nwmobile71
○
166
SAP NetWeaver Mobile 7.1 including Enhancement
Function-Oriented View: English
Application Server ABAP / ABAP Technology
Package 1
Administration Tools for AS ABAP
http://help.sap.com/nwmobile711
CCMS
PUBLIC
Profiles
Configuration in the
Maintaining Profiles
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
SAP Release and SAP Library Quick Link
○
SAP NetWeaver 7.3
http://help.sap.com/nw73
○
○
SAP NetWeaver 7.3 including Enhancement Package
Application Help
Application Server
Function-Oriented View: English
Application Server ABAP
1
Administration of Application Server ABAP
http://help.sap.com/nw731
and Administration Tools for Application Server ABAP
SAP NetWeaver 7.4
Configuration in the CCMS
http://help.sap.com/nw74
○
SAP Library Path (Continued)
Profiles
Monitoring
Maintaining
Profiles / Profile Maintenance
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
● Create Logon and RFC Server Groups using Transactions SMLG and RZ12
You create the following:
○ Logon groups using transaction SMLG
○ RFC server groups using transaction RZ12
Specify the following:
○ Name of the logon or RFC server group
○ Instance name (application server)
○ Group type attributes are optional
If required, you create the RFC server group parallel_generators.
● Create Operation Modes using Transaction RZ04
You check for existing operation modes and - if required - create a new operation mode using transaction
RZ04.
Specify the following:
○ Name of the operation mode
○ Short description
○ Optional: monitoring properties variant
Select the corresponding checkbox to assign the operation mode to the following:
○ Time table (assignment only from 0-24 h)
○ Current application server instance
● 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.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
PUBLIC
167
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 162]
● Perform Load Generation using Transaction SGEN
You generate the ABAP loads using transaction SGEN. ABAP loads are platform-dependent programs that
are generated during runtime and stored in database tables. Using transaction SGEN you can generate
ABAP loads of a number of programs, function groups, classes, and so on.
Choose one of the following generation modes:
○ Generate All Objects
All existing objects of all software components are generated synchronously. Job RSPARGENER8M
starts the generation directly after all ABAP objects have been prepared for generation and have been
stored in table GENSETC. Be aware that this is a time-consuming process.
Note
Make sure that you have sufficient space available on your database. The generation of all existing
objects requires around 2 - 9 GB of free space.
○ Prepare All Objects for Generation
All objects to be generated are prepared for generation and stored in table GENSETM. You can start the
generation of these objects later with transaction SGEN. Choose this strategy if object generation is to
be done outside the configuration task due to performance issues.
6.13 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.
168
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
Procedure
Proceed as described in the SAP Notes 1527879
and 510007
.
Related Information
Additional Parameters when Installing SAP Process Integration 7.5 or SAP Solution Manager 7.2 [page 68]
6.14 Installing Additional Languages and Performing
Language Transport
This section describes how to install and transport additional languages.
Note
You do not have to perform these steps or at least some of these steps if you are using a stack configuration
file (see Installation Using a Stack Configuration File (Optional) [page 36]) and processed the Install
Additional Languages screen during the installation.
Context
If you have problems during the language installation, see SAP Note 2456868
.
Procedure
1. Configure the language settings by using transaction I18N and choosing
System Configuration
I18N Customizing
I18N
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.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
PUBLIC
169
a. Classify the language.
b. Schedule the language transport.
c. Schedule the language supplementation.
Next Steps
Note
You can also install additional languages later, but if you install any Support Packages in the meantime, you
have to do one of the following:
● Install the Support Packages again.
● Use the report RSTLAN_IMPORT_OCS to extract the language-relevant information from each Support
Package.
For information about the language transport, see the SAP Library at:
Table 48:
SAP Release and SAP Library Quick Link
●
SAP Library Path (Continued)
SAP NetWeaver 7.1 for Banking Services from SAP 5.0
See the SAP NetWeaver Mobile Library
and 6.0
●
SAP NetWeaver 7.1 including Enhancement Package 1
for Banking Services from SAP 5.0 and 6.0
Note
Since the SAP NetWeaver Mobile 7.1 Library is the only
available SAP Library for ABAP systems based on SAP
NetWeaver 7.1, in this guide we always refer to it also for
SAP NetWeaver 7.1 for Banking Services from SAP 5.0
and 6.0.
●
SAP NetWeaver Mobile 7.1
http://help.sap.com/nwmobile71
●
SAP NetWeaver Mobile 7.1 including Enhancement
Package 1
http://help.sap.com/nwmobile711
170
PUBLIC
Application Help
Function-Oriented View: English
Application Server ABAP / ABAP Technology
Administration Tools for AS ABAP
System
Change and Transport
Language Transport (BC-CTS-LAN)
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
SAP Release and SAP Library Quick Link
●
SAP NetWeaver 7.3
http://help.sap.com/nw73
●
SAP NetWeaver 7.3 including Enhancement Package 1
http://help.sap.com/nw731
●
SAP NetWeaver 7.4
SAP Library Path (Continued)
Application Help
Function-Oriented View: English
Solution Life Cycle Management
Change and Transport System
Software Logistics
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.15 SAP Kernel 7.40 and Higher: IP Multicast Configuration
and Wake-Up Mechanism
Since SAP kernel release 7.40, the ABAP application server (AS ABAP) uses IP multicast datagrams with host
local scope to wake up the internal processes (such as dispatcher, Gateway, internet communication manager,
work processes) when dispatching requests.
Since SAP kernel release 7.40 Patch Level (PL) 46 and 7.41 PL 13, the dispatcher checks during startup
whether local IP multicast communication is working properly. You have to adjust the network configuration of
AS ABAP as described in SAP Note1931675 .
Since SAP kernel 7.41 PL 47 and 7.42 PL 14, a new event-based wake-up mechanism is available that replaces
the multicast mechanism. SAP recommends using this new mechanism in case of problems with multicast. For
details on activating the new mechanism see SAP Note 2050408
to ensure that local IP multicast
communication works properly.
6.16 PI 7.5 Only: Configuring the Process Integration System
After the Installation
To configure your SAP Process Integration 7.5 (SAP PI 7.5) system after installation, execute the Central
Technical Configuration (CTC) Wizard.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
PUBLIC
171
Prerequisites
If you have installed an SAP PI 7.5 system and you intend to run automated configuration using the Central
Technical Configuration (CTC) Wizard after the installation, make sure that the ABAP communication port is
either completely configured for HTTPS or optionally for HTTP, for example by configuring the ABAP
communication port during the installation process (see the Ports table in section SAP System Parameters
[page 56]). You can only run the CTC Wizard if the ABAP communication port is configured.
Procedure
To configure your SAP PI 7.5 system, execute the “SAP NetWeaver initial setup” CTC Wizard described in SAP
Note 1309239 .
Note
The CTC Wizard automatically executes all required technical configuration steps.
For more details about all single configuration steps executed by the CTC Wizard and how to apply them
manually, see the SAP Library at:
Table 49:
SAP Release and SAP Library Quick Link
SAP Library Path (Continued)
Application Help
SAP NetWeaver 7.5
English
http://help.sap.com/nw75
Function-Oriented View:
Process Integration
Configuring
Process Integration After Installation
Configuring Process Integration (PI) Dual Usage
Type
Basic Configuration for SAP Process
Integration (PI)
6.17 Configuring the User Management
After the installation has completed, configure the user management of your SAP system.
Procedure
After the installation of your SAP system has finished, you must decide whether you want to do the following:
○ Add the system to Central User Administration (CUA)
172
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
○ Use Lightweight Directory Access Protocol (LDAP) synchronization
For more information, see the SAP Library at:
Table 50:
SAP Release and SAP Library Quick Link
○
SAP NetWeaver 7.1 for Banking Services from
SAP Library Path (Continued)
See the SAP NetWeaver Mobile Library
SAP 5.0 and 6.0
○
Package 1 for Banking Services from SAP 5.0
and 6.0
○
SAP NetWeaver Mobile 7.1
https://help.sap.com/nwmobile71
○
SAP NetWeaver Mobile 7.1 including Enhance­
ment Package 1
https://help.sap.com/nwmobile711
○
SAP NetWeaver 7.3
https://help.sap.com/nw73/
○
SAP NetWeaver 7.3 including Enhancement
Package 1
https://help.sap.com/nw731
○
Note
SAP NetWeaver 7.1 including Enhancement
Since the SAP NetWeaver Mobile 7.1 Library is the only available
SAP Library for ABAP systems based on SAP NetWeaver 7.1, in this
guide we always refer to it also for SAP NetWeaver 7.1 for Banking
Services from SAP 5.0 and 6.0.
Application Help
Identity Management
Function-Oriented View: English
Security
Identity Management for System Landscapes
Integration of User Management in Your System Landscape
Adding an ABAP System to Your System Landscape
Application Help
Identity Management
Function-Oriented View: English
Security
Identity Management for System Landscapes
Integration of User Management in Your System Landscape
Adding an ABAP System to Your System Landscape
SAP NetWeaver 7.4
https://help.sap.com/nw74
○
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 installer created during the installation.
The tables below at the end of this section list the following users:
● Operating system users
● SAP system users
During the installation, the installer by default assigned the master password to all users created during the
installation unless you specified other passwords.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
PUBLIC
173
Recommendation
In all cases, the user ID and password are encoded only when transported across the network. Therefore, we
recommend using encryption at the network layer, either by using the Secure Sockets Layer (SSL) protocol
for HTTP connections, or Secure Network Communications (SNC) for the SAP protocols dialog and RFC.
Caution
Make sure that you perform this procedure before the newly installed SAP system goes into production.
For the users listed below, take the precautions described in the relevant SAP security guide.
You can find the security guide in the Security section of the product page for your SAP product at https://
help.sap.com/
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 installer had completed. For more information, see Operating System Users in SAP System
Parameters [page 56].
Table 51: Operating System and Database Users
User
User Name
Comment
Operating system user
<sapsid>adm
SAP system administrator
Oracle 12: This is also the default
Oracle database administrator
oracle
Oracle database administrator and
Oracle software owner (that is, the
owner of the database files)
This user is only available with Oracle
12 or Oracle 11 with ASM/Exadata.
174
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
User
User Name
Comment
Oracle 11: This is the default Oracle da­
ora<dbsid>
tabase administrator
Oracle 12: This is the additional Oracle
database administrator (that is, the
owner of the database files)
Oracle database user
Oracle database owner (that is, the
SAP<SCHEMA_ID>
owner of the database tables)
SYSTEM
Oracle standard database user
SYS
Oracle standard database user
OUTLN
Oracle standard database user
DBSNMP
Oracle standard database user
Table 52: 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. For more
information, see SAP Note 1749142 .
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
PUBLIC
175
Table 53: SAP System Users
User
User Name
Comment
SAP system user
SAP*
User exists in at least SAP system clients 000, 001,
and 066.
User exists in at least SAP system clients 000 and
DDIC
001.
EARLYWATCH
User exists in at least SAP system client 066.
Application Server Java Admin­
The name that you gave this user
This user exists in at least clients 000 and 001 of the
istrator
during the installation or the de­
ABAP system and in the User Management Engine
fault name J2EE_ADMIN (see
(UME) of the Java system. It has administrative per­
SAP System Parameters [page
missions for user management.
Note
This user has only been cre­
56])
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
Recommendation
Solution Manager 7.2 system.
We recommend that you use strong password
and auditing policies for this user.
Application Server Java Guest
Note
This user has only been cre­
ated if you have installed the
The name that you gave this user
This user exists in at least clients 000 and 001 of the
during the installation or the de­
ABAP system and in the User Management Engine
fault name J2EE_GUEST (see
(UME) of the Java system. It is used for anonymous
SAP System Parameters [page
access.
56])
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
cation Server Java
during the installation or the de­
ABAP system and in the User Management Engine
fault name SAPJSF (see SAP
(UME) of the Java system. It is used for a remote
System Parameters [page 56])
function call (RFC) between the ABAP system and
Note
This user has only been cre­
This user exists in at least clients 000 and 001 of the
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.
176
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
6.19 Performing the Client Copy
To get a production client, you have to perform a copy of the SAP reference client.
Context
The installer creates three ABAP clients during the installation, client 000, client 001, and client 066.
Note
Client 066 is no longer available in newly installed SAP systems based on SAP NetWeaver 7.5. 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.1 to
7.5x on UNIX : Oracle
Post-Installation
PUBLIC
177
Next Steps
For more information about the client copy and about how to perform it, see the SAP Library at :
Table 54:
SAP Release and SAP Library Quick Link
●
SAP Library Path (Continued)
SAP NetWeaver 7.1 for Banking Services from SAP 5.0
See the SAP NetWeaver Mobile Library
and 6.0
●
SAP NetWeaver 7.1 including Enhancement Package 1
for Banking Services from SAP 5.0 and 6.0
Note
Since the SAP NetWeaver Mobile 7.1 Library is the only
available SAP Library for ABAP systems based on SAP
NetWeaver 7.1, in this guide we always refer to it also for
SAP NetWeaver 7.1 for Banking Services from SAP 5.0
and 6.0.
●
SAP NetWeaver Mobile 7.1
Application Help
http://help.sap.com/nwmobile71
●
Application Server ABAP / ABAP Technology
SAP NetWeaver Mobile 7.1 including Enhancement
Administration Tools for AS ABAP
Package 1
System
http://help.sap.com/nwmobile711
●
SAP NetWeaver 7.3
SAP NetWeaver 7.3 including Enhancement Package 1
http://help.sap.com/nw731
●
SAP NetWeaver 7.4
Change and Transport
BC – Client Copy and Transport
Application Help
http://help.sap.com/nw73
●
Function-Oriented View: English
Application Server
Function-Oriented View: English
Application Server ABAP
Administration of Application Server ABAP
Transport System
Change and
BC – Client Copy and Transport
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
178
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
6.20 Performing Oracle-Specific Post-Installation Steps
You have to perform the following Oracle-specific post-installation steps.
Procedure
● Checking the Recommended Oracle Database Parameters
When installing the Oracle database, a standard database parameter set is used. To take into account the
size and configuration of your SAP system, and to enable new Oracle features, check and apply the
parameter settings as described in SAP Note 1431798
(Oracle 11g) or SAP Note 1888485
(Oracle
12c).
You can find an automated script in SAP Note 1171650
to help you check whether your SAP system
complies with the database parameter recommendations at any given point in time.
● Configuring Database User Profiles
If the SAP-specific database user profile SAPUPROF is not yet installed in the database, configure it as
described in SAP Note 1519872
.
● Updating Oracle Optimizer Statistics
To update the Oracle optimizer statistics, do the following:
a. Execute the following commands as the ora<dbsid> user:
brconnect -u / -c -f stats -t system_stats;
brconnect -u / -c -f stats -t oradict_stats;
b. Execute the following commands with SQLPlus:
SQL> exec dbms_scheduler.disable('GATHER_STATS_JOB');
SQL> exec dbms_scheduler.disable('ORACLE_OCM.MGMT_CONFIG_JOB');
SQL> exec dbms_scheduler.disable('ORACLE_OCM.MGMT_STATS_CONFIG_JOB');
For Oracle 11g, also execute the following command:
SQL> exec DBMS_AUTO_TASK_ADMIN.DISABLE
For more information, see SAP Note 974781
.
● Checking the Version of the Oracle Instant Client
If necessary, install the most up-to-date version of the Oracle Instant Client, as described in SAP Note
819829 .
● Configuring and Administering the Oracle Database
Configuring and Administering the Oracle Database
You have to configure your Oracle database before you start operating it with the SAP system.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
PUBLIC
179
For more information about Oracle database configuration and administration, see the SAP Library at:
Table 55:
SAP Release and SAP Library Quick Link
○
SAP Library Path (Continued)
SAP NetWeaver 7.1 for Banking Services from
See the SAP NetWeaver Mobile Library
SAP 5.0 and 6.0
○
Note
SAP NetWeaver 7.1 including Enhancement
Package 1 for Banking Services from SAP 5.0
Since the SAP NetWeaver Mobile 7.1 Library is the only
and 6.0
available SAP Library for ABAP systems based on SAP
NetWeaver 7.1, in this guide we always refer to it also for
SAP NetWeaver 7.1 for Banking Services from SAP 5.0 and
6.0.
○
SAP NetWeaver Mobile 7.1
SAP Library
http://help.sap.com/nwmobile71
○
○
Administrator's Guide
SAP NetWeaver Mobile 7.1 including Enhance­
Technical Operations (TOM)
ment Package 1
Administration of Databases
http://help.sap.com/nwmobile711
Oracle
SAP NetWeaver 7.3
Application Help
http://help.sap.com/nw73
○
SAP NetWeaver Mobile Library
Function-Oriented View: English
Database Administration
SAP NetWeaver 7.3 including Enhancement
Database Administration for
Database Administration for
Oracle
Package 1
http://help.sap.com/nw731
○
SAP NetWeaver 7.4
http://help.sap.com/nw74
○
SAP NetWeaver 7.5
○
SAP NetWeaver Application Server for ABAP 7.51
http://help.sap.com/nw75
innovation package
https://help.sap.com/nw751abap
○
SAP NetWeaver AS for ABAP 7.52
https://help.sap.com/nw752abap
● Installing the Latest Version of BR*Tools for Oracle 12c
Follow the instructions in SAP Note 2087004
12c.
180
PUBLIC
to install the most recent version of BR*Tools for Oracle
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
6.21 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:
Table 56:
SAP Release and SAP Library Quick Link
○
SAP NetWeaver 7.4
http://help.sap.com/nw74
○
SAP NetWeaver 7.5
http://help.sap.com/nw75
○
SAP Library Path (Continued)
Application Help
System Security
Only
Function-Oriented View: English
Security
System Security for SAP NetWeaver AS ABAP
Secure Storage in the File System (AS ABAP)
SAP NetWeaver Application Server for
ABAP 7.51 innovation package
https://help.sap.com/nw751abap
○
SAP NetWeaver AS for ABAP 7.52
https://help.sap.com/nw752abap
● For the secure storage in the database, the key change is described in the SAP Library at:
Table 57:
SAP Release and SAP Library Quick Link
○
SAP NetWeaver 7.4
http://help.sap.com/nw74
○
○
SAP NetWeaver 7.5
SAP Library Path (Continued)
Application Help
System Security
Function-Oriented View: English
Security
System Security for SAP NetWeaver AS ABAP
Secure Storage (ABAP)
http://help.sap.com/nw75
Only
SAP NetWeaver Application Server for
Individual Encryption Keys
Key Management
Using
Generating Encryption Keys
ABAP 7.51 innovation package
https://help.sap.com/nw751abap
○
SAP NetWeaver AS for ABAP 7.52
https://help.sap.com/nw752abap
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
PUBLIC
181
More Information
See also the entry Individual Encryption Key for the Secure Storage in table SAP System Parameters in SAP
System Parameters [page 56].
6.22 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.
Caution
Make sure that you fully back up your database so that you can recover it later if necessary.
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.
Prerequisites
You have logged on as user <sapsid>adm and stopped the SAP system and database [page 218].
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.
182
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
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 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
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
PUBLIC
183
Performing a Full Database Backup
1. Configure your third-party backup tool, if used.
2. Perform a full database backup (preferably offline).
If you use BR*TOOLS for the backup, refer to BR*Tools for Oracle DBA in the documentation SAP Database
Guide: Oracle (BC-DB-ORA-DBA), available in the SAP Library at:
Table 58:
SAP Release and SAP Library Quick Link
○
SAP Library Path (Continued)
SAP NetWeaver 7.1 for Banking Services from SAP
See the SAP NetWeaver Mobile Library
5.0 and 6.0
○
SAP NetWeaver 7.1 including Enhancement Pack­
age 1 for Banking Services from SAP 5.0 and 6.0
Note
Since the SAP NetWeaver Mobile 7.1 Library is the only
available SAP Library for ABAP systems based on SAP
NetWeaver 7.1, in this guide we always refer to it also for
SAP NetWeaver 7.1 for Banking Services from SAP 5.0
and 6.0.
○
SAP NetWeaver Mobile 7.1
Application Help
http://help.sap.com/nwmobile71
○
○
SAP NetWeaver Mobile
Library
Administrator’s Guide
Package 1
(TOM)
Administration of Databases
http://help.sap.com/nwmobile711
Administration for Oracle
SAP NetWeaver Mobile 7.1 including Enhancement
SAP NetWeaver 7.3
Application Help
http://help.sap.com/nw73/
○
SAP Library
SAP NetWeaver 7.3 including Enhancement Pack­
Technical Operations
Database
Function-Oriented View: English
Database Administration
Database Administration for
Oracle
age 1
http://help.sap.com/nw731
○
SAP NetWeaver 7.4
http://help.sap.com/nw74
○
SAP NetWeaver 7.5
○
SAP NetWeaver Application Server for ABAP 7.51
http://help.sap.com/nw75
innovation package
https://help.sap.com/nw751abap
○
SAP NetWeaver AS for ABAP 7.52
https://help.sap.com/nw752abap
184
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
6.23 Logging on to the SAP Web Dispatcher Management
Console
This section describes how to log on to the SAP Web Dispatcher.
Context
Note
This step is only required if you chose to install an integrated SAP Web Dispatcher instance within the ASCS
instance.
You must log on to the SAP Web Dispatcher Management Console to do the following:
● Check whether the SAP Web Dispatcher was installed successfully,
● Change the password of the webadm user,
● Access monitoring and administration tools.
Procedure
1. Open a web browser.
2. Enter the following URL, depending on whether you use HTTP or HTTPS:
http(s)://<Webdispatcher_Host>:<HTTP(S)_PORT>/sap/wdisp/admin/public/
default.html
Example
https://plx282:44300/sap/wdisp/admin/public/default.html
3. Log on as user webadm with the password that you entered during the input phase of the installation.
The SAP Web Dispatcher Monitor screen appears.
4. We recommend that you change the password of webadm immediately after the installation for security
reasons.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
PUBLIC
185
For more information on how to change passwords of existing users using the Admin Handler, see the
SAP Library at:
Table 59:
SAP Release and SAP Library Quicklink
○
SAP Library Path (Continued)
SAP NetWeaver Mobile 7.1
Application Help
http://help.sap.com/nwmobile71
○
SAP NetWeaver Mobile 7.1 including Enhancement
Server Infrastructure
Function-Oriented View
Application
SAP Web Dispatcher
Package 1
Administration of the SAP Web Dispatcher
http://help.sap.com/nwmobile711
Administration Interface
Area menu
Using the Web
Section ”HTTP
Handler”
○
○
SAP NetWeaver 7.1 for Banking Services from SAP See the SAP NetWeaver Mobile Library.
5.0 and 6.0
SAP NetWeaver 7.1 including Enhancement Pack­
age 1 for Banking Services from SAP 5.0 and 6.0
○
SAP NetWeaver Process Integration 7.1
Since the SAP NetWeaver Mobile 7.1 Library is the only
available SAP Library for ABAP systems based on SAP
NetWeaver 7.1, in this guide we always refer to it also for
SAP NetWeaver 7.1 for Banking Services from SAP 5.0 and
6.0.
Application Help
http://help.sap.com/nwpi71
○
Note
SAP NetWeaver Process Integration 7.1 Including
Server Infrastructure
Function-Oriented View
Application
SAP Web Dispatcher
Enhancement Package 1
Administration of the SAP Web Dispatcher
http://help.sap.com/nwpi711
Administration Interface
Area menu
Using the Web
Section ”HTTP
Handler”
○
SAP NetWeaver 7.3
Application Help
http://help.sap.com/nw73
○
SAP NetWeaver 7.3 including Enhancement Pack­
Server
Function-Oriented View
Application Server Infrastructure
Application
Components of
SAP Web Dispatcher
age 1
SAP NetWeaver Application Server
http://help.sap.com/nw731
Administration of the SAP Web Dispatcher
Area menu
Section ”HTTP Handler”
○
SAP NetWeaver 7.4
Application Help
http://help.sap.com/nw74
○
○
Application Server Infrastructure
SAP NetWeaver Application Server
SAP NetWeaver Application Server for ABAP 7.51
Administration of the SAP Web Dispatcher
innovation package
Administration Interface
SAP NetWeaver AS for ABAP 7.52
Application
Components of
SAP Web Dispatcher
http://help.sap.com/nw75
https://help.sap.com/nw751abap
○
Server
SAP NetWeaver 7.5
Function-Oriented View
Area menu
Using the Web
Section ”HTTP
Handler”
https://help.sap.com/nw752abap
186
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
Related Information
ASCS Instance with Integrated SAP Web Dispatcher [page 29]
6.24 SAP Web Dispatcher Configuration (Optional)
After installing SAP Web Dispatcher, you must configure it to be able to use it.
Note
This step is only required if you chose to install an integrated SAP Web Dispatcher instance within the ASCS
instance.
You can find the configuration information in the SAP Library at:
Table 60:
SAP Release and SAP Library Quicklink
●
SAP NetWeaver Mobile 7.1
http://help.sap.com/nwmobile71
●
SAP NetWeaver Mobile 7.1 including Enhancement
Package 1
SAP Library Path (Continued)
Application Help
Server Infrastructure
Application Server
Function-Oriented View
Application
Components of SAP NetWeaver
SAP Web Dispatcher
http://help.sap.com/nwmobile711
●
SAP NetWeaver 7.1 for Banking Services from SAP
See the SAP NetWeaver Mobile Library.
5.0 and 6.0
●
SAP NetWeaver 7.1 including Enhancement Package
1 for Banking Services from SAP 5.0 and 6.0
●
SAP NetWeaver Process Integration 7.1
http://help.sap.com/nwpi71
●
SAP NetWeaver Process Integration 7.1 Including En­
Note
Since the SAP NetWeaver Mobile 7.1 Library is the only avail­
able SAP Library for ABAP systems based on SAP
NetWeaver 7.1, in this guide we always refer to it also for SAP
NetWeaver 7.1 for Banking Services from SAP 5.0 and 6.0.
Application Help
Server Infrastructure
Function-Oriented View
Application
SAP Web Dispatcher
hancement Package 1
http://help.sap.com/nwpi711
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
PUBLIC
187
SAP Release and SAP Library Quicklink
●
SAP Library Path (Continued)
SAP NetWeaver 7.3
Application Help
http://help.sap.com/nw73
●
SAP NetWeaver 7.3 including Enhancement Package
1
Server Infrastructure
Application Server
Function-Oriented View
Application
Components of SAP NetWeaver
SAP Web Dispatcher
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
Related Information
ASCS Instance with Integrated SAP Web Dispatcher [page 29]
6.25 Gateway Configuration (Optional)
You have to configure the gateway to be able to use it.
Note
This step is only relevant if you installed a gateway integrated in the ASCS instance. For more information,
see ASCS Instance with Integrated Gateway [page 31].
You can find all relevant configuration information in the gateway documentation in the SAP Library at:
Table 61:
SAP Release and SAP Library Quicklink
●
SAP NetWeaver Mobile 7.1
http://help.sap.com/nwmobile71
●
SAP NetWeaver Mobile 7.1 including Enhancement
SAP Library Path (Continued)
Application Help
Server Infrastructure
Function-Oriented View
Connectivity
Application
SAP Gateway
Package 1
http://help.sap.com/nwmobile711
188
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
SAP Release and SAP Library Quicklink
●
SAP NetWeaver 7.1 for Banking Services from SAP
SAP Library Path (Continued)
See the SAP NetWeaver Mobile Library.
5.0 and 6.0
●
SAP NetWeaver 7.1 including Enhancement Package
1 for Banking Services from SAP 5.0 and 6.0
Note
Since the SAP NetWeaver Mobile 7.1 Library is the only avail­
able SAP Library for ABAP systems based on SAP
NetWeaver 7.1, in this guide we always refer to it also for SAP
NetWeaver 7.1 for Banking Services from SAP 5.0 and 6.0.
●
SAP NetWeaver Process Integration 7.1
http://help.sap.com/nwpi71
●
Application Help
Server Infrastructure
Function-Oriented View
Connectivity
Application
SAP Gateway
SAP NetWeaver Process Integration 7.1 Including En­
hancement Package 1
http://help.sap.com/nwpi711
●
SAP NetWeaver 7.3
http://help.sap.com/nw73
●
Application Help
Oriented View
SAP NetWeaver 7.3 including Enhancement Package Infrastructure
1
SAP NetWeaver Library: Function-
Application Server
Connectivity
Application Server
Gateway
http://help.sap.com/nw731
●
●
●
SAP NetWeaver 7.4
Application Help
SAP NetWeaver Library: Function-
http://help.sap.com/nw74
Oriented View
Application Server
SAP NetWeaver 7.5
Infrastructure
Components of SAP NetWeaver Application
http://help.sap.com/nw75
Server
Application Server
Gateway
SAP NetWeaver Application Server for ABAP 7.51
innovation package
https://help.sap.com/nw751abap
●
SAP NetWeaver AS for ABAP 7.52
https://help.sap.com/nw752abap
Related Information
ASCS Instance with Integrated Gateway [page 31]
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Post-Installation
PUBLIC
189
7
Additional Information
The following sections provide additional information about optional preparation, installation, and postinstallation 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.
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.
190
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
This section does not provide information about the use of LDAP directories with the LDAP Connector. For
more information about using and configuring the LDAP Connector for an ABAP system, see the SAP Library
at:
Table 62:
SAP Release and SAP Library Quick Link
●
SAP NetWeaver Mobile 7.1
http://help.sap.com/nwmobile71
●
SAP NetWeaver Mobile 7.1 including Enhancement
Package 1
●
SAP Library Path (Continued)
Application Help
Function-Oriented View
Identity Management
Server ABAP
Security
Identity Management of the Application
Configuration of User and Role Administration
http://help.sap.com/nwmobile711
Directory Services
LDAP Connector
SAP NetWeaver 7.1 for Banking Services from SAP
See the SAP NetWeaver Mobile Library.
5.0 and 6.0
●
SAP NetWeaver 7.1 including Enhancement Package
1 for Banking Services from SAP 5.0 and 6.0
●
SAP NetWeaver Process Integration 7.1
http://help.sap.com/nwpi71
●
SAP NetWeaver Process Integration 7.1 Including En­
hancement Package 1
http://help.sap.com/nwpi711
●
SAP NetWeaver 7.3
http://help.sap.com/nw73
●
SAP NetWeaver 7.3 including Enhancement Package
1
●
Note
Since the SAP NetWeaver Mobile 7.1 Library is the only avail­
able SAP Library for ABAP systems based on SAP
NetWeaver 7.1, in this guide we always refer to it also for SAP
NetWeaver 7.1 for Banking Services from SAP 5.0 and 6.0.
Application Help
Function-Oriented View
Identity Management
Server ABAP
Identity Management of the Application
Configuration of User and Role Administration
Directory Services
Application Help
Security
Security
LDAP Connector
Function-Oriented View: English
Identity Management
User and Role
Administration of Application Server ABAP
http://help.sap.com/nw731
User and Role Administration
SAP NetWeaver 7.4
Connector
Configuration of
Directory Services
LDAP
http://help.sap.com/nw74
●
SAP NetWeaver 7.5
●
SAP NetWeaver Application Server for ABAP 7.51
http://help.sap.com/nw75
innovation package
https://help.sap.com/nw751abap
●
SAP NetWeaver AS for ABAP 7.52
https://help.sap.com/nw752abap
Prerequisites
● You can only configure the SAP system for Active Directory services or other LDAP directories if these are
already available on the network. As of Windows 2000 or higher, the Active Directory is automatically
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
PUBLIC
191
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:
Table 63:
Operating System
Required Software
AIX
IBM Tivoli Directory Server client packages
HP-UX
The LDAP libraries listed in SAP Note 541344
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-todate information on available SAP systems.
To use LDAP operation mode, check that the sapmsg.ini file contains the following:
[Address]
Mode=LDAPdirectory
LDAPserver=
LDAPnode=
192
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
LDAPoptions=
Distinguish the following cases:
● If you use an Active Directory, you must set LDAPoptions=“DirType=NT5ADS”. For more information,
see the SAP system profile parameter ldap/options.
● You must specify the directory servers (for example, LDAPserver=pcintel6 p24709) if one of the
following is true:
○ The client is not located in the same domain forest as the Active Directory
○ The operating system does not have a directory service client (Windows NT and Windows 9X without
installed dsclient).
For more information, see the SAP system profile parameter ldap/servers.
● For other directory services, you can use LDAPnode to specify the distinguished name of the SAP root
node. For more information, see the SAP system profile parameter ldap/saproot.
SAP MMC
The SAP MMC is a graphical user interface (GUI) for administering and monitoring SAP systems from a central
location. It is automatically set up when you install an SAP system on Windows. If the SAP system has been
prepared correctly, the SAP MMC presents and analyzes system information that it gathers from various
sources, including the Active Directory.
Integrating the Active Directory as a source of information has advantages for the SAP MMC. It can read
system information straight from the directory that automatically registers changes to the system landscape.
As a result, up-to-date information about all SAP application servers, their status, and parameter settings is
always available in the SAP MMC.
If 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.1 to
7.5x on UNIX : Oracle
Additional Information
PUBLIC
193
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:
Table 64:
SAP Release and SAP Library Quick Link
●
SAP Library Path (Continued)
SAP NetWeaver Mobile 7.1
Application Help
http://help.sap.com/nwmobile71
●
Function-Oriented View
Server Infrastructure
SAP NetWeaver Mobile 7.1 including Enhancement
Application
SAP Management Console
Package 1
http://help.sap.com/nwmobile711
●
SAP NetWeaver 7.3
Application Help
http://help.sap.com/nw73
●
SAP NetWeaver 7.3 including Enhancement Package 1
http://help.sap.com/nw731
●
Function-Oriented View: English
Solution 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
Configuration Tasks for LDAP Directories
This section describes the configuration tasks for the Active Directory or other (generic) LDAP directories.
● Configuration Tasks for Active Directory
To enable an SAP system to use the features offered by the Active Directory, you have to configure the
Active Directory so that it can store SAP system data.
To prepare the directory, you use the installer to automatically:
○ Extend the Active Directory schema to include the SAP-specific data types
○ Create the domain accounts required to enable the SAP system to access and modify the Active
Directory. These are the group SAP_LDAP and the user sapldap.
○ Create the root container where information related to SAP is stored
○ Control access to the container for SAP data by giving members of the SAP_LDAP group permission to
read and write to the directory
You do this by running the installer on the Windows server on which you want to use Active Directory
Services and choosing
Generic Installation Options
<Database>
Preparations
LDAP Registration
Active Directory Configuration . For more information about running the installer on Windows, see the
documentation Installation Guide – <Product> on Windows: <Database>.
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.
194
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
● Configuration Tasks for Generic LDAP Directories
To configure other LDAP directories, refer to the documentation of your directory vendor.
● Enabling the SAP System LDAP Registration
Once you have correctly configured your directory server, you can enable the LDAP registration of the SAP
system by setting some profile parameters in the default profile.
To do this, run the installer [page 125] once for your system and choose:
Generic Installation Options
<Database>
Preparations
LDAP Registration
LDAP Support
If you use a directory server other than Microsoft Active Directory and/or non-Windows application
servers, you have to store the directory user and password information by using ldappasswd
pf=<any_instance_profile>. The information is encrypted for storage in DIR_GLOBAL and is therefore
valid for all application servers. After restarting all application servers and start services, the system is
registered in your directory server. The registration protocols of the components are dev_ldap*. The
registration is updated every time a component starts.
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 .
● 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 might be 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 system then creates new tablespaces and a new database schema.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
PUBLIC
195
● The installation of an additional SAP system in an existing database (MCOD)
The system then automatically creates additional tablespaces in the existing database and a schema user
in the existing database.
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.
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.
196
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
● 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 second SAP system, you must use the same <DBSID> as for the first SAP system.
● If you install an MCOD system, the SYSTEM tablespace must contain at least 400 MB of free space. If there
is not enough space left, increase the size of this tablespace with BRSPACE or BRTOOLS.
● If you decide to turn off archive log mode 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
Use
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.
For more information, see Integration of LDAP Directory Services in the Windows installation guide for your SAP
system solution and database.
Prerequisites
During the SAP instance installation you chose to configure the SAP system to integrate LDAP services.
Procedure
1. Log on as user <sapsid>adm.
2. Enter:
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
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
PUBLIC
197
7.4
Exporting and Mounting Directories via NFS
Related Information
Exporting and Mounting Directories via NFS for Linux [page 200]
Exporting and Mounting Directories via NFS for AIX [page 198]
Exporting and Mounting Directories via NFS for Oracle Solaris [page 202]
Exporting and Mounting Directories via NFS for HP-UX [page 199]
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.
Procedure
● To export an NFS filesystem, do the following steps:
a. Take the backup of the exports file:
cp -p /etc/exports /etc/exports_bak
b. Create an entry for each directory to be exported, using the full path name of the directory:
vi /etc/exports
c. Read the /etc/exports file and export all the directories listed:
exportfs -a
d. Confirm the exported directory listed:
showmount -e
e. Confirm the nfs client name and directory list:
showmount -a
● Mounting the NFS filesystem on the client:
198
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
a. Verify if the NFS server has exported the directory.
showmount -e <server_name>
b. Create the mounting directory if not already exist.
mkdir /local_directory
c. Mount the remote directory on the client:
mount <ServerName>:/<remote_directory> /<local_directory>
d. Confirm that the NFS filesystem has been mounted:
df -gt <NFS mount_name>
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).
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.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
PUBLIC
199
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
This section only provides the basic procedure. If you need more detailed information, check your OS vendor's
documentation.
The following procedure assumes that the central instance host is the NFS server.
Procedure
1. Log on as user root to the NFS server.
2. Make sure that your host is configured as NFS server as follows:
○ On Red Hat Linux, make sure that the output of the command:
chkconfig --list nfs
The output looks as follows:
Example
nfs 0:off 1:off 2:off 3:on 4:on 5:on 6:off
○ On SUSE Linux, enter the following command:
○ yast2
You can set up your host as NFS server as follows:
○ On Red Hat Linux, enter the following command:
system-config-users
○ On SUSE Linux, enter the following command:
yast2
3. To export a directory from a local file system, you can proceed as follows:
○ On Red Hat Linux, use the following tool:
system-config-nfs
○ On SUSE Linux, use the following tool:
yast2
Perform the configuration manually.
200
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
To perform the configuration manually, proceed as follows:
a. To add a line to the local file /etc/exports, enter the following:
#/etc/exports
<directory> <hostname>(<options>)
Note
There must not be a blank between <hostname> and<options>. Otherwise, the directory is
exported with default option (ro) (read-only) to the host specified by <hostname> and with the
option specified by <options> to all other hosts.
To export directories on Linux with root permissions, use the option no_root_squash. For security
reason, only use this option during installation.
Example
○ To export the directory /usr/sap/trans in read-only mode to the NFS client host.wdf.sap-ag.de,
enter the following:
#/etc/exports
/usr/sap/trans host.wdf.sap-ag.de(ro)
○ To export the directory in read-write mode with root permissions, enter the following:
#/etc/exports
/usr/sap/trans host.wdf.sap-ag.de(rw,no_root_squash)
○ To export the directory to all NFS clients of the domain using a wildcard (*), enter the following:
#/etc/exports
/usr/sap/trans *.wdf.sap-ag.de(rw)
b. To activate the changes (that is, inform the NFS daemon about the changes performed in /etc/
exports), enter the following command:
exportfs -r
c. To see a list of all currently exported directories, enter the following command:
exportfs -v
For more information, consult the man page by entering man exports.
4. Log on as user root to the host where the file system is to be imported.
5. To mount the file systems, enter the following command:
mount <nfs_server>:<file_system> <mount_point>
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
PUBLIC
201
Example
mount <nfs_server>:/usr/sap/trans /usr/sap/trans
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.
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>
202
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
c. If the /etc/dfs/dfstab was empty, the NFS server is not active.
○ On Solaris 9, start the NFS server with the following command:
/etc/init.d/nfs.server start
○ On Solaris 10, start the NFS server with the following command:
svcadm enable svc:/network/nfs/server:default
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 9, start the NFS server with the following command:
/etc/init.d/nfs.client start
○ On Solaris 10, start the NFS server with the following command:
svcadm enable svc:/network/nfs/client:default
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:
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
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
PUBLIC
203
7.6
Installing Oracle Real Application Clusters
You want to install Oracle Real Application Clusters (RAC) with the Software Provisioning Manager (the
“installer”) in an SAP environment. This section provides additional information for the RAC installation using
the installer.
Prerequisites
Example
As an example, this section describes the installation steps of a RAC installation using the following
installation parameters:
● DB_SID=C11
● default ASM data diskgroup=+DATA
● database hostnames (three node cluster)=vhost1,vhost2,vhost3
● three-digit threads=001,002,003 (it is also possible to have single-digit threads=1,2,3)
During the installation, the installer executes the Oracle executable $ORACLE_HOME/bin/srvctl to create the
<DBSID> cluster database (add database) and adds three instances (add instance) on the different hosts.
While the database is being loaded, the cluster is disabled (disable database).
● When the database installation, database load and also addtional steps like update statistics,
setting database users and creating secure store have all finished, the installer sets the
database to cluster mode (cluster_database=true) and enables the cluster database (enable
database).
You can find all these commands in the installer log files sapinst_dev*.log in the installation directory
(default: /tmp/sapinst_instdir):
Example
Oracle 11:
/oracle/C11/112/bin/srvctl add database -d C11 -o
/oracle/C11/112 -p +DATA/C11/spfileC11.ora -a DATA
/oracle/C11/112/bin/srvctl add instance -d C11 -i C11001 -n vhost1
/oracle/C11/112/bin/srvctl add instance -d C11 -i C11002 -n vhost2
/oracle/C11/112/bin/srvctl add instance -d C11 -i C11003 -n vhost3
/oracle/C11/112/bin/srvctl disable database -d C11
sqlplus "/ as sysdba"
ALTER SYSTEM SET CLUSTER_DATABASE=true
exit
204
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
/oracle/C11/112/bin/srvctl enable database -d C11
Oracle 12:
/oracle/C11/121/bin/srvctl add database -d C11 -oraclehome
/oracle/C11/121 -p +DATA/C11/spfileC11.ora -role PRIMARY -policy AUTOMATIC startoption OPEN -stopoption NORMAL
/oracle/C11/121/bin/srvctl add instance -db C11 -instance C11001 -n vhost1
/oracle/C11/121/bin/srvctl add instance -db C11 -instance C11002 -n vhost2
/oracle/C11/121/bin/srvctl add instance -db C11 -instance C11003 -n vhost3
/oracle/C11/121/bin/srvctl disable database -db C11
sqlplus "/ as sysdba"
ALTER SYSTEM SET CLUSTER_DATABASE=true
exit
/oracle/C11/121/bin/srvctl enable database -db C11
● When the database installation has finished and the installer has stopped, you can check the database
status as Oracle user or <sapsid>adm user with the following command:
Oracle 11: srvctl status database -d C11
Oracle 12: srvctl status database -db C11
Context
For additional information about how set up SAP systems to use Oracle Real Application Clusters (RACs), see
the whitepapers at https://www.sap.com/community/topic/oracle.html
SAP on Oracle Real Application
Clusters (RAC)
These whitepapers describe all required changes to the Oracle database, Oracle network configuration, Oracle
instance parameters, and so. However, they do not contain information about RAC installation with the
installer.
Procedure
1. You can then start the database on all nodes with the following command:
Oracle 11: srvctl start database -d C11
Oracle 12: srvctl start database -db C11
The installer does not start the database on all nodes after the installation has finished. Only the first
database RAC node is started.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
PUBLIC
205
You need to start all other instances manually after completing the preparation on the other database
nodes. In addition, when the installation is finished, the <sapsid>adm environment variable ORACLE_SID
is set to C11001 on the first node.
2. You prepare all other database instances as described in the following:
After completing the installation of the first RAC database node, you need to prepare all other database
nodes with the installer. These installation preparation steps create the required operating system users
and groups and also install the required kernel files like dba*tools and SAP Host Agent.
You can find this option on the Welcome screen of the installer at:
Database tools
Generic Installation Option
Oracle
RAC/ASM/Exadata Database Instance Preparation - Kernel <Version>
3. You install the primary application server instance and the additional application server instances:
For the RAC installation, the installer performs some additional steps during the installation of the
additional application server instance so that the application server of the additional application server
instance can connect to the cluster nodes. For this the installer updates the tnsnames.ora file with some
additional RAC-specific entries.
The installer modifies tnsname.ora like in the following example:
C11.WORLD
C11001.WORLD, C11002.WORLD, C11003.WORLD
C11_DVEBMGS01.WORLD
C11_D02.WORLD
The installer modifies SAP instance or start profiles like in the following example, where <xx> is a free
sequence number in the instance profile or start profile:
SETENV_xx = dbs_ora_tnsname=C11_DVEBMGS01
SETENV_xx = dbs_ora_tnsname=C11_D02
During the installation of the additional application server instance, the installer tries to restart the instance
but this fails because the RAC services are not registered at the cluster ware. To register the RAC services,
the installer creates the required commands in a shell script in the local installation directory.
You need to execute these shell scripts on one node of the cluster database as follows:
1. Log on to the database server as the Oracle user.
2. Set the Oracle environment to the home directory of the RDBMS using the following command:
setenv ORACLE_HOME /oracle/C11/112
3. Run the shell script using the following command:
call <Path_Of_Shell_Script>/C11_DVEBMGS01.sh
Example
Oracle 11:
Entries of the shell script:
srvctl add service -d C11 -s C11_DVEBMGS01 -r C11001 -a C11002,C11003 -P BASIC
-y AUTOMATIC -q true -j long -e SELECT -m BASIC -z 3 -w 5
srvctl start service -d C11 -s C11_DVEBMGS01
206
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
Entries of shell script for the additional application server instance server C11_D02.sh:
srvctl add service -d C11 -s C11_D02 -r C11002 -a C11001,C11003 -P BASIC -y
AUTOMATIC -q true -j long -e SELECT -m BASIC -z 3 -w 5
srvctl start service -d C11 -s C11_D02
Oracle 12:
Entries of the shell script:
srvctl add service -db C11 -service C11_DVEBMGS01 -preferred C11001 -available
C11002,C11003 -tafpolicy BASIC -policy AUTOMATIC -notification true failovertype SELECT -failovermethod BASIC -failoverretry 3 -failoverdelay 5
srvctl start service -db C11 -service C11_DVEBMGS01
Entries of shell script for the additional application server instance server C11_D02.sh:
srvctl add service -db C11 -service C11_D02 -preferred C11002 -available
C11001,C11003 -tafpolicy BASIC -policy AUTOMATIC -notification true faileovertype SELECT -faileovermethod BASIC -faileoverretry 3 -failoverdelay 5
srvctl start service -db C11 -service C11_D02
After you have executed these commands on the database server, the installation of the additional
application server instance can continue. Now you can start the instance without connection problems.
4. You start the additional application server instance instance.
7.7
Database Instance Installation on Oracle Automatic
Storage Management
This section provides information on the installation of a database instance on an Oracle Automatic Storage
Management (ASM).
Software provisioning manager performs the following steps that differ from the general installation on nonASM systems:
● It creates the oracle user and the additional Oracle groups oinstall, asmdba, asmadmin, and asmoper.
● It installs the correct user environment for the oracle and <sapsid>adm users.
Prerequisites
● You must have installed the Oracle GRID software. This software ensures that ASM can be used.
● You must have created the following Oracle disk groups:
○ +DATA, +<DBNAME>_DATA or +DATA_<DBMACHINENAME> for all data files, online redo logs (first copy),
and control file (first copy).
○ +ARCH, +<DBNAME>_ARCH for control file (second copy) and archive redo logs (not for engineered
systems such as Exadata or SuperCluster).
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
PUBLIC
207
○ +RECO, +<DBNAME>_RECO or +RECO_<DBMACHINENAME> for control file (third copy), online redo log
(second copy), RMAN backups and fast recovery area.
○ +OLOG, + MLOG for redo log file are optional for larger systems (not for engineered systems such as
Exadata or SuperCluster).
More Information
For more information, see SAP on Oracle Automatic Storage Management (ASM)
.
Related Information
Creating Operating System Users and Groups [page 80]
Oracle Directories [page 92]
Installation Checklist [page 112]
Ensuring User Security [page 173]
7.8
Implementing Oracle Database Vault with the Installer
The installer supports Oracle Database Vault. This section provides information about implementing Oracle
Database Vault (DV) with the installer.
Prerequisites
● Your Oracle database version must be 12.1 or higher.
● Check the prerequisites, restrictions, and patch requirements as listed in SAP Note 2218115
.
Context
For a new system installation, the installer prompts whether DV is to be installed.
DV requires the following addional users:
● secadmin
● secacctmgr
These users are created by the installer.
208
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
For more information about Oracle Database Vault, see the Oracle Database documentation referred to in SAP
Note 2218115 .
Procedure
1. Start the installer and choose the installation option for your system variant as described in Running the
Installer [page 125].
2. On the Oracle Database screen where you are prompted to enter the required Oracle database parameters,
mark the Install Oracle Database Vault checkbox.
3. On the Database Accounts for Oracle Database Vault screen, specify the following:
○ Provide the passwords for the Oracle Database Vault user accounts secadmin and secacctmgr which
are to be created by the installer.
○ If you want to be enabled after the installation has completed, mark the Enable Oracle Database Vault
checkbox.
Next Steps
Configure Oracle Database Vault as described in SAP Note 2218115
7.9
.
Oracle Database 12c Multitenant Database Installation
The multitenant option introduced in Oracle Database 12c allows a single container database (CDB) to host
multiple separate pluggable databases (PDB). Using Software Provisioning Manager ( the “ installer”) you can
create a CDB, PDB, and also a new pluggable database in an existing container database.
Container Database (CDB)
The container database is the body of a seed and a pluggable (PDB) database and is called CDB$ROOT. In this
special database the common user, SGA, control file, and more are stored. Every CDB has a “seed” database.
This “seed” is the template for creating additional PDBs. The seed database has the internal name PDB$SEED .
Pluggable Database (PDB)
The pluggable database includes the customer data, for SAP the SAP<SCHEMAID> data. Every PDB shares the
SGA, control file, redo logs and undo tablespace from the CDB. Every PDB has its own system and sysaux
tablespace and can have its own temporary tablespace.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
PUBLIC
209
Installation Features in the Installer
The installation has the following restrictions:
● This installation is only available for SWPM 7.* where * is greater than 1.
● This installation is only available for single instance installation on file system.
● SAP kernel version must be 7.45 or higher.
The installation is possible for the following scenarios:
● Install the CDB and PDB.
● Install one or more PDBs in an existing CDB.
For more information, see 2336881
Related Information
Installing the Container Database and a Pluggable Database [page 210]
Installing a Distributed Application Server Instance [page 211]
Installing an Additional Pluggable Database in a Pre-Installed Container Database [page 211]
7.9.1 Installing the Container Database and a Pluggable
Database
In this section we describe how you install the container database (CDB) and a pluggable database (PDB).
Procedure
1. Start the installer on the database instance host to perform the database instance installation as described
in Running the Installer [page 125].
2. On the SAP System Database screen, you have to specify the container database (CDB) system id (SID) in
the field Database ID. The SID cannot have the same SID as the PDB.
Recommendation
We recommend that you assign the CDB a different SID than the SAP system ID (<SAPSID>) because
the default SID of the pluggable database (PDB) equals the <SAPSID>.
3. On theOracle Multitenant Database screen, you select the PDB SID (default is SAP SID). CDB SID cannot
have the same SID as PDB SID. When you select No, a normal database installation is done.
210
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
Related Information
Oracle Database 12c Multitenant Database Installation [page 209]
SAP System Database Parameters [page 66]
7.9.2 Installing a Distributed Application Server Instance
For a distributed application server installation, you need to specify how the application server is to connect to
a pluggable database (PDB) or a “normal” database.You can install one or more additional PDBs in an existing
container database (CDB).
Procedure
1. Start the installer on the application server instance host as described in Running the Installer [page 125].
2. On the SAP System Database screen, enter the CDB SID of your existing CDB where your pluggable
database is located.
3. On the Oracle Multitenant Database screen, you select the PDB SID where you want to install the
application server instances.
Related Information
Oracle Database 12c Multitenant Database Installation [page 209]
SAP System Database Parameters [page 66]
7.9.3 Installing an Additional Pluggable Database in a PreInstalled Container Database
This section describes how you install an additional pluggable database (PDB) in a Pre-Installed container
database (CDB).
Procedure
1. Start the installer on the database instance host to perform the database instance installation as described
in Running the Installer [page 125].
2. On the SAP System Database screen, enter the container database system ID (CDB SID) of an existing
container database installation.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
PUBLIC
211
The installer recognizes that a normal database installation or a pre-installed CDB already exists.
3. If you want to install an additional PDB, on the Oracle Database screen enter Install Additional Pluggable
DB in Existing Container DB.
4. On the Oracle Multitenant Database screen, the installer displays all available PDBs. Select Install or
Connect to Multitenant PDB and specify the SID of PDB (PDBSID)
Related Information
Oracle Database 12c Multitenant Database Installation [page 209]
SAP System Database Parameters [page 66]
7.10
Installing the SAP Host Agent Separately
This procedure tells you how to install an SAP Host Agent separately.
Context
The SAP Host Agent is installed automatically during the installation of new SAP instances with SAP kernel 7.20
or higher (integrated installation). This procedure is only for hosts with no SAP Host Agent running on them,
due to the following reasons:
● There is no SAP system or instance on the host.
● The SAP system or instance running on the host has a kernel release lower than SAP kernel 7.20 and the
host does not yet have an SAP Host Agent.
● You have upgraded your SAP system to a release with a kernel release lower than SAP kernel 7.20 and the
host of the upgraded system or instance does not yet have an SAP Host Agent.
SAP Host Agent has the following executable programs and services:
● The SAPHostExec service
● The sapstartsrv service SAPHostControl
● The operating system collector saposcol
Note
The installed programs are automatically started when the host is booted.
The automatic start is ensured by the startup script sapinit, which starts the required executables.
The following procedure describes the steps you have to perform on the host where you install the SAP Host
Agent separately.
212
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
Procedure
1. Check the hardware and software requirements on the installation host.
The minimum requirements are as follows:
○ Hard Disk Space: 1 GB
○ RAM: 0.5 GB
○ Swap Space: 2 x RAM
For more information, see hardware and software requirements [page 38].
2. Make sure that the sapadm user is created.
During the installation, the installer checks all required accounts (users, groups) and services on the local
machine. The installer checks whether the required users and groups already exist. If not, it creates new
users and groups as necessary.
Table 65: 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 (attrib­
ute shells) in /etc/
security/login.cfg.
End of 'Platform': AIX
Table 66: Groups and Members of the SAP Host Agent User
Groups
Members
sapsys
sapadm
sapinst
sapadm
3. Set up the required file system for the SAP Host Agent:
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
PUBLIC
213
Table 67:
Directories
Description
Required Disk Space
/usr/sap/hostctrl
Contains the following directories:
100 MB
○
exe
Contains the profile
host_profile
○
work
Working directory of the SAP Host
Agent
For more information, see Setting up file systems and raw devices [page 86].
4. Download and unpack the Software Provisioning Manager archive on the host where you want to install the
SAP Host Agent as described in Downloading and Extracting the Software Provisioning Manager 1.0
Archive [page 102].
5. Make the latest patch level of the SAPHOSTAGENT <Version>.SAR file available on the host where you
want to install the SAP Host Agent.
You can do this in the following ways:
○ Download it from the following path: https://launchpad.support.sap.com/#/softwarecenter
SUPPORT PACKAGES & PATCHES
AGENT
SAP HOST AGENT 7.21
By Category
SAP Technology Components
SAP HOST
<Operating System>
○ Alternatively, you can also copy it from the UC kernel medium (folder K_<Version>_U_<OS>), where
“_U_” means Unicode.
You can either use the physical UC kernel medium from the installation package of your SAP system,
or download the kernel medium from https://launchpad.support.sap.com/#/softwarecenter . For
more information, see Downloading Complete Installation Media [page 110] .
Recommendation
It is highly recommended that you always choose the highest SP version of the SAPHOSTAGENT<SPversion>.SAR archive.
6. To install the SAP Host Agent, you start the installer [page 125] and choose
<Database>
Preparations
SAP Host Agent
Generic Installation Options
on the Welcome screen of the installer.
7. Check whether the installed services are available:
a. Log on as a user with root authorizations.
Note
When the host is booted, the startup script sapinit automatically starts the required executables.
b. Check whether the following services are available:
○ The control program saphostexec
○ The SAP NetWeaver Management agent SAPHostControl (sapstartsrv in host mode)
214
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
Next Steps
For more information about the SAP Host Agent, see the following documentation:
Table 68:
SAP Release and SAP Library Quick Link
●
SAP NetWeaver Mobile 7.1
http://help.sap.com/nwmobile71
●
SAP NetWeaver Mobile 7.1 including Enhancement
SAP Library Path (Continued)
Application Help
Server Infrastructure
Function-Oriented View
Application
SAP Host Agent
Package 1
http://help.sap.com/nwmobile711
●
SAP NetWeaver 7.1 for Banking Services from SAP
See the SAP NetWeaver Mobile Library.
http://help.sap.com/nwmobile71
●
Note
SAP NetWeaver 7.1 including Enhancement Package 1
for Banking Services from SAP
http://help.sap.com/nwmobile711
Since the SAP NetWeaver Mobile 7.1 Library is the only
available SAP Library for ABAP systems based on SAP
NetWeaver 7.1, in this guide we always refer to it also for
SAP NetWeaver 7.1 for Banking Services from SAP 5.0
and 6.0.
●
SAP NetWeaver 7.3
http://help.sap.com/nw73
●
SAP NetWeaver 7.3 including Enhancement Package 1
Application Help
Function-Oriented View: English
Solution Life Cycle Management
SAP Host Agent
http://help.sap.com/nw731
●
SAP NetWeaver 7.4
http://help.sap.com/nw74
●
SAP NetWeaver 7.5
●
SAP NetWeaver Application Server for ABAP 7.51
http://help.sap.com/nw75
innovation package
https://help.sap.com/nw751abap
●
SAP NetWeaver AS for ABAP 7.52
https://help.sap.com/nw752abap
7.11
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.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
PUBLIC
215
Prerequisites
The existing SAP system of the primary application server instance must meet the following requirements:
● It was upgraded from an SAP system release based on SAP NetWeaver lower than 7.1.
● It does not yet have an ASCS instance
Context
Before the Split
The 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.
216
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
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 56]:
○ 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 38].
3. Specify basic SAP System Parameters [page 56] for the ASCS instance to be created.
4. Set up the required file systems [page 86] for the ASCS instance to be created.
5. Check the prerequisites [page 122] and start the installer [page 125] on the host where the ASCS instance
is to be created.
6. On the Welcome screen, choose
Generic Options
Primary Application Server Instance
<Database>
Split Off ASCS Instance from Existing
.
7. Follow the instructions on the installer screens and enter the required parameters.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
PUBLIC
217
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 installer displays the Parameter Summary
screen. This screen shows both the parameters that you entered and those that the installer set by default.
If required, you can revise the parameters before starting the installation.
8. To start the installation, choose Start.
The installer starts the installation and displays the progress of the installation. When the installation has
successfully completed, the installer shows the dialog Execution of Split Off ASCS Instance from existing
Primary Application Server Instance has completed.
9. You check and if necessary modify the settings for the operating system users for your SAP system if they
were created by the installer.
For more information, see Creating Operating System Users and Groups [page 80].
10. Restart the application server instances [page 218] (primary application server instance and additional
application server instances if they exist).
11. Check whether you can log on to the application servers [page 152].
12. Ensure user security [page 173] for the operating system users of the newly created ASCS instance.
13. If required, perform an installation backup [page 182].
7.12
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 218]
● Using commands [page 222].
7.12.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.
218
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
● If you want to start or restart remote systems or instances, make sure that you have registered them in the
SAP Management Console (SAP MC). You do not need to register SAP systems or instances installed on
the local host, because the SAP MC displays them automatically.
● The SAP Host Agent is installed on the host where the application server of the SAP system or instance
runs.
● You have installed Java Runtime Environment (JRE) 5.0 or higher.
● Your Web browser supports Java.
● Your Web browser's Java plug-in is installed and enabled to run scripting of Java applets.
Context
Recommendation
If you experience any issues when starting or using the SAP MC, refer to SAP Note 1153713
.
● For more information about handling the SAP MC, see the SAP Library at:
Table 70:
SAP Release and SAP Library Quick Link
○
SAP NetWeaver Mobile 7.1
http://help.sap.com/nwmobile71
○
SAP Library Path (Continued)
SAP NetWeaver Mobile 7.1 including Enhancement
Package 1
Application Help
Function-Oriented View
Application Server Infrastructure
SAP Management
Console
http://help.sap.com/nwmobile711
○
SAP NetWeaver 7.3
http://help.sap.com/nw73
○
SAP NetWeaver 7.3 including Enhancement Package
1
Application Help
Function-Oriented View: English
Solution Life Cycle Management
SAP Management
Console
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/viewer/p/SAP_NETWEA­
VER_AS_ABAP_751_IP
● 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).
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
PUBLIC
219
For more information about handling the SAP MMC, see the SAP Library at:
Table 71:
Release SAP Library Quick Link
SAP Library Path (Continued)
○
SAP NetWeaver Mobile 7.1
See the SAP Library path for SAP NetWeaver 7.3 and
○
SAP NetWeaver Mobile 7.1 including Enhancement
higher.
Package 1
○
SAP NetWeaver 7.1 for Banking Services from SAP
5.0 and 6.0
○
SAP NetWeaver 7.1 including Enhancement Package 1
for Banking Services from SAP 5.0 and 6.0
○
SAP NetWeaver 7.3
Application Help
http://help.sap.com/nw73
○
SAP NetWeaver 7.3 including Enhancement Package
Function-Oriented View: English
Solution Life Cycle Management
SAP Microsoft
Management Console: Windows
1
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
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.
220
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
2. Choose Start.
The SAP Management Console (SAP MC) appears.
By default, the instances installed on the host you have connected to are already added in the SAP MC.
Note
If the instances have not been added or if you want to change the configuration to display systems
and instances on other hosts, you have to register your system manually. This is described in
Registering Systems and Instances in the SAP Management Console below.
● Starting SAP Systems or Instances
Similarly, you can start or restart all SAP systems and individual instances registered in the SAP MC.
1. In the navigation pane, open the tree structure and navigate to the system node that you want to start.
2. Select the system or instance and choose Start from the context menu.
3. In the Start SAP System(s) dialog box, choose the required options.
4. Choose OK.
The SAP MC starts the specified system or system instances.
Note
The system might prompt you for the SAP system administrator credentials. To complete the
operation, you require administration permissions.
Log in as user <sapsid>adm.
Starting SAP System Instances Successively
If you need to start the instances of an SAP system successively – for example when you want to start a
distributed or a high-availability system – proceed as follows:
1. Start the database instance.
2. Start the ABAP central services instance ASCS<Instance_Number>.
3. Start the primary application server instance D[VEBMGS]<Instance_Number>.
Note
In SAP systems based on SAP NetWeaver 7.5 or higher, the primary application server instance is
named D<Instance_Number>.
In SAP systems based on SAP NetWeaver 7.4 or lower, the primary application server instance is
named DVEBMGS<Instance_Number>.
4. Start additional application server instances D<Instance_Number>, if there are any.
● Stopping SAP Systems or Instances
Similarly, you can stop all SAP systems and individual instances registered in the SAP MC.
1. Select the system or instance you want to stop and choose Stop from the context menu.
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.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
PUBLIC
221
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.12.2 Starting and Stopping SAP System Instances Using
Commands
Prerequisites
You are logged on to the SAP system host as user <sapsid>adm.
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
.
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/hostctrl/exe/sapcontrol --help
222
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
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/hostctrl/exe/sapcontrol -nr <instance_number> -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/hostctrl/exe/sapcontrol -nr <instance_number> -function Start
For remote instances, the syntax is slightly different, because you also have to apply the -host and user parameters:
/usr/sap/hostctrl/exe/sapcontrol –nr <instance_number> -host <remote host> –
user <sapsid>adm <password> -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/hostctrl/exe/sapcontrol -nr <instance_number> -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/hostctrl/exe/sapcontrol -nr <instance_number> -function Stop
For remote instances, the syntax is slightly different, because you also have to apply the -host and user parameters:
/usr/sap/hostctrl/exe/sapcontrol –nr <instance_number> -host <remote host> –
user <sapsid>adm <password> -function Stop
Note
The database is not stopped by these commands. You have to stop the database using databasespecific tools or commands.
● 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/hostctrl/exe/sapcontrol –nr <instance_number> -host <remote host> –
user <sapsid>adm <password> -function GetSystemInstanceList
○ With the following command you get a list of instance processes and their status:
/usr/sap/hostctrl/exe/sapcontrol –nr <instance_number> -host <remote host> –
user <sapsid>adm <password> -function GetProcessList
● Troubleshooting
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
PUBLIC
223
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.13
Deleting an SAP System or Single Instances
This section describes how to delete a complete SAP system or single SAP instances with the Uninstall option
of the installer.
Prerequisites
● You have installed your SAP system with standard SAP tools according to the installation documentation.
● You are logged on as 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 SAPrelated processes are stopped. If there is a lock on one of the SAP system objects, the uninstall fails.
Note
You do not have to stop the SAP Host Agent. The SAP Host Agent is stopped automatically during the
uninstall process.
● When starting the uninstall, make sure that there are no SAP system user sessions still open.
Context
Note
With this installer option you do not delete the database software.
Note the following when deleting an SAP system or single instances:
● We strongly recommend that you delete an SAP system or single instances using the installer. However,
you can also delete an SAP system or single instance manually. For more information, see SAP Note
1259982 .
● You cannot delete an SAP system remotely.
224
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
● 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 installer as described in Running the Installer [page 125].
2. On the Welcome screen, choose:
Generic Installation Options
<Database>
Uninstall
Uninstall SAP Systems or Single Instances
3. Follow the instructions on the installer screens to delete a complete SAP system or single instances.
Note
To find more information on each parameter during the Define Parameters phase, position the cursor on
the required parameter input field , and choose either F1 or the HELP tab. Then the available help text
is displayed in the HELP tab.
The following table provides information about deleting a complete system or single instances with the
installer.
Table 81:
Deletion of
Remarks
Standard system
You can delete a standard system (where all instances reside on the same host) in one
installer run.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
PUBLIC
225
Deletion of
Remarks
Distributed or high-availability
If you want to delete a distributed or high-availability system, you have to run the in­
system
staller to delete the required instances locally on each of the hosts belonging to the
SAP system in the following sequence:
1.
Additional application server instances, if there are any
Caution
Do not select checkbox Uninstall all instances of the SAP system from this host
if you do not want to uninstall the complete SAP system or standalone engine.
For example, do not select this checkbox if you only want to uninstall an addi­
tional application server instance of an existing SAP system distributed over
several hosts. Otherwise the contents of mounted global directories under /
<sapmnt>/<SAPSID>/, such as instance profiles and kernel executables, are
also deleted.
2. Primary application server instance
3. Database instance
Choose whether you want to drop the entire database instance or only one or
more database schemas.
Since the installer only stops local instances automatically, make sure that before
deleting the database instance of a distributed system, you stop all remaining in­
stances. You must stop the instance with the message server only after having
entered all installer parameters for the deletion of the database instance.
Before deleting any database schema, make sure that:
○
You have performed a recent offline database backup.
○
You have stopped or deleted all SAP instances belonging to this database
schema.
○
You only delete the tablespaces that belong to the selected schema.
The database tablespace PSAP<SCHEMA_ID>DB belongs by default to the
Java schema SAP<SCHEMA_ID>DB. All other SAP tablespaces belong to the
ABAP schema SAP<SCHEMA_ID> (or SAPR3 for older SAP systems).
4. ABAP Central services instance (ASCS)
Note
To delete system directories mounted from an NFS server, you have to run the in­
staller on the NFS server.
Additional application server
If you want to delete additional application server instances of an existing SAP sys­
tem, you have to run the installer to delete them locally on each additional application
server instance host.
226
PUBLIC
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
Deletion of
Remarks
Standalone SAP Host Agent
The SAP Host Agent is automatically uninstalled from a host together with the last re­
maining SAP system instance.
If you want to uninstall a standalone SAP Host Agent, deselect Profiles Available and
select Uninstall Standalone SAP Host Agent on the General SAP System Parameters
screen.
4. When you have finished, delete the relevant directory structure on the global host.
5. Uninstall the Oracle database software with the Oracle Universal Installer (OUI).
For more information, see Oracle Database Software Uninstallation [page 227].
6. 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.
7. 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.14
Oracle Database Software Uninstallation
You have to uninstall the Oracle database software to complete the uninstallation of the Oracle database
instance.
Related Information
Uninstalling the Oracle 11 Database Software [page 227]
Uninstalling the Oracle 12 Database Software [page 228]
7.14.1 Uninstalling the Oracle 11 Database Software
This procedure tells you how to uninstall the database software, starting with Oracle Database 11g Release 2
(11.2).
Context
For more information, see SAP Note 1525025
.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
PUBLIC
227
Caution
Do not use RunInstaller or the new deinstall tool to remove an Oracle 11.2 database installation. The deinstall
tool might not only delete the software from the Oracle home, but also other files (database files, logs,
traces, configuration files, inventory) in <ORACLE_BASE>.
Therefore, we strongly recommend you to use the procedure below to remove the 11.2 Oracle home
software.
Procedure
1. Back up the central Oracle inventory, which is normally located at $ORACLE_BASE:
OS> cd $ORACLE_BASE
OS> zip -r oraInventory.zip oraInventory
2. Check whether Oracle home is registered in the central Oracle inventory:
OS> $ORACLE_HOME/OPatch/opatch lsinventory -all -invPtrLoc $ORACLE_HOME/
oraInst.loc
If Oracle home is registered, it appears in the displayed List of Oracle Homes. Otherwise, opatch
returns error code 73.
Oracle home must be registered in order to detach it.
3. Detach Oracle home from the central Oracle inventory:
OS> $ORACLE_HOME/oui/bin/runInstaller -silent -detachHome ORACLE_HOME=
$ORACLE_HOME -waitForCompletion -invPtrLoc $ORACLE_HOME/oraInst.loc
At the end of the procedure, you see the message:
'DetachHome' was successful
4. Remove the Oracle home software from the file system:
OS> rm -rf $ORACLE_HOME
7.14.2 Uninstalling the Oracle 12 Database Software
Procedure
Proceed as described in SAP Note 1915314
228
PUBLIC
.
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Additional Information
Important Disclaimers and Legal Information
Coding Samples
Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system
environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and
completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP
intentionally or by SAP's gross negligence.
Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as
"sales person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun
does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.
Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not
warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any
damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for
transparency (see: https://help.sap.com/viewer/disclaimer).
Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.1 to
7.5x on UNIX : Oracle
Important Disclaimers and Legal Information
PUBLIC
229
go.sap.com/registration/
contact.html
© 2018 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/corporate/en/legal/copyright.html
for additional trademark information and notices.