ESB Process and session-managed OpenEdge Application Servers
- Last Updated: March 30, 2020
- 1 minute read
- OpenEdge
- Version 12.2
- Documentation
Your .esboe files do not contain
information about your OpenEdge Application Server operating mode. OpenEdge installs
process templates into your Sonic Directory Service for you to include in
your process if you need a session-managed connection. The process template, OESessionManaged,
adds two invocation files to your process: Connect to
Session-Managed AppServer and Disconnect
from Session-Managed AppServer. By default, the connection
is made to the default dev.OpenEdge service in
the dev_OpenEdgeTest container. You can change
the service properties of your dev.OpenEdge service
in your Sonic Management Console, or you can create a new service
for your session-managed OpenEdge Application Server. If you create
a new service, you must re-configure all your invocation files in
your process to connect to your new service in your Sonic Workbench
process editor.
Best practices for process design dictates that a session-managed session should not span more than a single process. Alter your process design to use sub-processes if you require multiple session-managed OpenEdge Application Servers.
The following figure shows the OESessionManaged template in Sonic Workbench.
