Application Options

To configure the HotDBWAN application options, click on "Options" in the "File" menu.

General

As default, HotDBWAN's monitor pop-up alerts are enabled and every HotDBWAN monitor alert activates a pop-up alert window that appears at the bottom right corner of the screen.

In order to disable these pop-up alert windows, it is required to have other forms of alerts enabled. Configure the monitor to alert by Email or LAN. To disable HotDBWAN monitor pop-up alerts, uncheck the "Show monitor pop-up alerts" checkbox.

Pick the physical location for the client log files by clicking on the "..." button next to the "Client Log Path" textbox. Pick the physical location for the execution report files by clicking on the "..." button next to the "Execution Report Path" textbox.

Triggers

Triggers in HotDBWAN is an option to attach a failover or a failback execution with an external operation such as batch files, executables or any other windows supported extensions. The main purpose of triggers is using a batch file to synchronize any application connected to the database after failover or failback. For example, changing the application connection string from the source server to the primary target server after executing failover.

To add a new trigger, click on the "Add" button.

The trigger type is the HotDBWAN operation to attach an external command to. You can choose between a package trigger (Failover, Failback) and a server trigger (Server Failover, Server Failback). Choose a trigger type from the "Trigger Type" drop-down combo box.

The trigger entity is the package or the server that is combined with the trigger type (operation) to define the trigger. For example, a failover trigger for the package "Hot Northwind" will be executed only after a failover operation on this package. Choose a trigger entity from the "Trigger Entity" drop-down combo box.

The execution path is the full path to the external operation file. Type the execution path or pick it by clicking on the "..." button next to the "Execution Path" textbox. If a command line is required for the execution file, type it in the "Command Line" textbox.

After defining a new trigger, its execution file must be tested in order to continue. The success of this test is determined by the user. Press on the "Test" button and make sure that the execution file was executed successfully. Press on the "OK" button to continue.