Best Practices for Deploying HP-UX Secure Resource Partitions (SRP) for SAP Whitepaper

5
Table 1. Naming convention
SAP ID (SID)
SAP system identifier
DBSID
Database identifier
SAP INSTANCE
Number (NR)
SAP system instance number, consisting of a two digit number from 00 to 98
SAP INSTANCE
SAP system instance, e.g. DVEBMGS<NR> for ABAP or SCS<NR> for JAVA™
instances
host_name/vhost
Name of the host on which SAP will be installed. May be the same as the hostname
that resolves to the SRP compartment.
SRP compartment
SRP consists of compartments and additional options like IPFilter or PRM. For easy
readability, referring to compartments in this document also includes all other features
available for SRP
Other considerations
There are two approaches to configure SRP for SAP. Either, the SAP system already exists or the
system does not yet exist and will be installed. This document describes the best practices for both
approaches.
The installation model described in this white paper assumes compartment-specific binaries. This
statement means that an SAP system and Oracle® database are installed for each SRP compartment.
The installation can be done from the INIT compartment or from a new SRP compartment.
The exception to this rule is the use of the executable, saposcol. This executable may exist only once
per host and must to be run as a shared binary.
This document will only refer to standard SAP installations with Central Instance and Oracle 10g as
the database on one host based on NetWeaver products starting with NetWeaver 04. SRP
configurations for NetWeaver 7.0 ABAP or JAVA may be done in the same way.
Other SAP installation options like non-default installation directory, distributed installations or dialog
instance installation were not tested, the SAP_*.h compartment rule files can be used as a reference,
but may need adaptation.
Directory considerations
The standard SAP values for the SAP directories are assumed. If different paths are used during the
SAP installation, the rule files in this document will have to be adapted. The Oracle installation is
done within an SRP compartment using the Oracle RUNINSTALLER for SAP. For each SRP
compartment, a separate Oracle database will be installed, using the standard SAP directories for
Oracle: /oracle/<DBSID>.
Commonly used SAP directories, like the transport directory, are made unique by the SAP ID in the
examples used here; however, other differentiators may be used. In this case, the example rule files
will have to be adapted.
To use SRP for SAP, several manual modifications have to be done for the SAP system; they are listed
in the section, “Best practices for configuring SRP for the SAP production system”, in this white paper.
With these configurations, an SAP system will run within an SRP compartment. With the compartment
startup and shutdown option, it is also possible to start the SAP startup framework at compartment
startup.