Service client policy sets and bindings collection

Use this page to attach or detach service client policy sets from the application or its services, endpoints, or operations. Configure the attached bindings by using default bindings, creating new bindings, or using existing bindings for your application.

To view this administrative console page to attach a policy set to a client application, service, endpoint, or operation, complete the following actions:
  1. Click Application > Enterprise Applications.
  2. Select an application that contains Web services. The application must contain a service client. Click on the application_name link.
  3. Click the Service client policy sets and bindings link.
To view this administrative console page to detach a policy set from a server-based client resource, complete the following actions:
  1. Click Services > Policy sets > Application policy sets.
  2. Click on a policy_set_name link.
  3. Click the Attached applications link in the Additional Properties section.
  4. Click an application from the listing.
  5. Click the Service client policy sets and bindings link from the Web Services Properties section.
Application/Service Client/Endpoint/Operation

Specifies a service application and the associated service client, endpoints or operations.

Policy Set

Specifies the policy set attached to the service resource. The policy set column might show:

  • None, if there is no policy set attached directly nor attached at an upper level.
  • <Policy Set name>, for example, Ramp default if a policy set is attached directly.
  • <Policy Set name>(inherited), if a policy set is not directly attached to that level but a policy set is attached at an upper level.
  • Sub-level attachments, if a policy set is attached at the lower level and you are viewing the upper level attachment. Sub level policy set attachments do not appear.
Binding

Specifies the name of the binding associated with a policy set. The Binding column might show:

  • Not applicable, if there is no policy set attached directly nor attached at an upper or lower level.
  • <Bindings name>, for example, MyBindings1 or Default if a policy set is attached directly.
  • <Bindings name>(inherited) or Default(inherited), if a service resource inherits the bindings from an upper level attachment.
  • Sub-level binding, if the bindings are set at the lower level and you are viewing the upper level settings.
A service resource refers to the entities that you attach a policy set and assign bindings to. A service resource that inherits a policy set must inherit the bindings for that policy set. You can attach a policy set, detach a policy set and configure the bindings by clicking the appropriate button. The resulting action affects only the resources that you selected.
Button Resulting action
Attach Click this button to view a list of policy sets available to be attached to your application, service client, endpoint or operation. Select a policy set from the list and it is attached to the selected application, service client, endpoint or operation.
Detach

You can click this button to detach a policy set from a selected application, endpoint or operation. After the policy set is detached, if there is no policy set attached to an upper level resource, the Policy Set column displays None and the Binding column displays Not Applicable.

If there is a policy set attached to an upper level resource, the Policy Set column displays the <policy set name>(inherited) and the binding used for the upper level attachment is applied. The binding name is displayed with inherited added to it.

Assign Binding

Click this button to assign bindings from a list of available bindings for the selected policy set attachment. You can choose the default bindings for the selected application, service, endpoint or operation. The button is disabled if multiple resources with different policy sets are selected. Multi-select option is only available if all the resources have the same policy set attached.

You can create new bindings for the application and policy set attachment. The new binding you create is used for the affected resource. The new binding is disabled if multiple resources with different policy sets are selected. Multi-select option is only available if all resources have the same policy set attached.

Note: If you attach a new or different policy set to a resource, the binding reverts to the Default binding. The Default binding is initially used for all new policy set attachments.
To support the default binding for a client that runs on the server or a server based client using an asymmetric binding, the signing and the encryption keys must be the same for the client and the server. When both the client and server require the same default binding, no security is provided. Use this only for development purposes but not for production.



Links marked (online) require access to the Internet.

Related tasks
Related reference

uwbs_wsspsbinc