Managing policy sets and bindings for service clients at the application level using the administrative console
Use this administrative console task to manage policy sets for service clients applications or its services, endpoints, or operations.
Before you begin
About this task
You have developed a web service that contains all the necessary artifacts and deployed your web services application into your application server instance. Now, you can attach or detach policy sets and manage the associated bindings.
The policy set information is displayed in the Attached Policy Set column. If a policy set is
directly attached, then the policy set name appears; for example, WS-I RSP
is
displayed. If there is no policy set attached, and a policy set is attached at a higher level, then
the word inherited in parentheses is appended to the policy set name, as the following
example demonstrates: WS-I RSP (inherited)
. If there is no policy set attached
directly or at a higher level, then None
is displayed.
- Not applicable. There is no policy set attached, either directly or to a higher level service resource.
- Binding_name or Default. The binding name is displayed if a policy set is
attached directly and an application-specific binding or a general binding is assigned, for example,
MyBindings1
. Default is displayed if a policy set is attached directly but the service resource uses the default bindings. - Binding_name (inherited) or Default (inherited). A service resource inherits the bindings from an attachment to a higher level resource.
In Version 7.0 and later of this product, there are two types of bindings, application specific bindings and general bindings.
Application specific binding
You can create application specific bindings only at a policy set attachment point. These bindings are specific to and constrained to the characteristics of the defined policy. Application specific bindings are capable of providing configuration for advanced policy requirements, such as multiple signatures; however, these bindings are only reusable within an application. Furthermore, 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 have added. 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 clients, you can only create application specific bindings by selecting
for service client resources that have an attached policy set. See service clients policy sets and bindings collection. Similarly, for service clients, you can only create application specific bindings by selecting for service client resources that have an attached policy set. See service client policy set and bindings collection.General bindings
General bindings were introduced in Version 7.0 of this product. These bindings can be configured to be used across a range of policy sets and can be reused across applications and for trust service attachments. Though general bindings are highly reusable, they are however not able to provide configuration for advanced policy requirements, such as multiple signatures. There are two types of general bindings:
- General provider policy set bindings
- General client policy set bindings
You can create general policy set bindings by copying an existing binding or by creating a new one. For WS-Security bindings, copy an existing sample binding. Creating a new policy set binding from scratch for WS-Security can cause unexpected problems at run time.
To create general provider policy set bindings, in the administrative console, select
. To create general client policy set bindings, select .For more information, see Defining and managing service client or provider bindings. General provider policy set bindings can also be used for trust service attachments.
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.
Procedure
Results
Example
If you have configured a service client application instance, app1
and you want,
for example, to attach the Username WSSecurity default policy set to your application, first locate
app1
application in the . Click under the Web Services Properties section. Select the check box next to the
app1
service application. Click Attach and select
Username WSSecurity default policy set. Click Save, to save your
changes to the master configuration.
To assign a binding to the attached policy set, click app1
service application and click
Assign Binding. Select client sample binding from the
list. Click Save, to save your changes to the master configuration.