WS-ReliableMessaging default policy sets

WS-ReliableMessaging default policy sets

+
Search Tips | Advanced Search

The WS-ReliableMessaging default policy sets are pre-configured to provide reliable message exchange between Web services. Two of these policy sets...

WS-I RSP
WS-I RSP ND

...are immediately available, and the rest are available for import from a default repository.
With WS-ReliableMessaging, we can make the SOAP over HTTP-based Web services reliable without writing custom code. Use the provided non-editable default policy sets without change, or we can create customized copies of them.
The WS-ReliableMessaging policy delivers a message reliably to its intended receiver.
The WS-Addressing policy provides a transport-neutral way to uniformly address Web services and messages.
WS-ReliableMessaging uses WS-Addressing to provide asynchronous request and reply capabilities.
WS-ReliableMessaging V1.1 messaging requires WS-Addressing to be mandatory. If we use a policy set that includes...

WS-ReliableMessaging
WS-Addressing

...and the WS-Addressing policy is configured as optional, then WAS overrides the WS-Addressing setting and automatically enables WS-Addressing.

The following default policy sets that include the WS-ReliableMessaging policy are immediately available...

WS-I RSP Enable WS-ReliableMessaging V1.1 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, 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. In-order delivery is set to "false", so messages are not necessarily delivered in the order in which they were sent. Message integrity is provided by digitally signing the body, the time stamp, and the WS-Addressing headers. Message confidentiality is provided by encrypting the body and the signature.
Follows the WS-SecureConversation and WS-Security specifications.
WS-I RSP ND This is the network deployment version of the WS-I RSP policy set.
Provides the WS-I RSP default policy set and adds a managed non-persistent quality of service.
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.

The following additional default policy sets that include the WS-ReliableMessaging policy are readily available for import.
LTPA WS-I RSP Provides the WS-I RSP default policy set and adds a LTPA token included in the request message to authenticate the client to the service.
Username WS-I RSP Provides the WS-I RSP default policy set and adds a username token included in the request message to authenticate the client to the service. The username token is encrypted in the request.
WSReliableMessaging 1_0 Enable both WS-ReliableMessaging V1.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, 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. In-order delivery is set to "false", so messages are not necessarily delivered in the order in which they were sent.
Use this policy set with .NET-based Web services.
WSReliableMessaging default Enable both WS-ReliableMessaging V1.1 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, 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. In-order delivery is set to "false", so messages are not necessarily delivered in the order in which they were sent.
WSReliableMessaging persistent Enable 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. In-order delivery is set to "false", so messages are not necessarily delivered in the order in which they were sent.
Because this policy set specifies managed persistent quality of service, we have to define bindings to the service integration bus and messaging engine to use to manage the WS-ReliableMessaging state. We can attach and bind a WS-ReliableMessaging policy set to a Web service application using the admin console or using wsadmin.

Related concepts
Web services policy sets
WS-I RSP default policy sets
Add assured delivery to Web services through WS-ReliableMessaging
Learn about WS-ReliableMessaging
Create policy sets

WS-I RSP	Enable WS-ReliableMessaging V1.1 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, 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. In-order delivery is set to "false", so messages are not necessarily delivered in the order in which they were sent. Message integrity is provided by digitally signing the body, the time stamp, and the WS-Addressing headers. Message confidentiality is provided by encrypting the body and the signature. Follows the WS-SecureConversation and WS-Security specifications.
WS-I RSP ND	This is the network deployment version of the WS-I RSP policy set. Provides the WS-I RSP default policy set and adds a managed non-persistent quality of service. 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. The following additional default policy sets that include the WS-ReliableMessaging policy are readily available for import.
LTPA WS-I RSP	Provides the WS-I RSP default policy set and adds a LTPA token included in the request message to authenticate the client to the service.
Username WS-I RSP	Provides the WS-I RSP default policy set and adds a username token included in the request message to authenticate the client to the service. The username token is encrypted in the request.
WSReliableMessaging 1_0	Enable both WS-ReliableMessaging V1.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, 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. In-order delivery is set to "false", so messages are not necessarily delivered in the order in which they were sent. Use this policy set with .NET-based Web services.
WSReliableMessaging default	Enable both WS-ReliableMessaging V1.1 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, 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. In-order delivery is set to "false", so messages are not necessarily delivered in the order in which they were sent.
WSReliableMessaging persistent	Enable 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. In-order delivery is set to "false", so messages are not necessarily delivered in the order in which they were sent. Because this policy set specifies managed persistent quality of service, we have to define bindings to the service integration bus and messaging engine to use to manage the WS-ReliableMessaging state. We can attach and bind a WS-ReliableMessaging policy set to a Web service application using the admin console or using wsadmin.