Upgrade the Hubs

In this article, learn how to upgrade the hubs. We recommend that you upgrade your secondary hubs to the version that is installed on your primary hub.
uim902
In this article, learn how to upgrade the hubs. We recommend that you upgrade your secondary hubs to the version that is installed on your primary hub.
2
Considerations
Review the following considerations:
  • The contents of the hub configuration file (hub.cfg) are retained during the upgrade. When a hub is upgraded, other packages are not affected.
  • From UIM 9.2.0 onward, hub/robot- and probe-level licensing requirements have been removed. Deploy the hub, robot, and distsrv versions released with the latest UIM to remove the license dependency. If you want to continue with the older versions of hub and probes that require an extension of the license, contact Support so that they can assist you in extending the license (if required). We recommend taking a backup of the existing licenses before upgrading to UIM 20.3.0.
  • The robot version must always be higher than or equal to the hub version. Also, ensure that the required versions of java_jre, robot_update, and attr_publisher are already deployed on the secondary hub robots.
  • UIM uses OpenJDK instead of Oracle JDK. For more information about the OpenJDK usage in UIM, see Adopting OpenJDK.
  • For more information about upgrading to secure hubs (hub_secure), see Secure Hub and Robot.
Upgrade a Hub Using the Admin Console
You can deploy a package from the local archive of any hub that has the automated_deployment_engine probe to any robot in your infrastructure.
Follow these steps:
  1. Log in to Admin Console.
  2. Select a hub, and then select the
    Archive
    tab.
    Columns in the archive will display the local archive version of the hub currently installed and the version available from the web, if a newer one exists. You can have more than one version of a probe in the archive, and deploy any of the versions to the hub or to another robot.
  3. If a newer version of a probe in the local archive exists in the web archive, an update link will appear in the local archive column. Click on this link and enter valid credentials to download the newer package. A verification dialog box appears to verify the update.
  4. Select the check box next to the hub name and then select the vertical dots icon (Screen Shot 2016-03-08 at 4.00.44 PM.png) or the
    Actions
    menu and the
    Deploy
    option.
  5. In the dialog box, select a hub for deployment.
  6. Click the
    Deploy
    button.
The page redirects to the
Deployment Activity
tab where you can monitor the deployment progress.
Verify a Hub Package is Deployed in Admin Console
After a package has been deployed to a robot, if the package is a probe, it is displayed in both the
Installed Packages
tab and the
Probes
tab. If the package is not a probe, it is only displayed in the
Installed Packages
tab.
Follow these steps:
  1. Select the hub.
  2. Select the
    Installed Packages
    tab.
You can also select the robot for the hub, click on the Installed Packages tab, and view all installed packages, including the new hub.
Upgrade the Hubs Using the Infrastructure Manager
You can deploy a package from the local archive of any hub that has the automated_deployment_engine probe to any robot in your infrastructure.
Follow these steps:
  1. Launch Infrastructure Manger on your upgraded primary hub (or another hub with an updated archive).
  2. Locate the
    hub
    probe in the
    Archive
    .
  3. Drag-and-drop the probe onto the icon of the hub that you want to update.