Managing Serviceguard Extension for SAP on Integrity Linux, December 2005

Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances
Application Configuration
Chapter 288
IS1040 Installation Step:
Import the changed SAP profiles via SAP transaction RZ10.
IS1050 Installation Step:
The destination for print formatting, which is done by a Spool Work
process, uses the application server name. To make a spooler highly
available on the Central Instance server, set the destination of the
printer to <relocci>_<SID>_<INSTNR> using transaction SPAD.
IS1060 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.
IS1070 Installation Step:
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.
An instance definition for a particular operation mode consist of the
number and types of work processes as well as start and instance
profiles.
When defining an instance for an operation mode, enter the hostname
and the system number of the application server. By using <relocci> to
fill in the hostname field, the instance is working under control of the
CCMS after a failover without any change.