Run-Time Behavior for LaunchAnywhere Files on OS and OS X–Based Systems

InstallAnywhere 2023 R2

Note the following behavior that occurs at run time if your OS or OS X–based installer does not include a bundled VM and an end user uses the LAX_VM parameter for LaunchAnywhere to override the JRE that the installer or uninstaller uses:

•

If the end user uses LAX_VM for installation and uninstallation, both the installer and the uninstaller use whatever JVM was passed with LAX_VM.

•

If the end user uses LAX_VM for installation but does not use it for uninstallation, both the installer and the uninstaller use whatever JVM was passed with LAX_VM for the installation. If the specified JVM is not found, the system JVM is used.

•

If the end user does not use LAX_VM for the installation but does use LAX_VM for uninstallation, the installer uses the system JVM, and the uninstaller uses whatever JVM was passed with LAX_VM.

Note the following behavior that occurs if your OS or OS X–based installer includes a bundled VM:

•

If the end user uses LAX_VM for installation and uninstallation, both the installer and the uninstaller use whatever JVM was passed with LAX_VM.

•

If the end user uses LAX_VM for installation but does not use it for uninstallation, the installer uses whatever JVM was passed with LAX_VM for the installation. The uninstaller uses the bundled JVM.

•

If the end user does not use LAX_VM for the installation but does use LAX_VM for uninstallation, the installer uses the bundled JVM, and the uninstaller uses whatever JVM was passed with LAX_VM.

Note:If the Windows installer/uninstaller is launched as an administrator with LAX_VM—pointing to a JVM location which is a unsecure/non-admin user folder, then installer/uninstaller will exit. 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.