Policy set bindings settings
To view or define general or application specific bindings configuration information that is specific to a system for policies that we can associate with the selected policy set. Use the links on this page to work with bindings for each specific policy.
To view this admin console page when we are editing a general binding, click Services > Policy sets > General provider policy set bindings or Services > Policy sets > General client.policy set bindings.
To view this admin console page when we are creating or editing an application specific binding...
- Click Applications > Application Types > WebSphere enterprise apps.
- Select an application that contains Web services. The application must contain a service provider or a service client.
- Click Service provider policy sets and bindings or Service client policy sets and bindings in the Web Services Properties section.
- Select a binding by clicking the binding name in the table if the binding has been assigned to an attachment. You must have previously attached a policy set and assigned an application specific binding.
- [Optional] To edit a default cell binding or default server binding, click eitherServices > Policy sets > General provider policy set bindings or Services > Policy sets > General client.policy set bindings.
This admin console panel applies only to Java™ API for XML Web Services (JAX-WS) applications.
About Policy set bindings
Policy set bindings contain platform-specific information, like keystore, authentication information or persistent information, required by a policy set attachment. Each policy set attachment to a service provider or service client must have exactly one binding. By creating a policy set attachment, the general default bindings are used initially. When general bindings are used in association with a policy set attachment, the cell-level general bindings are applied at run time. If appserver level bindings exist, the server-level general bindings override the cell-level definition. General bindings specify configuration for both service client and service provider attachments and the general bindings are not tailored to a specific policy set or application.
When you define server-level general bindings, the binding begins in a completely unconfigured state. You must add each policy, such as WS-Security or HTTP Transport, to override the general binding and fully configure the bindings for each policy that we have added.
An application specific binding is a named binding created. Application specific bindings enable you to provide platform-specific configuration information for specific policy set attachments. By creating an application specific binding, the available binding configuration options are tailored to the definitions in the attached policy set. We can reuse application specific bindings for multiple service resources within an application. For example, if we create a trust service specific binding, that binding can be reused only for trust service attachments. By 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, that you want to override the general binding and fully configure the bindings for each policy that we have added.
Depending on the assigned security role when security is enabled, we 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 appserver.
- Bindings configuration name
Name of the policy set bindings configuration. The binding name is not editable when we are editing a binding. When we are creating a new binding, specify the binding name.
If running a V6.1 application, the Binding configuration name is displayed as V6.1 default policy set bindings
Use the following actions to create, edit, or delete policy set bindings.
Button Resulting action Add Adds the selected policy set binding to the application. Delete Removes the selected policy set binding from the application.
- Policies – HTTP transport
Links to the HTTP transport policy settings page where you define the HTTP transport settings. The HTTP features and HTTP connection polices are applied to outbound messages. The response listener policy is enforced on inbound messages.
- Policies – SSL transport
Links to the SSL transport policy settings page where you define the SSL transport settings.
- Policies – JMS transport
Links to the JMS transport policy settings page where you define the JMS transport settings.
- Policies – WS-Addressing
Links to the settings page for the WS-Addressing policy. In an ND environment, use this page enable or disable workload management. Otherwise, we can attach the WS-Addressing policy set to service resources. No additional configuration is required.
- Policies – WS-ReliableMessaging
Links to the panel where the WS-ReliableMessaging bindings are configured.
- Policies – WS-Security
Links to the WS-Security policy set bindings settings page where the WS-Security bindings are configured.
Related tasks
Manage policy sets
Set policy set bindings
Related
WS-ReliableMessaging settings
SSL transport security settings
HTTP transport policy settings
Keys and certificates
WS-Security authentication and protection
Caller collection
Caller settings
Message expiration settings
Actor roles settings
Application policy sets collection
Application policy set settings
Search attached applications collection
Administrative roles
Related information
Web Services Addressing policy set binding