4.6.06 enhancements

This topic provides a list of the enhancements included in version 4.6.06 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.06 enhancements

Version 4.6.06 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

Onboarding

Onboard existing Microsoft Hyper-V VMs

You can bring existing Microsoft Hyper -V Virtual Machines into BMC Cloud Lifecycle Management by onboarding them using any of the following procedures:

OnboardingOnboard existing Azure Resource Manager VMs

You can bring existing Microsoft Azure Resource Manager Virtual Machines into BMC Cloud Lifecycle Management by onboarding them using any of the following procedures:

Azure providerCompliance

Compliance at Service level for Azure Resource Manager providers

Cloud administrators can configure compliance standards for Azure Resource Manager by enrolling the respective servers in BMC Server Automation, and then leveraging the existing BMC Server Automation jobs to accomplish the following:

  • Enable compliance and select the compliance type
  • View the compliance status report for services and servers with the required details

End users and tenant administrators can only view the compliance status of services and servers. For details, see Monitoring BMC Cloud Lifecycle Management service compliance.

Azure providerAzure Disk ManagementBMC Cloud Lifecycle Management supports managed disks for Azure. You only have to specify the replication type (Premium or Standard) and the size of disk you need, and Azure creates and manages the disk for you. For more information, see To set up support for managed disk and replication type.
Azure providerAzure resource group creationYou can place Azure VMs in an existing resource group or allow BMC Cloud Lifecycle Management to create new resource groups.

A parameter named resource-container specifies the name of an existing resource group that you can consume to deploy or consolidate all workloads. You can specify this parameter within a service blueprint at the deployment definition level.

If you select Yes for the parameter’s User Entry field, end users can specify the resource group when requesting the service.

If you select Yes, enter a clear description so that users can click on the tooltip icon next to the field to learn what the field (parameter) requires.

A new field named Relax ARM Resource Group Constraint in the Register Provider page has been added. Select True to create a resource group with the name that the user has provided in the resource-container parameter. If the resource group with the specified name already exists, then it will consume that resource group to deploy or consolidate all workloads. However, if you select False, then ensure that you must specifiy a already existing resource group name in the resource-container parameter. The default is True. For more information, see Service blueprint parameters for Azure.

Azure providerAvailability set at resource group creation

To use the AVAILABILITY_SET_NAME parameter at the resource-set level, you must provide the values with the following naming convention for Name and Default Value field respectively:

Name - ResourceSet: AVAILABILITY_SET_NAME

Default Value - <AvailabilitySetName>:<Fault Domain>: < Update Domain>

where, the value of the Fault Domain and Update Domain must be an integer and accepted by Azure.

For more information, see Service blueprint parameters for Azure.

Azure providerCross region deploymentsBMC Cloud Lifecycle Management supports cross-region deployments of installable resources. However, you must ensure that the image is present and the image names are identical in all the regions. For more information, see Provisioning for Azure Resource Manager (with or without templates).
Azure providerCustom resource names for Azure resources

You can use a custom host name advisor to control the resource names assigned to provisioned Azure resources. Otherwise, the default resource name configuration from the Configuration workspace is used. The following values of the resources can be customized using the custom hostname provider:


  • Resource Groups
  • NICs
  • Storage Account
  • Disks
  • Load Balancers
  • Availability Sets
  • Public /Private IP artifacts 


For more information Registering a custom hostname advisor.

Custom PanelCustomization toolkitThe toolkit creates HTML and JavaScript files automatically based on the inputs provided from UI for creating a custom panel. For more information about how to enable and use the customization toolkit, see Enabling and using the customization toolkit.
Custom PanelDay 2 operations

New custom panel support for day2 operations and custom operator action UI enhancements. Now, you can perform the following actions:

Networking

Network path support on POD level network

Network path is now supported on POD level network.

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.06, 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.06 is critical.
  • For Compact Deployment environment (Single VM), the installation sequence of Feature Pack 4.6.06 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.06 installer (CLM_FeaturePack_4.6.06_Windows_Installer.zip for Windows and CLM_FeaturePack_4.6.06_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.06_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.06_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.06_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.
    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

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

Comments