fix egress connector

FIX Egress Connector

Version: 17.07

Supported Since: 17.01

What is FIX Egress Connector?

FIX Egress Connector can be used to send messages to FIX acceptors. The implementation is based on QuickFix/J, a free and open source Java implementation of the FIX protocol.

Sample Use Case

Due to the binary nature of FIX messages, the implementation currently supports only the forwarding of FIX messages already received from a FIX initiator. Refer to the introductory sample FIX Message Proxying for instructions on how to configure and use the FIX Egress Connector for message relaying.

Resource Prerequisites

A few project-level resources should be defined before configuring the connector:

  • A message store is used by FIX agents to store and retrieve messages for resend purposes. QF/J allows file-based and database-based message storage.

File-based message storage

Type

Bean

Class Name

org.adroitlogic.x.transport.fix.util.FileMessageStoreFactoryImpl

fileStorePath

path to be used as the filestore

  • Similarly, QF/J logging can be file-based or database-backed.

File-based logging:

Type

Bean

Class Name

org.adroitlogic.x.transport.fix.util.FileLogFactoryImpl

fileLogPath

path to be used for storing logs

  • The connector also requires a Map of additional endpoint settings ([session] category in QF/J) that would be used in establishing the outbound connection.

  • Another Map of additional QF/J application-level settings, containing properties such as logon timeout, should also be defined and provided to the connector.

Out Ports

On Exception

The message will be sent to this outport if the Egress Connector failed to process the message due to some reason

Side Ports

Connector Operation

This port is used to connect operational elements to the Egress Connector. By default, user does not have to connect any operational element and the default connector operation will be used.

Parameters

* marked fields are mandatory.

Heart-beat Interval *

heartbeat interval in seconds

Start Time *

time of day that this FIX session becomes activated

End Time *

time of day that this FIX session becomes deactivated

Reconnect interval *

time between reconnection attempts in seconds

FIX message store *

outgoing message storing factory (file/database) (e.g. file-based)

Log Factory *

outgoing Log storing factory (file/database) (e.g. file-based)

Other sender settings

Map of additional message sender (initiator) application settings

Socket connect host *

host to connect

Socket connect port *

socket port for connecting to a session

Begin String *

version of FIX this session should use

Sender Comp ID *

your ID as associated with this FIX session

Target Comp ID *

counterparty’s ID associated with this FIX session

Other endpoint session settings

Map of additional endpoint session settings

In this topic
In this topic
Contact Us