Web services can use the service integration bus to provide a single point of control, access,
and validation of Web service requests and allow control of Web services
that are available to different groups of Web service users.
About this task
With bus-enabled Web services
you can achieve the following goals:
- Create an inbound service: Take an internally-hosted
service that is available at a bus destination, and make it available
as a Web service.
- Create an outbound service: Take an externally-hosted
Web service, and make it available internally at a bus destination.
Bus-enabled Web services provide a choice of quality of
service and message distribution options for Web services, along with
intelligence in the form of mediations that allow for the rerouting
of messages.
To
enable Web services through service integration technologies, complete
the following steps:
Procedure
- Optional: Learn about bus-enabled
Web services. Explore the concepts that underly
service integration bus-enabled Web services.
- Plan your bus-enabled Web services installation.
Determine the bus-enabled Web services roles that each server is
to perform.
- Ensure that every server that
is to play a bus-enabled Web services role is a member of a service
integration bus. For more information, see Configuring the members of a bus.
- Install the bus-enabled
Web services applications and resources. For every server that
is to play a bus-enabled Web services role:
- Install and configure a Service Data Objects (SDO) repository
(used for storing and serving WSDL definitions).
- Install a selection of the following applications:
- The service integration technologies resource adapter (used to
invoke Web services at outbound ports).
- The bus-enabled Web services application.
- One or more endpoint listener applications.
- Create a new endpoint listener configuration for each endpoint listener
application that you have installed.
- Optional: If WebSphere® Application Server
global security is enabled, and you are working with secure service
integration buses, create
the minimum security configuration that is required for bus-enabled
Web services to work in a secure bus.
- Optional: Create an inbound service. An inbound
service is a Web interface to a service that is provided internally
(that is, a service provided by your own organization and hosted in
a location that is directly available through a service integration
bus destination). To configure a locally-hosted service as an inbound
service, you associate it with a service destination, and with one
or more endpoint listeners through which service requests and responses
are passed to the service. You can also choose to have the local service
made available through one or more UDDI registries.
- Optional: Create an outbound
service. An outbound service is a Web service that
is hosted externally, and is made available through a service integration
bus. To make an externally-hosted service available through a bus,
you first associate it with a service destination, then you configure
one or more port destinations (one for each type of binding, for example
SOAP over HTTP or SOAP over JMS) through which service requests and
responses are passed to the external service. You get the port definitions
from the WSDL, but you can choose which ones you want to create.
- Optional: Apply additional
security to your bus-enabled Web services. In a previous step you configured the minimum
security configuration for bus-enabled Web services to work in a secure
bus. However this level of security does not impose any security
restrictions on the users of your bus-enabled Web services configuration.
To control how your bus-enabled Web services configuration is used
by each group of your colleagues or customers, use the bus-enabled
Web services additional security features to enable working with password-protected
components and servers, with WS-Security and with HTTPS.
What to do next
For further information on specific aspects of bus-enabled
Web services, see the following topics: