Run-Time Behavior for LaunchAnywhere Files on macOS and OS X–Based Systems
InstallAnywhere 2020
Note the following behavior that occurs at run time if your macOS 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 macOS 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. |
See Also
LaunchAnywhere
Install Actions
LAX Properties
Open topic with navigation