Current release: TeamForge Connector Server 2.3.6 (aka CCF 2.3.6)

Here is a quick overview of the new features:


Support for TeamForge 16.7 updates, 16.10, 17.1 and 17.4

TeamForge connector (CCF) 2.3.6 officially supports TeamForge 16.7 updates, 16.10, 17.1 and 17.4.

Previous release: TeamForge Connector Server 2.3.5 (aka CCF 2.3.5)

Here is a quick overview of the new features:


Support for TeamForge 8.2

TeamForge connector (CCF) 2.3.5 officially supports TeamForge 8.2. 


Support for HP ALM 12.50

TeamForge connector (CCF) 2.3.5 officially supports HP ALM/QC 12.50. HP ALM defects and requirements can be bi-directionally synchronized with CollabNet TeamForge trackers and planning folders.

Newly added connector property

  • Expose SOAP connection timeout: This is used to set the TeamForge SOAP connection timeout values in CCFMaster Web UI.

Previous release: TeamForge Connector Server 2.3.4 (aka CCF 2.3.4)

Here is a quick overview of the new features:


Support for HP ALM 12.20

TeamForge connector (CCF) 2.3.4 officially supports HP ALM/QC 12.20. HP ALM defects and requirements can be bi-directionally synchronized with CollabNet TeamForge trackers and planning folders. We support the traditional QC Desktop client as well as the new HP ALM Web client.


Support for TeamForge 8.1

TeamForge connector (CCF) 2.3.4 officially supports TeamForge 8.1.


Support for Tomcat with 64 Bit JVM

CCF 2.3.4 officially runs on Oracle’s 64 Bit JVM. This is useful for customers with huge CCF data sets that require Java heap sizes > 3GB. CCF’s synchronization engines will still run on 32 Bit Oracle JVMs as Quality Center’s API requires this. For more info, click here

Newly added connector properties

  • Ignore Requirement Root Folder: If set to true, Quality Center’s root requirement root folder will not be shipped to TeamForge. Set to false by default.
  • COM Re-Initialization Count: Determines the number of QC COM API operations that will be performed before CCF will destroy all COM objects. This is to avoid COM memory leaks and QC driver crashes.

Previous release: TeamForge Connector Server 2.3.3 (aka CCF 2.3.3)

Here is a quick overview of the new features:


Support for TeamForge 8.0

TeamForge connector (CCF) 2.3.3 officially supports TeamForge 8.0.

Support for latest Tomcat distribution

TeamForge connector (CCF) 2.3.3 uses the latest Apache-Tomcat-7.0.59 distribution

Newly added connector properties

  • Ignore Sync User Name From Attachment: If this property is set to true, attachments synched to TeamForge will no longer be prefixed with the name of the connector user. The default is to prefix attachment file names.
  • Preserve Bulk Comment Order: If multiple comments are synched in one sync run, the original order will be maintained. The default behavior is to synch bulk comments in reverse order.

Previous release: TeamForge Connector Server 2.3.2 (aka CCF 2.3.2)

Here is a quick overview of the new features:


Support for TeamForge 7.2

TeamForge connector (CCF) 2.3.2 officially supports TeamForge 7.2.

Support for JDK 8

TeamForge connector (CCF) 2.3.2 uses Apache-Tomcat-7.0.53 distribution which supports Java 8.

Previous release: TeamForge Connector Server 2.3.1 (aka CCF 2.3.1)

Here is a quick overview of new features:


Support for HP ALM 12

TeamForge connector (CCF) 2.3.1 officially supports HP ALM 12.

CCF Training Videos

The new CCF training videos on Remote Administration  and Delegation support are available to users for free with the existing CCF training videos.

Previous release: TeamForge Connector Server 2.3 (aka CCF 2.3)

Here's a quick overview of CCF 2.3's main new features:


Support for TeamForge 7.1

TeamForge connector (CCF) 2.3 officially supports TeamForge 7.1

Lean Requirement mapping

  • Support for requirement type ‘ALL’ to sync all requirement types from HP QC/ALM to a single TF tracker using a single repository and graphical field mapping.
  • Eliminates the need of multiple repository mappings for each requirement type in HP QC/ALM which in turn reduces field mapping maintenance for CCF admins
  • Reduces the number of QC connections and thereby increases performance and and stability
  • Supported for all three types of field mappings namely custom XSLT, Mapforce Mapping  and Mapping rules mapping

Manage Field mapping through Web UI (CCFMaster)

  • Ability to view and manage the associated field mappings for the repository mapping direction from the Web UI
  • Allows to create field mappings from existing field mapping templates for the repository mapping direction directly from the Web UI
  • Support to create new linked field mapping from the existing field mapping templates in the Web UI
  • User will be able to switch/set active field mapping and delete inactive field mappings for the repository mapping direction from the Web UI
  • Field mappings can be linked/created from both connector and project mode field mapping templates from the Web UI

Improved log output from synchronization engines

  • Log entries about artifact updates and creation now also contain info about the affected TeamForge tracker

Previous release: TeamForge Connector Server 2.2.1 (aka CCF 2.2.1)


  • Supporting CollabNet TeamForge 7.0
  • No need for IAF dummy service any more (TeamForge 7.0 only)
  • Making CCF 2.2 as generic as CCF 1.5.1 by introducing a generic participant kind which can be used by third party CCF plugins to provide their own CCF Core and TF Web UI contributions
  • Providing a reference implementation for the generic participant kind which will allow synching TF with another ALM platform (MS TFS and Jira)
  •  Fixing bugs reported by our customers

Previous release: TeamForge Connector Server 2.1 (aka CCF 2.1)

Here's a quick overview of CCF 2.1's main new features:


Mapping Rules Graphical Field Mappings


•             MapForce independent, platform neutral Mapping rules graphical field mapping support in our rich clients (Eclipse and Windows Desktop Clients).

•             User does not need to acquire licenses for additional software's to create/edit the field mappings. Could use the in-built mapping rules field mappings in the  rich clients

•             This is not a replacement of the MapForce mapping feature, it is just another option to configure the mappings.

•             It is now possible to use the graphical mapping on a Linux or Mac client

•             Support for Default Mapping Rules templates to get started easily

•             Support for mapping rule kinds (Direct, Value-map, Constant field mapping rules and custom XSLT snippet)


Core configuration properties exposed over UI


•             Easy managing core configuration properties through UI

•             Supported on all  the 3 clients (Desktop , Windows and Web UI)

•             As configuration properties are tied with cores; care should be taken while updating  to avoid misconfiguring core property values.

•             Ability to restore default values.

•             Required Site Admin access

•             Configurable CCF core config properties are exposed via REST api


Online backup option


•             Connector can be backup easily through web UI. While backup, the current landscape contents and database snapshot will be taken as a backup under the CCFHOME/archive/backup-$Date directory.

•             CCF supports only manual restore of the backup contents

•             Required site admin access to use the connector backup.


Improved handling of ccf.conf file


•             Users are provided with different options to ease the configuration for loading CCF runtime properties after an update without re-installing the services.


Other Enhancements features



•             Connector Upgrade Enhancement

•             Prevent user from losing data while switching tabs

•             TF 6.2 support

•             REST API Enhancement


For more details, Please visit our help doc link -


You can also have a look at the PPT on to learn more about our new features.

Previous release: TeamForge Connector Server (aka CCF 2.0)

CCF 2.0 introduces a web based administration console for CCF that is tightly integrated with TeamForge using the Integrated Application Framework (IAF). It also introduces multi client and staging support. A presentation about CCF 2.0 can be found here.

Previous release: 1.5.1

CCF 1.5.1 gets rid of the QC, TF and PT resnych user, ships with improved documentation for remote administration and mass artifact imports and comes with various usability enhancements in CCF GUI.

CCF 1.5.1 related issues

Previous release: 1.5.0

CCF 1.5.0 will expose all tracker and planning folder fields that have been newly introduced in CollabNet TeamForge 5.4. Furthermore, it will support HP Quality Center 11. Finally, it will contain bug fixes for issues detected in previous CCF releases.

CCF 1.5.0 related issues

Previous release: 1.4.2

CCF 1.4.2 is a minor release that focuses on improving artifact synchronization in scenarios where parallel changes to artifacts are done frequently in different systems.

CCF 1.4.2 related issues

Previous release: 1.3.0


The primary new features in CCF 1.3.0 are support for HP QC requirements, the new agile features introduced in TeamForge 5.3 and support for parent child relationships.

Snippets from the release notes:

  • The CollabNet Connector Framework now supports synchronization of TeamForge tracker artifacts with Quality Center requirements. If you have TeamForge 5.3, you can synchronize planning folders with QC requirements.
  • You can synchronize TeamForge artifacts that have a parent-child relationship. A top-down approach is recommended when synchronizing hierarchies. For details, see the section on dealing with hierarchies in the Best Practices wiki.
  • Synchronization with TeamForge 5.3 tracker fields is fully supported.
  • HP QC COM API memory management is improved.
  • HTML-to-plain text formatting capabilities have been improved.
  • There is a better streaming algorithm for load balancing across multiple project mappings.
  • The Eclipse-based user interface (version 1.3.0) adds these features:
    • Project mappings for Quality Center defects as well as requirements are supported. Intelligent wizards are available for selecting project/tracker/requirement types in Quality Center, TeamForge and CollabNet Enterprise Edition.
    • It is possible to define and apply multiple graphical mapping templates.
    • The hospital view for quarantined artifacts has been improved, with enhanced replay functionality.

Previous release: 1.2.1

The primary new feature in CCF 1.2.1 is the addition of graphical field mapping and transformation.  This feature is optional and requires a commercial 3rd party product - Altova MapForce.  Details are in the wiki.

The CollabNet Connector Framework's Eclipse-based user interface provides these new features.

  • CCF Landscape editor
    • Create and modify data mappings on the fly using -
      • A sophisticated textual XSLT editor
      • The graphical data mapper software Altova MapForce
    • Easily switch between graphical and non-graphical data mapping
    • Use a special "operator mode" if you do not have access to CCF's files
  • CCF Preferences
    • Configure the graphical data mapping tool
    • Define roles that control user actions
    • Assign passwords to roles


Previous release: 1.2

The following features have been implemented:

- Support for QC 10.0

-Initial GUI with the following components:

  • CCF Landscape editor:
    • Graphically manage the CCF related properties of your ?TeamForge, HP QC and CEE systems

    • Monitor and control the status of your CCF services
    • Change the general CCF settings like data base connection and logging settings
    • Create, delete, modify and pause synchronization project mappings
    • Analyze problems that occurred for your project mappings
    • Create and modify data mappings on the fly
  • CCF Hospital View:
    • Query, analyze and modify the quarantined artifacts in the CCF hospital
    • Replay quarantined artifacts in real time
    • Manage the records in the CCF hospital
  • CCF Identity Mapping View:
    • Query, analyze and modify the mappings between your artifacts
    • Find problems within your identity mapping table and cure them


- Much more powerful dynamic XSLT processing component

- Hospital replay integrated in core scenarios

- Improved performance due to decreased number of web service calls and changes in the streaming algorithm

Previous release: 1.1.1

- Stabilized CCF 1.1 build

- An optional property has been added for reader components to ignore artifacts last modified by the connector user.

- Earlier, the CollabNet Connector Framework required that every mandatory field in a target system be defined. There was no option to preserve the current field value. With this release, the fieldValueHasChanged attribute is checked and the corresponding field is updated only if that attribute is set to true.

- XSLT scripts are available for all sample scenarios and use a simplified XSLT style.

- Several fixes have been made to prevent problems in Project Tracker caused by invalid XML characters. However, you will see the full effect of these fixes only with the upcoming release of CollabNet Enterprise Edition, version 5.3.

- An artifact property called shutdownCCFAfterInitialSync can be set to cause the connector to shut down after an initial synchronization of all artifact

- Remote monitoring, log level changing and auto restarting: Every scenario now comes with the OA HTTP JMX console turned on

Previous release: 1.1

Initial framework built on openAdaptor. Contains read/write support for SFEE Tracker Artifacts (version 4.4 SP1 and higher). Support for these example scenarios.

 - Add support for CEE Project Tracker artifacts (version 5.1 and higher)

 - Stabilization and improvements in runtime performance and memory usage.

 - Data source independence.

 - Improved conflict handling.

 - Update to latest openAdaptor release.

 - Provide Windows service wrapper files.

 - Support Hospital replay.