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.
New feature: This product supports using CustomProperties
policy and binding to set generic properties that are not supported
in other policy types. The additional properties are set in the binding.
You 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 the JAX-WS programming
model to set the property on the BindingProvider object. The CustomProperties
binding is only supported for service clients.
newfeat
Use the following commands and parameters
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 your 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.
Note: 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.
New feature: This topic
references one or more of the application server log files. Beginning
in WebSphere Application Server Version 8.0 you can configure the
server to use the High Performance Extensible Logging (HPEL) log and
trace infrastructure instead of using
SystemOut.log ,
SystemErr.log,
trace.log,
and
activity.log files or native z/OS logging
facilities. If you are using HPEL, you can access all of your log
and trace information using the LogViewer command-line tool from your
server profile bin directory. See the information about using HPEL
to troubleshoot applications for more information on using HPEL.
newfeat
The following
setBinding example command demonstrates
how you 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]]"]')
newfeat Mixed-version environment: In a mixed cell environment,
the following limitations apply to attachments to policy sets containing
CustomProperties policy:
- You must not create attachments to policy sets containing CustomProperties
policy for applications that are deployed on an application server
that is prior to WebSphere® Application
Server Version 8. The CustomProperties policy is only supported on WebSphere Application Server
V8 and later.
- An application that contains an attachment to a policy set containing
CustomProperties policy must not be deployed on an application server
that is prior to WebSphere Application
Server Version 8.
- If an application that is deployed in a cluster environment contains
an attachment to a policy set containing CustomProperties policy,
you must not add a member application server that is prior to WebSphere Application Server
Version 8 to the cluster.
mixv