HP Serviceguard Extension for SAP (SGeSAP) manual

These Application Servers are not necessarily virtualized or secured by Serviceguard, but an attempt can be triggered to start, stop or restart them with the package. If any triggered attempt fails, it doesn't automatically cause failure of the ongoing package operation. The attempts are considered to be non-critical. In certain setups, it is necessary to free up resources on the failover node to allow the failover to succeed. Often, this includes stopping less important SAP Systems, namely consolidation or development environments. If any of these instances is a Central Instance, it might be that there are additional Application Servers belonging to it. Not all of them are necessarily running locally on the failover node. They can optionally be stopped before the Central Instance gets shut down. This mechanism replaces the deprecated SERVER_CONSOLIDATION variable and the RM*arrays of earlier SGeSAP 3.x versions.

•In the ASSID[*]-arrayspecify the SAP System IDs of the instances that should be treated with the package. Making this a configurable option allows to specify instances that belong to the clustered SAP components. It also allows specification of different SIDs for less critical SAP applications.

•In the ASHOST[*]-array, refer to the hosts on which the instances reside - this can be either inside or outside of the cluster.

•The ASNAME[*]-arrayholds the instance names. These names are built by the abbreviations of the services that are offered by the Application Server. The name of a Dialog instance usually is D, the name of a Central Instance often is DVEBMGS.

•The ASNR[*]-arraycontains the instance IDs. If the corresponding ASHOST-entryspecifies a host that is part of the cluster, be sure to provide an ID that is different form the IDs used by any packaged instance. You should also make sure that there is no other SAP instance on the same host is using that ID.

•The ASTREAT[*]-arraydefines the way the instance is treated if the status of the package changes. There are five different values that may be configured in any combination: START_WITH_PKG,

STOP_WITH_PKG, RESTART_DURING_FAILOVER, STOP_IF_LOCAL_AFTER_FAILOVER, STOP_DEPENDENT_INSTANCES.

•ASTREAT[*]=0means that the Application Server is not affected by any changes that happens to the package status. This value makes sense to (temporarily) unconfigure the instance.

•${START_WITH_PKG}: Add 1 to ASTREAT[*] if the Application Server should automatically be started during startup of the package.

•${STOP_WITH_PKG}: Add 2 to ASTREAT[*] if the Application Server should automatically be stopped during halt of the package.

•${RESTART_DURING_FAILOVER}: Add 4 to ASTREAT[*] if the Application Server should automatically be restarted if a failover of the package occurs. If the restart option is not used the SAP ABAP Engine has to be configure to use DB-RECONNECT.

•${STOP_IF_LOCAL_AFTER_FAILOVER}: Add 8 to ASTREAT[*] if the Application Server should automatically be shut down if the package fails over to its node. This treatment policy will overrule the ${RESTART_DURING_FAILOVER} value if applicable.

•${STOP_DEPENDENT_INSTANCES}: Add 16 to ASTREAT[*] if the instance is a Central Instance and all specified Dialog Instances with the same ASSID[] should be stopped prior to it. This treatment policy overrules the treatment policies specified for Dialog Instances.

•For the ASPLATFORM[*]-arraythe platform for an Application Server that is controlled by the package is specified. Supported values are:

•"HP-UX": standard Application server running on HP-UX

•"LINUX": standard Application server running on LINUX

•"WINDOWS": Application Server handling is not standardized as there is no standard way to open a remote DOS/Windows shell that starts SAP Application Servers on the Windows platform. sap.functions provides demo functions using the ATAMAN (TM) TCP Remote Logon syntax. They should be replaced by implementations in customer.functions.

•"SG-PACKAGE": The Application Server runs as Serviceguard package within the same cluster. In this case ASHOST might have different values on the different package nodes. If this value is

Legacy Package Configuration 73