Configuring a WS-ReliableMessaging policy set by using the administrative console

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. Use the administrative console to configure a policy set for reliable messaging.

Before you begin

You can configure a reliable messaging policy set by using the administrative console as described in this task, or you can configure a reliable messaging policy set by using the wsadmin tool.

The following default policy sets work with WS-ReliableMessaging applications:
  • WS-I RSP
  • WS-I RSP ND
  • LTPA WS-I RSP
  • Username WS-I RSP
  • WSReliableMessaging 1_0
  • WSReliableMessaging default
  • WSReliableMessaging persistent
For more information, see WS-ReliableMessaging default policy sets.

If you can use any of these default policy sets without needing to modify their configuration, you need not complete this task. You are ready to attach and bind the default policy set to your application.

At any stage - that is, before or after you have built your reliable web service application, or configured your policy sets - you can set a property that configures endpoints to only support clients that use reliable messaging. This setting is reflected by WS-Policy if engaged.

About this task

To configure a reliable messaging policy set by using the administrative console, complete the following steps:

Procedure

  1. Create a policy set. You can create a new policy set, or copy and rename an existing policy set - either one that you have previously created, or one of the WS-ReliableMessaging default policy sets.
  2. Check that your policy set includes the policy types WS-ReliableMessaging and WS-Addressing. Add these policy types if necessary. These policy types contain the configuration options that support WS-ReliableMessaging. WS-Addressing provides the asynchronous request and reply capabilities for WS-ReliableMessaging, and is also required for WS-ReliableMessaging Version 1.1 synchronous messaging.
    Notes:
    • If you want to use secure conversation and reliable messaging policies in the same policy set, the secure conversation bindings must be configured to require that the reliable messaging headers are signed. The reliable secure profile default policy sets (WS-I RSP and WS-I RSP ND) are specifically designed and configured to use secure conversation and reliable messaging in the same policy set. If you use a copy of one of the reliable secure profile default policy sets (WS-I RSP and WS-I RSP ND), no further configuration of the secure conversation bindings is required. Otherwise, see Configuring WS-SecureConversation to work with WS-ReliableMessaging.
    • WS-ReliableMessaging Version 1.1 messaging requires WS-Addressing to be mandatory. If you use a policy set that includes WS-ReliableMessaging and WS-Addressing policies, and the WS-Addressing policy is configured as optional, then WebSphere Application Server overrides the WS-Addressing setting and automatically enables WS-Addressing.
  3. Configure the WS-ReliableMessaging policy type attributes. For the WS-ReliableMessaging policy you can configure the version of the WS-ReliableMessaging standard that you want to use, the order in which messages are delivered, and the required quality of service (the reliability level) for message delivery.
    Note: In WebSphere Application Server Version 6.1, you could also configure whether or not to use the WS-MakeConnection protocol. This configuration option has now been removed from the administrative console panel, because the product now automatically determines whether WS-MakeConnection is used, based on the following criteria:
    • Whether you are using WS-ReliableMessaging Version 1.0 or Version 1.1.
    • Whether the requester supports WS-MakeConnection.
    • Whether the message exchange protocol is synchronous or asynchronous.
  4. If required, configure the WS-Addressing policy type attributes. For example, the default WS-Addressing policy messaging style is Synchronous and asynchronous, which specifies that there is no restriction on the targeting of response messages. However if you enable policy sharing, the WS-Policy framework determines which style to use, and has a preference for the synchronous request-response pattern. Because the WS-Policy framework takes precedence, reliable messages are sent in a synchronous request-response pattern even if your client invokes the service asynchronously. To enforce asynchronous messaging, set the WS-Addressing policy messaging style to asynchronous only.
  5. Save your changes to the master configuration.

What to do next

You are now ready to attach your application to the policy set and define the bindings that you want to use.



In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms of Use | Feedback

Last updatedLast updated: Sep 19, 2011 5:16:49 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-base-iseries&topic=twbs_wsrm_policy_config
File name: twbs_wsrm_policy_config.html