Test case setup for the webApp.secure performance tests

Edit online

To perform the webApp.secure performance tests we needed to configure webApp.secure and the workload software.

webApp.secure setup

webApp.secure is distributed as an RPM file and installed with the “rpm -i” command.

webApp.secure installs in /usr/local/wa and all required customization is accomplished by the WAProperties.xml file located in /usr/local/wa/etc.

We made the following modifications to the WAProperties.xml file:
  • The IP address of the Apache HTTP Server was set to:

    <web-server-name>webserver</web-server-name>

  • A list of "entry point" URLs for the Web site was stated. These are the URL's that will be permitted access.

    <entry-point>/WebSeal_pages/*</entry-point> <entry-point>/PlantsByWebSphere/*</entry-point>

  • In the <ssl> stanza the following changes were made:
    • All SSL statements were set to:

      <enable values="True,False" default="False">True</enable>

    • To have no encryption between webApp.secure and Apache HTTP Server we set the following:

      <encrypt-to-web-server values="True,False" default="True">False</encrypt-to-web-server>

For all other webApp.secure configuration properties we used the default settings. See Detailed set up examples for the webApp.secure performance tests for the complete WAProperties.xml file we used.

Additional information on the installing and setting up of webApp.secure is available in the Welcome to webApp.secure and webApp.secure Installation and Setup Guide documents available from webScurity, Inc. at:

http://www.webscurity.com

Workload

The workload used in these tests was WebBench's static page content files. There are approximately 6000 static pages in the WebBench webserver benchmark. These files were placed on the WebSphere® Application Server in the PlantsByWebSphere directory.

An IBM® internal version of the WebSphere Studio Workload Simulator was used to drive the HTTP/HTTPS requests to the system under test. The WebSphere Studio Workload Simulator engine (iwlengine) runs on the client machine and generates requests continuously until the run time length is reached. WebSphere Studio Workload Simulator allows the specification of the number of client tasks that will be generating requests and is driven by a script.

In addition to valid file name requests, there are requests for invalid file names. The WebSphere Studio Workload Simulator script contained 6001 get or get ssl statements.