Before you install the service integration bus Web services enablement
(SIBWS) applications, you must consider your environment and determine,
for each server or cluster, which subset of the
applications to install.

The figure shows the main component types and flows for the Web service
enablement of the service integration bus (SIBWS). Of all these component
types, only three interact directly with the world outside the bus:
- The endpoint listeners.
- The outbound ports (which act as service invokers).
- The service destinations (which provide mediation points).
To make these components accessible from outside the bus,
install the SIBWS applications that support them on one or more of your
standalone servers
or clusters.
To determine which of the SIBWS applications you install on each
standalone server
or cluster, first determine the roles that the server
or cluster is to perform. A given server
or
cluster can perform one or more of the following roles:
- Endpoint
- If you want your server or cluster to act as
an endpoint, install the following resources:
- SDO repository.
- SIBWS application.
- Endpoint listener application.
- Service invoker
- If you want your server or cluster to act as
a service invoker (that is, an outbound port), install the following resources:
- SDO repository.
- Resource adapter.
- SIBWS application.
- Mediation point
- A mediation is deployed to a server or cluster. If
you want your server or cluster to provide a mediation
point for Web services, install the following applications:
- SDO repository.
- SIBWS application.
For each of these roles, you might choose to use a cluster
rather than a standalone application server for any of the following reasons:
- Reliability.
- Scalability.
- Performance.
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, for which you only need to install the SDO repository. This
role is never provided by a cluster, only a deployment manager or an unfederated
standalone server can act as a configuration connection point.