The FIX adapter produces a number of log files and it is essential to be aware of these when diagnosing problems. Essentially there are three main logs to consider:

To configure the logLevel and logFile details, see "Setting logging attributes for packages, monitors and events" in Deploying and Managing Apama Applications in the Apama documentation.

For example, to change the verbosity of the FIX adapter to DEBUG:

This is only applicable for FIX IAF Adapter. For FIX Connectivity adapter, the same information is captured in the correlator log. The IAF log contains all logging output from the transport(s) and codec as well as the IAF as a whole. The log will be sent to the IAFs stdout unless configured via the log switch (-f).

For each FIX session (that is, transport) the embedded QuickFIX engine will produce a set of log files under the directory that is specified in the FileLogPath transport property. By default, this is a directory called FIX_Logs and is created under the IAF (Correlator incase of FIX Connectivity adapter) working directory. Usually there will be six files for each session although from a debugging point of view you are primarily interested in:

When investigating the FIX message log, it is helpful to know the meanings of the various tags. A useful resource for this is FIXimate ( http://fiximate.fixtrading.org/latestEP) which has a full listing of all messages within FIX and their corresponding tags.