Upgrading AAI in Non-Automated Mode

This section describes the procedure for AAI upgrading an instance of AAI.

General Upgrade Overview

When upgrading the AAI server and connectors with a new release package, you perform the following tasks:

1. Do all preparation steps and make sure all prerequisites are fulfilled.

   For information, see Preparing for the AAI Upgrade.

2. Take down the connectors that you want to upgrade.

   For information, see the topics related to your connectors under Connectors.

3. Upgrade and start your AAI system, as described in this topic in Upgrading the AAI Server.

4. Upgrade and start each connector.

   Again, for information, see the topics related to your connectors under Connectors.

This topic covers only the steps related to C. Upgrade and start your AAI system. Use the links in the previous overview for instructions for the other tasks.

Upgrading the AAI Server

1. Shut down the AAI server. The upgrade will not execute if the server is running.

2. If you have not done so yet, download the relevant AAI product or solution. For more information, see Downloads.

   Important !

   Use the compatibility matrix (compatibility matrix) to find the relevant information on supported versions, setup, or prerequisites. Check all AAI components and prerequisites for vendor, version or setup information. For more information, see Compatibility Information.

3. Extract the upgrade bundle into a temporary directory. Ensure the following directories and file are present:

   • install\build.xml

   • install\log\log4j.properties

   • install\properties

4. Execute the upgrade script.

   If you are upgrading from a v6.x.x version to v24.x.x., a warning that the Insight panel, and with it, any Insight Reports that you have will be deleted. For more information, see Considerations When Upgrading to v24.x.x from v6.x.x.

   

   • To accept that the Insight reports will be deleted and proceed with the upgrade, click OK.

   • To stop the upgrade and prevent the deletion of your Insight reports, click Cancel Upgrade.  

     If you cancel, you will find these messages in the <AAI_installation>/log/upgrade.log file:

      [java] 12:41:31.264 INFO [upgrade.main.UpgradeParameters] upgrade properties file is <AAI_installation>/product/upgrade/build/upgrade-24.0.0-SNAPSHOT/install/properties/upgrade.properties

      [java] 12:42:02.848 INFO [ui.dialogs.SummaryPanelOkOrCancel] User has CANCELLED the upgrade of Automation Analytics & Intelligence.

     Exception in thread "main" <AAI_installation>/product/upgrade/build/upgrade-24.0.0-SNAPSHOT/install/build.xml: 184: Java returned: 3

          at org.apache.tools.ant.taskdefs.Java.execute(Java.java:87)

          at org.apache.tools.ant.Task.perform(Task.java:364)

          at org.apache.tools.ant.Target.execute(Target.java:341)

          at org.apache.tools.ant.Target.performTasks(Target.java:369)

     
     

5. Execute the upgrade script. Select the directory for the AAI installation.

6. If your database type is Oracle, specify the Oracle Table Space Definitions.

   

7. Specify Telemetry Configuration Options.

   

   AAI uses telemetry to send product usage and system configuration information to Broadcom. Specify whether the upgrade is related to a new or additional planned usage under a Portfolio License Agreement (PLA) with Broadcom by selecting Yes or No.

   • Send telemetry data: Specifies whether you want to send the telemetry data to Broadcom or not.

   • Company Domain: Specifies the domain name of your company. It is the last part of your company's email address.

   • Enterprise Site ID: Specifies your company's unique login site ID that is listed on the Broadcom Support portal.

   • Internal Identifier: (Optional) Specifies your department's non-personally identifiable information (non-PII) identifier that you use for your company's tracking needs. Specify whether you want to use a proxy to send the telemetry data to Broadcom.

   • Proxy URI: Specifies the URI to access the proxy server.

   • Username: (Optional) Specifies the user name that is required for proxy authentication.

   • Password: (Optional) Specifies the AES encrypted password that is associated with the proxy URI user name.

   Click OK to continue after completing your selections.

8. A dialog will be displayed if the AAI upgrade is successful. Click OK to continue.

   The upgrade will perform the following:

   • Create a timestamped tarball from the existing AAI server installation in the directory install\backup

   • If needed, generate a SQL script for upgrading the database schema in the <Automation_Analytics_Intelligence>\scripts directory

   • Log the details in the install\l\og\upgrade.log

   • Store upgrade related properties in install\properties\upgrade.properties

9. A second dialog will be displayed if the AAI upgrade is successful. Click OK to continue.

10. Use an administration tool specific to your DBMS (a command line or GUI) to run the SQL upgrade script to update the AAI database schema.

    Note:

    This step is not necessary if there are no changes to the database.

11. Restart AAI and confirm the server operates properly.

Post V24 Upgrade Considerations

If you upgrade from an AAI version 6.x.x to version 24.0.0 or higher, after fully upgrading your production environments, you can remove the Jasper server that you used to need to produce previous AAI client and Insight reports.

In addition, please note that having a second mirroring historical database is no longer needed. That recommendation was based on the performance impact on daily processing of job and jobstream events of calls from the external JasperSoft server. Now that everything is integrated within AAI, this is no longer an issue. Therefore, you can discontinue mirroring the historical data.

 

See also:

• Preparing for the AAI Upgrade

• Stopping, Starting, Restarting the AAI Server

• Securing AAI: TLS and Kerberos

• Installation and Upgrade