Before you install the service integration bus Web services enablement
(SIBWS) applications, you must consider your environment and determine,
for each server, 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 servers.
To determine which of the SIBWS applications you install on each server, first determine the roles that the server is to perform. A given server can perform one or more of the following roles:
- Endpoint
- If you want your server to act as
an endpoint, install the following resources:
- SDO repository.
- SIBWS application.
- Endpoint listener application.
- Service invoker
- If you want your server 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. If
you want your server to provide a mediation
point for Web services, install the following applications:
- SDO repository.
- SIBWS application.