CustomProperties policy and binding properties
Use the -attributes parameter for the setBinding command to specify additional configuration information for the CustomProperties policy set binding. Application and system policy sets can use the CustomProperties policy and binding.
This product supports using the CustomProperties policy and binding to set generic properties that are not supported in other policy types. The additional properties are set in the binding. We must only update existing properties, such as the enabled attribute, in the policy. The CustomProperties policy provides an alternative way to set a binding property instead of using JAX-WS to set the property on the BindingProvider object. The CustomProperties binding is only supported for service clients.
Use the following commands in the PolicySetManagement group of the AdminTask object to customize your policy set configuration.
- Use the -attributes parameter for the getPolicyType and getBinding commands to view the properties for our policy and binding configuration. To get an attribute, pass the property name to the getPolicyType or getBinding command.
- Use the -attributes parameter for the setPolicyType and setBinding commands to add, update, or remove properties from your policy and binding configurations. To add or update an attribute, specify the property name and value. The setPolicyType and setBinding commands update the value if the attribute exists, or adds the attribute and value if the attribute does not exist. To remove an attribute, specify the value as an empty string (""). The -attributes parameter accepts a properties object.
If a property name or value supplied with the -attributes parameter is not valid, then the setPolicyType and setBinding commands fail with an exception. The property that is not valid is logged as an error or warning in the SystemOut.log file. However, the command exception might not contain the detailed information for the property that caused the exception. When the setPolicyType and setBinding commands fail, examine the SystemOut.log file for any error and warning messages that indicate that the input for the -attributes parameter contains one or multiple properties that are not valid.
IBM recommends using the High Performance Extensible Logging (HPEL) log and trace infrastructure . We view HPEL log and trace information using the logViewer .
The following setBinding example command demonstrates how we can use the CustomProperties binding to set a value for the WSADDRESSING_DESTINATION_EPR endpoint reference binding property:
AdminTask.setBinding('[-bindingLocation "" -bindingName generalCellWideBind1 -attachmentType client
-policyType CustomProperties -attributes "[[WSADDRESSING_DESTINATION_EPR addressValue]]"]')
Mixed-version environment: In a mixed cell environment, the following limitations apply to attachments to policy sets containing CustomProperties
policy:
- We must not create attachments to policy sets containing CustomProperties policy for applications deployed on an application server that is prior to WebSphere Application Server v8.0. The CustomProperties policy is only supported on WAS v8.0 and later.
- An application containing an attachment to a policy set containing CustomProperties policy must not be deployed on an application server that is prior to WAS v8.0.
- If an application that is deployed in a cluster environment contains an attachment to a policy set containing CustomProperties policy, we must not add a member application server that is prior to WAS v8.0 to the cluster.
mixv
Related: