Web services can use the service integration bus (SIBus) and the Web services gateway 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.
Why and when to perform this task
With SIBus-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.
- Create a gateway service: Use the Web services
gateway to map an existing service - either an inbound or an outbound service
- to a new Web service that appears to be provided by the gateway.
SIBus Web services provides 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. The
Web services gateway is used to map Web services for use within your organization
and by external users, and to manage the relationships between externally-provided
Web services and those provided directly through a service integration bus
(that is, the relationships between inbound and outbound services).
To
enable Web services through service integration technologies, complete the
following steps:
Steps for this task
- Optional: Learn about SIBus Web services. Explore the concepts that underly the Web services enablement of the service integration
bus (SIBus).
- Plan your SIBus Web services installation. Determine the
SIBus Web services roles that each standalone server or
cluster is to perform.
- Ensure that every standalone server or
cluster that is to play an SIBus Web services role is a member of a service integration
bus. For more information, see Configuring the members of a bus.
- Install the SIBus Web services applications and resources. For
every standalone server or cluster that
is to play an SIBus 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 SIBus 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
SIBus 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: Create a gateway instance. Within
each service integration bus you can create multiple gateway instances. You
create Web services gateway instances to partition the total set of gateway
services into logical
groups to allow simpler management. The gateway provides you with a single
point of control, access and validation of Web service requests, and allows
you to control which Web services are available to different groups of Web
service users.
- Optional: Create a gateway service. A gateway
service is the Web interface for an underlying service (the target service)
that is either provided internally (hosted so as to be directly available
at a service destination), or provided externally (as an external Web service).
You use the Web services gateway to map an existing service - either an inbound
or an outbound service - to a new Web service that appears to be provided
by the gateway. The gateway service acts as a proxy: your gateway service
users need not know whether the underlying service is being provided internally
or externally.
- Optional: Apply additional security to your SIBus Web services-enabled Web services. In a previous step you configured the minimum
security configuration for SIBus Web services to work in a secure bus. However this
level of security does not impose any security restrictions on the users of
your SIBus Web services configuration. To control how your SIBus Web services configuration is used
by each group of your colleagues or customers, use the SIBus Web services additional security
features to enable working with password-protected components and servers,
with WS-Security and with HTTPS.
For further information on specific aspects of SIBus Web services, see
the following topics: