# QuickFix (Beta)

{% hint style="info" %}
The **Oracle NetSuite** connector is currently in beta phase. Learn more about the [Beta Program](broken://spaces/WCe1TFuaV0VWAPvSznmI/pages/xCQqIwZRiqUPw5O5BACZ).
{% endhint %}

**QuickFix** sends and receives financial messages using the [FIX (Financial Information eXchange)](https://www.fixtrading.org/) protocol, which is a global standard for real-time electronic trading communication. It enables the integration of trading systems and financial institutions with brokers, exchanges, and other market participants.

## **Parameters**

Take a look at the configuration parameters for the connector. Parameters supported by [Double Braces expressions](/documentation/connectors-and-triggers/double-braces/overview.md) are marked with `(DB)`.

### **Required tab**

<table data-full-width="true"><thead><tr><th>Parameter</th><th>Description</th><th>Default value</th><th>Data type</th></tr></thead><tbody><tr><td><strong>Fix version (Begin String)</strong> <code>(DB)</code></td><td>FIX protocol version (for example, <code>FIX.4.4</code>).</td><td>N/A</td><td>String</td></tr><tr><td><strong>Sender Comp ID</strong> <code>(DB)</code></td><td>Identifier of the counterparty sending the messages.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Target Comp ID</strong> <code>(DB)</code></td><td>Identifier of the counterparty that will receive the messages.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Connection Type</strong></td><td>Defines whether FIX will be <strong>initiator</strong> or <strong>acceptor</strong>.</td><td>initiator</td><td>String</td></tr><tr><td><strong>Host</strong> <code>(DB)</code></td><td>IP address or hostname to connect to (initiator).</td><td>N/A</td><td>String</td></tr><tr><td><strong>Port</strong> <code>(DB)</code></td><td>Port to connect to the FIX server (initiator).</td><td>N/A</td><td>Integer</td></tr><tr><td><strong>Start Time</strong> <code>(DB)</code></td><td>FIX session start time (<code>HH:mm:ss</code> format).</td><td>N/A</td><td>String</td></tr><tr><td><strong>End Time</strong> <code>(DB)</code></td><td>FIX session end time (<code>HH:mm:ss</code> format).</td><td>N/A</td><td>String</td></tr><tr><td><strong>Heartbeat Interval</strong> <code>(DB)</code></td><td>Interval between heartbeat messages, in seconds.</td><td>N/A</td><td>Integer</td></tr><tr><td><strong>Use Data Dictionary</strong></td><td>When enabled, allows the use of the FIX dictionary file (<code>dataDictionary</code>).</td><td>False</td><td>Boolean</td></tr><tr><td><strong>Fail On Error</strong></td><td>If the option is activated, the pipeline's execution with an error will be interrupted. Otherwise, the pipeline execution proceeds, but the result will show a false value for the <code>"success"</code> property.</td><td>False</td><td>Boolean</td></tr></tbody></table>

### **Optional tab**

<table data-full-width="true"><thead><tr><th>Parameter</th><th>Description</th><th>Default value</th><th>Data type</th></tr></thead><tbody><tr><td><strong>Lazy Create Engine</strong></td><td>If true, the QuickFIX/J engine is only created when the first message is sent or a consumer is configured. If false, the engine starts as soon as the endpoint is created. If this parameter isn’t set, the default value from the connector settings is used.</td><td>False</td><td>Boolean</td></tr><tr><td><strong>Session ID</strong> <code>(DB)</code></td><td>Identifies a specific FIX session. The format is: <code>(BeginString):(SenderCompID)/(SenderSubID)/(SenderLocationID)-(TargetCompID)/(TargetSubID)/(TargetLocationID)</code>.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Reset On Logon</strong></td><td>If enabled, resets the sequence numbers when logging on.</td><td>False</td><td>Boolean</td></tr><tr><td><strong>Reset On Logout</strong></td><td>If enabled, resets the sequence numbers when logging out.</td><td>False</td><td>Boolean</td></tr><tr><td><strong>Reset On Disconnect</strong></td><td>If enabled, resets the sequence numbers when connection is lost.</td><td>False</td><td>Boolean</td></tr><tr><td><strong>Reset SeqNum Flag</strong></td><td>If enabled, send <code>ResetSeqNumFlag=Y</code> on logon message.</td><td>False</td><td>Boolean</td></tr><tr><td><strong>Reconnect Interval</strong> <code>(DB)</code></td><td>Waiting time between reconnection attempts, in seconds.</td><td>N/A</td><td>Integer</td></tr><tr><td><strong>Logon Timeout</strong> <code>(DB)</code></td><td>Maximum time to complete a logon, in seconds.</td><td>N/A</td><td>Integer</td></tr><tr><td><strong>Logout Timeout</strong> <code>(DB)</code></td><td>Maximum time to complete logout, in seconds.</td><td>N/A</td><td>Integer</td></tr><tr><td><strong>Socket No Delay</strong></td><td>If enabled, activates <code>TCP_NODELAY</code> to reduce latency.</td><td>False</td><td>Boolean</td></tr><tr><td><strong>Socket Keep Alive</strong></td><td>If enabled, activates <code>TCP keepalive</code> on socket connection.</td><td>False</td><td>Boolean</td></tr><tr><td><strong>Use Data Dictionary</strong></td><td>If enabled, allows validation using a FIX dictionary.</td><td>False</td><td>Boolean</td></tr><tr><td><strong>Data Dictionary Path</strong> <code>(DB)</code></td><td>Path to FIX definition file (for example, <code>FIX44.xml</code>).</td><td>N/A</td><td>String</td></tr><tr><td><strong>Validate Fields Out of Order</strong></td><td>Validates messages even if fields are out of order.</td><td>False</td><td>Boolean</td></tr><tr><td><strong>Validate User-Defined Fields</strong></td><td>Enable validation for user-defined fields against the dictionary.</td><td>False</td><td>Boolean</td></tr><tr><td><strong>Start Day</strong> <code>(DB)</code></td><td>Day of the week to start the session (for example, Monday).</td><td>N/A</td><td>String</td></tr><tr><td><strong>End Day</strong> <code>(DB)</code></td><td>Day of the week to end the session (for example, Friday).</td><td>N/A</td><td>String</td></tr><tr><td><strong>Use Local Time</strong></td><td>If enabled, uses local time instead of UTC.</td><td>False</td><td>Boolean</td></tr><tr><td><strong>Check Latency</strong></td><td>If enabled, activates latency checking on incoming messages.</td><td>False</td><td>Boolean</td></tr><tr><td><strong>Max Latency</strong> <code>(DB)</code></td><td>Maximum allowed latency value, in seconds.</td><td>N/A</td><td>Integer</td></tr><tr><td><strong>File Store Path</strong> <code>(DB)</code></td><td>Directory where messages and logs will be stored.</td><td>N/A</td><td>String</td></tr><tr><td><strong>File Log Path</strong> <code>(DB)</code></td><td>Directory to store session logs.</td><td>N/A</td><td>String</td></tr></tbody></table>

### **Headers tab**

<table data-full-width="true"><thead><tr><th>Parameter</th><th>Description</th><th>Default value</th><th>Data type</th></tr></thead><tbody><tr><td><strong>EventCategory</strong></td><td>The category of the event being processed.</td><td>N/A</td><td>String</td></tr><tr><td><strong>MessageType</strong> <code>(DB)</code></td><td>The FIX message type (<code>MsgType</code> tag) to be used.</td><td>N/A</td><td>String</td></tr></tbody></table>

### **Documentation tab**

<table data-full-width="true"><thead><tr><th>Parameter</th><th>Description</th><th>Default value</th><th>Data type</th></tr></thead><tbody><tr><td><strong>Documentation</strong></td><td>Section for documenting any necessary information about the connector configuration and business rules.</td><td>N/A</td><td>String</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.digibee.com/documentation/connectors-and-triggers/connectors/tools/quickfix.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.