In some cases, Integration Server will receive a request to load a class, but is not given any information about where the class lives.

In this case, steps 1-6 are the same as in Scenario One, but because Integration Server does not know which package contains the class, it cannot go directly to the class loader for a particular package. Instead, Integration Server will start looking through all packages in the Integration Server_directory \instances\instance_name\packages directory. If you know which packages are most likely to contain the classes being searched for, you can reduce the number of packages searched by specifying the order in which Integration Server is to search packages. You control the search order by using the watt.server.classloader.pkgpriority server configuration parameter. For example, you could specify the following:

watt.server.classloader.pkgpriority=PackageD,PackageF

With this setting, Integration Server will search PackageD and PackageF for the class before searching in PackageA, PackageB, and PackageC.