Readme for Micro Focus Connect Hub Connector 24.2

This readme describes how to configure Micro Focus Hub Connector. Refer to the Micro Focus Community and Micro Focus Connect Help Center for further configuration instructions.

The Micro Focus Hub Connector for Micro Focus Connect (Micro Focus Hub Connector) lets you synchronize Hub assets like Requirements and Stories with assets in other Micro Focus Connectors, for example assets found in the Micro Focus Azure DevOps Connector.


Copyright 2018 - 2024 Open Text.

The only warranties for products and services of Open Text and its affiliates and licensors ("Open Text") are as may be set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Open Text shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.

Except as specifically indicated otherwise, this document contains confidential information and a valid license is required for possession, use or copying. If this work is provided to the U.S. Government, consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

  Installation and Upgrade Information Technical Notes
Prerequisites Known Issues Need assistance with the product?


Supported Versions

This version of the connector is certified with Hub version 6.0(17.0.0)

Unless otherwise specified, for any given MF Connect connector from OpenText, all versions of the connector product that are officially released and supported by it's vendor both four months before the time of the release of the connector as well as at the time of using the connector, are supported by OpenText. Not all product versions will be tested and validated by OpenText for each connector release. Instead, OpenText chooses a subset of versions that we deem representative or most important to run validation and certification tests against. These selected versions are mentioned in the respective connector read-me, clearly identifying them as "validated" or "certified". As stated above, this does not mean that Micro Focus Connect does not support other product versions - it only means that no validation test cycle was executed for the other versions.

Supported Assets

This version of the connector supports Agile asset types like Stories and Defects, as well as custom fields and types.




This connector requires at least build 24.2 of Micro Focus Connect and can be configured using the Micro Focus Connect UI.

The file should be copied to the Micro Focus Connect's AppData\data folder.

This connector is an update to the installed connector, you should remove (or move to a directory outside of the connectors) and replace the AppData\connectors\mfcConnectorStarteam\mfcConnectorStarteam*.jar file with the one provided.



Installation and Upgrade Information

The following information contains notes regarding installation, but does not replace the entire process.

Required Connection Information

In order to use this connector, you will need to collect and enter this information in the Micro Focus Connect user interface:



Known Issues

ConcurrentModificationExceptions Error

Occasional ConcurrentModificationExceptions may occur in the Micro Focus Connect log. This has no influence on the correctness of the synchronized data.

Clearing Values or Setting to No-Value

The StarTeam Connector does not support setting of numeric fields, enumerated fields, or user fields to no-value. For example, if the "other side" has a new story with no-value for "estimated points", the StarTeam Connector will generate an error when attempting to create the story.



Technical Notes

Tags Created as Server Tags

When running a Hub to Hub synchronization that contains Agile data with Tag properties, the tag will be created as a Server tag if it does not exist on the opposite side. The Hub connector cannot distinguish between Server and Project tags, and cannot correctly create a new tag to match the source tag’s identity. For example, when using Rhythm, the synchronized Project tag will appear under the Server tags.



Need assistance with the product?

Get support enables you to open a support incident or to submit a bug. You can also browse many helpful support resources.