Using Installation and Uninstallation Launcher Command-Line Options

-cp:a classpath;classpath
-cp:p
classpath;classpath

Modifies the classpath used by the launcher to install/uninstall—Cannot be used with a JAR archive (for example, setup.jar).

To add more than one class, separate each with the platform-specific delimiter. You can also specify that an ASCII file that contains the additional classpaths be used by preceding the filename with @.

Each classpath in this file must be on a separate line.

Adds myclasspath.jar and myotherclasspath.jar to the beginning of the classpath:

./setup.bin -cp:p myclasspath.jar: myotherclasspath.jar

setup.exe -cp:p myclasspath.jar; myotherclasspath.jar

Use the myclasspaths.txt file that contains a list of the additional classpaths, one per line, and add them to the end of the classpath:

setup.exe -cp:a @myclasspaths.txt

-is:javaconsole

Overrides the Distribution's Show Console property value of "False" by turning on the Java console at run time. This option has no affect on how the wizard runs (see the
-console option [Premier edition]).

setup.exe
-is:javaconsole

-is:javahome JavaHome
Directory

Specifically tells the launcher the home directory location of the JVM to use. This option works when executing a Java application launcher, as well as an installation/uninstallation Launcher. The JVM that resides in the specified directory must be one of the JVMs specified in the JVM Search Instructions property in the JVM Resolution view in order for it to work. Otherwise, this command-line option has no effect.

setup.exe -is:javahome
"C:/j2sdk1.4.1_01"

-is:log fileName

This option is useful for launchers that hide the Java console because it logs the detailed information about the launcher's processing, including the actual Java commands that were used to start the Java program, to the specified fileName. This includes all of the std out and std err messages from the Java process.

setup.exe -is:log myLogFile.txt
./setup.sh -is:log
"%HOME//ismp.log"

-is:silent

Prevents the appearance of the Launcher UI to the end user. This does not execute the application itself in silent mode, that is, prevent the Wizard from appearing. To do that, use the -silent option.

./setup.bin -is:silent

-is:tempdir directory

Sets the path to the temporary directory to which the launcher should write its temporary files. If the specified directory does not exist or is not a directory, the launcher will use the system temp directory instead, and no error message is provided.

setup.exe -is:tempdir
"C:/My Documents/temp"

-is:version

Reports the version of the launcher itself. When this option is specified, the launcher simply reports its version and exits without launching the application.

setup.exe -is:version