Preparing to upgrade the Application Server and ETL Engine

Before upgrading to the latest version of the Application Server and ETL Engine, review the following sections and complete the required activities to ensure that the installation program can successfully perform the upgrade.

Complete the pre-upgrade tasks

  • Review the System-requirements-for-the-Application-Server-and-ETL-Engine to ensure that your system meets the new requirements before starting the upgrade.
  • Starting version 11.5, the memory requirements 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.
  • In a standard oracle database deployment, database administrators implement the custom security hardening scripts to adhere to internal policies (such as restricting visibility to some common packages or views). However, for the TrueSight Capacity Optimizationproduct installer to query the ALL_USERS table in Oracle to retrieve all database users, ensure that your Oracle environment is not hardened.
  • Ensure that you have a full database and file-system backup of the installation folder or VM snapshot of all servers that host TrueSight Capacity Optimization components. The Repository folder contains deployment-specific historical data that must be preserved upon upgrade. Restoring the database backup will suffice to restart the upgrade from scratch. Also, if you have manually customized any configurations, such as TLS communications between products or Single Sign-On domain information, ensure that you have a backup of these configurations. You need to restore them upon upgrade.
  • Ensure that you use a supported version of the Oracle client. If you use an unsupported version, the upgrade fails with a validation error. 
  • Ensure that the Datahub system has a minimum of 10 GB free space for the H2 data migration. H2 databases used by the Near-Real-Time Warehouse service are replaced with a new local storage technology for better resilience and performance. The content of the H2 databases is automatically migrated to this new storage during upgrade. 

  • You can upgrade the product as a root or a non-root user:

    • If a shared repository is used and not mounted via /etc/fstab in your existing installation, BMC recommends that you upgrade the product as a root user.
    • For all other installation types, a non-root user can be used to run product updates.

    If you are using a local repository and want to use a shared repository after the upgrade, perform the following steps:

    1. Take a backup of your existing repository.
    2. Perform the upgrade as a root user, and select Shared Repository on the Shared RepositoryConfiguration page.
    3. Copy the backup taken before starting the upgrade to $BCO_HOME/repository.

Upgrade scenarios for a typical or distributed deployment

Depending on how you deployed the Application Server components, your upgrade process can vary.

Upgrade process for a typical deployment

  1. Upgrade the Primary Server (which includes the web server and data hub) and ETL Engine.
  2. Upgrade additional local or remote ETL Engines, if deployed

Upgrade process for a distributed deployment

  1. Upgrade the Primary Server (which includes the web server and database components).
  2. Upgrade the remaining components (data hub, primary scheduler, additional web servers, additional ETL Engines). If these components are on separate servers, upgrade them in the following recommended order.
    1. Data hub
    2. Primary scheduler
    3. Additional web servers
    4. Additional local or remote ETL Engines

Check the version of the integrated TrueSight Operations Management 

Consider the following scenarios to work with the TrueSight Operations Management extractors:

Scenario 1: TrueSight Operations Management is upgraded to version 10.1 or later

Scenario 2: TrueSight Operations Management version is not upgraded to 10.1 or later

If you were using the old TrueSight Operations Management extractors, you must now use the corresponding new extractors.

Old extractor

Corresponding new extractor

To use the new extractor, perform the following steps:

  1. Stop the old extractor.
  2. Configure and schedule the corresponding new extractor.
    Note: Ensure that you use the Entity Catalog from the corresponding old extractor.

You can continue to use the old extractors:

  • BMC - TrueSight Operations Management 9.0/9.5/9.6/10.0 extractor
  • BMC - TrueSight Operations Management 9.0/9.5/9.6/10.0 Generic View Extractor

For information about upgrading to the latest TrueSight Operations Management version, see Upgrading to TrueSight Operations Management 11.3.01.

Where to go from here

Perform the other pre-upgrade tasks listed in Preparing-to-upgrade-TrueSight-Capacity-Optimization.

 

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