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

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 of saposcol. To
complete the process, a plain text configuration file is needed that tells sapcpe which files need to be
included in the copying process.
A file of this type is usually called sapcpeft. If sapcpeft exists, sapcpe will automatically be executed
as the first step of the next instance restart. It needs to be created in the central executable directory. For
each additional file in the central executable directory it needs to contain a line with the following format:
<filename> local_copy check_exist
SAP also delivers template file lists within the central executable directory. These files have a filename of the
format *.lst. The following files override sapcpeft: frontend.lst, instance.lst,
instancedb.lst, tools.lst and inhouse.lst. Either the *.lst files should get removed, or they
should be used instead of sapcpeft. In this case, they need to be changed to include all executables and
libraries.
If the local executable directory only holds links, sapcpe is not configured correctly. It is not an option to
manually copy the local executables in this case. The next instance restart would replace the local copies
with symbolic links.
For latest information on how to utilize sapcpe refer to the SAP online documentation.
66 Step-by-Step Cluster Conversion