Migrate ALM/QC Synchronizer links

This topic describes how to migrate synchronization links from the Micro Focus ALM/QC Synchronizer to Micro Focus Connect connections. For details about the ALM/QC Synchronizer, see the ALM Synchronizer page.

Perform the migration

This section describes how to migrate synchronization links from the ALM/QC Synchronizer to Micro Focus Connect.

Note: ALM/QC synchronization links do not distinguish between connections and data sources. Each link combines the information relevant to the connection and the data source.

To migrate the synchronization links:

  1. In the Micro Focus Connect dashboard, create a data source for the Master source, ALM/QC. For details, see Create a data source.
  2. Create a second data source for the Target, such as Jira, Azure DevOps, or ALM/QC. The creation of these data sources is required at least once per active unique endpoint URL/domain. Data sources targeting the same endpoint (URL/domain) may be reused.
  3. Create a connection that is a mirror of the ALM/QC Synchronizer link. Use the same link name for the new connection. Ensure that the Master and Target of the connection match that of the ALM/QC Synchronizer link, especially if both endpoints are ALM/QC. For details, see Create and manage connections.

    Tip: Always use type specific project maps, and not Common Projects. This will allow the merging of connections, if necessary, in the future.

  4. Disable the link in ALM/QC Synchronizer.
  5. In the Synchronizer Dashboard, select Link > Export > Link Data Into Backup File. Synchronizer generates two files: LinkConfig.xml and LinkIdsMap.xml.
  6. For Jira type target endpoints:

    1. Create a property bag for Jira with the following content:






      type=link_issue_type_name (e.g. Bug)



    2. If using a proxy server, append the tomcat java options to the contents of the above file.

    3. Use the DataSourceExtractors script to query the Jira server for the issue type IDs and keys of the project in the ALM/QC Synchronizer link. (In the batch file, un-rem and run line 9.) For details, see Batch utility scripts. This batch creates an output file, jira.{projectkey}.{type}.txt.
  7. Stop all running connections in the Micro Focus Connect instance, using the StopAllConnections script.
  8. Zip and perform a backup of the AppData/data folder.
  9. Open the mfcGosipXrefsMerge.bat script.

    1. If you renamed the LinkConfig.xml or LinkIdsMap.xml files, modify lines 8 and 9 in the script file with the new names.
    2. For a Jira endpoint, use lines 10, 11, and 12 to specify the input key-value pair files in sequence to the command, for each input file that you created above. The script allows up to three key-value pair files. You may add or remove lines to or from the script to represent all of your Jira types. If you do add or remove lines, make sure to modify line 23 to reflect the correct set of lines, and the file name parameters they represent. Verify the paths of the files on lines 10, 11, and 12.
  10. Run the GosipXrefsMerge script. Un-rem and run line 23.
  11. Open ClearWatermarks.bat and un-rem line 21 and run it: mfcClearWatermarks.jar -removenulls -removemismatches. (This is the third version of the command in the batch script.)
  12. Log on to Micro Focus Connect and export the cross references for the Connect connection. Do a sanity check to make sure that the cross references between the ALM/QC master to the target endpoint systems are correct. Using the ALM Synchronizer link, make sure that the cross references have the expected values and that they represent artifacts known to have synced correctly between the endpoints.
  13. Once again, zip and backup the AppData/data folder.
  14. Perform a final verification. After the checks are successfully completed, start the connection and verify that Micro Focus Connect picked up where the ALM/QC Synchronizer left off.

Back to top