Hardware equipment and software environment for the webApp.Secure performance tests
To perform our webApp.secure tests, we created a customer-like environment. We configured the hardware and software, network, storage server, and the DMZ.
Hardware and Software
The following section lists the hardware, software, network, configurations, and test environment we used for our webApp.secure test runs.
Host hardware
Two LPARs on a 16-way IBM® System
z9™, type 2094-S18:
- One LPAR for z/VM® equipped with:
- 3, 4, or 5 CPs, dedicated
- 5 GB memory, 0.5 GB expanded memory
- OSA Express 2 gigabit Ethernet card (OSA code level 0805)
- HiperSockets™ connection (LPAR to LPAR)
- One LPAR for z/OS® equipped with:
- 2 CPs, dedicated
- 4 GB memory
- HiperSockets connection (LPAR to LPAR)
Network setup
- The z/VM LPAR was connected to the client using a Fiber Gigabit Ethernet Interface
- The z/VM guests used virtual guest LAN(s) configured as type HiperSockets with a maximum frame size (MFS) of 24 KB
- The z/VM LPAR and the z/OS LPAR were connected via a HiperSockets connection
Storage server setup
Enterprise Storage Server® (ESS)
2105 800
- IBM 3390 disk model 3
- Physical DDMs with 15,000 RPMs
Client hardware
One x330 PC with two processors, 1.26 GHz
Software
| Product | Version/Level |
|---|---|
| Apache HTTP Server | 2.0.49 |
| Red Hat Enterprise Linux® | RHEL 4 ES (client) |
| SUSE Linux Enterprise Server | SLES9 SP3 |
| webApp.secure | 3.0-1 |
| WebSphere® Application Server for z/OS | 6.0.2 |
| WebSphere Studio Workload Simulator | iwl-0-03309L (client) |
| z/OS | 1.07 |
| z/VM | 5.2 |
z/VM guest configuration
Each unit of the DMZ (firewall, Web server, webApp.secure server) was implemented in a separate Linux guest. The z/VM guests were interconnected by a z/VM guest LAN configured as type HiperSockets. All guests ran SLES9 SP3.