Verifying EDI Projects (EDI Monitoring)

Use the following information to verify that the record import is working.

Step 1            Select EDI Monitoring from the Admin menu.

edi_monitoring_selection.png

The following information is displayed for each record

Column

Description

ID

The EDI event ID number.

Project Name

The name of the EDI project that the event has defined in the EDI Desktop Studio.

Project Type

The type of data, such as personnel, badge, or organization records.

Records Succeeded

The number of records successfully updated during the integration event.

Failed Records

The number of records that were not updated by the integration event. Failed record details are stored in the log files.

Extract Type

The type of data extraction including interface or core (see the following step).

Start Time

The date and time when the data integration event began.

End Time

The date and time when the data integration event ended.

Step 2   Review the EDI projects on the EDI Monitoring window. There are two types of Extract Types:

·         Interface: this occurs when the ICPAM server connects to the remote data source and retrieves the records that have been added or modified since the last time the Interface extract was executed.

·         Core: this occurs when the ICPAM server validates the records retrieved by the Interface process, and then edits the ICPAM personnel database to make the additions, deletions, or edits.

edi_monitoring.png

If the Interface entry shows success, but the core does not, something in the extracted record is not compatible with the mapping between the Active Directory and ICPAM databases.

Step 3            To troubleshoot the errors and view additional error details, select Error Monitoring from the Admin menu.

Admin_options_list_2.jpg

Step 4  The Error Monitoring window displays entries for each failed record as shown below. The Messages column includes text regarding the cause. For example: “Site is null” messages occur if the site name was not entered on the Default/Transform values screen of the EDI Studio project.

error_monitoring.png

In addition, the following can occur:

Record updates in AD include a timestamp for the edit. When the ICPAM server connects, it compares the timestamp of the last edit in AD with what the last edit is that ICPAM knows about. If the AD timestamp is newer, the record is extracted.

After the record has been extracted from AD into ICPAM, the fields are checked for validity during the Core extract. For example if the AD last name (attribute sn) contains a number, ICPAM should fail to import that record into the personnel database because a valid last name cannot contain a number.

Step 5        After you have determined the cause of the error, modify the project. See Modifying a Running EDI Project. If an EDI data integration project fails, identify and resolve the problem, and then complete the instructions in Restarting a Failed EDI Project.

 

See also:

Importing, Starting, and Monitoring EDI Projects in ICPAM

Synchronizing Data Using Enterprise Data Integration (EDI)