What Types of Log Tables are Exported? |
 | ||
|
This documentation page describes a feature of version 3.3 of Iguana. In Iguana 4.0 and later, you only need to specify a database if you plan on sending messages to the database or receiving messages from it. Logging information is stored in external files, which are described in Changing the Log Directory. | ||
 |
Depending on the type of channel being set up, the following log tables may be exported to your database.
 | ||
* Denote log tables that must be exported to your database. ** Denote log tables that can be optionally exported to your database. | ||
 |
| Type of Log Table | Description |
|---|---|
| Channel Success Log* | Contains HL7 messages that were processed by that channel. It contains six columns:
The success log table is named channelname_cha_suc_log, where channelname is the name of the channel in Iguana. The information in this table corresponds to the data found in the Logs page in the Successes column in Iguana. Note that this log must be exported to your database. |
| Channel Destination or Source Error Logs* | Contains information about HL7 messages that were not processed by the destination or source component, as well as other channel error information such as connection errors. It contains six columns:
The destination error log table is named channelname_dest1_tochanneltype, where "channelname" is the name of your channel, "dest1" stands for destination component, and "tochanneltype" is the destination of the channel (e.g. "to_dat_err" stands for "to database errors"). The source error log follows a similar naming scheme, with "dest1" being replaced by "source1". Note that the logs tables are the same and do not depend on the channel being set up. These logs must be exported to your database. |
| Channel Database Destination or Source Data Tables** | The Database components contain destination or source data tables: The names and columns of the data tables will be identical to the tables you set up in the VMD file. The defined table columns in the VMD file will also map to the columns defined in the database. Note that you do not have to export these tables if you have existing data tables that you want to use. |
| Channel Database Source Status Tables* | When a database is specified as the source component for a channel, Iguana creates a status table for each message definition specified in the VMD file. This status table indicates the status of each outgoing message that matches this definition. Iguana polls this status table to determine whether new messages are ready to be sent. For more information, see Basic Database Schema. |
| Channel Message Filter Destination Data Tables* |
The Message Filter contains a single destination data table that must be exported. Its columns are used internally by Iguana for routing purposes and contains only the status table. The original messages are stored in the success logs. The status table is named channelname_status, where "channelname" is the name of your channel. Note that the message filter tables do not refer to the columns in the VMD file. |
| ||
| In the event that the database is unavailable, a text file is created in the Iguana iNTERFACEWARE install directory. ODBC errors will be stored in the log_channelname.txt file, while other error information will be stored in the ServiceErrorLog.txt file. | ||
|