sessionType

acceptor

Session type. If the type is not defined, then the session will be resolved as an acceptor.

Valid values: acceptor/initiator.

host

The connecting host for the initiator session

port

The connecting port for the initiator session or listening port for the acceptor session.

If the port property is defined for the acceptor, the FIXEdge server tries to open this port during the acceptor session start and close during its stop. The FIXEdge server accepts such a session only on the defined port.

The same port may be defined for several acceptor sessions. All of these sessions should contain the same value for the 'enableSSL' property.

senderCompID

The assigned value is used to identify a firm that sends the message

senderSubID

The assigned value is used to identify a specific message originator (desk, trader, etc.)

senderLocationID

The assigned value is used to identify a specific message originator’s location (i.e. geographic location and/or desk, trader)

targetCompID

The assigned value used to identify a receiving firm

targetSubID

The assigned value is used to identify a specific individual or a unit intended to receive the message

targetLocationID

The assigned value is used to identify a specific message destination’s location (i.e. geographic location and/or desk, trader)

fixVersion

appVersion

backupHost

Backup host for initiator session

backupPort

Backup port for initiator session

incomingSequenceNumber

0

An initial incoming sequence number

outgoingSequenceNumber

0

An initial outgoing sequence number

heartbeatInterval

30

Heartbeat interval (in seconds)

fixFieldList

User-defined fields for messages. If this list is not empty, the Engine adds it to each outgoing message.

outgoingLoginFixFieldList

Additional fields for the outgoing Logon message

groups

A comma-separated list of routing groups

username

The assigned value is used to identify a username to send in the Logon message for the initiator session and a username to validate with the user name from the Logon request for a session acceptor. The session will be accepted if the username is not defined.

password

disposeOnDisconnect

Disposes the FIX session when another side breaks the connection or in case of disconnection. More details about session statuses can be found in the FIX Antenna Java documentation.

NOTE: If the property is set to true, then the reconnect logic will be suppressed.

startOnload

startTime

stopTime

scheduleTimeZone

resetSequenceOnSchedule

storageNameTimestamped

Ability to add a session creation timestamp to the storage file name.

The timestamp replaces the placeholder {3} from the format defined in the outgoingLogFile parameter (see below).

If the option is enabled and the storage filename includes a timestamp of the session start, during the backup procedure such file will be moved to a backup folder with the same name. Otherwise, if the filename is simple and without a timestamp, the file will be copied with the timestamp by the FIX Engine backup procedure to support the uniqueness of this file in the backup folder.

storageTimestampFormat

The SimpleDateFormat pattern. 

NOTE: Avoid delimiter chars that are not valid for file system file names.

incomingLogFile

Incoming storage file name pattern.

• {0} will be replaced with actual sessionID
• {1} with actual SenderCompID
• {2} with actual TargetCompID
• {3} can be replaces with timestamp (see 'storageNameTimestamped')
• {4} with actual session qualifier

Acceptable values:

• {0}-{3}.in
• {3}-{0}.in
  

outgoingLogFile

Outgoing storage file name pattern.

• {0} will be replaced with actual sessionID
• {1} with actual SenderCompID
• {2} with actual TargetCompID
• {3} can be replaces with timestamp (see 'storageNameTimestamped')
• {4} with actual session qualifier.

Acceptable values:

• {0}-{3}.out
• {3}-{0}.out
  

timestampsInLogs

timestampsPrecisionInLogs

The desired precision of timestamps in the in/out log files.

Valid values:

• Milli
• Micro
• Nano

By default, human-readable storages include a millisecond timestamp for each message. This behavior could be flexibly changed. For example, it's possible to disable timestamps to minimize the latency and save time for timestamp generation. Or to increase the precision of timestamps if it is needed for better statistics.

markIncomingMessageTime

Transport will set the additional time mark in nanoseconds for incoming messages right after reading data from the socket if this option is set to true.
The AbstractFIXTransport.getLastReadMessageTimeNano() method could return this value.

Note that, by default, messages are marked with a timestamp at the moment of storing them in the storage. But, for incoming messages, it is possible to store the timestamp of the message reading with the enabled markIncomingMessageTime option, but this slightly increases the latency.

enableSSL

keyStorePath

Path to a KeyStore, which contains private keys for a secure connection.

One key is to be set per port.

keyStorePassword

trustStorePath

trustStorePassword

sslKeystoreType

sslTruststoreType

sslKeystoreKeyAlias

sslTruststoreKeyAlias

sslProtocol

Preferred SSL protocol.
For the initiator side, it's a protocol, which is used for handshake initialization (but the server may propose another protocol for connection).
For an acceptor side, it defined a family of possible protocols. See the SSLContext section in the Java Cryptography Architecture Standard Algorithm Name Documentation for information about standard protocol names.
To define certain protocol(s) for communication, please use the acceptedSslServerProtocols option.

acceptedSslServerProtocols

acceptedSslCipherSuites

Accepted SSL cipher suites for connection to the server.
Value type: comma-separated string.
Examples of value: "TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, ..."

keyManagerAlgorithm

keyManagerProvider

Key manager provider. Used to get the KeyManagerFactory instance.
Note that the list of registered providers may be retrieved via the Security.getProviders() method.

trustManagerAlgorithm

sslServerNeedClientAuth