When possible, Adapter for Enterprise Javabeans takes full advantage of Integration Server's per-package class loading scheme. This feature enables you to install application server vendor jar files and deployed EJB jar files under WmEJBAdapter\code\jars. Installing the files to this location limits the visibility of the classes and resources in those jars to Adapter for Enterprise Javabeans and its dependents, thus reducing the potential for class loading collisions with other packages installed on Integration Server.

For some application servers, installing the files under WmEJBAdapter\code\jars may not be possible due to their own internal class loading requirements. In these cases, the third-party jars files must be installed on either the system classpath or the server's classpath.

If you put jar files in the lib\system directory on the Integration Server on which Adapter for Enterprise Javabeans is installed, that Integration Server cannot be managed by Optimize Infrastructure Data Collector due to class loading conflicts. For more information about Infrastructure Data Collector support in the adapter, see Optimize Infrastructure Data Collector Support for the Adapter.