TrueSight Server Automation Console Automatic Upgrade: Windows only

In most cases, the TrueSight Server Automation Console version needs to match the Application Server version for the console to function correctly. When a console of an earlier version is detected, you are offered the option of having the console automatically upgrade itself.

For certain consoles, you can choose not to upgrade and not to perform the compatibility check. For more information, see To enable communication with clients of an earlier version of TrueSight Server Automation.

TrueSight Server Automation Console Automatic Upgrade supports all types of upgrades, including minor releases, service packs, and hotfixes.

To use the TrueSight Server Automation Console Automatic Upgrade, you need to install the TrueSight Server Automation Upgrade Service and configure the installer path in blasadmin. See the following sections for steps on installation, configuration, prerequisites, and uninstallation:

• Installing the TrueSight Server Automation Upgrade Service
• Prerequisites
• Configuring the blasadmin utility
• Uninstalling the TrueSight Server Automation Upgrade Service

Installing the TrueSight Server Automation Upgrade Service

The TrueSight Server Automation Upgrade Service can be installed while you are installing or upgrading the TrueSight Server Automation Console. To install the TrueSight Server Automation Upgrade Service, perform one of the following actions, depending on the type of installation or upgrade that you are performing:

Prerequisites

Before you use the TrueSight Server Automation Console Automatic Upgrade feature, ensure that the system meets the following requirements:

• You must disable the use of client-side certificates that secure access between Application Servers and agents or repeaters. For more information, see TLS-with-client-side-certificates-Discontinuing-use-of-client-side-certificates.
• The server on which the TrueSight Server Automation Console is installed has sufficient free memory (at least three times the size of the console installer file used for upgrade).

•  An RSCD agent must be installed on the server on which the console installer file is stored.

  Note

  Ensure that the RSCD agent is configured so that the console has read access to the location on which the console installer file is saved.

• The ConsoleInstallerLocation parameter in the blasadmin utility is set with the correct NSH path URL that points to the location of the TrueSight Server Automation Console installer file. See the steps provided in the following section.

Configuring the blasadmin utility

The administrator must set the ConsoleInstallerLocation parameter in the blasadmin utility to point to the location of the TrueSight Server Automation Console installer. You must also set the level up to which you want to compare the version numbers of the Application Server and Console.

1. Download the TrueSight Server Automation Console installer file that is used to upgrade the console. See Downloading-the-installation-files for steps on downloading product files from the BMC Software Electronic Product Distribution (EPD) site.

2. Save the TrueSight Server Automation Console installer file on a host that has an RSCD agent installed on it.

   Note

   Do not change the name of the installer file after downloading it from the EPD because this may cause an error during the upgrade of the console.

3. Start the blasadmin utility. See Starting-the-Application-Server-Administration-console for more information.

4. Use the set <Component> <Parameter> <NSH path URL> command in the blasadmin utility to set the location of the TrueSight Server Automation Console installer in the ConsoleInstallerLocation parameter. See the following example:

   set ConfigManagerUI ConsoleInstallerLocation //File_Server/Repositories/BSAConsole_Installers/
   

   Note

   Ensure that the RCP installer absolute path is accessible from the RCP auto upgrade.

5. Use the show <command> <parameter> command in the blasadmin utility, to check whether the ConsoleInstallerLocation parameter setting is correct. See the following example:
   
   show ConfigManagerUI ConsoleInstallerLocation
   ConsoleInstallerLocation:{{code language="none"}}
   //File_Server/Repositories/BSAConsole_Installers/
   {{/code}}
6. You must also set the level up to which you want to compare the version numbers of the Application Server and Console. The version number level maybe set up tominor, micro, or build. In the version number 8.9.0.125, 8 is the major level, 9 is the minor level, 0 is the micro level, and 125 is the build level. The level you set depends on the type of upgrade you are performing.
   
   Use the following command to set the level up to which you want to compare the version numbers:
   set appserver VersionCompatibilityCheck minor|micro|build
   
   minor — Sets the check to compare the major and minor parts of the version numbers
   micro — Sets the check to compare the major, minor, and micro parts of the version numbers. This setting is the default.
   build — Sets the check to compare all four parts of the version numbers
   
   For example, suppose the Application Server version is 8.9.0.125 and the client version is 8.9.0.123.
   If you specify:
   set appserver VersionCompatibilityCheck micro
   The check would find that the version numbers are the same and allow the connection between the Application Server and the Console.
   If you specify:
   set appserver VersionCompatibilityCheck build
   The check would find that the version numbers are different, and upgrade the Console.

Uninstalling the TrueSight Server Automation Upgrade Service

The TrueSight Server Automation Upgrade Service is automatically uninstalled when you uninstall the TrueSight Server Automation Console. For more information about uninstalling TrueSight Server Automation Console, see Uninstalling-components-on-Windows.