Use installer to perform other operations
Silently install updates to all products
You can silently search for and install updates for installed products with the installer.
In the same directory as the installation command, Installation Manager checks for a file that has the same name and the ".ini" extension. For example, if installc is the command, Installation Manager checks for installc.ini. If the .ini file contains the -input command, the updateAll command does not work. Before running the command, remove two lines from the .ini file: the line that includes the -input command and the line that points to the response file. An example of the two lines to remove:
-input @osgi.install.area\install.xmlIf you are installing in group mode, you do not need to edit an .ini file.
For version 1.4.4, input is used in the .ini file.
See Installation Manager command-line arguments for information about the input and updateAll commands.
Procedure
To find and install available updates for installed products:
- From a command prompt, switch to the directory that contains the extracted installation files for Installation Manager. Switch to the InstallerImage_platform subdirectory if you are using the installer included with your IBM product.
- Run the command:
Installation Manager 1.4.3...
Operating system Administrator Nonadministrator Group Windows installc.exe updateAll -acceptLicense userinstc.exe updateAll -acceptLicense Not available. Linux, UNIX, IBM i, and z/OS ./installc updateAll -acceptLicense ./userinstc updateAll -acceptLicense ./groupinstc -dataLocation appdata_loc -installationDirectory installation_directory updateAll -acceptLicense Group mode is not supported on IBM i.
Installation Manager 1.4.2 and earlier
installer.ini is a copy of a silent-install.ini or user-silent-install.ini file that does not contain the -input lines.
Windows installc.exe --launcher.ini installer.ini updateAll userinstc.exe --launcher.ini installer.ini updateAll Not available. Linux and UNIX ./install --launcher.ini installer.ini updateAll ./userinstc --launcher.ini installer.ini updateAll ./groupinstc -dataLocation appdata_loc -installationDirectory installation_directory updateAll Start with version 1.4.3:
- Use -acceptLicense in the command.
- Do not use --launcher.ini .ini file as this command option has been deprecated.
Silently install from authenticated repositories
You can silently install from an authenticated repository; however, authenticated repositories require credentials for access.
In the same directory as the installation command, Installation Manager checks for a file that has the same name and the ".ini" extension. For example, if installc is the command, Installation Manager checks for installc.ini. If the .ini file contains the -input command, the installAll command does not work. Before running the command, remove two lines from the .ini file: the line that includes the input command and the line that points to the response file. An example of the two lines to remove:
-input @osgi.install.area\install.xml
- If you are installing in group mode, you do not need to edit an .ini file.
- For version 1.4.4, input is used in the .ini file.
See Installation Manager command-line arguments for information about the -input and installAll commands.
Authenticated repositories are repositories that are in a location requiring credentials. The authentication requirements are set by your company administrators. Installation Manager saves credentials required for authentication but does not configure the authentication requirements.
Installation Manager uses the Eclipse infrastructure to save credentials to a keyring file. When the keyring file is specified in the -keyring keyring_file -password password options, Eclipse creates a keyring file if a keyring file does not exist.
If you share the same instance of Installation Manager with other users, see Save credentials when sharing the same instance of Installation Manager .
For additional information about keyring files, see the Eclipse workbench user's guide available from http://www.eclipse.org .
Procedure
To access authenticated repositories in silent mode, create a keyring file and include the file path in the install command:
- From a command prompt, switch to the directory that contains the extracted installation files for Installation Manager. Switch to the InstallerImage_platform subdirectory if you are using the installer included with your IBM product.
- From the command line, open the tools directory.
- Run the following command:
imutilsc saveCredential -url address -userName user_name -userPassword password -keyring keyring_file_path_with_.keyring_extension[ -password password ] [ -proxyHost proxy_host -proxyPort proxy_port [ -proxyUsername proxy_user_name -proxyUserPassword proxy_user_password ] [ -useSocks ] ] [ -verbose ]If you want to require authentication for the keyring file when referenced in another command, include a password for the keyring file. The keyring file is saved to the specified location.
- Repeat to store the credentials for multiple URLs in one keyring file.
- Switch back up to the main installation files directory.
- Run the installation command:
You must include a password with the install command when the keyring file requires authentication.
Include quotation marks around filepaths that have spaces.
Installation Manager 1.4.3
Operating system Administrator Nonadministrator Group Windows installc.exe input /path/to/respfile -keyringkeyring_file_path_with_.keyring_extension -password password -acceptLicense userinstc.exe input /path/to/respfile -keyring keyring_file_path_with_.keyring_extension -password password -acceptLicense Not available. Linux, UNIX, IBM i, and z/OS ./installc input /path/to/respfile -keyring keyring_file_path_with_.keyring_extension -password password -acceptLicense ./userinstc input /path/to/respfile -keyring keyring_file_path_with_.keyring_extension -password password -acceptLicense ./groupinstc -dataLocation appdata_loc input /path/to/respfile -keyring keyring_file_path_with_.keyring_extension -password password -acceptLicense Installation Manager 1.4.2 and earlier
installer.ini is a copy of a silent-install.ini or user-silent-install.ini file that does not contain the -input lines.
Operating system Administrator Nonadministrator Group Windows installc.exe --launcher.ini installer.ini input /path/to/respfile-keyring keyring_file_path_with_.keyring_extension -password password userinstc.exe --launcher.ini installer.ini input /path/to/respfile -keyring keyring_file_path_with_.keyring_extension -password password Not available. Linux and UNIX ./install --launcher.ini installer.ini input /path/to/respfile -keyring keyring_file_path_with_.keyring_extension -password password ./userinstc --launcher.ini installer.ini input /path/to/respfile -keyring keyring_file_path_with_.keyring_extension-password password ./groupinstc -dataLocation /path/to/respfile input /path/to/respfile -keyring keyring_file_path_with_.keyring_extension-password password Group mode is not supported on IBM i.
Start with version 1.4.3:
- Use -acceptLicense in the command.
- Do not use --launcher.ini .ini file as this command option has been deprecated.
Install available products
installAll is deprecated starting in Installation Manager version 1.4.4. It is recommended that you do not use this command because of a number of potential issues related to installing multiple products at the same time. For example:
- The installation fails if the packages have the same default installation directories but the packages cannot be installed into the same package group.
- The installation might be problematic for packages requiring additional information for installation. The user must provide required data using the -properties option that can cause data collisions among packages.
- You cannot control where extension packages are installed.
- Installation of many packages at the same time might require a significant amount of disk space and might take a long time to complete.
You can search for and silently install available products using the installer.
In the same directory as the installation command, Installation Manager checks for a file that has the same name and the ".ini" extension. For example, if installc is the command, Installation Manager checks for installc.ini. If the .ini file contains the -input command, the installAll command does not work. Before running the command, remove two lines from the .ini file: the line that includes the -input command and the line that points to the response file. An example of the two lines to remove:
-input @osgi.install.area\install.xml
- If you are installing in group mode, you do not need to edit an .ini file.
- For version 1.4.4, input is used in the .ini file.
See Installation Manager command-line arguments for information about the input and installAll commands.
Procedure
To find and install available products using installer:
- From a command prompt, switch to the directory that contains the extracted installation files for Installation Manager. Switch to the InstallerImage_platform subdirectory if you are using the installer included with your IBM product.
- Run the command:
Installation Manager 1.4.3
Operating system Administrator Nonadministrator Group Windows installc.exe installAll -acceptLicense userinstc.exe installAll -acceptLicense Not available. Linux, UNIX, IBM i, and z/OS ./installc installAll -acceptLicense ./userinstc acceptLicense installAll ./groupinstc -dataLocation appdata_loc -installationDirectory installation_directory installAll -acceptLicense Installation Manager 1.4.2 and earlier
installer.ini is a copy of a silent-install.ini or user-silent-install.ini file that does not contain the -input lines.
Windows installc.exe --launcher.ini installer.ini installAll userinstc.exe --launcher.ini installer.ini installAll Not available. Linux and UNIX ./install --launcher.ini installer.ini installAll ./userinst --launcher.ini installer.ini installAll ./groupinstc -dataLocation appdata_loc -installationDirectory installation_directory installAll Group mode is not supported on IBM i.
Start with version 1.4.3:
- Use -acceptLicense in the command.
- Do not use --launcher.ini .ini file as this command option has been deprecated.