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 your 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:
- Develop a JAX-WS web service provider or requester application.
- Install the application into WebSphere Application Server.
- 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 your reliable messaging application.
- 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 your reliable web service application, or configured your 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.
WS-ReliableMessaging became a stabilized feature in WAS v8.5.5.
To learn about the WS-ReliableMessaging implementation in WAS, 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
- 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
- WS-ReliableMessaging roles and goals
- WS-ReliableMessaging - requirements for interaction with other implementations
Add assured delivery to web services through WS-ReliableMessaging Detect and fix 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