HPE QC / ALM Connector – Requirements for Sync

This section explains how to connect to supported versions of HPE QC / ALM using Tasktop’s HPE QC / ALM connector.

HPE QC / ALM Installation requirements

If the server version is HPE QC / ALM v10 or older, the HPE QC / ALM Connectivity add-in needs to be installed. To download the add-in, go to

http://qualityCenterHostAndPort/qcbin/addins.html

(where qualityCenterHostAndPort should be similar to hpalm.example.com:8080).

HPE QC / ALM Repository Configuration requirements

Server Version

When creating repositories for HPE QC / ALM, a number of options are available in the “Server Version” dropdown under the “Additional Settings” area. If the server version is HPE QC / ALM 11 and above, the server version should be set to either Automatic or HPE QC / ALM 11 (REST).

Note that HPE QC / ALM 11.5 is not a supported server version (however HPE QC / ALM 11.52 is supported).

Server version selection in the HPE QC / ALM task repository properties dialog

If using HPE QC / ALM 10 or below, then the HPE QC / ALM 10 (Remote) option must be selected. The remote client is a special Sync-specific connector which uses HPE QC / ALM’s native client running in a remote process to work around memory-leak issues in the native client.

In Sync, the HPE QC / ALM 10 (Native) option is disabled by default due to instability. If Tasktop Sync is started up with this repository setting, it will likely crash periodically due to a bug in the HPE QC / ALM native client. It can still be force-enabled by adding the property showQcNativeClient to the TasktopSync.ini file.

Comment Parsing Strategy

There are three comment parsing strategies to choose from: None (no comment parsing strategy), Strict, and Lenient. These strategies represent the procedure in which the HPE QC / ALM multi-comment field is separated into individual comments for synchronization to another repository. The Strict comment parsing strategy is the default for Tasktop Sync.

It should be noted that enabling or disabling comment parsing in the repository settings page does not enable or disable comment synchronization in any related task mappings, and similarly enabling or disabling comment synchronization in a task mapping will not enable or disable comment parsing. This means that tasks which have comments which fail to parse will cause errors even when their task mapping has comment synchronization disabled, when comment parsing is enabled in the repository settings page.

No comment parsing strategy

When no comment parsing strategy is specified, HPE QC / ALM tasks will not have comments for synchronization.

If comment synchronization is disabled, one can still synchronize the multi-comment field from HPE QC / ALM to a rich text field in the other system.

Strict comment parsing strategy

This strategy employs the delimiter of twenty-five consecutive underscore characters used by HPE QC / ALM to separate the body of text into individual comments. Comments synchronized using this strategy will use the text following the “:” character as the text body for the synchronized comment. Text preceding this character will be used as comment metadata to discern the comment author and creation date. If the creation date cannot be parsed from the comment metadata, comment creation dates will show as Jan 1 1970 00:00:00 GMT.

Failure to parse the text body into individual comments will result in an error and stop synchronization of this artifact.

Lenient comment parsing strategy

As with the Strict parsing strategy, the Lenient strategy separates the text body into comments using the aforementioned delimiter. This strategy also attempts to parse the comment metadata preceding the “:” character of each comment to identify the comment author and creation date. Failure to parse this metadata results in using the entire comment text between delimiters (including malformatted comment metadata) as the body of text for each comment. In this case, comments have creation dates of Jan 1 1970 00:00:00 GMT. Because the comment author will not be known in the event of a metadata parsing failure, the person mapping must be configured with a valid default user.

Issues with synchronization will arise if malformed comments that have been created in HPE QC / ALM are corrected after they have been posted. The corrected comment will be recognized as a new comment and synchronized to the proxy repository. The malformed comment still present in the proxy repository will then be synchronized back to HPE QC / ALM. Correcting the duplicate malformatted comment in HPE QC / ALM will result in the repetition of these same actions by Tasktop Sync. Malformatted comments created in HPE QC / ALM while using the Lenient strategy will always be present in both repositories.

Switching strategies from Lenient to Strict

Malformatted comments that had been synchronized while using the Lenient strategy will cause synchronization failures after switching to the Strict comment parsing strategy.

Comments

In the repository section, comment-content-type should be set to text/html.