Use this page to manage policy sets for a Service Component Architecture (SCA) Web service client. You can attach and detach policy sets to a service reference, 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 reference can share its current policy configuration.
To view this administrative console page, your composition unit must use Web services and support SCA. Click Services > Service clients > service_client_name.
Specifies the full QName of the service client. The QName must be in a format that supports the Java™ class javax.xml.namespace.QName.
For the SCA sample business-level application HelloWorldAsync, the service client name resembles the following:
{http://websphere.ibm.com/HelloWorldServiceComponent/HelloWorldService}HelloWorldCallbackService
This SCA application has the product Web service namespace, http://websphere.ibm.com/, and the service name in its service client name.
Specifies the attached policy sets and assigned bindings for services, endpoints, or operations in the service client.
To attach or detach a policy set or to assign bindings with system-specific configurations, do the following:
Button | Resulting action |
---|---|
Attach Client Policy Set | Attaches a client policy set to the selected service,
endpoint, or operation. To attach a policy set, select a service, endpoint,
or operation and click Attach Client Policy Set > policy_set_option. To close the menu list, click Attach Client Policy Set. |
Detach Client Policy Set | Detaches a client policy set from the 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 Client 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 Client 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 | Assigns a policy set binding to the selected service,
endpoint, or operation. The options include the following:
|
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.
The Service/Endpoint/Operation column lists the service and the service references, endpoints, or operations that the service contains.
When the value in the column is a link, click the link to view or change settings about the attached policy set.
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. Composition units can use both 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 Assign Binding > New Application Specific Binding, on the 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 Assign Binding > New Application Specific Binding, on the Service clients policy sets and bindings collection page, for service client resources that have an attached policy set.
General 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 Services > Policy sets > General provider policy set bindings > New in the general provider policy sets panel, or by clicking Services > Policy sets > General client policy set bindings > 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.
Links marked (online) require access to the Internet.