Trace Metaconnector

The Trace Metaconnector allows you to trace events associated with a specified sub connection. You may specify options including where to capture data (either to the HCL Enterprise Integrator® (HEI) console or to a user-specified file name) and whether or not to include a timestamp with each trace log entry.

If there is a problem with your activity or connection, the Trace Metaconnector is a tool for you to use when troubleshooting. Also, trace output is useful for support staff when troubleshooting customer calls.

After launching an activity that uses a Trace Metaconnection, the first piece of information seen is a "BEGIN TRACE" string along with a timestamp. The next sequence of calls is typically LCXIdentify, LCXSetProperty, and then LCXConnect. At this point you may see a number of different activity-specific operations such as LCXExecute, LCXSelect, LCXInsert, LCXFetch, LCXUpdate, or LCXRemove. At the conclusion of an activity you'll usually see LCXDisconnect, followed by LCXTerminate, and then an "END TRACE" label.

Activity Log File

Trace information can be sent to the activity log.

Trace output using the stdout and log file methods uses carriage returns to format some information types, such as field list data. This formatting is not present when using the activity log method for capturing trace output.

Note: The activity log may perform with a noticeable amount of delay. This is caused by the disk input-output operations that are required for making each log entry.