IBM WebSphere Studio Workload Simulator

Tier one in this test scenario represents the presentation and user interaction layer.

Generally, it runs on client systems and accesses the application layer over a network connection. Typically such a network connection is SSL secured in production environments. In the case of DayTrader you require a client workload driver to generate some load.

The client application used for the System Under Test (SUT) is the IBM® Websphere Studio Workload Simulator. It is a command line-based IBM internal application that simplifies the automation of test cases.

There are also couple of Open Source developed solutions available such as, Apache JMeter, The Grinder or OpenSTA, which also would meet the requirements.

Sample output: IBM WebSphere® Studio Workload Simulator

# clients 25/25 | rd 13.7728 MB/s | wr 0.6585 MB/s | pg 1009415 | web err 0 
| resp avg = 0.006 | pg elem/s = 1673.833 
IWL0058I Time limit of 600 seconds has been reached.  Shutting down.
IWL0038I Run time = 00:10:05
IWL0007I Clients completed = 0/25
IWL0059I Page elements = 1009441 
IWL0060I Page element throughput = 1668.327 /s
IWL0059I Transactions = 836071 
IWL0060I Transaction throughput = 1381.794 /s
IWL0059I Network I/O errors = 0 
IWL0059I Web server errors = 0 
IWL0059I Num of pages retrieved = 1009416 
IWL0060I Page throughput = 1668.285 /s
IWL0060I HTTP data read = 8350.907 MB
IWL0060I HTTP data written = 396.831 MB
IWL0060I HTTP avg. page element response time = 0.006 
IWL0059I HTTP avg. page element response time = 0 (with all clients concurrently running)

Based on such a report the performance of the SUT can evaluated and compared against other test scenarios or runs with different IBM WebSphere Application Server (WAS) parameters.

Several runs were done for test scenarios involving different System z® cryptographic features. The results can be easily compared to each other based on the transaction numbers reported.