Let's say there are two WCC servers, <server1>.<example>.<com> and <server2>.<example>.<com> Both of them are using the same WCC database, so they effectively create a WCC cluster. In this WCC configuration, 3 AutoSys server configurations Finance, Trading, Loan were created to point to 3 different instances of AutoSys.
The tasks for collection of Jobs, Machines, Alarms etc,. they get distributed between the WCC nodes automatically by WCC clustering APIs. This document helps to identify what task is running on which WCC node, by issuing a database query against the WCC database.
Workload Automation AutoSys
For Oracle:
connect to the WCC database using sqlplus (example: sqlplus wccadmin/password@dbname) and run below query:
-- change the schema name wccadmin below if needed, to appropriate schema name
SET LINESIZE 10000
SET heading off
select T.TASKID || ' | ' || N.HOST || ' | ' || T.LAST_START_TIME || ' | ' || T.LAST_END_TIME || ' | ' || N.STATE
from wccadmin.CFG_COLLECTOR_TASKS T, wccadmin.CFG_COLLECTOR_NODES N
where T.NODE_ID = N.NODE_ID
order by T.LAST_END_TIME;
For SQL Server:
Connect to the WCC database using SQL Server Management Studio, select the WCC Database from the databases list and run below SQL query:
select T.TASKID, N.HOST, T.LAST_START_TIME, T.LAST_END_TIME, N.STATE
from CFG_COLLECTOR_TASKS T, CFG_COLLECTOR_NODES N
where T.NODE_ID = N.NODE_ID
order by T.LAST_END_TIME
For Postgres:
Connect to the WCC database using psql (example: psql -U <user> -d <wcc database name> hit enter and provide password)
-- change the schema name wccschema below if needed, to appropriate schema name
select T.TASKID, N.HOST, T.LAST_START_TIME, T.LAST_END_TIME, N.STATE
from wccschema.CFG_COLLECTOR_TASKS T, wccschema.CFG_COLLECTOR_NODES N
where T.NODE_ID = N.NODE_ID
order by T.LAST_END_TIME;
In our case above of 2 servers with 3 AutoSys configurations defined, in such a case, the output of the above query shows up like this:
CheckAndScheduleTasks |<server1>.<example>.<com> | 16-APR-25 06.11.00.768000 AM | 16-APR-25 06.11.01.410000 AM | ONLINE
Finance_MACHINE |<server1>.<example>.<com> | 16-APR-25 05.25.01.311000 PM | 16-APR-25 05.25.01.372000 PM | ONLINE
Trading_MACHINE |<server2>.<example>.<com> | 16-APR-25 05.25.11.309000 PM | 16-APR-25 05.25.11.367000 PM | ONLINE
Finance_JOB |<server2.<example>.<com> | 16-APR-25 05.25.21.270000 PM | 16-APR-25 05.25.21.307000 PM | ONLINE
Finance_ALARM |<server1>.<example>.<com> | 16-APR-25 05.25.21.306000 PM | 16-APR-25 05.25.21.332000 PM | ONLINE
Loan_MACHINE |<server2>.<example>.<com> | 16-APR-25 05.25.21.310000 PM | 16-APR-25 05.25.21.373000 PM | ONLINE
Trading_JOB |<server1>.<example>.<com> | 16-APR-25 05.25.22.944000 PM | 16-APR-25 05.25.22.982000 PM | ONLINE
Trading_ALARM |<server2>.<example>.<com> | 16-APR-25 05.25.22.974000 PM | 16-APR-25 05.25.22.999000 PM | ONLINE
Loan_ALARM |<server1>.<example>.<com> | 16-APR-25 05.25.24.630000 PM | 16-APR-25 05.25.24.655000 PM | ONLINE
Loan_JOB |<server2>.<example>.<com> | 16-APR-25 05.25.24.620000 PM | 16-APR-25 05.25.24.659000 PM | ONLINE
It'll be useful to identify if the task is running on a server where WCC services should not have been started, but the server was started by mistake.