Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), April 2009

In clustered SAP environments it is recommended to use local copies of the SAP executables. Local executables
limit the dependencies between the SAP package and the database package of a two package installation
to a minimum. They allow SAP packages to shutdown even if HA NFS is not available. To automatically
keep the local executables of any instance in sync with the latest installed patches, SAP developed the
sapcpe mechanism. With every startup of an SAP instance, sapcpe matches the latest executables that
were stored centrally with those stored locally and copies all required updates. Figure 2-3 shows the file
system layout with sapcpe.
Figure 2-3 sapcpe Mechanism for Executables
Table 2-5 Other SAP Instance Implementation Options as Listed in the Previous Sections:
DescriptionPath
EXCLUSIVE to this ABAP DI INSTANCE/usr/sap/<SID>/D01/
EXCLUSIVE to this ABAP ASCS INSTANCE/usr/sap/<SID>/ASCS02/
EXCLUSIVE to this JAVA SCS INSTANCE/usr/sap/<SID>/SCS03/
LOCAL to this JAVA CI INSTANCE Note: According to the
SAP documentation, it is recommended to configure JAVA CI and
JAVA DI on LOCAL file systems and not on EXCLUSIVE file systems.
/usr/sap/<SID>/JC04/
EXCLUSIVE to this JAVA REP INSTANCE/usr/sap/<SID>/ERS13/
SHARED NFS: the NFS automounter
The option for SHARED NFS is to use the NFS automounter as described below.
The automount scheme means that with the access to a automounter mount point the NFS file system will be
mounted to the local file system tree for as long as it is needed. When there is no activity on that file system
the automounter will automatically unmount the file system. A static NFS mount is usually mounted at boot
time, or done manually after boot, and only unmounted during shutdown, or by hand using the umount
command.
38 Planning a File System Layout for SAP in a Serviceguard/LX Cluster Environment