+

Search Tips   |   Advanced Search

Add assured delivery to Web services through WS-ReliableMessaging


WS-ReliableMessaging is an interoperability standard for the reliable transmission of messages between two endpoints. With WS-ReliableMessaging, we can make the 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 WAS, we can use WS-ReliableMessaging with JAX-WS 2.1 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 that contains a WS-ReliableMessaging policy type. This policy type offers a range of qualities of service: managed persistent, managed non-persistent, or unmanaged non-persistent.

New feature:

Support for the WS-ReliableMessaging standard was first introduced as part of the IBM WAS V6.1 Feature Pack for Web Services using RAMP V1.0 and default policy sets.

We can migrate WAS V6.1 WS-ReliableMessaging configurations to WAS ND v7.0.

The 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 WAS ND v7.0 are an implementation of the Reliable Secure Profile V1.0 specification.

If we create JAX-WS based WS-Notification services, we can apply WS-ReliableMessaging policies to them to make the WS-Notification services reliable.

See Set 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.

See WS-Policy.

The WS-Policy implementation in WAS supports Web Services Reliable Messaging Policy Assertion V1.0 and Web Services Reliable Messaging Policy Assertion V1.1.

See WS-Policy. newfeat 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 the 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 the reliable Web service application, or configured the 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.

For more information about using WS-ReliableMessaging, see the following topics:

 


Learn about WS-ReliableMessaging
Building a reliable Web service application
Administer reliable Web services
Detecting and fixing problems with WS-ReliableMessaging

 

Related tasks


Task overview: Implement Web services applications
Set endpoints to only support clients that use WS-ReliableMessaging
Set a WS-ReliableMessaging policy set
Attach and binding a WS-ReliableMessaging policy set to a Web service application
Detecting and fixing problems with WS-ReliableMessaging