Installer Command Line Arguments

[#1]

Summary

This article documents the arguments that may be passed to an installer from the command line.

Synopsis

This article documents the arguments that may be passed to an installer from the command line.

Discussion

The installer launcher will use the following environment variables if they are set prior to launching the installer:

• LAX_VM This is used to set the location of the Java executable with which to launch the installer.
• LAX_DEBUG Can be set to either true, false, or file. When set to true, the debug output will be written to the console. When set to file, a file named jx.log will be created in the same directory as the launcher containing the debug output.
• IATEMPDIR This is used to set the location the launcher will use as the directory to extract its files to.
• IA_PATH_[SOURCE_PATH] where [SOURCE_PATH] is the name of a Source Path used in your project. Used to override the the default location of the Source Path.

The following arguments may be passed to the installer on the command line:

• -help or -? for help. In order to view the output on Windows, the launcher must be created as a Console Launcher, not a GUI Launcher.
• -i [ swing | console | silent ] Used to set the UI mode used by the installer to either Swing, Console, or Silent.
• -l Uses the specified language code (and optional country code) to set the locale for the InstallAnywhere Installer.
• -r Generates a response file from the choices made in the installation.
• -f Override the default location of the response file which the installer should use.
• -DVAR_NAME=VAR_VALUE Will set the IA Variable VAR_NAME to the value VAR_VALUE in the installer. Can be used multiple times for multiple variables.
• LAX_VM /path/to/java Used to force the launcher to use a particular JVM on the target machine. This command line argument should immediately follow the launcher name on the command line.

Additional Information

For more information on the different types of Windows launchers, please see the HelpNet article, Installer Modes.

For more information on how Source Paths work, please see the HelpNet articles Source Paths and Adding and Removing Source Paths.