Try OpenEdge Now
skip to main content
Administration
Messaging and ESB Administration : Configuring and Managing the OpenEdge Adapter for Sonic ESB : Installation of the OpenEdge Adapter for Sonic ESB : Configuration
 
Configuration
Based on the type of installation identified, the following configuration takes place in your Sonic environment:
*Domain installation:
*Installs the default service instance, dev.OpenEdge, for the OpenEdge Adapter for ESB; this instance is configured to connect directly to the local esbbroker1 AppServer instance in your OpenEdge install
*Installs the property file for the OpenEdge Adapter for ESB
*Seeds the Directory Service for the Resource Editor
*Installs the OpenEdge .jar files for the OpenEdge Adapter for ESB into the Sonic Directory Service.
*Configures the Sonic Management Console
*Deployment installation:
*Performs all configuration tasks identified for a Domain install
*Creates a deployment container, named hostnameContainer, configured to run the OpenEdge Adapter for ESB and add it to the Management Framework (MF) container
*Development installation:
*Performs all configuration tasks identified for a Deployment install
*Configures the development container, dev_OpenEdgeTest, in the Sonic Workbench
When installation and configuration is complete, the Sonic Management Console has two OpenEdge services under ESB Configured Objects:
*OpenEdge Native Services — Supports the OpenEdge Adapter for ESB Native Invocation methodology
*OpenEdge Web Services — Supports the OpenEdge Adapter for ESB SOAP-based Web Service methodology