Trace Message Writer Service (com.ibi.agents.XDTraceAgent)

Syntax:

com.ibi.agents.XDTraceAgent

Description:

This service writes a message to the trace log of the system. The trace log accumulates messages to record the progress of activity within the server. Usually the trace log is used for debugging purposes.

Parameters:

Parameter	Description
Trace Level	The trace level at which the message is written to the trace log. Select one of the following trace levels from the drop-down list: Error Warn Debug
Message	The message to be written to the trace log.
Call at EOS?	In a streaming environment, EOS (End of Stream) is the short message that is sent after the last document, which signifies the EOS. This parameter determines whether this service should be called for the EOS message.

Parameter

Description

Trace Level

The trace level at which the message is written to the trace log. Select one of the following trace levels from the drop-down list:

Error
Warn
Debug

Message

The message to be written to the trace log.

Call at EOS?

In a streaming environment, EOS (End of Stream) is the short message that is sent after the last document, which signifies the EOS. This parameter determines whether this service should be called for the EOS message.

The edges returned are listed in the following table.

Edge	Description
success	The line was successfully sent to the trace system.
fail_parse	iFL used in the parameters was invalid.

The trace message is written to the trace log at the error or debug level. The trace system must be configured to accept the message on the issued level. Users must be made aware that the use of a trace log can adversely affect server performance.

Caution: The trace log is not the transaction log, which can hold messages regarding operations within the server. Messages can be written to the transaction log using the Activity Log Entry service (XDXALogEvent) and the Activity Log Business Error Message service (XDXALogBizErr). While trace messages are usually free format and designed to help debug a problem, the XALog (transaction log) is more structured and often has externally imposed security, event code, and format constraints.