Help files

Database Monitor Trigger

The Database Monitor Trigger monitors a certain database and fires a Process when any of the selected operations is performed on it.

Database_Monitor_Trigger_Image.png

The Database Monitor Trigger, when fired, assigns values to three Trigger Variables that are made available to the Process:

%DatabaseTriggerDatabaseName%, which contains the name of the database,

%DatabaseTriggerTableName%, which contains the name of the modified table, and

%DatabaseTriggerEventType%, which contains the operation that triggered the Process.

As you can have as many Triggers as you want attached to the same Process, this would allow you to know which Database Monitor Trigger fired the Process, and why.

Custom Description

Add a custom description to the trigger which will be shown in the Triggers tab under "Description".

Database Type

Choose between SQL Server and Oracle databases; in the latter case, the Port and Notification Port will also have to be entered.

Username

Enter the name of a User with access to the database.

Password

Enter the User's password.

Database Name

Specify the name of the database to be monitored.

Table

Enter the name of the specific table to be monitored.

Test Connection

Use the Test Connection button to ensure that WinAutomation is able to access the database using the entered information.

Operations

Select the types of operations which should be monitored.

On trigger failure retry every

Optionally set a time period after which the Trigger will attempt to resume monitoring after encountering an error.

Requirements

The Database Monitor Trigger requires the installation of a second party dll file from Oracle. The file can be downloaded here.

Download the latest ODP.NET version and extract the downloaded zip file.

Next, copy the Oracle.ManagedDataAccess dll file (odp.net\managed\common) in the WinAutomation installation folder (C:\Program Files\WinAutomation).