IBM Enterprise Workload Manager Release 1

82 IBM Enterprise Workload Manager

4.2 Setup function of the Control Center

This section describes how to set up the domain policy that defines the performance goals for

the workload running in your management domain. Work running in a multi-tiered

heterogeneous environment can be categorized into

transactions and processes. For both

transaction- and process-oriented work, EWLM provides reporting based on performance

goals defined in a service policy, which is similar to a service level agreement. Before going

into the details of how to set up your policies, let’s get familiar with some terminology first.

You are already familiar with the concept of a

management domain, a heterogeneous

environment comprised of a collection of managed servers and a domain manager. In this

environment, the

domain manager is the central point of control for a domain.

A management domain defines the environment in which a service policy runs. Only one

service policy is active in a management domain at any given time and this policy applies to

all managed servers in the domain. If no user-defined service policy has been activated, the

domain runs with a Default service policy.

Domain policy

You can think of a domain policy as a contract which prescribes how EWLM should treat

“work” within a management domain. This treatment may include how the work should be

classified, prioritized, managed, reported, and so forth.

A domain policy is a collection of service policies, applications, transaction classes, service

classes, and optionally platforms and process classes for an EWLM management domain.

The structural view of the components is shown in Figure 4-3. In the following sections we

look at each component in turn and describe the relation of these components to each other.

Figure 4-3 Structural view of domain policy

Service policy

A service policy describes the business performance objective and the business importance

of work running in a heterogeneous installation. It describes the business view of workloads

and ties it to the reporting and implicit management of the workloads. It does not contain any

explicit linkage to server topology or middleware. You can have several service policies that

Chapter 4. Administering EWLM 83

identify different performance objectives intended for different times. For example, you might

have one service policy for weekday processing and another one for month-end processing.

Similar to a service level agreement contract, a service policy is defined by a name and

consists of service classes, transaction classes, process classes, and optionally, defined

workload.

While you can define multiple service policies depending on your installation objectives,

service classes typically are the same for multiple policies. They usually differ in their goal

settings only. However, in many cases a single service policy is sufficient.

Generally, all transactions running in the management domain will be assigned to a service

class, whether a default service class for an application environment or an EWLM service

class. There is only one set of transaction classes and process classes in a Domain Policy.

You can assign these transaction classes and process classes to the multiple service policies

within the Domain Policy.

As shown in Figure 4-4, you can have multiple service policies defined in the domain policy,

representing different objectives for your enterprise. In this illustration, both service policies

(weekend and week day) share the same service classes (Web banking and Stock sales); the

only difference is that the performance goal for the service classes is slightly different to

represent the different performance objective.

Figure 4-4 Service policy