The Native Invocation methodology of the OpenEdge Adapter for Sonic ESB depends on an invocation file for the easy integration of services in the Sonic ESB business process through itineraries. For ABL procedures and functions, this invocation file is the .esboe file. An .esboe file supplies the information necessary for Sonic to make a call to PAS for OpenEdge to execute a single ABL procedure. After it is 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 about 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 describes the options.

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 the source is saved to disk and when the project has Build Automatically selected
  • Automatically generated when Clean is selected for the project and when Build Automatically is selected
  • Automatically generated when the source is compiled
Text editor or a source code generator other than Progress Developer Studio for OpenEdge Run the ProxyGen utility using compiled source code.
Non-declarative (code not annotated) Any Run ProxyGen using compiled source code.