Best Practices, Frequently Asked Questions and more

Why synchronize?
The CollabNet Connector Framework makes it possible to synchronize different development tools used by project members. With the CollabNet connector to HP Quality Center, you can synchronize requirements and defects between a CollabNet tracker and Quality Center. Team members can work with either tool, and seamlessly see the latest changes made in the other one.

How are artifacts and defects synchronized?
Quality Center defects are synchronized with CollabNet tracker artifacts when you add or modify them in either system.

How are artifacts and requirements synchronized?
Quality Center requirements are synchronized with CollabNet TeamForge tracker artifacts or planning folder artifacts in TeamForge 6.0, when you add or modify them in either system.

What are the connector requirements for HP Quality Center?
The CollabNet Connector Framework works with HP Quality Center versions 9.0, 9.2 and 10.0 and 11.

What are the CCF perspective and views?
The Eclipse plugin for the connector user-interface provides a CCF perspective and these views: CCF Explorer, Hospital, Identity Mapping and Identity Mapping Consistency Check.

What is the central database?
The CollabNet Connector Framework maintains the synchronization status and the identity mappings of all artifacts synchronized by the connector in a central HSQL database. Additionally, the CCF database contains information about artifacts that failed to ship to the target system.

Can I install the CCF GUI without Internet access?
Yes. If your company policy does not allow you to connect to the CCF Eclipse update site directly, you can create a zipped local update site.

What are artifact conflicts and how are they handled?
When you run the connector, a conflict typically occurs when a target artifact is changed by a user after the last update by the connector.

What is the artifact hospital?
The hospital is a database that stores artifacts that failed to ship to the target system during synchronization.

How do I back up the connector?
To back up the connector, copy your production scenario file folder found at <CCF_HOME>\production. If you followed the recommended process, this was the folder that was copied and renamed from the "samples" folder provided with the installation.

How do I pause synchronization?
Pausing the synchronization is performed from the same menu that is used after configuration to resume the synchronization.

Where can I find the logs?
Information about errors is available in .log files located in the respective /logs folder for each scenario. In addition, when you run a connector scenario as a service, the Java Service Wrapper logs all console output from the JVM process to the wrapper.log file directly under that scenario.

How do I handle failed artifacts?
Artifacts that fail are stored in the HOSPITAL database table. Depending on the exception that caused the failure, you could re-run or continue running the connector, or replay the artifact.

How is setting up the connector for Project Tracker in CollabNet Enterprise Edition different from setting it up for Project Tracker in TeamForge?
If you've been using the connector with Quality Center and CollabNet Enterprise Edition Project Tracker, the process for setting it up for Project Tracker in TeamForge, including mapping projects and fields, is the same.

Can I use the same CCF GUI for both ScrumWorks Pro and Quality Center integrations with TeamForge?
Yes. Get CollabNet Connector Framework 1.5.0, and the latest version of the CCF GUI from http://ccf.open.collab.net/update-site.