The name of the ReutersRFA adapter transport.

This parameter should be set to an optimum value based on the incoming message rate and number of CPUs available on the machine.

Defaults to 4

From which the market Depth should be constructed and published Possible valid values: MARKET_PRICE / MARKET_BY_PRICE / MARKET_BY_ORDER

Defaults to MARKET_PRICE

Level of market depth to be published.

Defaults to 5

Absolute file path where RIC translation file exists. Sample file exists in adapter parameter directory (ric-translation.txt. Invalid path leads to ignore the RIC translation.

List of fields to be considered while decoding OMM Message for payload. For this the ACRONYMs from RDM dictionary should be used and separated by comma(","). The asterisk character ("*") can be used to include all fields.

Defaults to None ("").

For Example: QUOTIM_MS,TIMCOR_MS

List of fields to be ignored while decoding OMM Message for payload. For this the ACRONYMs from RDM dictionary should be used and separated by comma(","). The asterisk character ("*") can be used to exclude all fields.

Defaults to None ("").

Example combinations:

Subset of include fields to be considered to generate update events. For this the ACRONYMs from RDM dictionary should be used and separated by comma(","). The asterisk character ("*") can be used to specify all include fields.

Defaults to None ("") (No updates will be generated on payload changes).

For Example: QUOTIM_MS

A measure of severity for a message, it provides control over which messages to be displayed. RFA Java uses four logging levels:

File path where all the logs should be stored.

Default value is RFA_%u.log

If this is'true' and given file path exists then appends logs to the file else overwrites them.

Default value is true.

This property carries set of fields which need to be validated and apply string escaping if there is any special character. Default values are BCAST_TEXT, SEG_TEXT, TOPIC_CODE, CO_IDS, DSPLY_NAME, DSPLY_NMLL, GN_TXT16_2

This is applicable if "PUBLISH_DEPTH_FROM" is MARKET PRICE. Valid values are 'tick' or 'depth'.

Default value is 'tick'

The MARKET PRICE model gets both depth data. This depth can be either top of the book or order book. Client can request for either type by configuring transport properties "Depth.BID.Price", "Depth.ASK.Price" etc. RIC for these two depth types will be different.

For example: ricTranslation.txt has following mapping

which means, if subscribed for symbol ABC.L then internally for tick request will translate as ABC.L but for depth request it will be translated as ABC.LO

If interested in top of the book data then configure:

MPDepth_RICType='tick'. RIC will be ABC.L

If interested in depth book data then configure:

MPDepth_RICType='depth'. RIC will be ABC.LO

Publish empty depths. By default, TICK/DEPTH is not published when there is no FID in the OMM message which matches default FIDs. Still, if you are interested in receiving empty depths then following property will enable it

<property name="AllowEmptyDepths" value="true"/>

<property name="AllowEmptyTicks" value="true"/>

Defaults to false.

There are some messages which will be logged for every request received by the transport. In normal condition this is unnecessary overhead but when there is any problem such messages are required for debugging purpose. You can enable this property using:

<property name="LogMessages" value="true"/>

Defaults to false.

Set the value of ApplicationId in LOGIN_REQ. If not set, ApplicationId will default to transport name.