Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), February 2008

SAP Supply Chain Management
APO Setup Changes
Chapter 4204
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.
GS220 liveCache installation Step:
Run SAP transaction LC10 and configure the logical liveCache names
LCA and LCD to listen to the relocatable IP of the liveCache package.
GS230 liveCache installation Step:
1. Configure the XUSER file in the APO user home and liveCache user
home directory. If a .XUSER 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 changed to the relocatable IP the liveCache is
running on.
• To list all mappings in the XUSER file, run the following command as
<lcsid>adm of the APO user:
su - <lcsid>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. Keys commonly
created by SAP include c, w and DEFAULT. If a mapping was created
without specifying a key, entries of the form <num><LCSID><hostname>,
e.g. 1LC1node1 exist. These will only work on one of the cluster hosts.