Frequently asked questions about the CollabNet Connector Framework
- What is the CollabNet Connector Framework?
The CollabNet Connector Framework (CCF) SDK is an openAdaptor based SDK that allows rapid integrations and migrations dealing with the artifact data shared between different tools in the ALM cycle in combination with the collaborative platforms from CollabNet.
- What's new in this release?
For information about new features, fixes and more see the release notes.
- 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?
When you configure and run the connector, CollabNet tracker artifacts and Quality Center defects are synchronized. The current state of synchronization and the identity mapping are stored in the CCF database.
- 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.
- 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.
- 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.
- 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.