Decisioning category — Batch Data page
|
Category |
Page |
Decisioning |
Batch Data |
The Batch Data page provides the facilities to define and manage the batch execution of the strategies that are accessed by your application. Depending on the type of action you want to perform, use the corresponding tab. Batch data functionality assumes the availability of customer data, data classes, and report definition rules. Additionally, for large scale batch decisioning purposes, you can access the Topology landing page through this page.
This page has four tabs:
This landing page is available to users who have access to the Decision Strategy Manager application. For additional information, see the PDN article About the Decision Strategy Manager.
The Batch Runs tab allows you to manage the offline strategy execution configurations (also referred to as batch runs) defined in your application. The display lists the following information about the offline strategy execution configurations available in your application.
Column |
Description |
Name |
The name of the configuration. |
Strategy |
The name of the strategy rule executed by the batch run. |
Input |
The name of the configuration that defines the input data for the batch run. |
Output |
The name of the configuration that defines where and how to store the results of the batch run. |
Records Processed |
The number of records processed during offline strategy execution. |
Finished |
The time since offline strategy execution was last executed and completed. |
Status |
The status of offline strategy execution. |
Updated By |
The user that last created, updated, or executed the configuration. |
ID |
The identifier of the batch run. |
Deletes the row. |
Two processing buttons display:
New opens the Strategy Execution Configuration form in a separate window that allows you to define a batch run.
Field |
Description |
Name |
Select the name of the configuration. A default name identical to the ID is assigned to a new batch configuration, but you can change it by entering a new name. |
Input |
Select the configuration that defines the input data for the batch run. Click the link to display the input configuration. |
Strategy |
Select the strategy rule that executes the batch run. Click the link to display the strategy rule. |
Component |
Select the decision component in the strategy. Only public components display. |
Output |
Select the configuration that defines how to store the output of the batch run. Click the link to display the output configuration. |
Click Submit to save and add the batch run to the batch run list. Click Submit and Execute to trigger the execution of the batch run and monitor its progress.
Click Stop to stop the batch run. Click Delete to delete the batch run. Click Re-Execute to execute the batch run again.
The Inputs tab allows you to manage the input configurations that define the input data used in the batch run. It lists the following information about the input configurations available in your application.
Column |
Description |
Name |
The name that identifies the configuration. |
Strategy Applies To |
The data class on which the strategy is defined. |
Report Definition |
The name of the report definition that provides the data for strategy execution. |
Case ID |
The Case ID associated with the configuration. |
Deletes the row. |
Two processing buttons display:
New opens the Create/Edit Input Configuration form in a separate window to define the input configuration.
Field |
Description |
Name |
The name of the input configuration. |
Strategy Applies To |
Select the data class on which the strategy is defined. |
Report Definition |
Select the name of the report definition that provides the input data for strategy execution. A specific filter pattern is required in the report definition so that batch execution can be distributed across PRPC nodes. This pattern consists of a filter condition that maps the appropriate column to the param.PartitionKey value. Distributed batch execution depends on this filter pattern, as well as how system nodes are configured for that purpose in the Topology tab. |
Case ID |
Displays the primary key in the database table providing the input data. |
Click Save to save the configuration and update the input list. Click Cancel to close the window without saving the input.
The Outputs tab allows you to manage the configurations that define how and where to store the results of the batch run. The display lists the following information about every input data configuration.
Column |
Description |
Name |
The unique name of this configuration. |
Type |
The type of output configuration. |
Strategy Result Class |
The name of the strategy result class configured in the output configuration. |
Database |
The name of the database where the output of the offline strategy execution should be stored. |
Database Table |
The name of the database table where the results should be stored. |
Deletes the row. |
Two processing buttons display:
The Topology tab allows you to define the participation and load of PRPC systems nodes in batch executions. The displays lists the following information about system nodes.
Column |
Description |
Host Name |
The name of the system node. |
Description |
The description of the node.Changing the description of the node may be necessary when multiple system nodes run on the same server. |
Agent Status |
The status — Disabled or Enabled — of the ProcessBatchJob agent. |
Enable Batch |
Check the box to add a given system node to the pool of nodes used to distribute batch execution. |
Threads |
Select the number of threads that can run in a given node. |
Updated Time |
The last time the configuration for a given node was saved. |
Updated By |
The name of the user who last updated the configuration for a given node. |
Node ID |
The PRPC node ID. |
ID |
The identifier of the batch run. |
Click Save to save the updates.
One processing button displays:
landing page | |
About predictive analytics and Decision Strategy Manager
|