Managing Serviceguard Extension for SAP, December 2007

SAP Supply Chain Management
SGeSAP Package Configuration
Chapter 4 231
NOTE Activation of pause mode, state changes of liveCache and liveCache
restart attempts get permanently logged into the standard package
logfile /etc/cmcluster/<LCSID>/lc<LCSID>.control.script.log.
The monitor can also be paused by standard administrative tasks that
use the administrative tools delivered by SAP. Stopping the liveCache
using the SAP lcinit shell command or the APO LC10 transaction will
send the monitoring into pause mode. This prevents unwanted package
failovers during liveCache administration. Restarting the liveCache in
the same way will also trigger reactivation of the monitoring. The
SAPDB Database Manager GUI is not yet cluster-aware and must not be
used to stop liveCache in combination with Serviceguard.
LC210 liveCache Installation Step:
Log in on the primary node that has the shared logical volumes mounted.
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.
ln -s /etc/cmcluster/<LCSID>/saplc.mon \
/sapdb/<LCSID>/db/sap/lccluster
LC215 liveCache Installation Step:
For the following steps the SAPGUI is required. Logon to the APO
central instance as user SAP*. Start transaction /nlc10 and enter LCA
for the logical connection.
/nlc10 -> Logical connection -> LCA -> liveCache ->
Create/Change/Delete Connection
Change liveCache server name to the virtual IP name for the liveCache
(<relocls_s) and save it. Change the liveCache instance name to
<LCSID>. Redo the above steps for LDA.