Use this page to attach and detach policy sets to an application, a service client, its endpoints or operations. You can select the default bindings, create new application-specific bindings, or use existing bindings for an attached policy set. You can view or change whether the client uses the policy of the service provider.
This panel displays detail information for an application and its associated Web service clients, endpoints and operations. You can view and manage policy set attachments and bindings information using this page.
To view this administrative console page, click
.Policy set bindings contain platform specific information, like keystore, authentication information or persistent information, required by a policy set attachment. When you create a policy set attachment, if the server is in a security domain and there is a default binding for the security domain, that default binding is applied; otherwise, the default global security domain bindings are used initially. You can create or customize the bindings.
Application specific bindings enable you to provide platform specific configuration information for specific policy set attachments. When you create an application specific binding, the available binding configuration options are tailored to the definitions in the attached policy set. You can reuse application specific bindings for multiple service resources within an application. 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 you must fully configure the bindings for each policy that you have added.
In support of multiple security domains, each of the named bindings is scoped to a security domain. With domain scoping, applicable configuration settings in the bindings, such as JAAS logins, is constrained based on the configuration attributes of the assigned domain. The default domain for bindings is the global security domain, and bindings scoped to the global security domain is available for all attachments, regardless of the domain in which the attached resource resides. Each service client or provider always has a binding because the global security default bindings cannot be removed. In fact, a service client or provider might have many layers of bindings because of the product configuration options. Such configuration options are application specific, domain level, global security, and server level.
The general bindings that are shipped with the product are provider and client sample general bindings. General bindings have two cell level defaults; one for the providers and one for the clients. Do not use these bindings in their current state in a production environment. However, if they were modified to contain non-sample data, they could be used in a production environment.
You cannot assign a binding to a service provider resource that does not have a policy set or has an inherited attachment. To assign a binding to such a service provider resource, you must first attach a policy set to the resource. Also, you cannot assign a binding to a service client resource that does not have an effective policy configuration or has an inherited policy attachment. To assign a binding to such a service client resource, you must first attach a policy set or specify the use of the provider policy.
依啟用安全時所指派的安全角色而定,您可能會有建立或編輯配置資料之文字輸入欄位或按鈕的存取權。 請檢閱管理角色文件,以進一步瞭解應用程式伺服器的有效角色。
標示(線上)的鏈結表示需要存取網際網路。