Planning your bus-enabled web services installation

Consider how your environment will be configured to support service integration bus-enabled web services. Determine which of the bus-enabled web services roles you want each server or cluster to perform.

Figure 1. A service integration environment with a gateway service In this figure, a gateway service has been added to the previous figure. The gateway service resembles an inbound service and maps to a target service.
These figures show the main component types and flows for bus-enabled web services. Of all these component types, only three interact directly with the world outside the bus:
By configuring these component types for a given stand-alone server or cluster, you enable that server or cluster to perform one or more of the following associated bus-enabled web services roles:
You might choose to use a cluster rather than a stand-alone application server to support a role for any of the following reasons: For example, in a production environment you would typically use a cluster to act as an endpoint.
Note: There is a fourth role of Configuration connection point. This role is never provided by a cluster; only a deployment manager or an unfederated stand-alone server can act as a configuration connection point.
Concept topic Concept topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Feb 6, 2014 8:11:25 PM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-nd-mp&topic=cjw_install_plan
File name: cjw_install_plan.html