Use this administrative console task to manage policy sets and bindings for the service reference, its endpoints, and operations.
Before completing this task, you must install one or more Java API for API for XML-based Web Services (JAX-WS) web services, that contain at least one client service reference.
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.
When you configure the policy set attachments for a service reference, you can override the policy set attachments that are inherited from the service client using the administrative console. You can attach a policy set and binding for a service reference that is different from the policy set attachment for the service client. You can also specify to not attach a policy set to a service reference, even if a policy set is attached to the service client.
The default behavior is that a service reference, and its endpoints and operations, inherits the policy set attachment of the corresponding resources of the service. Service references are only valid for service clients.
Using the administrative console, you can configure the service reference to either inherit policy set and bindings configuration from the service client or to specify individual settings for the service reference by attaching policy sets and bindings that are different from the policy sets and bindings attached to the service client.
The policy set information is displayed in the Attached Policy Set column. If a policy set is directly attached, then the policy set name is displayed; for example, WS-I RSP. If there is no policy set attached, and a policy set is attached at a higher level or to the service client, 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.
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 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:
You can create general client policy set bindings by accessing New in the general provider policy sets panel or by accessing > New in the general client policy set and bindings panel. See defining and managing service client or provider bindings.
>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.
When you finish this task, you have specified policy sets and bindings for a service reference.
You can now proceed to manage other service references for the service client or to manage policy sets and bindings for service clients at the application level using the administrative console.