The Data Veracity Profile is used to select the particular database that Data Veracity will be connected to. The profile can also generate the SQL scripts to be used for creating the database tables where the erroneous UDRs will be stored in.
The Data Veracity profile is loaded when you start a workflow that depends on it. Changes to the profile become effective when you restart the workflow.
Configuration
To create a new Data Veracity profile, click the New Configuration button in the upper left part of the Desktop window, and then select Data Veracity Profile from the menu.
Data Veracity profile
The following settings are available in the Data Veracity profile:
| Setting | Description |
|---|---|
Database Profile | This is the database the agent will connect and send data to. Click the Browse... button to get a list of all the database profiles that are available. For further information see Database Profile. Data Veracity is supported for use with the following databases:
|
UDR Type Mapping | UDRs to be used by the Data Veracity Profile are listed here |
| Use MIM | Select this check box to allow the use MIMs listed under the Named MIMs table. |
| Named MIMs | This list will display the user defined MIMs that can be made available for use by the Data Veracity Forwarding Agent. |
| UDR Type Tables SQL Script | This text box will generate the SQL statements for the selected UDRs' table schema and indexes for the TXN_ID, ERROR_CODE, INSERT_TIME and STATE field. The schema will be generated based on the number of UDRs in the UDR Type Mapping table. Click the SQL button to generate the SQL statements. Warning! Users will have to copy the SQL script generated in the text box to create the Data Veracity tables on their own in the database listed in the Database profile. The Data Veracity profile will not automatically create the tables for you. PostgreSQL Schema Name There will not be a schema name included with the SQL command generated for PostgreSQL. Info! The user should create adequate indexes along with the indexes already provided by the script, in order to achieve the best performance for Data Veracity. Note! The name of the column constraints will be based from the Internal UDR name. An example would be, if an Internal UDR is named customerTI, the name of the column constraints will be prefixed with customerTI. When there are multiple Internal UDRs with identical names but present in different folders in your configuration, the names of the column constraints will be the same as well. This will cause a conflict error to occur when creating the table in your Database. It is highly recommended to have proper naming conventions for Internal UDRs, to prevent any conflicts. |