Creating a local mirror of the IBM Rational Performance Tester update server

For Rational Performance Tester, Version 6.1

This file is available in the following national languages:

Brazilian Portuguese	Chinese - Simplified	Chinese - Traditional
French	German	Italian
Japanese	Korean	Spanish

Contents

1.0 Downloading and extracting updates

To create a local mirror of the IBM Rational Performance Tester update server, download the following updates. If you previously created a local mirror of the update server, remove any outdated feature files before downloading these updates.

After you download the updates, extract the files to a target directory that will stage your local mirror of the update server. You can extract all the updates to the same target directory. The updates do not overwrite each other.

Attention:

• You must download the IBM Rational Product Updater 6.0.0.4.
• You must remove outdated feature files from your local mirror of the update server.

2.0 Creating and updating site.xml files

Generally, an update site and a discovery site exist for each product. The update site contains product fixes, such as interim fixes and fix packs, and the discovery site contains optional features.

Note: There is no discovery site for the Rational Product Updater or Rational Performance Tester 6.1.1.

Each downloaded product fix contains a site_identifier.xml file in the product\61\update\ directory, and each downloaded feature contains a site_identifier.xml file in the product\61\discovery\ directory, where identifier identifies the product fix or feature and product identifies the product. The site_identifier.xml files for updates to the Rational Product Updater are located in the rpu\60\update\ directory.

The update site and the discovery site each require a separate site.xml file. To create each site.xml file, you must combine the <feature/> information from the appropriate site_identifier.xml files.

To create or update a site.xml file, complete the following steps:

1. Open a site_identifier.xml file in a text editor. For example, open site_611.xml.
2. Save the file as site.xml in the same directory. If the directory already contains a file named site.xml, copy the <feature/> information from site_611.xml into the <site></site> section of site.xml.
3. Copy the <feature/> information from each site_identifier.xml file into site.xml.

Your rpt\61\update\site.xml will look similar to the following:

<?xml version="1.0" encoding="UTF-8" ?>
<site>
   <feature patch="false"
      id="com.ibm.rational.performance.tester.611" version="1.0.0"
      url="features/com.ibm.rational.performance.tester.611_1.0.0.jar"/>
   <feature
      id="updater.rpt.common.plugins.611" version="1.0.0"
      url="features/updater.rpt.common.plugins.611_1.0.0.jar"/>
   <feature
      id="updater.rpt.common.wb.plugins.611" version="1.0.0"
      url="features/updater.rpt.common.wb.plugins.611_1.0.0.jar"/>
   <feature
      id="updater.rpt.common.nl.plugins.611" version="1.0.0"
      url="features/updater.rpt.common.nl.plugins.611_1.0.0.jar"/>
   <feature
      id="updater.rpt.common.doc.plugins.611" version="1.0.0"
      url="features/updater.rpt.common.doc.plugins.611_1.0.0.jar"/>
</site>

3.0 Creating a policy.xml file

Each downloaded product fix and feature contains a product\policy_identifier.xml file that references its site_identifier.xml file. You must combine all of the policy_identifier.xml files into a single policy.xml file and edit the URL maps. After you create this file, you can use it for all product updates and reference the site.xml file that you created in the previous section.

To create the policy.xml file, complete the following steps:

1. Open a product\policy_identifier.xml file with a text editor. For example, open policy_611.xml.
2. In the main directory of your mirror site, save the file as policy.xml.
3. Edit the URL map to point to site.xml instead of site_identifier.xml. Ensure that you specify a universally accessible absolute path to site.xml. For example, if your mirror site is on a Web server named server1, your policy.xml file will be similar to the following example:


<?xml version="1.0" encoding="UTF-8" ?>
<update-policy>
   <url-map pattern="com.ibm.rational.performance.tester.update" url="http://server1/rational_updates/rpt/61/update/site.xml/">
</update-policy>


4. Add the URL map information from all other product\policy_identifier.xml files, such as rsa\policy_wbi_6001.xml.


For each product that you can update from your local mirror of the update server, you should have one URL map for the update site and another URL map for the discovery site. Additional URL maps are required for feature discovery sites. The patterns are provided in each product\policy_identifier.xml file.


5. Edit each URL map to point to site.xml instead of site_identifier.xml. Your file will be similar to the following example:


<?xml version="1.0" encoding="UTF-8" ?>
<update-policy>
   <url-map pattern="com.ibm.rational.performance.tester.update" url="http://server1/rational_updates/rpt/61/update/site.xml/">
   <url-map pattern="com.ibm.rational.software.architect.discovery" url="http://server1/rational_updates/rsa/60/discovery/site.xml/">
   <url-map pattern="com.ibm.rational.wbi.rsa" url="http://server1/rational_updates/rsa/60/discovery/site.xml/">
</update-policy>


6. Create a URL map for the updates to the Rational Product Updater by typing a universally accessible absolute path to its site.xml file.


<url-map pattern="com.ibm.orca.product.updater" url="http://server1/rational_updates/rpu/60/update/site.xml"/>


7. Save the policy.xml file.

4.0 Installing updates from the local mirror of the update server

After the local mirror of the update server is available, users can install updates by completing the following instructions.

Install updates with the same user account that installed Rational Performance Tester.

Restrictions:

• Rational Performance Tester cannot be open when you install an update.
• On Windows^® operating systems, you must use an account with Administrator privileges. On Linux^® operating systems, you must use the root user account.

To install an update, complete the following steps:

1. Start the Rational Product Updater:
   • On Windows operating systems, click Start > Programs > IBM Rational > Rational Product Updater.
   • On Red Hat Enterprise Linux 3.0 (GNOME desktop environment), open the main menu and click Programming > Rational Product Updater.
   • On SuSE Linux Enterprise Server 9.0 (K Desktop Environment), open the main menu and click IBM Rational > Rational Product Updater.

Note: On Red Hat Enterprise Linux 3.0 and SuSE Linux Enterprise Server 9.0, if you use a desktop environment other than the default, the product shortcuts might not appear in the default location. In this case, you can start Rational Product Updater by running install_dir/updater/eclipse/rpu.exe on Windows, and running install_dir/updater/eclipse/rpu on Linux.


2. Click Preferences > Update Sites.
3. Type the path to the policy.xml file that is in the main directory of the local mirror of the update server.
4. Click OK.
5. Click Find Updates or Find Optional Features.


If the Rational Product Updater requires an update, you are prompted to install it before you can continue. Click OK. The Rational Product Updater installs the update, restarts, and retrieves a list of available updates.


6. Select the update that you want to install.


Tip: To view the description for an update, click the update. The description is displayed in the Detailed information pane.


7. Click Install Updates or Install Optional Features.
8. Review and accept the license agreement and continue the installation by clicking OK.


Depending on the speed of your computer processor and the amount of RAM in your computer, the update might take an extended period of time to install.

After the installation is complete, the Rational Product Updater lists the installed updates on the Installed Products page.


9. Close the Rational Product Updater.

Note: An active z/OS Rational Agent Controller process will not be updated. z/OS RAC must be restarted to ensure the updates are available.