Status: Unverified
SYMPTOM(s):
OpenEdge Adapter for Sonic ESB does not get tailored when using Sonic ESB 7.x
The OpenEdge Adapter for Sonic ESB is not automatically configured
A Sonic ESB 7.x location is specified during the OpenEdge installation
When the ESB Adapter tries to initialize it throws the following exception(s):
ID=dev_ESBTest (severe) [ESBService] Error initializing service application OE-Service
ID=dev_ESBTest (severe) Trace follows...
java.lang.ClassNotFoundException: com.progress.esb.adapter.EsbAdapter
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at com.sonicsw.xqimpl.util.ExtClassLoader.findClass(Unknown Source)
com.progress.wsa.WsaSOAPEngineException: Missing required WsaSOAPEngine init parameter: Progress installation directory
at com.progress.wsa.ApacheSOAPEngine.initialize(ApacheSOAPEngine.java:341)
at com.progress.wsa.ApacheSOAPEngine.initialize(ApacheSOAPEngine.java:218)
at com.progress.esb.adapter.EsbAdapter.init(EsbAdapter.java:290)
FACT(s) (Environment):
OpenEdge 10.1A
OpenEdge 10.1B
Sonic ESB 7.x
All Supported Operating Systems
CAUSE:
Bug# OE00147898
FIX:
Upgrade to OpenEdge 10.1C or later.
- OR -
To workaround this issue, please configure the Sonic ESB Adapter manually.
1. Run seed.sh from $ESB_HOME/bin
2. Then follow these steps:
a. Go to $DLC/esbadapter/config.
b. Edit OpenEdgeSrvType.properties and replace value [[install_dir]] with the value of $DLC.
c. Edit OpenEdgeSrvType.xml and replace [[SONIC ESB]] with the value of $ESB_HOME
d. Import $DLC/esbadapter/config/OpenEdgeSrvType.properties to /System/SonicESB/7.5/properties/servicetypes using either SMC or esbadmin tool.
e. Import $DLC/esbadapter/config/OpenEdgeSrvType.xml using esbadmin tool by following these steps:
i. Run $ESB_HOME/bin/esbadmin.sh on UNIX and esbadmin.bat on windows.
ii. Execute 'connect Domain1 tcp://localhost:2506 <username> <password>' where localhost should be the name of the machine where Sonic is running and also make sure that you are using the correct port number. If security is enabled for your management Broker, then you also need to specify the username and password, otherwise they can be omitted.
iii. Execute 'import serviceType $DLC/esbadapter/config/OpenEdgeSrvType.xml' to create OpenEdge Services type.
3. Under the Resources tab of the ESB Container (which is hosting your OpenEdge ESB Adapter instance) add the following jar files:
$DLC/esbadapte/lib/esbadptr.jar
$DLC/esbadapte/lib/regexp.jar
$DLC/esbadapte/lib/soap.jar
$DLC/esbadapte/lib/servlet.jar
4. In the SMC, under the Configure tab, right-click on your Sonic MF Container which is hosting your ESB 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 separate machines:
- Copy the $DLC/esbadapter directory into the $ESB_HOME directory.
- Set the com.progress.openedge.home property to the $ESB_HOME directory.
5. Restart the Sonic MF Container which is hosting your ESB Container.