WS-ReliableMessaging settings

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: Services > Policy sets > Application policy sets > policy_set_name > WS-ReliableMessaging .

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.

Standard

Select the WS-ReliableMessaging specification to use for reliable transmission of your messages. WS-ReliableMessaging Version 1.1 is the default value. Details of the supported WS-ReliableMessaging specifications are available at the following Web addresses:
Note: If you plan to invoke a .NET-based Web service, you must select WS-ReliableMessaging Version 1.0.

Deliver messages in the order that they were sent

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.

Note: There is a performance overhead in using in-order delivery, because messages are held in a queue until they can be delivered in order. You can tune your system to reduce the effect of this overhead.

[Fix Pack 5 or later] 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.

Quality of Service

Select one of the following qualities of service:
Unmanaged non-persistent - Tolerates network and remote system failures
You can configure Web service applications to use WS-ReliableMessaging with a default in-memory store. This quality of service requires minimal configuration. However it is non-transactional and, although it allows for the resending of messages that are lost in the network, if a server becomes unavailable you will lose messages. This quality of service is for single server only and does not work in a cluster. This quality of service is not supported on the z/OS® platform. The default is Unmanaged Non-Persistent.
Managed non-persistent - Tolerates system, network, and remote system failures, but state is discarded after messaging engine restart
This in-memory quality of service option uses a messaging engine to manage the sequence state, and messages are written to disk if memory is low. This quality of service allows for the re-sending of messages that are lost in the network, and can also recover from server failure. However, state is discarded after a messaging engine restart so in this case you will lose messages. This option supports clusters as well as single servers.
Managed persistent - Tolerates system, network, and remote system failures
This quality of service for asynchronous Web service invocations is recoverable. This option also uses a messaging engine and message store to manage the sequence state. Messages are persisted at the Web service requester server and at the Web service provider server, and are recoverable if the server becomes unavailable. Messages that have not been successfully transmitted when a server becomes unavailable can continue to be transmitted after the server restarts.
Note:



Related tasks
Tuning Web services reliable messaging applications



Related concepts
Qualities of service for WS-ReliableMessaging
Related tasks
Configuring a WS-ReliableMessaging policy set by using the administrative console
Configuring endpoints to only support clients that use WS-ReliableMessaging
Learning about WS-ReliableMessaging
Managing policy sets using the administrative console
Configuring the WS-ReliableMessaging policy
Related reference
Application policy sets collection
Application policy set settings
Service client policy set and bindings collection
Service provider policy sets and bindings collection
WS-ReliableMessaging - administrative console panels
Reference topic    

Terms of Use | Feedback

Last updated: Oct 21, 2010 7:37:48 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v701sca&product=was-nd-mp&topic=uwbs_wsspsrmd
File name: uwbs_wsspsrmd.html