Sumant Renukarya 270002B42N Visits (1881)
It is possible to export and import the work items from a repository to another. Here was a unique situation, which demanded additional work.
We were trying to export workitems to CSV and import it in to other repository. It is possible to get the XML data entered in an attribute of a work item upon export, if that attribute is of the type wiki or HTML. However we had an attribute of the type largeString, which had XML content as the data for this attribute.
Exporting the work item to CSV in this case did export the attribute but not the XML data to CSV.
==> Here are the steps that we took, to bring the XML content from the attribute of the type large string at the target project area. It makes use of Temporary HTML attribute for this cause.
4. Apply the script to the LargeHTML attribute.
Please note, the use case mentioned here may not be applicable to all users performing an export and import, as this was a unique situation with a non-typical solution.
One of the users using IBM Rational Team Concert (RTC) 4.0.1 were planning to move some work items to a different repository.
To do this, they were considering the following options along with some requirements:
a. Move the work items, preserving workitem ID and if possible history also.
b. Export workitems to CSV file and then import it into other repository.
Here is the information that should help users with similar queries:
So those references would break if the work item is moved.
AcdntlPoet 2700019V2G Visits (1827)
IBM Rational Synergy for Rational Team Concert Bridge Connector - Part 1 - This article describes the use of Rational Synergy for Rational Team Concert (RTC) Bridge Connector. It talks about who can utilize this integration, and the benefits and the features of doing so.
IBM Rational Synergy for Rational Team Concert Bridge Connector - Part 2 - This article describes the use of Rational Synergy for Rational Team Concert (RTC) Bridge Connector. It talks about who can utilize this integration, and the benefits and the features of doing so.
IBM Rational Synergy for Rational Team Concert Synchronizer - Rational Synergy users can now migrate to Rational Team Concert (RTC) and migrate their source code data to RTC. This articles talks about the Rational Synergy for Rational Team Concert Synchronizer and who should use this integration. It also talks about some of the benefits, best practices, workarounds and limitations of the RTC Synchronizer integration.
Sumant Renukarya 270002B42N Visits (1691)
If you are using Rational Team Concert (RTC) 184.108.40.206 and an Oracle database, trying to load a plan with more than 1000 work items may fail.
Here are the symptoms and errors:
a. In the web client, it shows the below error:
b. In the Eclipse client, it gives the warning that it has more than 1000 work items.
However, ignoring the warning still doesn’t help in loading the workitems on the planned items tab.
c. The complete error is as follows:
If the working environment is a combination of RTC 220.127.116.11 version and Oracle database only and this issue is encountered, one has come across a known defect.
Here are the details of the defect work item from jazz.net and this is fixed in RTC 4.0.1: http
In case you need a fix, a PMR needs to be raised with IBM Rational Client Support asking for a hot-fix, along with the mention of the existing hot-fixes installed, if any.
AcdntlPoet 2700019V2G Visits (2333)
Learn how to set up an IBM Rational Team Concert main build that performs an IBM Rational Developer for System z code review. Based on the result of the code review, the process either submits the build to compile, or stops and reports the code review errors. Apply the tested, documented sample described in this article to implement a similar solution on your own platform. The steps focus on the Rational Team Concert administrator who writes an Ant task to compile COBOL programs, depending on other previous tasks, such as quality control.
Set up a Jazz Build Engine to run an Ant script: Part 1. Setup build definitions- The initial Part 1 article describes the technical and functional context of the scenario, and the Jazz Build Engine configuration.
Set up a Jazz Build Engine to run an Ant script: Part 2. Setup build scripts to perform preview build- In this Part 2 article, we introduce the Ant-based build script, build.xml, that defines tasks for the build to run.
Set up a Jazz Build Engine to run an Ant script: Part 3. Setup build scripts to coordinate code review and build- In the final article, Part 3 describes how to run the RPP synchronize task, how to implement a code review, how to parse, convert, and publish the code review results, and how to run the build.
Figure 1. Technical context for the sample scenario: