WAS v8.5 > End-to-end paths > Web services - Reliable messaging (WS-ReliableMessaging)

Add assured delivery to web services through WS-ReliableMessaging

Develop a JAX-WS provider or requester application, and configure a policy set to enable WS-ReliableMessaging. Install the application then attach the policy set. To use either of the managed qualities of service, bind the application or policy set to a service integration bus and messaging engine. WS-ReliableMessaging is an interoperability standard for the reliable transmission of messages between two endpoints. With WS-ReliableMessaging, we can make your SOAP over HTTP-based web services reliable without having to write custom code. We can get different qualities of service with WS-ReliableMessaging. These range from protecting against loss of messages across a network, through to protecting against a server becoming unavailable.

With WebSphere Application Server, we can use WS-ReliableMessaging with JAX-WS web services applications that use a SOAP over HTTP binding. To configure a web service application to use WS-ReliableMessaging, you attach a policy set containing a WS-ReliableMessaging policy type. This policy type offers a range of qualities of service: managed persistent, managed non-persistent, or unmanaged non-persistent. The managed qualities of service, managed persistent and managed non-persistent, are supported by the service integration bus.For each attachment between an application and a policy set, we can select the bus and messaging engine to use for the reliable messaging protocol state.

Support for the WS-ReliableMessaging standard was first introduced as part of the IBM WAS v6.1 Feature Pack for Web Services. At that time, the Reliable Asynchronous Messaging Profile (RAMP) v1.0 specification used WS-ReliableMessaging to ensure the reliable delivery of messages, and the Feature Pack for Web Services in WAS v6.1 included default policy sets that support this specification. We can migrate WAS v6.1 WS-ReliableMessaging configurations that use RAMP-based policy sets to the current version of the product.

Following on from the RAMP v1.0 specification, the Web Services Interoperability organization (WS-I) Reliable Secure Profile working group has developed v1.0 of an interoperability profile dealing with secure, reliable messaging capabilities for web services. This profile is similar to RAMP v1.0, except that it is updated to use WS-ReliableMessaging v1.1 with the OASIS WS-SecureConversation v1.3 specification. The WS-I RSP default policy sets provided in this version of WAS are an implementation of the Reliable Secure Profile v1.0 specification.

If you create JAX-WS based WS-Notification services, we can apply WS-ReliableMessaging policies to them to make your WS-Notification services reliable. For more information, see Configure WS-Notification for reliable notification.

The WS-Policy implementation in WAS supports Web Services Reliable Messaging Policy Assertion v1.0 and Web Services Reliable Messaging Policy Assertion v1.1. For more information, see WS-Policy.

To enable WS-ReliableMessaging for an application, you take the following broad actions:

  1. Develop a JAX-WS web service provider or requester application.
  2. Install the application into WAS.
  3. Attach a reliable messaging policy set (either a default policy set or one that we have created) to an aspect of the application (that is, application level or web service level). Policy sets define the reliability level (quality of service) and other configuration options to apply to your reliable messaging application.
  4. Define the bindings for each attachment to a policy set that specifies a managed quality of service. That is, choose the service integration bus and messaging engine to use to maintain the state for the managed persistent and managed non-persistent qualities of service.

At any stage - that is, before or after we have built your reliable web service application, or configured your policy sets - we can set a property that configures endpoints to only support clients that use reliable messaging. This setting is reflected by WS-Policy if engaged.

  1. Develop a reliable web service application.
  2. Configure a policy set instance to enable WS-ReliableMessaging.
  3. Install your reliable JAX-WS web service application.
  4. Attach and bind a WS-ReliableMessaging policy set to the application.

  5. Save your changes to the master configuration.
  6. Stop then restart the server.


Results

A reliable JAX-WS application is deployed into a suitably configured environment and started.


Subtopics


Related concepts:

JAX-WS application deployment model


Related


WS-ReliableMessaging
Administer reliable web services
Tasks: Implementing web services applications
Configure endpoints to only support clients that use WS-ReliableMessaging
Detecting and fixing problems with WS-ReliableMessaging


+

Search Tips   |   Advanced Search