Managing HP Serviceguard Extension for SAP for Linux, December 2013

Check SAP liveCache instance in the initial SGeSAP module selection screen (Select a Toolkit ->
SGeSAP -> SAP liveCache instance).
The configuration dialogs brings up the screen for configuring the liveCache module.
Figure 23 Configuring liveCache screen
From the command line use:
cmmakepkg m sgesap/livecache lcLC1.config to create the package configuration
file. Then edit and apply the configuration file.
NOTE:
An SGeSAP liveCache package should not be configured with other SGeSAP modules, even
though it is technically possible .
The SGeSAP easy deployment (deploysappkgs) script does not support liveCache.
Verification:
Start up package on each configured node
Make sure the liveCache can be accessed on each client node by executing dbmcli U c
on these nodes
Make sure SCM LC10 integration can connect every time
5.6 Cluster conversion for existing instances
The recommended approach to clustering SAP configurations with Serviceguard is described in
“Installation options (page 52), “SAP installation (Phase 2)” (page 65), “Post SAP installation
tasks and final node synchronization (Phase 3a)” (page 66), and “Completing SGeSAP package
creation (Phase 3b)” (page 73) sections. The basic goal is to initially setup a "cluster-aware"
environment and then install SAP using virtual hostnames and the appropriate storage layout. There
might be configurations though, where the cluster conversion of an existing SAP instance or database
is necessary in order to make it high available with SGeSAP.
Such a cluster conversion consists primarily of two tasks:
Separating and moving the SAP instance files/file systems to file systems categorized as local
copies, as shared exclusive or as shared nfs file systems as described in chapter 4
“SAP Netweaver cluster storage layout planning” (page 37). This might involve creating new
volume groups and logical volumes as well as copying the instance files from the current file
86 Clustering SAP Netweaver using SGeSAP packages