Try OpenEdge Now
skip to main content
Messaging and ESB
Guidelines for Using and Programming for the OpenEdge Adapter for Sonic ESB : Web Services Invocation methodology : Differences between the Web Services Invocation methodology in the OpenEdge Adapter for Sonic ESB and the WSA : WSM and WSD file usage
 
WSM and WSD file usage
When you install a Web Services Invocation OpenEdge service in Sonic ESB, you specify one of the following two files as the service definition:
*The WSM file — Created by Proxy Generator from the compiled r-code for an AppServer application
*The WSD file — Exported from an existing Web service
Sonic ESB stores a copy of the specified service definition file as a resource. The file retains its original name. The OpenEdge Adapter for Sonic ESB relies on the stored WSM or WSD file for the information needed to code and decode client SOAP messages and to access the appropriate service to execute requests.
When you deploy a Web service to a WSA instance, in contrast, the WSA stores the service definition as a copy of the original WSM or WSD file with the name FriendlyName.wsad. The WSA relies on this WSAD file for the necessary information about SOAP processing and service identification.
WSAD files do not exist in Sonic ESB.