About Real Time Monitoring

Real time monitoring processes are designed to check data quality at the point of data entry, but not return a response to the calling application, so that there is no extra burden on the user modifying the data on the source system. As there is no need to return a response, there are fewer restrictions on what the EDQ process can do - for example, it may include profiling processors that work on all the records for the period of time that the monitoring process runs.

Real time monitoring processes have the following characteristics:

• They read data from a real time provider (such as the inbound interface of a Web Service).

• They may include any of the processors in the processor library, including those such as Duplicate Check that are not suitable for real time response processes.

  Note:

  If a real time monitoring process contains processors that are designed to process whole batches, and are therefore not suitable for real time response processes, it should be run in Normal mode, and not in Interval mode. The supported execution types of each processor are listed in the help page for the processor.

• They either write no results, or write their results to a staged data table and/or external database or file.

• The process completes when it is stopped or when a configured time or record threshold is reached.

• They may be executed either in Normal mode (for a limited period of time, or processing a limited number of records), or in Interval mode.

For more information, see Enterprise Data Quality Online Help.