WS-Security binding for the generation of outbound request to a target.
You can configure the service integration bus for secure transmission of SOAP messages using tokens, keys, signatures and encryption in accordance with the Web Services Security (WS-Security) 1.0 specification.
You use WS-Security bindings to secure the SOAP messages that pass between service requesters (clients) and inbound services, and between outbound services and target Web services. Bindings provide the information that the run-time environment needs to implement the WS-Security configuration (for example "To sign the body, use this key"),
Bindings are administered independently from any Web service that uses them, so you can create a binding then apply it to many Web services.
You use a request generator with an outbound configuration. A request generator binding generates the requests from an outbound service to a target Web service.
Configuration properties for this object. These property values are preserved even if the run-time environment is stopped then restarted. Changing these property values typically has no effect until the run-time environment is restarted; for example, by stopping then restarting an application server. See the information center task descriptions for information about how to apply configuration changes to the run-time environment.
The name of the binding.
Required | Yes |
Data type | Text |
Specifies whether to use the default binding information. When this option is enabled, Web services security uses the default binding information instead of the custom binding information defined here.
Required | No |
Data type | Check box |
Specifies the namespace used by Web services security to send a request. However, this field configures the namespace value only and does not enforce the semantics of the specification related to the namespace. Web services security uses the processing semantic only in draft 13 of the OASIS specification.
Required | Yes |
Data type | Selection list |