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

OpsHub Post Migration Instructions

Version-wise checklist to be executed after migration are mentioned in this document. Kindly go through all the version-wise sections from your installed OpsHub version to the version you migrated one by one and fulfill each one of them to make things work successfully after migration.

Note: It is required to fulfill migration check list(s) of each version(s) which comes within the up-gradation range. E.g. migrating OpsHub from 5.8 version to 5.15 in this case it is required to performed check list(s) for all version ranging from 5.9 to 5.15 in sequence. Check here [#Migrating OpsHub to version 5.9 or above post-requisites]

Upgrade system proxy

HP ALM/QC Proxy Up gradation

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

  • Open IIS (Internet information service) Manager, expand server, expand sites and select the site which you created earlier for HP ALM/QC Proxy.
  • Stop the proxy by clicking Stop link under the Manage Web Site menu.
  • Navigate to (C:\Inetpub\wwwroot\) and delete HPQCWebService folder.
  • Navigate to \Other_Resources\Resources directory.
  • Extract HPQCWebService.zip from above directory to IIS directory (C:\Inetpub\wwwroot\). This will create opshub directory inside the extracted zip folder.
  • If you have changed the path of log file, then you need to perform the following again.
  • Open web.config from HPQC Web Service application in notepad and change following properties: Set value of “value” attribute ofelement under with the valid path to logger file that has appropriate write permission for logging. For example, we will save logs to the C:\logs\ folder so the setting will look like this: IBM Rational RequisitePro

    • Go to Windows Services and look for a service with the name OpsHub ReqPro Service. “Stop” the service if its status is ‘Started’.
    • Open command prompt with administrative privileges and type the following command:sc delete ‘OpsHub ReqPro Service’. Press enter. It will delete the registered OpsHub ReqPro Service.
    • Navigate to \Other_Resources\Resources directory.
    • Delete previously extracted OpsHubReqProWebService folder from above directory.
    • Then extract OpsHubReqProWebService.zip from above directory.
    • Execute registerReqProWCFService.bat with Run As administrator privileges.
    • Once command get executed, go to Windows Services and look for service with name OpsHub ReqPro Service. Check if the service is started or not. If the service is started, then stop the service.
    • Right click on OpsHub ReqPro Service, Go to Properties Click on Log on Tab, Select This Account option and provide required information for this account.
    • Start the OpsHub ReqPro Service.
    • Test the web service by opening this URL in browser http://:<9191>/ReqProService. E.g. http://localhost:9191/ReqProService.

    Team Foundation Server ALM System / Visual Studio Online

    • Go to Windows Services and look for a service with the name OpsHubTFSService. Stop the service if its status is ‘Started’.
    • Open command prompt with administrative privileges and type the following command:sc delete ‘OpsHubTFSService’. Press enter. It will delete the registered OpsHubTFSService.
    • Navigate to \Other_Resources\Resources directory.
    • Delete previously extracted OpsHubTFSService folder from above directory.
    • Then extract OpsHubTFSService.zip from above directory.
    • Open command prompt with Administrator privileges and navigate to extracted folder where registerTFSWCFService.bat resides, and execute ‘registerTFSWCFService.bat’ from command prompt.
    • Once command get executed, go to Windows Services and look for a service with the name OpsHubTFSService and check if the service is started or not. If not, then start the service.
    • Test the web service by opening this URL in browser http://:<9090>/TFSService. E.g. http://localhost:9090/TFSService.

    Team Foundation Server Version Control System

    • Go to Windows Services and look for a service with the name OpsHubTFSService. Stop the service if its status is ‘Started’
    • Open command prompt with administrative privileges and type the following command:sc delete ‘OpsHubTFSService’. Press enter. It will delete the registered OpsHubTFSService.
    • Navigate to \Other_Resources\Resources directory.
    • Delete previously extracted OpsHubTFSService folder from above directory.
    • Then extract OpsHubTFSService.zip from above directory.
    • Open command prompt with Administrator privileges and navigate to extracted folder where registerTFSWCFService.bat resides, and execute ‘registerTFSWCFService.bat’ from command prompt.
    • Once command get executed, go to Windows Services and look for a service with the name OpsHubTFSService and check if the service is started or not. If not, then start the service.
    • Test the web service by opening this URL in browser http://:<9090>/TFSService. E.g. http://localhost:9090/TFSService.

    Visure

    • Go to Windows Services and look for a service with the name OpsHubVisureService. Stop the service if its status is ‘Started’.
    • Open command prompt with administrative privileges and type the following command:sc delete ‘OpsHubVisureService’
    • Press enter. It will delete the registered OpsHubVisureService.

    • Navigate to \Other_Resources\Resources directory.
    • Delete previously extracted OpsHubVisureService folder from above directory.
    • Then extract OpsHubVisureService.zip from above directory.
    • Open VisureWebService.exe.config in a text editor. At the end of that file find the following line.
    • Set the value to a folder location where the Local System has write access. (This step can be skipped if your Local System has adequate write permissions in the Local Drive C: )

    • Open command prompt with Administrator privileges and navigate to extracted folder where registerVisureWebService.bat resides, and execute ‘registerVisureWebService.bat’ from command prompt.
    • You will be asked for the version of Visure you are using. Provide the version and press enter. And if in case command prompt asks to overwrite any dlls, give ‘y’.
    • Once command get executed, go to Windows Services and look for service with name OpsHubVisureService, check if the service is started or not. If not, then start the service.
    • Test the web service by opening this URL in browser http://:<9292>/VisureService. E.g. http://localhost:9292/VisureService.

    Enterprise Architect

    Migrating to version 6.3 and above

    If you are configuring OpsHubEAWindowsService for the first time, then you need to refer section, 6.39.1 Prerequisites under the topic 6.39 Enterprise Architect in OIMGuide6.3.pdf. If you have already configured OpsHubEAWindowsService before, please follow the steps mentioned below.

    • Go to Windows services. Find the service with the name OpsHubEAWindowsService. Stop the service if its status is ‘Started’.
    • Open command prompt with administrative privileges and type the following command:sc delete ‘OpsHubEAWindowsService’
    • Press enter. It will delete the registered OpsHubEAWindowsService.

    • Navigate to \Other_Resources\Resources directory.
    • Delete previously extracted OpsHubEAService folder from above directory.
    • Then extract OpsHubEAService.zip from above directory.
    • Open EAService.exe.config in a text editor. At the end of that file find the following line .
    • Set the value to a folder location where the Local System has write access. (This step can be skipped if your Local System has adequate write permissions in the Local Drive C: ).

    • Right click on registerEAService.bat and select Run as administrator.
    • After the bat file is executed, go to Windows Services and look for service with name OpsHubEAWindowsService, right click on it and select Properties. In the Properties window, go to Log On tab and check if the Local System account is selected. If not, please select it and click on Apply then click OK. Restart the service.
    • Test the web service by opening this URL in browser http://:9393/EAService. E.g. http://localhost:9393/EAService.

Migrating OpsHub Version to 6.10 or above

LDAP server Configurations

This step is applied if the user is migrating from any older version of OpsHub Integration Manager to OpsHub Integration Manager 6.10 or above and the user has already configured the LDAP server configuration in OpsHub Integration Manager. From OpsHub Integration Manager 6.10 onwards, For User Name field of LDAP server configuration it is required to set complete distinguished name (DN) or userPrincipalName (UPN) of the connection user. This user used to connect to the LDAP server. And Expected format is DN or UPN of the connection user. Example, user@domain.name or cn=user,cn=users,dc=domain,dc=name. Perform following steps:

  • Go to User Management Section, under Login Server Management click on View Login Servers.
  • Repeat following steps for each LDAP server configured at your end.
  • Click on Edit to update the server configuration, change Username value to either complete distinguished Name (DN) or userPrincipalName (UPN) of already set username.
  • Say for example, current user name value set as: CN=testuser now you require to change this to complete DN or userPrincipalName of user. Such as either set value as: cn=testuser,cn=users,dc=domain,dc=name. or testuser@domain.com . In case you want to provide username in userPrincipalName format then please note before providing the userPrincipalName value for connection username, check your ldap sever having the value set for the userPrincipalName attribute in the format of user@domain.name.

  • Click on Test Server Connection, to check connectivity with the changed username value in new format.
  • Click on Saver Configuration, to update the changes.

Workflow changes

After migration to OpsHub Integration Manager 6.10 or above version, Work flow name will be automatically changed. Postfix _OHOld will added to all existing workflow prior to migration. No action need to take on user side. This is for the information. Say for example, before migration the workflow name is Default Integration Workflow then after migration to OpsHub Integration Manager 6.10 or above, Workflow name changed to ‘Default Integration Workflow _OHOld’

Migrating OpsHub Version to 6.10 Update2 or above

VersionOne System Configurations

This step is applied if the user is migrating from any older version of OpsHub Integration Manager to OpsHub Integration Manager 6.10 Update 2 and the user has already configured the VersionOne system. From OpsHub Integration Manager 6.10 Update 2, VersionOne Time Zone field has become mandatory to be given while creating VersionOne system, with default value being ‘EST’ (for cloud deployments).If the timezone where VersionOne is deployed is other than ‘EST’, select the appropriate timezone from the dropdown menu.

Migrating OpsHub Version to 6.11 Update1 or above

HTTPS SSL Certificates Alias Name Configurations

Follow the instructions given below if you have installed an older version (version older than 6.11 U1) of OpsHub in HTTPS mode, and you are now migrating to a version greater than or equal to 6.11 U1 of OpsHub.

Situation 1: If you know the HTTPS certificate alias name given during OpsHub Integration Manager installation, then you can directly go to step number 6.

Situation 2: In case you have forgotten the alias name given during OpsHub Integration Manager installation, follow the steps mentioned below:

  • Open Command Prompt in Administrator mode and navigate to \OpsHubServer , and execute the command given below.

OpsHub_Resources\jre\bin\keytool.exe -list -v -keystore OpsHub_Resources/jre/lib/security/cacerts > Certificates.txt

  • The system will ask for password. Use the default password “changeit”.

If the default password doesn’t work and you suspect it has changed, then go the \opshubserver\conf\server.xml>, and check the password given under node as ‘keystorePass’ attribute. Once you have the password, execute the command mentioned in first step and re-enter the changed password.

  • The certificate details will be exported in ‘Certificates.txt‘ file.
  • Now, check the alias name by using the ‘PrivateKeyEntry‘ keyword in ‘Certificates.txt’ (generated in step number 1). It will show a ‘certificate entry’ as shown below. The required alias name can be known from this ‘certificate entry’, which in this case is ‘tomcatalias2‘.

Alias name: tomcatalias2 Creation date: Mar 2, 2017 Entry type: PrivateKeyEntry Certificate chain length: 1 Certificate[1]: Owner: CN=DESKTOP-QMNPA55, OU=Your Company Name, O=Your Company Name, L=Ahmedabad, ST=Gujarat, C=IN Issuer: CN=DESKTOP-QMNPA55, OU=Your Company Name, O=Your Company Name, L=Ahmedabad, ST=Gujarat, C=IN Serial number: 3b591623 Valid from: Thu Mar 02 18:08:26 IST 2017 until: Fri Jun 30 18:08:26 IST 2017 Certificate fingerprints: MD5: 3B:8D:EB:28:23:FA:90:DC:52:AA:79:38:66:50:69:76 SHA1: 9D:65:84:6B:A4:9D:80:9A:59:53:27:7D:00:DA:0E:CB:7E:13:14:93 SHA256: D9:16:DF:32:B7:EE:6B:C1:17:CF:61:3E:D1:AC:97:5C:6B:F1:89:68:74:3C:68:05:25:81:EF:C5:30:EF:4D:7B Signature algorithm name: SHA256withRSA Version: 3

Extensions:

1: ObjectId: 2.5.29.14 Criticality=false SubjectKeyIdentifier [ KeyIdentifier [ 0000: 76 18 F0 50 82 1D B0 90 0C D8 90 89 9C 64 FB 58 v..P………d.X 0010: 1B A3 DA 85 …. ] ]

  • Open the file \OpsHubServer\conf\server.xml.
  • Navigate to the section for configuring connector for HTTPS (which looks like the one shown below).

maxThreads="150" scheme="https" secure="true"
              clientAuth="false" sslProtocol="TLS" sslEnabledProtocols="TLSv1,TLSv1.1,TLSv1.2" 
              ciphers="TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA256, TLS_RSA_WITH_AES_256_CBC_SHA" 
              keystoreFile="C:\Program Files\OpsHub_HSQL_ALIAS_6_10\OpsHub_Resources\jre\lib\security\cacerts" keystorePass="changeit" server="OpsHub Server"/>
  • Add the key alias found in step number 4 as keyAlias=”tomcatalias2” in the connector tag mentioned above.

Once you complete this step, the connector tag will look like the code shown below. ‘tomcatalias2’ is the alias found in this case. Please note that you have to enter the alias name found at your end.

maxThreads="150" scheme="https" secure="true"
              clientAuth="false" sslProtocol="TLS" sslEnabledProtocols="TLSv1,TLSv1.1,TLSv1.2" 
              ciphers="TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA256, TLS_RSA_WITH_AES_256_CBC_SHA" 
              keystoreFile="C:\Program Files\OpsHub_HSQL_ALIAS_6_10\OpsHub_Resources\jre\lib\security\cacerts" keyAlias="tomcatalias2" keystorePass="changeit" server="OpsHub Server"/>
  • Restart your OpsHub server, and you are done with the post-migration steps for properly configuring the alias name for HTTPS SSL certificates in OpsHub.

Migrating OpsHub Version to 6.12 Update1 or above

Zendesk comments mapping change

This step is applicable for all mappings where one of the end point is Zendesk system, as from OpsHub Integration Manager Version 6.12 U1 onwards HTML formatting is supported for Zendesk comments. Therefore, if comments are mapped/enabled in existing mappings, user needs to remap the comments as below.

Note: In case advance mapping is done for comments please take its backup and apply the similar logic as earlier advance mapping, after re-enabling comments checkbox. Please contact support@opshub.com for help in case required for advance mapping case?

Edit the mapping -> uncheck the comments option from mapping and check (Enable) again -> save the mapping. Above steps are to be repeated for all mappings where one of the end point is Zendesk system.

Migrating OpsHub Version to 6.12 Update2 or above

Jama Relationship mapping change

This step is applied when the user is migrating from any older version of OpsHub Integration Manager to OpsHub Integration Manager 6.12 Update 2 and the user has already configured integration with one of end point as Jama System and further relationship mapping is also configured.

As from version 6.12 Update2 and above, upstream relationships of Jama are also supported, the existing relationships name changes. Therefore, the user needs to remove the existing relationship and remap with newly added relationship name. Now, for every relationship, there will be two types: 1. Downstream and 2. Upstream.

For example, if mapping is configured with Related to relationship, then user is required to remove the Related To relationship and remap with Related to (Downstream) relationship.

Migrating OpsHub Version to 6.14 or above

VersionOne mapping change

This step is applied when the user is migrating from any older version of OpsHub Integration Manager to OpsHub Integration Manager 6.14 and the user has already configured mapping with target system as VersionOne.
From version 6.14 and above, the projects can be mapped using only Project Path. Therefore, the user needs to remove the existing mapping of Project id and Project, and add a field mapping of Project Path with their corresponding project. When the mapping is opened after migration, above fields will be shown as invalidated.

Validate mapping state for attachments, comments and links

The below post migration steps is applicable to below two cases:

  • If you are migrating from 6.12 U1 and if any mappings were created or updated in same version
  • If you are migrating from 6.12 U2 or 6.14 HF 2 and if any old mappings were updated in these versions.

Then after migrating with latest version of 6.14 there can be two scenarios.

Scenario 1: You need to validate the mapping state. If your mapping is in unchecked state for attachment, comments or links in previous version then there is a possibility that they are checked and we need to disable it by updating the mapping.

For example: Jira to Rally mapping is configured without comments, then you need to validate whether the comments checkbox in unchecked or not, if not then just update the mapping by uncheck the comment check box and save it.

Scenario 2: If you face any failure event stating attachments, comments or links operation not supported, then just update the mapping by clicking on edit button and just save it.

Note: Second scenario may occur for the entity that doesn’t support attachments, comments, or links.

IBM Rational Team Concert System Configurations

This step is applicable if the user is migrating from any older version of OpsHub Integration Manager to OIM6.14-HF5 or higher and the user has already configured the IBM Rational Team Concert system. From OIM6.14-HF5, “Rational Team Concert Server TimeZone” field has become mandatory while creating IBM Rational Team Concert system, so edit IBM Rational Team Concert system and select the appropriate time zone value from the dropdown menu (if not selected previously).

Migrating OpsHub Version to 6.14 U2 or above

IBM Rational Team Concert System Jar Location Update

Applicable For: The user using IBM Rational Team Concert in OpsHub Integration Manager. Perform the steps given below:

  • Stop the OpsHub Server Service.
  • Copy all the IBM Rational Team Concert jars from the old location to \OpsHubServer\ lib\ThirdPartyJars\RTC folder.
  • Start the OpsHub Server Service.

Migrating OpsHub Version to 6.15 or above

Azure DevOps Server (TFS) or Azure DevOps Services (VSTS) mapping change

Applicable For: Integration configured from Azure DevOps Server (TFS)/Azure DevOps Services (VSTS) to Azure DevOps Server (TFS)/Azure DevOps Services (VSTS) for Test Suite entity with:

  • Test-Case linkage mapping and
  • Requirement to bring the Configuration and Tester of the Test Case linkage.

Perform the steps given below:

  • Edit the mapping of the Test suite entity configured between the Azure DevOps Server (TFS) systems
  • Click the pencil icon against the Issues Relationship option to edit the script of link mapping
  • Append the following mapping inside the Issues Relationship script box. Script need to append just after the id element. Search for the following element tag. And append the config and tester script just after the id tag.
  • Search for the following id element tag within existing script.
  • <xsl:if test="id!="> 
                               <xsl:element name="id"> 
                                 <xsl:value-of select="id"/>  
                                 <xsl:value-of select="id"/> 
                               </xsl:element> 
             </xsl:if>
  • Append the following script after the above id element tag completed.
  • <config> 
                               <xsl:for-each select="linkProps/Property/config/string"> 
                                 <fieldvalue> 
                                   <xsl:value-of select="."/> 
                                 </fieldvalue> 
                               </xsl:for-each> 
                             </config>  
                            				
                             <testers> 
                               <xsl:for-each select="linkProps/Property/testers/Property/*"> 
                                 <xsl:element name="{name()}"> 
                                   <xsl:for-each select="com.opshub.eai.metadata.UserMeta"> 
                                     <fieldvalue> 
                                       <xsl:value-of select="userName"/> 
                                     </fieldvalue> 
                                   </xsl:for-each> 
                                 </xsl:element> 
                               </xsl:for-each> 
                             </testers>

    Please note, testers are a user field. If your source and target systems have different users then you may need to further update the tester script to do an advance mapping for the tester�s users. Above script will simply write the incoming tester user to target tester field of test case linkage.

  • Now click the Save button in the Issue Relationship dialog box to save the changed mapping.
  • Finally, click the Save to save mapping.

Migrating OpsHub Integration Manager Version to 6.15 U2 or above

Jenkins system configurations password to be changed to Jenkins instance API Token

Applicable For: Integration configured with Jenkins end system

  • There is a change in the field�s display name on Jenkins UI. It has changed from Jenkins User Password to Jenkins API Token. From now onwards, OpsHub Integration Manager will use Jenkins API Token instead of Jenkins User Password. Therefore, it is mandatory for users to update the already configured instances of Jenkins with OpsHub Integration Manager with this change.
  • To get Jenkins API token of your instance, please refer the section 6.40.8.2 of OIMGuide6.15_U2.

Changes in the Advance mappings for converting HTML to plain text

Applicable For: Advance mapping that contains convertHTMLToPlainText(htmltext,true()/false()) method

  • There is a change in the method signature to convertHTMLToPlainText method that is used for converting HTML text to plain text. Now, there is no need to pass boolean true () or false ().
  • You need to change convertHTMLToPlainText(htmltext, true ()/false () to convertHTMLToPlainText(htmltext).

Git system configurations changes

Applicable For: Integration configured with Git

  • Edit all the Git systems and fill value for Git Executable Path, which is the absolute Git Client Path on the machine on which OpsHub is installed, for example C:\Program Files\Git\bin

Migrating OpsHub Integration Manager Version to 7.1 or above

Jama Filter configuration need to be updated if criteria is configured for Jama system.

Applicable For: Integration configured with Jama as a source system.

  • Edit the filter used in integration and update the select project option to current project instead of the actual project name.

VersionOne System Configuration changes

Applicable For: Integrations configured with VersionOne

  • From OpsHub Integration Manager 7.1, VersionOne’s Time Zone field input is changed. If your VersionOne Server Time zone is ‘Eastern Standard Time’ or ‘Eastern Daylight Time’ then no additional steps are needed, but if your VersionOne Server Time zone is different, then edit the VersionOne system and specify the value according to the VersionOne Server Time zone.

IBM Rational ClearQuest System Configuration changes

Applicable For: Integrations configured with IBM Rational ClearQuest

  • From OpsHub Integration Manager 7.3, IBM Rational ClearQuest’s Time Zone field input is changed. If your IBM Rational ClearQuest Server Time zone is ‘Eastern Standard Time’ or ‘Eastern Daylight Time’ then no additional steps are needed, but if your IBM Rational ClearQuest Server Time zone is different, then edit the IBM Rational ClearQuest system and specify the value according to the IBM Rational ClearQuest Server Time zone.

Migrating OpsHub Integration Manager Version to 7.5 or above

Changing Salesforce System Configuration version to Salesforce UI theme.

Applicable For: If you have configured salesforce system.

  • The version field in the System Configuration form of OpsHub Integration Manager will now onward contain Salesforce UI theme instead of the system versions.
  • Follow the steps given below to update this change in the system configuration section:
    • Navigate to Go to OpsHub Integration Manager->Integrations–>Configure Systems ->Salesforce->Edit.
    • If you are using Salesforce Classic UI theme, then change your version to ‘Classic’. If you are using Salesforce Lightning UI theme, then change your version to ‘Lightning’.
    • Click the Save button.

Migrating OpsHub Integration Manager Version to 7.6 or above

Changing of Jira User Name to Jira User Email and Jira Password to Jira API Tokens for Jira Cloud(on-demand/SaaS) instance.

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

  • Jira username and password are going to deprecate soon for Jira cloud API use and allowing Jira Email id and API Token.Along with that OpsHub Integration Manager is allowing to use of user’s email and Jira API token in Jira system configuration for Jira Cloud(on-demand/SaaS).
  • To change the jira user email and jira api token follow below steps.
    • Login into the OpsHub Integration Manager.
    • Navigate to the Integration -> System Configuration.
    • Edit Jira System (Make sure system is configured with Jira cloud instance).
    • Make sure Basic Authentication is selected from Jira Authentication Mode. Since Jira is going to deprecate cookie-based authentication for cloud instance,we also deprecated cookie-based authentication.
    • Make sure Jira Deployment Type is selected as On-Demand.
    • Update Jira User Email and Jira API Token field.(Refer this link for finding an API Token)
    • Click on save once you update email and api token.

Migrating OpsHub Integration Manager Version to 7.7 or above

Treating ServiceNow reference fields as look-up type fields

Applicable For: When you have mapped reference fields in ServiceNow integrations.

  • Going forward, all the reference fields i.e. fields that are referring to some other ServiceNow entity will be treated as look-up type fields. You will be able to do value mapping for such fields just like other look-up type fields.
  • It won’t affect existing integrations with reference fields mapped. If you want to define value mapping for such fields by loading the lookups on the UI, you must remove existing field mapping for that reference field and re-map that field.

Migrating OpsHub Integration Manager Version to 7.9 or above

Added implementation for ServiceNow HTML type fields

Applicable For: When you have mapped HTML fields in ServiceNow integrations.

  • Till now, HTML type fields were treated as Text fields in OpsHub Integration Manager. With this release, we have provided the implementation for HTML fields along with the support for inline image. So, going forward, HTML fields will come as HTML only instead of Text in fields mapping.
  • It won’t affect existing integrations with HTML fields mapped. If you want your mapped HTML field in an existing integration to be treated as HTML only, you must remove existing field mapping for that HTML field and re-map that field.

HTTPS Deployment configuration changes to prevent vulnerability

Applicable For: If you have OpsHub Integration Manager on https, then it is recommended to change OpsHub Integration Manager server settings to prevent vulnerability. The TLSV1.0 and TLSV1.1 protocol are vulnerable and to prevent any security breach, change the settings by following the steps mentioned below:

  • Stop OpsHub Integration Manager server.
  • Open \OpsHubServer\conf\server.xml file in the editor.
  • Find ‘sslEnabledProtocols’ keyword in this file for Connector tag and keep value to TLSv1.2 only so that sslEnabledProtocols attribute will have the following value: sslEnabledProtocols=”TLSv1.2″.
  • Start OpsHub Integration Manager server.

Migrating OpsHub Integration Manager version to 7.10 or above

Behavioral changes for HP ALM fields

Applicable For: Mapped fields for HP ALM integrations

  • Up till the last release, all the HP ALM fields were treated as editable in OpsHub Integration Manager. With this release, whether a field is editable or not will be decided based on the configuration of that field in HP ALM.
  • The change will not affect the existing integrations. If you try to edit the mapping for any field that was previously ‘editable’ and is now ‘read-only’, and that field is mapped on the target side, you will not be allowed to save the mapping. You will have to delete the mapping for this field and only then you can save the mapping.

Migrating OpsHub Integration Manager version to 7.11 or above

Behavioral changes For API Mapping Methods

Applicable For: When you have configured advanced XSLT mapping for any of these APIs: getEmailFromUserName, getUserNameFromEmail, getUserFullNameFromEmail, getEntityFieldValue, getEntityMultipleFieldValue, getEntityFieldValueByQuery and utils:isLookupValueValid.

  • Go to the logs folder in the OpsHub Integration Manager installation directory and open the PostMigrationChanges_V7_11.txt file.
  • In that file you’ll find a table with title MAPPINGS (OHMT_C_scripts). If you don’t find a table with this title in the ‘PostMigrationChanges_V7_11.txt’ file, then it means all your mappings were automatically migrated by the migration process. In this case, then, you don’t have to make any of the changes mentioned below.
  • But if you do find the table and some rows into it, this means you have used the above-mentioned APIs in your mappings which were not automatically migrated. Please follow steps mentioned below to correct your advance mappings.

Migrating Utility Methods:

1. For each row in the ‘MAPPINGS (OHMT_C_scripts)’ table, open the mapping specified in the ‘Mapping Name’ column. Now in that mapping, one of the fields might be using the method specified in the ‘Method Name’ column. Therefore, search all the fields in which advanced mapping is done for the method specified in the ‘Method Name’ column.

  • For example if you are searching for the method ‘getUserNameFromEmail’ in the mapping, you might find something like this in one of the fields: getUserNameFromEmail($workflowId, ‘Jira’, SourceXML/updatedFields/Property/Detected-space-By/userEmail, ‘false’, ‘false’).
  • Here for all the methods, the second parameter i.e the value between the first and second comma (,) will be either the name of your source system or target system. In this case the value between the first and second comma is ‘Jira’.

2. Now for each such method, follow the steps below:

  1. If the name in between first and second comma is that of source system, replace the name with $sourceSystemId.
  2. If the name in between first and second comma is that of target system, replace the name with $targetSystemId.
  • In our example if we consider ‘Jira’ to be target system, the value after replacing it should be: getUserNameFromEmail($workflowId, $targetSystemId, SourceXML/updatedFields/Property/Detected-space-By/userEmail, ‘false’, ‘false’).
  • Therefore, the state of the method will change:
    • from: getUserNameFromEmail($workflowId, ‘Jira’, SourceXML/updatedFields/Property/Detected-space-By/userEmail, ‘false’, ‘false’)
    • to: getUserNameFromEmail($workflowId, $targetSystemId, SourceXML/updatedFields/Property/Detected-space-By/userEmail, ‘false’, ‘false’)
  • Repeat the steps listed above for all the rows in the ‘MAPPINGS (OHMT_C_scripts)’ table.
Note: Please note, After the ‘MAPPINGS (OHMT_C_scripts)’ table, you’ll find another table with title ‘ADVANCED MAPPINGS (OHMT_EAI_mapping_xml)’. Please ignore this table as it only provides additional information for debugging purposes.

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

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

  • If you have used User Name in Advance XSLT during field mapping, then you need to replace it with User Account Id.
  • If you have used User Name Advance integration/ reconciliation workflow configuration, then you need to replace User Name with User Account Id.
  • On activation of integration, the integration(s) that are associated with Jira cloud system will be paused till 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.”