Chapter 5. The ITSO EWLM scenario 121
5.1.1 Business scenario
We implemented the following two Web applications in the ITSO environment:
򐂰
Trade3 provides online trading service for stock broker.
򐂰
Plants by WebSphere provides online shopping service for those who are interested in
gardening.
Why do we want to use EWLM? We want to view the performance of each workload
individually and in detail, as well as the AIX batch application. We want to view the
performance of shopping related transactions as a group. We want to define business goals
for each service class after load testing, since we have no Service Level Agreements (SLAs).
The purpose of the monitoring and reporting section is to guide you in creating a way to
understand performance considerations and possible performance problems in your
environment.
5.1.2 Naming convention
All EWLM components like transaction class, process class, service class, workload, and
service policy need names. These names must be in accordance with the EWLM naming
requirements, which are the following:
򐂰 Up to 64 valid characters
򐂰 The valid characters include:
Upper case alphabetic characters (A-Z)
Lower case alphabetic characters (a-z)
Numeric characters (0-9)
Blank ( )
Period (.)
Underscore (_)
Hyphen (-)
򐂰 Start with alphabetic character
򐂰 End with alphabetic character, numeric character, period, underscore, or hyphen
EWLM components often have similar names. We recommend that you set up your own
naming convention to avoid confusion. Once you decide on a naming convention, use it in
your EWLM domain consistently. As soon as your environment includes more than just a
handful of transactions it can get complicated. In Table 5-1 we show the naming convention
we used in this chapter. The ApplicationName is optional for the workload and is replaced by
appropriate application name like trade3 or plants, and _identifier is optional and is used to
distinguish the class from another within the same component. An example of a transaction
class for our test environment is TC_Trade3_shopping.
Note: There are two functions that we do not cover in this chapter:
򐂰 Integration with firewall and security
򐂰 Load balancing
Refer to Chapter 6, “Using a firewall and securing EWLM” on page 155 and Chapter 7,
“Using load balancing” on page 187 for more information on these topics.

Get IBM Enterprise Workload Manager Release 1 now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.