Managing HP Serviceguard Extension for SAP for Linux, December 2013

• Disable liveCache xserver autostart (optional
• Create the liveCache monitoring hook
Create XUSER file
The SGeSAP liveCache module requires that a userkey with the "control user" has been setup for
the lcsidadm user. Normally, key c is used for this, but other keys can also be used. If the c key
does not exist, login as user <lcsid>adm and execute xuser –U c –u control,password
–d LCSID –n virtual-host set to create the XUSER file and the c key. Other keys will only
necessary if SCM/liveCache integration uses decentralized authorization instead of centralized
authorization. Latter is preselected in transaction LC10 and the recommended way of authorization.
Verify the userkey setup by running a connect test using dbmcli –U c db_state. This command
must return "online" if the liveCache is up.
The XUSER file must be distributed (along with the user itself if not done yet) to all node in cluster
planned to run the liveCache.
Verify transaction LC10
Make sure that the SAP LC10 transaction (Maintain liveCache integration) of the SCM
system uses the virtual hostname for the LCA, LDA and LEA database connections: Field liveCache
Server in the liveCache connection information. This is usually the case if liveCache
client was selected during SCM central instance installation and the values used during liveCache
installation were provided in that step.
Disable xserver Autostart (optional)
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.
Possible values are offline, (only vserver
will be started) admin, (start in admin
mode) slow, (start in cold-slow mode)
online. (start in online mode)
onlinelc_start_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.
5.5 Completing SGeSAP package creation (Phase 3b) 85