WebSphere WebSphere Application Server Network Deployment, Version 6.1.x Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

Planning your Bus-enabled Web services installation

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

Inbound, outbound and gateway services: how a client request is received by an endpoint listener, then passed through an inbound port to an inbound service; how an outbound service passes a request through an outbound port to an external service; how a gateway service resembles an inbound service and maps to a target service.
The figure shows 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 standalone 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 standalone 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 actually a fourth role of Configuration connection point This role is never provided by a cluster; only a deployment manager or an unfederated standalone server can act as a configuration connection point.

Concept topic

Terms of use | Feedback


Timestamp icon Last updated: 26 February 2009
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.pmc.nd.multiplatform.doc/concepts/cjw_install_plan.html

Copyright IBM Corporation 2004, 2009. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)