The EGL runtime code for generated Java™ applications
is in the Rational® Business
Developer plugins directory. The plugins directory
is located in the product shared resources directory.
The runtime code is located in the following plug-in JAR file:
com.ibm.etools.egl.java.binaries_version.jar
- version
- The version number for the product.
The following distributed platforms are supported:
- AIX®
- HP-UX
- Linux (Intel)
- Linux (zSeries)
- iSeries®
- Solaris
- USS
- Windows platforms
See product prerequisites for supported versions. EGL provides
32- and 64-bit support for AIX,
HP-UX, Solaris, Linux, and Windows platforms. zSeries support is 64–bit only.
The runtime code includes the following:
- JAR files which contain Java code
that is common to all supported distributed platforms
- Platform-specific code
Do as follows:
- Extract the files to each system on which deployed EGL applications
are to be run.
- Include the JAR files in the CLASSPATH of the deployment systems.
Here are the files:
- fda7.jar is required for all uses and is in com.ibm.etools.egl.java.runtime_version,
where version is the product version.
- fda6wrappers.jar is needed if you used Java wrappers in EGL version 6.x, are regenerating
the wrappers in EGL 7.x, and wish to avoid updating the native Java code that invokes the wrappers.
In this case, set the build descriptor option wrapperCompatibility to V6 at
generation time, as noted in the help topic for that option.
The
file fda6wrappers.jar is in the same location as fda7.jar.
- hpt.jar is needed in two cases:
- You are running web transactions; or
- You used Java wrappers in VisualAge® Generator version
4.x or 5.x, are regenerating the wrappers in EGL 7.x, and wish to
avoid updating the native Java code
that invokes the wrappers. In this case, set the build descriptor
option wrapperCompatibility to V4 or V5,
as appropriate. For details, see the help topic for that option.
The file hpt.jar is in com.ibm.etools.egl.java.runtime_version\webtrans,
where version is the product version.
- hpt.gateway is also needed if you are running web transactions.
The file is in the same location as hpt.jar.
- vgjwgs.jar is needed if you are running web transactions that
were generated with VisualAge Generator
4.x.
- Copy any platform-specific code to a directory on each deployment
system; and set environment variables for each of those systems as
appropriate:
- For AIX (32- or 64-bit support)
- The files of interest are in the directory Aix or
(for 64-bit support) Aix. Change the PATH and
LIBPATH environment variables so they reference the directory that
contains the platform-specific code you copied from the website. Note
that if libCursesCanvas7.so is on the path in
the LIBPATH variable, the Java runtime
will use Curses for the Text or Console user interface (drawn directly
on your terminal window) and the Swing library, which opens a new
window for the UI, will be unavailable.
- For HP-UX (32- or 64-bit support)
- The runtime files are in one of the following four directories:
- For Itanium processors:
- HPUXItanium
- HPUX64Itanium (for 64-bit support)
- For RISC processors:
- HPUXRisc
- HPUX64Risc (for 64-bit support)
If the
libCursesCanvas7 library (.so
extension for Itanium, .sl
extension for RISC) is on your library path:
- The Java runtime uses Curses
for the Text or Console user interface, which is drawn directly on
your terminal window.
- The Swing library, which opens a new window for the UI, is unavailable.
For Itanium processors
and 64-bit RISC processors, use the LD_LIBRARY_PATH environment variable
for the library path. For 32-bit RISC processors, use the SHLIB_PATH
environment variable for the library path. Change the appropriate
variable to include the directory that contains the platform-specific
code you copied from the website.
- For iSeries
- The files of interest are in the directory iSeries.
In qshell, change to the directory you just uploaded the files to
and run the setup.sh script with the "install" option:
- > setup.sh install
- In addition, some other environment variables must be set. For
information on how to set these environment variables, run the script
with the "envinfo" option:
- > setup.sh envinfo
- If for some reason you delete a symlink that is created for you
during install, you can recreate it with the "link" option:
- > setup.sh link
You also need to set
the LIBPATH environment variable.
- For Linux (32- or 64-bit
support, Intel hardware)
- The required files are in the following directory:
- Linux, for 32-bit support.
- Linux64, for 64-bit support.
Change the PATH and LD_LIBRARY_PATH environment variables
so they reference the directory that contains the platform-specific
code you copied from the website. Note that if libCursesCanvas7.so is
on the path in the LD_LIBRARY_PATH variable, the Java runtime will use Curses for the Text or
Console user interface (drawn directly on your terminal window) and
the Swing library, which opens a new window for the UI, will be unavailable.
- For Linux (zSeries hardware)
- The required files are in the directory Linux. Change
the LD_LIBRARY_PATH environment variable so it references the directory
that contains the platform-specific code you copied from the website.
(EGL provides no executable programs for this platform, so it does
not require the PATH variable.)
- For Solaris (32- or 64-bit support)
- The files of interest are in the directory Solaris or
(for 64-bit support) Solaris64. Change
the PATH and LD_LIBRARY_PATH environment variables so they reference
the directory that contains the platform-specific code you copied
from the website. Note that if libCursesCanvas7.so is
on the path in the LD_LIBRARY_PATH variable, the Java runtime will use Curses for the Text or
Console user interface (drawn directly on your terminal window) and
the Swing library, which opens a new window for the UI, will be unavailable.
- For USS
- The files of interest are in the directory USS.
Change the PATH and LIBPATH environment variables so they reference
the directory that contains the platform-specific code you copied
from the website.
- For supported (32- or 64-bit) Windows platforms
- The files of interest are in the directory Win32 or Win64.
Change the PATH environment variable so it references the directory
that contains the platform-specific code you copied from the website.