IIP Example 3: Silently installing an existing IIP - Modifying response files during IIP creation

This example shows how to modify the build definition file created for the IIP from "IIP Example 1: Creating and installing an IIP containing the appserver and a feature pack". Response files are added to each contribution during creation time and the IIP is installed silently. You must first create an IIP like one from "IIP Example 1: Creating and installing an IIP containing the appserver and a feature pack". This example will reuse certain files and values from that example.

In "Example 2: Silently installing an existing IIP - Modifying response files at install time", you were able to modify the installation mode of the IIP because the setting which allows users to override the installation mode was chosen during IIP creation. Like Example 2, this example will modify the IIP created in the first example, but the response files will be specified at creation time and not during install time.


  1. Launch the Installation Factory in GUI mode using the IF_home\bin\ifgui.sh script. Click Open Build Definition.

  2. On the Modify Existing Build Definition panel, click Browse and select the com.ibm.sampiip. created in Example 1.

  3. The Build Definition Wizard is displayed. Click Next on the Mode selection panel, Package Identification panel, Build Information panel, and Integrated Installation Wizard Settings panel, since we are not going to leave the default values for these settings.

  4. On the Construct Integrated Installation Package panel, highlight the appserver invocation in the Installation Package Invocations field and click Modify.

  5. On the Installation Package Properties panel, select the Silent installation (Requires Response File) radio button and click the Response Files tab. Highlight the non-root response item in the table and click Modify.

  6. On the Modify Default Silent Installation Response File panel, Click Browse to select the response file you want to include for this CIP being installed as a non-root user. Usually the response file you want to choose is the one already inside the CIP directory structure. Note that during IIP creation time, the response file you input in the Directory path and file name of the default silent installation response file field will be copied to a location relative to the IIP. For example, because we are specifying a response file for this invocation for a non-root user, it will be copied to IIP_root/ResponseFiles/6.1.0-WS-WASND_1- 1/LinuxX32/nonRoot/responsefile.nd.txt. This will be the response file that should be edited later by the installing user at install time if changes are necessary. The original response file for the CIP is left untouched in the CIP. Click OK.

    The installation location in the response file has a lower priority than one specified at install time. Because you specified during IIP creation in Example 1 that users installing this IIP can override certain values like the install location, installing users can specify the installation location in the installation wizard. In this case, we can safely remove the installation location parameter in the response file if you wish since it will be specified at install time.

  7. Repeat the same step for a root user in case users want to perform a root installation.

  8. On the Installation Package Properties panel, click OK. we have now specified a response file for both root and non-root users.

  9. On the Construct Integrated Installation Package panel, repeat steps 4-8 for the feature pack CIP.

  10. Once all four response files have been specified for the invocations, click Next on the Construct Integrated Installation Package panel and all following panels until the Summary panel.

  11. On the Integrated Installation Package Preview panel, click Save build definition file and generate integrated installation package. Click Finish.

  12. Once the IIP is successfully generated, you will see that the response files are copied into the /newdisk/IF/iip/ResponseFiles directory. Feel free to modify these response files if needed.

  13. Launch the IIP installer wizard from/newdisk/IF/iip/bin using the install.sh command.

  14. Click Next on the Welcome panel. On the Installation Selection panel, select an install location for the application server CIP. You do not need to fill in an install location value for the feature pack CIP because it will automatically use the appserver location when it installs. The IIP installer will install both invocations in silent mode.

  15. Verify the installation using the /bin/versioninfo command.



Both the appserver and the feature pack contributions were installed silently using the IIP installation wizard.

A second approach is to run the IIP installation silently in addition to the contributions in a completely automated installation. To run the IIP installation silently, we can use a response file or provide the installation options on the command line. Using an IIP response file makes the invocation simpler and more repeatable compared to providing options on the command line. There is a sample IIP response file created for each IIP located at <IIP_root>/iip. For detailed information on installing silently see Installing an IIP silently.


Next steps

Review the two other IIP examples to learn more about creating and installing IIPs. The complete IIP sample guide is available on the Installation Factory web site at
IBM Installation Factory for WAS V6.1 for Windows.

Related concepts

Related tasks

Related reference

Related information


Last updated Nov 11, 2010 1:01:09 PM CST