User's Guide

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.
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
62 Step-by-Step Cluster Conversion