+

Search Tips   |   Advanced Search

WS-ReliableMessaging settings


For the WS-ReliableMessaging policy we can configure the version of the WS-ReliableMessaging standard 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 pane in the console... Services > Policy sets > Application policy sets > policy_set_name > WS-ReliableMessaging .

With WAS, we 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 we 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 we have built the reliable Web service application, or configured the 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.

Standard

Select the WS-ReliableMessaging specification to use for reliable transmission of the messages. WS-ReliableMessaging Version 1.1 is the default value. Details of the supported WS-ReliableMessaging specifications are available at the following Web addresses:

If we plan to invoke a .NET-based Web service, select WS-ReliableMessaging V1.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 we enable in-order delivery, also verify the requester application polls for the messages in the order in which it wants to receive them.

See Set the WS-ReliableMessaging policy.

Specifying in-order delivery also marginally increases reliability if we are using the managed persistent quality of service. For more information, see A message is not recovered after a server becomes unavailable, even with the managed persistent quality of service.

Quality of Service

Select one of the following qualities of service:

Unmanaged non-persistent - Tolerates network and remote system failures

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. 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.

  • All three qualities of service are supported when applications are deployed to the appserver. Thin client and client container applications use the first option only.

  • For the unmanaged non-persistent quality of service, the messages are stored only in memory. For both of the managed qualities of service, the messages are managed by a messaging engine and stored in a message store. You specify a binding to a bus and messaging engine on the WS-ReliableMessaging policy binding form. If the chosen quality of service is Unmanaged Non-Persistent, which does not use a binding to a messaging engine, then any binding specified is ignored.




 

Related concepts


Qualities of service for WS-ReliableMessaging

 

Related tasks


Set a WS-ReliableMessaging policy set
Set endpoints to only support clients that use WS-ReliableMessaging
Learn about WS-ReliableMessaging
Manage policy sets
Set the WS-ReliableMessaging policy

 

Related


Application policy sets collection
Application policy set settings
Service client.policy set and bindings collection
Service provider policy sets and bindings collection
WS-ReliableMessaging - admin console panels