Why does the EMS transport in Hawk Configuration get disabled, even though EMS is installed already?
Article ID: KB0091912
Updated On:
| Products | Versions |
|---|---|
| TIBCO Hawk | - |
| Not Applicable | - |
Description
Resolution:
It’s because the ems java library files are missing from the class path.
Please open windows registry, find HKEY_LOCAL_MACHINE\SOFTWARE\TIBCO Software\TIB/Hawk\4.8.x, make sure that Agent Classpath, Event Classpath, Display Classpath contains EMS java library file jms.jar, tibjms.jar, tibrvjms.jar, tibcrypt.jar and jaxp.jar, and then restart Hawk Configuration.
Please note that EMS 5.0 has the .jar files under $EMS_ROOT/5.0/lib. This is different from EMS 4.x or lower which have these .jar files in $EMS_ROOT/clients/java.
It’s because the ems java library files are missing from the class path.
Please open windows registry, find HKEY_LOCAL_MACHINE\SOFTWARE\TIBCO Software\TIB/Hawk\4.8.x, make sure that Agent Classpath, Event Classpath, Display Classpath contains EMS java library file jms.jar, tibjms.jar, tibrvjms.jar, tibcrypt.jar and jaxp.jar, and then restart Hawk Configuration.
Please note that EMS 5.0 has the .jar files under $EMS_ROOT/5.0/lib. This is different from EMS 4.x or lower which have these .jar files in $EMS_ROOT/clients/java.
Issue/Introduction
Why does the EMS transport in Hawk Configuration get disabled, even though EMS is installed already?
Feedback
Yes
No
Powered by
