WAS v8.5 > Reference > Sets

SCA service client settings page

Use this page to manage policy sets for a Service Component Architecture (SCA) web service client. We can attach and detach policy sets to a service reference, its endpoints, or operations. We can select the default bindings, create new application-specific bindings, or use bindings created for an attached policy set. We can view or change whether the service reference can share its current policy configuration.

To view this dmgr console page, your composition unit must use web services and support SCA. Click Services > Service clients > service_client_name.


Service client

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:

This SCA application has the product web service namespace, http://websphere.ibm.com/, and the service name in its service client name.


Policy Set Attachments

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:

  1. Select a service, endpoint, or operation. The Service/Endpoint/Operation list is nested, indicating parent-child relationships.

  2. Click the desired button.

Button descriptions. Use the buttons to attach or detach client policy sets and to assign policy set bindings.

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:

Default

Specifies the default binding for the selected service, endpoint, or operation. We can specify client and provider default bindings to be used at the cell level or global security domain level, for a particular server, or for a security domain. The default bindings are used when an application-specific binding has not been assigned to the attachment. When you attach a policy set to a service resource, the binding is initially set to the default. If we do not specifically assign a binding to the attachment point using this Assign Binding action, the default specified at the nearest scope is used.

For any policy set attachment, the run time checks to see if the attachment includes a binding. If so, it uses that binding. If not, the run time checks in the following order and uses the first available default binding:

  1. Default general bindings for the server
  2. Default general bindings for the domain in which the server resides
  3. Default general bindings for the global security domain

New Application Specific Binding

Select this option to create a new application-specific binding for the policy set attachments. The new binding you create is used for the selected resources. If you select more than one resource, ensure that all selected resources have the same policy set attached.

Client sample

Select this option to use the Client sample binding.

Client sample V2

Select this option to use the Client sample V2 binding when we are using either the Kerberos V5 WSSecurity default or the TrustServiceKerberosDefault policy sets.

Saml Bearer Client sample

Select this option to use the Saml Bearer Client sample. The Saml Bearer Client sample extends the Client sample binding to support SAML Bearer token usage scenarios. We can use this sample with any of the SAML bearer token default policy sets.

Saml HoK Symmetric Client sample

Select this option to use the Saml HoK Symmetric Client sample. The Saml HoK Symmetric Client sample extends the Client sample binding to support SAML holder-of-key (HoK) symmetric key token usage scenarios. We can use this sample with one of the SAML HoK Symmetric key default policy sets: either SAML11 HoK Symmetric WSSecurity default or SAML20 HoK Symmetric WSSecurity default.

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.

Service/Endpoint/Operation

Specifies the name of the service and the associated service references, endpoints or operations.

The Service/Endpoint/Operation column lists the service and the service references, endpoints, or operations the service contains.

Attached Client Policy Set

Policy set that is attached to a service reference, endpoint, or operation.

The Attached Client Policy Set column can contain the following values:

  • None. No policy set is attached, either directly or to a higher-level service resource.
  • Policy_set_name. The name of the policy set that is attached directly to the service resource, for example, WS-I RSP.
  • Policy_set_name (inherited). The name of the policy set not attached directly to a service resource, but that is attached to a higher-level service resource.

When the value in the column is a link, click the link to view or change settings about the attached policy set.

Binding

Binding configuration that is available for a service reference, endpoint, or operation.

The Binding column can contain the following values:

  • Not applicable. No policy set is 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.

When the value in the Binding column is a link, click the link to view or change settings about the binding.


About policy set bindings

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

We 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 creating 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, 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, we 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, we 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

We 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.

We 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.


Related


Composition unit settings
References policy sets and bindings collection for SCA composites
Create SCA business-level applications
Define and managing policy set bindings
Define and managing service client or provider bindings
Manage policy sets


+

Search Tips   |   Advanced Search