Overview of the add-on policy for SAP

Edit online

This information together with the contained subtopics provide an understanding of the resources that are defined in the *SAPSRV add-on policy. With this knowledge, you can determine, which of these resources are required for your specific environment.

The following SAP-related components are defined in the SA z/OS® *SAPSRV add-on policy. Not all of the components might be needed for your specific environment. For example, for an ABAP-only SAP system you do not need the Java™ components. Therefore, the first step in adapting the policy for a specific SAP system is to determine which parts of the policy you actually want to exploit.

The SAP HA wizard detects, based on the available SAP configuration files, which SAP components are to be automated and it generates a policy that contains these components.

The SA resources that might be relevant for an SAP system can be classified as follows:

  • Resources that are related to a specific SAP system:
    • Db2® z/OS resources
    • ABAP central services - including enqueue server and message server, and the associated VIPA.
    • ABAP enqueue replication server and the associated ABAP ERS VIPA
    • Java central services - including enqueue server and message server, and the associated VIPA
    • Java enqueue replication server and the associated JAVA ERS VIPA.
    • SAP Java Gateway
      With SAP 7.1 and higher, the SAP Java SCS has its own stand-alone gateway process that is modeled as a resource in the SA z/OS *SAPSRV add-on policy
    • Remote SAP application servers
  • Resources that are common to all the SAP systems:
    • NFS server
    • SAProuter or SAP Web Dispatcher or both
    • SAP Host Agent executables to monitor a host (LPAR) with SAP NetWeaver components
    • SAP Solution Manager Diagnostics Agent (SMDA).