One of the difficult tasks in performing an import of external data into a ClearQuest database is determining how to define the data type of a field within a ClearQuest record. If you define it incorrectly, the import of data will fail because of a type mismatch and you will need to modify your ClearQuest schema to correct the issue.
(This is the last in a three-part series of articles describing the migration of RTC SCM data to ClearCase.)
SCM Artifact Migration – Implementation Challenges
The previous blog in this series described the importing of RTC SCM metadata and content into ClearCase. What it didn't describe were the many challenges in accurately mapping SCM artifacts from the RTC data model to the ClearCase data model. For brevity, the most significant deficiencies that had to be accommodated for in RTC were:
ClearCase Work Area Manager presents the user with an overview of an entire design workspace in-terms of the information pertaining to the design management. It lists the design libraries managed by ClearCase in a tree representation. User can perform basic and advance design management operations on the designs listed under WAM.
(This is the second in a three-part series of articles describing the migration of RTC SCM data to ClearCase.)
Importing SCM Metadata and Content – Design
The importer would be designed to be coupled to the schema output by the exporter. The expectation is that a description of the stream to import is described in metadata (JSON) as:
I’m pleased to announce the release of ClearQuest 18.104.22.168, 22.214.171.124, and 126.96.36.199. This is the second fixpack released this year, following on the heels of the release of 9.0.1 in June. While the 188.8.131.52 release contains only defect and security related fixes, what follows is the content of the 9.0.x releases. For a list of the fixes provided in each release, please visit http://www-01.ibm.com/support/docview.wss?uid=swg27036262.
I’m pleased to announce the release of ClearCase 184.108.40.206, 220.127.116.11, and 18.104.22.168. This is the second fixpack released this year, following on the heels of the release of 9.0.1 in June. While the 22.214.171.124 release contains only defect and security related fixes, what follows is the content of the 9.0.x releases. For a list of the fixes provided in each release, please visit http://www-01.ibm.com/support/docview.wss?uid=swg27023148.
As part of the ClearCase integration with Cadence Virtuoso, the ClearCase design management capabilities are available to the designers from within the Virtuoso’s cellview editors (CVE) namely schematic, layout etc.
‘ClearCase’ menu is made available on the menu bar of the cellview editors. Designers can perform the design management operations using the ClearCase menu. Detailed messaging from design management operations is routed to the Command Interpreter Window (CIW).
Many software and hardware projects are subject to regulatory requirements that can be challenging and expensive to implement. ClearCase provides numerous features that aid in implementing solutions to many of these challenges. These include security mechanisms, extensive process automation and control support, multi-domain traceability and auditing support, and more. This webinar will provide an overview of many of these mechanisms with examples of potential application.
Not all users of ClearCase use the Unified Change Management (UCM) process. In fact, base ClearCase is an excellent choice for projects that don’t require the process enforcement and activity management that UCM provides but who still want the security, scalability, auditability, traceability and stability inherent in ClearCase.
(This is the first in a three-part series of articles describing the migration of RTC SCM data to ClearCase.)
When I joined HCL, I was asked to provide tooling to help our internal customers migrate their SCM systems from Rational Team Concert ("RTC") to ClearCase. While there exist tools to help synchronize the two repositories in simplistic ways, there are no tools that will export the full history of SCM artifacts out of RTC and into ClearCase. Having been a developer of both the RTC and ClearCase products, I looked forward to the creative challenge of solving that problem.