TeamForge connector 2.3.4 adds these new
features.
- Support for TeamForge 8.1
- TeamForge connector (CCF) 2.3.3 officially
supports TeamForge 8.1.
- 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 both, the traditional QC Desktop client and the new HP
ALM Web client.
- 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. Click here for more
information.
- Newly added connector properties (requires update of CCF synchronization
engines/cores)
-
- 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 destroys all the COM
objects. This is to avoid COM memory leaks and QC driver
crashes.