Migration is required from current version to higher version as it includes support and feature enhancement from the older version.

Migration Pre-requiste for Windows and Linux

Provide the permissions to database user as mentioned in the Database Selection section of the Installation_Steps page.

Follow instruction as mentioned in Pre-Migration Checklist before starting the upgradation process based on current version of OpsHub Integration Manager installed and version to which OpsHub Integration Manager will be upgraded. (If you do not have access to the Pre-Migration Checklist, log a ticket on our customer portal if you have the access or get in touch with your point of contact (POC) for integration.)

Migration Steps for Windows

Given below are the migration steps:

  • Inactivate all the integrations.
  • Stop Server Service from services.ms
  • Take back up of the database (refer to the

    Please refer OIM_Backup page)

  • Take back up of the application folder (refer to the OIM_Backup page)
  • Go to “/OpsHub_Resources” directory and remove all xml files if available in the directory
  • Extract OpsHubV_Migrator_.zip and execute the migration file
  • It will ask for existing installation path, give the same installation path where you have installed the application
  • Click Next
  • If you are migrating to version 7.12 or above, you need to register by following the steps mentioned here.
  • After successful migration, the server will be started automatically
  • After loading OpsHub Integration Manager UI, please refresh the browser once before doing any operation.

Please refer Post-Migration_Checklist. Verify the version by opening the user interface in browser and check version information at the bottom.

  • Activate all the integrations.
  • Follow the guidelines given in the Post-Migration_Checklist once the migration process is complete.
Note: If any systems having proxy requirement such as Azure DevOps Server (TFS) and HPALM is configured, required to replace proxy files and re-register the proxy services. Please refer Upgrade system proxy of Post-Migration_Checklist page.
Note: Default conflict behavior has changed since version 5.11.

Migration Steps for Linux

Given below are the migration steps:

  • Inactivate all the integrations.
  • To stop the Server service, run this command on command prompt ps -ef | grep “java” to get the PID and then execute kill -9 .
  • If you are running OpsHub Integration Manager without service or without root access stop server as described below:
    • Go to “/OpsHubServer/bin” directory and run shutdown.sh file. It will take some time to stop server.
  • Take back up of the database (refer to the

    Please refer OIM_Backup page)

  • Take back up of the application folder (refer to the OIM_Backup page)
  • Go to “/OpsHub_Resources” directory and remove all xml files if available in the directory
  • Extract OpsHubV_Migrator_.zip and execute the migration file
  • If you are migrating to version 7.19 or above, Please follow steps described in Before Installation section here.
  • To run the sh file, use the following command sh install.sh
  • It will ask for existing installation path, give the same installation path where you have installed the application
  • Click Next
  • If you are migrating to version 7.12 or above, you need to register by following the steps mentioned here.
  • After successful migration, the server will be started automatically
  • After loading OpsHub Integration Manager UI, please refresh the browser once before doing any operation.

Please refer Post-Migration_Checklist. Verify the version by opening the user interface in browser and check version information at the bottom.

  • Activate all the integrations.
  • Follow the guidelines given in the Post-Migration_Checklist once the migration process is complete.
Note: If any systems having proxy requirement such as Azure DevOps Server (TFS) and HPALM is configured, required to replace proxy files and re-register the proxy services. Please refer Section 2 Upgrade system proxy of Post Migration Checklist document.
Note: Default conflict behavior has changed since version 5.11.