Use this page to attach and detach policy sets to an application, a service provider, its endpoints, or operations. You can select the default bindings, create new application-specific bindings, or use bindings that you created for an attached policy set. You can view or change whether the service provider can share its current policy configuration.
This page provides detail information for an application and its associated Web service providers, endpoints, and operations. You can view and manage policy set attachments and bindings information using this page.
To view this administrative console page, click
.Depending on your assigned security role when security is enabled, you might not have access to text entry fields or buttons to create or edit configuration data. Review the administrative roles documentation to learn more about the valid roles for the application server.
Specifies the name of the application and the associated service providers, endpoints or operations.
The Application/Service/Endpoint/Operation column lists the service application and the service providers, endpoints, or operations that the application contains.
Specifies the policy set that is attached to a service provider, endpoint, or operation.
When the value in the column is a link, click the link to view or change settings about the attached policy set.
Specifies the binding configuration that is available for a service provider, endpoint, or operation.
When the value in the Binding column is a link, click the link to view or change settings about the binding.
In this release, there are two types of bindings: application-specific bindings and general bindings.
Application-specific bindings
You can create application-specific bindings only at a policy set attachment point. These bindings are specific to, and constrained by, the characteristics of the defined policy. Application-specific bindings can provide configuration for advanced policy requirements such as multiple signatures; however, these bindings are reusable only within an application. Also, application-specific bindings have very limited reuse across policy sets.
When you create an application-specific binding for a policy set attachment, the binding begins in a completely unconfigured state. You must add each policy, such as WS-Security or HTTP transport, that you want to override the default binding, and fully configure the bindings for each policy that you add. For WS-Security policy, some high level configuration attributes such as TokenConsumer, TokenGenerator, SigningInfo, or EncryptionInfo might be obtained from the default bindings if they are not configured in the application-specific bindings.
For service providers, you can create application-specific bindings only by selecting Service providers policy sets and bindings collection page, for service provider resources that have an attached policy set. Similarly, for service clients, you can create application-specific bindings only by selecting , on the Service clients policy sets and bindings collection page, for service client resources that have an attached policy set.
, on theGeneral bindings
You can configure general bindings to be used across a range of policy sets and they can be reused across applications and for trust service attachments. Although general bindings are highly reusable, they cannot provide configuration for advanced policy requirements such as multiple signatures. There are two types of general bindings: general provider policy set bindings and general client policy set bindings.
You can create general provider policy set bindings by clicking New in the general provider policy sets panel, or by clicking > New in the general client policy set and bindings panel. For details about defining and managing service client or provider bindings, see the related links. General provider policy set bindings might also be used for trust service attachments.
>Specifies whether the service provider can share its current policy configuration.
When the value in the column is a link, click the link to view or change settings about how the policy configuration can be shared.
For a service, if the policy set is inherited from the parent application, the policy sharing value is also inherited, and you cannot change it. The value is not a link and it is followed by the term inherited in parentheses.
For an endpoint or operation, the value is not a link and it is followed by the term inherited in parentheses. The setting is inherited from the parent application or service and you cannot change it.
Attach Policy Set | Click this button to view a list of policy sets available for attachment to the selected service, endpoint, or operation. Select a policy set from the list to attach and it is attached to the selected service, endpoint, or operation. To close the menu list, click Attach Policy Set. |
Detach Policy Set | Click this button to detach a policy set from a selected
service, endpoint, or operation. After the policy set is detached,
if there is no policy set attached to an upper level service resource,
the Attached Policy Set column displays None and
the Binding column displays Not Applicable. If there is a policy set attached to an upper level service resource, the Attached Policy Set column displays policy_set_name (inherited) and the binding used for the upper level attachment is applied. The binding name is displayed followed by (inherited). |
Assign Binding | Click this button to select from a list of available bindings
for the selected policy set attachment. All the bindings are listed
along with the following options:
To close the menu list, click Assign Binding. |