Upgrading the Reporting Server

As an AAI administrator, you upgrade the Reporting Server in Windows or Linux.

Use the compatibility matrix (compatibility matrix) to check all relevant Automic Automation Intelligence components and prerequisites for vendor, version or setup information (Java version, browser compatibility and so on). For more information, see Compatibility Information.

set MAIL_AUTH=<true or false>
set MAIL_HOST=<MAIL_HOST>
set MAIL_PORT=25
set MAIL_PROTOCOL=smtp
set MAIL_USERNAME=<MAIL_USERNAME>
set MAIL_PASSWORD=<MAIL_PASSWORD>
set MAIL_FROM=<MAIL_FROM>

Upgrading the Reporting Server on Windows

To upgrade the Reporting Server on Windows, you have to use the same terma-bi-windows-installer executable file that was used for the installation.

1. If you have not done so yet, go to https://downloads.automic.com/, log in with your Broadcom account and download the relevant AAI product or solution. For more information, see Downloads.

2. Install the terma-bi-win-installer-i4j archive, extract it and run the terma-bi-windows-installer-<version>.exe file to setup the installer.

3. Follow the instructions of the Install4J wizard.

   The installer automatically detects whether a previous installation exists and starts the upgrade process.

   If the upgrade process detects that there is no Chrome available on the system, or that the current version is already up-to-date, a corresponding message is displayed.

To access the upgrade logs, check the upgrade-logs.txt file located in the upgrade directory terma-bi-win-installer-i4j-<version>\upgrade.

Upgrading the Reporting Server on Linux

This section guides you through upgrading the Reporting Server on Linux.

Prerequisites

Before upgrading your system, make sure you meet the following requirements:

• Ensure that the current Reporting Server installation is working correctly.

• Backup your current Reporting Server installation or snapshot the virtual machine on which is running with the machine powered off.

• Ensure that there is no systemd service defined for the Reporting Server. If there are custom services, make sure you disable and remove them, as the upgrade will install a systemd service.

• Ensure that systemctl daemon-reload has been executed as root after removing the systemd service definition.

• Ensure that the symlink from /etc/aai/bi-reporting/terma-bi-install.conf points to the termaBi.config file corresponding to your current installation.

  Note:

  Make sure that the termaBi.config file is available in your system as it is required for the upgrade process. If the file is not available, it must be created using the parameters of the current version (the one that you want to upgrade).

  The Reporting Server service account must be able to read and write the symlink configuration, as well as create files in the /etc/aai/bi-reporting/ directory.

Upgrade Process

1. Unpack the .zip file to get the terma-bi-linux-installer-<version>.rpm and terma-bi-configure-rpm.sh files.

2. Run terma-bi-configure-rpm.sh.

Installing a Hotfix

If you have already installed the Reporting Server 2.0 and want to upgrade to a hotfix version, you do not need to go through the whole upgrade process. To install a hotfix version, do the following:

1. Go to https://downloads.automic.com/, log in with your Broadcom account and download the latest version of the Reporting Server. For more information, see Downloads.

2. Unpack the .zip file (AAI.BI_Reports.Upgrade.<DBType>.zip) to get the processedReports.zip.

3. Run the js-import utility to load the reports (Oracle and SQL Server):

   Windows

   <BI_SERVER_INST_DIR>\buildomatic\js-import.bat --input-zip <path to Oracle or SqlServer processedReports zip> --update

   Linux

   <BI_SERVER_INST_DIR>/buildomatic/js-import.sh --input-zip <path to Oracle or SqlServer processedReports zip> --update

See also:

• Preparing for the AAI Upgrade

• Upgrading the Reporting Server

• Configuring the Reporting Server for TLS Authentication