JavaClassLoader configurable service

Select the objects and properties that you want to change for the JavaClassLoader configurable service.

For JavaClassLoader configurable services, you must stop and start the integration server for a change of property value to take effect.

Supplied configurable services that are created for each integration node Properties for each configurable service that is defined Description of properties

None

includedDeployedJars

 The JAR files that are loaded by the classloader. The JAR files must have been deployed to the integration server.
Specify one of the following values:
  • none if no deployed JAR files are to be loaded.
  • automatic if only the JAR file that contains the class that implements a JavaCompute node is to be loaded. This value is not valid for ESQL, and results in a runtime error.
  • a semicolon separated list of JAR file names that are to be loaded. The JAR file names must end with .jar. No wildcard characters are supported.

    You can include automatic in the list to also load the JAR file that contains the class required by a JavaCompute node. Including automatic results in a runtime error, if the configurable service was specified in an ESQL routine.

The default value is automatic.

Java™ classes in the JAR files in includedDeployedJars are searched and loaded before classes in the JAR files in the sharedJarPath.

Note: Inside applications or shared libraries that have Java isolation enabled, you can use a JavaClassLoader configurable service only if the includedDeployedJars property is set to none. Deployed JAR files inside applications or shared libraries with Java isolation enabled are not visible to JavaClassLoader configurable services. For more information, see Java isolation.

sharedJarPath

 The fully qualified file path of a single additional directory to be searched by the classloader. The directory must not be in the integration node file path or work path, as defined by the MQSI_FILEPATH and MQSI_WORKPATH environment variables.

If the directory is specified, it is used to resolve additional classes.

If the directory is not specified, the integration node shared-classes directories are used to resolve additional classes.

Java classes in the JAR files in includedDeployedJars are searched and loaded before classes in the JAR files in the sharedJarPath.