No connections available in Web Client Server Alias field

Products

• CA Workload Automation DE

Issue/Introduction

After patching the Web Client, the prior defined connection details are missing. How can we re-add these connection details?

 

Environment

Release : 12.3

Component : WORKLOAD AUTOMATION DE (DSERIES) WEB CLIENT

Resolution

After patching Web Client to address log4j vulnerability, customer was unable to login as there were no connections listed in Server Alias to choose from. The Web Client service typically runs as a service account. Customer restarted Web Client as root user and the connections are now listed. Advised customer to perform following steps:

1. Stop the Web Client service.
2. Move the <installdir>/repo/connections_tbl_new.dat file to /tmp directory for backup purposes.
3. Change ownership recursively on the Web Client installation directory to reflect the desired service account.
4. Start the Web Client service.
5. Access the URL as documented in the README file in the Web Client installation directory.
6. Provide user credentials to login.
7. In the Server Alias field on the login screen, choose Other.
8. This will prompt you to define a new connection. Provide the appropriate details for your connections..
9. A new connections_tbl_new.dat file is generated in <installdir>/repo/.

Once you've logged in, you can define the remaining connections within the Web Client using "Manage Connections"