104 IBM Enterprise Workload Manager
service policy; therefore, it continues to use the previously activated policy that belongs to
another domain policy that is not deployed. If you encounter this state, contact an IBM
service representative for further assistance.
EWLM disabling: A user has requested to disable the managed server using the EWLM
Control Center. The managed server is in the process of ending EWLM on the server.
ARM services continues to collect performance data but it is not sent to the EWLM domain
EWLM disabled: The managed server is not running the EWLM managed server function
or the server has not attempted to join the EWLM domain. To start EWLM on this server,
you need to manually start EWLM on the server. The server remains in the list of managed
servers for up to seven days. Then, the managed server is removed from the list.
From the pull-down menu, two options are available:
Properties: This option shows you details about the managed server such as the server
name, the status, the Active Service Policy, the server architecture, if LPAR is enabled, the
EWLM version and build number.
Disable: Stops the EWLM managed server and removes it from the domain. This option is
intended for removing a server that is not functioning properly. You need to restart it with
the startMS command on the server itself; you cannot restart it from the Control Center.
A main feature of the initial release of EWLM is the reporting capability. When a policy has
been activated, you can monitor how it is running in the EWLM management domain using:
– Goal versus actuals for:
• Service classes
• Transaction classes
• Process classes
– Managed servers
Topology reports – application and server
Real time performance monitors
– Goal achievement
– Processor utilization
– Transaction count and rate
As briefly discussed in Figure 4-2 on page 81, the reporting interval can be changed by
clicking the Preferences tab. The interval can be set to 1, 5, 10, 15, 30, 45 or 60 minutes. The
reporting interval is displayed on all of the reporting panels, usually mid screen.
4.4.1 First-level reports
The first-level reports have the objective of showing performance – to project the actual
response time versus the desired goal, and to examine the CPU and the response time.
Chapter 4. Administering EWLM 105
You can start with the Exceptions report. It shows a list of services classes that are not
meeting their goals. The report lists, by service class, the service class name, performance
index, its importance, current performance, and the performance goal. This level of reporting
shows, at a glance, the problem areas within the domain.
Figure 4-22 Exceptions report
Figure 4-22 shows a sample of the Exceptions report where you can see the service classes
that are not achieving the goal. EWLM uses the Performance Index (PI) to indicate how well a
service class is attaining the goal defined for it. The Performance Index is a ratio between the
response time goal and the actual response time. A PI greater than 1 means that the goal is
being missed, while a PI less than 1 means that the goal is being met.
Table 4-4 Performance Index (PI)
On the screen, you can immediately see the PI, which can be the starting point for
understanding what caused the problem.
This report provides information organized at the workload level, including the service classes
that belong to the workload definition. A sample Workloads report is shown in Figure 4-23.
After selecting a workload, you can drill down to see each individual service classes. This
level of reporting is useful to identify the performance characteristics of a specified workload.
Situation PI value
Service Class is doing better than the goal defined for it Less than (<) 1
Service Class is attaining the goal defined for it 1
Service Class is missing the goal defined for it Greater than (>) 1