+

Search Tips   |   Advanced Search

Provide transactional recoverable messaging through WS-ReliableMessaging

If our WS-ReliableMessaging application runs inside the web container and uses a managed quality of service, we can use WS-ReliableMessaging to provide transactional recoverable messaging.

The WS-ReliableMessaging transactional model is as follows:

For the outbound (requestor) case on a one-way message send, if the enableTransactionalOneWay property is set to true, then the send is performed under any transactional context currently held by the application thread. (Note that transactions are not supported under an outbound two-way message exchange).

For the inbound (provider) case, if the inOrderDelivery property is set to true, then an inbound message is dispatched to the application under a transaction. For an inbound two-way message exchange, the response is also generated under that transaction and is not sent until that transaction has committed.

WS-ReliableMessaging transactions do not use the WS-AtomicTransactions protocol. The relationship between these two protocols is as follows:

For more information, see WS-AtomicTransactions.

To provide transactional recoverable messaging through WS-ReliableMessaging, work through the steps described in Add assured delivery to web services through WS-ReliableMessaging and also complete the following additional steps:


Tasks

  • Configure the WS-ReliableMessaging policy
  • Configure a WS-ReliableMessaging policy set by
  • Configure a WS-ReliableMessaging policy set
  • WS-ReliableMessaging
  • Detect and fix problems with WS-ReliableMessaging
  • Administer reliable web services
  • WS-ReliableMessaging: supported specifications and standards