You can download additional JREs with the JRE download wizard. Click [JRE download wizard] to download the JREs you need. The drop down list will be updated after the download has finished.
If you wish to bundle a JRE that is not available from ej-technologies' download server or that has custom modifications (like an installation of the javax.comm API), please see the JRE bundle creation wizard on how to create your own JRE bundle.
A statically bundled JRE will always be distributed inside the installation root directory, on Windows and Linux/Unix in the directory jre and on Mac OS X in [content directory]/.install4j/jre.bundle. The content directory is available from the installer runtime variable sys.contentDir. and resolves to the installation directory for folder media file types and Contents/Resources/app for archive media file types. The actual location of the JRE installation directory is available from the installer runtime variable sys.preferredJre after the "Install files" action has run.
When you update your application and include a static JRE bundle again, the old JRE bundle will be deleted prior to installation, so that any files left over from the old JRE cannot interfere with the new JRE.
To enable the download on demand, you have to locate the corresponding .tar.gz bundle archive in the jres subdirectory of your install4j installation and place it on a server so that the HTTP download URL will point to the bundle archive. The URL has to be of the form http://www.myserver.com/somewhere/windows-x86-1.6.0_08.tar.gz.
If the installer determines that there is no suitable JRE present, it will ask the user whether the JRE should be downloaded. If the Start download without user confirmation, if necessary check box has been selected, that confirmation is skipped and the download starts immediately.
If the download fails or is aborted by the user, the download URL will be displayed together with instructions on where to place the downloaded bundle archive.
You can override the default JRE search in a Microsoft Windows installer executable by passing the argument -manual to the installer executable. The installer will then report that no JRE could be found and offer you to locate one in your file system. If you have set up a dynamic JRE bundle, it will also offer you to download one. This is a good way to test if your download URL is correct.
The check box install as a shared JRE determines whether the bundled JRE should be private for the application or whether other applications distributed with install4j can share this JRE. The following scenarios are covered by this approach:
Note: installers generated by install4j will never install a JRE on the system path or make Windows registry changes. The term "shared installation" only applies to applications distributed with install4j. Other applications will not be able to use such a JRE.