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 67
You can also use strict policy, if your SAP system is the only one running
at the site and you are low on memory. Strict policy frees up more of its
own shared memory segments than the normal policy does.
Advanced Options of sap.config
In ${SGCONF} there is a file called customer.functions. Do not change
the sap.functions. The file provides ten predefined hooks, which allow
the specification of individual startup or runtime steps at certain phases
of the db/dbci/ci package script execution.
A summary of the hooks in chronological order:
1. start_addons_predb: additional startup steps on database host
after all low level resources are made available
after the system has been cleaned up for db start
before start of database instance
2. start_addons_postdb:additional startup steps on database host
after start of the database instance
3. start_addons_preci: additional startup steps on Central Instance
host
after start of the database instance
4. start_addons_postci:additional startup steps on Central Instance
host
after start of the Central Instance
before start of any Application Server Instance
5. start_addons_postciapp: additional startup steps that are performed
on the Central Instance host
after startup of all Application Server Instances
Equally, there are hooks for the stop procedure of packages:
1. stop_addons_preciapp: usually this function contains actions that
relate to what has been added to
start_addons_postciapp
2. stop_addons_preci: relates to start_addons_postci