+

Search Tips   |   Advanced Search

Enabling web services through the service integration bus

Web services can use the service integration bus 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.

With bus-enabled web services we can achieve the following goals:

  • Bus-enabled web services provide a choice of quality of service and message distribution options, 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 the 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...

    1. Optional: Learn about bus-enabled web services. Explore the concepts that underly service integration bus-enabled web services.

    2. Plan the bus-enabled web services installation. Determine the bus-enabled web services roles that each stand-alone server or cluster is to perform.

    3. Ensure that every stand-alone server or cluster that is to play a bus-enabled web services role is a member of a service integration bus. For more information, see Configure the members of a bus.

    4. For every stand-alone server or cluster that is to play a bus-enabled web services role, install and configure a Service Data Objects (SDO) repository on the stand-alone server, or (for a server or cluster that is part of a managed cell) on the network deployment cell.

      For WAS v6.0, we also had to manually 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.

      For later versions of WAS, these applications are installed automatically as and when needed. For example, the endpoint listener application is installed automatically when you configure an endpoint listener.

    5. Create a new endpoint listener configuration for each endpoint listener application to use to receive inbound service requests.

    6. Optional: Create an inbound service. An inbound service is a web interface to a service provided internally (that is, a service provided by our 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. We can also choose to have the local service made available through one or more UDDI registries.

    7. 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 we can choose which ones to create.

    8. Optional: Create a gateway instance. Within each service integration bus we can create multiple gateway instances. We 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 we can use it to control which web services are available to different groups of web service users.

    9. 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). Use 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: the gateway service users need not know whether the underlying service is being provided internally or externally.

    10. Optional: Apply additional security to the bus-enabled web services. By default, the bus-enabled web services configuration works when WAS security is enabled and your service integration buses are secured. However this level of security does not impose any security restrictions on the users of your bus-enabled web services configuration. To control how the bus-enabled web services configuration is used by each group of the 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 more information about specific aspects of bus-enabled web services, see the following topics:


    Subtopics

    • Configure the SDO repository
      Service Data Objects (SDO) is an open standard for enabling applications to handle data from different data sources in a uniform way, as data graphs. Service integration bus-enabled web services use an SDO repository for storing and serving WSDL definitions. Use this task to create and configure your preferred database to store SDO data, and to install and configure an SDO repository on each server to use for bus-enabled web services.

    • Configure web services for a service integration bus
      Take an internally-hosted service that is available at a bus destination, and make it available as a web service; Take an externally-hosted web service, and make it available internally at a bus destination; 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.

    • Administer the bus-enabled web services resources
      Use the console to configure the main service integration bus-enabled web services resources: endpoint listeners; JAX-RPC handler lists; WS-Security bindings and configurations; references to UDDI registries.

    • Create a new WS-Security binding
      Create a new WS-Security binding for use with service integration bus-enabled web services. You use WS-Security bindings to secure the SOAP messages that pass between service requesters (clients) and inbound services, and between outbound services and target web services.

    • Create a new WS-Security configuration
      Create a new WS-Security configuration for use with service integration bus-deployed web services. You use WS-Security configurations to secure the SOAP messages that pass between service requesters (clients) and inbound services, and between outbound services and target web services.

    • Passing SOAP messages with attachments through the service integration bus
      The service integration technologies support web services that use a SOAP binding to pass attachments in a MIME message.


    Related concepts

  • Bus-enabled web services: Frequently asked questions

  • Specifications and API documentation