WS-ReliableMessaging default policy sets

The WS-ReliableMessaging default policy sets provide reliable message exchange between Web services. The WS-ReliableMessaging policy sets are the WSReliableMessaging default policy set, the WSReliableMessaging persistent policy set, and the WSReliableMessaging 1_0 policy set.

With WS-ReliableMessaging, you can make your SOAP over HTTP-based Web services interoperable and reliable without writing custom code. Use the WSReliableMessaging default policy set, the WSReliableMessaging persistent policy set or the WSReliableMessaging 1_0 policy set as provided with the application server. To customize the policy sets, you must first copy the policy set, and then configure custom policy settings and bindings to meet your needs.

The WS-ReliableMessaging default policy sets include the WS-ReliableMessaging and WS-Addressing policies. WS-ReliableMessaging provides the ability to deliver a message reliably to its intended receiver. WS-Addressing provides a transport-neutral way to uniformly address Web services and messages, and WS-ReliableMessaging uses WS-Addressing to provide asynchronous request and reply capabilities.

These are the WS-ReliableMessaging default policy sets:

WSReliableMessaging default
This policy set enables both WS-ReliableMessaging and WS-Addressing and uses the minimum quality of service, unmanaged non-persistent. 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, failure of a server results in lost messages. This quality of service is for single server only and does not function in a cluster.
WSReliableMessaging persistent
This policy set enables both WS-ReliableMessaging and WS-Addressing and uses the maximum quality of service, managed persistent. This quality of service supports asynchronous Web service invocations and uses a service integration messaging engine and message store to manage the sequence state. Messages are processed within transactions are persisted at the Web service requester server and at the Web service provider server, and are recoverable in the event of server failure.
Because this policy set specifies managed persistent quality of service, you need to define bindings to the service integration bus and messaging engine that you want to use to manage the WS-ReliableMessaging state. For more information, see Attaching and binding a WS-ReliableMessaging policy set to a Web service application using the administrative console or using the wsadmin tool.
WSReliableMessaging 1_0
This policy set enables both WS-ReliableMessaging Version 1.0 and WS-Addressing and uses the minimum quality of service, unmanaged non-persistent. 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, failure of a server results in lost messages. This quality of service is for single server only and does not function in a cluster.
You can use this policy set with .NET-based Web services.

The Reliable Asynchronous Message Profile (RAMP) default policy sets also use the WS-ReliableMessaging policy to enable reliable message exchange.




Related concepts
RAMP default policy sets
Related tasks
Adding assured delivery to Web services through WS-ReliableMessaging
Learning about WS-ReliableMessaging
Creating policy sets using the administrative console
Concept topic Concept topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 1:23:07 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-dist&topic=cwbs_wsspsrm
File name: cwbs_wsspsrm.html