Upgrade a Multiple OC Configuration

In this article, learn how to upgrade a multiple OC configuration. You run the upgrade and complete post-upgrade tasks.
uim203
In this article, learn how to upgrade a multiple OC configuration. You run the upgrade and complete post-upgrade tasks.
  • Note that the "Upgrade Operator Console" and "Upgrade a Multiple OC Configuration" are two separate procedures. Based on your setup, you can follow the appropriate procedure.
  • To upgrade from a previous version of OC to OC 20.3.3, use the OC 20.3.3 upgrade installer available with the UIM 20.3.3 upgrade release. For more information about UIM 20.3.3, see the UIM 20.3.3 article.
  • UIM 20.3.3 has removed dependency on CA Business Intelligence (CABI) for rendering the native OC screens: Home page, Group view page, Device view page, and Monitoring Technologies (probes) view page. Custom and Out-of-the-Box dashboards and reports are still rendered by using CABI; that is, they have a dependency on CABI. However, the native OC screens are no longer dependent on CABI (Jaspersoft) and are rendered by using HTML5. For more information about the native OC screens using HTML5, see the Configuring and Viewing Monitoring Data article or the "Removing CABI Dependency (Native Operator Console)" section in the UIM 20.3.3 article.
  • To upgrade from a previous version of OC to OC 20.3.2, use the OC 20.3.2 upgrade installer available with the OC 20.3.2 patch release. For more information about the OC 20.3.2 patch, see the OC 20.3.2 Patch article.
  • To upgrade from OC 20.3.0 to OC 20.3.1, use the upgrade installer for Operator Console that the UIM 20.3.1 patch contains. Note that UIM 20.3.1 is a patch release over UIM 20.3.0. The UIM 20.3.1 patch does not include any upgrade installer for the UIM Server. The patch includes the OC upgrade installer along with the separate standalone artifacts that you can use to upgrade the respective components to 20.3.1. For more information about the artifacts that are available as part of the UIM 20.3.1 patch release, see the UIM 20.3.1 article.
2
Run the Upgrade
To upgrade a multi-OC environment, follow the information in this section.
For 20.3.3
Run the OC installer on the primary hub and navigate to the
Select Robot
dialog. Select the robot where you want to upgrade the existing OC instance. In 20.3.3, a new option
Specify IP
is also available in the
Select Robot
dialog. This option is in addition to the already existing
Choose
option. You can select the
Specify IP
option and directly enter the IP address of the robot where you want to upgrade the OC instance. The installer identifies that an older version of the OC is already available on the robot and prompts a message stating that you are going to upgrade the OC instance. You can then proceed with the remaining steps to upgrade the instance.
For more information about the steps, see Install Operator Console (OC).
Prior to 20.3.3
  1. Deactivate the wasp probe on the secondary OC server.
  2. Deactivate the robot running the secondary OC server.
  3. Execute the OC installer from the primary hub, and select the primary OC server as the target.
    Verify that your first OC is working correctly. Also, take a backup of your database.
  4. Deactivate the wasp probe on the primary OC server.
  5. Restart the robot running the secondary OC server.
  6. Clean up the existing UMP webapps before upgrading to OC on the secondary OC server. Below are the UMP webapps that need to be deleted:
    • cloudmonitor
    • listdesigner
    • listviewer
    • mobile
    • mytickets
    • policyeditor
    • qoschart
    • relationshipviewer
    • reports
    • reportscheduler (UMP reportscheduler)
    • servicedesk
    • slareports
    • unifiedreports
    • usm
    • saml-portlet
    • ump-theme
    • portal-compat-hook
    • ump-read-only-theme
    Follow the below steps to clean up UMP webapps:
    1. Remove these webapps sections from wasp.cfg of the secondary OC server. This can be done in two ways:
      1. Open the wasp.cfg in Raw Configure and delete the listed webapps sections under the webapps folder using the Delete Section option.
      2. Open the wasp.cfg in Edit mode and remove the sections under the webapps.
    2. Deactivate the wasp.
    3. Delete these webapps folders from \Nimsoft\probes\service\wasp\webapps.
    4. Delete the .war files of these webapps from \Nimsoft\probes\service\wasp\webapps.
    5. Restart the wasp.
  7. Drag the following packages from the Archive in the below order to the secondary OC server:
    • java_jre
    • wasp
    • wasp_service_wrapper
    • nisapi_wasp
    • ump
    • ump_operatorconsole
    • wasp_alarmviewer_api
    • policy_management_ws
    • mcsuiapp_portlet
    • ump_cabi
    • ump_accountadmin (Optional)
    • ump_dashboard (Optional)
      Ensure that you drag each of the ump_<portlet_name> packages that are required for your environment from the Archive.
  8. If the following keys and addresses are not already present, add them to wasp through the Raw Configure option, ump_common section:
    • maintenance_mode = /<domain>/<hub>/<UIM_server>/maintenance_mode
    • udm_manager = /<domain>/<hub>/<UIM_server>/udm_manager
    • mpse = /<domain>/<hub>/<UIM_server>/mpse
  9. Activate, and then deactivate, the wasp probe.
  10. Activate the wasp probe on the primary OC server.
  11. When the wasp is running on the primary OC server, activate the wasp on the secondary OC server.
These manual steps (Prior to 20.3.3) will work for 20.3.3 also. However, it is recommended that you use the OC 20.3.3 installer as explained in the "For 20.3.3" section while upgrading from an earlier version of OC to OC 20.3.3.
You have successfully upgraded the multiple OC server configuration.
Complete Post-Upgrade Tasks
Complete the following tasks after the upgrade is complete:
Clear Browser After Upgrading
If you upgraded from a previous OC version, clear your browser completely to remove older versions of components that might be cached.
You do not need to perform this step if you are upgrading from an earlier version of OC to OC 20.3.2 or later.
Follow these steps:
  1. Log out from OC.
  2. Clear the browser cookies and cache.
  3. Exit all browser windows.
  4. Log in to OC.