WCC Job Views node count is different from the list of jobs. Also the Dashboard shows and old Autosys server that is no longer configured.
search cancel

WCC Job Views node count is different from the list of jobs. Also the Dashboard shows and old Autosys server that is no longer configured.

book

Article ID: 270035

calendar_today

Updated On:

Products

Autosys Workload Automation

Issue/Introduction

We have two issues.
Issue 1 is when we look at views in the monitoring tab of WCC the count for at the node level for the view is different that the actual number of jobs listed when the node is expanded.


Issue 2 is on the Dashboard for the Servers widget we see an old autosys instance listed that is not configured under the configuration tab.

How can we correct these issues?

Environment

Autosys R12.x
WCC R12.x

Resolution

1) Export your views to a file and correct and import them again using the wcc_config command and import with the wcc_monitor command.
https://techdocs.broadcom.com/us/en/ca-enterprise-software/intelligent-automation/autosys-workload-automation/12-0-01/administrating/ca-wcc-administration/ca-eem-policy-migration/migrate-monitoring-views.html

Note 1:
for the views and filters with the old server definition, change the insert_ to delete_
Example:

insert_filter: testfilter1
    view: PamTest1
    filter: (job_name LIKE * AND status = FAILURE)
    alert_policy: all_alerts
    active: true

To
delete_filter: testfilter1
    view: PamTest1
    filter: (job_name LIKE * AND status = FAILURE)
    alert_policy: all_alerts
    active: true

Note 2:
For all other versions change the insert_ to modify_ as you can not insert an existing view or filer.
Example:
insert_filter: test-filter2
    view: PamTest1
    filter: (job_name LIKE * AND status = FAILURE)
    alert_policy: all_alerts
    active: true

To
modify_filter: test-filter2
    view: PamTest1
    filter: (job_name LIKE * AND status = FAILURE)
    alert_policy: all_alerts
    active: true


2) Shut down your WCC instances in DEV and then bring up the primary server, make sure you can log in, and then bring up the other ones.