Managing Serviceguard Extension for SAP Version A.06.00 for Linux, December 2012

Module sgesap/livecache – SAP liveCache instance
The liveCache setup is very similar to a sgesap/dbinstance setup with MaxDB. However, there
are a few minor differences:
• The liveCache installation does not create a XUSER file (.XUSER.62)
• The liveCache clients are the work processes of the SCM system which belong to a different
SID
Additional steps for livecCache are:
• Create the XUSER file with the c key
• Make sure SAP transaction LC10 in the SCM system has the virtual hostname for liveCache
configured
• 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, the 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
76 Clustering SAP using SGeSAP packages