When working with policy sets in the administrative console, you
can customize some policies.
Before you begin
This task assumes that you are working with a policy set to which
the WS-ReliableMessaging policy has been added.
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.
About this task
To configure the WS-ReliableMessaging policy for a given policy set,
use the administrative console to complete the following steps:
Procedure
- In the navigation pane, click .
The WS-ReliableMessaging settings form is displayed.
- Modify one or more of the following properties:
- 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, or if you want
to enable transaction support for inbound (provider) message exchanges as
described in Providing transactional recoverable messaging through WS-ReliableMessaging, or
if you want to marginally increase reliability as described in WS-ReliableMessaging troubleshooting tips.
Tip: When
you enable this option, WS-ReliableMessaging ensures that the messages are
made available to the requester application in the order that they were sent.
That is, if WS-ReliableMessaging cannot make a given message available, it
will not make any subsequent messages available. However, the requester application
must also poll for the messages in the order in which it wants to receive
them. For example:
- WS-ReliableMessaging makes message 1 available, then message 2, then message
3.
- The requester application uses asynchronous polling to deliberately poll
for message 2, then message 3, then message 1. All three messages are available,
so this polling out of order is successful.
Even though WS-ReliableMessaging is delivering the messages in the order
that they were sent, the requester application is choosing to receive them
out of order.
- Quality of service
- Click a radio button to choose the required quality of service. The three
choices are:
- Unmanaged non-persistent
- 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.
- Managed non-persistent
- 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
- 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.
The default is unmanaged non-persistent.
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.
- Click OK.
- Save your changes to the master configuration.
Results
After you have customized the reliable messaging policy, the associated
policy set uses this policy to help ensure reliable delivery of messages.