Response file commands

You can use this reference table to learn more about response file commands.

The offering id value refers to package id in the provided examples: id='offering id'.

Response file commands Description
Profile
<profile 
id='the profile (package group) id' 
installLocation='the installation location of  the profile'
<data key='key1' value='value1'/>
<data key='key2' value='value2'/>

</profile>
A profile is an installation location. Use the profile command to create a package group or installation location. If the specified package group exists, then the command has no effect. Currently, when creating the profile, the silent installation creates two installation contexts: one for Eclipse and one for native.

You can use the data element to set profile properties.

The following list contains the currently supported keys and related values for Installation Manager installations:

  • The eclipseLocation key specifies an existing Eclipse location value, such as c:\myeclipse\eclipse.
  • The cic.selector.arch key specifies the architecture to install: 32-bit or 64-bit.

    32-bit 64-bit
    ia64_32 ia64
    PA_RISC PA_RISC64
    ppc ppc64
    s390 s390x
    sparc sparc64
    x86 x86_64

  • The cic.selector.nl key specifies the language pack to be installed, using ISO-639 language codes such as zh, ja, and en. If you are installing the translations for an offering, include this property key in your response file. Your language choices apply to all packages installed in the package group.

Separate multiple NL values with commas.

The following list contains the currently supported language codes:

  • Arabic (ar)
  • Czech (cs)
  • Danish (da)
  • English (en)
  • French (fr)
  • German (de)
  • Greek (el)
  • Hungarian (hu)
  • Italian (it)
  • Japanese (ja)
  • Korean (ko)
  • Lithuanian (li)
  • Polish (pl)
  • Portuguese (pt_BR)
  • Russian (ru)
  • Simplified Chinese (zh_CN)
  • Slovenian (sl)
  • Spanish (es)
  • Traditional Chinese (Taiwan) (zh_TW)
  • Turkish (tr)

Some languages support only partial translations. When a language is partially translated, the untranslated content defaults to English. You can find additional property keys in the documentation for the product you are installing.

Repositories
<server>
<repository location='http://example/
repository/'>
<repository location=”file:/C:/
repository/”>
!—add more repositories below--
…
      </server>
Use this command to specify the repositories that are used during a silent installation. Use a URL or UNC path to specify remote repositories; or use directory paths to specify local repositories.
Install
<install>
<offering profile= 'profile id' 
features= 'feature ids' 
id= 'offering id' version= 'version' 
selected='true' installFixes='value'></offering>

!—add more offerings below
…

</install>

Install features with a package:

<install modify='true'> or <install modify='false'> (optional attribute)

<install modify='true'>
<offering profile='profile id'
 id='offering id' version='version' 
features='-'/>
</install>
Use the install command to specify the installation packages to install.

Profile: The profile ID must match an existing profile or a profile created by the set profile command.

Features: Feature IDs can be optionally specified by a comma-delimited list. For example: 'feature1, feature2'. If no feature IDs are specified, the default features are installed.

Required features are installed even when they are not explicitly specified in the comma-delimited list.

Selected: The selected attribute is optional. By default, selected is set to true. When selected is set to false, silent installation does not install the package. While running in the wizard mode, the package shows in the package selection page but is not selected initially.

Version: The version number is not required. If no version is specified, the Installation Manager installs the latest product with the specified ID.

For example, to install Product A version 1.0:

<server>
     <repository location="http://productA/version10/repository/">
</server>

<install>
     <offering profile= 'IBM Software Development Platform' features= 'main_feature' id= 'com.ibm.productA'</offering>
</install>

For example, to install Product A version 1.0.1:

<server>
     <repository location=”http://productA/version101/repository/">
</server>

<install>
<offering profile= 'IBM Software Development Platform' features= 'main_feature' id= 'com.ibm.productA'</offering>
</install>

installFixes: You can choose to install or not to install fixes with the offering. Include one of the following values with the install command to specify fixes to install with the latest version of the offering:

  • installFixes='all'
  • installFixes='recommended'
  • installFixes='none'

If you have specified a version for your offering ID, the installFixes default value is 'none'. If you have not specified a version for your offering, the installFixes default value is 'all'.

Modify: The default value is false. This attribute is optional. Use the modify='false' attribute to indicate that you do not want to modify an existing installation by including additional features. Use the modify='true' attribute to indicate that you want to modify an existing installation by including additional features.

When you are installing only additional language packs, use a hyphen “-“ in the feature list to indicate that no other new features are being added. You must specify modify='true' and features='-' to add language packs. If you do not, the install command installs all of the default features.

Update (in wizard mode)
<update>
<offering profile= 'profile id'>
</update>
Use this command to specify the profile to update. The profile ID must match an existing profile.

This command can be used only in wizard mode to start the Update wizard; it does not work in silent mode.

Modify (in wizard mode)
<modify>
<offering profile= 'profile id'>
</modify>
Use this command to specify the profile to modify. The profile ID must match an existing profile.

This command can be used only in wizard mode to start the Update wizard. The command does not work in silent mode.

Uninstall
<uninstall>
<offering profile= 'profile id' 
features= 'feature ids' 
id= 'offering id' version= 'version'>
</offering>

!—add more offerings below
<…></uninstall>

Uninstall a package without specifying a version:

<uninstall>
<offering profile= 'profile id' 
id= 'offering id'></offering>
</uninstall>

Uninstall all packages within a package group:

<uninstall>
<offering profile= 'profile id'>
</offering>
</uninstall>

Uninstall features:

<uninstall modify='true'> or <uninstall modify='false'> (optional attribute)

<uninstall modify='true'>
<offering profile='profile id'
 id='offering id' version='version' 
features='-'/>
</uninstall>
Use the uninstall command to specify the packages to uninstall.

Profile: The profile ID must match an existing profile or a profile specified in a profile command. Specifying the feature ID, offering ID or version is optional. You can specify the profile ID with none, one, two or all three of the options: feature ID, offering ID or version.

For example, when there is no feature ID, offering ID or version specified, then all the features, offerings and versions in the specified profile ID are uninstalled. If you specify the profile ID and version, then the installed packages that match the profile ID and version are uninstalled. All the features and offerings that match the profile ID and version are uninstalled.

Modify: The default value is false. This attribute is optional. Use the modify='false' attribute to indicate that you do not want to modify an existing uninstall by removing additional features. Use the modify='true' attribute to indicate that you want to modify an existing uninstall by removing additional features.

When you are uninstalling only additional language packs, use a hyphen “-“ in the feature list to indicate that no other features are being removed. You must specify modify='true' and features='-' to remove language packs. If you do not, the uninstall command removes all of the features.

Import
<import>
<offering profile= 'profile id' 
features= 'feature id' 
id= 'offering id' version= 'version' 
selected='true'></offering>

!—add more offerings below
<…>
</import>
Use the import command to specify the existing installation packages to import.
Rollback
<rollback>
<offering profile= 'profile id'
 id= 'offering id' 
version= 'version'>
</offering>

!—add more offerings below
<…>

</rollback>
Use the rollback command to roll back to the specified version from the current version. You cannot specify features in a rollback command.
InstallAll
<installAll installFixes='value'/>

This command is equivalent to using

-silent installAll 

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.

Use this command to silently search for and install all available packages.

You can choose to install or not to install fixes with the offering. Include one of the following values with the installAll command to specify fixes to install with the latest version of all offerings:

  • installFixes='all'
  • installFixes='recommended'
  • installFixes='none'

The installFixes default value for installAll is 'none'.

UpdateAll
<updateALL installFixes='value'/>

This command is equivalent to using

-silent updateAll 
.
Use this command to silently search for and update all available packages.

You can choose to update or not to update fixes with the offering. Include one of the following values with the updateAll command to specify fixes to update with the latest version of all offerings:

  • installFixes='all'
  • installFixes='recommended'
  • installFixes='none'

The installFixes default value for updateAll is 'all'.

License
<license policyFile='policy file  location'  merge='true'/>

For example:

<license policyFile='c:\mylicense.opt' merge='true'/> 
Use the license command to generate a response file that contains a license command. You start the Manage Licenses wizard after starting IBM Installation Manager in record mode.

During record mode, when you set flex options through the Manage Licenses wizard, the options that you set are recorded in a license policy file named license.opt. The license.opt file is in the same directory as the generated response file and the response file contains a license command that references the policy file.

Set the merge attribute to true or false. By default, the merge attribute is set to true. When set to the default setting of true, new policy data in the specified license policy is merged with the existing license policy. When set to false, the exist policy is overwritten by the policy specified in the license policy file.

Not all IBM products use Installation Manager to manage licenses. Check documentation for your product for license administration information.


Additional response file attributes

Response file attribute Description
Clean
<agent-input clean='true'>
</agent-input>
By default, the clean attribute is set to false. Installation Manager uses the repository and other preferences that are specified in the response file and the existing preferences set in Installation Manager. If a preference is specified in the response file and set in the Installation Manager, the preference that is specified in the response file takes precedence.

When the clean attribute is set to true, Installation Manager uses the repository and other preferences that are specified in the response file. Installation Manager does not use the existing preferences set in Installation Manager.

Temporary

<agent-input clean='true' temporary='false'>
</agent-input>
When the temporary attribute is set to false, the preferences that are set in your response file persist. The default value is false. When the temporary attribute is set to true, the preferences that are set in the response file do not persist. You can use the temporary and clean attributes together. For example, you set clean to true and temporary to false. After running the silent installation, the repository setting that is specified in the response file overrides the preferences that were previously set.
Reboot later
<agent-input rebootLater='false'>
</agent-input>
When rebootLater is set to false and the installed package requires restarting the system on Windows, Installation Manager restarts the system after the execution of the response file is finished. The default value is false.

When rebootLater is set to true, the system does not restart.


Deprecated response file attributes

Response file attribute Description
License agreement acceptance
<agent-input acceptLicense='false'>
</agent-input>

Deprecated in Installation Manager 1.4.3. Use -acceptLicense on the command line.

By default, you do not agree to accept the licenses that an installation package carries when using Installation Manager in silent installation mode. If the package you are installing has a license agreement that must be accepted, the silent installation operation fails. To accept the license agreement, you must set the attribute to <agent-input acceptLicense='true'>. By doing so, you agree to accept the license agreements for every package specified in the response file.

+

Search Tips   |   Advanced Search