Automating using IBM Z System Automation

Edit online

All vital components are placed on the z/OS® platform.

As depicted in Figure 1, IBM Z System Automation is the focal point to manage the local SAP resources on z/OS and the remote application server resources. It integrates with SAP's sapstartsrv framework and infrastructure. The environment is automated with System Automation only. Note that this is the only supported solution, if you want to include a Windows application server under System Automation control.

Note: In the following, the phrase integrates with SAP's sapstartsrv framework and infrastructure also implies that the *SAPSRV add-on policy 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 lifecycle tools, like the SAP Software Update Manager (SUM).
Figure 1. Automation using SA z/OS
Automation using SA z/OS

The ABAP or Java™ application servers are controlled via proxy resources.

SA z/OS controls and automates all SAP-related components that run under z/OS or z/OS UNIX. In addition, SA z/OS also controls the remote SAP application server instances through proxy resources. The definition of these proxy resources must have the following features:

  • Include mechanisms to issue SSH commands to the remote machines to start and stop the application servers. SSH has the advantage that it can be set up using keys for authorization, which enables transparent log-in on a remote application server. Transparent means, that a script can log in without providing a password or a password phrase.
  • Include mechanism to use TCP/IP - based monitoring via the samsapctrl_asping utility (see ABAP application server instances and Java application server instances).

Therefore, SA z/OS controls:

  • Db2® z/OS data sharing members
  • SAP Central Services (for ABAP, or for Java, or for both)
  • Application servers on AIX®, Linux®, or Windows via proxy resources
  • NFS server
  • SAP host agent
  • Other SAP utilities that can run under z/OS or z/OS UNIX, for example, SAP Web Dispatcher, or the Solution Manager Diagnostics Agent.

Non-z/OS SAP resources like other utilities that have an affinity to the application server are outside the control of SA z/OS. These resources are not highly available.

The sample scripts that are used to control the application servers on AIX, Linux, or Windows do not run on the application server itself. They use SSH to execute commands on the application servers, for example, to start or stop an application server.

This configuration implies that you have SAP components that are running on two different platforms:

  • The SAP Central Services on z/OS UNIX, and
  • The SAP application servers on AIX, Linux, or Windows.