dmmckinn 1200006SCS Visits (1574)
Guidance for deploying Rational Team Concert into an existing Rational ClearCase environment
IBM Rational Team Concert (RTC) provides various types of integration capabilities: the synchronizer, the importer, and the bridge. The integration is not a one-size-fits-all and you may need help with deciding which integration capability best suits your current deployment or your future deployment plan. The information below provides a brief overview about the integration capabilities. Additional "Getting Started" information and "Quick Tour" videos are available in the Rational Team Concert and Rational ClearCase integration cookbook topic in the deployment wiki on Jazz.net.
Rational ClearCase Bridge
The Rational ClearCase Bridge provides a traceability link from Rational ClearCase artifacts to work items in Rational Team Concert. This is primarily for a customer who wants to continue to use Rational ClearCase as a source control system, but also wants to take advantage of Rational Team Concert features such as agile planning, dashboards, etc. You do not have to change your current usage of Rational ClearCase, but you can enhance your Rational ClearCase deployment by using Rational Team Concert in a complementary fashion.
Developers can associate UCM activities or base Rational ClearCase versions to Rational Team Concert's work items. You can then navigate from one to the other in the developer IDE. Because a Rational Team Concert work item is used as the "glue" for all development lifecycle artifacts, it provides end-to-end traceability throughout the development life-cycle, from project planning to source code changes.
Rational ClearCase Version Importer
The Rational ClearCase Version Importer (new in Rational Team Concert 4.0.5) is a one-way data replication tool from Rational ClearCase to Rational Team Concert source control. You can migrate all the versions in any branches in Rational ClearCase in a single operation, and the version branching is also replicated in Rational Team Concert source control. The importer also preserves the checked-in user information.
It can also import Rational ClearCase view configurations as Rational Team Concert baselines since the version 4.0.6.
You can use the version importer for both Base ClearCase and UCM ClearCase, but it does not import UCM metadata.
Rational ClearCase Synchronizer and Baseline Importer
The Rational ClearCase Synchronizer is a two-way data replication between Rational ClearCase and Rational Team Concert source control. You can choose a UCM stream or a Rational ClearCase branch to set up synchronization with a stream of Rational Team Concert source control. It leverages the Jazz Team Build, and you can run the synchronization on a scheduled basis or by request. This provides flexibility to enterprise customers by allowing a subset of teams to choose SCM tools to work with, while letting you manage all of the latest source code through a single SCM repository.
The Rational ClearCase Baseline Importer is a one-way data replication from Rational ClearCase to Rational Team Concert source control. Like the synchronizer, you can choose a UCM stream where all baselines or only selected baselines are imported, or you can choose to import label types for base Rational ClearCase. It also leverages the Jazz Team Build, so you can run the import of new baselines/label types on a scheduled basis or by request.
Version Importer or Baseline Importer?
There are two migration tools available - the Version Importer and the Baseline Importer. You can choose either of the technology that fits to your requirements to migrate the data from Rational ClearCase to Rational Team Concert source control.
AcdntlPoet 2700019V2G Visits (1727)
Rational DOORS Next Gen: Creating a Requirements Management Project from a Template- In this video we are creating a new requirements management project from a template; more specifically the Automated Meter Reader Sample template that comes with IBM® Rational® DOORS Next Generation.
Saurabh.Tyagi 270005CY2K Visits (1807)
I am sure you have seen multiple download buttons after adding Rational Tokens to existing Token server using the License Key Center, wondering why – please find the details below.
IBM Rational License Key Center captures the activity with the date history. When more tokens are added to the existing server on different intervals, Rational License Key Center records the number of Tokens assigned to the server and the date when it was generated.
This helps you to determine the total number of token to be used during the import of the license key on the server.
For Example: Screen shot 1 will show you how the download page looks on license key center when initially100 Tokens are generated for a given server on the July 3rd 2014.
Now, as and when the requirement for Tokens increases the License key center administrator logs in to the center to add more Tokens
Example: 100 more on a 8th of July, I see 2 download buttons.
What is important here is the date that the key center captures to maintain history of number of Tokens used on different dates. So on the July 8th the license key was generated for 200 Tokens irrespective of which Download button you choose.
Note: The license keys get appended when more tokens are added to the existing server, so ideally there is no difference in quantity between the two download buttons.
Author: Saurabh Tyagi, co-author Edwin Premnath
AcdntlPoet 2700019V2G Visits (1618)
IBM UrbanCode Deploy with Patterns 10 Minute Demo- Senior Technical Staff Member, Michael elder talks about integrating UrbanCode Deploy with your cloud and virtualization environments. Learn more at: http
Saurabh.Tyagi 270005CY2K Visits (1785)
When you renew support for the certain rational products listed below, the order will not flow in to rational license key center, instead the PA (Passport Advantage) website would get updated with the latest software versions.
The reason for these products not to flow into LKC (license key center) is because they work on version based concept. What is a version based concept? It is products which are designed to work without the maintenance expiry date in the license file.
For Example: Here is a “version based license”. You have a permanent license key with no maintenance expiration date.
INCREMENT ClearQuest rational 1.10000 permanent 32 EB37995684D9 \
Hence the latest maintenance renewal will not appear in the license file.
Below are the list of Rational product that flow into the License key Center after support renewal are:
The above products work on “date based concept” where it is mandatory to have the latest maintenance end date to appear in the license file.
A date based license key has the Subscription and Support (S&S) end date built-in as the license key version.
For example: 2010.1231 is Dec 31, 2010, the end date of your current S&S. The license key is used with any software version released before the end date of the built-in license version (S&S end date). To use any newer release, the license key must be updated with new S&S orders for each period of renewal.
When receiving your S&S renewal email, you must enter the IBM License Key Center and upgrade your license key using your S&S Renewal Order. Most date based licenses can be used for earlier versions as long as nothing else has changed, like FEATURE, INCREMENT, and so on.
Here is an example of a date based license. You have permanent license key with the maintenance expiration date of January 31, 2012.
INCREMENT DOORS telelogic 2012.0131 permanent 6 40C0
This key will work for any product software versions released on or before January 31, 2012. If you intend to use a product version released after January 31, 2012, you must purchase and apply a Renewal Order to the existing license file. This can only be done through the License Key Center.
If your license key expiration is permanent, you can use the keys permanently. However, it might be limited to versions with corresponding valid S&S renewal dates.
Note: The original License Order and Associated Renewal Order have to be registered on the same IBM Site ID. To apply the renewal order and upgrade the license keys, the orders must reside on the same License Key Center account ID
Author: Saurabh Tyagi, co-author Edwin Premnath