+

Search Tips   |   Advanced Search

Set a WS-ReliableMessaging policy set using wsadmin


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 command scripts to configure a policy set for reliable messaging.

Configure a reliable messaging policy set using wsadmin or we can configure a reliable messaging policy set .

The following default policy sets work with WS-ReliableMessaging applications:

See WS-ReliableMessaging default policy sets.

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

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.

To configure a reliable messaging policy set using wsadmin...

 

  1. Create a policy set. Use the createPolicySet command to create a new policy set, or the copyPolicySet command to copy and rename an existing policy set - either one that we have previously created, or one of the two WS-ReliableMessaging default policy sets.

    See Creating and copying policy sets using wsadmin.

  2. If the policy set does not include both the policy types WSReliableMessaging and WSAddressing, add these policy types using addPolicyType.

    AdminTask.addPolicyType('[-policySet PolicySet1 -policyType WSReliableMessaging]')
    AdminTask.addPolicyType('[-policySet PolicySet1 -policyType WSAddressing]')

    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 V1.1 synchronous messaging. Notes:

    • 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 we 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 Set WS-SecureConversation to work with WS-ReliableMessaging.

    • WS-ReliableMessaging V1.1 messaging requires WS-Addressing to be mandatory. If we use a policy set that includes WS-ReliableMessaging and WS-Addressing policies, and the WS-Addressing policy is configured as optional, then WAS overrides the WS-Addressing setting and automatically enables WS-Addressing.

  3. Set the WS-ReliableMessaging policy type attributes.

    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. For detailed information about these configurable attributes, see WS-ReliableMessaging settings. Use the setPolicyType command to configure these attributes. For example:

    AdminTask.setPolicyType('-policySet PolicySet1 -policyType WSReliableMessaging -attributes "[[inOrderDelivery false][specLevel 1.0] [enabled true][qualityOfService managedPersistent][type WSReliableMessaging]]" -replace'

  4. Save the changes to the master configuration.

    To save the configuration changes...

    AdminConfig.save()

 

Next steps

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

 

Related tasks


Set WS-SecureConversation to work with WS-ReliableMessaging
Set endpoints to only support clients that use WS-ReliableMessaging
Building a reliable Web service application
Learn about WS-ReliableMessaging
Detecting and fixing problems with WS-ReliableMessaging
Set a WS-ReliableMessaging policy set

 

Related information


Set application and system policy sets for Web services using scripting