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.

4.6.07 enhancements

 

This topic provides a list of the enhancements included in version 4.6.07 of the BMC Cloud Lifecycle Management solution. It also provides an overview of how to get started with the new version. The topic includes the following sections:

Version 4.6.07 enhancements

Version 4.6.07 is available on the Customer Support website at http://www.bmc.com/support. 

The following table outlines the features in this release and where you can find more information:

 Category

Feature

 Description

General

Add Label to Disk

A new Label attribute has been added for Disk. You can create labels for any existing or additional disks. For more information about how to create labels, see Managing-servers-in-a-service.

You can also apply labels using REST API. For more information, see Label class.

Third Party provider update

OpenStack upgrade

OpenStack version that is shipped with BMC Cloud Lifecycle Management has been upgraded from v2 to v3. You can now use OpenStack v3 along with the existing OpenStack v2 version .

For more information about other third-party software versions, see Supported releases of OpenStack.

While managing multiple OpenStack accounts, you must provide domain name along with user name in OpenStack v3.

Five new fields (Proxy Settings) have been added to Manage Multiple OpenStack User Account screen. If you are using a proxy host to access the internet, you must ensure that you enter the information in this fields. Now, you can work with multiple proxies and also can add account without proxy with single provider instance. You need not create new provider instance to use different proxy setting. For more information, see Managing-multiple-OpenStack-accounts.

Now, you can select a logical data centre from the available list of logical data centre for an account.  For more information, see Managing-the-OpenStack-Logical-Data-Centers.

This version adds a flexible way of automatically choosing the instance type based on the CPU and memory values (within the instance family). For more information, see Creating-options-and-option-choices-in-the-OpenStack-Provider.

Custom provider

Custom Operator Action

Now, Custom Operator actions on PaaS and custom resources are supported. You can register and delete custom operator actions for Application Container, Custom Container, Custom Resource, and Database.

For more information, see Creating-and-deleting-custom-operator-actions.

Third Party provider update

Azure SDK upgrade

Azure SDK version that is shipped with BMC Cloud Lifecycle Management has been upgraded from 1.2.1 to 1.5.1. For more information, see Product-compatibility-and-limitations-for-the-Azure-provider.

Third Party provider update

AWS SDK version

AWS SDK version that is shipped with BMC Cloud Lifecycle Management has been upgraded from 1.8.11 to 1.11.261. For more information, see CLM-AWS-SDK.

Third Party provider update

JRE version updated to 1.8 Update 181

Java Runtime Environment (JRE) version certified with Cloud Lifecycle Management has been updated to 1.8.0_181 (JRE 1.8 Update 181). The following modules are certified: BMC Remedy Mid Tier, Cloud Platform Manager , CLM Self-Check Monitor, BMC AR System Server – Cloud Portal and Database.

Callouts

Asynchronous AO Call-Out

TrueSight Orchestration callouts can be asynchronous for any given action.

A new Is Asynchronous checkbox has been added to Configuration > Callouts > Register Callout window. For more information, see To register a BMC Atrium Orchestrator callout.

Earlier, TrueSight Orchestration callouts can only be synchronous, where BMC Cloud Lifecycle Management continues polling the status of the callout to complete the action. For the tasks, that take more than one day to complete (for example, a workflow in an external system), synchronous AO callout creates a load on the Platform Manager. When callouts are configured as asynchronous for any action, the task on the Platform Manager is hibernated, thus, minimizing a load of polling on the Platform Manager. The task is resumed by an external entity (AO WF, Java Program) by using the BMC Cloud Lifecycle Management API.

My Cloud Services console

Multibranding

You can modify the styles.css file to rebrand or reskin prominent portions of the My Cloud Services console, based on Tenants. You can also customize the menu items on My Cloud Services console based on Cloud User roles and Tenants. For more information, see Rebranding-or-skinning-the-My-Cloud-Services-console.

Discontinued support for Azure Classic

Azure Classic is no longer supported because Service Management APIs are deprecated.

Discontinued support for BMC Rapid Deployment Stack

BMC Compact Rapid Deployment Stack and Small Rapid Deployment Stack are no longer supported.

Downloading the feature pack

To download version 4.6.07, see Downloading-the-installation-files.

Preparing to install the feature pack

Before installing the feature pack, ensure that the following conditions are met:

  1. If you are using any of the earlier versions, upgrade to BMC Cloud Lifecycle Management version 4.6.00.
  2. Ensure that the supported products are at the latest service pack or patch level. 
    For more information about the supported product versions, see Component-BMC-product-service-pack-and-patch-levels.
  3. Close any open session of BMC Remedy Developer Studio before running the installer.
  4. Make sure that the Enterprise BMC Remedy AR System Primary server is running.
  5. Make sure that the primary BladeLogic Application Server is running.
  6. Make sure that the Quick Start service is running.

  7. If you have changed the administrator user password for the enterprise AR System and cloud AR System after the last time you installed BMC Cloud Lifecycle Management, you must ensure that the passwords match the installation configuration file. If the passwords do not match, the installation fails.

    Perform the following steps to ensure that the passwords match
    1. Generate an encrypted password: 
      1. On the Cloud Platform Manager, go to C:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Utilities.
      2. Run the BMCCloudLifeCycleManagementMaintenanceTool.bat/sh file.
      3. Click Encrypt.
      4. In the Password and Confirm Password fields, enter the new password.
      5. Click Encrypt.
      6. Copy the new encrypted password.
    2. Update the encrypted password in the installation configuration file on the enterprise AR System: 
      1. Go to InstallationDirectory\BMCCloudLifeCycleManagement\ and open the BMCCloudLifeCycleManagementInstalledConfiguration.xml file.
      2. Search for the BMC_AR_PASSWORD_HOSTING attribute.
      3. In the value field for the attribute, enter the encrypted password.
    3. On the cloud AR System server, follow the same steps to update the encrypted password in the installation configuration file.
  8. Make sure that the BMC Remedy AR System ports specified in the BMCCloudLifeCycleManagementInstalledConfiguration.xml file are accurate. 
    If the ports are not accurate, stop the enterprise AR System or cloud AR System services, updated the port numbers, and restart the service. For more information, see BMC Knowledge Article 000081555.
  9. Take a VM snapshot and a database backup of the enterprise AR System server and Platform Manager.
  10. Ensure that the JAVA_HOME variable is set on the servers where you are installing the feature pack. On Linux servers, ensure that X11 libraries are installed.

  11. Save any customizations performed in non-overlay mode. Otherwise, they are deleted during the feature pack installation.

    Warning

    Installing the feature pack can affect the AR objects in a non-overlay mode. Ensure that you follow the best practices for customizations. For more information, see Creating-overlays-with-BPCU-for-existing-customizations.

Installing the feature pack

This section describes the procedure to install the latest feature pack.

Note

For installing the latest feature pack on a single-VM compact deployment setup, place the installer file on the host and extract the files. Perform step 2 to install the feature pack.

To install the latest feature pack

  • For Small Deployment environment (Multiple VMs), the following installation sequence of Feature Pack 4.6.07 is critical.
  • For Compact Deployment environment (Single VM), the installation sequence of Feature Pack 4.6.07 does not apply. 

Note

In the BMC lab environment, installing the feature pack took about 15 minutes in the Windows Compact Deployment.

  1. Download and extract the Feature Pack 4.6.07 installer (CLM_FeaturePack_4.6.07_Windows_Installer.zip for Windows and CLM_FeaturePack_4.6.07_Linux_Installer.tar.gz for Linux) and place a copy on each of the VMs that have the following components installed:
    1. Enterprise BMC Remedy AR System Primary server
    2. Enterprise AR System Secondary server, if applicable

    3. Cloud Platform Manager

      Notes

      Install the feature pack on the enterprise BMC Remedy AR System first and then on Platform Manager.

      For Linux, extract the installer by using the tar –xvf CLM_FeaturePack_4.6.07_Linux_Installer.tar.gz command.

      On the Cloud Platform Manager host, set JAVA_HOME to the bundled JRE (for example, C:\Program Files\BMC Software\BMCCloudLifeCycleManagement\JVM_1.8.0_60).

    4. Standalone CLM Self-Check Monitor
    5. Standalone Cloud Portal Web Application (clmui)
  2. On the Enterprise AR System server, install patch: 
    1. Start one of the following installation programs:
      • On Microsoft Windows, navigate to the ..CLM_FeaturePack_4.6.07_Windows_Installer\CLMPatchInstaller\Disk1 location and then run the setup.exe file or double-click the setup.exe file. 

      • On Linux, navigate to the .. CLM_FeaturePack_4.6.07_Linux_Installer/CLMPatchInstaller/Disk1 location and run the setup.bin file by using Xmanager.

        With Xmanager, X applications installed on remote UNIX-based computers run seamlessly with Windows applications side by side.

        Note

        You can also use the VConsole to launch the installer.

    2. On the Welcome panel, review and implement the best practices in your environment, and then click Next. 
      For example, take a snapshot of the host, back up the database, and so on. 
       
    3. Review the components detected by the installer, and then click Next. 
      The installer applies updates to the detected components.
      ComponentsDetected.png
    4. On the Directory Selection panel, review the location on the host where you want to install the BMC Cloud Lifecycle Management feature pack files and then click Next.
      You can accept the default value if you do not have a specific location for the installation files.
    5. On the Installation Preview panel, review the patch installer information (for example, the location of the feature pack) and then click Install. 
       
    6. On the Installation Summary panel, review the installation log and then click Done to finish the installation. 
       
  3. Repeat step 2 on the Enterprise AR System Secondary server if you are running a Small Deployment.
    This step does not apply to Compact Deployment.
  4. Repeat step 2 on the Cloud Platform Manager host if you are running a Small Deployment.
    This step does not apply to Compact Deployment. 
  5. Repeat step 2 on the standalone CLM Self-Check Monitor host if you are running a Small Deployment.
    This step does not apply to Compact Deployment. 
  6. Repeat step 2 on the standalone Cloud Portal Web Application (clmui) host if you are running a Small Deployment.
    This step does not apply to Compact Deployment. 

Configuring after installing the feature pack

Perform the following post configuration procedures after installing the latest feature pack:

To clear the cache on the primary mid-tier

Use this procedure to clear the cache on the primary mid-tier host.

  1. Log on to the Mid Tier Configuration Tool for the primary mid-tier installed in your cloud environment. This mid-tier is different than the mid-tier running on the enterprise AR System server.
  2. Perform a flush cache.
    The flush cache removes all items from the cache that the primary BMC Remedy Mid Tier maintains. The next time the mid tier needs those objects, the most up-to-date versions are retrieved from the AR System server.
  3. Clear the browser cache.

To clear the cache on the secondary mid-tier hosts

Use this procedure to clear the cache on secondary mid-tier hosts. You do not need to perform these steps for the mid-tier running on the Enterprise AR System server.

  1. Log on to the Mid Tier Configuration Tool for the secondary mid-tiers used by the BMC Cloud Lifecycle Management console that are different than the mid-tier running on the enterprise AR System server.
  2. Perform a flush cache.
    The flush cache removes all items from the caches that the secondary BMC Remedy Mid Tier maintains. The next time the mid tier needs those objects, the most up-to-date versions are retrieved from the AR System server.
  3. Clear the browser cache.
  4. Perform the following steps to hard delete the secondary mid-tier cache:
    1. Stop the mid-tier service.
    2. Log in to the mid-tier server, and delete the contents of the following folders:
      1. ARSystem\midtier\attstore
      2. ARSystem\midtier\cache
      3. ARSystem\midtier\cachetemp
      4. ARSystem\midtier\dvmodule
      5. ARSystem\midtier\PluginsCache
      6. ARSystem\midtier\WEB-INF\atriumDeploymentPackages
      7. ARSystem\midtier\WEB-INF\AtriumWidget
      8. ARSystem\midtier\WEB-INF\AtriumWidget-7604
    3. Delete the atrium-* files in the ARSystem\midtier\WEB-INF\lib folder.
    4. Delete the contents of the work and temp folders in the ....\...\Apache Software Foundation\Tomcat X.X folder.
    5. Delete the viewStats.dat and viewStats.dat.bak files from the ARSystem\midtier\WEB-INF\Classes folder.
    6. Start the Tomcat (JSP Engine) service.


Related topics

Known-and-corrected-issues

 

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