Maximizing Performance and Scalability with IBM WebSphere

Chapter 1: The Need for Performance

Figure 1-1: The operations and performance methodologies intersect

Figure 1-2: The operations and performance methodologies intersect, with an increase in performance

Figure 1-3: Performance management model

Figure 1-4: Costs for mitigating performance issues, immediate and future

Figure 1-5: Pre- and post-upgrade support costs for an example platform

Figure 1-6: Pre- and post-upgrade support costs for an example platform, the optimized approach

Figure 1-7: Indicative operational costs, initial outlay

Figure 1-8: Comparing costs of both options

Figure 1-9: The second-year cost comparison of both options

Figure 1-10: A two-year TCO comparison of both options

Figure 1-11: The waterfall model

Figure 1-12: Correctly configured environmentthe funnel, or carrot -shaped, model

Chapter 3: WebSphere 4 and 5 Component Architectures

Figure 3-1: Example WebSphere HTTP plug-in topology

Figure 3-2: Web container services within WebSphere

Figure 3-3: EJB container insulation and implementation

Figure 3-4: Server group association with WebSphere 4 components

Figure 3-5: WebSphere 4 cloning and workload management flowchart

Figure 3-6: WebSphere 5 standard deployment component architecture

Figure 3-7: WebSphere 5 network deployment component architecture

Chapter 4: WebSphere Infrastructure Design

Figure 4-1: High-level iSCSI implementation

Figure 4-2: High-level SAN implementation

Figure 4-3: FCAL architecture

Figure 4-4: Distributed storage architecture example

Figure 4-5: Disk performance overview

Figure 4-6: Storage support costs

Figure 4-7: Storage implementation costs

Chapter 5: WebSphere Deployment and Network Architecture

Figure 5-1: Horizontal scaling example with WebSphere

Figure 5-2: Example of a horizontally and vertically scaled environment

Figure 5-3: An example garbage collection monitoring graph

Figure 5-4: Major network types within a WebSphere topological architecture

Figure 5-5: Overhead associated with communications via a firewall for heavy transaction data

Figure 5-6: A thin Web server configuration

Figure 5-7: A 3- tier firewall topology

Figure 5-8: Abstraction layer for the Web tier

Figure 5-9: An example high-level single-channel topology

Figure 5-10: A high-level, single-channel, 2-tier topology

Figure 5-11: A high-level, single-channel, 3-tier topology

Figure 5-12: A high-level, 3-tier, multi-JVM topology

Figure 5-13: Multiple JVM transaction considerations

Figure 5-14: The dual Web server thin model

Figure 5-15: The dual Web server thick model

Figure 5-16: Component mapping for a thick Web server topology

Figure 5-17: A basic J2EE application operating under WebSphere

Figure 5-18: A split Web and EJB container JVM configuration

Figure 5-19: A dual Web, single application server, dual JVM topology

Figure 5-20: A multi-Web server, multiapplication server topology

Figure 5-21: Single points of failure in a WebSphere environment

Figure 5-22: Multiple application servers with multiple application JVMs

Figure 5-23: WebSphere high-availability extension

Figure 5-24: An active-standby database failover

Figure 5-25: An active-active database configuration

Figure 5-26: Geographically distributed Web servers

Figure 5-27: A compartmentalized server approach

Chapter 6: WebSphere Platform Performance, Tuning, and Optimization

Figure 6-1: An end-to-end measurement

Figure 6-2: Lightweight versus heavyweight transaction characteristics

Figure 6-3: Database connection usage

Figure 6-4: Example logging of garbage collection

Figure 6-5: Historic garbage collection logging

Figure 6-6: Correct queuing configuration, the Carrot model

Figure 6-7: Example queuing model

Chapter 7: WebSphere Failover and High Availability Considerations

Figure 7-1: An active-standby cluster configuration before failover

Figure 7-2: An active-standby cluster configuration after failover

Figure 7-3: An active-active cluster configuration before failover

Figure 7-4: An active-active cluster configuration after failover

Figure 7-5: A disaster recovery hot site topology

Figure 7-6: A complex WebSphere high availability environment

Figure 7-7: Web server failover and high availability model

Figure 7-8: Global routing example

Figure 7-9: Global routing example failover scenario

Figure 7-10: Dual application server configuration

Figure 7-11: An example of session management with WebSphere

Figure 7-12: An example of session management with WebSphere in a failover scenario

Figure 7-13: EJB container failover in WebSphere version 4

Chapter 8: External WebSphere System Availability

Figure 8-1: High-availability LDAP implementation

Figure 8-2: Basic NFS implementation

Figure 8-3: Highly available NFS implementation

Chapter 9: WebSphere EJB and Web Container Performance

Figure 9-1: High-level application server framework container view

Figure 9-2: Web container view

Figure 9-3: EJB container view

Figure 9-4: WebSphere version 4 administration console

Figure 9-5: EJB Container Service dialog box in WebSphere version 4

Figure 9-6: EJB container services in WebSphere version 5

Figure 9-7: The Web Container Service dialog box in WebSphere version 4

Figure 9-8: Web container services in WebSphere version 5

Chapter 11: WebSphere Database Performance and Optimization

Figure 11-1: Example DAO pattern implementation

Figure 11-2: JDBC type 1 driver implementation

Figure 11-3: JDBC type 2 driver implementation

Figure 11-4: JDBC type 3 driver implementation

Figure 11-5: JDBC type 4 driver implementation

Figure 11-6: Oracle 8 i /9 i high-level architecture

Figure 11-7: DB2 architectural overview

Figure 11-8: WebSphere pool manager connection architecture

Figure 11-9: Configuring the WebSphere 4 pool manager connection

Figure 11-10: WebSphere 5 Pool Manager Connection dialog box

Chapter 12: Legacy Integration: Performance Optimization

Figure 12-1: Example integration of a WebSphere/J2EE application with a legacy application

Figure 12-2: Example CORBA and WebSphere implementation

Figure 12-3: Example CORBA and WebSphere transaction

Figure 12-4: MQ Series communications with WebSphere

Figure 12-5: Web Service communications with WebSphere

Chapter 13: Performance Management Tooling

Figure 13-1: The Performance tool console

Figure 13-2: Adding a new monitor

Figure 13-3: Selecting the monitor agents

Figure 13-4: Adding the % Processor Time counter

Figure 13-5: Buttons to give you different views of the data

Figure 13-6: Graphing Queue Length and % Disk Time

Figure 13-7: Adding network error counters

Figure 13-8: Network utilization output

Chapter 14: Profiling and Benchmarking WebSphere

Figure 14-1: Performance management methodogy

Figure 14-2: Using JProbe

Figure 14-3: JProbe Memory Profiler

Figure 14-4: JProbe extended memory profiler

Figure 14-5: HPjmeter

Figure 14-6: Resource Analyzer

Figure 14-7: Tivoli Performance Viewer

Figure 14-8: WSAD Profile view