Server default binding settings
Use this page to specify the server default bindings if you want to override the default bindings that are specified for the cell (global security) or the security domain to which the server is deployed.
- Click .
- From Security, click Default policy set bindings.
這個管理主控台頁面只適用於 Java™ API for XML Web Services (JAX-WS) 應用程式。
Policy set bindings for servers
To understand default policy set bindings, it is important to first understand policy set bindings.
Policy set bindings contain platform-specific information, such as keystore, authentication information or persistent information that is required by a policy set attachment. A policy set attachment is a policy set that is attached to an application resource. In WebSphere® Application Server Version 7.0 and later, there are two types of bindings, general bindings and application specific bindings.
There are two types of general bindings, general service provider bindings and general service client bindings. You can configure one or more general service provider bindings and one or more general service client bindings across a range of policy sets. Additionally, you can re-use these general bindings across applications and for trust service attachments. To define and manage general bindings, in the administrative console click
or . The general service provider and client bindings have independent settings that you can customize to meet the needs of your environment. To learn more about general bindings, read about defining and managing policy set bindings.You can create application specific bindings when you attach a policy set to an application resource. These bindings are specific to and defined to the characteristics of the 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 limited reuse across policy sets. To assign application specific bindings to an application for service providers, in the administrative console click
. To assign application specific bindings to an application for service clients, in the administrative console click .Default policy set bindings for servers

General service provider and client bindings are not linked to a particular policy set, and they provide configuration information that you can reuse across multiple applications. You can create and manage general provider and client policy set bindings and then select one of each binding to use as the default for an application server. Setting the server default bindings is useful if you want the services that are deployed to a server to share binding configuration. You can also accomplish this sharing of binding configuration by assigning the binding to each application deployed to the server or by assigning a security domain with a default binding to your server.
- Server level default
- Security domain level default
- Cell (global security) default
The general bindings that are provided with the product are initially set as the cell (global security) default bindings. The default service provider binding and the default service client bindings are used when no application specific bindings or trust service bindings are assigned to a policy set attachment. If you do not want to use the provided Provider sample as the default service provider binding, you can select an existing general provider binding or create a new general provider binding to meet your business needs. Likewise, if you do not want to use the provided Client sample as the default service client binding, you can select an existing general client binding or create a new general client binding. To specify a cell (global security) default bindings, in the administrative console click . For environments with multiple security domains, you can optionally choose the general provider and general client bindings that you want to use as the default bindings for a domain. To learn more about default policy set bindings for the cell (global security), see the default policy set bindings documentation.
In addition to choosing default bindings for the cell (global security), you can also choose the general provider and general client bindings that you want to use as the default bindings for a server. Use this page to choose the default bindings for a server from the administrative console. Click Default policy set bindings. If you do not choose a general binding as the default for a server, the default bindings for the domain in which the server resides is used. If you do not choose a binding as the default for a domain, the default bindings for the cell (global security) is used. You must choose a default service provider and default service client bindings for the cell. The general bindings that are included with the product are initially set as the cell (global security) default bindings. You cannot delete a binding that has been selected as the default binding for server, a domain, or the cell. Before you delete the binding, you must select a different binding as the default or choose to use the defaults for the cell (global security).
and then from Security, click
如果您的應用程式含有一或多個在 WebSphere Application Server 6.1 版層次配置的應用程式特定連結,則這個應用程式是一個 6.1 版應用程式。如果您的應用程式是部署於 6.1 版的伺服器(但於 7.0 版或更新版本的應用程式伺服器環境內),或您擁有 6.1 版應用程式(部署於 7.0 版或更新版本的應用程式伺服器),您可以對 Cell 指定 6.1 版預設原則集連結。 這些連結用於 6.1 版應用程式內的用戶端和提供者原則集附件,以及 6.1 版伺服器所部署的服務應用程式附件。此外,除非在附件點由應用程式特定連結或 6.1 版伺服器預設連結置換,否則這些預設連結會用於 6.1 版附件。您可以將 6.1 版連結升級為 WebSphere Application Server 7.0 版及更新版本所用的連結。如果 6.1 版應用程式不是安裝在 WebSphere Application Server 6.1 版上,請利用 wsadmin 工具,以 upgradeBindings 指令來升級連結層次。
mixv根據啟用安全時所指派的安全角色而定,您可能會有建立或編輯配置資料之文字輸入欄位或按鈕的存取權。 請檢閱管理角色說明文件,以進一步瞭解應用程式伺服器的有效角色。
Server default provider binding
Specifies the default server binding. Select the name of the binding you want to use as the default for service providers deployed to this server.
If you are using multiple security domains, the name of the security domain to which the binding is scoped is specified with the name of the server default provider binding. Only bindings that are scoped to global security or to the security domain to which the server is assigned are available in the list.

Server default client binding
Specifies the default client binding. Select the name of the binding you want to use as the default for service clients deployed to this server.
If you are using multiple security domains, the name of the security domain to which the binding is scoped is specified with the name of the server default client binding. Only bindings that are scoped to global security or to the security domain to which the server is assigned are available in the list.

Version 6.1 default bindings
If you have a Version 6.1 application that you want to use in the Version 7.0 and later application server environment and you want to specify Version 6.1 default bindings for this server, you can click this link to specify Version 6.1 default bindings.