You can use an XML-based response file to specify predefined information
such as silent installation preferences, repository locations, installation
profiles, and so on. Response files are beneficial for teams and companies
that want to install installation packages silently and to standardize the
locations and preferences for installation packages.
Sample response file |
<agent-input >
<!-- add preferences -->
<preference name="com.ibm.cic.common.core.preferences. http.proxyEnabled" value="c:/temp"/>
<!-- create the profile if it doesn't exist yet -->
<profile id="my_profile" installLocation="c:/temp/my_profile"></profile>
<server>
<repository location=
"http://a.site.com/local/products/sample/20060615_1542/repository/"></repository>
/server>
<install>
<offering profile= "my_profile" features= "core" id= "ies" version= "3.2.0.20060615">
</offering>
/install>
</agent-input>
|
Additional response file attributes
You can also
define attributes for the response file: clean mode and license
agreement acceptance.
Clean mode attribute
You can apply a
clean attribute
in a response file so that the silent installation functionality will not
preserve server and preferences settings in the user interface (UI) of Installation
Manager. If you want to run in clean mode, set the following attribute to
true on
the opening response file tag:
<agent-input clean="true">
If
you set the clean attribute to
true, the silent installation
will not preserve the server preference settings; these settings only take
effect in the current setting. When you view the Installation Manager UI after
the silent install is complete, notice that the repositories and other preferences
specified in your response file are displayed on the Preferences page. These
settings will not appear if you run the silent installation in clean mode.
Note: The
clean mode attribute is designed for use during testing and debugging.
License agreement acceptance attribute
By default,
you agree to accept whatever license an installation package carries when
using Installation Manager in silent installation mode. If you do not want
to accept the license agreement, you can use an additional attribute in the <agent-input> element
that automatically fails the silent installation operation, <agent-input
acceptLicense='false">. If the installation package you are installing
has a license agreement that must be accepted, the silent installation operation
will fail.