Delay in WCC in terms of reflecting EEM policy change
search cancel

Delay in WCC in terms of reflecting EEM policy change

book

Article ID: 208166

calendar_today

Updated On:

Products

Autosys Workload Automation

Issue/Introduction

In EEM MonitorViewControl policy, when making a change to the policy, it is delayed significantly to be reflected on WCC side.

The views on WCC side will not show up unless a new view is created. 

Environment

Release : 12.0

Component : WORKLOAD CONTROL CENTER

Resolution


You can adjust that it takes for WCC to check with EEM to see if there are new policies to consume.
See: WCC -> Configuration -> Preferences -> Monitoring -> Security Cache Timeout

NOTE 
WCC does not perform full cache syncs in every request.
By default, it updates the cached group attributes, policies, and calendars, but does not update the sessions.
The impact on the behavior of WCC is that user attributes will not be updated until the user logs off and on again.
This means changes to policies reflect immediately but user attributes changes requires logout and login.
 
There is a way, if required, to force a full update so the user attribute changes for the existing sessions will be reflected immediately.
You can add the following properties to 
 wcc/data/config/application/config/resources/connection.properties
 
eem.fullCacheUpdate=true
eem.cacheUpdateInterval=30
 
Restart WCC after making this change.
With that in place a full cache sync, including user attributes will be done every 30 seconds.