Response file commands | Description |
---|---|
Set profile <profile id="the profile id" installLocation="the install location of the profile"> <data key="key1" value=”value1”/> <data key="key2" value=”value2”/> </profile> |
Use this command to create an installation location. If the specified
installation location already exists, the command has no effect. Currently,
when creating the profile, the silent installation will also create two installation
contexts; one for Eclipse and one for native.
A profile is an installation location. You can use the <data> element for setting profile properties. The following list contains the keys
currently supported keys and related values:
Note: Separate multiple NL values with commas.
The following
list contains the currently supported language codes:
|
Set repositories <server> <repository location="http://xxx/repository/"> <repository location=”file:/C:/repository/”> <!—add more repositories below--> <…> </server> |
Use this command to specify the repositories used during silent installation. Use a URL or UNC path to specify remote repositories; use directory paths to specify local repositories. |
Install <install> <offering profile= "profile id" features= "feature ids" id= "offering id" version= "offering version"></offering> <!—add more offerings below> <…> </install> <install modify="true">(optional attribute) |
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.
|
<install modify="true">or <uninstall modify="true"> (optional attribute) <uninstall modify="true"> <offering profile="profileID" 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. If the attribute is not set to true, the value defaults to 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 no new features are being added. Important: You must specify "modify=true" and
a hyphen "-" feature list as specified in the example;
otherwise, the install command will install the offering's default features
and the uninstall command will remove all 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 installation packages that will be
uninstalled. The profile ID must match an existing profile or a profile specified in a profile command. Further, if there are no feature IDs specified, all the features in the specified offering will be uninstalled; if there are no offering IDs specified, all 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 rollback to the specified offerings from the version currently installed on the specified profile. You cannot specify features in a rollback command. |
InstallAll <installALL/> Note: This
command is equivalent to using
–silent –installAll. |
Use this command to silently search for and install all available installable packages. |
UpdateAll <updateALL/> Note: This
command is equivalent to using
–silent –updateAll. |
Use this command to silently search for and update all available installable packages. |
License <license policyFile=“policy file location”/> For example: <license policyFile=”c:\mylicense.opt”/> |
Use this command to generate a response file containing 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 you set will be recorded in a license policy file named “license.opt” in the same directory as the generated response file; the response file will contain a license command that references the policy file. |
Wizard <launcher -mode wizard -input < response file > |
Use this command to start Installation Manager in UI mode. The UI mode starts Installation Manager in either the install wizard or the uninstall wizard. However, in this case, the response file can only contain preference commands and install commands or preference command and uninstall commands; you can not mix install and uninstall commands in the same response file when you run Installation Manager in UI mode. |