Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

...

ParameterDescriptionExample

FixLayer.FixEngine.Sessions.ArchivePath

Defines the path to move log files after the session is closed.

Note: directory must exist otherwise the backup procedure will fail.

Warning

It shouldshouldn't point to the path from BackupDirectory (defined in engine.properties), otherwise error message will occur on session start, and the session won't start.

FixLayer.FixEngine.Sessions.ArchivePath = FixEdge1/log/archive
FixLayer.FixEngine.Session.Session_Name.StorageType

Mandatory.  Defines the session storage type.

Valid values: "persistent" | "persistentMM" | "splitPersistent" | "transient" | "null"

FixLayer.FixEngine.Session.TestFIXAcceptor.StorageType = persistentMM
Logging parameters: refer to Logging parameters page for details.

If you want FIXEdge to store logs in system logs or print it to the console you should change Log.Device property:

Accepted values:

...

FixLayer.FixEngine.Session.Session_Name.LogDirectory

Optional. Defines the path to the directory in which logs of the primary connection of the session are stored.

If this property was not specified with value then the value of the LogDirectory will be used.

Info

This parameter is available since FIXEdge C++ 6.14.0 release.

FixLayer.FixEngine.Session.TestFIXAcceptor.LogDirectory = FixEdge1/logs
FixLayer.FixEngine.Session.Session_Name.Backup.LogDirectory

Optional. Defines the path to the directory in which logs of the backup connection of the session are stored.

f this property was not specified with value then the value of the BackupDirectory will be used.

Info

This parameter is available since FIXEdge C++ 6.14.0 release.

FixLayer.FixEngine.Session.TestFIXAcceptor.Backup.LogDirectory = FixEdge1/logs/backup
Logging parameters: refer to Logging parameters page for details.

If you want FIXEdge to store logs in system logs or print it to the console you should change Log.Device property:

Accepted values:

  • File - messages will be written to the file.
  • Console - messages will be written to the console.
  • EventLog - messages will be written to the Windows Event Log (Windows-specific).
  • WinDebug - messages will be written to the OutputDebugString (Windows-specific)
  • Syslog -  messages will be written to the system log (Linux/Unix specific).

It also could be configured per category.

Info

Please see How to divide different categories and severities of log files into different files in the Logging section for details. 

Configuring logs rotation

...