Modifying policies using the administrative console

With your policy sets, you can define policies for WS-Addressing, WS-Security, WS-ReliableMessaging, HTTP transport, and SSL transport. The policies for all but WS-Security are relatively straightforward to define. Only user-created policy sets can be modified.

Before you begin

A user-created policy set must exist. The provided default policy sets cannot be edited. You can create a copy of the default policy set or create a completely new policy set in order to specify the policies for it.

About this task

Polices are associated with policy sets, so you can change an instance of a policy for a particular policy set.

Procedure

  1. Select the policy set containing the policy you want to modify. To customize the policies associated with a policy set, from the administrative console, click:
    • Services > Policy sets > Application policy sets > policy set name (where the selected policy set is a custom policy set and can be edited). Click a policy name in the Policies table.
    • Or Services > Policy sets > System policy sets > policy set name. Click a policy name in the Policies table.
  2. Modify the settings. Depending on which Policy you choose, different settings can be modified. The WS-Addressing and WS-Transaction policies have no properties that can be configured. They are either included and enabled in the policy set or not included or enabled.
  3. [Optional] If the policy to be modified is not already in the Policies table, click Add and select a policy from the list to modify.
  4. Save the changes you have made. Once you change the settings on a policy, you need to save the changes to return to the policy set.

Results

The policy set configuration is saved with the selected modifications.

Example

You have created a copy of the WSReliableMessaging persistent default policy set and named it WSRM_p1. You want to change the settings on the WSReliableMessaging policy that is included in the copy of this policy set, so you click your WSRM_p1 policy set from the Application policy sets window and then click the WSReliableMessaging policy from the Policies table. You can then alter the following settings:
Standard
The default setting is WSReliableMessaging 1.1.
Deliver messages in the order that they were sent
The default setting is false. Valid values are true or false.
Quality of service
The default is Unmanaged non-persistent
Enable 'MakeConnection' for synchronous two-way message exchange
This setting is selected by default.
You save your changes and return to the Application policy sets window for the WSRM_p1 policy set.

What to do next

You can use the policy set as it now is or you can change bindings or attach or detach it from applications.
Note: Because this policy set specifies managed persistent quality of service, you need to define bindings to the service integration bus and messaging engine that you want to use to manage the WS-ReliableMessaging state. For more information, see Attaching and binding a WS-ReliableMessaging policy set to a Web service application using the administrative console or using the wsadmin tool.



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 and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 1:23:07 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-dist&topic=twbs_wsspsptmod
File name: twbs_wsspsptmod.html