The Java SE Runtime Environment (JRE) on Solaris is not bundled with an installer. Software vendors should consider bundling the Java SE Runtime Environment and an installer with the software they supply to end-users.
There are several ways that the directory heirarchy of the Java SE Runtime Environment and application software can be structured. A suggested directory structure is as follows:
[app-dir] ________________|___________ | | | bin lib [runtime-dir] | | ________|________ app.jar | | bin lib | |
The Java SE Runtime Environment is installed in its own subdirectory, referred to as [runtime-dir] which includes all of the Java SE Runtime Environment's required files (as listed in the README) in the bin and lib sub-directories. The bin and lib directories beneath [runtime-dir] should have the same directory hierarchy and relative placement of files as the bin and lib directories created upon installation of the Java SE Runtime Environment. Optional internationalization files can be included for language localization support, if desired. Note that this directory structure is used by the JDK.
The example directory structure above shows all application-specific classes in the file [app-dir]/lib/app.jar. To make maintenance of the software easier, it is recommend that application-specific software be placed in a directory other than the Java SE Runtime Environment's directory, as in the example.
If native code support is required, then the native library must be located on the path specified by LD_LIBRARY_PATH. One way to do this in the above example would be to install the native libraries in [app-dir]/lib/[sys]. LD_LIBRARY_PATH would then be set to include these directories.