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 the StackInformation.properties file

This topic describes the use and configuration of the StackInformation.properties file.

Overview

After installing BMC Cloud Lifecycle Manager, when you start the Cloud Platform Manager for the first time, the StackInformation.properties file is created on the Cloud Platform Manager. The StackInformation.properties file stores the information about the BMC Cloud Lifecycle Management components and is used to provide information about all components to the cloud database. This file is used for restarting BMC Cloud Lifecycle Management components and Downloading-log-files-for-service-offering-instance-failures.

If you make any changes to the file, you need to ensure that you restart the Platform Manager for the changes to reflect in the Cloud Database. 

In any of the following conditions occur, the StackInformation.properties file is not created on the Cloud Platform Manager:

  • If NSH is not installed on Platform Manager
  • On a multi-vm stack, if the RSCD agent service is not started on any of the virtual machines or is not reachable
  • If the RSCD agent service is not running on the port where the Self Check RSCD agent port is running (The port number should be same for all components.)
  • If any component in a multi-VM stack environment is not reachable

If the StackInformation.properties file is not created on the Cloud Platform Manager, the Restart All Components button on the CLM Self Checker or BMC Cloud Lifecycle Management Health Dashboard is not enabled. You can create the file manually or edit the existing file to ensure all information is captured accurately and then restart the Cloud Platform Manager. 

If you uninstall a BMC Cloud Lifecycle Management component, for example, TrueSight Orchestration, you need to manually update the StackInformation.properties file on the Platform Manager. While updating the file, you must delete all entries for the component else the changes are not reflected accurately in the cloud database.

If any component is installed after Cloud Platform Manager is started, for example if you install TrueSight Orchestration after the Cloud Platform Manager is started, the details about TrueSight Orchestration are not captured in the file. You must manually update the information in the StackInformation.properties file. 

To edit the StackInformation file

  1. Go to <Cloud Platform Manager installation directory>\Platform_Manager\configuration and open the StackInformation.properties file. 
    The following figure describes the sample StackInformation.properties file.
    Sample stackinformation properties.png

  2. Make changes as per your requirement. 
    The following table describes the properties to be added for a component in the StackInformation.properties file.

    Property

    Description

    host

    The host name where the BMC Cloud Lifecycle Manegement component is installed For example: bmcstrykerclmonbmc

    installationDirectory

    The location where the BMC Cloud Lifecycle Management component is installed For example: C\:\\Program Files\\BMC Software\\AO-Platform\\

    logPattern

    The location where logs are captured For example: C\:\\Program Files\\BMC Software\\AO-Platform\\tomcat\\logs\\grid.log

    serviceName

    The service name of the component For example: AO-CDP

    type

    The component that is installed For example: BMC_ATRIUM_ORCHESTRATOR

  3. Save the file and restart Cloud Platform Manager.

Related topics

Monitoring-BMC-Cloud-Lifecycle-Management-health-with-the-CLM-Self-Checker

Downloading-log-files-for-service-offering-instance-failures

 

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