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

sap_ext_treat defines the way the instance is treated if the status of the package changes.
sap_ext_treat values are of a sequence of five 'y' and 'n' characters, each position representing
the activation or deactiviation of a feature.
Set the 1. position to 'y' to automatically make an attempt to start the instance with each package
startup operation.
Set the 2. position to 'y' to automatically make an attempt to stop the instance with each package
shutdown operation.
Set the 3. position to 'y' to automatically make an attempt to restart the instance with each package
failover operation.
Set the 4. position to 'y' to automatically shut down the instance if the package starts on the node
on which it is running.
Position 5 is currently not in use.
If a specified instance is a Central Instance and other specified instances depend on it, the shutdown
sequence will make sure that this Central Instance will always be started before and stopped after
the depending instances. Apart from that rule, several instance operations will be triggered in
parallel.
The first three positions in the treatment string are only effective if the instances do belong to the
SAP system to which the package is associated (sap_ext_system=sap_system). The fourth
position can also be set for any other SAP system, in order to allow system consolidation.
Example 1:
The package is associated to SAP System SG1. The primary node is also running a non-clustered
ABAP Dialog Instance with instance ID 01. It should be stopped and started with manual package
operations. In case of a failover, a restart attempt should 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 should 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 testsystem QAS and a dialog instance D03
of the clustered SG1. All this should 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
Subsection for additional SAP infrastructure software handling: OS472
Parameters to influence SAP software that runs outside of SAP Application Server Instances come
with module sgesap/sapinfra.
sap_infra_sw_type defines a SAP infrastructure software component that is to be covered by
the package. Such software pieces often support a specific SAP Netweaver Application Server,
but they won't get started and/or stopped as part of the Instance. SAP Netweaver Application
Server Instances are not specified here, but by using the sap_instance attribute. Legal values
for sap_infra_sw_type:
saposcol = a SAP operating system monitor collector
86 Step-by-Step Cluster Conversion