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 page in the console, click the following path: Services > Policy sets > Application policy sets > policy_set_name > WS-ReliableMessaging.
With WebSphere Application Server, we can use WS-ReliableMessaging with JAX-WS web services applications that use a SOAP over HTTP binding. Select the WS-ReliableMessaging specification to use for reliable transmission of our messages. WS-ReliableMessaging Version 1.1 is the default value. Select the WS-ReliableMessaging specification to use for reliable transmission of our messages. WS-ReliableMessaging Version 1.1 is the default value. Details of the supported WS-ReliableMessaging specifications are available at the following web addresses:
- The WS-ReliableMessaging specification Version 1.0, February 2005.
- The OASIS WS-ReliableMessaging specification Version 1.1, February 2007.
If we plan to invoke a .NET-based web service, select WS-ReliableMessaging Version 1.0.
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 your reliable web service application, or configured your 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 our messages. WS-ReliableMessaging Version 1.1 is the default value. Select the WS-ReliableMessaging specification to use for reliable transmission of our messages. WS-ReliableMessaging Version 1.1 is the default value.
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, we must also ensure that the requester application polls for the messages in the order in which it is to receive them. See Configure the WS-ReliableMessaging policy.
Specify in-order delivery also marginally increases reliability if we are using 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
- We 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 we will lose messages. This quality of service is for single server only and does not work in a cluster. (ZOS) 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 we 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 application server. 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 our 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:
Qualities of service for WS-ReliableMessaging Configure a WS-ReliableMessaging policy set by Configure endpoints to only support clients that use WS-ReliableMessaging WS-ReliableMessaging Manage policy sets Tune web services reliable messaging applications WS-ReliableMessaging - administrative console panels Application policy sets collection Application policy set settings Service client policy set and bindings collection Service provider policy sets and bindings collection