IIP Example 2: Silently installing an existing IIP - Modifying response files at install time

This example will silently install the IIP created in "IIP Example 1: Creating and installing an IIP containing the appserver and a feature pack". You must first create an IIP like the 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.

There are two ways to silently install an IIP: run the IIP installer wizard but install the contributions silently, or run the IIP installer without the wizard and install contributions silently. This example will step through the silent installation of the IIP created in the previous example. The first approach is to install the contributions in silent mode. we need to modify the response files for both invocations. We can either create a brand new response file for each invocation, or modify the existing samples response file. In this example, you will modify existing sample response file. See Installing an IIP silently for more detailed information on how to modify a response file.

 

  1. Find the IIP created in the previous example. The directory provided in the example is /newdisk/IF.

  2. Modify the response file for the WAS CIP.

    1. The default sample response file for WAS CIP is /newdisk/IF/ifpackage/WAS/responsefile.nd.txt. Make a backup copy of the file and modify the following values:
      -OPT silentInstallLicenseAcceptance="true"
      -OPT if_cip_modifyexistinginstall="customizationAndMaintenance"
      -OPT installType="installNew"
      -OPT feature="noFeature"
      -OPT profileType="none"
      -OPT PROF_enableAdminSecurity="false"
      
      Also uncomment the following entry for non root installation:
      -OPT allowNonRootSilentInstall=”true”
      

    2. Copy the modified response file to /newdisk/IF/iip/responsefile.nd.txt.

  3. Modify the response file for the Feature Pack for Web Services CIP.

    1. : The default sample response file for the feature pack CIP is /newdisk/IF/wsif/WEBSV/responsefile.WEBSV.txt. Make a backup copy of the file and modify the following values:
      -OPT silentInstallLicenseAcceptance="true"
      -OPT if_cip_modifyexistinginstall="customizationAndMaintenance"
      -OPT installType="installNew"
      -OPT PROF_enableAdminSecurity="false"
      
      Also uncomment the following entry for non root installation:
      -OPT allowNonRootSilentInstall=”true”
      
      If a standalone profile is to be created as part of the install, use the following options:
      -OPT createProfile="true"
      -OPT profileType="standAlone"
      

      Find the stand alone appserver profile section and fill out the required names and values for the new profile.

    2. Copy the modified response file to /newdisk/IF/iip/responsefile.WEBSV.txt.

  4. Launch the IIP installation wizard. Change the current directory to /newdisk/IF/iip/bin, and launch the IIP installer in GUI mode by executing the install.sh command. We omitted the –iipUserType parameter in the command because by default the user is set to root. Click Next on the Welcome panel.

  5. Specify the installation locations for the two contributions. We might notice that the installation locations were not specified in the response files. You will set the installation locations here in the IIP installation wizard. Alternatively, the installation locations could have been specified in the response files and omitted from the IIP installer wizard. The values could be specified in both places, in which case the one in the wizard will be used instead of the one in the response files. Since we are going to install the invocations in silent mode, we also need to specify the location of the response files.

    1. Highlight the first invocation (WAS CIP), and click Modify.

    2. On the Modify Installer Properties panel, select Silent installation (requires a response file) to indicate this invocation will be invoked in silent mode. This will override the interactive mode set during the IIP creation time. we are able to do this because one of the options selected during the creation of this CIP was to allow users to override the installation mode.

    3. Specify the installation location of the WAS CIP to /opt/IBM/WebSphere/AppServer2 and specify the file name and path of the response file to/newdisk/IF/iip/responsefile.nd.txt. Click OK.

    4. Highlight the second invocation (Feature Pack for Web Services CIP), and click Modify.

    5. Select Silent installation (requires a response file). Keep the default installation directory path as $RESV{6.1.0-WS-WASND_1-1:installLocation}. This macro will ensure that Feature Pack for Web Services CIP will be installed in the same location as invocation 6.1.0-WS-WASND_1-1, the WebSphere Application Server CIP. Specify the response file name and path to /newdisk/IF/iip/responsefile.WEBSV.txt and click OK.

  6. Click Install to start the installation. The IIP installer will install both contributions in silent mode using the install location and response file values you entered in the previous steps.

  7. When both contributions have installed successfully, click Finish to exit the IIP installation wizard.

  8. Verify the installation

    1. Verify WAS version using the versionInfo command which can be found in the /newdisk/IBM/WebSphere/AppServer/bin directory. You should find both WAS and Feature Pack for Web Services are installed at the 6.1.0.16 level.

    2. To view interim fixes that are installed, use the ./versionInfo.sh –long > version_long.txt. You should find that interim fixes for both the WebSphere Application Server and feature pack products have been installed.

    3. We can also review the logs for each product in the /newdisk/IBM/WebSphere/AppServer/logs directory.

 

Results

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_directory>/iip. For detailed information on installing silently see Installing an IIP silently.

  1. The default sample response file is located in/newdisk/IF/iip. Make a backup copy of the file and modify the following values, substituting your own value for the appserver CIP install location. Do not modify the second install location which is associated with the feature pack CIP. Note that we are still using the contribution response files created in steps 2 and 3.
    -iipNoGUI
    -iipOptionSet=6.1.0-WS-WASND_1-1
    -OPT installLocation=/opt/IBM/WebSphere/AppServer3
    -options /newdisk/IF/iip/responsefile.nd.txt
    -silent
    -iipOptionSet=6.1.0-WS-WASWS_1-1
    -OPT installLocation=$RESV{6.1.0-WS-WASND_1-1:installLocation}
    -options /newdisk/IF/iip/responsefile.WEBSV.txt
    -silent
    

  2. Change directories to /newdisk/IF/iip/bin and run the installer using the following command, substituting the name of the response file you edited and saved:
    ./install.sh –iipResponseFile=/newdisk/IF/iip/responsefile.iip.txt
    

  3. After a few minutes both contributions are installed silently. Verify the installation following step 8.

 

Next steps

Review the other two IIP examples for more information on IIP creation and installation. 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