Creating you first response file

A response file can be prepared in a number of ways:

  1. Have a completed response file with all fields manually filled in and enter the path in the task.
  2. Have a response file pre-filled in with Tokens for all the variables, with this approach the response file just be contained within the package. Tokens are in the form of @@install_path@@ and will be replaced from the data dictionary during deployment time. The plugin provides a sample response file to help you get started.
  3. Use variables in your response file (new in IBMIM 1.72) and add these variables to the orchestration task as resources, this allows you to keep a response file in a shared directory and the variables will be replaced at run time. If using variables you must use the following supported variable names only:

To use variables tag in the response file to declare the variables you wish to use in the orchestration task, remember you must use the predefined naming.


<variable name='was_installPath' />

<variable name='portal_profile' />

<variable name='portal_installtype' />


Once added to the variables tag then these must also be set as follows in the response file.:

<data key='user.was.installLocation,' value='$was_installPath'/>

<data key='user.profile.config.mode,' value='$portal_profile'/>

<data key='user.wp.install.type,' value='$portal_installtype'/>

This response file can now be added to you package or referenced from a shared location buy all similar installments and you only ever need to worry about updating the correct fields in the tempalte form and RapidDeploy will take care of the rest.

For more information on IIM response files please referee to IBM documentation on this.