Response file commands

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

Profile

<profile 
id="the profile (package group) id" 
installLocation="the install location of
 the profile">
<data key="key1" value=”value1”/>
<data key="key2" value=”value2”/>

</profile>
 A profile is an installation location. Use this command to create a package group (or installation location). If the specified package group already exists, then the command has no effect. Currently, when creating the profile, the silent install will also create 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:
  • The eclipseLocation key specifies an existing Eclipse location value, such as c:\myeclipse\eclipse.
  • The cic.selector.nl key specifies the Natural Language (NL) locale selections, such as zh, ja, and en.
Note: Separate multiple NL values with commas.
The following list contains the language codes. Not every language is supported in every product:
  • English (en)
  • French (fr)
  • Italian (it)
  • Simplified Chinese (zh)
  • Russian (ru)
  • Traditional Chinese (Taiwan) (zh_TW)
  • Traditional Chinese (Hong Kong) (zh_HK)
  • German (de)
  • Japanese (ja)
  • Polish (pl)
  • Spanish (es)
  • Czech (cs)
  • Hungarian (hu)
  • Korean (ko)
  • Portuguese (pt_BR)

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= "offering 
version" selected="true"></offering>

<!—add more offerings below>
<…>

</install>
 Use this command to specify the installation packages that will be installed.

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

Feature IDs can be optionally specified by a comma-delimited list, such as "feature1, feature2” and so on. If no feature IDs are specified, all the default features in the specified offering will be installed.

Note: Required features will be included for installation, even if they are not explicitly specified in the comma-delimited list.

The version number is not required. If no version is specified, the Installation Manager will install the most recent product with the specified id and any available updates and fixes.

The 'selected' attribute is optional. By default, 'selected' is set to "true". When 'selected' is set to "false", silent install will not install the package. While running in the wizard mode, the package will be displayed in the package selection page but not selected initially.

Update (in wizard mode)

<update>
<offering profile= "profile id">
</update>
 Use this command to specify the profile that will be updated. The profile ID must match an existing profile.
Note: This command can only be used in wizard mode to invoke 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 that will be modified. The profile ID must match an existing profile.
Note: This command can only be used in wizard mode to invoke the update wizard; it does not work in silent mode.

Modify <install modify="true"> or <uninstall modify="true"> (optional attribute)

<uninstall modify="true">
<offering profile="profile id"
 id="Id" version="Version" 
features="-"/>
</uninstall>

Use the <install modify="true"> attribute on install and uninstall commands to indicate that you want to modify an existing install. The default value is false. If the intent of the modify operation is only to install additional language packs, then a hyphen “-“ should be used in the offering feature id list to indicate that no new features are being added.

Important: You must specify modify="true" and a hyphen "-" for the features list as specified in the example; otherwise, the install command will install the offering's default features and the uninstall command will remove all of the features.

Uninstall

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

<!—add more offerings below>
<…>

</uninstall>
 Use this command to specify the packages that will be uninstalled.

The profile ID must match an existing profile or a profile specified in a profile command. In addition, if there are no feature IDs specified, then all of the features in the specified offering will be uninstalled; if there are no offering IDs specified, then all of the installed offerings in the specified profile will be uninstalled.

Rollback

<rollback>
<offering profile= "profile id"
 id= "offering id" 
version= "offering version">
</offering>

<!—add more offerings below
<…>

</rollback>
 Use this command to roll back to the specified offerings from the version that is currently installed on the specified profile. You cannot specify features in a roll back command.

InstallAll

<installALL/>
Note: This command is equivalent to using 
–silent –installAll
.
 Use this command to silently search for and install all available packages.

UpdateAll

<updateALL/>
Note: This command is equivalent to using 
–silent –updateAll
.
 Use this command to silently search for and update all available packages.

License

<license policyFile=“policy file
 location”/>

For example:

<license policyFile=”c:\mylicense.opt”/>
If your product package requires an installed license, use this command to generate a response file that contains a license command by starting the license wizard after starting Installation Manager in record mode.

During record mode, if you set flex options through the license management wizard, the options that you set will be recorded in a license policy file named “license.opt” in the same directory as the generated response file and the response file will contain a license command that references the policy file.

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 will use the repository and other preferences that are specified in the response file as well as the existing preferences that are set in the 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.

If the clean attribute is set to 'true', Installation Manager will use the repository and other preferences that are specified in the response file and the existing preferences that are set in the Installation Manager will not be used.

Temporary

<agent-input clean="true" temporary="false">
</agent-input>

By default, the temporary attribute is set to 'false' and the preferences that are set in your response file will be persisted. When you set the temporary attribute to 'true', the preferences that are set in the response file will not be persisted.

You can use the temporary and clean attributes together. For example, if you set clean to 'true' and temporary to 'false', after running the silent install the repository setting that is specified in the response file will override the preferences that were set in the previous sessions using Installation Manager.

License agreement acceptance

<agent-input acceptLicense="false">
</agent-input>

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 will fail. 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.

Reboot later

<agent-input rebootLater="false">
</agent-input>
 By default, rebootLater is set to 'false' and if the response file installs any package that requires rebooting the system on Windows, Installation Manager will reboot the system after the execution of the response file is finished.

When rebootLater is set to 'true', the system will not reboot.
Feedback