Kbase P144823: How to use a session-managed OpenEdge AppServer with the OpenEdge Sonic ESB Native Adapter ?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
09/06/2009 |
|
Status: Unverified
GOAL:
How to use a session-managed OpenEdge AppServer with the OpenEdge Sonic ESB Native Adapter ?
GOAL:
How to use the managed session model with the OpenEdge Sonic ESB Native Adapter ?
GOAL:
How to configure the OpenEdge Adapter for ESB when using the Native Invocation methodology with a session-managed OpenEdge AppServer ?
FACT(s) (Environment):
All Supported Operating Systems
Sonic ESB 7.x
OpenEdge 10.1C
OpenEdge 10.2x
FIX:
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.
So the basic steps to configure your ESB Process to connect to a session-managed AppServer are as follows:
- Generate an invocation file (.esboe) from your procedures for your ESB Native Adapter.
- In the Sonic Management Console (SMC) set the AppServer Operating Mode for the OpenEdge Native Services instance (e.g. dev.OpenEdge to State-aware, State-reset or Stateless).
- Inside Sonic Workbench create an ESB Process.
- Drag and drop the OESessionManaged template into your ESB Process.
- Drag and drop the OpenEdge Native Services between the Connect and Disconnect steps of the OESessionManaged template .
- Configure your OpenEdge Native Services step to use the invocation file (.esboe) and optionally also configure the Request/Response Mapping.
- Make sure that all OpenEdge Native Services steps (including the ones from the OESessionManaged template) are using the correct OpenEdge Native Services instance (e.g. dev.OpenEdge).
- Upload your ESB Process and deploy it into an ESB Container (or reload the ESB Container if already deployed).