Table of Contents |
---|
Overview
...
- EPAM products have their own format, that closely mimics the structure of official FIX specification, leveraging "block" elements and references, defining type system, and some more. Additionally, besides runtime metadata, it also contains human-readable textual details about message & tag meaning.
The QuickFIX dictionary is natively supported by FIX Antenna C++ since FIX Antenna C++ 2.28.0 and no longer requires manual conversion to FIX Antenna format. The QuickFIX dictionary has a simplified format that does not use "blocks" and "references", and instead describes the same messages in a flatter format. It also skips textual details on content.
QuickFIX Dictionary doesn't support conditional validation.Info The QuickFIX dictionary is not yet natively supported by FIX Antenna JAVA or FIX Antenna .NET Core
...
Structure | Description | |||
---|---|---|---|---|
<fixdics> | Root tag of the additional dictionary. | |||
<update> | Dictionary update operation. Can be zero or one <update> element. | |||
<fixdic> | Dictionary to be updated. Can be zero or more <fixdic> elements. | |||
@id | ID of the additional dictionary. | |||
@parent_id | ID of the original dictionary additional dictionary based on. Valid values are:
| |||
@fixversion | FIX version additional dictionary based on. | |||
@title | The name of the additional dictionary. | |||
@version | Additional dictionary version. | |||
@date | Date of the last additional dictionary update. | |||
... | <typedef>/<valblockdef>/<fielddef>/<blockdef>/<msgdef> to be added/updated. The structure of listed elements is the same as described in standalone dictionary structure. | |||
</fixdic> | - | |||
</update> | - | |||
</fixdic> | - |
Please see the article How to use custom dictionaries for the cases of additional dictionaries usage.
Info |
---|
There is no way to remove elements from the base FIX dictionary |
How to manage a list of dictionaries in FIXAntenna based applications
List of dictionaries to be used by FIXAntenna based applications can be managed using the DictionariesFilesList property in engine.properties
configuration file.
...
As mentioned above, dictionaries can be customized for the needs of a particular exchange.
Refer to How to use custom dictionaries with FIXEdge article for details.
...
Simple Client can be used in order to check that the dictionary doesn't have errors.
Below is the step-by-step instruction how to check the dictionary with the help of Simple Client:
- Open the folder with SimpleClient;
- Specify prepared dictionary in DictionariesFilesList property in
engine.properties
configuration file Simple Client refers on; - Run the Simple Client;
- Check the results of the launch:
- If the specified dictionary doesn't have errors, Simple Client will be launched successfully;
- If If the specified dictionary has any error, Simple Client won't be started and the message with the reason will appear: