iFIX ODBC Alarm Service Configuration Dialog Box
The iFIX ODBC Alarm Service Configuration dialog box displays the following items:
SQL Login Information
Field |
Description |
Use Login Information from SQL Configuration Check Box |
Allows you to use the existing SQL setup to specify the database type, user name, password, and database identifier. This feature can be used only if you have installed and configured the iFIX SQL option. |
Database Type Field |
Allows you to specify a database type for the relational database. You can also click the Browse button to display a list of available database types. If you are using a Microsoft Access database, the database and the Alarm ODBC service must be on the same machine. |
Database Type Browse Button |
Allows you to display a list of available database types. |
User Name Field |
Allows you to enter the user name required to connect to the relational database. |
Password Field |
Allows you to enter the password required to connect to the relational database. |
Database Identifier Field |
Allows you to specify a database identifier for the relational database. You can also click the Browse button to display a list of available database identifiers. |
Database Identifier Field Browse Button |
Allows you to display a list of available database identifiers. |
Options
Field |
Description |
Allow Operator to Pause Alarm Logging Check Box |
Allows you to temporarily stop alarms from being written to the relational database. |
Update Interval Text Box |
Allows you to control how often data is written to the relational database. Valid entries are 1 to 300 seconds. The default is 1 second. |
Alarm Queue Size Field |
Allows you to specify the maximum number of records in the iFIX Alarm Queue. By increasing the queue size, you can prevent alarm loss. Valid entries are from 1 to 32767. The default value is 100. |
Number of Records to Log from iFIX Field |
The number of records to read from the user queue before writing to the relational database. Increasing this number will result in a more efficient ODBC, but will also increase the risk of losing alarms. The maximum number you can enter is 100. |
Number of Records to Log from Backup File Field |
The number of records to read from the Lost Connection file before writing to the relational database. |
Lost Connections Options
Field |
Description |
File Field |
Allows you to specify a temporary (TMP) file for the Alarm ODBC Service. If the service cannot access the relational database, alarms and messages are saved in this file. When the relational database re-establishes contact with the Alarm ODBC Service, iFIX automatically reads the data in the TMP file to update the relational database. Leave this field blank to disable this feature. |
File Field Browse Button |
Allows you to select a file. |
Tag Field |
Allows you to specify a tag that indicates a broken connection with the relational database. Alternatively, instead of entering a tag here, you can create an Alarm ODBC watch dog using the Scheduler. For more information, refer to the Creating an Alarm ODBC Watchdog Using the Scheduler section. |
Tag Field Browse Button |
Allows you to enter the node name and tag name. |
User Fields
Field |
Description |
Field Name1 |
Allows you to enter any ASCII format (A_) database block field. For a complete list of available database block fields, refer to the Database Manager Help system. |
Field Name2 |
Allows you to enter any ASCII format (A_) database block field. For a complete list of available database block fields, refer to the Database Manager Help system. |
Field Name3 |
Allows you to enter any ASCII format (A_) database block field. For a complete list of available database block fields, refer to the Database Manager Help system. |
Field Name4 |
Allows you to enter any ASCII format (A_) database block field. For a complete list of available database block fields, refer to the Database Manager Help system. |
Database Configuration
Field |
Description |
Create Table at Runtime if Not Found Check Box |
Allows you to have the Alarm ODBC Service create the table at run-time if it does not exist. |
Table Name Field |
Allows you to specify a table name. When you enter your own table name, you must select the alarm and message fields you want to archive using the Column Configuration spreadsheet. If you are creating a table, you must enter a unique name. You cannot overwrite an existing table. NOTE: When writing to an Oracle database, be aware that the table name cannot include an embedded period (.) in the name. For instance, an entry such as SchemaName.TableName.Alarms would not be acceptable in this field, since it includes a period between SchemaName and TableName. |
Create Table Now Button |
Allows you to create a table when you configure the Alarm ODBC Service. |
Column Configuration
Field |
Description |
Select All Button |
Allows you to select all the iFIX Field Names and populate the SQL Column Names automatically. When Clear All is active, allows you to disable any selected iFIX Field Names. |
Restore Defaults Button |
Allows you to use the default table name, FIXALARMS, to simplify the table setup. When you use the default table name, the Alarm ODBC Service completes the Column Configuration spreadsheet. |
Column Configuration List Box |
Allows you to specify the alarm and message fields you want to archive. |