WAS v8.5 > WebSphere applications > Web services > WS-ReliableMessaging

WS-ReliableMessaging - How it works

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

The reliability is provided by reliable messaging middleware that sits between the web service requester and the web service provider. This middleware layer is shown beneath the dotted line in the following diagram, and includes the reliable messaging source and the reliable messaging destination.

When using WS-ReliableMessaging with a two-way programming API, if the requesting application fails and is restarted it will not receive its reply message. In this model, WS-ReliableMessaging is being used to protect from network failures only. Moreover:

Figure 1. The interactions used to exchange web services messages reliably.

In the previous diagram, the application source invokes a web service. The sequence of interactions is as follows:

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.


Related concepts:

Qualities of service for WS-ReliableMessaging
Web Services Addressing overview


Related


Add assured delivery to web services through WS-ReliableMessaging
Detecting and fixing problems with WS-ReliableMessaging


+

Search Tips   |   Advanced Search