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

The SGeSAP ENQueue Operation Resource (ENQOR) needs to be specified for each SCS, ASCS
or ERS instance. The monitoring resource is provided by SGeSAP within the HP-UX Event Monitoring
System (EMS). It does not need to be created. It is available, if the system has an SAP system
installed, that uses [A]SCS/ERS instance pairs.
Available resources can be checked with the command:
resls /applications/sap/enqor
The required resource has the name /applications/sap/enqor/<SID >ers<instnr> for
applications based on SAP kernel SAP 7.x.
NOTE: The required resource has the name /applications/sap/enqor/<SID >scs or for
SAP applications based on kernel 4.x or 6.x.
Example entries for a package that clusters a [A]SCS instance that is replicated within instance
ERS21:
resource_name /applications/sap/enqor/C11ers21
resource_polling_interval 30
resource_start automatic
resource_up_value != IDLE
NOTE: If the package clusters SCS and ASCS instance, two enqor resources need to be defined.
Example entries for a package that clusters the replication instance ERS21:
resource_name /applications/sap/enqor/C11ers21
resource_polling_interval 30
resource_start automatic
resource_up_value != SERVING
Subsection for external Application Server handling: OS471
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 following 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. An attempt can be triggered to shutdown instances that
belong to any other SAP system (details are given below).
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.
A sap_ext_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 can not be specified here.
sap_ext_system defines the unique SAP System Identifier (SAP SID) to which the corresponding
sap_ext_instance is associated. If no value is specified, the setting of sap_system is assumed.
sap_ext_host 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 operating environment. If the value is not specified, the local hostname computed during a
package operation gets substituted.
Modular Package Configuration 85