WebSphere Application Server Version 6.1 Feature Pack for Web Services
             Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

             Personalize the table of contents and search results
             New or updated topic for this feature pack

Defining binding information for policy sets

You can define default bindings at the cell-level or the application server level, and for one or multiple policy sets in a cell.

About this task

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. When you create a policy set attachment, the default bindings are used initially. When default bindings are used in association with a policy set attachment, the cell-level default bindings are applied at runtime. If application server level bindings exist, the server-level default bindings override the cell-level definition. Default bindings specify configuration for both service client and service provider attachments and the default bindings are not tailored to a specific policy set or application. When you define server-level default bindings, 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 you must fully configure the bindings for each policy that you have added.

A custom binding is a named binding that you create. Custom bindings enable you to provide platform specific configuration information for specific policy set attachments. When you create a custom binding, the available binding configuration options are tailored to the definitions in the attached policy set. You can reuse custom bindings for multiple service resources within an application. When you create a custom 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 you must fully configure the bindings for each policy that you have added.

Note: Use the default bindings in a testing environment. Do not use default bindings in a production environment. Default bindings contain sample key files that must be customized before use in a production environment.
Complete these steps to:
  • Use the default bindings from the cell or application server level.
  • Use the existing custom bindings in the same application
  • Create a new custom binding for the attachment

Procedure

  1. To view your current policy set and binding configuration from the administrative console, click Services > Policy sets > Application policy sets > policy_set_name > Attached applications and then click an application. Depending on the application that you select, use one of the following topics for help with the bindings attached to policy sets: Sort on the Attached policy set column on either of the policy sets and bindings pages to select the service resources with the same policy set attached. Likewise, sort on the Binding column to select the service resources that share the same custom binding to attach to a different policy set. If you sort on the Policy Set or the Binding column, the hierarchical relationship of the service resources in the first column is not accurate. You can sort again on the Application/Service/Endpoint/Operation column to restore the hierarchical relationship. The entries in the Application/Service/Endpoint/Operation column display in ascending order.
  2. To work with specific policy bindings from the administrative console, click Services > Policy sets > Application policy sets > policy_set_name > Attached applications. Click an application name, and then click either the Service provider policy sets and bindings or the Service client policy sets and bindings. Then click a binding name in the Bindings column of the table.
    Note: If no applications appear when you click Attached applications, you do not have any applications attached to the selected policy set. To attach a policy set and binding to an application using the administrative console, click Applications > Enterprise Applications > application name. Then, click either Service provider policy sets and bindings or Server client policy sets and bindings to attach resources to your policy set and to assign bindings.
    .
  3. Define default bindings at the server or cell level.
    • To define default bindings at the cell level, click Services > Policy sets > Default policy set bindings .
    • To define default bindings at the application server level, click Servers > Application servers > server_name >Default policy set bindings .

    For information on how to access the policy bindings, read about default policy set bindings settings.

Results

When you finish this task, you have viewed and altered the bindings for a policy in a policy set.



In this information ...


IBM Redbooks, demos, education, and more


Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

IBM Suggests
Task topic    

Terms of Use | Feedback

Last updated: Nov 25, 2008 2:35:59 AM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.wsfep.multiplatform.doc/info/ae/ae/twbs_wsspsbin.html