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 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.
Note: This topic references one or more of the application server log files. As a
recommended alternative, 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 on distributed and IBM®
i systems. You can also use HPEL in conjunction with your 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.
For transitioning users: In WebSphere Application
Server Version 7.0 and later, the security model was enhanced to a domain-centric security model
instead of a server-based security model. The configuration of the default global security (cell)
level and default server level bindings has also changed in this version of the product. In the
WebSphere Application Server Version 6.1 Feature Pack for Web Services, you can configure one set of
default bindings for the cell and optionally configure one set of default bindings for each server.
In Version 7.0 and later, you can configure one or more general service provider bindings and one or
more general service client bindings. After you have configured general bindings, you can specify
which of these bindings is the global default binding. You can also optionally specify general
binding that are used as the default for an application server or a security domain.
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
Configure the WSAddressing policy by specifying the following properties with the setPolicyType command:
- 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.
The following example uses the setPolicyType command to set WS-Addressing to mandatory, and the
messaging style to synchronous, for the policy set
myPolicySet:.
AdminTask.setPolicyType('[-policySet "myPolicySet" -policyType WSAddressing
-attributes "[[usingaddressing required][wsaMode WSA_SYNC]]"]')
WSAddressing binding properties
Configure
the WSAddressing policy by specifying the following property with
the setBinding command:
- 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]"]')