Automation Analytics & Intelligence(AAI/JAWS) Upgrade Tips

Products

Automation Analytics & Intelligence

Issue/Introduction

Automation Analytics & Intelligence(AAI/ formerly known JAWS) Upgrade Tips.

Please review this document before upgrading AAI in addition to the AAI Upgrade Guide.

Environment

Release : 26.0.0

Resolution

Before upgrading, review the latest Release Notes for the version you will be upgrading to as well as any versions in between the version you are currently on and the version you are upgrading to, to be aware of any fixes, new features, and database changes that may be required after upgrading.

Please also review the AAI Upgrade Guide available here.

Upgrade workflow:

1. Back up the AAI Database

2. Back up AAI Installation Directory

3. If upgrading from 24.1.x or earlier, AAI will require a new version of Java. Releases after 24.2 require Java 17.x and the JAVA_HOME variable must be set to the new Java path.

3. Download upgrade file for Windows or Linux from https://support.broadcom.com/enterprise-software/download-center, copy to the AAI server. (If Linux change permissions on the file "chmod 755 upgrade.sh".

4. Stop AAI services. "jaws.sh stopync" on Linux or shutdown the "Automation Analytics & Intelligence" service on Windows.

- - On Linux verify jboss is non longer running.

ps -eaf | grep jboss

- - Make sure any files within the AAI directory are not open when running the upgrade.
  - Stop the Webswing config tool process by running
    - Linux: <Install Dir>/webswing.sh stop
    - Windows: <Install Dir>\webswing.bat stop
  - If any AAI process or files are open it will caue the upgrade to fail

5. Run the upgrade script. ./upgrade.sh(Linux) or upgrade.bat(Windows).

6. If there are any errors during the upgrade please check the upgrade.log in the <Upgrade Files>/install/log directory and look towards the bottom of the file.

7. A file name like upgradeJawsDbTo26.x.x.sql will be created in the /<Install Dir>/scripts directory. Have your DBA run this script to update the database schema with the user that connects to AAI.

Additional Component Upgrades

Data Provider Upgrades
- CA7 Data Provider upgrade steps can be found here.
- IWS Data Provider upgrade steps can be found here.
Connector Upgrades
- IWS Connector - Follow the steps here for upgrading the IWS connector.
- For All other Universal Connectors follow the upgrade steps for the specifc connector:
- HTTPS/TLS: If your Universal Connectors are configured to user HTTPS/TLS there are required post upgrade steps to regenerate and redeploy the connector jar that connector uses to store its certificate chain, that must be followed as documented here.

Upgrade Tips:

On Linux you will need X11 forwarding in order to run the upgrade script interactively or you can use the headless upgrade procedure here.
- We recommend using MobaXterm for easy X11 setup, or if you will be using Xming with Putty, you can follow the steps for configuring Xming with Putty.
Ensure the database scripts run after upgrade are run by the user that AAI uses to connect to the database and that user has permissions to those tables or you may see an error like below:
ORA-00942: table or view does not exist
You should be able to upgrade to the latest version of AAI from most versions. If you are on a version earlier then 5.8.6 please contact Broadcom Support before attempting any upgrade.

Please ensure your database server has enough storage for expansion during upgrade.

Additional Information

AAI 26.0 and later has a new Frontend Gateway service that you now use to connect to the AAI webUI and the configuration tool, which means the same port will be used to connect to AAI and the configuration tool.
In 26.0 the log file location has moved to <Install Dir>/log instead of <Install dir>/jboss/standalone/log as documented here.
The script to start AAI on Linux has been renamed to aai.sh and has some new options to start/stop individual micro services as documented here.
A complete list of platform changes for AAI 26.0 can be found here.