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.

Configuring CLM Self Checker


This topic describes how to configure the CLM Self Checker, either installed with the Install Planner or installed as a standalone application

To on-board the CLM Self-Check Monitor with Platform Manager

You must onboard the CLM components you want monitored by the CLM Self Checker.

Note

  • Create a cloud administrator that you will use to onboard CLM CLM Self-Check Monitor with Platform Manager.  
  • Update the C:\Windows\System32\drivers\etc\hosts (Windows) or \etc\hosts file (Linux) on the CLM Self Checker host with the details of the Platform Manager VM.
  • If the credentials of BMC Lifecycle Management components change, you must repeat the onboarding procedure.
  1. In a browser, enter the Self-Checker URL.
    For example:
    https://<SelfChecker>:8443/health 
  2. If you installed using the CLM Self-Check Monitor with the existing HTTPS self-signed certificate, your connection is initially distrusted in the browser. Add and confirm the site exception. 
  3. In the CLM Health window, review the instructions and then click the Configuration Panel link.
  4. On the Settings panel, define the Platform Manager settings:

    Field

    Description

    Platform Manager Host Name

    Name or IP address of Platform Manager

    Platform Manager Install Path

    Full path of Platform Manager installation, for example, C:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Platform_Manager or /opt/bmc/BMCCloudLifeCycleManagement/Platform_Manager

    Cloud Admin User Name

    Create a separate cloud administrative user and onboard the BMC Cloud Lifecycle Management stack using those credentials. This cloud administrator should not access the BMC Cloud Lifecycle Management portal or the Enterprise AR or Cloud AR servers.

    Cloud Admin Password

    Password of separate cloud administrative user

  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 System servers from legacy cloud installations:
    1. Select Enterprise AR settings, and then specify the Enterprise-AR details.
    2. Click Test EAR Connection to verify that your configuration settings are correct. 
      If your connection is successful, you can onboard the configuration.
  7. Click On-board and wait for the successful onboarding of BMC Cloud Lifecycle Management components.
    Wait 10-15 minutes for the first batch of data to arrive in the charts.
  8. Click the Health link at the top of the page to view the data. Make sure that the various components are displayed.

    Note

    The Restart All Components button might not be enabled if you did not install NSH on the Platform Manager host and the Stackinformation.properties is not created. For more information, see  Important troubleshooting information when restarting services.

    CLMSelfCheckerConsole.gif 

 

Note

If the credentials of BMC Lifecycle Management components change, you must repeat the onboarding procedure.

If a BMC Cloud Lifecycle Management component product is down during the onboarding of components to the CLM Self Checker, the Application Version will be missing for that component. To display the Application Version, make sure all component products are running, and then re-onboard the Platform Manager.

To configure notifications for the CLM Self Checker

This section describes how to configure email notifications for the CLM Self Checker. 

Note

Step 1 to Step 5 apply only to version 4.6.00.


If you are running versions 3.1, 4.0, or 4.1, skip to Step 6. You can only configure SMTP Server Configuration from the BMC Self Checker > Settings > Notifications.  

  1. Log on to the BMC Cloud Lifecycle Management Administrator Console.
  2. Click the vertical Workspaces menu at the left and select Configuration.
  3. Click the Notifications tab.
  4. In the SMTP Server Configuration area, enter the information as described in the following table to configure SMTP server connection:

    Field

    Description

    SMTP Host Name

    The host name of your SMTP server

    SMTP Port

    The port on which your SMTP server

    Sender's Email Address

    The email address of the sender from whose account the email notifications are sent

    SMTP Authentication

    Specifies whether to authenticate the connection to the SMTP server

    SMTP User Name

    The user name required to log on to the SMTP server

    SMTP Password

    The password that corresponds to the user name

    Use TLS encryption

    Specifies whether to use TLS encryption to establish a secure connection 

  5. Click Save
  6. In the CLM Self Checker, click Settings.
  7. Click Notifications
    Notifications.png 
  8. In the Email Notification section, enter the email addresses to receive notifications, and the conditions under which notifications will be sent.

    Field

    Description

    Send Email To

    Enter email address of recipient. Separate addresses by commas.

    CC

    Enter email address of CC (carbon copy) recipients. Separate addresses by commas.

    Notify me if health check status is

    Select 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 least

    Select how often to notify. 01 Hour is the default. You can choose 05 minutes to 24 Hours.

  9. Click Save
    Make sure that the notification settings are successfully updated. 

To configure component settings

Use these steps to modify the URLs of the TrueSight Server Automation (formerly called BMC Server Automation) and TrueSight Orchestration (formerly called BMC Atrium Orchestrator) Dashboards, as well as the default interval at which data on the charts is refreshed.

  1. On the Settings panel, click Component Settings.
  2. If needed, modify the URLs to the TrueSight Server Automation (TSA) and TrueSight Orchestration (TSO) Dashboards.
    TrueSight Server Automation Health and Value Dashboards are integrated and installed with BMC Server Automation 8.6.00 and later.

    Field

    Description

    TSA Dashboard URL

    Address of TrueSight Server Automation Dashboard. Already entered by default.

    TSO Dashboard URL

    Enter TrueSight Orchestration URL. For example:
    http://<hostnameOrIpAddress>:<webServerPort>/tsocdp
    http://CDPhost:28080/tsocdp

    Health Check Refresh Interval

    Select refresh rate to check the health of your system. You can choose 05 Minutes (default), 10 Minutes, or 15 Minutes.

  3. If needed, select a new refresh interval for data on the Health charts.
  4. Click Save
    Make sure that the settings are successfully updated.  

For information about the TSA Dashboard, see Using the Health and Value Dashboards in the TrueSight Server Automation documentation. 

For more information about the TSO Dashboard, see Verifying the TrueSight Orchestration installation.

To configure the CLM Self Checker URL to view the Health Dashboard summary page from the My Cloud Services Console

If you installed the CLM Self Checker when installing BMC Cloud Lifecycle Management, the installation automatically sets the Self Checker URL. If you installed CLM Self Checker as a standalone application, you must configure the Self Checker URL by editing the PreferenceGroup.json file on the Platform Manager machine.

  1. Make a backup copy of the installDirectory\Platform_Manager\configuration\preferences\PreferenceGroup.json file for editing.
  2. Open the original PreferenceGroup.json file for editing.
  3. Locate the following lines, and update the value line with the correct Self Check Monitor host name and port number, for example https://clm-lab-test:8443/health/.

    {
    "cloudClass": "com.bmc.cloud.model.beans.PreferenceGroupNameValuePair",
    "guid": "2375aae2-ee8b-4a6c-adec-ea31b90b1f70",
    "name": "selfChecker base URL",
    "preferenceGroup" : "/preferencegroup/ffd5922e-68fd-4970-83b0-2c47641402d1",
    "value": "https://selfcheck_monitor_host:port/health"
    }
  4. (Required only if the CLM Self Checker is configured for HTTPS) Perform the following steps to reflect the use of HTTPS in the My Cloud Services Console:
    1. Copy the selfcheckSslCertificate.cert file from the <selfchecker_home>/selfchecker/Certificates directory on the Self Checker host to the My Cloud Services Console VM.
    2. Run the following command to import the CLM Self Checker certificate to the My Cloud Services Console JAVA location:

      ./keytool -importkeystore -srckeystore <selfcheckSslCertificate.cert> -destkeystore <enduserpotalhome>/jre/lib/security/cacerts -srcstoretype JKS -deststoretype JKS -srcstorepass changeit -deststorepass changeit

  5. Restart the Platform Manager CSM service. Wait 5-10 minutes to view the Health Dashboard summary page. 

Where to go from here

 

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