When you export and deploy an applet or application built with VisualAge for Java, you also need to deploy the runtime for the features with which you created the code, if any, and put the deployed runtime Jar or Zip on your class path.
In general, the Jar files are compressed and are for use when running applets off of a server. The Zips are uncompressed and should be placed on the CLASSPATH of the deployment machine for running applications locally.
Depending on which features you have installed, and which edition of VisualAge for Java you have, the following runtime libraries are provided in the IBMVJava/eab/runtime30 or runtime20 directory of your install image. (This may not be a complete list.) Also, you can find these runtimes in the extras/runtime30 or runtime20 directory on the product CD.
Feature (E)=Enterprise Edition only | Workspace Project Name | Runtime name (one of each .jar and .zip unless otherwise specified) | Supported Runtime Platforms |
Data Access Builder (E) | IBM Enterprise Data Access Libraries | ivjdab30 | ![]() ![]() ![]() ![]() |
RMI Access Builder (E) | IBM Enterprise RMI Access Builder Library | ivjrmi.zip, ivjrmicl.jar | ![]() ![]() ![]() ![]() |
Java-to-C++ (E) | IBM Enterprise CPP Access Builder Library | ivjcpp30.zip![]() ![]() ![]() |
![]() ![]() ![]() |
Access Builder for SAP R/3 (E) | IBM Access Builder for SAP R/3 Libraries | ivjsap20.jar, infobus.jar![]() ![]() ![]() |
![]() ![]() ![]() |
Persistence Builder (E) | VisualAge Persistence, VisualAge Persistence Common Runtime | ivjpb30 | ![]() ![]() ![]() |
ET/400 (E) | IBM Enterprise Toolkit for AS/400 | as400ut.jar, jt400.jar, jt400mri.zip | ![]() Non visual also: ![]() |
HPJ for Workstations (E) | n/a | Use the hpjdeploy command to generate the runtime. See the ET/Workstation task Deploying Applications and reference hpjdeploy Command. | ![]() ![]() ![]() |
Servlet Builder (E) | IBM Servlet Builder class libraries | ivjsb30 | ![]() ![]() ![]() ![]() |
Domino Agent Runner | n/a | IVJAgentRunner.jar and AgentRunner.nsf (in IBMVJava\eab\runtime30\domino\ar\) | ![]() |
e-Connectors (E) | Common Connector Framework | ccf (in IBM Connectors/classes) This is a prerequisite for all e-Connector runtimes. | ![]() ![]() ![]() ![]() |
Connector SAP | ivjsap12.jar, infobus.jar![]() ![]() ![]() |
![]() ![]() ![]() |
|
Connector IMS TOC | imstoc (in IBM Connectors/classes) | ![]() ![]() |
|
Connector MQSeries | mqccf (in IBM Connectors/classes) | ![]() ![]() ![]() |
|
Connector HOD | hod40connector, hod40converters (in IBM Connectors/classes) | ![]() ![]() ![]() ![]() ![]() ![]() |
|
Enterprise Access Builder for Transactions (E) | IBM Enterprise Access Builder Library | eablib | ![]() ![]() ![]() ![]() |
SQLJ | SQLJ Runtime Library | sqlj-runtime | ![]() ![]() ![]() |
Data Access Beans | IBM Data Access Beans | ivjdab | ![]() ![]() ![]() |
Java Record Framework (E) | IBM Java Record Library | recjava (also in IBM Connectors/classes) | ![]() ![]() ![]() ![]() |
The runtime directories also contain the unzipped form of most of the runtime libraries so that your CLASSPATH need only contain the IBMVJava/eab/runtime30 and runtime20 directories, as opposed to each runtime Zip. This simplifies setting up for testing applications on your development machine.
Warning: It is important that you test the deployment of your applications as your end-users will see them, specifically without the unzipped runtimes on their CLASSPATH. You can easily do this by removing the IBMVJava/eab/runtime30 directory (and other runtime directories you may have added) from your CLASSPATH variable.
Runtimes for previous releases are provided in the IBMVJava/eab/runtime20 directory (and also the extras/runtime20 directory on the product CD).
Deploying an application to debug it
If you want to debug an application that has been deployed, you must install the
appropriate debugger back-end on the target machine. See the online help for the
VisualAge for Java debugger you are using for more information.