publishing datatype 2 marketfeed and 6 Refinitiv Wire Format

graham.street
graham.street Explorer
edited June 4 in TREP APIs

Hi

I am not a developer so forgive this simple question. How much effort would be required to change a provider from sending data to the ADH in Marketfeed (datatype 2) to Refinitiv wire format RWF (datatype 6)

We have a number of applications that send data to TREP but they send data in Marketfeed. I hear that soon the support for marketfeed will diminish and moving to RWF if a sensible move. I am wondering from your development perspective, how much effort is required ?

Hope you can help

best regards

Graham

Tagged:

Answers

  • Gurpreet
    Gurpreet admin

    Hello @graham.street

    Your applications must have been written using the RFA API, which were using the legacy MarketFeed protocol. Modifying these application to now use RWF/OMM will require application code change. I can't quantify the amount of effort, but it would be a good idea to get your developers to look into these applications with priority - since the support for MarketFeed will be dropped from the infra components in coming years, and these will stop working altogether.

    Your developers have an option use latest version of legacy RFA SDK and modify the code to use OMM, or completely re-write the application using EMA SDK. Latter option is better since EMA is considerably easier to use and would help if the developers of the original app are no longer around.

    Here are couple of resources from migrating from RFA to EMA API.

    https://developers.lseg.com/en/article-catalog/article/legacy-api-migration

    https://developers.lseg.com/en/article-catalog/article/rfa-to-ema-migration-notes

Categories