WebSEAL setup

For our Tivoli WebSEAL performance tests, we setup a WebSEAL junction, a connection between a WebSEAL server and a backend Web application server.

• The connection between a WebSEAL server and a back end Web application server is known as a WebSEAL junction. A WebSEAL junction is a TCP or SSL connection between a front end WebSEAL server and a back end server. The back end server can be another WebSEAL server or, more commonly, a third-party Web application server. The back end server Web space is "connected" to the WebSEAL server at a specially designated junction (mount) point in the WebSEAL Web space. A junction allows WebSEAL to provide protective services on behalf of the back end server. WebSEAL can perform authentication and authorization checks on all requests before passing those requests on to the back end server.
• WebSEAL maintains the following HTTP log files, which record HTTP activity:
  • request.log
  • agent.log
  • referer.log
  By default, these log files are located in the /var/pdweb/www-default/log directory. Stanza entries for configuring traditional HTTP logging are located in the [logging] stanza of the WebSEAL configuration file. The WebSEAL web server request logs are not automatically deleted by WebSEAL. The logs will grow until manually deleted or the file system in which they are placed becomes full. In our tests the log files, when used, were reset at the beginning of each run.