Upgrade notes

This topic provides a summary of the key points that you should know if you are upgrading to TrueSight Capacity Optimization 11.5 or 11.5.01.

Upgrade notes for version 11.5.01

Version 11.5.01 is a Service Pack. Before you install this service pack, you must have previously installed the base version (11.5.00) of the product. 

This section provides key notes if you are upgrading to TrueSight Capacity Optimization 11.5.01. For information about enhancements and fixes added in this service pack, see 11.5.01: Service Pack 1.

What should you know before the upgrade?

  • The 11.5.01 installation differs from the earlier service pack installations. In the earlier service pack releases, a single file was used for the Application Server installation, whereas 11.5.01 requires an additional file to prepare for the installation. The TSCO_AppServer_ver11.5.01_AS_PREPARE.zip file prepares the Application Server for service pack installation, and the TSCO_AppServer_ver11.5.01_AS_CONTENT.zip file installs the service pack.

    For information about downloading and applying Service Pack 1, see Applying the service pack.

  • When you install 11.5.01, the status of some components on the Status page changes to Maintenance, and they are displayed in grey for 30 minutes. During this period, the status check and alert notifications are disabled. After 30 minutes, the status of the components is updated, and the status check and alert notifications are restored.

What should you know after the upgrade?

  • For custom data marts, a new identifier attribute and the VIEW macro are added in 11.5.01. After you upgrade to version 11.5.01, the functionalities for existing data marts will be affected.
    • A unique identifier will be automatically assigned to each data mart.
      • If the existing data mart has a physical name, it will be copied to the new identifier attribute. 
      • If the existing data mart does not have a physical name, a unique identifier as ER_V_<DataMartName> will be automatically assigned to each data mart. 
    • Existing data marts that are using the VTEMPL macro with erid will be automatically updated to use the VIEW macro and the identifier. The syntax is ${VIEW(identifieralias)}.
      For creating a new SQL query, BMC recommends using the VIEW macro instead of the VTEMPL macro. 
    • Relationships between data marts in the source environment are retained in the destination environment. The entire hierarchy tree of data marts is exported correctly due to identifiers. No additional manual task is needed to replicate the data mart relationships.
      For details, see Managing data marts for custom views, reports, and report templates.
    • If you have development and production environments with the same views, BMC recommends that you perform the following procedure after the upgrade. This procedure ensures that the identifiers are in sync between the two environments:
      1. Export the views from the production environment. 
      2. Import these view packages in the development environment. 
      3. Modify and validate the views in the development environment. 
      4. Export the views from the development environment. 
      5. Import these view packages in the production environment. 
  • Support for the Citrix XenServer extractor is dropped in TrueSight Capacity Optimization 11.5.01. You can use the BMC TrueSight Capacity Optimization Gateway VIS files parser ETL to collect data from the Citrix XenServer environment.

    If you are using the Citrix XenServer ETL for extracting data from your Citrix XenServer environments, data collection will stop after the upgrade.

    If you are using the Citrix XenServer ETL with the Gateway VIS files parser ETL and they are sharing the same entity catalog, data collection will continue with the Gateway VIS files parser ETL.

    You must unschedule and delete the existing Citrix XenServer ETLs.

  • When you view a recommendation for the first time after the upgrade, incomplete data is displayed in the recommendation details. It might take a day to populate all data. If you want to view the complete data in the recommendation details immediately, refresh the indicators in the Auto Forecasting Service using the Force indicators refresh option and run the Optimizer - daily task. For more information, see Viewing and managing backend services and Configuring the Optimizer task.

Upgrade notes for version 11.5

This section provides a summary of the key points that you should know if you are upgrading to TrueSight Capacity Optimization 11.5. For information about new features and enhancements added in this release, see 11.5 enhancements.

The TrueSight Capacity Optimization 11.5 installation program supports direct upgrades from the three most recent versions of the product, that is versions 10.7, 11.0, and 11.3.01. If you are running earlier versions of the product, you must perform at least one interim upgrade before you can directly upgrade to the latest version of the product. For more information, see Supported upgrade paths.

What should you know before the upgrade?

The prerequisites and upgrade instructions described in the Upgrading topic enable you to upgrade the TrueSight Capacity Optimization components smoothly. Do note these release-specific guidelines:

  • TrueSight Capacity Optimization 11.5 is supported with TrueSight Presentation Server 11.3.02
    • If you are upgrading from TrueSight Capacity Optimization 11.0 to 11.5, upgrade the Presentation Server to 11.3.01 and then apply the Fix Pack 11.3.02. 
    • If you are upgrading from TrueSight Capacity Optimization 11.3.01 to 11.5, you already have Presentation Server 11.3.01. Apply the Fix Pack 11.3.02.
  • The memory requirement for the system that hosts the Application Server has been increased from 8 GB to 16 GB. Ensure that your system has sufficient RAM to accommodate this increase in value. For details, see System requirements for the Application Server and ETL Engine.
  • The support for 11.x Oracle clients is dropped. If you are using any of the 11.x Oracle clients, you must upgrade the client to 12.1 or later (12.2.0.1.0 or later is recommended). Otherwise, the upgrade fails with a validation error. Oracle 11.2.x server is still supported.
  • The Datahub system should have a minimum of 10 GB of free space to accommodate changes in the request queue management for the Near-Real-Time Warehouse service.
  • Java runtime environment for TrueSight Capacity Optimization is upgraded to AdoptOpenJDK 11. If you are using the custom Java ETL, ensure that the ETL code and required additionally deployed libraries are compatible with AdoptOpenJDK 11. Also, if you are using a third-party JDBC driver for ETLs or reports, ensure that it is compatible with AdoptOpenJDK 11.

What should you know after the upgrade?

  • Storage-All-in-One is a new ETL that you can use to fetch data from storage systems. To ensure that this new ETL recognizes the existing entities, it must share the same entity catalog with the existing ETLs. Otherwise, you will need to reconcile entities to resolve duplicates. For details, see Entities and Metrics of Storage All-in-One ETL for TrueSight Capacity Optimization.
  • BMC recommends using the new Moviri Prometheus ETL instead of the Moviri Heapster ETL to collect data from Kubernetes. For the new ETL to recognize the existing entities, it must share the same entity catalog with the Moviri Heapster ETL. For details, see Moviri Integrator for TrueSight Capacity Optimization – k8s (Kubernetes) Prometheus.
  • The unit of measure for Spare CPU threshold of Overallocated optimizer condition is changed from GHz to number of cores. After you upgrade to 11.5, the default value for this field is automatically updated. However, you must review and revise any customized value for this field according to the new unit of measure. For more information, see Overallocated VM recommendation.
  • As support for Cloud Lifecycle Management is dropped, a few related components will not be available after upgrade to 11.5. However, all the imported data will be available. 

    • The Cloud Lifecycle Management Infrastructure and Services ETLs will be unscheduled automatically. When you try to run or schedule these ETLs, an error is displayed in the logs.

    • Capacity-Aware Placement Advice will not be available. Unregister the BCM Provider in the Cloud Lifecycle Management to be redirected to use the default round-robin placement policy. For details on unregistering the BCM Provider, see  Unregister the BCM Provider.
    • Automated Chargeback for Cloud Lifecycle Management reports will be preserved for historical purposes, but will not be updated.

    For details, see Dropped support for Cloud Lifecycle Management.

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

Comments