WebSphere environment

The Websphere environment used in our tests is described in this topic.

To emulate a customer-like configuration, one WebSphere® Application Server environment consisted of:
  • An IBM® HTTP web server
  • The WebSphere Application Server
  • A DB2® UDB database server
This environment is called a "triplet".

"Combination" servers were also employed where the IBM HTTP Server, WebSphere, and DB2 UDB coexist on the same Linux™ on System z® server, these servers are called "combos". The setup is shown in Figure 2. This setup represents guests with very different resource requirements at very different workload levels.

For the static portion of our test we use two triplets, and two combo servers; Triplet 1, Triplet2, Combo1 and Combo2. This is referred to in the paper as the first "Set" or "Set 1".

For the dynamic portion of the test, two additional triplets and two additional combo servers were added; Triplet 3, Triplet 4, Combo3 and Combo4. In this paper this is referred to as the second set or "Set 2".

For the static tests there are a total of eight Linux on System z guests. For the dynamic tests the total number of Linux guests is 16.

For dynamic workload testing the workload was switched to the second set after completing the workload on the first set, and then similarly back to the first set after completing the workload on the second set. This creates warmed up idling systems, which are switched from a state where the resource utilization is at its maximum to a state where the resource utilization is at its minimum.

For all tests we used two Client drivers on two System x336 systems.

Figure 1. Setup for one set of servers and a targeted load
A flow diagram showing setup for one set of servers and a targeted load