09 June, 2011

Installing Rational Automation Framework for WebSphere and Rational Build Forge checklist

This checklist with the installation sequence for Rational Automation Framework for WebSphere (RAFW) and Rational Build Forge was copied from the following link:

https://www-304.ibm.com/support/docview.wss?uid=swg21386782&wv=1


  1. Update IBM Installation Manager:

    Open Installation Manager and select the Update option.

    Note: If you update Installation Manager as a part of installing Rational Build Forge, the RAFW_ENABLED variable is ignored.
  2. Obtain the Rational Build Forge 7.1.1 product installation images:

    At the root directory of the installation media or the downloaded images, locate thereadme.txt file.

    You must follow the instructions in the readme.txt file to create a complete product image:
    1. Download the images to a temp directory.
    2. Locate the ZIP files for your edition of Rational Build Forge.
    3. Download first and second ZIP files to a temp directory.
    4. Unzip the contents of the first ZIP file and second ZIP files to the temp directory.
  3. From the temp directory, open a shell or command prompt. Set theRAFW_ENABLED=yes environment variable for your operating system, for example:

    Windows example:
    ------------------
    C:\temp> set RAFW_ENABLED=yes

    UNIX/Linux example:
    ---------------------
    $ /tmp export RAFW_ENABLED=yes
  4. At the same shell or command prompt, start the launchpad program and Installation Manager, for example:

    Windows example:
    ------------------
    C:\temp>launchpad.exe

    UNIX/Linux example:
    ---------------------
    $ /tmp launcher
  5. When the launchpad program opens, select Rational Build Forge Management Console Installation option to start Installation Manager and install the Rational Build Forge components.
  6. After Rational Build Forge installation completes, in the Rational Automation Framework for WebSphere Information Center, complete the setup detailed in the the Post-installation setup section. 

No comments: