Managing HP Serviceguard Extension for SAP for Linux (May 2013)

This sgesap/sapextinstance module can also be used to configure diagnostic instances which
failover with clustered dialog instances (They start together with the dialog instance and stop
together with the dialog instance). Although technically they belong to a different SID, they can
be started and stopped with the package. The hostname to be configured is the same as the virtual
hostname of the instance configured in the package (which usually also is part of diagnostic instance
profile name). If a SMDA instance is configured, it will be displayed in the Serviceguard Manger
guided package configuration.
Example 1:
The package is associated with SAP System SG1. The primary node is also running a non-clustered
ABAP Dialog Instance with instance ID 01. It must be stopped and started with manual package
operations. In case of a failover, a restart attempt must be made on the primary node (if the primary
node is reachable from the secondary). There is a second instance D01 on a server outside of the
cluster that must similarly be started, stopped and restarted.
sap_ext_instance D01
sap_ext_host node1
sap_ext_treat yyynn
sap_ext_instance D02
sap_ext_host hostname1
sap_ext_treat yyynn
Example 2:
The failover node is running a central, non-clustered test system QAS and a dialog instance D03
of the clustered SG1. All these must be stopped in case of a failover to the node, in order to free
up resources.
sap_ext_instance DVEBMGS10
sap_ext_system QAS
sap_ext_host node2
sap_ext_treat nnnyn
sap_ext_instance D03
sap_ext_host node2
sap_ext_treat yyyyn
Example 3:
The package contains one or more dialog instances configured for vhost1 for which also a
diagnostic agent is configured. It must stop before the instances are stopped and started after the
instances are started.
sap_ext_instance SMDA97
sap_ext_system DAA
sap_ext_host vhost1
sap_ext_treat yynnn
Configuring SAP infrastructure components (sgesap/sapinfra)
The SAP infrastructure software defines software components that support a specific SAP Netweaver
Application Server, but are independent of the Server start or stop sequence.
NOTE: SAP Netweaver Application Server instances cannot be specified here.
Legal values for sgesap/sap_infra_sw_type are described in Table 25 (page 75).
Table 25 Legal values for sgesap/sap_infra_sw_type
DescriptionValue
SAP operating system monitor collectorsaposcol
SAP additional monitor collectorsapccmsr
SAP XI/PI/EAI remote function call adapterrfcadapter
Completing SGeSAP package creation (Phase 3b) 75