Details
-
Fix
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
2.7.1
-
None
Description
Current Situation
- With
JITL-742support for custom argument value resolvers was introduced. Deployment: Library classes should be packaged in a .jar file and the .jar file should be deployed to the <AGENT_HOME>/lib/user_lib directory
- Problem (Unix systems)
- Excerpt from agent.log:
... info com.sos.js7.job.resolver.JobArgumentValueResolverCache - [check custom resolvers dir][./user_lib][jar name pattern](?i)^jobapi-register-.*\.jar$ ... WARN com.sos.js7.job.resolver.JobArgumentValueResolverCache - [/var/sos-berlin.com/js7/agent/var_4445/./user_lib]java.nio.file.NoSuchFileException: ./user_lib- The Job API uses the environment variable JS7_AGENT_LIBDIR to locate this folder.
- This variable is only available when the agent runs on Windows, but not on Unix systems.
- As a result, the <AGENT_HOME>/lib/user_lib directory is not found on Unix.
- Excerpt from agent.log:
Desired Behaviour
- See JS7 - Job Environment Variables
- The Job API should use the JS7_AGENT_HOME variable to locate the user_lib directory, ensuring cross-platform compatibility.
Workaround on Unix
Set the environment variable JS7_AGENT_LIBDIR to point to <AGENT_HOME>/lib in the agent start script.
Test Instructions
- Configure and run any JITL-Job workflow.
- Check the agent.log and look for messages like (these messages are created only once when the first Job API job starts after the Agent starts):
... info com.sos.js7.job.resolver.JobArgumentValueResolverCache - start... ... info com.sos.js7.job.resolver.JobArgumentValueResolverCache - [cached][base64:]com.sos.js7.job.resolver.StandardBase64Resolver ... info com.sos.js7.job.resolver.JobArgumentValueResolverCache - [cached][enc:]com.sos.js7.job.resolver.StandardEncryptionResolver ... info com.sos.js7.job.resolver.JobArgumentValueResolverCache - [check custom resolvers dir][/opt/sos-berlin.com/js7/agent/lib/user_lib][jar name pattern](?i)^jobapi-register-.*\.jar$ ... info com.sos.js7.job.resolver.JobArgumentValueResolverCache - end
- The messages should not contain any warnings, and the absolute path to user_lib should be logged instead of a relative path like ./user_lib.
Attachments
Issue Links
- is related to
-
JITL-742 Support for custom argument value resolvers for JITL jobs
-
- Released
-