JAR files are loaded in the following
precedence order:
- JAR files placed in the integration server shared-classes directory
allow only a single defined integration server to access them. Files
placed in here are loaded first. No other integration servers can use
them.
Add the JAR files to the following directory:
Ensure that the broker name, and any integration servers created,
contain only characters that are valid on your file system. You may
also need to create the required directory structure.
All files
placed into the integration server shared-classes directory
that have a .jar extension, are loaded and made
available in the broker Java™ environment
for that integration server. JAR files in this directory take precedence
over JAR files in the broker shared-classes directory.
Note: If the integration server shared-classes directory
is empty when the integration server is deleted, the directory is automatically
removed.
- JAR files placed in the broker shared-classes directory
allow only a single defined broker to access them. Files placed in
here are loaded after any files placed in the integration server shared-classes directory.
No other broker can use them.
Add the JAR files to the
following directory:
Ensure that the broker name contains only characters that are
valid on your file system. You may also need to create the required
directory structure.
All files placed into the broker shared-classes directory
that have a .jar extension, are loaded and made
available in the broker Java environment
for that broker. JAR files in this directory take precedence over
JAR files in the top level shared-classes directory.
Note: If the broker shared-classes directory
is empty when the broker is deleted, the directory is automatically
removed.
- JAR files placed in the top level shared-classes directory
are made available to all brokers and all integration servers. Files
placed in here are loaded after any files placed in the broker shared-classes directory.
Add the JAR files to the following directory:
- For Windows
workpath\shared-classes
- For Linux, UNIX and z/OS
workpath/shared-classes
Note: On z/OS,
the workpath or component directory
is typically unique per broker, and therefore the top level shared-classes directory
is not shared with other brokers. In this case, there is no difference
between using the top level shared-classes directory
and using the broker shared-classes directory.