Interface Log

The Interface Log records every message processed by the Commander4j interface system — both inbound messages received from external systems and outbound messages sent to them. It is the primary tool for monitoring integration activity and diagnosing message failures.

What is Logged

Every time the interface service processes a message, a record is written to the log containing:

Field	Description
Event Time	When the message was processed
Interface Type	The type of message (e.g. ProcessOrder, DespatchConfirmation, MaterialDefinition, BillOfMaterials)
Direction	Inbound (received from an external system) or Outbound (sent to an external system)
Message Reference	A reference identifier for the message
Message Information	Key business data associated with the message, such as a process order number, material code, or SSCC
Action	The operation performed
Message Date	The timestamp carried within the message itself
Status	Success or Failed
Error	If the message failed, the error description is recorded here
Workstation	The workstation or service instance that processed the message
Filename	The source or destination file associated with the message

Filtering the Log

The screen provides the following filters:

Filter	Description
Date range	From and to event timestamps
Interface Type	Dropdown of all known message types
Direction	Inbound / Outbound / All
Status	Success / Failed / All
Action	Filter by the action field
Message Reference	Text search
Message Information	Text search (e.g. search for a specific process order or SSCC)
Error Message	Text search within the error description
Limit Results	Restrict the number of rows returned

Resubmitting Failed Messages

If a message has a status of Failed, it can be resubmitted for reprocessing. Select one or more failed rows and use the resubmit function. Commander4j will re-execute the appropriate message handler for each selected record.

This is useful when a message failed due to a transient issue (for example, missing reference data that has since been created) and can be safely retried without re-sending the original file.

Exporting

The filtered result set can be exported to Excel for offline analysis or sharing with support.

Relationship to Interface Admin

The Interface Admin screen is where message types are configured — their input/output paths, formats, and trigger conditions. The Interface Log is the operational view of what those configured interfaces have processed.

Database Table

Log records are stored in SYS_INTERFACE_LOG. Old records can be removed using the archive function.