How to make the Hawk agent work with EMS 5.0?
Article ID: KB0087224
Updated On:
| Products | Versions |
|---|---|
| TIBCO Hawk | - |
| Not Applicable | - |
Description
Resolution:
After EMS 5.0, there is a little change for the folder structure. Previously, the client jar files is under <ems>/clients/java. After EMS 5.0, it’s <ems>/lib.
Since Hawk is using the previous EMS folder as the default folder to search the EMS client jar file, there is some thing we can do to make hawk work with EMS 5.0.
1. Even you installed the EMS 5.0; you can still install the EMS client component bundled in the Hawk suite. This is the easiest way to make the hawkagent work with EMS 5.0. You don’t need to change any thing and there is no conflict will caused by that.
2. If you really don’t want to install the EMS client component bundled in Hawk suite, here is the changes you need to do:
A: on Windows system, you need to add the EMS java library file jms.jar, tibjms.jar, tibrvjms.jar, tibcrypt.jar and jaxp.jar to keys: Agent Classpath, Event Classpath and Display Classpath in registry: HKEY_LOCAL_MACHINE\SOFTWARE\TIBCO Software\TIB/Hawk\4.x.x.
B: on UNIX/LINUX machine, you need to change the script files: startagent, startdisplay and startevent under <hawk>/bin as following:
Set the EMS_ROOT to the EMS 5.0 installation folder.
Replace the following lines in the scripts file:
JARFILE="$JARFILE:$EMS_ROOT/clients/java/jms.jar"
JARFILE="$JARFILE:$EMS_ROOT/clients/java/tibjms.jar"
JARFILE="$JARFILE:$EMS_ROOT/clients/java/tibrvjms.jar"
JARFILE="$JARFILE:$EMS_ROOT/clients/java/tibcrypt.jar"
To:
JARFILE="$JARFILE:$EMS_ROOT/lib/jms.jar"
JARFILE="$JARFILE:$EMS_ROOT/lib/tibjms.jar"
JARFILE="$JARFILE:$EMS_ROOT/lib/tibrvjms.jar"
JARFILE="$JARFILE:$EMS_ROOT/lib/tibcrypt.jar"
Leave along the following line:
JARFILE="$JARFILE:$EMS_ROOT/clients/java/jaxp.jar"
Since there is no such jar file after EMS 5.0.
After EMS 5.0, there is a little change for the folder structure. Previously, the client jar files is under <ems>/clients/java. After EMS 5.0, it’s <ems>/lib.
Since Hawk is using the previous EMS folder as the default folder to search the EMS client jar file, there is some thing we can do to make hawk work with EMS 5.0.
1. Even you installed the EMS 5.0; you can still install the EMS client component bundled in the Hawk suite. This is the easiest way to make the hawkagent work with EMS 5.0. You don’t need to change any thing and there is no conflict will caused by that.
2. If you really don’t want to install the EMS client component bundled in Hawk suite, here is the changes you need to do:
A: on Windows system, you need to add the EMS java library file jms.jar, tibjms.jar, tibrvjms.jar, tibcrypt.jar and jaxp.jar to keys: Agent Classpath, Event Classpath and Display Classpath in registry: HKEY_LOCAL_MACHINE\SOFTWARE\TIBCO Software\TIB/Hawk\4.x.x.
B: on UNIX/LINUX machine, you need to change the script files: startagent, startdisplay and startevent under <hawk>/bin as following:
Set the EMS_ROOT to the EMS 5.0 installation folder.
Replace the following lines in the scripts file:
JARFILE="$JARFILE:$EMS_ROOT/clients/java/jms.jar"
JARFILE="$JARFILE:$EMS_ROOT/clients/java/tibjms.jar"
JARFILE="$JARFILE:$EMS_ROOT/clients/java/tibrvjms.jar"
JARFILE="$JARFILE:$EMS_ROOT/clients/java/tibcrypt.jar"
To:
JARFILE="$JARFILE:$EMS_ROOT/lib/jms.jar"
JARFILE="$JARFILE:$EMS_ROOT/lib/tibjms.jar"
JARFILE="$JARFILE:$EMS_ROOT/lib/tibrvjms.jar"
JARFILE="$JARFILE:$EMS_ROOT/lib/tibcrypt.jar"
Leave along the following line:
JARFILE="$JARFILE:$EMS_ROOT/clients/java/jaxp.jar"
Since there is no such jar file after EMS 5.0.
Issue/Introduction
How to make the Hawk agent work with EMS 5.0?
Feedback
Yes
No
Powered by
