Virtual Machines

With InstallAnywhere developers can define a valid list of JVMs their installer can use. This option can be used to select VMs that have been fully tested. LaunchAnywhere searches for VMs sequentially based on VM type (Java 1 JRE, Java 2 JRE, JDK, and so on). Valid VM types are listed in the LaunchAnywhere executable's lax.nl.valid.vm.list property.

LaunchAnywhere uses the following approaches on each platform:

• Windows: first search on the system path, then the system Registry.

• UNIX: search the system path.

• Mac OS X: LaunchAnywhere will use the VM specified in the Project | Platforms | Mac OS X task.

InstallAnywhere developers can also set the heap size for the VMs.

NOTE

Change the heap size when experiencing out-of-memory conditions. With large installations that have many files to install, the heap size may need to be increased.

Optional Installer Arguments

To support JVM configuration options that are not available through the InstallAnywhere advanced designer, specify additional command-line parameters to pass to the JVM used by the installer through the use of the Optional Installer Arguments | Additional Arguments field.

Java

The Project | Java subtask enables developers to fine-tune the classpath settings and decide whether to install the bundled JVM. Developers may choose not to install a VM, to install the VM only while performing the installation, or to leave the VM on the target system. If developers choose to install the VM, the VM install folder pull-down list provides a variety of locations.