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

Step-by-Step Cluster Conversion
SAP WAS System Configuration
Chapter 3178
IS1150 Installation Step:
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.
IS1160 Installation Step:
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.
IS1170 Installation Step:
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.