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.

Configuring the My Cloud Services Console

This topic describes how to configure the My Cloud Services console (also known as the Cloud Portal Web Application), either installed with the Install Planner or installed as a standalone application

Video – Configuring the My Cloud Services Console

The following video (7:30) describes how to properly configure the My Cloud Services console. The video also includes helpful troubleshooting tips.


Before you begin

  • Ensure that JRE_HOME is in your system PATH variable.
  • Create a CLM end user to log on to the My Cloud Services console. 
  • Take a VM snapshot of the Platform Manager and My Cloud Services console hosts in case you make a configuration mistake and you need to back out. 
  • Verify the host name you used when you created your certificates during installation, especially if you used a fully-qualified domain name (FQDN). 
  • Verify if you used the bundled JRE during installation. You must identify the correct cacerts file used during installation. 
  • Enter the HTTPS to the Platform Manager to verify that it is working correctly.
    For example:
    You want to see the following information displayed in the browser:

To configure the Platform Manager JSON

  1. Log on to the PM host.
  2. Stop the BMC CSM service. 
  3. Open a file explorer and change directories into the installDirectory\Platform_Manager\configuration\preferences directory.
  4. Make a backup copy of the installDirectory\Platform_Manager\configuration\preferences\PreferenceGroup.json file for editing.
  5. Open the original PreferenceGroup.json file in a good text editor.
  6. Locate the following lines in the JSON. 

        "cloudClass" : "com.bmc.cloud.model.beans.PreferenceGroupNameValuePair",
        "guid" : "98d27d82-44fc-41c8-bde0-007f0fa8fc2f",
        "name" : "clmui base URL",
        "preferenceGroup" : "/preferencegroup/ffd5922e-68fd-4970-83b0-2c47641402d1",
        "value" : http://<clmuihost>:<clmuiport>/clmui
  7. Update the value line with the correct protocol (https, not http), the My Cloud Services Console host name, and the correct port number.
    For example:
  8. Save the file. 
  9. Navigate to the PlatformManagerInstallationDirectory\configuration subdirectory and delete the org.eclipse.osgi folder.

  10. Navigate inside the PlatformManagerInstallationDirectory\cache subdirectory and delete all files.

  11. Navigate inside the PlatformManagerInstallationDirectory\Logs subdirectory and delete all log files.

  12. Restart the BMC CSM service.
    It takes about 5 to 10 minutes for Platform Manager to propagate the changes into the entire BMC Cloud Lifecycle Management installation.

To import the Platform Manager cacerts certificate into the My Cloud Services Console host

  1. On the Platform Manager, navigate to the JREHOME/lib/security directory. 

  2. Copy the JREHOME/lib/security/cacerts file.

  3. Log on to the My Cloud Services Console host.
  4. Paste the cacerts file into a temporary folder.
  5. Open a command window and navigate to the bundled JRE directory. 

  6. Navigate to the JRE bin directory.
  7. Enter the following keytool import command:

    keytool -importkeystore -srckeystore "C:\temp\cacerts" -destkeystore "C:\Program Files\BMC Software\CloudPortalWebApplication\jre\lib\security\cacerts" -srcstoretype JKS -deststoretype JKS -srcstorepass changeit  -deststorepass changeit -noprompt

    Make sure there are no import errors. All the certificates should be imported correctly. 

To verify the Platform Manager configuration in the My Cloud Services Console host

  1. On the My Cloud Services Console host, stop the CSM Portal Service.
  2. Navigate to the ..\CloudPortalWebApplication\tomcat\webapps\clmui\WEB-INF\classes directory.

  3. Open the Config.properties file in a good text editor. 

  4. Make sure that Platform Manager URL is correctly configured for your environment.
    For example, the default URL in the BMC lab environment was:


    This URL did not work properly and threw Error 500 when initially logging on to the My Cloud Services Console host. Because the self-signed certificate was created with a FQDN during installation, the URL in the Config.properties file needed to be changed to:

  5. Restart the CSM Portal service.

To verify that the My Cloud Services console host is configured correctly

  1. Open the My Cloud Services console by using following URL:
    For example (assuming that you used the HTTPS protocol):
  2. If you configured the HTTPS protocol, your connection is initially distrusted in the browser. Add and confirm the site exception.
  3. Log on as a CLM end user.
    You should not see any errors (for example, Error 500) when the console opens.

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. Perform the following steps to reflect the use of HTTPS in the My Cloud Services Console:
    1. Copy the selfcheckSslCertificate.cert file from the selfCheckerHome/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 endUserPortalHome/jre/lib/security/cacerts -srcstoretype JKS -deststoretype JKS -srcstorepass changeit -deststorepass changeit

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

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.