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

Configuring external instances (sgesap/sapextinstance)
External dialog instances (“D” and “J”-type) can be configured into a SGeSAP package using the
sgesap/sapextinstance module. These instances can eitherbelong to the SID configured in the
package (values sap_ext_system and sap_system are identical), ora as a “foreign” SID (values of
sap_ext_system and sap_system are different). They can be started, stopped and restarted with
the package, but also stopped when the package fails over to the node where the instance is
running. A restriction that applies to instances with a foreign SID is that these can only be stopped
if the package fails on the local node.
Any instances configured with the sapextinstance module are handled on a best effort basis.
Failing to start or stop an external instance will not cause the whole package to fail. Such instances
are also not monitored by a SGeSAP service monitor. If the sapcontrol usage attribute is enabled
(enabled per default on SGeSAP/LX), SGeSAP will try to use sapcontrol commands to start and
stop instances.
For instances on remote hosts, sapcontrol will use the –host option to control the remote instance.
Note this requires that the remote instance’s sapstartsrv is already running and the required
webservices (for starting and stopping the instance) are open for remote access from the local
host (For more information, see the SAP notes 927637 and 1439348). If remote access via
sapcontrol fails and fallback access via remote shell is enabled, the remote shell will be used
instead.
The sapextinstance module also uses the attributes configured in the sgesap/sap_global
module. The attribute sgesap/sap_global/sap_system is used as the default SID,
sgesap/sap_global/rem_comm as the communication mechanism from the cluster node to
the application server.
Serviceguard Manager or the CLI interface can be used to configure the module.
NOTE: deploysappkgs cannot configure this module.
Attributes to define a single external instance are
DescriptionGUI LabelModule Attribute
Instance type and number (like D01). Only D,J
and SMDA types allowed.
External SAP Instancesap_ext_instance
SID of the external instance. If unspecified,
sap_system (the SID of the package) is assumed .
SAP System IDsap_ext_sytem
Host were the external instance resides. Virtual
hostname allowed.
Hostnamesap_ext_host
Actions on external instance (see table
Table 23 (page 72) for more information)
Contains a ‘y’ for each action to be executed, a
‘n’ if action must be skipped. List of five y/n values.
Values represented as checkboxessap_ext_treat
Table 23 Overview of reasonable treat values
DescriptionMeaningValue (. = y/n)
Application server is started with the package (own SID)start with packagey.... (position 1)
Application server is stopped with the package (own SID)Stop with package.y... (position 2)
Application server is restarted when package performs a failover
(own SID). Restart occurs on package start.
Restart during failover..y.. (position 3)
72 Clustering SAP using SGeSAP packages