Question & Answer
Question
How can I update IBM® Rational® ClearCase® Remote Client (CCRC) using the Eclipse™ Update Policy Control?
Answer
The ClearCase Remote Client (CCRC) uses Eclipse Update technology to search for and install updated versions of the CCRC software. This capability is available in both the stand-alone and Eclipse IDE versions of CCRC.
CCRC contains a default embedded URL that is used to connect to a remote public IBM server to obtain updates. Some organizations may prefer to provide local control over updates for reasons including bandwidth limitations, firewall restrictions, or the requirement for internal quality testing prior to deployment. Use of the Eclipse Update Policy Control provides local sites the ability to manage your CCRC updates.
For more information, see the topic Eclipse Update Policy Control in Eclipse help.
Allocate space on an HTTP server for the CCRC bits
Set up an update policy file on the web server
Set the Update Policy Preference
Set the Automatic Updates Preference
These steps will allow your organization to enforce local update policies for CCRC updates using the Eclipse Update Policy Control.
IMPORTANT: These instructions apply to "updating" a client release within a single release of ClearCase (for example updating version 6.14.x for access to ClearCase servers 2003.06.14 or later). These are not instructions for "upgrading" between versions (for example client version 6.14.x to 7.0 or from "upgrading" from 7.0 (7.0.1.CU03 Build id: BALTIC_CCRC_UPDATE.D070327) to 7.0.1 (7.0.1.D061004 Build id: BALTIC_MR1.D070516)
Step 1: Allocate space on an HTTP server for the CCRC bits
As IBM provides updates and fixes on the ibm.com site, you then download those updates onto your local server.
Download the file ccrc_update_site_<version number>.zip. When you are ready to deploy the update to your organization, unzip the file to the space you allocated on your local server.
Note: You may use an existing RWP server with ClearCase installed which has a default location allocated to contain the CCRC download bits (Windows: C:\Program Files\Rational\ClearCase\web\update -- Linux/UNIX: /opt/rational/clearcase/web/update).
Example:
In this example, the Rational Web Platform (RWP) server is named RWP-Server_1 will be used. The new CCRC download bits have been added to this server and can be accessed using the following URL: http://RWP-Server_1/ccrc/update
Step 2: Set up an update policy file on the web server
In the space allocated on your web server, create a file named ccrc_policy.xml.
Populate the ccrc_policy.xml file with the following content:
<?xml version="1.0" encoding="UTF-8"?> <update-policy> <url-map pattern="com.ibm.rational.clearcase" url="local_url"/> </update-policy> |
Example:
Continuing with the example from step 1, the url="local_url" would be set to the following URL:
http://RWP-Server_1/ccrc/update
Instruct users to set the Update Policy preference, and optionally the Automatic Updates preference in their CCRC clients.
Step 1: Set the Update Policy Preference
From the Rational Software Development Platform, Eclipse, or the stand-alone ClearCase Remote Client, click Window > Preferences and then select Install/Update.
In the Update Policy section, specify as the Policy URL: <local_url>/ccrc_policy.xml, and apply the change.
Example:
Continuing with the example, the Policy URL would look as follows:
Note: This policy URL will override the URL that is embedded in CCRC. CCRC will now only check for updates as instructed by your local update policy.
Optional: Set the Automatic Updates Preference
From the Rational Software Development Platform, Eclipse, or the stand-alone ClearCase Remote Client, click Window > Preferences and then select Install/Update > Automatic Updates.
Have your clients configure the Automatic Updates Preference to control how you wish to have clients receive and apply updates to CCRC and apply the changes.
Rational Software Development Platform preferences and Eclipse preferences are stored on a per-workspace basis, so the Update Policy Preference needs to be set each time a new workspace is created. Here is an alternative for system administrators who install the product for their users.
Edit the file plugin_customization.ini which is stored in the primary product plug-in and set the default value of the updatePolicyURL property as follows:
org.eclipse.update.core/updatePolicyURL=<local_url>/ccrc_policy.xmlWhere <local_url> is the location on the web server where the new updates will be made available.
Example:
Continuing with the example from step 1, the <local_url> would be set to the following URL:
http://RWP-Server_1/ccrc/update
If you are using Rational Software Development Platform or Eclipse, the primary product plug-in is org.eclipse.platform.
Related Information
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21196280