Defining custom formats for the MFT stand-alone file logger

It is possible to define a subset of custom message types within a log format definition to reduce the amount of configuration required to customize your log file format.


If a messageTypes element is not included in the FileLoggerFormat.xml file, the format for that message type uses the default format. You need only to specify the formats we want to be different from the default.


Example

In this example, the format definition replaces the default format for the transferStarted message type, with this reduced version that outputs only the user that started the transfer. All other message types use the default format because they are not included in this log format definition:

<?xml version="1.0" encoding="UTF-8"?>
<logFormatDefinition  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.00"
 xsi:noNamespaceSchemaLocation="FileLoggerFormat.xsd">
  <messageTypes>
    <transferStarted>
      <format>
        <inserts>
          <insert type="user"   width="19" ignoreNull="false">/transaction/action/
           @time</insert>
          <insert type="user"   width="48" ignoreNull="false">/transaction/@ID</insert>
          <insert type="system" width="6"  ignoreNull="false">type</insert>
          <insert type="user"   width="0"  ignoreNull="true">/transaction/originator/
           userID</insert>
        </inserts>
        <separator>;</separator>
      </format>
    </transferStarted>
  </messageTypes>
</logFormatDefinition>
Parent topic: MFT stand-alone file logger format


Related information