Using a Package Class Loader
By default, when a service in a package needs to load a class into storage, the package's class loader defers the search for the class to its parent class loader, which is always the Integration Server class loader. However, there may be times when you want Integration Server to use the package's class loader instead. For example, you might want to use a newer version of a class that exists in the package directory, rather than the version the Integration Server class loader will access.
For the package class loader to have access to class you want to load, the jar files containing the class you want load must exist in this directory:
Integration Server_directory \instances\instance_name\packages\packageName\code\jars directory.
To configure
Integration Server to use a package class loader
1. Navigate to the Integration Server_directory \instances\instance_name\packages\packageName directory, where packageName is the name of the package that has the jar files that you want to load.
2. Add the following property to the manifest.v3 file:
<value name='classloader'>package</value>
3. Reload the package.
For more information about how
Integration Server loads classes, refer to
Class Loading in Integration Server