Upgraded UIM to 20.3.3, and set up a report within Report Scheduler. Seems to be working, but getting a Success and a Failed on each execution.
.
Release : 20.3
Component : UIM - UMP_REPORTSCHEDULER
- UIM limitation supports only one Operator Console in a clustered environment.
- For a multi-node OC environment, the Report Scheduler functionality in UIM 20.3.3 no longer supports the job_refresh_secs configuration property in the /webapps/reportscheduler section of the wasp.cfg.
- Now, it supports the execute_email_action( will be execute_email_actions) configuration property in the /webapps/reportscheduler section of wasp.cfg. The execute_email_action property lets you prevent the duplicate reports by stopping the execution of the email actions on one or more OC servers.
- On each OC server that you want to stop executing email actions, add the execute_email_actions property with a value of false. Therefore, with this property, you can resolve the issue of users receiving duplicate reports in a multi-node OC environment.
*************
Currently techdocs suggest to update the configuration key "execute_email_action" under webapps/reportscheduler section.
The actual key used in the implementation is "execute_email_actions". Please note a trailing s at the end of the key. Please update key name and verify this scenario once.
wasp config after update:
<reportscheduler>
smtp_host = x.x.x.x
transport_protocol = smtp
reloadable = true
smtp_port = 25
smtp_auth = false
cross_context = true
smtp_user =
unpack_war = true
smtp_starttls = false
load_on_startup = true
email_from_address = [email protected]
path = /reportscheduler
execute_email_actions = true
</reportscheduler>