Here is a list of features and things you can do with the CollabNet Connector Framework.  These features apply to any of the supported ALM's listed as well as your own adaptor should you choose to write your own.


  • Unidirectional Synchronization: Collabnet Connect /sync unidirectional synchronization allows transfer of data in one direction from source to target ALM system. Migration from existing/legacy ALM system to TeamForge can be done through unidirectional synchronization.
  • Bidirectional Synchronization: Collabnet Connect /sync bi-directionally synchronize artifacts (defects, tracker items, requirements); including parent- child relationships, their comments and attachments. Changes are synched through in almost real time (less than seconds) and its not batch based.


Repository Mappings

  • Graphically manage and configure your repository mappings using the desktops graphical console and Web UI
  • Architecturally designed streaming algorithm for load balancing across multiple project mappings

Field Mappings

  • Supports non-graphical (Custom XSLT) and graphical mappings(Altova Mapforce and platform independent mapping rules mapping )
  • Platform neutral Mapping rules graphical field mapping support in rich clients (Eclipse and Windows Desktop Clients).One could use the graphical mapping on a Linux or Mac or Windows client
  • Extremely powerful and flexible mapping rule kinds (Direct, Value-map, Constant field mapping rules and custom XSLT snippet)
  • Switch between graphical and non-graphical data mapping on the fly
  • Reverse the graphical mapping  rules of a field mapping or a field mapping template so that user only have to design field mapping rules for one direction and start with a meaningful autogenerated template for the other one. This feature save up to 50 percent of the synchronization setup/maintenance time.

Field Mapping Template Support

  • Define and apply multiple graphical and non-graphical mapping templates to get started easily
  • Templatize field mappings and save them for the whole project/connector
  • Export templates and import them from staging to production systems
  • Sticky mappings: Link the project mappings to template. Automatically new mappings are applied when template gets changed

Conflict Detection and Resolution

  • CCF conflict handling supports detection, resolution and error logging in a cross repository environment and conflict handling mechanism is source and target system independent
  • User Configured conflict resolution policy is applied automatically whenever a conflict is detected while repository synchronization
  • Supported resolution policies are Always override, Always Ignore, always Override and Ignore Locks, Quarantine Artifact (Logged as failed shipment to manually resolve the conflict)
  • Whenever conflict is detected and resolved each event is logged and also CCF administrators gets notified about the work item conflict and resolution applied
  • Merge and lock stealing supported

Failed Shipments

  • When the work item fails during synchronization, it is stored as Failed shipments
  • CCF administrators get notified on failed entries during synchronization. User could identify the failed entry, examine the cause of the failure , analyze the payload what exact data passed to/from the tools, resolve/fix the issue and replay the fail entry to ship it again without any data loss
  • No silent skipping of failed artifact shipments hence no data is lost or duplicated
  • Auto replay rules for locked artifacts
  • When the artifact ships successfully, user can mark older versions as fixed

Delegation Support

  • Collabnet Connect / Link (IAF) Integrated with CollabNet TeamForge (CTF)
  • CTF project admins can delegate CCF tasks dealing with mapped entities of their projects to ordinary users by using TF permissions
  • Only a subset of mappings and actions is visible to users with limited permissions


  • CCF uses TeamForge user accounts for authentication
  • Site admin can perform all operations and CCF specific permissions are granted over CollabNet Connect /Embed IAF
  • CCF supports integration for SSL enabled and hosted systems as well
  • Flexible logging including SMTP messaging of errors via the log4j logging framework

Connector Backup and Upgrade

  • CCF supports incremental back up of complete set of necessary data on single click through web UI to recover the data after its loss, be it by data deletion or corruption.
  • On Connector backup, the current landscape contents and database snapshot will be taken as a backup and could be restore the original after a data loss event
  • Connector can be quickly and easily upgraded through web UI to the latest version

Open Source and Community Driven

  • CollabNet Connect/Sync is an Open-source project and built on powerful open source technologies such as openAdaptor and the Spring Framework
  • Active open source community participation and support on developing new third party integrations using Collabnet Connect /Sync
  • Customers can always look at the source code and use to develop own custom third party integrations.

System Requirements

Operating System:

A dedicated machine to run CCF with any of the below operating systems


  •  Windows Server 2008/2003 (32 bit/64 bit)
  •  Windows XP/Vista/7 (32 bit/64 bit)


  • RHEL 5.2 + (32 bit/64 bit)

(includes Cent OS/Fedora)


Hardware :

  •  4 - 8 GB system memory
  • 2 CPU
  • 1-100 GB free disk space



  • Oracle/Sun JDK 6 or  later (for QC-TF integration must to have 32 bit JVM)
  • CCF apache tomcat zip (latest version)
  • Eclipse Indigo/v3.x with CCF GUI plugin
  • CollabNet Windows desktop Client (Optional)
  • OTA client registration in CCF machine (in case of HP ALM 11 or above)



For a medium sized QC-TF installation (for synching 100,000 of artifacts), CCF team recommends to have a dedicated 64 bit Windows OS machine with 2 CPU; 8GB RAM ; 80 GB of disk space and a 32 bit JVM.

Supported Adaptors

The CollabNet Connector Framework includes read/write adaptors for the following products.  The feature within the product that we support is included in (parenthesis).

CollabNet TeamForge (Tracker artifacts):

  • TeamForge 5.3 and higher: tracker item and planning folder sync support
  • TeamForge 5.2: tracker item sync support
  • CollabNet SourceForge Enterprise 5.0 to 5.1: tracker item sync support
  • SourceForge Enterprise Edition 4.4 SP1 + HF1: tracker item sync support

CollabNet Enterprise Edition (Project Tracker artifacts):

  • 5.0 and higher: project tracker sync support

HP Quality Center (defects and requirements):

  • HP ALM 11.0, 11.5, 12, 12.20, 12.50: defect and requirement sync support
  • 10.0: defect and requirement sync support
  • 9.0, 9.2: defect sync support
  • SQL Server and Oracle 10g tested

These adaptors can be mixed and matched in any combination to build a bidirectional synchronization tool.  You can also write your own read/write adaptor and plug it in to the CollabNet Connector Framework to synchronize with any of these tools.

Information to help get you started writing your own adaptor can be found in the wiki .  If you want to connect a commercial tool like JIRA or ClearQuest we suggest you start a discussion in our forum to see if there any other parties interested in helping you.  You can even start your own project on openCollabNet to host this effort.

Supported Operating Systems

CollabNet Connector Framework is written in Java and should run on any operating system with a Java 6 JRE.  However, specific adaptors can have requirements for specific operating systems.  For example, the HP Quality Center adaptor uses the Quality Center client API, which is COM-based and only runs on Windows operating systems.  So if you are using CCF to connect to HP Quality Center you must run CCF on a Windows system.  However, the adaptor does not have to run on the same physical server as Quality Center, so the Quality Center server itself can be running on any OS that it supports.

CollabNet currently only qualifies the Quality Center adaptor with Quality Center running on a Windows server, but the Quality Center client API should handle any details related to the server OS. 

Screenshots of Graphical Admin Console

CCF Eclipse Desktop CCF Eclipse Desktop CCF Windows DesktopCCF Windows Desktop




Repository Mapping Directions RepositoryMappingswebui.jpg

Conflict Resolution PolicyConflict Resolution

 IAF PermissionsIAF Permissions  Delegation  SupportDelegation Support  Connector UpgradeConnector Upgrade
 Failed ShipmentsFailed Shipments  Failed Shipment DetailsFailed Shipment Details  Identity MappingsIdentity Mappings  Identity Mapping DetailsIdentity Mapping Details
Mapping Rules MappingMapping Rules Mapping Reverse Field Mapping WizardReverse Field Mapping Wizard Import Field Mapping TemplatesImport Field Mapping Templates Templatize Field MappingTemplatize Field Mappings