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 Cloud Platform Manager

The following procedure provides the steps for configuring the Cloud Platform Manager in high-availability and stand-alone (not high-availability) environments.

To configure Cloud Platform Manager in a stand-alone environment

  • (Windows) In the Windows Services, stop and restart the BMC CSM service.
  • (Linux) Stop and start the bmccsm service from the /etc/init.d/ directory.

To configure Cloud Platform Manager in a high-availability (HA) environment

Use this procedure to configure Platform Manager for an HA environment. Additional configuration is necessary to accommodate the BMC Cloud Lifecycle Management Quick Start feature in an HA environment running on Windows or Linux.

  1. On the Platform Manager host, navigate to the <Platform Manager installation directory>\configuration folder.
  2. Stop the BMC_CSM service.
  3. Open the config.ini file and add the following parameter before the org.osgi.service.http.port=8080 entry:
    org.osgi.service.http.ipaddress=<Cluster IP address>
  4. Clear the cache and log files:
    1. Navigate to the <Platform_Manager_installation_directory>\configuration subdirectory and delete the org.eclipse.osgi folder.
    2. Navigate to the <Platform_Manager_installation_directory>\cache subdirectory and delete all files.
    3. Navigate to the <Platform_Manager_installation_directory>\Logs subdirectory and clear all log files.

  5. Start the BMC_CSM service and monitor csm log files, which are located in
    <Platform_Manager_installation_directory>\Logs.

To accommodate Quick Start in a Windows HA environment

Use this procedure to ensure that Quick Start runs when Cloud Platform Manager is configured for a Windows HA environment.

  1. Upgrade the Cloud Platform Manager -- Primary server.
  2. Before upgrading the Cloud Platform Manager -- Secondary server, move the service to the secondary node.
  3. Start the Cloud Platform Manager on the Secondary server.
  4. Create the BMCQuickstart service by using a command line to run the following command:

    sc create BMCQuickStart binPath= "\"S:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Platform_Manager\QuickStart\quickstart.exe\" -s \"S:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Platform_Manager\QuickStart\quickstart.conf\"" DisplayName= "BMCQuickStart"
    
  5. Using Cluster Manager, right-click on the BMC_CSM service and select Add a resource -> 4 – Generic Service.
  6. In the Select Service panel, select the BMCQuickstart service and click Next.
  7. On the Confirmation panel, click Next.
  8. On the Summary panel, click Finish.
  9. In the Cluster Manager, right-click on the newly added BMCQuickstart service and select Properties.
  10. In the Properties window, select the Dependencies tab and add the QuickStart service as a resource. Click OK.
  11. Failover the cluster and use the Cluster Manager to determine if the BMCQuickstart service started after the BMC_CSM service.

To accommodate Quick Start in a Linux HA environment

Use this procedure to ensure that Quick Start runs when the Cloud Platform Manager is configured for a Linux HA environment.

  1. Upgrade the Cloud Platform Manager -- Primary server.
  2. Before upgrading the Cloud Platform Manager -- Secondary server, move the service to the secondary node.
  3. Start the Cloud Platform Manager on the Secondary server.
  4. Create a soft link for the BMCQuickstart service by using a command line to run the following command:

    ln -s /etc/init.d/BMCQuickStart/gfs/bmc/BMCCloudLifeCycleManagement/Platform_Manager/QuickStart/sh.script.in
    
  5. Modify the script for the start/stop/status of the BMC_CSM and BMCQuickStart service to accommodate the addition of the BMCQuickStart service. For example, if you have a cluster environment, the /gfs/service_startup/startservice.sh script (or something similar) already exists. Modify it to include the BMCQuickStart service.
  6. Failover the cluster and use the Cluster Manager to determine if the BMCQuickstart service started after the BMC_CSM service.

Where to go next

CLM product configuration files after upgrade

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.

Comments