Use this option to work with WS-Security bindings
that comply with the Web Services Security (WS-Security) 1.0
specification.
You get, from the owning parties, the WS-Security bindings for the client (in the case of an inbound service) and the target Web service (in the case of an outbound service).
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. WS-Security 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"),
You receive this security binding information direct from the service requester or target service provider, in the form of an ibm-webservicesclient-bnd.xmi file for the client, and an ibm-webservices-bnd.xmi file for the target Web service. You extract the information from these .xmi files, then manually enter it into the WS-Security bindings forms.
WebSphere Application Server also includes a set of default WS-Security binding objects. However if you are using either of the single server products WebSphere Application Server or WebSphere Application Server Express, then these default bindings are configured within the application server (under the administrative console option
server_name [Configuration tab, Security section] ) and are not available for use with service integration technologies-enabled Web services.From the administrative console, you can complete the following service integration tasks for WS-Security bindings: