WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

5.2 Terminology
5.2.1 Load balancers
Table 5-3 Topology selection based on security requirements
Requirement = security Solution/topology
Web server ► Separate the Web server into a DMZ, either on
LPAR or separate system.
► Use a DMZ secure proxy instead of Web server
with WebSphere plug-in.
► Separate administrative traffic from productive
traffic
Application server ► Implement WebSphere Application Server
security.
► Create a separate network tier for the
application server.
► Separate the application servers from the
database and EIS layer
► Separate administrative traffic from productive
traffic
Before examining the topologies, take a minute to review the following
terminology. These are elements that you will see in the diagrams describing
each topology.
A load balancer, also referred to as an IP sprayer, enables horizontal scalability
by dispatching TCP/IP traffic among several identically configured servers.
Depending on the product used for load balancing, different protocols are
supported.
In our topologies, the load balancer is implemented using the Load Balancer
Edge component provided with the Network Deployment package, which
provides load balancing capabilities for HTTP, FTP, SSL, SMTP, NNTP, IMAP,
POP3, Telnet, SIP, and any other TCP based application.
Note: On the z/OS platform, the function that provides intelligent load
balancing is the Sysplex Distributor. It balances incoming requests based on
real-time information about whether the possible members achieve their
performance goals. The member with the best performance rating processes
the incoming request.
134 WebSphere Application Server V7.0: Concepts, Planning, and Design