Using the Rational Test Lab Manager samples

In addition to the normal Build Forge® administration, you will need to follow these instructions to make the automation projects for Rational® Performance Tester and Rational Service Tester for SOA Quality usable with Rational Test Lab Manager.

Before you begin

All the projects and libraries use the installrpt or install-linux environment file. Review each variable in this file and ensure that it makes sense for the response files that you use.

Procedure

  1. Designate a Build Forge server to host the automation projects response files, etc. Name this server RPTFILESERVER and ensure that it has .get access. The automation scripts search this server for the Installation Manager response files.
  2. Unzip install_dir\RPT-RST_RQMAdapter\rtlm_buildforge\RPT-RST_RTLM_Samples.zip and copy the FILEROOT directory onto the server RPTFILESERVER. Place the automation artifacts in the directory rpt-response-dir, beneath directory BF_ROOT.
  3. For every Build Forge agent to be used, install the Installation Manager to the location im-install-dir. This automation is not provided in the Rational Performance Tester or Rational Service Tester for SOA Quality samples.
  4. Change each install response file to point to either:
    • Your Installation Manager remote repository, such as repository location='http://mysite/repo', or
    • The location of the installation images, possibly on the local network, such as repository location='\\localhost\linuxtemp\RPT_8.1\disk1'.
  5. Import the Build Forge samples:
    1. Locate the bfimport.exe command located in the Build Forge server install.
    2. Copy all the *.xml and import.bat files from the extracted RPT-RST_RTLM_Samples.zip into the same directory as bfimport.exe.
    3. Run import.bat
    4. Delete the *.xml and import.bat files.
    All samples are now available through the Build Forge management console.
  6. Set up a Build Forge agent computer. This is the machine where the automation will occur. On Windows®, make sure it has enough disk space on C: to handle RPT installs. On Linux®, use the RPM to install the Build Forge agent. The automation scripts require that the Installation Manager is installed at a specific location, therefore you might need to uninstall the Installation Manager beforehand.
    1. Install the Build Forge agent.
    2. Create a directory to serve as the Build Forge root directory, for example: C:\Builds or /bfroot.
    3. On the Build Forge server, set up a server authentication that contains the credentials to log onto this agent.
    4. On the Build Forge server, setup and test the server connection.
    5. Install the Installation Manager to the directory specified by im-install-dir, for example: C:\Program Files\InstallationManager\eclipse.
    6. Follow the instructions in the Build Forge document on setting up Linux agent, specifically if your system uses pam.d.
  7. Set up the Build Forge source server agent. The automation scripts use the environment installrpt on Windows and installrpt-linux on Linux. Review the variables defined in these environments and set as appropriate for your automation needs. See Variables for installrpt environment files for reference information about each variable.

What to do next

Determine which sample project to run on the Build Forge agent. Modify the variables used by that project appropriately and run the project via the lab management functions of Rational Quality Manager. See the Build Forge information center for information about running scripts on remote lab resources.

Feedback