DB2 UDB for z/OS Version 8 Performance Topics - IBM Redbooks

A second role of the managed server layer is to gather relevant transaction-related statistics
from middleware applications and route these statistics to the EWLM domain manager. The
application middleware implementations, such as WebSphere Application Server, understand
when a piece of work starts and stops, and the middleware understands when a piece of work
has been routed to another server for processing, for example, when a WAS server routes a
request to a DB2 database server.
An important aspect of the EWLM approach is that all data collection and aggregation
activities are driven by a common service level policy, called the EWLM Domain Policy.
The final link is the EWLM Control Center. This is where all the EWLM concepts come
together; where you can create an EWLM domain policy and activate that policy on all
servers of the domain with a single click. See the following screen shots in order to get a look
and feel of the EWLM Control Center.
Figure 7-23 shows the Managed Server view of your EWLM Control Center. It provides an
overview of the status of all the managed servers in the EWLM management domain. In this
example, there is a Communication error between domain manager and managed servers on
AIX and z/OS that requires attention. The managed server on Windows appears to be
running fine as indicated by the “Active” state.
Figure 7-23 Enterprise Workload Manager Control Center - Managed servers
Figure 7-24 is an example of a server topology report. Note the location name (STLABD7) is
displayed in the diagram when DB2 for z/OS is EWLM enabled.
314 DB2 UDB for z/OS Version 8 Performance Topics