WSAddressing policy and binding properties
Use the -attributes parameter for the setPolicyType and setBinding commands to specify additional configuration information for the WSAddressing policy and policy set binding. Application and system policy sets use the WSAddressing policy and binding.
WSAddressing is an interoperability standard for addressing Web services and providing addressing information in messages. For more information, see the W3C Candidate Recommendation (CR) versions of the WS-Addressing core and SOAP specifications.
- 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.

To support a mixed-cell environment, WebSphere Application Server supports Version 7.0 and Version 6.1 bindings. General cell-level bindings are specific to Version 7.0 and later Application-specific bindings remain at the version that the application requires. When the user creates an application-specific binding, the application server determines the required binding version to use for application.
WSAddressing policy properties
- usingAddressing
- Specifies whether a WS-Addressing SOAP header is included on messages.
Use one of the following values:
- required
- WS-Addressing is mandatory. Servers return an error if they receive a message that does not contain a WS-Addressing header. Clients always include WS-Addressing headers in SOAP messages.
- optional
- WS-Addressing is not mandatory. Servers do not generate an error if they receive a message that does not contain a WS-Addressing header. Clients might not include WS-Addressing headers in SOAP messages, for example, if WS-Policy is enabled and the server does not specify that WS-Addressing is mandatory.
- wsaMode
- Specifies the messaging style that this policy set supports. Use
one of the following values:
- WSA_SYNC
- Response messages must be targeted at the WS-Addressing anonymous URI.
- WSA_ASYNC
- Response messages must not be targeted at the WS-Addressing anonymous URI.
- WSA_BOTH
- The targeting of response messages is not restricted.
AdminTask.setPolicyType('[-policySet "myPolicySet" -policyType WSAddressing
-attributes "[[usingaddressing required][wsaMode WSA_SYNC]]"]')
WSAddressing binding properties
- preventWLM
- Specifies whether to prevent workload management for references to endpoints that were created by the application programming interface (API) in a cluster environment. Messages that target Endpoint References (EPRs) within a cluster environment are workload managed by default.
- Preventing workload management routes messages that target EPRs
to the node or server on which the EPR was created. You might disable
workload management if the endpoint maintains the in-memory state,
which has not been replicated across other nodes or servers within
the cluster.For example, the following command prevents workload management for a cell-wide general binding, from the WSAddressing policy.
AdminTask.setBinding('[-bindingLocation "" -bindingName cellWideBinding2 -policyType WSAddressing -attributes "[preventWLM true]"]')