Question
Auto-owners Insurance
US
Last activity: 31 Mar 2017 10:59 EDT
PEGA-Rules Inconsistancies
We have two AES environments: Prod AES monitors and Test AES . We recently updated the location where temp data (such as the extract marker) is stored for Prod AES. Afterwards, we began noticing that the SystemCleaner agent entry was failing in Prod AES. We resolved this by having SystemCleaner run at 3:00am instead of 12:00am. (I believe we were having the same issue as described here: https://collaborate.pega.com/question/systemcleaner-creating-exception.) While looking at SystemCleaner, I noticed that PEGA-Rules had inconsistencies between the agent, the Prod AES agent-schedule, and the Test AES agent-schedule. I am hoping that somone could provide insight on how the Prod AES and Test AES agent-schedules should be setup.
Agent
• SystemCleaner: Enabled, Run at 12:00am every weekday
• SystemPulse: Enabled, Run every 60 seconds
• SystemIndexer: Enabled, Run every 60 seconds
• RuleUsageSnapshot: Enabled, Run at 1:00am every weekday
• StaticContentCleaner: Disabled, Run every 3600 seconds
• SystemWorkIndexer: Disabled, Run every 60 seconds
Test AES Agent Schedule
• SystemCleaner: Enabled, Run every 86400 seconds (ran at 3:11am last)
• SystemPulse: Enabled, Run every 60 seconds
• SystemIndexer: Enabled, Run every 60 seconds
• RuleUsageSnapshot: Enabled, Run every 86400 seconds (ran at 3:10am last)
• StaticContentCleaner: Disabled, Run every 3600 seconds
• SystemWorkIndexer: Disabled, Run every 60 seconds
Prod AES Agent Schedule
We have two AES environments: Prod AES monitors and Test AES . We recently updated the location where temp data (such as the extract marker) is stored for Prod AES. Afterwards, we began noticing that the SystemCleaner agent entry was failing in Prod AES. We resolved this by having SystemCleaner run at 3:00am instead of 12:00am. (I believe we were having the same issue as described here: https://collaborate.pega.com/question/systemcleaner-creating-exception.) While looking at SystemCleaner, I noticed that PEGA-Rules had inconsistencies between the agent, the Prod AES agent-schedule, and the Test AES agent-schedule. I am hoping that somone could provide insight on how the Prod AES and Test AES agent-schedules should be setup.
Agent
• SystemCleaner: Enabled, Run at 12:00am every weekday
• SystemPulse: Enabled, Run every 60 seconds
• SystemIndexer: Enabled, Run every 60 seconds
• RuleUsageSnapshot: Enabled, Run at 1:00am every weekday
• StaticContentCleaner: Disabled, Run every 3600 seconds
• SystemWorkIndexer: Disabled, Run every 60 seconds
Test AES Agent Schedule
• SystemCleaner: Enabled, Run every 86400 seconds (ran at 3:11am last)
• SystemPulse: Enabled, Run every 60 seconds
• SystemIndexer: Enabled, Run every 60 seconds
• RuleUsageSnapshot: Enabled, Run every 86400 seconds (ran at 3:10am last)
• StaticContentCleaner: Disabled, Run every 3600 seconds
• SystemWorkIndexer: Disabled, Run every 60 seconds
Prod AES Agent Schedule
• SystemCleaner: Enabled, Run at 3:00am every weekday
• SystemPulse: Enabled, Run every 60 seconds
• SystemIndexer: Enabled, Run every 60 seconds
• RuleUsageSnapshot: Enabled, Run at 1:00am every weekday
• StaticContentCleaner: Disabled, Run every 3600 seconds
• SystemWorkIndexer: Enabled, Run every 60 seconds
***Moderator Edit: Vidyaranjan | Updated Categories***
Accepted Solution
Pegasystems Inc.
US
Pegasystems
US
86400 seconds is one day so in that regard your test and prod schedules are indicating the same frequency of once a day, the only difference being that for the system cleaner and rule usage snapshot, the prod schedule indicates exactly WHEN during each day they should run. /Eric
Accepted Solution
Pegasystems Inc.
US
Hello,
It's hard to say exactly how it "should" be set up, since it's so dependent on your specific needs. I expect that someone at your site set the test agent schedule and as Eric pointed out, that's once a day. I think you will probably see drift over time with that setup, since I believe the 86400 second clock starts counting once the agent finishes running. So assuming that takes 60 seconds to complete, it would start 86460 seconds after the last time it started. Because of that, I would generally suggest a schedule more in line with your prod system. That way you can predictably run things during an optimal time for your environment.
Thanks,
Mike
Auto-owners Insurance
US
Thanks for the suggestions! Is there any suggestions on whether SystemWorkIndexer should be enabled or disabled in AES?
Auto-owners Insurance
US
It looks like SystemWorkIndexer is used in work object indexing. If we still have questions on this, I can open a separate question.
Hello,
It's hard to say exactly how it "should" be set up, since it's so dependent on your specific needs. I expect that someone at your site set the test agent schedule and as Eric pointed out, that's once a day. I think you will probably see drift over time with that setup, since I believe the 86400 second clock starts counting once the agent finishes running. So assuming that takes 60 seconds to complete, it would start 86460 seconds after the last time it started. Because of that, I would generally suggest a schedule more in line with your prod system. That way you can predictably run things during an optimal time for your environment.
Thanks,
Mike