You can use the Jython or Jacl scripting language to create a custom binding to match your installation environment or requirements.
Before you use the commands in this topic, verify that you are using the most recent version of the wsadmin tool. The policy set management commands that accept a properties object as the value for the attributes or bindingLocation parameters are not supported on previous versions of the wsadmin tool. For example, the commands do not run on a Version 6.1.0.x node.
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 should be 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 JAAS configuration name.
For application policy sets, you can specify the policy set bindings at the cell-level and server-level using default binding configurations, or at the application level using custom binding configurations. If no binding information is specified during policy set attachment, the policy set inherits the default binding.
For system policy sets, you can specify the bindings at the cell-level and the server-level. The available bindings for system policy sets are the TrustServiceSymmetricDefault and TrustServiceSecurityDefault bindings. If no custom binding information is specified by the attachment, the resources inherit the TrustServiceSymmetricDefault or TrustServiceSecurityDefault binding.
In this information ...Related tasks
Related reference
| IBM Redbooks, demos, education, and more(Index) |