Performing the upgrade

The following video (4:06) illustrates how you can upgrade from TrueSight IT Data Analytics 2.1 to TrueSight IT Data Analytics 2.5

 The [confluence_iframe] macro is a standalone macro and it cannot be used inline. Click on this message for details.
This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.https://youtu.be/nFhHpbQY35Q

This topic contains the following information:

• • Before you begin
  • Upgrade sequence in a multiple-server deployment
  • Upgrading the product or particular product components
  • Troubleshooting a failed upgrade
  • Post-upgrade notes
  • Upgrade and integration
  • Where to go from here

Before you begin

Ensure that the following requirements are met:

• Ensure that all the components of the product are up and running.
• Depending on your operating system, ensure that the following environment variable is already set.
• The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
  This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.
• Create a back up of all the indexed data at an appropriate location. For more information, see Backing-up-and-restoring-data.

• Ensure that the existing saved searches are not configured with duplicate names.

  Recommendation

  If you have saved searches or content pack components containing field (or tag) names starting with an underscore, BMC recommends you to modify such saved searches and content pack components to use renamed fields and tags.

  This is important because with version 2.5.00, fields and tags starting with an underscore (_) are not supported. Post-upgrade, such fields and tags are automatically renamed to start with x_. Thus, unless you modify such fields and tags beforehand, post-upgrade saved searches and content packs containing such fields (or tags) will not be usable. For more information, see Post-upgrade notes.

Upgrade sequence in a multiple-server deployment

If you are operating in a multiple-server deployment, the order in which you upgrade the components and the order in which you start the components is important.

You need to upgrade the components in the following order of priority. The following order also applies for starting the services post-upgrade. For more information, see Starting-or-stopping-product-services.

1. Configuration Database
2. Indexer
3. Upgrade the following components (order is not important):
   
   • Collection Station
   • Console Server
   • Search

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. The upgrade sequence is important while upgrading in a multiple-server deployment.

   
   

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. (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.
9. (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.

Troubleshooting a failed upgrade

While running the upgrade, it is possible that you see the Feature Configuration Database failed error on the Installation Summary screen.

This error is likely to occur in a scenario if you upgraded from version 2.0.00 to 2.1.00 and then to 2.5.00. This issue can occur due to a conflict between a user and its role mapping that might have occurred in version 2.1.00 of the product. To resolve the issue, please contact BMC Support.

Post-upgrade notes

The following notes are important to consider after an upgrade:

• 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.
• With version 2.5.00, the following changes apply:
  • You cannot name fields and tags starting with an underscore (_). If the previously indexed data contains any instances of field (or tag) names starting with an underscore, post-upgrade such fields and tags are automatically renamed to start with "x". For example a field name _type is renamed to x_type.
    With this feature, the following changes apply:
    • If you have saved searches containing field (or tag) names starting with underscore: Post-upgrade, modify the saved search query and change the field (or tag) name instances to start with an x.
    • If you have content packs components containing field (or tag) names starting with underscore: Contact BMC Support.
  • Square brackets cannot be used while naming a component that can be included in a content pack, for example, saved searches, data patterns, collection profiles, and dashboards. Post-upgrade, any such components using square brackets in the name are renamed to replace square brackets with round brackets. For example, a data pattern DB [Oracle] will be renamed to DB (Oracle) after the upgrade.
  • The Include subdirectories check box is no longer available while creating the following data collectors. Instead, you can specify the ** wildcard sequence at the end of the directory path to collect data from subdirectories.
    • Monitor-file-on-Collection-Agent
    • Monitor-file-over-SSH
    • Monitor-file-over-Windows-share
  • With this release, the configuration changes that were earlier done by navigating to conf\services, must be performed by navigating to custom\conf\services. This is important to ensure successful upgrades in the future.
  • Data collectors created by using collection profiles use the following naming convention. This naming convention provides information about the collection profile name and the content pack name.
    
    • If the collection profile is created by a user: <collectionProfileName>_<dataCollectorTemplateName>_<hostName>.
      Example: A data collector created by using the collection profile, "CollP1", associated with the host, "HostA" and using the data collector template, "DCT1" is named as "CollP1_DCT1_HostA".
    • If the collection profile is imported via a content pack: <collectionProfileName> [contentPackName]_<dataCollectorTemplateName>_<hostName>.
      Example: A data collector created by using the collection profile, "CollP1", imported via a content pack, "CP1", associated with the host, "HostA" and using the data collector template, "DCT1" is named as "CollP1 [CP1]_DCT1_HostA".

Upgrade and integration

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

After upgrading to version 2.5.00 of the product, if you continue to use version 10.1.00 of TrueSight Presentation Server, the integration will actually occur with TrueSight Infrastructure Management 10.0.500 registered with TrueSight Presentation Server. In this scenario, you can continue to get and send events from and to the TrueSight Infrastructure Management server. However, some integration features might not be available.

For more information, see Integrating.

Where to go from here

(Optional) Start using BMC Atrium Single Sign-On 9.0 as your authentication mechanism by running the enablesso CLI command.