ReadMe for Borland Connect – TFS sample connector

• Version: @Connect_buildnumber
• Last Updated: February 18, 2014

Please refer to the Borland Community and Borland Connect Release Notes for further configuration instructions.

This connector requires at least build 1.0.2.21 of Borland Connect. The latest version of Borland Connect can be downloaded from Micro Focus SupportLine (http://supportline.microfocus.com).

Required Libraries

All of the below files must exist in the root folder of the Borland Connect installation in order for the TFS Connector to execute. Borland Connect installs all of these except the TFS Client Assemblies, which must be installed separately. Since they are registered in the GAC, they do not need to be in the root folder of the Borland Connect install.

• The Microsoft Visual Studio Team Foundation Server 2012 Software Development Kit (http://www.microsoft.com/en-us/download/details.aspx?id=22616) (zip file named: TFS-SDK-11.0.0.1306) contains the following files which should be copied to the root folder of the Borland Connect installation.
• com.microsoft.tfs.sdk-11.0.0.jar from the redist/lib directory
• Seven dlls from the redist/native directory based on whether you have installed 32 or 64 bit Borland Connect
• The following files from the Deploy folder should be copied into the root folder of the Borland Connect installation: TFSLinkReader.dll and COMWrapper.dll.
• The open source Java Native Access library ( version 4.0 ) can be downloaded from https://github.com/twall/jna, the file ( jna-4.0.0.jar ).
• The TFS Client assemblies are required to be installed if using the 32 bit version of Borland Connect. These assemblies are not available from Microsoft in 64 bit. These are installed with Visual Studio, however a separate license referred to as a Client Access License ( CAL ) can also be purchased from Microsoft. These assemblies do not have to be copied into the Borland Connect root folder, since as a result of the installation they are registered in the GAC. The names of these assemblies (typically located in C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\ReferenceAssemblies\v2.0 ) are:
  • Microsoft.TeamFoundation.Client.dll
  • Microsoft.TeamFoundation.Common.dll
  • Microsoft.TeamFoundation.WorkItemTracking.Client.dll
• The Borland Connect installer registers the TFSLinkReader.dll in the GAC.  However, if at the time of install, the TFS Client assemblies have not been installed, then after they are installed, you must register the dll.  The command to register the TFSLinkReader.dll in the GAC is:

  C:\Windows\Microsoft.NET\Framework\v4.0.30319>regasm /codebase "C:\Program Files (x86)\Borland\Connect\TFSLinkReader.dll"

Required Connection Information

In order to use this connector, you will need to collect and enter this information in the Borland Connect user interface or in the <datasource> element in the Connect.xml file:

• Name - Borland Hub option. Enter a unique name for the data source.
• Product - Borland Hub option. Select the data source product name.
• TimeOffset - Borland Hub option. Number of seconds the data source time differs from the Borland Connect process time.
• User - Enter the user name.
• Password - Enter the password for the user.
• URL - Enter the TFS URL to connect to.

Known Limitations

• TFS does not store historical data for Iteration objects. Therefore the mapping cannot be bi-directional.
• The TFS connector does not support impersonation. As such, changes synchronized from Borland Hub into TFS will show the Author as the administrative user specified in the configuration file. However, since Borland Hub does support impersonation, the changes from TFS into Borland Hub will show the Author as the user that made the edit in TFS as long as that user’s full name exists in Borland Hub.
• Support for synchronizing TFS Links to Borland Hub Traces is not supported for Borland Connect 64 bit due to the unavailability of 64 bit TFS Client assemblies.