MonitorViewControl policy are not reflected within WCC

Document ID : KB000048256
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

When creating a new MonitorViewControl policy or modifying an existing MonitorViewControl policy it is not being reflected immediately within WCC.

Solution:

When creating a new MonitorViewControl policy or modifying an existing MonitorViewControl policy it is not being reflected immediately within WCC.

This is due to a parameter within WCC namely 'Security Cache Timeout' which has by default a value of 60 minutes. Any changes to MonitorViewControl policies are being refreshed by WCC every 60 minutes. This is done for performance reasons.

The parameter can be found under 'Configuration' tab, select under Preferences 'Monitoring'. Under section 'Backend Services' you have the field 'Security Cache Timeout'.

Security Cache Timeout:

Specifies the time (in minutes) after which the security cache is invalidated

Default: 60

Limits: 0,1-2147483647

Note: When any CA EEM policy that affects Monitoring is changed, by default, it takes 60 minutes to be reflected in CA WCC.
The default timeout value reduces the overhead of checking CA EEM for every request. However, you can set the timeout to a lower value to reflect CA EEM security changes in Monitoring more quickly.
Setting the value to 0 allows security changes to be reflected immediately.

When you need to test 'MonitorViewControl' policies, we recommend to set the value to 0 so that the changes are reflected immediately.
Once testing is done, set the timeout value back to default 60.