Managing Serviceguard Extension for SAP Version B.05.10, September 2010

APO Setup Changes
Running liveCache within a Serviceguard cluster package means that the liveCache instance is
now configured for the relocatable IP of the package. This configuration needs to be adopted in
the APO system that connects to this liveCache. Figure 4-3 shows an example for configuring
LCA.
Figure 4-4 Example HA SCM Layout
liveCache Installation Step: GS220
Run SAP transaction LC10 and configure the logical liveCache names LCA and LCD to listen
to the relocatable IP of the liveCache package.
liveCache Installation Step: GS230
Do the following to continue:
1. Configure the XUSER file in the APO user home and liveCache user home directories. If an
.XUSER.62 file does not already exist, you must create it.
2. The XUSER file in the home directory of the APO administrator and the liveCache
administrator keeps the connection information and grant information for a client connecting
to liveCache. The XUSER content needs to be adopted to the relocatable IP the liveCache is
running on.
• To list all mappings in the XUSER file, run the following command as sidadm of the
APO user:
su - <sid>adm
# dbmcli -ux SAPR3,SAP -ul
For liveCache 7.6 or higher:
su - <lcsid>adm
dbmcli -ux SAP<LCSID>,<password> -ul
This command produces a list of MAXDB user keys that may be mapped to the liveCache
database schema via a local hostname. SAP created keys commonly include c, w and
DEFAULT. If a mapping was created without specifying a key, entries of the form
APO Setup Changes 125