WebSphere Application Server Topology Options

1. © 2009 IBM Corporation
WebSphere Application Server
Topology

2. © 2009 IBM Corporation
Stand-alone server topology
• Installation of WAS on one single (physical) machine or logical partition (LPAR)
with one application server only.
• No load balancing or high availability at all

3. © 2009 IBM Corporation
Vertical scaling topology
• This vertical scaling example includes a cluster and three cluster members.
• Basic load balancing is performed at the Web server plug-in level based on a
weighted round-robin algorithm

4. © 2009 IBM Corporation
Horizontal scaling topology
• Horizontal scaling means to create one logical unit of servers across multiple
systems or LPARs where each member of the unit is able to serve each request.
• Does not require an IP sprayer, but if you want to scale at the Web server tier as
well, then it will require an IP sprayer

5. © 2009 IBM Corporation
Horizontal scaling topology (with Load Balancer)
 Both Web servers are active at the same time and perform load balancing and failover between the
application servers in the cluster through the Web server plug-in.
 The active Load Balancer sprays requests to the Web servers.

6. © 2009 IBM Corporation
Reverse proxy topology
 Reverse proxy servers, like the one provided with the Edge components or the DMZ secure proxy, are
typically used in DMZ configurations for two major reasons:
 To provide additional security between the public Internet and the Web servers (and application
servers)
 To increase performance and reduce the load on the servers by content caching

7. © 2009 IBM Corporation
Topology with redundancy of multiple components