The fixaj.log file is generated in two different locations. For example:

• C:\Program Files (x86)\iWay61\config\base\logs\fixaj.log

  No logs are captured in this instance of the log file. It is empty.

• C:\FIX\logs\fixaj.log

  This instance of the log file is capturing the logs of the FIX Engine.

Workaround:

The fixaj.log file is the internal B2Bits log. The reason the server is logging it is because the iWay Integration Solution for FIX has a log4j.properties file that sets B2Bits to debug level logging in the iwxfix\lib\b2bits folder. If a similar file is placed in front of the iSM classpath, a B2Bits log file will also appear in that location.