WCC Console Down with CAUAJM_E_00067 After AutoSys 24.2 Upgrade

Products

• Autosys Workload Automation

Issue/Introduction

After upgrading AutoSys Workload Automation from version 12.x to 24.x, the WCC console fails to launch or display data.

Symptoms:

• WCC Web UI returns an "HTTP 500 Internal Server Error."
• WCC Web UI displays the following errors:
  • E190098 TSL (web services validation) - A connection exception was encountered:
https://WCC_URL:9443/AEWS returned status 401.
  • E190099 TSL (monitoring id validation) - Connection exception encountered. CAUAJM E 00065 Validation Internal Error: User failed authentication..
• WCC logs show error code CAUAJM_E_00067.
• Authentication failures such as EE_AUTHFAILED or E150010 are present in the CA-wcc.log.
• AutoSys services may show warning CAUAJM_W_119012 indicating EEM security configuration issues.

Environment

Product: AutoSys Workload Automation
Versions: Upgrading from 12.x to 24.x (e.g., 24.2)
Component: Workload Control Center (WCC), EEM
OS: Linux / Windows

Cause

During the major version upgrade to 24.x, existing EEM certificates used by the AutoSys Application Server and WCC components become invalid. The security handshake requires regenerated certificates aligned with the 24.x security protocols.

Resolution

To restore connectivity, you must regenerate the EEM certificates for both the AutoSys instance and the WCC component.

Step 1: Regenerate AutoSys Instance Certificates

1. Log in to the AutoSys server and launch the security utility:
   autosys_secure
2. Select Option 2: Manage CA EEM security settings.
3. Select Option 1: Manage CA EEM server settings.
4. Select Option 2: Set CA EEM server location and regenerate certificate.
5. Follow the prompts to provide the EEM Server Name, Admin ID (EiamAdmin), and Password.
6. Restart the AutoSys WebServer service.

Step 2: Regenerate WCC Component Certificates

1. Navigate to the safex directory in your WCC installation.
2. Run the following command to generate new wcc.pem and wcc.key files: 
   ./safex -h <eem_hostname> -u EiamAdmin -p <password> -f IssueCertificate.xml
3. Copy the new wcc.pem and wcc.key files to the $CA_WCC_INSTALL_LOCATION/data/config directory.
4. Register the new certificates using wcc_config: 
   ./wcc_config.sh -u <admin> -p <pass> --eemhostname <eem_host> --eemcertname wcc.pem --eemcertkey wcc.key --eemadmin EiamAdmin --eempassword <eem_pass>
5. Restart the WCC services: 
   unisrvcntr restart CA-wcc-services

Additional Information

Link to our main Contact Broadcom support article

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on the respective region.

AutoSys TechDocs: Set CA EEM Server Location and Regenerate Certificate
KD 430428: Regenerating EEM Certificates Using autosys_secure
KD 192947: Autosys WCC / WebUI URL gives HTTP 500 internal server error