Details
-
Feature
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
2.7.4
-
None
Description
Current Situation
The classpath in the agent.sh|.cmd Agent Start Script does not support to add paths dynamically for user Java libraries. Instead, user Java libraries have to be provided directly in the ./lib/user_lib folder without sub-folders. Any changes made to the Agent Start Script will be overriden by later updates to the software.
Desired Behavior
Users should be able to add paths to user Java libraries dynamically to the Agent's classpath.
- A new environment variable JS7_AGENT_CLASSPATH_USER is introduced that holds the paths to user Java libraries. Users can specify the environment variable in their agent_<port>.sh|.cmd Agent Instance Start Script.
- The Agent Start Script will consider the environment variable when added to he Instance Start Script:
- Unix: The colon ':' is used to separate paths. Users specify .jar files or a directories using *.
JS7_AGENT_CLASSPATH_USER=/home/sos/agent/lib/user_lib/project1/*:/home/sos/agent/lib/user_lib/project2/*:/home/sos/agent/lib/user_lib/project3/my_jobs.jar
- Unix: The colon ':' is used to separate paths. Users specify .jar files or a directories using *.
-
- Windows: The semicolon ';' is used to separate paths. Users specify .jar files or directories using *.
set JS7_AGENT_CLASSPATH_USER=C:/Program Files/sos-berlin.com/js7/agent/lib/user_lib/project1/*;C:/Program Files/sos-berlin.com/js7/agent/lib/user_lib/project2/*;C:/Program Files/sos-berlin.com/js7/agent/lib/user_lib/project3/my_jobs.jar
- Windows: The semicolon ';' is used to separate paths. Users specify .jar files or directories using *.
Maintainer Notes
- A patch is available
- Extract above archive to $AGENT_HOME/bin