Before recording a response file

Review the information before recording a response file to silently install, update, modify, roll back, or uninstall an IBM software product:


The -skipInstall agentDataLocation argument

When recording a response file with the -skipInstall agentDataLocation command-line argument, we run the installation process, but the IBM software product is not installed. By using the -skipInstall agentDataLocation argument, we can create a response file for an installation process without running the installation. The agentDataLocation location stores the data for installing the product on other computers. The next time we use -skipInstall with the same agentDataLocation, we can record a response file to update, modify, roll back, or uninstall the product.

If we have multiple deployment scenarios, we can record multiple response files.

If we use -skipInstall agentDataLocation, use different directories for the agentDataLocation in each scenario.

For example, we record a response file to install an IBM software product.


Search preferences

To determine whether Installation Manager searches for updates to installed products, including itself, select these preferences:

For computers that have access to the ibm.com website and have those preferences selected, we can run the silent installation command with the argument. The updateAll argument searches available repositories for updates. For computers that do not have access to the ibm.com website or do not have those preferences selected, we must download fix packs from ibm.com, update the response file with the repository location, and run the silent installation command with the input argument. For information about the search preferences, see:


Record a response file to install, update, modify, roll back, or uninstall a product

We can use one response file to record each change to a product. Or we can record a new response file for each change. The contents of the response file change based on the actions that you take while we record a response file.

For example, we record the installProduct.xml response file. During installation, we install only the client application. After you complete the recording, the installProduct.xml file contains the commands to install the client application. Later we decide to install the server application. During the recording, you specify the same name for the installProduct.xml response file. The installProduct.xml file is updated to contain only the commands to install the server application. The response file does not contain the commands to install the client application.

Restriction: We cannot record a response file to install, update, modify, or uninstall Installation Manager. We can modify a response file to install, update, modify, or uninstall Installation Manager, see Modify a response file to install a package and Installation Manager.


File names for the agentDataLocation installation directory

To record response files for multiple product installation scenarios, use descriptive directory names.

For example, we must create a response file for an administrators computer and a response file for a users computer. We use the -skipInstall agentDataLocation option when we record the response file. Specify these directory names for the different installations: ProductA1.Admin and ProductA1.Users.


Platforms

We must record a response file on the same platform that you plan for the installation. If we plan installations for multiple platforms, we must have a response file for each platform. For example, to install on a computer that runs Microsoft Windows, we must record the response file on a computer that runs Windows.  We can record a response file with Windows XP Professional and use the response file with Windows 2003.  To install software on a Linux computer, we must record the response file on a computer that runs Linux.


Repositories

To avoid downloading the repository files to each computer, locate the repository in a directory that the computers for installation can access. To use only one repository for the installation files or to install products from an HTTP server, use Packaging Utility to create a repository that contains all the installation files. If the repositories are on a shared drive, select a drive that is common to the computers we are installing the software on.  The response file stores the drive and directory location for the repositories. If the drive letter is different for the computer we are installing software on, we must manually edit the response file to change the drive letter.

See Repository preferences for information about repository preferences. See Overview of IBM Packaging Utility for information about the Packaging Utility.


Silent installation preference keys

Some silent installation preferences cannot be edited in the Installation Manager interface. We must manually edit the response file. For information about silent installation preferences, see Silent installation preference keys.


Home