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 and replacing the 1.0 Health Dashboard with the standalone Self-Check Monitor

This topic provides information about how to upgrade and replace the 1.0 Health Dashboard with the standalone Self-Check Monitor utility. 


You can use this topic with version 4.5 of the standalone Self-Check Monitor utility. 

Supported BMC Cloud Lifecycle Management versions

You must be using BMC Cloud Lifecycle Management 3.0, 3.1, 4.0, or 4.1.

Minimum system requirements

To upgrade Health Dashboard, your system must meet the following minimum system requirements.

CategoryMinimum requirement
Operating system

One of the following:

  • Microsoft Windows 2012 R2
  • Microsoft Windows 2008 R2
  • Microsoft Windows 2008
  • Red Hat Enterprise Linux 5.x
  • Red Hat Enterprise Linux 6.x
  • Red Hat Enterprise Linux 7.x

Note: Linux systems must have the X environment to run the BMC Cloud Lifecycle Management Dashboards upgrader.


All of the following:

  • 2 CPUs
  • 4GB RAM
  • 60GB Hard disc space

Any of the following:

  • Microsoft Internet Explorer 9 or greater
  • Mozilla Firefox 26.0 or greater

Java Runtime Environment 7

Ensure that JRE_HOME is in your system PATH variable.

Additional requirements for Health Dashboard and Self-Check Monitor

In addition to the minimum system requirements, ensure that the following requirements are met:

  • You are an Administrator or the root user of the computer on which you will upgrade the Health Dashboard.
  • All BMC Cloud Lifecycle Management component products (such as BMC Remedy AR System, BMC Server Automation, and so on) are accessible from the computer on which you will upgrade the Health Dashboard.
  • On Linux systems, ensure that you have execute permission for the jrel.7.0/bin/java directory.
  • If you are using Microsoft Internet Explorer, ensure that it is not running in Compatibility Mode.
  • clmhealth and Platform Manager services are running on their respective target hosts
  • RSCD Agent is installed on the computer on which you will upgrade the Health Dashboard. 
  • BMC Server Automation Network Shell (NSH) is installed on the computer on which you will upgrade the Health Dashboard. You can use the NSH installer bundled with your BMC Cloud Lifecycle Management installer files (and not the directory of your upgraded BMC Cloud Lifecycle Management solution) in the Applications\BL-NSH directory. For more information about upgrading NSH, see upgrading only the Network Shell (Linux and UNIX) and upgrading only the Network Shell (Windows).
  • On Windows systems, configure the terminal services (gpedit.msc and regedit). 
  • BMC Server Automation NSH on the Health Dashboard server and BMC Server Automation RSCD Agent on the Platform Manager must be configured to use the same port number. 

    1. For example, on the Platform Manager, open the C:\Windows\rsc\secure file and locate the following line: 

    2. Now open the same file on the Health Dashboard server. The following line should have the same port number, in this example 4750: default:port=4750:protocol=5:tls_mode=encryption_only:encryption=tls.

  • The Health Dashboard server must have, at minimum, read access permission to the Platform Manager RSCD agent. For example, on Windows open the C:\Windows\rsc\exports file and locate the following line:
    * rw,user=Administrator

    Use the following command to grand read permission, where ipAddress is the IP address of the Health Dashboard:
    ipAddress r,user=Administrator

  • At any time, only one instance of the clmhealth utility (the Health Dashboard) is monitoring BMC Cloud Lifecycle Management.
  • If you have downloaded the HealthDashBoards-upgrader.zip file on a Windows computer and transferred it to a Linux computer, ensure that you have execute permission for the bundled jre-1.7.0 folder on that Linux computer.

To upgrade and replace the Health Dashboard with the Self-Check Monitor

  1. Download the Self-Checker ZIP file from EPD to the computer on which you want to upgrade the Health Dashboard. 
  2. Unzip the file.
  3. Do one of the following:


    Double-click the setup file.

    The CLM Self-Check Monitors screen appears


    Start the X graphical environment, and then enter the following command:
    ./java -jar setup.jar

    The CLM Self-Check Monitors screen appears.

  4. Review the Welcome panel, and then click Next.
  5. Enter the path for Java Runtime Environment (such as C:\Program Files\Java\jre7), and then click Next

  6. Enter the port numbers used to start up and shut down the Self-Check Monitors server, then click Next.
    Enter the correct protocol (HTTPS is the default), target host, and port (8443 is the HTTPS default). You can modify the URL to use HTTP and port 443. 

  7. In the Custom CA Certificate Configuration panel, enter the certificate information, and then click Next
    The default choice for the Use Existing Certificate option is No, and it was used in this example.

  8. In the Tomcat Web Server Certificate Information panel, review the keystore information, and then click Next.
  9. In the Installation Preview panel, review the upgrade information (from 1.0.00 to 4.5.00), and then click Next.

  10. When processing has completed, click Next.
    The Installation Summary panel appears.

  11. Review the information (especially the new Self-Checker URL), and then click Done.

To onboard the Self-Check Monitor with Platform Manager

  1. In a browser, enter the Self-Checker URL, for example, https://<SelfChecker>:8443/health.
  2. If you configured the HTTPS protocol, your connection is initially distrusted in the browser. Add and confirm the site exception.
  3. In the CLM Self Checker window, review the instructions and then click the Configuration Panel link. 
  4. On the Settings panel, define the Platform Manager settings:

    Platform Manager Host NameName or IP address of Platform Manager
    Platform Manager upgrade PathFull path of Platform Manager upgradeation, for example, C:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Platform_Manager
    Cloud Admin User NameUser name defined when you upgradedPlatform Manager. By default, clmadmin.
    Cloud Admin PasswordPassword defined when you upgradedPlatform Manager.
  5. Click Test PM Connection to verify that your configuration settings are correct. 
    If your connection is successful, you can continue with the configuration.  
  6. If you are using two AR servers, select Enterprise AR settings, and then specify the Enterprise-AR details.
  7. Click On-board to complete the configuration.

To configure email notifications


You must configure the SMTP server details before you can enable and configure email notifications. 
  1. On the Settings panel of the Self-Checker, click Notifications.
  2. Define the email notifications:

    Send Email ToEnter email address of recipient. Separate addresses by commas.
    CCEnter email address of CC (carbon copy) recipients. Separate addresses by commas.
    Notify me if health check status isSelect health check condition. RED (default) is severe and indicates the need for immediate attention. ORANGE indicates that you should monitor that aspect of the component frequently, and consider improvements to improve its health.
    Do not repeat action for at leastSelect how often to notify. 01 Hour is the default. You can choose 05 minutes to 24 Hours.
  3. Click Save
    Make sure that the settings are successfully updated. 

To configure component settings

  1. On the Settings panel of the Self-Checker, click Component Settings.
  2. Define the email notifications:

    BSA Dashboard URLAddress of BladeLogic Server Automation Dashboard. Already entered by default.
    BAO Dashboard URLEnter BMC Atrium Orchestrator URL. For example:
    Health Check Refresh IntervalSelect refresh rate to check the health of your system. You can choose 05 Minutes (default), 10 Minutes, or 15 Minutes.
  3. Click Save
    Make sure that the settings are successfully updated.  

To use an existing Tomcat server for the Self-Check Monitor

  1. Complete one of the following set of steps to set a new -D parameter for the Tomcat server, referencing the location of the BMC Cloud Lifecycle Management configuration.properties file:


    a. In the Control Panel, open the System pane.

    b. Click Advanced System Settings.
    The Advanced tab of the System Properties dialog box opens.

    c. Click Environment Variables.
    The Environment Variables dialog box opens.

    d. Under System Variables, click New.
    The New System Variable dialog box opens.

    e. In the Variable Name field, enter JAVA_OPTS.

    f. In the Variable Value field, enter -DdashboardProperties=path_to_configuration.properties_file

    g. In the New System Variable dialog box, click OK.

    h. In the Environment Variables dialog box, click OK.

    i. In the System Properties dialog box, click OK.

    LinuxEnter the following command:
    export JAVA_OPTS="-DdashboardProperties=path_to_configuration.properties_file"
  2. Locate the dashboards.war file in your Self-Check Monitor upgrade directory.
  3. Copy the dashboards.war file to the webapps folder of your existing Tomcat upgrade.
  4. Update the configuration.properties file of your BMC Cloud Lifecycle Management upgrade.
  5. Stop and then restart the Tomcat server.

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.