Detailed Tracing
Highly detailed logging can be written to the database for individual imports. This is especially useful during development and testing.
In addition to the logging controlled by the Log
element, you can
set up detailed tracing for the operation of each Import
element
independently. This is done using the TraceActions
,
TraceField
, and TraceLifeTime
attributes of
the Import
element.
- To trace each import at a summary level, a record is created in the
ECMImportLog_Summary
table each time the Business Importer is started in import or simulation mode. - To trace the objects included in the import, a record is created in the
ECMImportLog_Object
for each object included in the import (except for theCustom
object). - To track individual actions, a record is created in the
ECMImportLog_Detail
table for each action of the type(s) identified in theTraceAction
attribute of theImport
element.
TraceLifeTime
attribute of the
Import
element to the minimum timespan consistent with your
debugging needs. Tracing Imports (Summary)
A record is created in the ECMImportLog_Summary
table each time the
Business Importer is started in import or simulation mode. Each row
contains the following information:
Column | Description |
---|---|
ImportID |
Unique identifier for each record. |
ImportName |
The |
ImportType |
The |
Action |
|
StartDate |
The date and time the import was started (database date and time). |
EndDate |
The date and time when the import finished (database date and time). |
Status |
Values:
|
Processed |
The number of records processed from the data source. |
Rejected |
The number of records rejected from the data source. The same record can be rejected for multiple reasons, but will be counted only once. |
Tracing Objects
A record is created in the ECMImportLog_Object
for each object
included in the import (except for the Custom
object). Each row
contains the following information:
Column | Description |
---|---|
ImportObjectID |
Unique identifier for each record. |
ImportID |
Reference to the |
ObjectName |
The name of the object as specified in the XML. |
ObjectType |
The type of the object. |
StartDate |
The date and time the import of this object was started (database date and time). |
EndDate |
The date and time when the import of this object finished (database date and time). |
Processed |
The number of records for this object processed from the data source. |
Rejected |
The number of records for this object rejected from the data source. The same record can be rejected for multiple reasons, but will be counted only once. |
Matched |
The number of records for this object matched between the data source and the compliance database. |
Updated |
The total number of records for this object updated in the compliance database. |
Created |
The total number of records for this object created in the compliance database. |
Deleted |
The total number of records for this object deleted from the compliance database. |
Tracing Records
ECMImportLog_Detail
table for each action
of the type(s) identified in the TraceAction
attribute of the
Import
element. The TraceAction
attribute
specifies whether the creation, updating, rejection, or deletion of individual
records needs to be tracked in the database logging. ECMImportLog_Detail
table.
There are primarily relationships between objects. For example, the license
allocation object cannot be logged in this way.Column | Description |
---|---|
ImportDetailID |
Unique identifier for each record. |
ImportID |
Reference to the |
RecordNumber |
ID of the record considered. |
Action |
|
MGSRecordKey |
ID of the record in the FlexNet Manager Suite compliance database. |
ImportObjectID |
Reference to the |
RecordDescription |
To more clearly identify the individual record, this column is
populated as defined by the |
Message |
This column contains the reasons for discarding records. |
2022 R1