HTTPS configured DA fails to start after upgrade to 25.4.4 or later

Products

• Network Observability
• CA Performance Management

Issue/Introduction

After upgrading to Performance Management 25.4.4, the data aggregator starts, but nothing is listening on its configured port (normally 8582).

Looking in the <DA_INSTALL_DIR>/IMDataAggregator/data/log/netops-data-aggregator.log file we see the following:

Caused by: java.io.IOException: Alias name [sscada] does not identify a key entry

Environment

Upgrade to Performance Management 25.4.4 or later

Cause

The alias in the keystore is not sscada.

To verify:

<DA_INSTALL_DIR>/IMDataAggregator/jre/bin/keytool -list -keystore <DA_INSTALL_DIR>/IMDataAggregator/config/ssl/keystore 

Enter the keystore password when prompted.

Example output:

Enter keystore password:
Keystore type: PKCS12
Keystore provider: SUN

Your keystore contains 1 entry

1, Aug 25, 2025, PrivateKeyEntry,

The alias in this example is 1 and not sscada

Resolution

Run the <DA_INSTALL_DIR>/scripts/sslConfig.sh command

Just launching the command will set the correct alias

Choose option 6 to verify this has changed

Example:

------------------------------------------
Data Aggregator HTTPS/JMX SSL Configurator
------------------------------------------

Please choose an option:
1 - Enable DA HTTPS/JMX SSL
2 - Disable DA HTTPS/JMX SSL
3 - Import a certificate into truststore
4 - Import updated DA signed certificate
5 - List truststore
6 - List keystore
7 - Generate CSR for keystore
8 - Delete a certificate from truststore or keystore
9 - Export the DA public certificate from keystore
q - Quit

------------------------------------------------
HTTPS status                       : ENABLED
HTTPS Connection status [port 8582]: UP
------------------------------------------------
ActiveMQ JMX over SSL status       : ENABLED
ActiveMQ JMX SSL connection status : SUCCESS
------------------------------------------------
Your choice: [Default=1]:6
Enter an exact or partial alias (Blank for all):
Details (y/[n]): n

sscada, Aug 25, 2025, PrivateKeyEntry,

-------------------------------------------------------------------
Press enter to go back to the main menu.

After correcting, restart the  Data Aggregator process:

systemctl stop dadaemon
systemctl start dadaemon

Additional Information

If you are planning to upgrade, you can check this ahead of time to avoid this issue after upgrade

<DA_INSTALL_DIR>/IMDataAggregator/jre/bin/keytool -list -keystore <DA_INSTALL_DIR>/IMDataAggregator/apache-karaf/etc/keystore 

If the alias is not sscada, run the sslConfig.sh tool as noted above.