TIBCO EMS 8.4 support
Article ID: 112702
Updated On:
Products
CA Application Performance Management Agent (APM / Wily / Introscope)
INTROSCOPE
Issue/Introduction
TIBCO EMS Standalone agent failed to start with TIBCO EMS 8.4
TIBCO EMS Standalone agent failed to start with TIBCO EMS 8.4 In the IntroscopeAgent.log the below messages are reported:
[WARN] [com.wily.soaextension.tibcoems.agent.TibcoEMSMonitor] slf4j-simple-1.4.2.jar is present in agent classpath but does not exist.
[WARN] [com.wily.soaextension.tibcoems.agent.TibcoEMSMonitor] slf4j-api-1.4.2.jar is present in agent classpath but does not exist.
[WARN] [com.wily.soaextension.tibcoems.agent.TibcoEMSMonitor] tibcrypt.jar is present in agent classpath but does not exist.
[ERROR] [com.wily.soaextension.tibcoems.agent.TibcoEMSMonitor] Some mandatory jar files are missing from agent classpath, ending agent application.
TIBCO EMS Standalone agent failed to start with TIBCO EMS 8.4 In the IntroscopeAgent.log the below messages are reported:
[WARN] [com.wily.soaextension.tibcoems.agent.TibcoEMSMonitor] slf4j-simple-1.4.2.jar is present in agent classpath but does not exist.
[WARN] [com.wily.soaextension.tibcoems.agent.TibcoEMSMonitor] slf4j-api-1.4.2.jar is present in agent classpath but does not exist.
[WARN] [com.wily.soaextension.tibcoems.agent.TibcoEMSMonitor] tibcrypt.jar is present in agent classpath but does not exist.
[ERROR] [com.wily.soaextension.tibcoems.agent.TibcoEMSMonitor] Some mandatory jar files are missing from agent classpath, ending agent application.
Environment
TIBCO EMS 8.4
APM 10.7
APM 10.7
Resolution
Tibco stopped shipping tibcrypt.jar, slf4j-api-1.5.2.jar, & slf4j-simple-1.5.2.jar jars from TIBCO EMS 8.4 version . These are mandatory jar files for EMS standalone agent.
To resolve this issue , Copy “tibcrypt.jar, slf4j-api-1.5.2.jar, & slf4j-simple-1.5.2.jar “ from EMS 8.3 or “tibcrypt.jar, slf4j-api-1.4.2.jar, & slf4j-simple-1.4.2.jar” from older versions like TIBCO 6.1 to EMS agent folder & update PATH in Agent startup scripts.
Here is an example:
Navigate to <EMS Agent home>>/EMSMonitor.sh/bat
Update copied jars files path in below section & restart the Agent
Jar files required for SSL Connection.
export TIB_CRYPT_JAR=lib/tibcrypt.jar
export TIB_SLF4J_API_JAR=lib/slf4j-api-1.4.2.jar
export TIB_SLF4J_SIMPLE_JAR=lib/slf4j-simple-1.4.2.jar
Note: Above jar files are required only for SSL connection , if you want to connect EMS without SSL , then comment above 3 properties & remove ‘TIB_CRYPT_JAR, TIB_SLF4J_API_JAR, TIB_SLF4J_SIMPLE_JAR’ values from export CLASSPATH property in EMSMonitor.sh/bat file
To resolve this issue , Copy “tibcrypt.jar, slf4j-api-1.5.2.jar, & slf4j-simple-1.5.2.jar “ from EMS 8.3 or “tibcrypt.jar, slf4j-api-1.4.2.jar, & slf4j-simple-1.4.2.jar” from older versions like TIBCO 6.1 to EMS agent folder & update PATH in Agent startup scripts.
Here is an example:
Navigate to <EMS Agent home>>/EMSMonitor.sh/bat
Update copied jars files path in below section & restart the Agent
Jar files required for SSL Connection.
export TIB_CRYPT_JAR=lib/tibcrypt.jar
export TIB_SLF4J_API_JAR=lib/slf4j-api-1.4.2.jar
export TIB_SLF4J_SIMPLE_JAR=lib/slf4j-simple-1.4.2.jar
Note: Above jar files are required only for SSL connection , if you want to connect EMS without SSL , then comment above 3 properties & remove ‘TIB_CRYPT_JAR, TIB_SLF4J_API_JAR, TIB_SLF4J_SIMPLE_JAR’ values from export CLASSPATH property in EMSMonitor.sh/bat file
Additional Information
This is a workaround to allow APM to work with TIBCO EMS 8.4
Feedback
Yes
No
Powered by
