ReadMe for Borland Connect – Rally sample connector

• Version: @Connect_buildnumber.
• Last Updated: September 12, 2014

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

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

Required Libraries

The following libraries are required to run the Rally Connector for Borland Connect.  These files should be retrieved from the local Deploy folder or from the RallyDev developers site and placed into the root Borland Connect directory prior to running Borland Connect.  For further configuration instructions, see the Borland Connect Release Notes.

• RallyConnector.jar (included in deploy folder)
• commons-codec-1.6.jar
• commons-logging-1.1.1.jar
• gson-2.1.jar
• httpclient-4.2.1.jar
• httpclient-cache-4.2.1.jar
• httpcore-4.2.1.jar
• rally-rest-api-1.0.6.jar

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 Rally URL to connect to.
• Proxy - Enter the Rally Proxy.
• Workspace - Enter the Rally Workspace.

Known Limitations

• If a Rally property has a size limit (such as Story name or description) and the mapped value from Borland Hub is greater than that limit, then the Borland Hub item cannot be synchronized into Rally and an error will be logged stating that the update in Rally could not be completed due to the size limit of the property.  This issue can be avoided by mapping text properties of the same size limit.
• The Rally connector does not support impersonation.  As such, changes synchronized from Borland Hub into Rally will show the Author as the administrative user specified in the configuration file.  However, since StarTeam does support impersonation, the changes from Rally into Borland Hub will show the Author as the user that made the edit in Rally as long as that user’s full name exists in Borland Hub.
• The Rally admin user specified in the Connect.xml file must have their Default Workspace in the Rally User Profile set to the same Workspace as is specified in the Connector. If the Default Workspace does not match, then Borland Connect will receive a Workspace Not Found Exception when attempting to synchronize with Rally.  In order to synchronize data from two different workspaces, you must create two DataSources each with a different user whose default workspace is set to the workspace to be synchronized.
• History for Rally SyncItems is implemented by parsing the “Revisions” descriptions which use ‘[‘ and ‘]’ as delimiters. Borland Connect uses historical value (not just Modify Time ) data to resolve bi-directional mappings, when two updates to the same property on the same item occur during a synchronization cycle.  If this occurs and the value of the property contains a delimiter character, then the second update may be overwritten with the first value.