HP Serviceguard Extension for SAP (SGeSAP) manual Cmapplyconf -P ./sap.config

If the use of the SAP control framework is not required, then remove the reference link from the sapinit script. Furthermore, any running sapstartsrv processes can be killed from the process list. For example:

rm /sbin/rc3.d/S<###>sapinit

ps -ef grep sapstartsrv

kill <PID_of_sapstartsrv>

Module-based SGeSAP packages will handle the sapstart service agent automatically. For SAP releases based on kernel 7.10 or higher, SGeSAP can also register an instance with the startup framework as part of the package startup operation and de-register it as part of the package halt.

If the service agent is started via SGeSAP and configured to autostart the SAP instance, SGeSAP will monitor the operation to make sure that the instance startup succeeds.

Installation Step: IS474

The configuration file needs to be applied and the package started.

This step assumes that the cluster as such is already configured and started. Please refer to the Managing Serviceguard user's guide if more details are required.

The SGeSAP package configuration will be distributed to all nodes, verified on all nodes, and activated by issuing the following command on the package configuration file that was created and customized above:

cmapplyconf -P ./sap.config

64 Step-by-Step Cluster Conversion