Upgrade Overview

This topic provides an overview of upgrading Operations Hub.

To access Operations Hub new features and improvements, make sure to upgrade to the latest version of the application.

You have the option to upgrade Operations Hub with or without purging the database (DB).

With DB Purge

This approach provides the option to purge the Operations Hub database during uninstallation:

  1. Uninstall the current version of Operations Hub on your machine.
  2. Proceed to install the new version of Operations Hub.

This fresh installation will incorporate the latest enhancements and bug fixes.

Without DB Purge

Install or upgrade the new version of Operations Hub without uninstalling the previous version. This approach does not involve database purging.

If upgrading Operations Hub without purging the database, ensure that you follow these guidelines to prevent login issues:
  • Provide the same user name and password that you gave during the initial installation. Consistency in user credentials is crucial for a seamless transition.
  • If you provide a different set of credentials other than the tenant admin credentials used in the initial install, the user ID will not match with the existing Proficy Authentication (UAA) records. As a result, users will not be able to log into Operations Hub.

Troubleshooting Upgrade Issues

ch_admin user does not acquire the iqp.user privilege during upgrade: During Operations Hub upgrade from version 2022.6 to 2023 or later, the user ch_admin does not receive the iqp.user privilege by default. As a result, when the user ch_admin tries to create apps and initiates the runtime, an unexpected Access Denied error is encountered.

Workaround: As a temporary remedy, you can manually fix this issue by assigning the iqp.user group to the ch_admin user. Access the user record to modify and add the group:
  • Log in to the Classic Operations Hub interface and access the user record, (OR)
  • Log in to Configuration Hub and access the user record under Proficy Authentication.

The workaround would ensure that apps generated under the ch_admin account can be accessed without encountering any access-related issues.