Jar files

The IBM® Toolbox for Java™ is shipped as a set of jar files. Each jar file contains Java packages that provide specific functions. You can reduce the amount of required storage space by using only the jar files required to enable the specific functions that you want.

To use a jar file, make sure that you include an entry for it in your CLASSPATH.

The following chart indicates which jar files you must add to your CLASSPATH to use the associated function or package.

IBM Toolbox for Java package or function Jar files required to be in your CLASSPATH
Access classes jt400.jar (client) or jt400Native.jar (server) Note 1, or jt400Proxy.jar in a proxy environment
CommandHelpRetriever class jt400.jar (client) or jt400Native.jar (server) Note 1 and an XML parser and XSLT processor Note 2
CommandPrompter Note 3 jt400.jar, jui400.jar, util400.jar Note 4, and an XML parser Note 2
Commtrace classes jt400.jar (client) or jt400Native.jar (server) Note 1
HTML classes jt400.jar Note 1 plus jt400Servlet.jar (client), or jt400Native.jar (server) Note 1
HTMLDocument class The same jars required for HTML classes, plus an XML parser and XSLT processor Note 2
JCA classes jt400.jar (client) or jt400Native.jar (server) Note 1
JDBC Data Source GUI jt400.jar (client) Note 1 and jui400.jarNote 5
NLS system and error messages jt400Mri_lang_cntry.jar Note 6
PCML (development and run-time, parsed) Note 7 jt400.jar (client) or jt400Native.jar (server) Note 1, Note 8, and an XML parser Note 2
PCML (run-time, serialized) jt400.jar (client) or jt400Native.jar (server) Note 1, Note 8
PDML (development) Note 3 uitools.jar, jui400.jar, util400.jar Note 4, and an XML parser Note 2
PDML (run-time, parsed) Note 3 jui400.jar, util400.jar Note 4, and an XML parser Note 2
PDML (run-time, serialized) Note 3 jui400.jar, and util400.jar Note 4
ReportWriter classes jt400.jar (client) or jt400Native.jar (server) Note 1, reportwriter jars Note 9, and an XML parser and XSLT processor Note 2
Resource classes jt400.jar (client) or jt400Native.jar (server) Note 1
RFML jt400.jar (client) or jt400Native.jar (server) Note 1, and an XML parser Note 2
Security classes jt400.jar (client) or jt400Native.jar (server) Note 1, or jt400Proxy.jar in a proxy environment
Servlet classes jt400.jar Note 1 plus jt400Servlet.jar (client), or jt400Native.jar (server) Note 1
iSeries™ System Debugger Note 3 jt400.jar (client) Note 1 and tes.jar
ToolboxME for iSeries jt400Micro.jar (client) Note 10 and jt400.jar (server) or jt400Native.jar (server)Note 1
Vaccess classes jt400.jar (client) Note 1
XPCML jt400.jar (client) or jt400Native.jar (server) Note 1, and an XML parser and XSLT processor Note 2

Note 1: Some of the IBM Toolbox for Java classes are in more than one jar file:

Note 2: When you must use an XML parser or XSLT processor, make sure that they are JAXP-compliant. For more information, see the following page:

XML parser and XSLT processor

Note 3: Using CommandPrompter, PDML, or the iSeries System Debugger also requires one additional jar file that is not part of IBM Toolbox for Java: jhall.jar. For more information about downloading jhall.jar, see the Sun JavaHelp(TM) Web site Link outside Information Center.

Note 4: util400.jar contains iSeries-specific classes for formatting input and for using the command line prompter. Using the CommandPrompter class requires util400.jar. Using PDML does not require util400.jar, but it is useful.

Note 5: jui400.jar contains the classes necessary to use the JDBC DataSource GUI interface. jt400.jar ( Note 1) contains the classes necessary for all other JDBC functions.

Note 6: jt400Mri_xx_yy.jar contains translated messages, including strings contained in exception messages, dialogs, and output from other normal processing. In jt400Mri_lang_cntry.jar, lang = the ISO Language Code and cntry = the ISO Country or Region Code used to translate the contained text. In some cases, the ISO Country or Region Code is not used. Installing a particular national language version of the IBM Toolbox for Java licensed program on the iSeries installs the appropriate jt400Mri_lang_cntry.jar file. If the language is not supported, the install defaults to the English version, which is included in the IBM Toolbox for Java jar files.

You can add support for other languages by adding more than one of these jar files to the classpath. Java loads the correct string based on the current locale.

Note 7: Serializing your PCML file during development has two benefits:

  1. You need to parse the PCML file only during development and not during run-time
  2. Users need fewer jar files in their CLASSPATH to run the application

To parse the PCML file during development, you need both the PCML run-time in data.jar or jt400.jar and the PCML parser in x4j400.jar. To run the serialized application , users need only jt400.jar. For more information see Building iSeries program calls with PCML.

Note 8: Use jt400.jar and jt400Native.jar instead of data400.jar. data400.jar contains the PCML runtime classes, which are now also in jt400.jar and jt400Native.jar (Note 1). data400.jar is shipped to retain compatibility with previous releases of IBM Toolbox for Java.

Note 9: Copies of the ReportWriter classes are in more than one jar file:

If your application streams PCL data to an iSeries spooled file, you must make the access classes available by using the appropriate jar file ( Note 1). Creating a spooled file to hold PCL data requires the AS400, OutputQueue, PrintParameterList, and SpooledFileOutputStream classes. For more information, see the ReportWriter classes.

Note 10: jt400Micro.jar does not contain the classes needed to run MEServer, which reside in both jt400.jar and jt400Native.jar (Note 1). jt400Micro.jar is available only from the IBM Toolbox for Java and JTOpen Web site Link outside Information Center.

Parent topic: Installing IBM Toolbox for Java on your workstation