0
●0 ●1 ●3
What are the changes if we migrate from RFA 7.7 to RFA 8.2 and how much effort is required for that
Hi,
Thank you for your participation in the forum.
Is the reply below satisfactory in answering your question?
If yes please click the 'Accept' text next to the reply. This will guide all community members who have a similar question.
Otherwise please post again offering further insight into your question.
Thanks,
AHS
Please be informed that a reply has been verified as correct in answering the question, and has been marked as such.
Thanks,
AHS
25.3k
●87 ●12 ●25
Hi @aftab
When you say RFA 7.7, are you using the MarketData / MarketFeed / SSLED (connection) interface or the OMM / RSLL (connection) based interface?
- If you are already using OMM / RSSL interface then the code changes should be minimal if any.
- If however, you are using the legacy SSLED connection type / MarketData interfaces then there will be considerable code changes required.
To get an idea of the code changes for option 2 above, you can compare the example source code for the legacy example RFASTTicker with something like OMM example StarterConsumer / the RFA tutorials steps 1-7.
You will note for example, that for the OMM interface, the login process, the dictionary request and parsing, the item subscription request, the item payload parsing etc are considerably different compared to the legacy interface.
We generally advise any customer moving away from RFA C++/Java legacy interface to the newer OMM interface to upgrade to EMA (part of the Refinitiv Real-Time SDK) - EMA is easier to learn, there is far less code to write and maintain and we have better learning for EMA on the Developer Portal.
Hi @aftab
I forgot to highlight another very important point.
If you migrate to EMA (rather than RFA 8.x), then you won't have to rewrite your application again - if/when RFA is eventually End of Life (no date at this point in time)
