Managing HP Serviceguard Extension for SAP for Linux (May 2013)

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 24 (page 74) 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 24 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)
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.
74 Clustering SAP using SGeSAP packages