Unsupported content 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.

Upgrading CLM Self-Check Monitor to version 4.6

This topic provides information about upgrading the CLM Self-Check Monitor utility as a standalone application. 

Supported BMC Cloud Lifecycle Management versions

You must be using BMC Cloud Lifecycle Management 4.5.

Minimum system requirements

To upgrade CLM Self-Check Monitor, your system must meet the following minimum system requirements.

Category

Minimum requirement

Operating system

One of the following:

  • Microsoft Windows 2012 R2
  • Microsoft Windows 2008 R2
  • Microsoft Windows 2008
  • Red Hat Enterprise Linux 5.5
  • 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 installer.

Hardware

All of the following:

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

Browser

Any of the following:

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

Java

Java Runtime Environment 8 (1.8.0_60)

Additional requirements for the CLM 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 CLM Self-Check Monitor.
  • 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 CLM Self-Check Monitor.
  • On Linux systems, ensure that you have execute permission for the jre1.8.0/bin/java directory.
  • If you are using Microsoft Internet Explorer, ensure that it is not running in Compatibility Mode.
  • NSH is a requirement for the Self-Check Monitor to work properly. In version 4.6, NSH is bundled with the Self-Check Monitor installer. 
  • BMC Server Automation NSH on the CLM Self-Check Monitor server and BMC Server Automation RSCD Agent on the Platform Manager must be configured to use the same port number. For example, on the Platform Manager open the C:\Windows\rsc\secure file and locate the following line: rscd:port=4750:protocol=5:tls_mode=encryption_only:encryption=tls. Now open the same file on the CLM Self-Check Monitor 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 CLM Self-Check Monitor 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 CLM Self-Check Monitor:
    ipAddress r,user=Administrator

  • At any time, only one instance of the clmhealth utility (the CLM Self-Check Monitor) is monitoring BMC Cloud Lifecycle Management.
  • If you have downloaded the HealthDashBoards-installer.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.
  • Ensure that JRE_HOME is in your system PATH variable.

To upgrade the CLM Self-Check Monitor

  1. Download the BMC Cloud Lifecycle Management solution from the EPD site or from the Applications folder (for example, ..\..\Applications\SelfChecker).
  2. Start the installer:
    • On Microsoft Windows, double-click the setup.cmd file.

    • On Linux, launch the installer by using Xmanager.
      With Xmanager, X applications installed on remote UNIX based computers run seamlessly with Windows applications side by side.

      You can also use VConsole to launch the installer.

  3. In the lower right corner of the Welcome page, click Next.
  4. Review the license agreement, click I agree to the terms of the license agreement, and then click Next.
  5. On the Installation Prerequisites panel, review all the prerequisites that you must complete before you start the upgrade.

  6. Select the I have read the prerequisites check box and click Next. 
    (optional) Select the Do not display this panel for subsequent installations check box if you do not want to view the prerequisites again during other product upgrades.  

    If you have not completed any of the prerequisites listed on the Installation Prerequisites panel, exit the installer and complete the steps first.

  7. On the Directory Selection panel, navigate to the location on the host where you want to install the planner and click Next.
    The default location is C:\Program Files\BMC Software\Planner.
  8. On the Installation Preview panel, review the information and click Install.
  9. If NSH is not installed, the system prompts you to install it.
    The default location is C:\Program Files\BMC Software\NSH. 
  10. In the Select Installation Type panel, select Upgrade and then click Next.
  11. In the Integrate Disclaimer Information panel, review the guidance.
    Make sure that upgrading does not impact your customizations or your system performance. 
  12. Click I agree to the terms of the disclaimer, and then click Next. 

  13. On the BMC Installation Registry panel, select if you have a backup registry to use or if you are integrating from scratch, and then click Next. 

    The backup registry lists the target hosts and which products were installed on them. This example does not have an registry available to simplify the upgrade process. If you do not have a registry, you must compile your own list of target hosts.

    For more information, see deployment template for other types to implement.

  14. In the BMC AR System Configuration panel, the installer asks if you use one or more AR System servers in your environment.
    Since this example is based on the 4.1 Small Deployment which uses only only AR System server (this also applies to Compact Deployment or RDS stacks), select Yes, I have only one BMC AR System server, and then click Next. If you were upgrading from 3.1.x which uses two AR System servers, you would select No (I have an Enterprise-AR and a Cloud-AR server).
  15. In the Select Deployment Template panel, select the template that matches your requirements (for example, Small Deployment), and click Next.
  16. In the Deployment Tier Selection panel, select Control Tier, and click Next.
    You can upgrade products in the Control Tier, in the Workload Tier, or in both tiers. The default is Both, but this example only upgrades products in the Control Tier.

  17. In the Host Information for a Small Deployment panel, enter all the product hosts in your environment (in this case, especially the CLM Self-Check Monitor host), and then click Next. 
    The installer validates all the hosts on the Control Tier, to ensure a successful integration. You do not need to enter a host name in every field on this panel, just the product hosts currently used in your environment. 

    The Host Information panel performs the integration that, in earlier releases, was a pre-upgrade procedure.

  18. If you are prompted to, enter the operating system user credentials and passwords for the target hosts, and then click Next. 
    You can apply the same credentials for all target hosts. The installer validates the credentials, deploys the RSCD Agent on the target hosts, and performs additional installation actions. 

  1. When the installer finishes integrating all the products, review the products, versions, and hosts listed in the Integration Summary panel, and click Next.

    Note

    After integration, you can review the product versions before and after the upgrade.

  2. In the Select Deployment Type panel, select Upgrade to Cloud Lifecycle Management 4.6.00, and then click Next.
    All product hosts that you integrated with your BMC Cloud Lifecycle Management solution by running the installer are now visible in the Host Information panel. If the host name or the product that you chose for upgrade is incorrect, click Previous to correct the information.
  3. If you are prompted to, enter the operating system user credentials and passwords for the target hosts, and then click Next. 
    You can apply the same credentials for all target hosts. The installer validates the credentials, deploys the RSCD Agent on the target hosts, and performs additional installation actions.  
  4. Review the summary host information, and then click Next.
  1. Review the Welcome panel, and then click Next. 
    The installer copies files to the target server, verifies free space, and so on.
  2. Take a VM snapshot of the target host, and then click Next.

  3. In the NSH panel, review the default NSH installation path (by default, C:\Program Files\BMC Software\NSH), and then click Next.

    NSH is a requirement for the Self-Check Monitor to work properly. In version 4.6, the planner installer upgrades NSH before the Self-Check Monitor upgrade. 

  4. In the Java Information panel, review the settings (the bundled JRE is selected by default), and then click Next. 
    Using the default bundled JRE simplifies SSL configuration, among other advantages. You can also enter the directory path to an external 64-bit Oracle 1.8 JRE 64-bit directory, for example, C:\Program Files\Java\jre8.
  5. Review the HTTPS or HTTP port numbers (the HTTPS default port is 8443) used to start up (8090) and shut down (8007) the CLM Self-Check Monitor server, and then click Next.

  6. In the Custom CA Certificate Configuration panel, enter the certificate information (the default is NO), and then click Next. 
    You can chose to install using the existing self-signed certificate, or you can provide the location of a third-party certificate and password.

    Note

    You must copy the third-party certificate to the target host.

  7. In the Tomcat Web Server Certificate Information panel, review the keystore information or update it as needed (for example, enter and confirm the keystore password), and then click Next.
  8. In the Installation Preview panel, review the information, and then click Install.
  9. In the Installation Summary panel, review the information, and then click Done.

Where to go from here

 

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*