Managing Serviceguard Extension for SAP Version B.05.10, December 2012

The Virtual Hostname parameter corresponds to the virtual hostname that got specified during SAP
installation. The SAP virtual hostname is a string value. It is not possible to specify the corresponding
IPv4 or IPv6 address. If the string is empty, the DNS resolution of the first specified package
ip_address parameter will be substituted. In this case, the script only works properly if reliable
address resolution is available. Domain name extensions are not part of the virtual hostname. SAP
Enqueue Replication Service instances (ERS) have the purpose to keep track of the runtime status
of a SAP Central Service instance. They allow for a more seamless failover experience. For each
SAP Replication Service that is part of the package, the corresponding, replicated Central Service
instance, needs to be specified in the Replicated Instance field.
GI040 Select the database that is to be clustered (sgesap/sapdatabase module)
These settings determine the name of the database (schema) for SAP. Optionally,
listener_name can be set if the Oracle listener is defined with a name different from the
default value LISTENER.
Optionally, listener_password can be set if a password for the Oracle listener process is
configured. The root user and any user with a defined Serviceguard access role (full admin, package
admin or monitor) will be able to read this value.
The sgesap/dbinstance module can be used for SAP JAVA-only, ABAP-only, or dual stack
database instances.
The module will detect all available SAP tools to handle the database and use them if possible. If
no SAP tools are there or the SAP tools fail to work, a fallback is implemented to handle the
database with generic tools of the database vendor.
1. Select a database technology by clicking on one of the provided DB Vendor radio buttons.
2. In most situations, Serviceguard Manager Auto-Discovery can discover the databases in the
cluster. If Serviceguard Manager can discover the databases, you can either select a database
from the drop-down list, or enter a database manually. If Serviceguard Manager cannot
auto-discover databases in the cluster, the Select or Enter Database Name feature will not
appear. Instead, a field labeled, DB Name is shown—you must enter a database name into
the DB Name field. Usually this is a three letter name, similar to a SAP System ID value (SID).
If the value is not specified, but a DB Vendor has been set, it is assumed that the database
name equals the SAP System ID that has already been chosen.
3. For SAP MaxDB database: optionally, a Maxdb Userkey can be chosen that is mapped for
the operating system level administrator to the database control user (via XUSER settings). The
value needs to be set if the default control userkey is not available for usage.
4. For Oracle database: a Listener Name and a Listener Password can be specified. The password
will not be written out explicitly in any subsequent Serviceguard Manager dialog. The password
is not protected against root access to the filesystem and it will be transferred on the network
connections between the nodes as part of configuration exchange operations. If the password
parameter needs to be used, make sure that these networks are trusted.
5. For Sybase database: optionally, an ASE User and Password can be specified. If SAP
mechanisms fail or are not available, this option provides database native monitoring and
shutdown in case SAP mechanisms fail or are not available. The password is not written out
explicitly in any subsequent Serviceguard Manager dialog. The password is not protected
against root access to the filesystem and it is transferred on the network connections between
the nodes as part of configuration exchange operations. If the password parameter needs to
be used, make sure that these networks are trusted.
GI050 Specify influence on external instance (sgesap/sapextinstance module).
Parameters that can be set to influence non-critical additional instances on cluster nodes or outside
of the cluster ("external Application Servers") if module sgesap/sapextinstance is used. In
certain setups, it is necessary to free up resources on the failover node to allow the failover to
succeed. Often, this includes the stop of less important SAP Systems, namely consolidation or
development environments.
76 Step-by-Step Cluster Conversion