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

The external SAP instance parameters may be used to configure special treatment of SAP Application
Server instances during package start, halt, or failover. These Application Servers need not
necessarily be virtualized. They must not be clustered themselves. Clustered SAP Instances can be
influenced by specifying Serviceguard package dependencies.
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.
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.
An External SAP 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 cannot be specified here.
SAP System ID defines the unique SAP System Identifier (SAP SID) to which the corresponding
external instance is associated. If no value is specified, the setting of the global SAP System ID is
assumed.
Hostname 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.
To remove a configured external SAP instance from this list, click on the radio button adjacent to
the external SAP instance that you want to remove, then click Remove.
To edit a configured external SAP instance, click on the radio button adjacent to the SAP instance
you want to edit, then click Edit>>. The SAP instance information will move to the SAP System ID
input field, External SAP Instance input field, Hostname input field, Start With Package checkbox,
Stop With Package checkbox, Restart With Package checkbox, and Stop If On Same Node As
Package checkbox—where you can make changes. Click Update and the edited SAP instance
information will be returned to the Configured External SAP Instances list.
To add an external SAP instance to the Configured External SAP Instances list, enter information
into the SAP System ID input field, External SAP Instance input field, Hostname input field, Start
With Package checkbox, Stop With Package checkbox, Restart With Package checkbox, and Stop
If On Same Node As Package checkbox. Click <<Add to move this information to the Configured
External SAP Instances list.
To clear the input fields, click Reset Input Fields.
GI060 Influence SAP software infrastructure tools (sgesap/sapinfra module).
The SAP infrastructure software component is software pieces that 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.
Legal values for sap_infra_sw_type:
saposcol = a SAP operating system monitor collector
sapccmsr = SAP additional monitor collector
rfcadapter = a SAP XI/PI/EAI remote function call adapter
sapwebdisp = a SAP webdispatcher
The following value can be specified more than once:
saprouter = a SAP software network routing tool
To add an SAP infrastructure software component to the Configured SAP Infrastructure Software
Components list, enter information into the Type, Start/Stop, and Parameters input fields. Click
<<Add to move this information to the Configured SAP Infrastructure Software Components list.
Modular Package Configuration 77