search cancel

WCC URL stopped working when the AutoSys Webserver, AEWS, was not available

book

Article ID: 202095

calendar_today

Updated On:

Products

CA Workload Automation AE - Business Agents (AutoSys) CA Workload Automation AE - System Agent (AutoSys) CA Workload Automation AE - Scheduler (AutoSys) Workload Automation Agent CA Workload Automation AE

Issue/Introduction

EEM is accessible but WCC is not.

Restarting WCC does not resolve the issue.

CA-wcc-services would initialize but CA-wcc would not.

The logs show "SERVICE_CONTROL_CODE : 4" and not much else.

 

 

Environment

Release : 11.4.7

Component : WORKLOAD CONTROL CENTER

Resolution

In WCC versions lower than r12, WCC may not fully initialize and startup if you have AutoSys instances defined with WebServers and those WebServers are not available.

Confirm your AutoSys Webservers are available and working without issue before restarting WCC again.

 

If the web servers are no longer available and you cannot restart WCC to remove them from the autosys server definition you can do so via direct db updates:

Run the following queries in the db.

select * from AO_SCHEDULER;
select * from CFG_AUTOSYS_11_3;

Null out the WEBSERVICEURL
Example:
update CFG_AUTOSYS_11_3 set WEBSERVICESURL='' where NAME like 'server';
(replacing 'server' with the actual server names in the prior queries)
Also run:
update AO_SCHEDULER set ADDRESS='', CONNECTED=0, PORT=0, PROTOCOL='';

Then restart CA-wcc.

Again, WCC r12 will resolve the issue where if WCC has issues with any AEWS WebServers defined that it may cause WCC to not start and initialize properly.