Some records not processing with CQ Connector
RTC 2.0.0.2 with CQ Connector Gateway 2.0.0.2 and ClearQuest V7.1.1 running on Windows 2003 is the environment. I've gone through the troubleshooting steps outlined in this tech note http://jazz.net/library/techtip/89. I'm using ClearCase UCM projects integrated with the ClearQuest user database and have three UCM_Project records created in CQ called CCCQRTCProject, HelloWorld and PerlScripts and these are mapped to Work Item categories in the sync rules. All three of these UCM projects existed before I configured the CQ Gateway. Once I started the gateway only CCCQRTCProject was processed correctly. The other two projects were not processed. There are no JazzConnectorChangeEvent records waiting in ClearQuest. A defect created against CCCQRTCProject in ClearQuest processed correctly and a work item was created so I know the gateway is operational.
Any hints as to why the other two UCM_Project records are not being processed? And yes, the UCM_Project query filter I use does select these projects.
Any hints as to why the other two UCM_Project records are not being processed? And yes, the UCM_Project query filter I use does select these projects.
4 answers
If those other CQ UCM_Project records (aka HelloWorld and PerlScripts) were created before the CQ user database was configured to be CQ Connector-enabled, then they wouldn't appear in the JazzConnectorChangeEvent table.
You can sync in those CQ UCM_Project records into RTC by creating a CQ record that references them provided the CQ record satisfies the CQ query filter.
You can sync in those CQ UCM_Project records into RTC by creating a CQ record that references them provided the CQ record satisfies the CQ query filter.
If those other CQ UCM_Project records (aka HelloWorld and PerlScripts) were created before the CQ user database was configured to be CQ Connector-enabled, then they wouldn't appear in the JazzConnectorChangeEvent table.
You can sync in those CQ UCM_Project records into RTC by creating a CQ record that references them provided the CQ record satisfies the CQ query filter.
Thanks. I created a CQ defect as you suggested and the UCM_Project sync'd to RTC. Is there another method to achieve this "forced" sync without creating a new defect? I'm think about larger CQ projects that have many components that may span as many Work Item categories that may want to phase in the adoption of RTC with the CQ Connector. In this case, some UCM_Projects may want to adopt RTC later then others.
You can use the synctool, which is a command-line tool, to sync in a batch of CQ records. This will use the query filter you define for a particular CQ record type to determine the set of records to sync in. See http://publib.boulder.ibm.com/infocenter/rtc/v2r0m0/topic/com.ibm.team.connector.cq.doc/topics/t_importing_batch.html for more information.
My team is running into a similar problem. I have the CQ Connector set up and have imported my existing CQ records with the synctool. The problem we are experiencing is that users can create a CQ record outside of our defined sync query. Then the user may modify the CQ record so now it is selected by the sync query but it does not get created in RTC.
Do you have a solution to this problem?
Do you have a solution to this problem?