Best Practices, Frequently Asked Questions and more

What are the connector requirements for TeamForge and ScrumWorks Pro?
The CollabNet ScrumWorks Pro – TeamForge Integration works with TeamForge 5.3 and higher and ScrumWorks Pro releases 4.4 and higher.

What artifacts are synchronized?
In synchronizing a TeamForge project to a ScrumWorks Pro product, the following project mappings are available:

How are SWP Product Backlog Items synchronized with TeamForge artifacts?
The connector supports bidirectional synchronization of ScrumWorks Pro Product Backlog Items and TeamForge artifacts. Some fields synchronize birectionally, while others only synchronize from ScrumWorks Pro to TeamForge.

How are SWP Tasks synchronized with TeamForge artifacts?
The connector supports bidirectional synchronization of ScrumWorks Pro Tasks and TeamForge artifacts. All fields synchronize bidirectionally except for the task's parent.

How is SWP MetaData synchronized with TeamForge artifacts?
All meta-data, which includes teams, sprints, themes, and users, is only synchronized from ScrumWorks Pro to TeamForge. Meta-data usage within Product Backlog Items and Tasks are not always a bidirectional synchronization.

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 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.

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.

Why do the user and resync user need to be dedicated connector users?
The credentials for the connector user and resync user cannot be used to login to TeamForge or ScrumWorks. If changes are applied in either application by either the dedicated connector user or the resync user, the data will not be synchronized.

Why do you need a connector user and a resync user?

Why is data not synchronizing between TeamForge and ScrumWorks Pro?
There are many possible reasons why data is not synchronized. Below is a list of possibilities:

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.

How do I uninstall the connector?
To uninstall the connector, run these scripts an administrator: