Try OpenEdge Now
skip to main content
Application and Integration Services
OpenEdge Messaging and ESB : OpenEdge Adapter for Sonic ESB : Native Invocation methodology : .esboe files
.esboe files
The Native Invocation methodology of the OpenEdge Adapter for Sonic ESB, depends on an invocation file for the easy integration of services in Sonic ESB business process via itineraries. For ABL procedures and functions, this invocation file is the .esboe file. A .esboe file supplies the information necessary for Sonic to make a call to an OpenEdge Application Server to execute a single ABL procedure. Once created, the .esboe file can be dropped onto the canvas of the Sonic ESB Process Editor in Sonic Workbench to create a new step in an ESB process. For more information on generating an ESB process, see your Sonic documentation.
Creation of the invocation file depends on the developer’s choice of a declarative or non-declarative approach to development. The following table details the options.
Table 2. Generating .esboe files
Source code development approach (declarative/ non-declarative)
Source code development tool
.esboe file generation
Declarative (annotated code)
Progress Developer Studio for OpenEdge
*Automatically generated when source is saved to disk, when the project has Build Automatically selected
*Automatically generated when Clean is selected for the project, and Build Automatically is selected
*Automatically generated when the source is compiled
Text editor, or other source code generator other than Progress Developer Studio for OpenEdge
Run the ESBOEGEN utility using compiled source code.
Non-declarative (code not annotated)
Run ProxyGen using compiled source code.
For details on using creating .esboe files, see the OpenEdge Development: Messaging and ESB guide.