Deleting application-specific bindings from your configuration using wsadmin scripting
You can use the Jython or Jacl scripting language to delete a custom application or system policy set binding from your configuration. You cannot delete cell-level default bindings.
Before you begin
在使用這個主題中的指令之前,請確認您使用 wsadmin 工具的最新版本。 在舊版的 wsadmin 工具中,不支援接受內容物件作為 attributes 或 bindingLocation 參數值的原則集管理指令。 例如,在 6.1.0.x 版節點上,不執行這些指令。
Administrative role | Authorization |
---|---|
Administrator | The Administrator role must have cell-wide access to modify bindings. If you have access to a specific resource only, you can modify bindings for the resource for which you have access. |
Configurator | The Configurator role cannot modify bindings. |
Deployer | The Deployer role cannot modify bindings. |
Operator | The Operator role cannot modify bindings. |
Monitor | The Monitor role cannot modify bindings. |
About this task
Policy set bindings specify the details about how your quality of service (QoS) is configured. For example, a policy set attachment determines that sign, encrypt, or reliable messaging is enabled. The policy set binding specifies how the protection is configured, for example, the path of the keystore file, the class name of the token generator, or the Java Authentication and Authorization Service (JAAS) configuration name.
For application policy sets, policy set bindings exist at the cell-level and server-level using default binding configurations, or at the application level using application-specific binding configurations. You can also specify cell-level general bindings. For system policy sets, bindings exist at the cell level and server level, or you can create application-specific bindings.
Use the following procedure to delete application-specific bindings for trust policy sets and application level bindings for application policy sets:
Procedure
Results
The application-specific binding of interest is removed from your configuration.