Note: Please note, the steps mentioned in this document are also applicable to partner integration systems.

Pre Migration Instructions

Version wise pre-requisites to run migration are mentioned in this document. Kindly go through all the version wise sections from your installed version to the version you want to migrate one by one and fulfil each one of them to run migration successfully.

Migrating Version to 6.10 Update 2 or above

VersionOne System Checklist

Make sure that there are no failures in the integrations where VersionOne is involved.

  • Go to Failed Events Management from the dashboard.
  • Check whether there are failed events for VersionOne or not.
  • In case there are no failed events. You can continue with your migration process of OpsHub Integration Manager.
  • In case there are any failed events. You will have to resolve them as per requirement before you can proceed with OpsHub Integration Manager Migration.

Migrating Version to 6.11 Update 2 HF2 or above

Users Checklist

There should not be any user in OpsHub Integration Manager with username opshub_internal or Migration.

  • Go to User Management > User Group Management > View Users
  • Confirm that there should not be any user with username opshub_internal or Migration
  • If there is any user with these usernames then edit the user and modify username

Migrating Version to 6.14 or above

Workflow associations to Integrations Checklist

Example: If “Default Integration Workflow” is associated with “Create” event in an integration more than once.

Starting from 6.14 this relationship has been restricted to be unique. Multiple associations with same event will no longer be possible in the same integration, since they are redundant. Before migration, all such duplicate associations are mandatorily required to be removed.

  • Also ensure that, same workflow associations are associated with every event type. Example: If “Default Integration Workflow” is associated with “Create” event, and “Default Integration Workflow 1” is associated with “Update” event in an integration.

Starting from 6.14 workflow and integration association is independent of event types.

Migrating Version to 6.14 U2 HF1 or above.

Remove the default link setting

This checklist applicable only if your current version is 6.14 U2 HF1 or 6.14 U2 HF2 and you are migrating to any x version which is > 6.14 U2 HF1 or > 6.14 U2 HF2. Further you have any default link settings configured at your instance. Perform following step prior to migration, if meeting above condition.

  • Edit the mapping where you have default link setting configured.
  • Remove the Default Link settings.
  • Save the mapping.
  • Repeat step 1 to 3 for all the mapping where default link setting configured on current version 6.14 U2 HF1 or 6.14 U2 HF2 version.

Why this checklist requires and how to restore default link setting back after migration? Default link configuration parameters has been changed from version higher than 6.15 hence user need to remove older default link settings prior to migrating from 6.15 version. After migration you can restore default link settings by reconfiguring the default link again as per the new settings. For more details on how to configure default link from 6.15 version onwards refer the Default Link setting section of OpsHub Integration Manager Guide under field mapping section.

Migrating OpsHub Integration Manager to version 7.6 or above pre-requisites

Enhancement in Jira System Configuration for Cloud(on-demand/SaaS) instance

Applicable For: If you have configured jira system for Cloud(on-demand/SaaS) instance.

  • Jira is going to deprecate Jira Username and Jira Password for Jira cloud API. Along with that OpsHub Integration Manager is also deprcating jira username and jira password for system configuration. Instead of that OpsHub Integration Manager is allowing Jira UserEmail and Jira API Token for system configuration. Make sure you have Jira UserEmail id and API Token which has system administration privileges (Refer this link for finding an API Token).

Migrating OpsHub Integration Manager version to 7.11 or above

Changing Jira User Name to Jira User Account Id for Jira Cloud (on-demand/SaaS) instance

Applicable When: You have configured Jira system for Cloud (on-demand/SaaS) instance.

  • After upgradation, on activation of integration, the integration(s) that are associated with Jira cloud system will be paused until Jira User Name to account id migration job is executed. While execution of Jira User Name to account id migration, other Jira cloud integration sync log(s) will show this error message, “Poller pre-processing for system [SystemName] with integration “[IntegrationName]” is in-progress, hence this integration can’t be executed. Once the pre-processing is completed, this integration will resume its processing if it is in Active state. Make sure your integration “[IntegrationName]” is in active state.”

DEPRECATED: Updating multiple XSL templates into a single advanced XSL template

Deprecated Functionality: Using more than one XSL tag in the Advanced XSL of a single field.

Applicable When: You have configured advanced XSL of an element in a way that there is more than one XSL snippets in the advanced XSL of a single element.

  • If you have more than one XSL snippet in the advanced mapping of a single element like in the example shown below, you’ll have to update it to ‘use only one XSL tag’. Updating multiple elements from a single advanced XSL may be removed in the future versions of OpsHub Integration Manager.
    <xsl:template name="tokenizeList" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
        <!-- Some other tags -->
    </xsl:template>
    
    <xsl:template match="SourceXML/updatedFields/Property/Expected-space-Result" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" >
        <!-- Some other tags -->
    </xsl:template>
  • So for example, if you want to edit the advanced XSL of ‘Description’ field whose default advanced XSL looks like the XSL shown below, you must only update the content inside and . Do not add/edit advance XSL of another field in the XSL of this field.
    <Description>
      <xsl:value-of xmlns:xsl="http://www.w3.org/1999/XSL/Transform" select="utils:convertWikiToHTML(SourceXML/updatedFields/Property/description)"/>
    </Description>
  • Given below is an example of an invalid XSL. Here in the advance XSL of the ‘Description’ field, there is an additional XSL tag to edit the ‘Summary’ field. Remove any such mappings from your OpsHub Integration Manager instance.
    <Description>
      <xsl:value-of xmlns:xsl="http://www.w3.org/1999/XSL/Transform" select="utils:convertWikiToHTML(SourceXML/updatedFields/Property/MyDescription)"/>
    </Description>
    
    <summary>
      <xsl:value-of xmlns:xsl="http://www.w3.org/1999/XSL/Transform" select="SourceXML/updatedFields/Property/MyCustomSummary"/>
    </summary>

Migrating OpsHub Integration Manager version to 7.18 or above

OpsHub Integration Manager host URL checklist

Applicable when: Hostname for OpsHub Integration Manager contains special characters except “-” and “.”

Reason: Due to security concerns, special character except “-” and “.” are disabled for the hostname. A “hostname” (Net, Host, Gateway, or Domain name) is a text string up to 24 characters drawn from the alphabet (A-Z), digits (0-9), minus sign (-), and period (.). Note that periods are only allowed when they serve to delimit components of “domain style names”. For more details, read the memo RFC-921 and RFC-952.

Actions: Please correct the hostname for OpsHub Integration Manager instance, refer memo RFC-921 and RFC-952 for valid hostname details.