Managing Serviceguard Extension for SAP, December 2007

SGeSAP Cluster Administration
Change Management
Chapter 6 301
SAP Software Changes
During installation of the SGeSAP Integration for SAP releases with
kernel <7.0, SAP profiles are changed to contain only relocatable
IP-addresses for the database as well as the Central Instance. You can
check this using transaction RZ10. In the DEFAULT.PFL these entries are
altered:
SAPDBHOST= <relocatible_db_name>
rdisp/mshost= <relocatible_ci_name>
rdisp/vbname= <relocatible_ci_name>_<SID>_<INR>
rdisp/enqname= <relocatible_ci_name>_<SID>_<INR>
rdisp/btcname= <relocatible_ci_name>_<SID>_<INR>
rslg/collect_daemon/host = <relocatible_ci_name>
There are also two additional profile parameters SAPLOCALHOST and
SAPLOCALHOSTFULL included as part of the Instance Profile of the
Central Instance. Anywhere SAP uses the local hostname internally, this
name is replaced by the relocatable values <relocatable_ci_name> or
<relocatable_ci_name>.domain.organization of these parameters.
Make sure that they are always defined and set to the correct value. This
is vital for the system to function correctly.
Relocatable IP addresses can be used consistently beginning with SAP
kernel 6.40. Older releases use local hostnames in profile names and
startup script names. Renamed copies of the files or symbolic links exist
to overcome this issue.
The destination for print formatting, which is done by a Spool Work
process, uses the Application Server name. Use the relocatable name if
you plan to use Spool Work processes with your Central Instance. In
these cases no changes need to be done in case of a failover - printing will
work persistently.