DevTest Custom Jar Not Being Picked Up in /hotDeploy
Article ID: 112141
Updated On:
Products
CA Application Test
CA Continuous Application Insight (PathFinder)
Issue/Introduction
VSM is using one extra JAR. This jar is copied in the hotDeploy folder of the VSE server(Linux box).Still while depoying the VSM error is shown as JAR is missing.
Environment
Release: All supported DevTest releases
Component: ITKOVS
Resolution
Copied the jar file to the DEVTEST_HOME/lib/shared folder and restarted the VSE. \
As long as you can run your jar in the DEVTEST_HOME/lib/shared folder with no errors then this will be okay.
Running in hotDeploy is suggested for custom jars so as not to conflict with jars we deliver with DevTest, but not mandatory.
NOTE: Set system environment variable LISA_PRE_CLASSPATH to the DevTest/hotDeploy folder, this will pick up /hotDeploy before /lib/shared.
As long as you can run your jar in the DEVTEST_HOME/lib/shared folder with no errors then this will be okay.
Running in hotDeploy is suggested for custom jars so as not to conflict with jars we deliver with DevTest, but not mandatory.
NOTE: Set system environment variable LISA_PRE_CLASSPATH to the DevTest/hotDeploy folder, this will pick up /hotDeploy before /lib/shared.
Feedback
Yes
No
Powered by
