Objectives

 

A typical minimal configuration for a WAS V5.1 installation is illustrated in Figure 1-1. There is a single Web (HTTP) server and a single appserver, and both are co-resident on a single machine.

The performance characteristics of this setup are limited by the power of the machine on which it is running, and by various constraints inherent in the configuration itself and in the implementation of WAS. A short introduction to the various components of the WebSphere runtime is provided in 1.2, WAS architecture.

Figure 1-1 Basic WebSphere configuration

We are interested in defining system configurations that exhibit the following properties:

  1. Scalability
  2. Workload management
  3. Availability
  4. Maintainability
  5. Session management
  6. Performance impacts of WAS security

Note that scaling the appserver environment does not help if your application has an unscalable design. For Web application and EJB development best practices, refer to Chapter 18, Application development: Best practices for performance and scalability and to the white paper WAS Development Best Practices for Performance and Scalability, found at:

 Next | Home

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.