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

To add an SAP infrastructure software component to the Configured SAP Infrastructure Software
Components list:
1. Enter information to the Type, Start/Stop, and Parameters boxes.
2. Click <Add to move this information to the Configured SAP Infrastructure Software Components
list.
To remove an SAP infrastructure software component from this list:
Click the option adjacent to the SAP infrastructure software component that you want to remove,
then click Remove.
To edit a configured SAP infrastructure software component:
Click the option adjacent to the SAP infrastructure software component that you want to edit, then
click Edit>>.
The SAP infrastructure software component information moves to the Type, Start/Stop, and
Parameters boxes—where you can make changes.
Click Update, and the edited SAP infrastructure software component information is returned to the
Configured SAP Infrastructure Software Components list.
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, 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)
Completing SGeSAP package creation (Phase 3b) 77