Configuring BMC Cloud Lifecycle Management 4.x to enable CAPA

To enable Capacity-Aware Placement Advice (CAPA) and TrueSight Capacity Optimization Cross Launch features, and to install the integration on Windows and Linux platforms, you need to register the BCM Provider in Windows and Linux Platform Managers. 

Note

The integration procedures described in this section involve stopping the Platform Manager service, performing a manual sequence of steps, and then restarting the API server. The Platform Manager functionality will be unavailable until the manual steps are completed and the service is restarted. Please plan accordingly to minimize downtime.

For more information, see the following sections in this topic:

To register the BCM Provider on Windows to enable CAPA

  1. Stop the Platform Manager service: Access the Windows Services Management Control and stop the BMC CSM service.
  2. Navigate to the %BMC_CLOUD_LIFE_CYCLE_MANGEMENT_HOME%\Platform_Manager\configuration folder.
  3. In the providers.json file, search for the following access attributes, and set the attributeValue to false:
    • UsePeerHintForVCVRPVHPlacement
    • UsePeerHintForVDSPlacement
  4. In the same folder, open the config.ini file and ensure that the following entry exists in the osgi.bundles property section:
    lib/BCMProvider-1.0.0.jar@start
  5. Start the Platform Manager service: Access the Windows Services Management Control and start the BMC CSM service.

  6. Register the BCM provider:
    1. Go to %BMC_CLOUD_LIFE_CYCLE_MANGEMENT_HOME%\Platform_Manager\bcmprovider-registration-1.0.0.
    2. To run the registration utility, run the BCMProviderInstallerUI.bat file from the Command Line Interface.
      The following user interface of the BCMProviderInstaller utility is displayed.
       
    3. Enter the following connection parameters:

      Note

      Default TrueSight Capacity Optimization ports:

      • Datahub Server: 8280
      • Console Server: 8000
      • CSM API Server parameters
        • Server Name: Name of the CSM API server
        • Server Port: CSM API port number (default: 8080)
        • Username: Username to sign in to the CSM API server
        • Password: Password for the above username
        • Login Type: Select any one – IMPERSONATE, SUPERUSER, REGULAR
        • Protocol: Choose between http or https
      • TrueSight Capacity Optimization parameters
        • Datahub Server Name: Name of the Datahub Server
        • Datahub Server Port: Datahub Server port number (Use the default port: 8280)
        • Console Server Name: Name of the Console Server
        • Console Server Port: Console Server port number (default: 8000)
        • Console Server Protocol: Choose between http or https

    4. Click Register to register the BCM Provider in Platform Manager server. If the connection fails, an error message is displayed. 

      Recommendation

      BMC recommends you to click Test Connection to test values and save inputs for the registration utility. If you register without using the Test Connection option, the utility will not save the connection details that have been entered, and you will need to re-enter the details.

To register the BCM Provider on Linux to enable CAPA

  1. Stop the BMC CSM service: Access the Platform Manager server, and run the following command:
    /etc/init.d/bmccsm stop
  2. Navigate to the %BMC_CLOUD_LIFE_CYCLE_MANGEMENT_HOME%\Platform_Manager\configuration folder.
  3. In the providers.json file, search for the following access attributes, and set the attributeValue to false:
    • UsePeerHintForVCVRPVHPlacement
    • UsePeerHintForVDSPlacement
  4. In the same folder, open the config.ini file and ensure that the following entry exists in the osgi.bundles property section:
    lib/BCMProvider-1.0.0.jar@start
  5. Start the BMC CSM service: Access the Platform Manager server and run the following command:
    /etc/init.d/bmccsm start
  6. Register the BCM Provider:

    1. Go to %BMC_CLOUD_LIFE_CYCLE_MANGEMENT_HOME%\Platform_Manager\bcmprovider-registration-1.0.0.
    2. To run the registration utility, run the BCMProviderInstallerUI.sh script from the Command Line Interface.
      The following user interface of the BCMProviderInstaller utility is displayed.

    3. Enter the following connection parameters:

      Note

      Default TrueSight Capacity Optimization ports:

      • Datahub Server: 8280
      • Console Server: 8000
      • CSM API Server parameters
        • Server Name: Name of the CSM API server
        • Server Port: CSM API port number (default: 8080)
        • Username: Username to sign in to the CSM API server
        • Password: Password for the above username
        • Login Type: Select any one – IMPERSONATE, SUPERUSER, REGULAR
        • Protocol: Choose between http or https
      • TrueSight Capacity Optimization parameters
        • Datahub Server Name: Name of the Datahub Server
        • Datahub Server Port: Datahub Server port number (Use the default port: 8280)
        • Console Server Name: Name of the Console Server
        • Console Server Port: Console Server port number (default: 8000)
        • Console Server Protocol: Choose between http or https

    4. Click Register to register the BCM Provider in Platform Manager server. If the connection fails, an error message is displayed. 

      Recommendation

      BMC recommends you to click Test Connection to test values and save inputs for the registration utility. If you register without using the Test Connection option, the utility will not save the connection details that have been entered, and you will need to re-enter the details.

To unregister the BCM Provider from Windows to disable CAPA

  1. Stop the Platform Manager service: Access the Windows Services Management Control and stop the BMC CSM service.
  2. Navigate to the %BMC_CLOUD_LIFE_CYCLE_MANGEMENT_HOME%\Platform_Manager\configuration folder.
  3. In the providers.json file, search for the following access attributes, and set the attributeValue to true:
    • UsePeerHintForVCVRPVHPlacement
    • UsePeerHintForVDSPlacement
  4. Start the Platform Manager service: Access the Windows Services Management Control and start the BMC CSM service.
  5. Unregister the BCM Provider: Go to $BMC_CLOUD_LIFE_CYCLE_MANGEMENT_HOME/Platform_Manager/bcmprovider-registration-1.0.0 and run the BCMProviderInstallerUI.bat utility.
    After you launch the utility, you see the following buttons:
    • Test Connection: Check connectivity to the Platform Manager server. The status of the connection can be one of the following, and is displayed in a dialog box:
      • Registered: BCM Provider is currently registered.
      • Unregistered: BCM Provider is currently unregistered.
      • Connection failure: Error connecting to the Platform Manager server.
    • Unregister: Unregister the provider from the Platform Manager server. If the connection fails, an error message is displayed.

      Click Unregister to unregister the BCM Provider in Platform Manager server, and uninstall it from Windows.

Note

After you unregister the BCM Provider, the CAPA service will stop being associated with BMC Cloud Lifecycle Management. However, TrueSight Capacity Optimization is still integrated to BMC Cloud Lifecycle Management and will continue importing data for other entities.

To unregister the BCM Provider from Linux to disable CAPA

  1. Stop the Platform Manager server: Access the Platform Manager server and run the following command:
    /etc/init.d/bmccsm stop
  2. Navigate to the %BMC_CLOUD_LIFE_CYCLE_MANGEMENT_HOME%\Platform_Manager\configuration.
  3. In the providers.json file, search for the following access attributes, and set the attributeValue to true:
    • UsePeerHintForVCVRPVHPlacement
    • UsePeerHintForVDSPlacement
  4. Start the Platform Manager service: Run the following command:
    /etc/init.d/bmccsm start
  5. Unregister the BCM Provider: Go to the $BMC_CLOUD_LIFE_CYCLE_MANGEMENT_HOME/Platform_Manager/bcmprovider-registration-1.0.0 directory and run the and run the BCMProviderInstallerUI.sh script to launch the BCMProvider Registration Utility.

    After you launch the utility, you see the following buttons:

    • Test Connection: Check connectivity to the Platform Manager server. The status of the connection can be one of the following, and is displayed in a dialog box:
      • Registered: BCM Provider is currently registered.
      • Unregistered: BCM Provider is currently unregistered.
      • Connection failure: Error connecting to the Platform Manager server.
    • Unregister: Unregister the provider from the Platform Manager server. If the provider has not been registered or the connection fails, an error message is displayed.

      Click Unregister to unregister the BCM Provider in Platform Manager server, and uninstall it from Linux.

Note

The installer log file is present at the same location as the utility itself. The name of the log file is BCMProviderInstaller.log.

After you unregister the BCM Provider, the CAPA service will stop being associated with BMC Cloud Lifecycle Management. However, TrueSight Capacity Optimization is still integrated to BMC Cloud Lifecycle Management and will continue importing data for other entities.

To enable secure HTTPS communication between BMC Cloud Lifecycle Management 4.5 and BMC Capacity Optimization

Note

This section applies to BMC Cloud Lifecycle Management version 4.5 only. Previous integrations between BMC Capacity Optimization and BMC Cloud Lifecycle Management supported HTTP communication only, not HTTPS.

For detailed steps, see the relevant section in Integrating with Capacity Optimization .

Related topics

Capacity-Aware Placement Advice

BMC Cloud Lifecycle Management


Was this page helpful? Yes No Submitting... Thank you

Comments