ReadMe for AccuRev Connector for Borland Connect

AccuRev Connector for Borland Connect (AccuRev Connector) lets you synchronize AccuWork assets like stories, tasks, and change requests with those in other Borland Hub repositories and clients like StarTeam Agile.

Release Information


This section lists prequisites required to successfully install, configure, and run AccuRev Connector.

Borland Connect Requirements

AccuRev Connector requires Borland Connect version 1.3 or later. You can download the latest version of Borland Connect from Micro Focus SupportLine (

Refer to the Borland Community ( and Using Borland Connect for configuration information for Borland Connect.

AccuWork Schema Requirements

You must define the following fields in your AccuWork schema if they do not already exist. Note that the fields must have the Name and Type shown in the following table. (The Label field controls what appears on the issue record form, and you can call that whatever you like.)

Field Name Field Type
starTeamKey Text
starTeamIssueLink Attachments
project Choose
iteration List
type Choose

Note that you must also create the values for fields with types of Choose and List. For example, for the "project" field, specify the project names in the AccuWork schema.

AccuRev Client Requirements

The AccuRev client must be installed on the same machine on which Borland Connect is installed.

Required Libraries

AccuRev Connector requires the libraries from the .jar files listed here.

These .jar files are available in the AccuRev Connector .zip file that also includes this ReadMe.html:

And these .jar files are available from external sources, as noted:

Once you have collected the required .jar files, place them in the Borland Connect root directory prior to running Borland Connect. See Using Borland Connect for additional configuration information.

Configuring AccuRev Connector

You configure AccuRev Connector using the Borland Connect Create Connection Wizard. You can bootstrap this process by merging pre-defined AccuRev <DataSource> and <Synchronization> elements in the Connect.xml.sample configuration file with the Connect.xml configuration file located in your StarFlow Extensions/Connect folder. The Connect.xml.sample file is included in the AccuRev Connector .zip file that also contains this ReadMe.html. For a complete description of this process, see Merging Connect.xml Content in Using Borland Connect.

Specifying the Connection to the AccuRev Data Source

In order to use AccuRev Connector, you need to specify the following parameters, which allow the Borland Hub to connect to your AccuRev data source:

In addition, the following fields are required in order to synchronize AccuWork and StarTeam Agile assets:

Finally, you might have to specify one or more of the following fields depending on how you want to synchronize AccuWork assets.

See Sychronizing AccuWork and StartTeam Agile Assets for specific information.

Sychronizing AccuWork and StarTeam Agile Assets

AccuRev Connector allows you to synchronize AccuWork assets with those from other Borland Hub repositories and clients. The default configuration synchronizes assets from AccuWork and StarTeam Agile, as shown in the following table:

AccuWork Asset StarTeam Agile Asset
Iteration Sprint
UserStory Story
Task Task
Defect Change Request

You can, of course, customize AccuRev Connector to do whatever you like -- you might choose to synchronize AccuWork defects with StarTeam Agile defects instead of Change Requests, for example. Note that the available assets in AccuWork are based on the values defined for the "type" field in your AccuWork schema and use the names defined for those values. (Your AccuWork schema might have a type of "bug" instead of "defect", for example.) The following sections provide additional information on synchronizing StarTeam Agile and AccuWork assets.


The AccuRev Connector supports parent-child relationships between stories and tasks, though you must explicitly configure them if you want relationships synchronized. Note that you can define other types of assets as parents. For example, in AccuWork, an issue with a type of "task" can point to a user story or a defect.

In addition, if you want tasks to inherit the Target Release from the parent story, you must set the Apply Value from Parent field for the AccuRev data source.


AccuWork issues with a type of "Defect" can be synchronized to a StarTeam Agile story with a type of "Defect" or to Change Requests. By default, AccuWork defects are synchronized with StarTeam Agile Change Requests.


If you want to synchronize sprints and iterations:

Managing Deleted Assets

AccuRev's TimeSafe architecture prevents AccuWork issues from being deleted though no such restriction exists in StarTeam Agile. However, you can use the On Delete State and On Delete Status fields to set the AccuWork issue's State field to Cancelled and the Status field to Closed when the corresponding asset is deleted from StarTeam Agile.

Calculated Field Values

The following types use fields whose values are calculated by AccuRev Connector:

If you plan to synchronize any of these types, you must specify their calculated fields with the values as shown in the following table:

Field Name Value
parentProperty internal_Parent
modifiedByProperty internal_modifiedUser
modifiedTimeProperty internal_modifiedTime

Known Limitations

AccuRev Connector 2014.1 has the following known limitations: