[Version 5.0.2 and later]Scaling the Web services gateway

You cannot install the gateway into an application server that is part of a cluster. However, you can still scale the gateway by installing an identical gateway on several application servers, then using a plug-in to the front-end HTTP server to balance the load.

Why and when to perform this task

The servers that you include in the load-balancing group can be stand-alone application servers, or application servers that are members of a deployment manager cell, or a mixture of the two. Each server in the group can be hosted on a separate node, or all the servers can be hosted on one or two nodes.

If you create each application server in the group as a member of a single deployment manager cell (that is, create all the servers on machines that are nodes of a single cell), you can use the deployment manager tooling for the cell to help you install and update the gateway installation on each application server in the group, no matter where each server is physically hosted.

You configure and maintain an instance of the gateway that is separate from your deployment group as the source configuration for every gateway in the group. You use the back up option to save the source configuration as a Shared configuration, then you restore the saved configuration to every gateway in the group.

[Version 5.0.2]To scale the Web services gateway, complete the steps given in Scaling the Web services gateway using unlocked configuration deployment.


Related concepts
Related tasks
Enabling Web services through the Web services gateway



Searchable topic ID:   twsg_scale
Last updated: Jun 21, 2007 4:55:42 PM CDT    WebSphere Application Server Network Deployment, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/twsg_scale.html

Library | Support | Terms of Use | Feedback