Managing Serviceguard Extension for SAP Version B.05.10, September 2010

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.
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.
The external SAP instance parameters may be used to configure special treatment of SAP
Application Server instances during package start, halt, or failover. These Application Servers
need not necessarily be virtualized. They must not be clustered themselves. Clustered SAP
Instances can be influenced by specifying Serviceguard package dependencies.
An attempt can be triggered to start, stop, restart, or notify instances that belong to the same SAP
system as the instances in the package.
All the triggered attempts are considered to be non-critical. If any triggered attempt fails, it
doesn't cause failure of the ongoing package operation. Don't use these parameters for
non-redundant resources and single points of failure.
An External SAP Instance defines any SAP Netweaver Application Server instance based on
the SAP ABAP technology-stack, the SAP JAVA technology-stack, or a combination of both. All
parts of the instance are treated together as a single entity. This includes instance parts like icman,
workprocesses, SAP JVMs, or an IGS. SAP infrastructure software that does not come as part of
an instance cannot be specified here.
SAP System ID defines the unique SAP System Identifier (SAP SID) to which the corresponding
external instance is associated. If no value is specified, the setting of the global SAP System ID
is assumed.
Hostname defines the hostname on which the instance resides (which might be inside or outside
of the cluster). It is also possible to specify a virtual hostname. The host can run a Linux or HP-UX
Modular Package Configuration 67