A new format of Version property is available since FIXEdge 5.9.
...
Examples of dictionary modifications can be found in the FIX and FIXML Dictionaries Customization Guide.
Protocol customizations in FIX Antenna based products can be done as:
...
Add paths to custom dictionaries files to DictionariesFilesList property in the engine.properties file
...
Add definitions of parsers to AdditionalParsersList property in engine.properties file
e.g.
| Code Block | ||
|---|---|---|
| ||
# List of additional protocols id's that require to register parsers # Format of each value divided by semicolon: [UNIQUE_PARSER_NAME@][FIXT_PROTOCOL1:]APP_PROTCOL1[,APP_PROTCOL2...] # Example if you have FIX44Custom dictionary: AdditionalParsersList = FIX44Custom |
| Info |
|---|
In the case of modification FIX50+ protocols, a transport-level protocol can be also specified in the parser name. The format is the following: [UNIQUE_PARSER_NAME@][FIXT_PROTOCOL1:]APP_PROTCOL1[,APP_PROTCOL2...] AdditionalParsersList = CustomParserName1@FIXT11:FIX50Custom |
...
Configure FIX session to use a custom dictionary
Modify the Version property of the session in the configuration.
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
Session.Sender/Target.ParserVersion = FIX44Custom Session.Default.ParserVersion = CustomParserName1@FIXT11:FIX50Custom |
...
The value of the default custom version is specified in the DefaultCstmApplVerID <1408> field of the Logon message. Its value can be configured in FIXEdge.properties via the Version property - the first custom version in the list will be considered the default one and its value will be set for the DefaultCstmApplVerID <1408> field of the Logon message.
...