For the WS-ReliableMessaging policy you can configure the version of the WS-ReliableMessaging standard that you want to use, the order in which messages are delivered, and the required quality of service (the reliability level) for message delivery. The product can enforce these policies on inbound messages and applies them to outbound messages.
To view this page in the console, click the following path: .
With WebSphere® Application Server, you can use WS-ReliableMessaging with Java API for XML-Based Web Services (JAX-WS) 2.1 Web services applications that use a SOAP over HTTP binding. 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.
Do not edit the policies associated with the provided default policy sets. If you have to modify the reliable messaging policy settings, use a copy of a default policy set or create a new policy set.
At any stage - that is, before or after you have built your reliable Web service application, or configured your policy sets - you can set a property that configures endpoints to only support clients that use reliable messaging. This setting is reflected by WS-Policy if engaged.
Select this option if the sender of a request has to receive a response before it sends the next request.
If you enable in-order delivery, you must also ensure that the requester application polls for the messages in the order in which it is to receive them. For more information, see Configuring the WS-ReliableMessaging policy.
Specifying in-order delivery also marginally increases reliability if you are using the managed persistent quality of service.
The performance overhead is greatly reduced;
you should not have to tune your system to reduce its effect, although
you might want to tune your system for other purposes.