Installing standalone CLM Self-Check Monitor

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

Supported BMC Cloud Lifecycle Management versions

You must be using BMC Cloud Lifecycle Management 4.6. 

Minimum system requirements

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

Additional requirements for the CLM 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 install 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 install the CLM Self-Check Monitor.

• 
  

• 
   On Linux systems, ensure that you have execute permission for the jrel.8.0/bin/java directory for version 4.6.

• If you are using Microsoft Internet Explorer, ensure that it is not running in Compatibility Mode.

• For the Self-Check Monitor to work, install BMC Server Automation Network Shell (NSH) on the CLM Self-Check Monitor host.

  For more information, see Configuring the StackInformation.properties file.
  
  To install NSH, you can use the NSH installer bundled with your BMC Cloud Lifecycle Management installer files (and not the directory of your installed BMC Cloud Lifecycle Management solution) in the Applications\BL-NSH directory. For more information about installing NSH, see Installing only the Network Shell (Linux and UNIX) and Installing only the Network Shell (Windows).

  
  

• 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 jrel.8.0/bin/java directory for version 4.6.

• Ensure that JRE_HOME is in your system PATH variable.

To install the CLM Self-Check Monitor

1. Download the installer.zip file from EPD to the computer on which you want to install the CLM Self-Check Monitor.  
2. Unzip the installer file.

3. Do one of the following:

   Environment	Steps
   Windows	Navigate to the Disk1 folder and double-click the setup file. The CLM CLM Self-Check Monitors screen appears
   Linux	Start the X graphical environment, navigate to the Disk1 folder, and then enter the following command: ./setup.bin The CLM CLM Self-Check Monitors screen appears.

4. Review the Welcome panel, and then click Next. 
   The installer copies files to the target server, verifies free space, and so on.

5. Take a VM snapshot of the target host, and then click Next.

6. Review the Destination Directory (by default, C:\Program Files\BMC Software\SelfChecker or /opt/bmc for Linux), and then click Next. 
   If the path does not exist, you are prompted to accept that the directory will be created. Make sure that you enter a directory with enough space to perform the installation. 

   Note

   For Linux installations the path must not contain spaces.

7.  

8. 
   

   Select the Use Bundled JRE option to simplify SSL configuration (among other advantages), and then click Next. 

   You can also enter the directory path to an external 64-bit Oracle 1.8 JRE directory for version 4.6 – for example, C:\Program Files\Java\jre8. 

9. 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.

10. 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.
11. In the Tomcat Web Server Certificate Information panel, review the keystore information or update it as needed, and then click Next.

12. In the Installation Preview panel, review the information, and then click Install.

13. In the Installation Summary panel, review the information, and then click Done.

Where to go from here

• Configuring CLM Self Checker
• Enabling SSL HTTPS on core Linux CLM applications that currently use HTTP
• Enabling SSL HTTPS on core Windows CLM applications that currently use HTTP
• After you on-board the Platform Manager, wait for approximately 10-15 minutes (depending on your infrastructure) for the server to collect data. 
• Verifying the CLM CLM Self-Check Monitor installation
• Monitoring BMC Cloud Lifecycle Management health with the CLM Self Checker