This topic provides a list of enhancements included in version 4.6.00 of the BMC Cloud Lifecycle Management solution. The topic also provides an overview of how to get started with the new version.
Enhancements in version 4.6
The following sections provide an overview of the enhancements included in version 4.6.00 of the BMC Cloud Lifecycle Management solution.
The following video (7:43) presentation provides a high-level summary of the new features and enhancements in version 4.6.00 of BMC Cloud Lifecycle Management.
The installation process in version 4.6.00 is almost exactly the same as version 4.5.00, with only a few minor differences.
|Improved security with Mid Tier installation||To improve security, the 8.1.02 version (8.1.SP02 Patch 001 201512021621 Hotfix) of the BMC Remedy Mid Tier and Tomcat 7.0 are installed.|
|Install planner installs Network Shell (NSH) with Platform Manager||To simplify configuration with the CLM Self-Check Monitor, the install planner installs Network Shell (NSH) with Platform Manager.|
|Installing Small Deployment Windows for version 4.6||Entire MS Windows/SQL Server process for Small Deployment is thoroughly documented from start-to-finish, complete with screenshots.|
|Installing Small Deployment Linux for version 4.6||Entire Linux/Oracle process for Small Deployment is thoroughly documented from start-to-finish, complete with screenshots.|
|Installing Compact Deployment Linux for version 4.6||Entire Linux/Oracle process for Compact Deployment is thoroughly documented from start-to-finish, complete with screenshots.|
|Special CLM system user (clmsystemuser) created with installer||When you run through the post-installation steps for the BMC AR System Server - Cloud Portal and Database, you create a special CLM system user to execute administrator-level actions.|
In version 4.6, only Compact, Small, and Medium deployments are supported.
The upgrade process in version 4.6.00 is almost exactly the same as version 4.5.00, with only a few minor differences.
|Improved security with Mid Tier upgrade||To improve security, the installer upgrades your environment to the 8.1.02 version (8.1.SP02 Patch 001 201512021621 Hotfix) of the BMC Remedy Mid Tier and 7.0 version of Tomcat.|
|Upgrading BMC Server Automation components from 3.1.x takes place in two stages||Upgrading the BMC Server Automation components in CLM version from 3.1.x to 4.6 takes place in two stages – first, you upgrade the application server and console to 8.6.01. Second, the installer prompts you to upgrade the components to to 8.7.00 (patch 1) . For more information, see End-to-end in-place 2AR upgrade for version 4.6.|
|End-to-end in-place 2AR upgrade for version 4.6||Entire MS Windows/SQL Server in-place 2 AR System upgrade upgrade process for Small Deployment is thoroughly documented from start-to-finish, complete with screenshots.|
|End-to-end in-place 1AR upgrade for version 4.6||Entire MS Windows/SQL Server in-place 1 AR System upgrade upgrade process for Small Deployment is thoroughly documented from start-to-finish, complete with screenshots.|
Compact RDS available for deployment
The 4.6 version of the Compact Rapid Deployment Stack (RDS) is now available for deployment in your Linux environment. You can download the ZIP file from EPD on the BMC Customer Support site.
BMC Compact Rapid Deployment Stack is no longer supported.
Small RDS available for deployment
The 4.6.03 version of the Compact Rapid Deployment Stack (RDS) is now available for deployment in your Linux environment. Contact BMC Customer Support to access the download files.
BMC Small Rapid Deployment Stack is no longer supported.
My Cloud Services Console enhancements
The following table describes the enhancements to the My Cloud Services Console included in this release:
|User labeling of resources||You can add labels to categorize your resources. For example, you might want to label servers according to their purpose or to a project code. See Using labels to categorize your resources.|
The My Cloud Services console remembers the resource type that you viewed the last time you were in the Resources List view and returns to that view when you view the Resources List again (even if you log in again). If you refresh your browser cache, the default resource type list will be the Services list.
|Compliance at service level|
Cloud administrators can configure compliance standards in new BMC Cloud Lifecycle Management installations or existing ones to accomplish the following:
|Simplified localization and other features|
For more information, see Localizing the My Cloud Services console for version 4.6.
|Auto-Decommissions activity and System User|
An Activity log entry for the Auto-Decommission activity is now displayed in My Cloud Resources console, to make the process more transparent. Version 4.6.00 also introduced a new System User to show that this action was initiated by the system, and not by another other user. .
Several new ways to customize the My Cloud Services console were introduced:
|Top-level menu and submenu items|
You can customize the My Cloud Services console with top-level menu and submenu items (as shown below). You can include additional dashboards, reports, or direct links on the My Cloud Services console. For more information, see Customizing the My Cloud Services console with top-level menu and submenu items.
|Customized messages on the login page||You can create a static text message – for example, an agreement statement or a copyright message – on the login page of the My Cloud Services console. For more information, see Customizing messages on the login page of the My Cloud Services console.|
|Custom panels or sections to the Catalog service details page||By configuring a json file, you can further customize the Catalog service details page so that the page contains a separate panel (under the generic section at the top or at the bottom of the other panels) or a section within a server group’s panel. For more information, see Adding custom panels or sections to the Catalog service details page.|
|Dynamic lists to fields in the Catalog service details page||If you want to implement drop-down lists for parameters that users must enter, you can make these lists dynamic. The set of customizations offered and the choices within each service offering can vary by tenant. The selections the user makes are stored with the service offering instance. For more information, see Adding dynamic lists to fields.|
You can now validate your users' passwords. See the descriptions for Password Regex and Password Help Text in Configuration workspace overview.
Indexing and Elasticsearch
You can now use full cluster, failover, or other robust features of Elasticsearch. See Indexing and Elasticsearch. Also, to provide an easy means for cloud administrators to resynchronize indexes for resources, a new functionality, Resync Index has been introduced in the Configuration workspace. See .
Changes to integration with BMC IT Service Management
The following changes were made to improve the integration with BMC IT Service Management:
- A CL prefix was added to all string-based unique IDs in the Foundation data.
- For all IDs where the ID is a numeric type, the value was changed to the next increment.
- Escalations were provided for the initial load of Foundation data from Corporate ITSM to CLM AR
- DSO initial load escalations and DSO filters were configured to exclude default BMC Remedy AR System users (such as Demo).
- The license type that is set on the Corporate ITSM server is retained.
- Escalations on CLM AR are now available by default to make Foundation data (that is transferred through DSO) compatible with BMC Cloud Lifecycle Management. The escalations include escalations such as CMF:USE:02_OnboardTenant_Bulk and CMF:USE:03_SyncTenantUser_Corporate.
- The pre-checker tool was enhanced to include:
- Rules to verify against Corporate ITSM
- Integrity checks to compare data between CLM AR and Corporate ITSM
- BMC Change integration enhancements include:
- Change integration extensions on Corporate ITSM
- More detailed information related to options and service owners in the Change requests
For more information, see Integrating with Corporate ITSM for Foundation data and Integrating with BMC Change Management.
If a service offering instance provisioning fails, BMC Cloud LifeCycle Management retries provisioning because the enableSOIProvisioningRetry property is set to true in the providers.json properties file. In BMC Cloud LifeCycle Management 4.5.00, this property was disabled or set to false.
Virtualization environment enhancements
|Support for Hyper-V Generation 2 VMs|
You can set up and provision a Microsoft Hyper-V Generation 2 VM by using a Hyper-V Generation 2 template.
With Hyper-V Generation 2 support, you can:
For details, see Creating the VGP in BMC Server Automation for Hyper-V.
The following table describes the BMC Cloud Lifecycle Management Developers API enhancements included in this release:
The following are some of the new classes added to the OpsManager class of the Cloud API:
Third-party provider enhancements
The following table lists the changes to the third-party providers included in this release:
|Includes support for the OpenStack Juno and Kilo releases. For details, see Overview of the OpenStack Provider.|
|Enables cloud administrators to enroll the Azure provider via a proxy server. For details, see To register the Azure Provider instance.|
|vCloud|| Enables cloud administrators to refresh the Logical Data Center (LDC) information with new networks added or existing networks removed from the virtual data center . For details, see Synchronizing a Logical Data Center. |
Product versions and compatibility
For detailed information about versions, service pack, and patch levels for the products installed in BMC Cloud Lifecycle Management 4.6.00, see
Downloading the files
For download instructions, see Downloading the installation files.
Download all the files in the BMC Cloud Lifecycle Management 4.6.00 folder.
Installing the version as a fresh installation
- If you do not already have BMC Cloud Lifecycle Management installed in your environment, perform the procedures in the Installing section using the downloaded files.
Ensure that the supported products are at the latest service pack or patch level listed in the following table. Review especially any required hotfixes.
Required products Version in 4.6 installer
BMC Atrium Core Web Registry 8.1.01 BMC Atrium Orchestrator Content
BMC Atrium Orchestrator Platform, including:
- BMC Atrium Orchestrator – Configuration Distribution Peer
- BMC Atrium Orchestrator – Configuration Distribution Peer (High Availability)
BMC Cloud Lifecycle Management, including:
- Cloud Database Extensions
- Cloud Platform Manager
- Cloud Portal AR Extensions
BMC Network Automation , including:
- (Optional) BMC Network Automation – Device Agent
8.7.00 BMC Remedy Action Request System 8.1.01 BMC Remedy Mid Tier 8.1.02 (8.1.SP02 Patch 001 201512021621 Hotfix) BMC Remedy Service Request Management 8.1.01
BMC Server Automation, including:
- BMC Server Automation – Application Server and Console
- BMC Server Automation – Virtual Center Agent (installed manually)
- (Optional) BMC Server Automation – Advanced Repeater
- (Optional) BMC Server Automation – PXE Server
- (Optional) BMC Server Automation – File Server
8.7 Patch 1
If you want to use third-party providers such as Azure, OpenStack, and IBM Bluemix Infrastructure with 4.6.00, do not install these providers separately. Instead, install 4.6.03.
Upgrading to the new version
If you are upgrading from any previous version to version 4.6, you must review the items in the Preparing for upgrades topic to successfully complete the upgrade process. Ensure that the supported products are at the latest service pack or patch level listed in Component BMC product service pack and patch levels.
You do not need to perform the data migration steps while upgrading from version 3.1 to 3.1.01. You can upgrade your system by performing the steps listed in the Upgrading section.
If you are using the existing BMC Cloud Lifecycle Management version 2.1.x, 3.0.x, or 3.1.x host to launch the version 4.6 installation program, then perform the following tasks prior to upgrading:
- Uninstall the existing planner version. To uninstall the existing planners, perform the following steps:
- Microsoft Windows: Go to the <Planner Install Directory\UninstallBMCPlanner> folder and run the uninstall.bat file. Example: C:\Program Files\BMC Software\Planner\UninstallBMCPlanner.
- Linux: Go to the <Planner Install Directory/UninstallBMCPlanner> folder and run the uninstall.sh file. Example: /opt/bmc/Planner/UninstallBMCPlanner.
- Backup all the installer-related files from the following location:
- Microsoft Windows: c:\windows\temp and %temp% folders
- Linux: \tmp folder
- Delete all the uninstall files from both of the above locations.
BMC recommends that you restart the Microsoft Windows computer after performing the pre-upgrade tasks.