Error: Old EEM hostname appears during WCC 12․1 or 24․x upgrade

Products

• Autosys Workload Automation

Issue/Introduction

During a Web UI (WCC) upgrade or response file creation, the installer interview phase incorrectly displays a decommissioned CA EEM server hostname․​​​​​‌​

SYMPTOMS:

• The CA EEM Properties screen shows an old or decommissioned EEM server․

• The current instance of WCC has never actively used this EEM server․

• Running wcc_config․sh --displayeem shows the correct EEM configuration․

CONTEXT: This occurs when upgrading WCC from 12․x to newer versions like 12․1 or 24․x

IMPACT: You cannot proceed smoothly through the installer interview phase․

Environment

 

• OS: Red Hat Enterprise Linux

• Database: Oracle, SQL Server, or PostgreSQL

• Application: AutoSys Workload Automation / WCC 12․x and 24․x

 

Cause

During an upgrade, the AutoSys installer retrieves the previous EEM hostname directly from the CFG_GLOBAL_PREF table in the WCC Database․While wcc_config․sh --displayeem reads from the current application runtime and local configuration files, the installer establishes a direct JDBC connection to the database․
If a previous EEM migration updated the filesystem but failed to update this specific database record, the installer continually fetches the decommissioned server․

Resolution

PREREQUISITES:

• Database Administrator (DBA) access or direct access to the WCC database․

STEPS:

Step 1:
CONNECT TO THE WCC DATABASE Connect to the database hosting the WCC schema using your preferred database client (e․g․, SQL*Plus, pgAdmin, SQL Server Management Studio)․

Step 2:
VERIFY THE STALE RECORD
Command:
SELECT PREFKEY, PREFVALUE FROM CFG_GLOBAL_PREF WHERE PREFKEY='internal․eem․host';

EXPECTED: The query returns the old EEM hostname in the PREFVALUE column․

Step 3:
UPDATE THE DATABASE RECORD Run an UPDATE statement to replace the decommissioned server with your current, active EEM hostname exactly as it appears in your wcc_config․sh output․
Command:
UPDATE CFG_GLOBAL_PREF SET PREFVALUE = '[FQDN / hostname]' WHERE PREFKEY='internal․eem․host';

Step 4:
COMMIT THE TRANSACTION If you are using a database that requires explicit commits (such as Oracle or PostgreSQL), ensure you commit the change․
Command:
COMMIT;

Step 5:
RESTART THE INSTALLER.
Completely exit any stalled installer sessions․
Rerun the installer to generate your response file․

 

EXPECTED: The installer queries the database, finds the correct EEM hostname, and allows you to proceed․

VERIFY SUCCESS:

• The installer interview phase displays the correct active CA EEM server․