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 that are supported at the API layer are one-way "fire and forget," or two-way request and reply.

WS-ReliableMessaging became a stabilized feature in WebSphere Application Server Version 8.5.5.

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.

Note: When you use WS-ReliableMessaging with a two-way programming API, if the requesting application fails and is restarted it does not receive its reply message. In this model, WS-ReliableMessaging is being used to protect from network failures only. Moreover:
  • Client-side retransmissions start only after the client starts sending new messages to the service (this situation is true for both one-way and two-way operations).
  • Two-way operations that resume cannot drive the response message back to the client application; the message gets back only as far as the inbound sequence on the client.
Figure 1. The interactions used to exchange web services messages reliably.Two boxes that are shown, represent the initial sender and the ultimate receiver of a web services SOAP over HTTP message. Within the initial sender box, the application source sends the message to a reliable messaging (middleware) source. Within the ultimate receiver box, the application destination receives the message from a reliable messaging (middleware) destination. The SOAP over HTTP message is transmitted by the reliable messaging source to the reliable messaging destination, and the reliable destination sends an acknowledgement message back to the reliable messaging source.

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

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, you can select the bus and messaging engine to use for the reliable messaging protocol state.


指出主題類型的圖示 概念主題



時間戳記圖示 前次更新: July 9, 2016 11:12
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=cwbs_wsrm_how
檔名:cwbs_wsrm_how.html