InfoCenter Home >
7: Multimachine management >
7.1: Using WebSphere Application Server in a multimachine environment >
7.1.3: Multimachine topologies >
7.1.3.6: HTTP server separation sample topologies >
7.1.3.6.2: Semi-remote HTTP sample topology

7.1.3.6.2: Semi-remote HTTP sample topology

Overview

Semi-remote HTTP is a variation of the HTTP topology described in article 7.1.3.6.1, HTTP transport sample topology. The difference between the two topologies is whether an instance of the application server runs on the machine that hosts the Web server. A semi-remote HTTP configuration has an instance of an application server running on the same machine as the Web server; a remote HTTP configuration does not.

semihttptop.gif (9761 bytes)

Semi-remote HTTP can be used to direct client requests to additional application server clones on other machines. In this example, it redirects client requests to both the application server instance running on Machine A and the clones running on Machine B.

Typical use

Using a semi-remote HTTP configuration is recommended only in situations where hardware limitations prevent you from hosting the Web server on a dedicated machine.

In many production environments, one set of servers is configured to run Web servers and another set of servers is configured to run application servers. If a customer either needs to add capacity in a production environment or cannot fully replicate the production configuration in the production test environment, semi-remote HTTP provides a means of load distribution between a machine hosting both the Web and application server and machines hosting just the application server.

A semi-remote HTTP configuration can also be used as a WebSphere proof-of-concept for demonstrating load distribution in situations where there are a limited number of machines.

Go to previous article: HTTP transport sample topology Go to next article: Reverse proxy (IP forwarding) sample topology

 

 
Go to previous article: HTTP transport sample topology Go to next article: Reverse proxy (IP forwarding) sample topology