Update AAI Database Password for Application in Multi-Instance Environment

Products

• Automation Analytics & Intelligence

Issue/Introduction

You need to update the Oracle database password for the account used to run the application in an environment with Primary and Business Continuity Plan instances ․​​​​​‌​‍

SYMPTOMS:

• The configuration tool attempts to connect to the database using the current password upon startup ․

• Changing the password on the primary instance while the secondary instance is down may cause the configuration tool to lock the database account when started on the secondary instance ․

CONTEXT: This occurs when updating database credentials in a highly available or multi-node setup ․

IMPACT: The application on the secondary instance cannot start or connect to the database, potentially locking the database service account ․

Environment

Automation Analytics & Intelligence (AAI) 24.X

Resolution

RECOMMENDED APPROACH:

1․ START CONFIGURATION TOOL Start the configuration tool on both the Primary and Business Continuity Plan instances ․

2․ UPDATE DATABASE PASSWORD Update the account password directly on the Oracle database ․

3․ UPDATE APPLICATION CONFIGURATIONS Change the password in the configuration tool on both instances and save the configurations ․

EXPECTED: The application connects to the database with the new password on all instances ․

ALTERNATIVE APPROACH (MANUAL FILE UPDATE):

1․ STOP SERVICES Ensure all application services on the Business Continuity Plan instance are stopped ․

2․ EDIT DATABASE CONFIGURATION FILE Path: <Automation_Analytics_Intelligence>/jboss/standalone/configuration/jaws-database․xml

Locate the jaws-configuration section ․
Update the encrypted value to false: <encrypted>false</encrypted>
Update the password value to your new clear-text password: <password><Clear text Password></password>

Save the file ․
NOTE: Do not modify other connection parameters unless required ․

3․ ENCRYPT NEW PASSWORD Launch the Configuration tool utility ․
Navigate to the database tab ․
Click the encrypt button to encrypt the password ․
Save the changes ․

EXPECTED: The configuration tool updates the XML file with the newly encrypted password ․

 

Additional Information

ROOT CAUSE:
The configuration tool automatically attempts to connect to the database to validate the schema version upon startup ․
If the stored password does not match the updated database password, the connection fails and may lock the account ․

 

PREVENTION:
Always update the password simultaneously on all active configuration tools or manually update the offline configuration files before launching the tool ․