install AutoSys and WebUI with existing databases but with new EEM servers

Products

• Autosys Workload Automation

Issue/Introduction

Creating new VMs for schedulers using existing databases, the install failed with the following in the cawa_installer* log

 

2025-04-23 08:52:52,929 [main] DEBUG com.ca.wla.ae.installer.common.security.AEValidateEEMProperties(390) - [Authenticate Error: Authentication Failed]
com.ca.eiam.SafeException: EE_SPONSORERROR iSponsor Error
2025-04-23 08:52:52,930 [main] WARN  com.ca.wla.ae.installer.common.security.AEValidateEEMProperties(488) - EEM connection error
2025-04-23 08:52:52,931 [main] ERROR com.ca.wla.ae.installer.logger.LogHelper(27) - [CAUAJM_E_112101] Unable to connect to the CA EEM server.
EE_SPONSORERROR iSponsor Error
2025-04-23 08:52:52,932 [main] DEBUG com.ca.wla.ae.installer.logger.LogHelper(35) - Setting the result variables:$AE_SEC_PRE_VALIDATE_RETURN_STATUS$ to:E_AE_Remote_EEM_Connection :$AE_SEC_PRE_VALIDATE_RETURN_MSG$ to:[CAUAJM_E_112101] Unable to connect to the CA EEM server.
EE_SPONSORERROR iSponsor Error
2025-04-23 08:52:52,933 [main] DEBUG com.ca.wla.ae.installer.customaction.initialize.AESetDefaultAndValidateSecurityStatus(110) - eemServers=

 

Resolution

From within the WebUI database run the following:

delete from CFG_GLOBAL_PREF where prefkey='internal.eem.host'

 

From within the AutoSys database run the following:

delete from aedbadmin.ujo_keymaster where hostid = 'SECURITY'; 
update aedbadmin.ujo_alamode set int_val=0 where type = 'JOB';
update aedbadmin.ujo_alamode set int_val=0 where type = 'EVT'; 
delete from aedbadmin.ujo_alamode where type = 'SEC'; 
delete from aedbadmin.ujo_blobs where blob_id = 'SAFECERT';

After the above, AutoSys and the WebUI can be installed against existing databases and point to new EEM host(s).

 

NOTES:

The examples above are for Oracle, similar SQL should be run for MSSQL, SYBASE and Postgres.

Also make sure to commit the database changes and execute them in all the databases if using more than one.