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

Table 23 Overview of reasonable treat values (continued)
DescriptionMeaningValue (. = y/n)
Application server is stopped when package fails over to local
node, that is on the same node where the application server is
currently running (own & foreign SID)
Stop if package local...y. (position 4)
Reserved for future used....y (position 5)
Figure 20 Configuring sapextinstance screen
Supported operating systems for running external instances are Linux, HP-UX and Microsoft
Windows-Server. For Windows the example functions start_WINDOWS_app and
stop_WINDOWS_app must be adapted to the remote communication mechanism used on the
Windows Server. In this case, there must be a customer specific version of these functions in
customer_functions.sh.
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:
Completing SGeSAP package creation (Phase 3b) 73