Managing HP Serviceguard Extension for SAP for Linux (May 2013)

If the liveCache is version >=7.8, then the xserver structure is the same as that of the MaxDB of
the corresponding version. If it is planned to run more than one liveCache or MaxDB on the system
it is advisable to decouple the xserver startup (sdggloballistener and DB specific). For more
information, see MaxDB section describing the decoupling of startup.
Setup of monitoring hook
Create a symbolic link that acts as a hook that informs SAP software where to find the liveCache
monitoring software to allow the prescribed interaction with it. Optionally, you can change the
ownership of the link to sdb:sdba. For this step the shared file system /sapdb/LCSID must be
mounted and the environment variable $SGCONF must be defined.
ln -s $SGCONF/sgesap/monitors/saplc.mon /sapdb/LCSID/db/sap/lccluster
Setting up the liveCache package
Attributes offered by the liveCache module are:
DescriptionParameter (Example)Parameter
LC1lc_system
The virtual hostname onto which the
liveCache has been installed
reloc1lc_virtual_hostname
List of values which define into which
state the liveCache must be started.
onlinelc_start_mode
Possible values are offline, (only vserver
will be started) admin, (start in admin
mode) slow, (start in cold-slow mode)
online. (start in oline mode)
Key to access the liveCache as
described in previous step. Default is
‘c’.
clc_user_key
The Serviceguard Manager guided package setup offers discovered values, if a liveCache is
installed.
Check SAP liveCache instance in the initial SGeSAP module selection screen (Select a Toolkit ->
SGeSAP -> SAP liveCache instance).
The configuration dialogs brings up the screen for configuring the liveCache module.
Figure 22 Configuring liveCache screen
From the command line use:
cmmakepkg –m sgesap/livecache lcLC1.config to create the package configuration
file. Then edit and apply the configuration file.
78 Clustering SAP using SGeSAP packages