WS-ReliableMessaging

WS-ReliableMessaging is an interoperability standard for the reliable transmission of messages between two endpoints. Use these topics to learn more about WS-ReliableMessaging.

Without WS-ReliableMessaging, the web services that require assured delivery of SOAP messages can either use a vendor-specific binding such as SOAP over JMS (which provides limited interoperability) or they can use SOAP over HTTP and rely upon you to write the associated durable message stores, custom retry logic at the sender, and duplicate detection at the receiver. With WS-ReliableMessaging, we can make the SOAP over HTTP-based web services reliable without having to write custom code.

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 WebSphere Application Server.

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.

To learn about the WS-ReliableMessaging implementation in WebSphere Application Server, see the following topics:

• WS-ReliableMessaging - How it works

• Benefits of using WS-ReliableMessaging

• Qualities of service for WS-ReliableMessaging

• Use patterns for WS-ReliableMessaging

• WS-ReliableMessaging sequences

• WS-ReliableMessaging - terminology

• WS-ReliableMessaging: supported specifications and standards

Subtopics

• WS-ReliableMessaging - How it works
  WAS uses WS-ReliableMessaging as part of the transport layer for SOAP over HTTP messages. The message exchange patterns supported at the API layer are one-way "fire and forget," or two-way request and reply.

• Benefits of using WS-ReliableMessaging
  With WS-ReliableMessaging, along with the other components of the Reliable Secure Profile, we can support the business-to-business web services scenarios without having to write our own custom retry logic, duplicate detection code and persistence code.

• Qualities of service for WS-ReliableMessaging
  We can get different qualities of service with WS-ReliableMessaging, depending on the level of durability and transaction support provided by the store used to manage the reliable messaging state. These qualities of service range from protecting against loss of messages across a network, through to protecting against server failure.

• Use patterns for WS-ReliableMessaging
  Links to descriptions of the use patterns that motivate WS-ReliableMessaging. Each use pattern description includes an overview of the business problem, of the technical solution without WS-ReliableMessaging, of the shortcomings of this solution, and of how we can use WS-ReliableMessaging to overcome these shortcomings.

• WS-ReliableMessaging sequences
  The WS-ReliableMessaging protocol relies on a "sequence" to manage the transmission of messages from reliable messaging source to reliable messaging destination. Each application message is given an identifier that identifies both the sequence and the message number (the position) within the sequence. Protocol flows are used to create sequences, to acknowledge messages and to terminate sequences.

• WS-ReliableMessaging - terminology
  

• WS-ReliableMessaging: supported specifications and standards
  WebSphere Application Server provides support for two levels of the WS-ReliableMessaging specification. This gives compatibility with vendors that provide WS-ReliableMessaging support at the February 2005 level, as well as meeting the requirements of the current OASIS specification. This implementation of WS-ReliableMessaging also composes with many other web services standards.

• WS-ReliableMessaging roles and goals
  Computing roles that members of the organization might perform, and how we can use WS-ReliableMessaging to help meet the goals of each role.

• WS-ReliableMessaging - requirements for interaction with other implementations
  The information and configuration needed for another vendor's reliable messaging source to send messages to a WAS reliable messaging destination, or for a WAS reliable messaging source to send messages to another vendor's reliable messaging destination.

Related tasks

Add assured delivery to web services through WS-ReliableMessaging

Detecting and fixing problems with WS-ReliableMessaging

Configure endpoints to only support clients that use WS-ReliableMessaging

WS-ReliableMessaging - terminology

WS-ReliableMessaging: supported specifications and standards

WS-ReliableMessaging roles and goals

WS-ReliableMessaging - requirements for interaction with other implementations