Performing the upgrade


This topic provides information about upgrading the BMC TrueSight IT Data Analytics product from an earlier version.

The upgrade process requires you to upgrade all the components of the product to the latest version. For example, you cannot use Collection Station of an earlier version with all other components upgraded to the latest version. This is important to avoid potential problems and errors.

Notes

  • The Collection Agents are not considered to be one of the product components. For more information about the product components, see the product architecture.
  • If you are upgrading the Collection Stations, note that post-upgrade, the Collection Stations are included in the pool named, ITDAPool. For more information, see Data-collection-redundancy.
  • If you are operating in a multiple-server deployment, ensure that you upgrade the Configuration Database and Indexers before upgrading other components.

This topic contains the following information:

Before you begin

Ensure that the following requirements are met:

  • Ensure that the earlier version of the product is up and running.
  • Create a back up of the indexed data at an appropriate location. For more information, see Backing up and restoring data.

    Note

    The product does not automatically back up the indexed data.

Related topics

Where to find more information

If a problem occurs

Where to find troubleshooting information

Upgrading the product or particular product components

  1. Start the installation program by running the setup (for Windows) or setup.bin (for Linux) file. Click Next.

    Note

    In a multiple-server deployment, if you have multiple instances of a product component, then you need to run the upgrade individually on each of the computers hosting that product component.


  2. Read the license agreement and agree to the terms. Click Next.
  3. The type of installation you performed (earlier), determines the type of upgrade. Depending on the type of upgrade, perform the steps described in the following table:

    Upgrade type

    Steps

    Typical install

    Depending on your platform, you can choose to keep the following check box selections unchanged and click Next:

    • (Windows only) Check box for pinning the product to your Start menu, and starting the product services immediately after the upgrade is complete.  
    • (Windows and Linux) Check box for starting the product services immediately after the upgrade is complete.

    Custom install

    • The product components to be upgraded are automatically displayed as per your earlier installation. Click Next.
    • (Windows only) The check box for pinning the product to your Start menu is displayed. You can choose to keep the default selection unchanged and then click Next.

    The Installation Preview screen is displayed, providing information about the features to be installed, the total disk size, the destination directory, and so on.    

  4. Click Install to start the upgrade.  
  5. (Optional) Click View Log to see the installation log.
  6. To exit the installation program, click Done.
    By default, the following environment variable pointing to the product installation path is automatically set:
     

    Windows

    Linux

    %BMC_ITDA_HOME%

    $BMC_ITDA_HOME

  7. To view the upgraded version of the product, reload the current browser page so that the cached content is ignored.

    Tip

    Reload the page by pressing Ctrl+F5 on the browser page.

  8. (Applicable to a Collection Station upgrade only) After completing the Collection Station upgrade, navigate to %BMC_ITDA_HOME%\conf\services\collectionstation.conf file and then perform the following steps

    1. Edit the collectionstation.conf file and locate the line, wrapper.java.classpath.2=../../station/collection/lib/agent-foundation-1.0-SNAPSHOT.jar.
    2. Replace agent-foundation-1.0-SNAPSHOT.jar with agent-foundation-2.1.00-RELEASE.jar.
    3. Save the collectionstation.conf file.
    4. Restart the Collection Station.
      For more information, see Starting-or-stopping-product-services.

    This step is important to successfully upgrade the Collection Station.

  9. (Optional) To apply enhanced security checks and to prevent CSRF attacks, you might want to configure the system before you can access it. For more information, see Configuring-access-URLs.
  10. (Optional) If you want to enable security for the Console Server, you need to configure the system. For more information, see  Enabling-security-for-third-party-certificates.

     

    Note

    After completing the upgrade, ensure that you replace the earlier CLI files with the new ones available with the upgraded version of the product. This is important if you had earlier copied the CLI files on a computer other than the one hosting the product components. For more information, see Using-the-command-line-interface.

Upgrade and integration

Version 2.1.00 of the product is supported with version 10.1.00 of the BMC TrueSight Presentation Server. Note that integrating with version 10.1.00 of TrueSight Presentation Server actually involves an integration with TrueSight Infrastructure Management 10.0.500 registered with TrueSight Presentation Server.

If you upgrade to version 2.1.00 of the product, but continue to use version 10.0.00 of TrueSight Presentation Server, then you can still get and send events from and to the TrueSight Infrastructure Management server, which is registered with TrueSight Presentation Server. However, you cannot use some of the new integration features available.

For more information, see Integrating.

Troubleshooting user mapping conflicts

After completing the upgrade, it is possible that you might not be able to log on to the product. Such a scenario can occur due to the difference in how the user, user group, and role mapping was handled prior to version 2.1.00 of the product.

The following table provides a comparison of the user authentication approaches in the different versions.

Version 2.0 and earlier

Version 2.1 and later

  • Users are mapped to both user groups and roles.
  • User groups are mapped with users only.
  • Users are mapped to user groups.
  • User groups are mapped to roles.


For more information, see Troubleshooting-common-issues by selecting all the upgrade-related categories.

Where to go from here

(Optional) To start using BMC Atrium Single Sign-On 9.0 as your authentication mechanism, you need to run the enablesso CLI command to manually details of the Atrium Single Sign-On server.

 

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