Customizing Individual Launcher Settings
InstallAnywhere 2023 R2
InstallAnywhere lets you specify which JVM each LaunchAnywhere in your project should use.
To specify which JVM a launcher in your project should use:
| 1. | In the Advanced Designer, on the Sequence page, click Install. The Install view opens. |
| 2. | In the Visual Tree, select the Create LaunchAnywhere item that you want to configure. |
| 3. | Click the Properties tab at the bottom of the screen. |
| 4. | Click the Advanced Settings subtab. |
| 5. | In the Configure LaunchAnywhere with list, select the appropriate option. Available options are: |
| • | VM selected by the installer or by the end user via Choose VM Panel—The launcher uses the same JVM that the end user selected or that the installer chose. |
| • | VM used by the installer—The launcher uses the same JVM that was used to run the installer. |
When the VM that was bundled with the installer is present, the launcher uses that VM. If no VM was bundled with the installer, the launcher uses the JVM that was specified in the Installer Valid VM List (on the Installer Settings tab, which is available in the JVM Settings view of the Project page) as its value for lax.nl.valid.vm.list.
| • | the first VM found in the system matching the VM Search Settings defined under Project -> JVM Settings—The launcher uses the JVM that was selected during the installer’s JVM search. |
The launcher’s JVM selection criteria are set at install time. Therefore, the launcher itself does not use any customized search paths or Java executable patterns that are set on the Windows and UNIX subtabs of the Search Panel Settings tab (Project page > JVM Settings view > Search Panel Settings tab).
| • | no specific VM—The launcher performs its own JVM search at the time that the launcher is run. |
If you select this option, the launcher uses the value in its lax.nl.valid.vm.list property as the VM search criteria.
Note:Now only the JVMs in a secure location will be allowed to launch the installer as an administrator on the Windows platform. The JVMs in the non-admin user folders will not be permitted to be used and will be restricted with security error message. This behaviour option can be turned off by setting the designer.jvm.securefolder.check property to false in the com.zerog.ia.Designer.properties.
Note:For a detailed discussion of how the launcher’s Advanced Settings options affect VM selection, see About the Launcher’s JVM Selection Behavior at Run‑Time.
See Also