Skip to main content

Go-Live Process

Required Items

Before starting the upgrade for go-live, request the following items:

  • Permanent License Key and Temporary Sunset Key:

    • Create a support ticket to obtain these keys.

    • Attach your RepositorySelection.xml file for the new version to the case. This helps support create your permanent key with the correct server and repository information.

    • The sunset key is a 30-to-60-day temporary key designed to help transition from the old version. It allows users to double-check or test anything in the old version after go-live, ensuring everyone uses the new version by the end of the period.

Potentially Required Items

  • ClickOnce Deployment Files: If using ClickOnce, create a support ticket with your new version number to obtain these files.

  • Scheduler Installation Files: If using Scheduler, create a support ticket with your new version number to obtain these files.

  • RepositorySelection.xml File:

    • This file should be saved in the Hubble install path as referenced in the Prior to Installation section.

    • If deploying Hubble to individual workstations, Citrix, or terminal servers, ensure this file and the Hubble desktop software (Hubble MSI file) are available for each additional install.

Preparing for Go-Live

Consider the following for go-live:

  1. Obtaining and Applying a Permanent Key:

    1. Create a support case for your permanent key 2 weeks to 3 days in advance. The turnaround time on key cases is less than 24 hours.

    2. Install the key ahead of time to test it, but you will need to reinstall it after the final backup and restore process.

  2. Distributing the New Version to End Users:

    1. For fewer than ten Hubble users, install Hubble on end-user desktops.

    2. For more than ten users, use the current method (ClickOnce, Citrix, or terminal servers).

    3. Install the new version on all necessary desktops and servers before following the final go-live process.

  3. Installing Scheduler:

    1. Install the new scheduler version as part of the go-live process to avoid running scheduler from both versions simultaneously.

    2. Create a support case for the scheduler MSI file 2 weeks to 3 days in advance.

  4. Ensuring Recent Reports are in the New Version: The final go-live process includes taking a new backup and restoring it into the new version to ensure all recent changes are included.

Final Go-Live Process

  1. Final Backup: Follow the instructions in Object Repository Backup Process to take a final backup from your current version. This is typically done within a 24-hour window of your go-live to obtain the latest report updates made by end users.

  2. Budgeting/Planning Backup: If using Budgeting and/or Planning, follow the instructions in Chapter 2, section "Budgeting/Planning Backup Process" to take your final budgeting backup.

  3. Restore Final Backup: Follow the instructions in Restore the Object Repository Backup to restore the final backup into your latest version.

  4. Apply Permanent Key: Apply your permanent key to the new version. See the section "Apply a New Permanent License Key" below.

  5. Update Profiles: Follow the instructions in Add or Update Profiles. Only edit each profile that exists in your current/old production environment. New or renamed connections and profiles do not need to be edited since the restore did not affect them.

  6. Restore Budgeting/Planning Database Backup: If using Budgeting and/or Planning, follow the instructions in Restore the Budgeting/Planning Database Backup to restore your final budgeting backup into your latest version.

  7. Confirm Login and Report Functionality: Confirm you can log into Hubble reporting for your new version and run a report. If successful, proceed to step 8. Otherwise, resolve any issues before moving on.

  8. Apply Sunset Key: Apply your sunset key to the current/old version. See the section "Apply a New Permanent License Key" below.

  9. ClickOnce Installation: If using ClickOnce, follow the instructions provided by support for the ClickOnce install when you created a ticket for the ClickOnce deployment files.

  10. Ensure New Version Visibility: If using Citrix or Windows Terminal Server, ensure users will see and use the new version.

  11. Inform Users: If using desktop installs, ensure users know to begin using the new version. It is recommended to send instructions to delete the current/old version one to two weeks after go-live to prevent accidental logins to the old version.

  12. Install Scheduler: If using Scheduler, install it now.

Apply a New Permanent License Key

The license key is specific to your object repository. Since this is a new object repository, the license key restored from the backup will not be valid for the new test version of Hubble.

When support or fulfillment sends a new license key, they will include instructions for applying the key. Follow those instructions. Alternatively, details on replacing a license key can be found in the License Keys section of the Administration and Configuration Guide for the version of Hubble being installed, as referenced in Additional Resources.

Was this article helpful?

We're sorry to hear that.

Powered by Zendesk