Data Veracity Collection Agent Configuration(4.3)
The Data Veracity Collection agent's configuration dialog contains the following tabs:
Data Veracity - This tab contains the configuration needed to collect UDRs or batch files from Data Veracity.
Setting | Description |
---|---|
Profile | Click Browse to select a predefined Data Veracity Profile.  This profile contains the Data Veracity UDR type and table information that the Collection agent requires to collect the erroneous UDR or Batch files. For further information, see Data Veracity (4.3). |
Type | UDR and Batch radio button here will be enabled according to the selected Data Veracity Profile. Select either UDR or Batch to determine if the agent will be collecting UDRs or Batch files from the Data Veracity tables. The Collection agent can only collect either UDR or Batch at any one time.  |
Filtering | Type: UDRData Veracity Collection Agent configuration - UDR Type This table is where we can specify what UDR to collect, and the rules to collect the selected UDR Type. Click on the Add button to add the rule. The UDR Type dropdown list will display the UDR Type from the selected Data Veracity Profile. The Error Code dropdown list will display all the Error Codes available in MZ, see Error Codes(4.2). The Saved Filters dropdown list will display all the Saved Filters for the selected Data Veracity Profile, see Filters(4.2). Select a UDR Type to collect, and select to collect either with an Error Code or with a Saved Filter. Duplicate UDR Type is not allowed in Filtering table. Type: BatchÂFor Batch collection, Data Veracity collection agent will collect the batch records from the Data Veracity table specified in Data Veracity Profile and collect according to the added rules here.  Click on the Add button to add the rule. The Error Code dropdown list will display all the Error Codes available in MZ, see Error Codes(4.2). The Saved Filters dropdown list will display all the Saved Filters for the selected Data Veracity Profile, see Filters(4.2). Multiple Error Codes and Saved Filters are allowed here as long as it is not a duplicate entry. |
Collection Size | Collection Size is the value that defines how many UDRs will be collected before the collection agent finishes the current batch and starts a new one. The default value is 5000. The range for the value is 1 - 100000. This field is only available for collecting UDR. |
SQL Bulk Size | To improve performance, data records are retrieved in bulk. The SQL Bulk Size value specifies how many records that will be included in each bulk. The default value is 1000. The range for the value is 1 - 100000. |
State | This combo box displays a list of states that indicates which UDRs with the corresponding state to collect from the database. The choices presented in the list are NEW, UPDATED and NEW or UPDATED. The default value is NEW or UPDATED. This field is only available for collecting UDR. |
Read Only | This check box will have the agent retrieve the Data Veracity UDRs or Batch records without updating the state of the records from the database. Such as, UDRs that were collected with the state NEW will not have its state changed to REPROCESSED when Read Only is enabled. |
The Data Veracity Collection agent's configuration dialog contains the following tabs:
Data Veracity - This tab contains the configuration needed to collect UDRs or batch files from Data Veracity.
Setting | Description |
---|---|
Profile | Click Browse to select a predefined Data Veracity Profile.  This profile contains the Data Veracity UDR type and table information that the Collection agent requires to collect the erroneous UDR or Batch files. For further information, see Data Veracity (4.3). |
Type | UDR and Batch radio button here will be enabled according to the selected Data Veracity Profile. Select either UDR or Batch to determine if the agent will be collecting UDRs or Batch files from the Data Veracity tables. The Collection agent can only collect either UDR or Batch at any one time.  |
Filtering | Type: UDRThis table is where we can specify what UDR to collect, and the rules to collect the selected UDR Type. Click on the Add button to add the rule. The UDR Type dropdown list will display the UDR Type from the selected Data Veracity Profile. The Error Code dropdown list will display all the Error Codes available in MZ, see Error Codes(4.2). The Saved Filters dropdown list will display all the Saved Filters for the selected Data Veracity Profile, see Filters(4.2). Select a UDR Type to collect, and select to collect either with an Error Code or with a Saved Filter. Duplicate UDR Type is not allowed in Filtering table. Type: BatchÂFor Batch collection, Data Veracity collection agent will collect the batch records from the Data Veracity table specified in Data Veracity Profile and collect according to the added rules here.  Click on the Add button to add the rule. The Error Code dropdown list will display all the Error Codes available in MZ, Error Codes(4.2). The Saved Filters dropdown list will display all the Saved Filters for the selected Data Veracity Profile, Filters(4.2). Multiple Error Codes and Saved Filters are allowed here as long as it is not a duplicate entry. |
Collection Size | Collection Size is the value that defines how many UDRs will be collected before the collection agent finishes the current batch and starts a new one. The default value is 5000. The range for the value is 1 - 100000. This field is only available for collecting UDR. |
SQL Bulk Size | To improve performance, data records are retrieved in bulk. The SQL Bulk Size value specifies how many records that will be included in each bulk. The default value is 1000. The range for the value is 1 - 100000. |
State | This combo box displays a list of states that indicates which UDRs with the corresponding state to collect from the database. The choices presented in the list are NEW, UPDATED and NEW or UPDATED. The default value is NEW or UPDATED. This field is only available for collecting UDR. |
Read Only | This check box will have the agent retrieve the Data Veracity UDRs or Batch records without updating the state of the records from the database. Such as, UDRs that were collected with the state NEW will not have its state changed to REPROCESSED when Read Only is enabled. |