BMC strongly recommends that you upgrade to BMC Capacity Optimization 9.0.01 directly. BMC Capacity Optimization 9.0.01 is a full-product installation.
You can use the BMC Capacity Optimization Installer to upgrade from versions 4.x to version 9.0. Customers using versions 3.x should first upgrade to 4.x and then to 9.0.
If you have installed BMC Capacity Optimization 4.x on multiple servers, you must perform a configuration task before you upgrade to version 9.0. This configuration step is required to ensure that the association between servers and BMC Capacity Optimization components is preserved during upgrade.
A specific utility is provided to perform this preparation that you can download from ftp://ftp.bmc.com/pub/bco/9.0.0/upgrade. For additional details, refer to the Readme documentation provided at the same location.
This topic provides additional recommendations for upgrade use cases:
- Email configuration: In BMC Capacity Optimization 9.0, email configuration is centralized and specified only once in the administration user interface.
- Connectors upgrade: Some specific connectors in 9.0 are deprecated and an upgrade method is suggested.
- Built-in dashboard upgrade and Custom dashboards upgrade: Console and dashboard user interfaces are unified in 9.0 and all dashboards (built-in and custom) appear under the new 9.0 Console UI in the Views tab.
In version 4.x, the email configuration was stored on each BMC Capacity Optimization host, and the user was prompted whether to save settings or not, every time an upgrade or new installation was performed. However, in BMC Capacity Optimization 9.0, email configuration (that is, SMTP server, user name, and password) is centralized and specified only once in the administration user interface (Admin > System > Configuration). Due to this change, settings currently in 4.x are not preserved when upgrading to 9.0. After upgrade, you must manually configure email settings in Admin > System > Configuration.
In general, many connector modules are updated with 9.0 for defect fixes and enhancements. If you have ETL instances already configured and running, they will continue to work with the updated module without the need for reconfiguration.
However, in some specific cases, BMC Capacity Optimization 9.0 offers a better alternative for an existing connector, and hence a reconfiguration is recommended. These special cases are as follows:
- NetApp DataFabric ETL: BMC Capacity Optimization 9.0 offers a new and enhanced ETL for NetApp DataFabric named NetApp -- DataFabric Manageability SDK extractor. BMC recommends that you switch to the new ETL to extract additional object types and many more metrics than the earlier 4.xETL offering.
- The earlier NetApp ETL to extract data from NetApp Datafabric Manager using the HTTP URL connection is deprecated. The 4.x ETL now has a changed label "NetApp – DataFabric Manager 4.x extractor [deprecated]" to denote that it is deprecated. The 4.x ETL is still available in 9.0.00 to allow users enough time to migrate to the new NetApp ETL.
- If you have scheduled and are collecting data using the 4.x ETL, after you upgrade to BMC Capacity Management 9.0, BMC recommends that you use the Lookup Sharing feature. To do this, while configuring the new ETL, select the Lookup Sharing tab and specify the 4.x ETL as the shared ETL. This will share the lookup of entities when the switch happens from 4.x ETL to the new one.
For more information about this connector, see Integrating with NetApp DataFabric.
- VMware vCenter ETL: BMC Capacity Optimization 9.0 offers a new and enhanced collection method for VMware vCenter that allows collecting detailed metrics even when the logging level in vCenter is low. This new module is called VMware vCenter Extractor Service. BMC recommends that you switch to the new ETL especially in a case where you need detail metrics and it is not possible, or recommended, to increase logging level in vCenter.
- The earlier vCenter ETL (hence referred to as 4.x ETL) to extract data from vCenter is still available under the name of VMware vCenter and ESX History Extractor. The 4.x ETL is not deprecated, and is still recommended to be used for historical data extraction (extraction of data for a past period). In fact, the new vCenter Extractor Service in 9.0 offers a real-time data collection method, that does not allow to recover past data.
- Users having ETLs already scheduled and running with the 4.x vCenter connector module will continue to be able to use those without any change. However, in case of detailed metric collection it is recommended to configure a new ETL instance using the new vCenter Extractor Service module (during the ETL creation, remember to select Lookup sharing and share lookup with the 4.x ETL instance). The 4.x ETL module can be kept in case a historical recovery is needed.
For more information on this connector, see BMC Capacity Optimization integration with VMWare.
- BMC ProactiveNet ETL: BMC Capacity Optimization 9.0 offers a new and enhanced extractor for ProactiveNet 9.0, that provides additional support for virtualization technologies with detailed entity types and metrics.
- The earlier 4.x ETL for ProactiveNet 8.5/8.6 is still available but deprecated. It will appear in the module list with a label ending with [deprecated].
- If you had existing ETL instances configured and scheduled to run, that are connected to ProactiveNet 8.5/8.6, they will continue to run until ProactiveNet is the same version (8.5/8.6). However, this module is deprecated as ProactiveNet upgrade to 9.0 is recommended.
- BMC recommends the following ways to get a full 9.0 upgrade for the BMC ProactiveNet Performance Management Suite:
- EMC StorageScope ETL: BMC Capacity Optimization 9.0 offers a supported connector for EMC StorageScope. No supported connector was available in 4.x, but there was a Template Connector for EMC StorageScope. Users having the Template Connector in place are recommended to switch to the new EMC StorageScope connector.
As you can freely modify the Template connector, BMC cannot provide advice on the possibility to share the lookup table and preserve historical data when switching from Template to the officially supported connector. The safer method is to create new entities (new domain) without any lookup sharing. If you want to try preserving historical data between the custom ETL for StorageScope based on Template, BMC recommends executing this test in a non-production environment.
Built-in dashboard upgrade
A new version of the built-in dashboard is installed after 9.0 installation is complete.
Before you perform the product upgrade:
- If you granted access rights to one or more built-in dashboard to specific Access Groups, make sure you remember those grants.
- To verify access rights for a dashboard, in the Admin dashboard, access the Communities portlet to see assigned members for each community.
- If you modified one of the dashboards and want the upgrade process to maintain your modified version, you can rename the selected ones. For example, you can rename Welcome to WelcomeBackup and it will remain available after the upgrade.
After the upgrade is complete, all out-of-the-box dashboards of version 4.x like Consolidation, Virtual Farm, Chargeback, need to be updated with the following procedure:
- Choose Administration > System > Maintenance.
- In the Additional Components table, click INSTALL to complete the installation.
If a dashboard was not installed before the upgrade, it will not get installed after the upgrade. To install the dashboard, click INSTALL.
Following is the complete list of the out-of-the-box dashboards:
- Admin: Not available in 9.0, it is substituted by VIEWS in the Admin tab.
- Welcome: Not available in 9.0, as the VIEWS tab is integrated in the Console.
- Consolidation: New version available in 9.0.
- Chargeback: New version available in 9.0.
- Cloud Capacity Visibility: New version available in 9.0.
- Virtual Farm: New version available in 9.0.
- AIX Virtual Farm: New version available in 9.0.
- Solaris Virtual Farm: New version available in 9.0.
- HP Virtual Farm: New version available in 9.0.
After the procedure is complete, these Views (new term for dashboard in 9.0) appear under the Views tab, and are owned by the admin user. To grant access to other users, you must edit each View and associate it to one or more Access Groups.
BMC discourages keeping renamed version of dashboards from #3 to #9 since they were heavily modified in version 9.0 and previous versions are not guaranteed to work. BMC strongly recommends that you install the new version of the same dashboards, as described above.
Custom dashboards upgrade
The upgrade process from BMC Capacity Optimization 4.x to 9.0 preserves custom dashboards and their association to BMC Capacity Optimization Access Groups. Immediately after upgrade, login as a admin user to see post-upgrade information related to upgrade of your custom dashboards on your home page.
A custom dashboard can be based:
- On out-of-the-box portlets from BMC Capacity Optimization: After the upgrade, all out-of-the box portlets in your custom dashboards will have the same behavior as before. If you used these to build your custom dashboard, the dashboard will have the same behavior.
- On custom portlets not belonging to BMC Capacity Optimization, but developed externally leveraging Java Portlet API and Liferay framework: If you used custom portlets in your dashboard, you will need to re-install them manually to see them.
The Liferay component has been updated from version 5.1.1 to version 6.0.6. if your custom portlets are based on the standard Java Portlet API specs, they should continue to work. If they were using specific Liferay features they could need to be updated to work with the new Liferay version. Please refer to Liferay documentation for more information on changes between the two versions.
In BMC Capacity Optimization dashboard 4.x, you can grant access rights on a dashboard (that is, community) to an Access Group or directly to some users. Only community-Access Groups associations will be preserved. BMC recommends that you review your direct associations to users before upgrading, because they will be lost in the upgrade process. In BMC Capacity Optimization 9.0, in fact, community access is granted only through Access Groups: no direct community-user association is permitted.