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

In file ${SGCONF}/<LCSID>/lc<LCSID>.control.script add the following lines to the customer
defined functions customer_defined_run_cmds and customer_defined_halt_cmds .
These commands will actually call the SGeSAP/LX relevant functions to start and stop the liveCache instance.
So the customer defined functions are the glue that connects the generic Serviceguard components with the
SGeSAP/LX components.
function customer_defined_run_cmds
{
### Add following line
${SGCONF}/<SID>/saplc.sh startDB <LCSID>
test_return 51
}
function customer_defined_halt_cmds
{
### Add following line
${SGCONF}/<SID>/saplc.sh stopDB <LCSID>
test_return 52
}
liveCache installation Step: LC190
The ${SGCONF}/<LCSID>/sap.config configuration file of a liveCache package is similar to the
sap.config configuration file of the generic SGeSAP/LX packages.
The following standard parameters in sap.config have to be set for a liveCache package:
DB=LIVECACHE
DBRELOC=<reloclc_s>
TRANSRELOC=<relocsapnfs_s>
CLEANUP_POLICY= [ strict | normal | lazy ]
The strict option can be set in order to guarantee the liveCache package gets all resources required on the
adoptive node. Remember that this option can crash a system running on the adoptive node.
▲ The following liveCache specific parameters in sap.config have to be set:
LCSTARTMODE specifies the mode of the liveCache database up to which it should be started automatically.
Possible values for version 7.4 of liveCache are:
OFFLINE: only vserver will be started
COLD: liveCache started in cold mode
SLOW: liveCache started in cold -slow mode
WARM: liveCache started in warm mode
In liveCache version 7.5 some of these values have changed: (<from> -> <to>)
OFFLINE -> OFFLINE
COLD -> ADMIN
SLOW -> SLOW
WARM -> ONLINE
It is recommended to use the new values for liveCache version 7.5. For compatibility reasons the original
values will still work.
114 SAP Supply Chain Management