Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), February 2008

Step-by-Step Cluster Conversion
Linux Configuration
Chapter 3 115
To automatically synchronize local copies of the executables, SAP
components deliver the sapcpe mechanism. With every startup of the
instance, sapcpe matches new executables stored centrally with those
stored locally. Figure 3-1 shows a SAP file system layout with sapcpe
activated for two Application Servers.
Figure 3-1 sapcpe Mechanism for Executables
To create local executables, the SAP file system layout needs to be
changed. The original link /usr/sap/<SID>/SYS/run needs to be
renamed to /usr/sap/<SID>/SYS/ctrun. A new local directory
/usr/sap/<SID>/SYS/run will then be required to store the local copy. It
needs to be initialized by copying the files sapstart and saposcol from
the central executable directory /sapmnt/<SID>/exe. Make sure to
match owner, group and permission settings. Do not forget to set the s-bit
Central Instance
App Server 1
/usr/sap/<SID>/SYS/exe/
/usr/sap/<SID>/SYS/exe/
/usr/sap/<SID>/SYS/exe/
/sapmnt/<SID>
exe/
NFS Mounted
/sapmnt/<SID>
exe/
NFS Mounted
/sapmnt/<SID>
exe/
App Server 2
sapcpe
sapcpe
NFS
NFS
dbg/
opt/
run/
dbg/
opt/
run/
ctrun/
dbg/
opt/
run/
ctrun/
softlink
NFS
Copied executables
via sapcpe