ALERT

EBI Script installation guide

1 Prerequisites
To connect to the EBI database, ALERT needs Honeywell components to be installed on the machine.
Those required modules are the ODBC drivers: ODBC Client XXX.msi where XXX is the EBI version.
Once installed, those drivers create a data source called EBIDatasource. This source will be used in
the ODBC data connection string configuration.
An EBI user must be used for the data connection. He can be added in the EBI configuration. We
generally use the following user:
Name: ODBC
Password: ODBCODBC
This user will be used in the ODBC data connection string configuration.

2 Script importation
Launch Alert, log on as System operator (By default: ALERT).
Go to Configuration->Options. Select the Supervision tab and check Message processor
activation.

Confirm with OK.

Go to Configuration-> Message processor. In the prototype field, click on this arrow
then on Import

09/30/2011

EBI Script installation guide version 1.2

and

2/8

09/30/2011

EBI Script installation guide version 1.2

3/8

Select the Honeywell-EBI.pro script and click on Open.

The Message Processor Setup window displays the following information:

Now that the import of the script is finished, we'll go to the configuration

09/30/2011

EBI Script installation guide version 1.2

4/8

3 Script configuration
The Script contains 8 global variables. These allow the general configuration of the script.
DBConnectionString: It represents the connection string to the database. The following string
is an example withe the previously used parameters:
DSN=EBIDataSource;DRIVER=;DBQ=.;UID=ODBC;PWD=ODBCODBC;DOMAIN=;RemoteHost=;R
edundantCPU=N;RedundantLAN=N .
To check the connection string, you can create a .udl file. The connection type is an ODBC
connector. Then, you need to select the EBIDataSource and entre the server and EBI user
parameters. Once checked, the connection string can be copied to the message processor.

TraceLevel: It allows you to set the trace level you want to display in the journal log of Alert. By
default the value 0 displays only the errors.
PollingTimer: It defines the time interval between 2 SQL connections and retrieval of data.
TreatmentType: It sets the operating mode of the alarm processing by the script.
This variable can take the following values:
- 1: Static operation. Alarms you want to be processed are directly defined in Alert.
- 2: Dynamic operation. Alarms are created dynamically based on filters created in the
message processor. For example, we can handle dynamically all the alarms with a
priority focus L 00 .
- 3: Dual operation, static and dynamic. In this mode, you must know that static alarms
will be given priority. If an alarm comes in and it has been defined as "hard" in the
software, it will be triggered without taking into account the filters.
StatUpdateMsg and DynUpdateMsg: It allows you to specify if in the static and/or dynamic
mode you want the alarm message to be updated with the description of the new alarm.
EBIToAlertAck: It allows you to specify whether you want to recover the acknowledgement
made on the EBI and acknowledge the corresponding alarm in Alert.
09/30/2011

EBI Script installation guide version 1.2

5/8

gsHoneywellEBIIniFile: This variable contains the path and name of the file Honeywell-EBI.ini.
This file is used to store the link between a condition name for reset and the condition name for
the corresponding alarm.
After setting up the script, click the button Init.

4 Configuration of the variables in Alert

4.1 Static Variables

Once the script is configured, we need to create, in Alert, the variables of the database you want
to monitor. To do this, right click on Tags in the left tree of Alert. Click Add a tag...

The box External Tag appears, select Other.

In the field Item, enter the name of the variable as Source_ConditionName.

One can find this information in the view Event2 of the database in the fields source and
ConditionName.
Remarks: In some case, the Condition Name is different for a status of alarm and for a status of
reset. In this case, you have to define in the HoneywellEBI.ini file the alarm Condition Name
according to the reset Condition Name.
Sample for a HoneywellEBI.ini file
[NORMAL STATE]
AlarmConditionName= "ALARM"
Confirm with OK. The configuration window of the variable opens.

09/30/2011

EBI Script installation guide version 1.2

6/8

Set the trigger condition on NONE, and then configure the schedule corresponding to that
variable (cf Alert documentation).

4.2 Dynamic Variables

If the operating mode chosen in the script is the dynamic mode, you must create filters in order
for the alarms to be created based on the criteria you set. To create filters, go to Configuration->
Message Processor. Click on Filters .

09/30/2011

EBI Script installation guide version 1.2

7/8

A new window appears listing all existing filter. Click Add to create a new one.

The dialog box for configuring a filter appears:

Define the name of the filter
Define the condition of
creation of the alarm. In
our example, an alarm is
created when the
Variable ConditionName
is equal to PVLO.

Define the identifier

that will be assigned to
the alarm when
established for the first
time. It may be wise to
add a field that will
distinguish dynamic
alarms from static
alarms. In our example,
we add "Dyn_" at the
beginning of the
identifier.
Define the treatment to
process for the triggering,
return to normal, etc...
Every action can be
associated with a
condition.

09/30/2011

EBI Script installation guide version 1.2

8/8