webMethods and Intelligent Business Operations 10.2 | Administering Mediator | Mediator | WS-Addressing Processing in Mediator | Implementation of WS-Addressing in CentraSite
 
Implementation of WS-Addressing in CentraSite
CentraSite can import and virtualize WSDLs having WS-Addressing annotations. For the virtualized services, the annotations are kept in the WSDL because they do not contain relevant information about the native service endpoint.
The following WS-Addressing headers can be included in a WSDL:
*<wsam:UsingAddressing wsdl:required="true" />
*Explicit wsam:Action attributes for operation input/output elements. For example:
wsam:Action="http://greath.example.com/2004/wsdl/resSvc/opCheckAvailability"
*Default actions for inputs and outputs (for backwards compatibility with WSDL 1.1). The following pattern is used to construct a default action for inputs and outputs. The general form of an action Internationalized Resource Identifier (IRI) is as follows:
wsam:Action="[target namespace][delimiter][port type name][delimiter][input|output name]"
*Endpoint references, such as:
*<wsa10:EndpointReference>
*<wsa10:Address>[url]</wsa10:Address>
*</Identity>
*</wsa10:EndpointReference>
What happens to these WS-Addressing headers?
*For a native service (created through import WSDL), the WSDL remains as is.
*For a virtual service:
*The WS-Policy attachment block (containing the UsingAdressing element) is removed.
*The wsam:Action attributes remain on the operations.
*The endpoint references are removed because they are replaced by Mediator's endpoint information.

Copyright © 2015- 2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release