Unsupported content

 

This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Upgrading the Dashboards from 7.7.x and 7.8.x to 7.9.00 with ASSO

The topic describes how to use the GUI installation program to upgrade the BMC Atrium Orchestrator Health and Value Dashboard component. 

Before you begin

  • You must have upgraded the repository and a configuration distribution peer (CDP).
  • The authentication system and the repository must be running.
  • You must have shut down the CDP service and it is recommended that you shut down the OCP (see Starting and stopping product components and services).
  • You must have downloaded the installation files from the BMC EPD website.
  • You must be logged on as an administrator and have administrator rights on the computer on which you install the dashboard.
    • On Microsoft Windows, you must have administrator permissions. 
    • On Linux and Solaris, any non-root user with write permission to the /opt/bmc directory can perform the installation.
      On Linux and Solaris, the non-root user must also have permission to run the following commands:
      • dmidecode -t 1 | grep Manufacturer
      • lsb_release -d
  • You must have completed the Dashboards worksheet for upgrades from 7.7.x and 7.8.x to 7.9.00 with ASSO to record any changes to your system settings.
  • Back up copies of the dashboard property files (see To back up dashboard property files).
  • If you are upgrading from BAO Platform 7.7.x and the Health Dashboard version 1.0 associated with that release, you must have removed some files associated with that installation (see To uninstall the Health Dashboard V1.0). 
  • If you are installing on a Windows computer, ensure that Data Execution Prevention (DEP) is configured to recognize the installation program executable (see Configuring DEP on Windows computers before upgrades).
  • If you are upgrading on a Linux computer, run the rngd service to ensure that the system has adequate entropy (Run the rngd service on Linux computers before upgrades).
  • You must have exited all other programs.

To back up dashboard property files

In these instructions, AO_HOME represents the dashboard installation location.

Make a backup of the two dashboard property files in the AO_HOME/tomcat/webapps/baodashboard/WEB-INF/classes directory: gridmap.properties and gridhosts.properties. Store them in a different location. You can reuse them when you configure the environment to use the dashboards after the installation.

If you are upgrading from 7.8.x, also make a backup of the hdb.properties file (in the same directory).

To uninstall the Health Dashboard V1.0

Note

These steps are only required for upgrades from BAO 7.7.x releases with the Health Dashboard V1.0.  

If you installed the Health Dashboard V1.0, you must manually remove some files associated with that installation prior to installing the dashboards in this release. The files that you need to remove depend on whether you used an existing Tomcat server for the dashboard or you used the Tomcat server included in the dashboard download file.

In these instructions, AO_HOME represents the dashboard installation location.

  1. Make a backup of the two dashboard property files in the AO_HOME/tomcat/webapps/baodashboard/WEB-INF/classes directory: gridmap.properties and gridhosts.properties. Store them in a different location. You can reuse them when you configure the environment to use the dashboards after the installation.
  2. Before uninstalling the files, stop the Tomcat server. 
    From the command line, cd to the AO_HOME/bin directory and stop the Tomcat server by running one of the following commands:
    • UNIX: shutdown.sh
    • Windows: shutdown.bat
  3. Uninstall the dashboard files using the instructions for your Tomcat server usage:
    • Environments using the Tomcat server included with the dashboard download: On the Tomcat server, delete the Tomcat directory and its contents, which include dashboard files.
    • Environments using an existing Tomcat server: On the Tomcat server, navigate to the webapps directory and remove the the following:
      • healthdashboard.war file
      • healthdashboard directory and its contents
  4. You can restart the Tomcat server after removing the files. From the command line, cd to the AO_HOME/bin directory and start the Tomcat server by running one of the following commands: 
    • UNIX: startup.sh
    • Windows: startup.bat

To upgrade the dashboards

  1. Navigate to and start the installation program for your operating system. See Performing the installation for the installation program names.
  2. On the splash screen, select the language in which to view the installation program, and click OK.
  3. On the Welcome panel, review the information and click Next.
  4. On the license agreement panel, select I agree to the terms of the license agreement, and click Next.
  5. On the Installation Type panel, select Upgrade an existing install, and click Next.
  6. Using the upgrade worksheet, enter settings to upgrade the dashboard. 
    The installation program verifies the communication with the repository. If it detects any invalid or conflicting information, it halts the installation process and displays an error message that describes the problem. After you provide valid values, the installation continues.
  7. Click Yes when prompted to restart the server and then click Next.
  8. When you have finished reviewing the installation preview in the Installation Choices Summary panel, click Install.
  9. When the installation finishes successfully, click Done.

Where to go from here

Replace the gridmap.properties and gridhosts.properties files with your backed up copies. For information about the properties in these files, see Configuring your environment to use BMC Atrium Orchestrator dashboards

For upgrades from 7.8.x , replace the hdb.properties file. For information about this file, see Changing dashboard and report default settings.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments