Skip to main content

Patterns for e-business > Select Custom design > Select Non-Functional Requirement > Review Runtime patterns > Review Product mappings >
c


Non-Functional Requirements::High Performance: Product mappings - Windows 2000

Product mappings correlate real products with one or more runtime nodes. Recall that the High Performance: Basic Runtime pattern is actually the High Availability: Runtime pattern: Variation 2: Load balancer hot standby. The product mapping for this Basic Runtime pattern is not detailed below. As such, the first figure below corresponds to High Performance: Runtime pattern: Variation 1: Redirectors.

Variation 1: Redirectors

High Performance: Product mapping - Windows 2000: Redirectors
(Click a node to get a detailed explanation.)
Design Last Updated: 02-2004
High Performance: Product mapping - Windows 2000: Variation 1
Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information

The Web server redirector nodes run the IBM HTTP Server with the WebSphere Application Server HTTP plug-in. Note there are two redirector nodes in this design. One redirector node could possibly be sufficient to satisfy all requests. However, high availability considerations recommend using two redirectors with load balancer spraying requests to both of them.

Variation 2: Separation

High Performance: Product mapping - Windows 2000: Separation
(Click a node to get a detailed explanation.)
Design Last Updated: 02-2004
High Performance: Product mapping - Windows 2000: Variation 2
Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information

The WebSphere Application Server V4 HTTP plug-in that runs in the HTTP Redirector nodes can perform a load balancing function to spray client requests between the two presentation server nodes.

Variation 3: Caching proxy

High Performance: Product mapping - Windows 2000: Single caching proxy
(Click a node to get a detailed explanation.)
Design Last Updated: 02-2004
High Performance: Product mapping - Windows 2000: Signle caching proxy
Click for more information CLick for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information

The caching proxy node is implemented using the Caching Proxy feature of WebSphere Application Server V5 Edge Components. A caching proxy reduces bandwidth use and improves a Web site's speed and reliability by providing a point-of-presence node for one or more back-end content servers (Web application servers shown on the figures). The WebSphere Application Server V5 Caching Proxy can cache and serve static content and content dynamically generated by WebSphere Application Server. For additional information on performance, scalability, and high availability within WebSphere Application Server, see IBM WebSphere V5.0 Performance, Scalability, and High Availability, SG24-6198.

The WebSphere Application Servers are configured with the same applications available on both servers. This can be accomplished using clones. Cookie-based affinity is provided by the WebSphere Application Servers.

High Performance: Product mapping - Windows 2000: Caching proxies
As stated previously, product mapping correlates real products with one or more runtime nodes. In this scenario, we document only the products implemented on nodes in the DMZ since this is where we will demonstrate our alternatives. The following product mapping graphics only list software that is new or modified from the High Availability: Variation 1: Single load balancer product mapping.
(Click a node to get a detailed explanation.)
Design Last Updated: 02-2004
High Performance: Product mapping - Windows 2000: Variation 3
Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information

Note that two caching proxy nodes are illustrated in the design above. This is a high availability configuration with one caching proxy node being able to perform all caching functions if the other node is unavailable. One possible configuration uses Windows 2000 as the base operating system while the other uses AIX V4.3.3 as the base. In both cases, IBM WebSphere Edge Server V2 requires Java 1.3 as a prerequisite.

IBM Edge Server
The caching proxy nodes are implemented using the Caching Proxy component of IBM WebSphere Edge Server V2.0. The caching proxy component can be configured so that cached pages are saved in only one caching proxy node. At the same time, if one caching proxy node becomes unavailable, the remaining node can assume the caching function for all cached pages.

Note that there are two sets of high availability load balancer nodes in the design above. Both of these load balancer instances can be configured on the same pair of machines, thus minimizing hardware requirements.

Variation 4: Caching proxies with security plug-in

High Performance: Product mapping - Windows 2000: Single caching proxy with security plug-in
(Click a node to get a detailed explanation.)
Design Last Updated: 02-2004
High Performance: Product mapping - Windows 2000: Single caching proxy security plug-in
Clink for more information Click for more information CLick for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information

Tivoli Access Manager for e-business provides a single point of user authentication (identification), authorization (access) and administration for e-business initiatives. It provides Web single sing-on, single point of controlling access to Web-based resources, and standards-based APIs to allow virtually any application server to access its security services.

High Performace: Product mapping: Windows 2000 - Caching proxies with security plug-in
(Click a node to get a detailed explanation.)
Design Last Updated: 01-2004
High Availability: Product mapping - Windows 200: Caching proxies with security plug-in
Click for more information Click for more information Click for more information Click for more information Clink for more information Click for more information CLick for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information Click for more information

The load balancer nodes are implemented using the high availability Load Balancer feature of WebSphere Application Server V5 Edge Components. The Load Balancer feature is configured so the two caching proxy nodes comprise one load balanced cluster. Requests can be distributed round-robin or based on load using advisors. The Media Access Control (MAC) forwarding method of Load Balancer can be used in this configuration. However, both Network Address Translation (NAT) and Network Address Port Translation (NAPT) forwarding methods could be used. Enhanced recognition of available CPU and memory resources on content servers using advisors or metric server agents is provided with the Load Balancer. Session affinity to a specific back-end server can be maintained using the sticky time affinity feature or the active cookie support of the Load Balancer. SSL connections from the client to the load balancer will be tunneled to the back-end proxy servers. For additional information on performance, scalability, and high availability within WebSphere Application Server, see IBM WebSphere V5.0 Performance, Scalability, and High Availability, SG24-6198.

Next, Review guidelines and related links or review another product mapping: AIX

c