Download PDF - IBM Redbooks

must ensure that there is consistency in the performance goals for workloads that run across
the distributed and the z/OS platforms at the same time (in the ensemble).
The only exception is when the middleware of the workload is ARM instrumented. In such a
configuration, the middleware can move the correlator to the z/OS, and the System z IBM
Workload Manager (WLM) can recognize the presence of the correlator and perform the
classification by using the correlator as a filter.
2.11 SAP on the zEnterprise System
With the zEnterprise System, clients can now deploy an integrated hardware environment
that brings mainframe and distributed technologies together. This section addresses
integrating the server portfolio and the SAP solution portfolio. It also explains the zEnterprise
System and the 3-tier architecture. It concludes by explaining the business value of using the
zEnterprise System.
2.11.1 Integrating the server portfolio
SAP on System z is usually a heterogeneous landscape. In many cases, only the database is
running on System z, especially for availability and scalability reasons.
Such a heterogeneous setup, in which the SAP NetWeaver ASs can run on different hosts,
causes administrative, organizational, and functional overhead. To set up and operate the
network, the servers, and the operating system infrastructure, a profound expertise and
various areas of responsibilities are required.
This setup poses challenges when problems arise. To analyze the root cause of a problem,
people from various functional areas with a diverse set of analysis tools (often from various
vendors) are involved, which is where the zEnterprise System helps. With a standard
zEnterprise System configuration, you can implement different SAP instances on System z or
on System p. Figure 2-9 on page 26 shows an example of this setup.
Chapter 2. Architectural overview of SAP NetWeaver with DB2 for z/OS 25