Argument | Description |
---|---|
-accessRights | Defines whether Installation Manager operates
in administrator or nonadministrator mode. For nonadministrator mode,
use the —accessRights argument with the nonAdmin parameter: -accessRights
nonAdmin For administrator mode, use —accessRights with
the admin parameter: -accessRights admin. If —accessRights is
not used, the default value is set based on current user permissions.
Note:
For Microsoft® Windows® XP users who are members of the Administrator
group, the default value is always -accessRights admin.
For these users to run in nonadministrator mode, pass the -accessRights
nonAdmin argument explicitly.Installation Manager reports an error when the user does not have appropriate system permissions. Attention: Do not change this argument when installing, modifying,
updating, rolling back, or uninstalling the same instance of Installation Manager. For example,
User1 installs Installation Manager
in the C:\user1\InstallationManager directory
with administrator access rights. When running a command to modify Installation Manager in the C:\user1\InstallationManager directory,
User1 must not use the -accessRights nonAdmin argument.
For information about installing as an administrator or nonadministrator, see Installing as an administrator or nonadministrator. |
-dataLocation <agentDataLocation> | Specifies the directory location for the Installation Manager data directory.
This location stores information about installed packages. Set this
location when installing Installation Manager. Attention: Do not change this argument after Installation Manager is installed.
Changing this argument can damage the installation data. This damage
can prevent you from modifying, updating, rolling back, or uninstalling
installed packages.
For information about the types of files and information stored in the agent data Location, see Agent data location. |
-encryptString stringToEncrypt | Encrypts the entered string. Use -encryptString with -passwordKey to
increase encryption security. In the user interface, the following command opens the String Encryption Utility window: IBMIM -encryptString password where password is the string that is encrypted. In the String Encryption Utility window, the String to be encrypted field contains the string to encrypt. The Encrypted version of the string field contains the encrypted value to copy into the response file. In the String Encryption Utility, you can change the String to be encrypted field, and then click OK to generate a new encrypted string. In the command-line interface, the following command returns the encrypted string on the command line:IBMIM -silent -noSplash -encryptString password where password is the string that is encrypted. When you record a response file, encrypted strings for passwords are created and stored in the response file. where value contains the encrypted string. An
example of an encrypted string from a response file for IBM Rational
ClearCase:
<profile installLocation='C:Program Files\IBM\RationalSDLC' id="IBM Rational SDLC'> <data key='user.CC_ServerProcessPassword,com.ibm.rational.clearcase.nt_i386' value='1ML/Coqkg33e5616BcUnYg==' </profile> After recording the response file, use -encryptString to generate and paste different encrypted strings into the response file. For example, you record a response file. You have five computers to install an IBM product on by using the response file. Each of the five computers requires a different password value for a data key in the response file. Before running the installation on one of the computers, generate the encrypted string for the password to be used on the computer. Copy the encrypted string into the response file. Start the silent installation with the updated response file. |
-exportInstallData <InstallDataFile> | Exports installation data to the specified file in a .zip
file format. You can use this argument to generate a .zip file
that contains data for problem analysis.
|
-help | Displays a short description of Installation Manager command-line arguments. |
-ignoreRepositoryDigest | Directs Installation Manager to ignore the repository digest file, repository.xml, when accessing repositories. |
-input <responseFile> | Specifies an XML response file as the
input to Installation Manager or
the Installation Manager installer.
The response file contains commands that Installation Manageror the Installation Manager installer
run. You cannot use -input with -installAll or -updateAll You
can use a file path or a URL for the <responsefile>
value. These examples show file paths and URL strings:
Remember: You can record a response file,
edit a sample response file, or manually create a response file.
|
-keyring <file> [-password <password>] | When specified, causes Eclipse to create keyring file if
a keyring file does not exist. The -password <password> argument
is optional. If the password is not specified, Eclipse uses a default
password. You can provide stronger encryption by specifying a password
to open the key ring file. The contents of the key ring file are encrypted. You must have write permissions for the keyring file. Installation Manager uses the Eclipse infrastructure to save credentials to a key ring file. For additional information about key ring files, refer to the Eclipse workbench user's guide available from http://www.eclipse.org. |
--launcher.ini <.ini file> Examples:
|
Specifies the location of the product .ini file to use. When
this argument is not specified, Installation Manager checks
for a file in the same directory as the launcher that has the same
name and the ".ini" extension. For example, if installc.exe is
the launcher, Installation Manager checks
for installc.ini. The silent-install.ini file contains the initialization parameters for installing silently. The silent-install.ini file is located in the same directory as the installc.exe file and must be present. The user-silent-install.ini file is used for a nonadministrator installation. The user-silent-uninstall.ini file is used for a nonadministrator uninstall procedure. Important: The version of silent-install.ini and user-silent-install.ini files
provided in the installation files for Installation Manager use the -input command-line
argument . To use -installAll or -updateAll with
these .ini files, you must remove two lines: the -input line
and the line that points to the response file. An example of the two
lines to remove:
-input @osgi.install.area\install.xmlIf the -input and response file lines are not removed, the -installAll and -updateAll command-line arguments do not work. The .ini files in the Installation Manager installation directory do not use the -input command-line argument . An example of a silent-install.ini file
from the installation files for Installation Manager:
-accessRights admin -vm jre_5.0.2.sr8a_20080811b\jre\bin\java.exe -nosplash --launcher.suppressErrors -silent -input @osgi.install.area\install.xml -vmargs -Xquickstart -Xgcpolicy: gencon An example of a silent-install.ini file
from the Installation Manager installation
directory:
-accessRights admin -vm C:\Program Files\IBM\Installation Manager\eclipse\jre_5.0.2.sr8a_20080811b\jre\bin\java.exe -nosplash --launcher.suppressErrors -silent -vmargs -Xquickstart -Xgcpolicy: gencon If you run a command that uses the -input argument and the .ini file that you use also contains the -input argument, the response file that the -input argument in the command specifies is used. The response file that the -input argument in the .ini file specifies is ignored. An example of a command that uses the -input argument: ./install --launcher.ini silent-install.ini -input <input file path and name> |
--launcher.suppressErrors | Suppresses the Java™ virtual machine (JVM) error dialog. |
-log | (Optional) Specifies a log file that records the result of
the silent installation. The log file is an XML file. When your silent installation is complete, the log file contains the root element of <result> </result>. When errors occur during the installation, the silent install log file contains error elements and messages. Do not use -log when recording a response file. |
-mode wizard | Runs the Install wizard with the specified response file. You must use -input when using -mode wizard. |
-nosplash | Suppresses the splash screen. |
-passwordKey | Opens a window for the user to enter a password key. The password key is used to encrypt or decrypt fields requiring encryption. Using -passwordKey without specifying <passwordKey> is supported for the GUI mode only. For silent installations, you must use -passwordKey <passwordKey>. |
-passwordKey <passwordKey> | Uses <passwordKey> to encrypt or decrypt passwords. |
-record <responseFile> | Specifies the location of the response file. |
-showProgress | Displays a progress bar on the console. |
-ShowVerboseProgress | Displays progress text on the console. For example, the text Reboot the machine to complete the install. is displayed when restarting the computer is required. |
-silent
|
Specifies that the Installation Manager installer
or Installation Manager run
in silent mode. Use -silent -installAll to silently install all available packages. Use -silent -updateAll to silently update all installed packages. You cannot use -input with -installAll and -updateAll.
With -installAll, the default features for a package
are installed. To specify which features are installed, you must use -input <responseFile>.
The response file contains the information about which features to
install.
Note: When you record a response file, you can select the
features to install.
|
-skipInstall <agentDataLocation> | Records a response file without installing the IBM product.
The agentDataLocation value specifies the directory
location for the installation folders and files. Although the IBM
product is not installed, the files and folders that are required
for installation are created and stored in the specified directory.
The directory must be writable. Verify that the file paths in the argument exist. Installation Manager does not create directories for response files. Attention: Do
not specify an existing agentDataLocation directory
for the new agentDataLocation location value. See Agent data location for
default locations of the agentDataLocation directory.
Important: When you record a response file
using the -skipInstall argument, you must keep the
directory, folders, and files that are created. By keeping the agentDataLocation directory,
you can modify the installation later. When you record a new response
file to modify the installation, you specify the same directory for agentDataLocation.
Use a different agentDataLocation value for each version of an IBM product that you install. You must first record an installation of an IBM product using -skipInstall before you record an update. |
-version | Prints the version of the application then exits. |
-vm | Specifies the Java launcher. In silent mode, always use java.exe on Windows, and java on Linux® and UNIX®. |