Creating a local mirror of the IBM Rational Application Developer update server

For Rational Application Developer, Version 6.0

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^® Application Developer 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.

Attention: You must download IBM Rational Product Updater 6.0.1.

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.

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, fix packs, and refresh packs, and the discovery site contains optional features.

Note: Rational Product Updater does not have a discovery site.

Each downloaded product fix contains a site_identifier.xml file in the product\60\update\ directory, and each downloaded feature contains a site_identifier.xml file in the product\60\discovery\ directory, where identifier identifies the product fix or feature and product identifies the product. The site_identifier.xml files for updates to 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_60_6011.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_60_6011.xml into the <site></site> section of site.xml.
3. Copy the <feature/> information from each site_identifier.xml file into site.xml.


For example, the following code displays the result of copying the <feature/> information from rad\60\discovery\site_601_J2C6012.xml and rad\60\discovery\site_i4gl.xml into rad\60\discovery\site.xml:

<?xml version="1.0" encoding="UTF-8" ?>
<site>
<!-- J2C refresh feature-->
<feature id="com.ibm.j2c.win32" os="win32" patch="false" url="features/com.ibm.j2c.win32_6.0.1.2.jar" version="6.0.1.2"> <category name="refreshpack"/>
</feature>
<feature id="com.ibm.j2c.linux" os="linux" patch="false" url="features/com.ibm.j2c.linux_6.0.1.2.jar" version="6.0.1.2"> <category name="refreshpack"/>
</feature>
<feature id="updater.j2c.nl1.plugins.601" patch="false" url="features/updater.j2c.nl1.plugins.601_1.0.0.jar" version="1.0.0"> <category name="proxies"/>
</feature>
<feature id="updater.j2c.plugins.601" patch="false" url="features/updater.j2c.plugins.601_1.0.0.jar" version="1.0.0"> <category name="proxies"/>
</feature>
<feature id="updater.j2c.resource.adapters" patch="false" url="features/updater.j2c.resource.adapters_1.0.0.jar" version="1.0.0"> <category name="proxies"/>
</feature>
<feature id="updater.j2c.linux.permissions" patch="false" url="features/updater.j2c.linux.permissions_1.0.0.jar" version="1.0.0"> <category name="proxies"/>
</feature>

<!--I4GL conversion utility-->
<feature patch="false" id="com.ibm.etools.i4gl.conversion.refresh.win32" version="6.0.0.1a" url="features/com.ibm.etools.i4gl.conversion.refresh.win32_6.0.0.1a.jar" os="win32">
</feature>

<feature patch="false" id="com.ibm.etools.i4gl.conversion.refresh.linux" version="6.0.0.1a" url="features/com.ibm.etools.i4gl.conversion.refresh.linux_6.0.0.1a.jar" os="linux">
</feature>

<feature patch="false" id="updater.rad.ifeature.i4glconversion.refresh.001" version="1.0.0" url="features/updater.rad.ifeature.i4glconversion.refresh.001_1.0.0.jar">
</feature>

<feature patch="false" id="updater.zips.i4glconversion.refresh.win32.001" version="1.0.0" url="features/updater.zips.i4glconversion.refresh.win32.001_1.0.0.jar">
</feature>

<feature patch="false" id="updater.zips.i4glconversion.refresh.linux.001" version="1.0.0" url="features/updater.zips.i4glconversion.refresh.linux.001_1.0.0.jar">
</feature>

</site>

Note:
• Replace outdated feature information in the product\60\discovery\site.xml file with the latest feature information that is available.
• Do not replace the previous feature information in the product\60\update\site.xml file with the latest product fix information that is available.
• The order of the feature information is not significant.


4. Save and close the updated site.xml file. Keep the original site_identifier.xml files for reference.
5. Close your text editor.

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. 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_60_6011.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.application.developer.update" url="http://server1/rational_updates/rad/60/update/site.xml"/>
</update-policy>


4. Add the URL map information from all other product\policy_identifier.xml files, such as rad\policy_j2c_601.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.application.developer.update" url="http://server1/rational_updates/rad/60/update/site.xml"/>
   <url-map pattern="com.ibm.rational.application.developer.discovery" url="http://server1/rational_updates/rad/60/discovery/site.xml"/>
</update-policy>


6. Create a URL map for the updates to 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.
8. Close your text editor.

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 the product.

Restrictions:

• The product 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 log in as root.

To install an update, complete the following steps:

1. Start 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.


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 Rational Product Updater requires an update, you are prompted to install it before you can continue. Click OK. Rational Product Updater installs the update, restarts, and retrieves a list of available updates.


6. Select the update that you want to install.
7. Click Install Updates or Install Optional Features.
8. To accept the license agreement and continue the installation, click 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, Rational Product Updater lists the installed updates on the Installed Products page.


9. Close Rational Product Updater.