Manage the Java™ applications that are deployed to a broker.
A PAR file is given its own Java classloader, ensuring that the node classes are isolated from any other node classes.
For more details, see User-defined node class loading.
If a JavaCompute node specifies a JavaClassloader configurable service, you must define a configurable service with the name specified by the node on the broker. For more details, see JavaCompute node classloading using a configurable service.
ESQL Java routines and JavaCompute nodes that specify the same JavaClassLoader configurable service share one instance of the classloader. Therefore, the nodes and the routines use the same in-memory version of Java classes, and have access to the same static variables. The classloading mechanism for ESQL routines is the same as for JavaCompute nodes; for more details, see JavaCompute node classloading using a configurable service.