For the WS-ReliableMessaging policy you can configure the version of the WS-ReliableMessaging standard that you want to use, the option to use the WS-MakeConnection protocol for synchronous two-way message exchange, the order in which messages are delivered, and the required quality of service (the reliability level) for message delivery. The
product enforces these policies on inbound messages and applies them
to outbound messages.
To view this pane in the console, click the following path: .
With WebSphere Application Server, you can use WS-ReliableMessaging with Java API for XML-Based Web Services (JAX-WS) 2.0 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 need to modify the reliable messaging
policy settings, use a copy of a default policy set or create a new
policy set.
Configuration tab
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 or host a Web service that is compatible with reliable
.NET clients, you must select WS-ReliableMessaging Version 1.0.
Enable "MakeConnection" for synchronous two-way message exchange
Select this option to enable WS-MakeConnection, which is a standard method of enabling synchronous two-way message exchange with WS-ReliableMessaging.
For more information, see the WS-MakeConnection specification Version 1.0, February 2007.
Note:
- If you are using WS-ReliableMessaging Version 1.1 and you want
to use synchronous two-way message exchange, you must enable "MakeConnection".
- If you are using WS-ReliableMessaging Version 1.0, you cannot
use "MakeConnection".
- If you want to use "MakeConnection" you must also include
the WS-Addressing policy in the policy set.
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 wants 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. For more
information, see A message is not recovered after a server becomes unavailable, even with 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.
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, it is for single server only and it does not support clusters. Although this quality of service allows for the re-sending of messages that are lost in the network, failure of a server results in lost messages. 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 supports clusters as well as single servers. This 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, a failure of the messaging engine causes message loss.
- 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 fails. Messages that have not been successfully transmitted when a server fails can continue to be transmitted after the server restarts.
Note:
- 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 (delivery bindings) settings form. If your chosen quality of
service is Unmanaged Non-Persistent, which does not use a binding
to a messaging engine, then any binding that you specify is ignored.