If you use third-party or custom Java packages in the Java transformation, you must configure the classpath. The Secure Agent includes the classes and resource files within the classpath when it compiles the Java code. You do not need to configure the classpath if you use only built-in Java packages.
For example, you import the Java package
in the Java transformation and define the package in converter.jar. You must add converter.jar to the classpath before you compile the Java code. However, if you import the package java.io, you do not need to set the classpath because java.io is a built-in Java package.
Set the classpath to each JAR file or class file directory associated with the Java package. Separate multiple classpath entries with a semicolon (
) on Windows or a colon (
) on UNIX. The JAR or class files must be accessible by the Secure Agent.
If you use the Java transformation in an
, the files must be stored in the following directory on the Secure Agent machine:
<Secure Agent installation directory>/ext/ctjars
Additionally, consider the following guidelines for
If the Secure Agent machine stops unexpectedly and the agent restarts on a different machine, you must add the JAR or class files to the same directory on the new machine.
If you update the JAR or class files on the Secure Agent machine, the files take effect the next time you run a job on the
To prevent long-running jobs from failing, do not update the files on the Secure Agent machine more than four times while you have jobs running.
If you use a serverless runtime environment, the files must be stored in the supplementary file location. If you update the files, you must redeploy the serverless runtime environment for the changes to take effect. For more information about the location, see