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

Step-by-Step Cluster Conversion
SAP WAS System Configuration
Chapter 3 175
SAP WAS System Configuration
This section describes some required configuration steps that are
necessary for SAP to become compatible to a cluster environment.
NOTE The following configuration steps do not need to be performed if the SAP
System was installed using virtual IPs. The steps are only required to
make a non-clustered installation usable for clustering.
• SAP ABAP Engine specific configuration steps
• SAP J2EE Engine specific configuration steps
SAP ABAP Engine specific configuration steps
Logon as <sid>adm on the primary node on which the Central Instance
has been installed. The appropriate Serviceguard package should still
run on this host in Serviceguard debug mode.
IS1100 Installation Step:
For ci virtualization, change into the profile directory by typing the
alias:
cdpro
In the DEFAULT.PFL change the following entries and replace the
hostname with the relocatible name if you cluster a (ci) component. For
example:
SAPDBHOST = <relocdb>
rdisp/mshost = <relocci>
rdisp/sna_gateway = <relocci>
rdisp/vbname = <relocci>_<SID>_<instnr>
rdisp/btcname = <relocci>_<SID>_<instnr>
rslg/collect_daemon/host = <relocci>