Managing Serviceguard Extension for SAP Version A.06.00 for Linux, December 2012

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 24 (page 74).
Table 24 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
SAP webdispatcher (not installed as SAP instance, but
unpacked and bootstrapped to
/usr/sap/<SID>/sapwebdisp)
sapwebdisp
SAP software network routing toolsaprouter
The values saprouter and biamaster can be specified more than once.
The attribute sap_infra_treat defines whether the component will only be started/notified
with the package startup, or whether it will also be stopped as part of a package shutdown (default).
Possible values are startonly and startnstop.
sap_infra_sw_params defines additional command line parameters to be called with the
component. A sap_infra_sw_host value can be added to specify the hostname where to
start a BIA master instance. This parameter will be ignored for other infrastructure components,
which always get started/stopped locally.
Examples:
sap_infra_sw_type saposcol
sap_infra_sw_type saprouter
sap_infra_sw_treat startnstop
sap_infra_sw_params "-H virtual_IP -W 20000\
-R /sapmnt/C11/profile/saprouttab\
-T /sapmnt/C11/profile/dev_rout1"
74 Clustering SAP using SGeSAP packages