Kbase P145019: Missing ESB Container and Service for the OpenEdge 10.2A Adapter for Sonic ESB installation when con
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/1/2009 |
|
Status: Verified
SYMPTOM(s):
Missing ESB Container and Service for the OpenEdge Adapter for Sonic ESB installation when connecting to Sonic 7.5 Domain Manager
The dev_OpenEdgeTest ESB Container and dev.OpenEdge Service are missing in Sonic Management Console (SMC)
The OpenEdge Native Services step contains no Service Type after dragging and dropping it into an ESB Process from within Workbench
The steps from the OESessionManaged template contain no Service Types after dragging and dropping it into an ESB Process from within Workbench
FACT(s) (Environment):
OpenEdge 10.2A
Sonic Workbench 7.5
Windows XP
CAUSE:
Bug # OE00174939
FIX:
Follow these steps for a possible solution:
- 1) Install Service Pack 2 for Sonic 7.5 (shutdown all Sonic processes first).
- 2) Start your Sonic Domain Manager.
- 3) Make sure that all properties of the %DLC%\install\tlr\installtlr.properties file are correct (except for the ones with "[[...]]" values).
- 4) Also make sure that the installMode property in the the %DLC%\install\tlr\installtlr.properties file has a value of 2.
- 5) Rename the esbadaptertlr.log located in %DLC%\install\tlr .
- 6) Make sure that all paths are correct in the %DLC%\sonicl\ESB7.5\config\offline.bat file.
- 7) Run the %DLC%\sonicl\ESB7.5\config\offline.bat batch file.
- 8) Verify that there are no error messages in the newly created esbadaptertlr.log file located in the %DLC%\install\tlr directory (if there are, then these need to be solved before continuing).
- 9) Install Service Pack 1 for OpenEdge 10.2A (while the Sonic Domain Manager is up and running).
- OR -
Manually configure the default OpenEdge ESB Container and Service:
- 1) Create an instance of the OpenEdge Native Services called dev.OpenEdge.
- 2) Create an ESB Container called dev_OpenEdgeTest.
- 3) Add the dev.OpenEdge Service to the dev_OpenEdgeTest ESB Container.
- 4) Under the Resources tab of the ESB Container (which is hosting your OpenEdge ESB Adapter instance) add the following jar files:
sonicfs:///System/OpenEdge/10.2A/esbadapter/lib/activation.jar
sonicfs:///System/OpenEdge/10.2A/esbadapter/lib/esbadptr.jar
sonicfs:///System/OpenEdge/10.2A/esbadapter/lib/mail.jar
sonicfs:///System/OpenEdge/10.2A/esbadapter/lib/regexp.jar
sonicfs:///System/OpenEdge/10.2A/esbadapter/lib/soap.jar
sonicfs:///System/OpenEdge/10.2A/esbadapter/lib/servlet.jar
Note: If they are not located in the SonicFS, then they can be imported from the %DLC%\esbadapter\lib directory.
- 5) Add the dev_OpenEdgeTest ESB Container to the dev_OpenEdgeTest MF Container.
- 6) In the Sonic Management Console (SMC), under the Configure tab, right-click on dev_OpenEdgeTest MF Container and select Properties. Under the Environment tab, set a new Java System Property called com.progress.openedge.home to the value of your OpenEdge install directory (e.g. C:\Progress).
Note: In cases where Sonic ESB and OpenEdge are on seperate machines:
- Copy the %DLC%\esbadapter directory into the <ESB_HOME> directory.
- Set the com.progress.openedge.home property to the <ESB_HOME> directory.
- 7) Restart the Sonic MF Container which is hosting your ESB Container.