Question
Verizon Wireless
US
Last activity: 6 Jun 2017 9:42 EDT
DSM agents schedule interval (PEGA 7.2.2)
Hi Team,
Could you please suggest regarding the DSM agents schedule interval and the number of node instances (single or multiple nodes) on which agents should be enabled.
Please find the attachment for the list of Pega-DecisionEngine agents.
Regards,
Pradeep Pydi,
<Removed personal information>
Pegasystems Inc.
IN
Hi Pradeep,
Here are the details on DSM agents:
UpdateAdaptiveModels
This agent governs, how often the client nodes go to the adaptive server to get the most up to date model (i.e., that contains statistical information about all interactions with the customer on any nodes). The default setting is 30 seconds, but if this leads to too much network traffic it can certainly be set to a higher value. It should be enabled on on all nodes, without it, the nodes will not get updated models (and in essence predictions will be default).
ADMSnapshot
Adaptive Decision Manager can capture historical data for reporting purposes. The ADM Data Mart is implemented by periodically triggering the ADMSnapshot agent (Pega-DecisionEngine ruleset, PRPC:Administrators access group).
By default, the agent is scheduled to run every 120 seconds. The Data Mart settings in the Adaptive Decision Manager section of the Services landing page allow you to define how often the activity runs to capture the state of models and predictor binning.
ProcessBatchJob
Large scale simulations are enabled by performing strategy execution in batch across system nodes. The assignment, queuing and management of large scale simulations is governed by the ProcessBatchJob agent configuration. The agent is scheduled to run with a given regularity (in seconds) to trigger checking assignments in the DSMBatchJobs@pega.com workbasket.
Hi Pradeep,
Here are the details on DSM agents:
UpdateAdaptiveModels
This agent governs, how often the client nodes go to the adaptive server to get the most up to date model (i.e., that contains statistical information about all interactions with the customer on any nodes). The default setting is 30 seconds, but if this leads to too much network traffic it can certainly be set to a higher value. It should be enabled on on all nodes, without it, the nodes will not get updated models (and in essence predictions will be default).
ADMSnapshot
Adaptive Decision Manager can capture historical data for reporting purposes. The ADM Data Mart is implemented by periodically triggering the ADMSnapshot agent (Pega-DecisionEngine ruleset, PRPC:Administrators access group).
By default, the agent is scheduled to run every 120 seconds. The Data Mart settings in the Adaptive Decision Manager section of the Services landing page allow you to define how often the activity runs to capture the state of models and predictor binning.
ProcessBatchJob
Large scale simulations are enabled by performing strategy execution in batch across system nodes. The assignment, queuing and management of large scale simulations is governed by the ProcessBatchJob agent configuration. The agent is scheduled to run with a given regularity (in seconds) to trigger checking assignments in the DSMBatchJobs@pega.com workbasket.
If there are assignments, they will be queued to create threads based on the thread configuration for each node. The status of the work item is updated as it progresses in this process and you can monitor the assignment by viewing the instances in the workbasket. How many threads can be run in a given node is something that you define in the Topology landing page. You need to have the ProcessBatchJob agent configured in your ruleset to make use of this functionality.
Please note that each agent interval needs to be defined / changed as per the business requirement. For more details please refer to DSM Operations guide: https://pdn.pega.com/documents/dsm-operations-guide-722
Hope this helps!