Try OpenEdge Now
skip to main content
Messaging and ESB Administration : Configuring and Managing the OpenEdge Adapter for Sonic ESB : Using the OpenEdge Adapter for Sonic ESB : Editing OpenEdge service properties
Editing OpenEdge service properties
Default values for the properties of an OpenEdge service are stored in a Sonic ESB resource that is loaded from one of the following files:
*ESBOE file — The invocation file associated with the Native Invocation Methodology. Create ESBOE files while you are developing your ABL application by including source code annotations and generating the ESBOE file with Progress Developer Studio for OpenEdge or the ESBOEGEN utility. Or you generate the ESBOE files after your development is complete by using ProxyGen.
*WSM file — Is a Web Services Mapping (WSM) file, associated with the Web Service Invocation methodology. Use ProxyGen after developing your ABL application, to create a WSM file.
*WSD file — Is a Web Service Definition (WSD) file. Use a WSD file if you intend to deploy an existing WSA-based Web service in Sonic ESB. You can export the service definition from OpenEdge Management or OpenEdge Explorer and use the resulting Web Service Definition (WSD) file instead of a WSM file. By doing so, you preserve the defined properties of the service and avoid the need to modify them again.
Note: For more information on ProxyGen, see OpenEdge Development: Open Client Introduction and Programming.
If you want to change the defaults, follow the instructions provided in the following sections:
*Adding the WSM or WSD resource to the Sonic ESB Directory Service
*Generating a WSDL file from the OpenEdge Resource Editor
For any specific service instance, you can override some of the defaults stored in the file by editing the desired values in the SMC. You can specify these service-specific values when you create the service instance, and you can edit them after the instance has been defined (see Creating an OpenEdge service instance). In cases where no value is explicitly defined for a service, the default value is in effect.
By overriding the defaults with service-specific values, you can use the same WSM or WSD resource as the basis for multiple services that differ only with respect to a few details. For example, you might want to create two or more services that provide the same functionality but use the facilities of different AppServers.
Note: Editing the service properties in the SMC does not affect any values stored in the WSM or WSD resource. Conversely, editing the resource does not affect any overrides that were entered for the service instance.
* Adding the WSM or WSD resource to the Sonic ESB Directory Service
* Editing the default service properties