The Sonic Native Invocation client type generates a script file (.esboe file) for each specified procedure or function that can be imported directly into Sonic Workbench for deployment to a Sonic ESB container. When a Sonic ESB process is created using the Sonic Native Invocation methodology, ABL procedures are called directly through an OpenAPI call to an OpenEdge AppServer. For more information on the Sonic Native Invocation methodology, see OpenEdge Development: Messaging and ESB.
Note: You can also change the deployment settings for this client type during deployment to a Sonic ESB container.
Client Details for the Sonic Native Invocation client type displays the following generation settings:
Invocation File Deployment Options — The following settings to generate the .esboe files for deployment:
Save to Output Directory — Specify this option to have your .esboe files written to the directory specified in the Output Directory field described in the General settings for proxy generation.
Deploy to Directory Service — Specify this option to have your .esboe files written to your Sonic Directory Service. If specified, you must also specify the absolute path of your Sonic Directory Service in Resource Dir. For more information on Sonic Directory Services, see your Sonic documentation.
Overwrite Files — If you specified Deploy to Directory Service, select Overwrite Files to replace any existing files in your Sonic Directory Service.
Create Deployment Archive — Specify this option to have your .esboe files written into a deployment archive. If specified, you must also specify an archive (.xar) file in Archive Name.
Advanced — Click this button to access the Advanced Sonic ESB Options dialog box, which allows you to specify settings for the Sonic Domain Manager where the .esboe files are to be deployed. For a detailed description, see Advanced Sonic ESB Options dialog box.
Invocation File Deployment Options — The following settings to generate the .esboe files for deployment: