Skip to content

FIX parameters

When you implement an integration use case that requires a FIX connection, you can use the following FIX parameters in your proxy service artifact.

Info

The Micro Integrator can use the FIX transport only if the FIX transport listener and sender are enabled and configured at the server level. Read about the FIX transport.

To add service-level transport parameters to a proxy service:

  1. Open your proxy service artifact in MI VS Code extension.
  2. In the Design View, click on the Edit button and expand the Advanced Options section and navigate to Service Parameters.

  3. Click the Add Parameter text button to open the following form to add the parameter name and value as a key-value pair:

See Creating a Proxy Service for instructions.

Service-Level parameters

Parameter Description
transport.fix.AcceptorConfigURL URL to the Quickfix/J acceptor configuration file (see notes below).

This is required for receiving messages over FIX.
transport.fix.InitiatorConfigURL URL to the Quickfix/J initiator configuration file (see notes below).

Required for sending messages over FIX.
transport.fix.AcceptorLogFactory Log factory implementation to be used for the FIX acceptor (determines how logging is done at the acceptor level).

Possible values are console, file, and jdbc.

Logging is disabled by default.
transport.fix.InitiatorLogFactory Log factory implementation to be used for the FIX acceptor (determines how logging is done at the acceptor level).

Possible values are console, file, and jdbc.

Logging is disabled by default.
transport.fix.AcceptorMessageStore Message store mechanism to be used with the acceptor (determines how the FIX message store is maintained).

Possible values are memory, file, sleepycat, and jdbc.

The default value is memory.
transport.fix.InitiatorMessageStore Message store mechanism to be used with the initiator (determines how the FIX message store is maintained).

Possible values are memory, file, sleepycat, and jdbc.

The default value is memory.
transport.fix.ResponseDeliverToCompID If the response FIX messages should be delivered to a location different to the location where the request originated, use this property to set the DeliverToCompID field of the FIX messages.
transport.fix.ResponseDeliverToSubID If the response FIX messages should be delivered to a location different to the location where the request originated, use this property to set the DeliverToSubID field of the FIX messages.
transport.fix.ResponseDeliverToLocationID If the response FIX messages should be delivered to a location different to the location where the request originated, use this property to set the DeliverToLocationID field of the FIX messages.
transport.fix.endAllToInSequence By default, all received FIX messages (including responses) will be directed to the inSequence of the proxy service. Use this property to override that behavior.

By default, this setting is true.
transport.fix.BeginStringValidation Whether the transport should validate BeginString values when forwarding FIX messages across sessions.

By default, this setting is true.
transport.fix.DropExtraResponses In situations where the FIX recipient sends multiple responses per request, use this parameter to drop excessive responses and use only the first one.

By default, this setting is false.