Database Monitors

The Database Monitor object allows you to monitor a database and execute different processes in Clarify whenever activity (inserts, deletions, or updates to fields and rows) takes place on an Oracle, Microsoft SQL Server, and IBM DB2 i DBMS database.

After initial database configuration, Database Monitors can be deployed and started, which automatically applies a trigger on the specified database table location. When the insertion, deletion, or update occurs, the Database Monitor then executes an Event and associated Business Process task(s). See Configuring Your Database Before Using Database Monitors.

Business Use

Use the Database Monitor to have Clarify respond immediately when database records are inserted, deleted or specific columns are updated in database tables. Responses can include specific transformations or other processes based on specific data and criteria. For example:

  • Automatically synchronize changes from one database to all other related/supporting databases in your business environment.
  • Whenever a new Customer is added to your database, have a Database Monitor identify and pass the new record information into Clarify to automatically begin a transformation process.
  • Automatically process orders when flagged sections of the database change.

As one of several source interface objects used to bring information into Clarify, its ultimate purpose is to launch an Event and begin a process based on the newly-received information. Database Monitors provide an effective way to automate responses to your business events when manifested as database actions.

How the Object Works

Database Monitors are created and defined in the Studio. When the Monitor is deployed and activated, a trigger will be created and added to a database table. The statement or row-level trigger on the database senses activity (insert,delete, or update) and invokes a message, which is placed on a queuing table, and then delivered to Clarify. Taking the parameters from the message payload, Clarify then launches an Event to start a process.

Creating and defining the Database Monitor in the Studio incorporates the following:

Data Source and Event Selection

Database Monitor objects require both a Data Source and Event to be present in your Project.

  • The Data Source is an object that defines the information Clarify needs to connect to a single database. It also specifies which tables, views, and columns Clarify can interact with.
  • Events often serve as the middle-man to channel data into Clarify. Events use Event parameters to capture and hold information about the source data, and then transfer that information to Business Process parameters.

Monitored Table, Columns and Return Criteria

Configure Database Monitors to react only when specific columns change, and specify which data will be returned. A snapshot of the selected data can be provided to Clarify as part of the notification, and "before and after" versions of your data can be included when applicable.

Returning only the data for a specific column(s) is a good way to manage large amounts of data being passed through a Database Monitor. Including data that you’re just going to ignore is unnecessary and can add processing time as well as resources to both the database and to Clarify.

Notification by Statement or Row

Determine the level at which the database trigger sends a notification (message payload) for the update, insert, or delete. Drop-down options include Row or Statement levels.

Selective Queries

Use custom queries to monitor for specific database criteria using logical expressions and operators.

Process Summary

To use this object, you must:

  • Complete initial database configuration. See Configuring Your Database Before Using Database Monitors
  • Create the object.
  • Define the object by specifying the data source, table and columns to monitor, and associating the Business Process that performs the desired integration activity.