Chapter 6 Logging and debugging 103
Debug messages
In addition to startup information, the <instance name>_eiemain.dbg file records
high-level information about data exchanges found, licenses issued, licenses
absent, and event requests. You should consult
<instance name>_eiemain.dbg if
your data exchange fails to start and no
<exchange_name>.dbg file is created, or if an
event request fails to run.
NOTE
Only one <instance name>_eiemain.dbg debug file is created regardless of how
many data exchanges are configured.
The following text is an example of
<instance name>_eiemain.dbg:
Starting to look for changes to data exchange definitions
Service has detected 1 active data exchanges on AR System
Location of
'FlatFile' adapter obtained
License granded to FlatFile.
Adapter Version: 7.1.00
Thread started to manage exchange: SamplePullExchange_2
Starting threads to manage event driven requests
Immediate async thread started.
Event Request cleanup thread started.
Waiting for 5 minutes to look for changes to data exchange definitions.
Using an <exchange_name>.dbg debug file
For detailed information about the problems that occur in specific data exchanges,
you should enable the log of debug events in
eie.cfg.
If you enable the logging of debug events, when a data exchange starts, the
Integration Engine service creates a unique debug file for it, assigning it the name
of the data exchange. For example, if the data exchange is named
GetDiskDetail,
the debug file will have the name
GetDiskDetail.dbg.
NOTE
If you configure multiple concurrent data exchanges on the Main tab of the
EIE:DataExchange, the Integration Engine service debug files are assigned the
name of the data exchange with a sequence number appended to it. Using the
example in the previous paragraph, if two concurrent data exchanges are
configured, the debug file names are
getdiskdetail_1.dbg and
getdiskdetail_2.dbg.
Each data exchange debug file provides a list of all rules entered in the Data
Exchange application in the order that they are entered on the respective Mapping
Information window for AR System forms, CI classes, or relationship classes. The
debug file also indicates on which tabs of the forms these rules are entered.
NOTE
EIE:DataMapping, EIE:CMDBDataMapping, and EIE:CMDBRelMapping are
backend forms used to store information. You cannot interact directly with these
forms.
