Managing Serviceguard Extension for SAP on Integrity Linux, December 2005

Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances
Cluster Configuration
Chapter 2 69
OS690 Optional Step:
For the two package concept, there might be a need to also have a
mechanism in place, that collects the same operating system values as
saposcol on the Central Instance host and feeds them back into the SAP
component for display with the SAP transaction OS07.
sapccmsr is a program that can be used to achieve these results. It
requires a working directory <shared_dir> that must be on a shared
logical volume of the database package. Within this directory or within
the central profile directory, a new profile <sid>_sapccmsr_<relocci>
should be created. The file has at least two entries:
SAPLOCALHOST=<relocdb>
DIR_PERF=<shared_dir>
In order to initialize the whole process the command sapccmsr -r has to
be run at least once while the SAP component is up and running. This
command will then connect the monitor to OS07 and creates a logical
RFC destination. The registration process is described in SAP's standard
documentation. With these prerequisites in place, the sapccmsr template
of customer.functions can be activated. Example entries in sap.config:
SAPCCMSR_START=1
SAPCCMSR_CMD=sapccmsr
SAPCCMSR_PFL=/sapdb/<dbsid>/sapccmsr/<sid>_sapccmsr_<relocci>
Refer to the comments in sap.config for example entries.