Customizing IBM Z System Automation

Edit online

Read the contained information on how to set up IBM Z System Automation (SA z/OS®) for the high availability solution for SAP, based on the *SAPSRV add-on policy.

Availability and use of the current *SAPSRV add-on policy

This edition of Business Continuity for SAP on IBM Z is based on the *SAPSRV add-on policy of SA z/OS 4.1, APAR level OA61966 and of SA z/OS 4.2, APAR level OA61966. The previous *SAP add-on policy in earlier System Automation releases is no longer part of the System Automation product.

If you have migrated your SA policy from earlier releases, and if this policy contains SAP systems that are automated with the previous *SAP add-on policy, then you can continue to use it on SA z/OS 4.1 and 4.2.

The *SAPSRV add-on policy uses the standard SAP sapstartsrv service for starting SAP instances. Thereby it enables seamless integration of an SA z/OS controlled SAP Central Services instance into SAP systems management tools, like SAP's Management Console, or into SAP life cycle tools, like the SAP Software Update Manager (SUM). Furthermore, the use of this policy is a prerequisite for using the SAP HA Interface (see SAP HA Interface for SA z/OS).

Note:
  1. Although the SAP HA wizard can significantly reduce the effort for creating a SA policy for SAP, a detailed knowledge of IBM Z System Automation is nevertheless required to make SAP high availability work.
  2. Throughout this publication, the sample SAP system ID (SID/SAPSID)
    • of SID is used for all resources that belong to SAP Central Services instances
    • of CON is used for the resources of an optional SAP Web Dispatcher
    • of SM1, SM2, and SM3 are used for the resources of optional SAP Solution Manager Diagnostics Agent (SMDA) installations.

The SAP HA wizard replaces these samples <SID>s with the actual SID of your SAP installations. If you create your SA policy without using the wizard, you need to manually replace the sample values with the SIDs (SAPSIDs) of your own SAP installation.

Features of the *SAPSRV add-on policy

The *SAPSRV add-on policy assumes that if you use an enqueue replication server, you installed it with its own virtual host name. For a rationale, see Virtual host name for the ERS instance.

Additionally, the *SAPSRV add-on policy also models the SAP host agent.

This *SAPSRV add-on policy is supported by the SAP HA wizard, which is included in the tar-file ING_sap.tar in the z/OS UNIX directory: /usr/lpp/ing/SAP.

The SAP HA wizard uses the *SAPSRV add-on policy. You can interactively construct a new SAP policy. For a detailed description of the wizard operation, see the PDF file included in the tar-file.

The *SAPSRV add-on policy includes resource definitions for remote application server resources. The SAP HA wizard supports the adaption of these resources to your specific SID. See SAP application servers as proxy resources for a description of these resources.

Note: The *SAPSRV add-on policy comes with new job names for all resources compared to the *SAP add-on policy. See Table 2 for details. You may need to adapt port bindings within the TCPIP.PROFILE, if you use this feature.

Prerequisites

The following assumes that you set up your environment, as described in Concepts for a high availability SAP solution through Customizing SAP for high availability. The *SAPSRV add-on policy is based on SAP Kernel 7.20 or higher. As a consequence, SAP Syslog Collector and Sender are no longer necessary and supported. For details on how to use the SAP central system log via HTTP or HTTPS, refer to SAP Notes 1704753, 1041390, and 2115344 in Table 1.