InfoCenter Home >
7: Multimachine management >
7.2 Managing workloads >
7.2.2 Workload management for servlets

7.2.2 Workload management for servlets

Workload management for servlets can be enabled as follows:

  • Clone application servers that host servlet engines.
  • Use an HTTP redirector or a transport mechanism to distribute processing requests across multiple machines.

Clone application servers

Cloning an application server in which a servlet engine is running automatically enables workload management for the application server and the servlets it hosts. Configure the servlet engine to maximize its performance and throughput, then create a server group and clones by using the WebSphere Administrative Console.

Redirect processing requests

A second way to manage workloads is to distribute HTTP requests to clones that reside on a machine other than the machine containing the Web server. You can enable workload mangement through an HTTP redirector or the underlying transport mechanism used in WebSphere Application Server.

A servlet redirector is a special-purpose application server that uses Remote Method Invocation (RMI) over the Internet Inter-ORB Protocol (IIOP) to distribute HTTP requests to application servers on machines remote to the Web server. It is used to distribute requests to clones of a servlet engine.

Servlet redirectors act as EJB clients to the cloned application servers in which the servlet engines run. Because they use EJB client invocations to communicate with the application servers, they can participate in workload management. This enables them to perform load balancing and provides failover support.

Redirecting processing requests to application server clones by using remote OSE provides a simplified form of load balancing and supports failover. Load balancing is done manually by redirecting requests from URLs to specific application servers and their clones and by a round-robin selection policy between clones. Remote OSE itself is not part of the workload management service.

Go to previous article: Workload management for enterprise beans and application servers Go to next article: Workload management for administrative servers

 

 
Go to previous article: Workload management for enterprise beans and application servers Go to next article: Workload management for administrative servers