HP Serviceguard Extension for SAP (SGeSAP) manual Saplocalhostsidinstnr, SID/dbhost = relocdb

SAPLOCALHOST is set to the hostname per default at startup time and is used to build the SAP application server name:

<SAPLOCALHOST>_<SID>_<INSTNR>

This parameter represents the communication path inside an SAP system and between different SAP systems. SAPLOCALHOSTFULL is used for rfc-connections. Set it to the fully qualified hostname.

The application server name appears in the server list held by the message server, which contains all instances, hosts and services of the instances. The application server name or the hostname is also stored in some system tables on the database.

Installation Step: IS1130

If you cluster a single-instance database, you need to maintain the transport management parameters.

In the transport directory parameter file(s), e.g. /usr/sap/trans/bin/TPPARAM, modify the dbhost entry as follows:

<SID>/dbhost = <relocdb>

Optional Step: IS1140

If you have already received your licenses from SAP install them on all the nodes where the Central Instance can start.

Refer to the Serviceguard Extension for SAP Release Notes for further information on how to do this. The package comes up without a license, too. But certain restrictions apply to the SAP application.

SAP will now be ready to run on all cluster nodes. Test the manual startup on all adoptive nodes.

Installation Step: IS1150

Connect with a SAPGUI. Import the changed SAP profiles within SAP.

The transaction is called RZ10.

After importing the profiles, check with rsparam in SE38 if the parameters SAPLOCALHOST and SAPLOCALHOSTFULL are correct. If you do not import the profiles, the profiles within SAP can be edited by the SAP Administrator. The values listed from the SAP system will be wrong and, when saved, will overwrite the values which edited on the HP-UX level.

Installation Step: IS1160

The destination for print formatting, which is done by a Spool Work process, uses the application server name.

If the application server name stays the same because SAPLOCALHOST has been set to the relocatible name, after a switch no changes need to be done.

Printing works consistently. A print job in process at the time of the failure is canceled and needs to be reissued manually after the failover. To make a spooler highly available on the Central Instance server, set the destination of the printer to e.g. <relocci>_<SID>_<INSTNR> using transaction SPAD.

Installation Step: IS1170

Batch jobs can be scheduled to run on a particular instance.

You select a particular instance by its hostname at the time of job scheduling. The application server name

and the hostname retrieved from the Message Server are stored in the Batch control tables TBTCO, TBTCS...

When the batch job is ready to run, the application server name is used to start it on the appropriate instance. When using <relocci> to build the application server name for the SAP instance, you do not need to change batch jobs, which are tied to the locality, after a switchover, even if the hostname which is also stored in the above tables differs.

Installation Step: IS1180

Within the SAP Computing Center Management System (CCMS) you can define operation modes for SAP instances.

An operation mode defines a resource configuration for the instances in your SAP system. It can be used to determine which instances are started and stopped, and how the individual services are allocated for each instance in the configuration.

SAP Application Server Configuration 89