Does SFC Java 3.5.x / 3.6.0 work with RTDS 3.5+?
Hi,
Could someone confirm whether RTDS 3.5 and later only work with RSSL and standard SSL connectivity using port 8101 will cease to function? Specifically we are interested in how the RTDS platform upgrade will impact our SFC Java adaptor which is currently based on SFC Java 3.5.x.
We understand from the API compatibility matrix and from this answer that SFC Java 3.5.6 is obsolete but it is not yet EOL. Is this correct? Does SFC Java 3.6.0 offer any benefits over 3.5.6 in terms of support for RTDS 3.5+ and/or with regards to rebranding?
Thanks
Best Answer
-
Hello @Paolo Parlapiano,
I am looking at REFINITIV REAL-TIME DATA DISTRIBUTION SYSTEM aka TREP - Technical Doc Links for 3.5.1 – April 2021 v3
From there I follow through to the latest ADS Installation Guide (3.5.1)
It continues to support SSL connections, on port 8101.
Per API Compatibility Matrix, JSFC 3.5.6 is in active obsolescence.
In JSFC 3.6.0.L1 REBRAND document please find:
"
There is *no* impact on the existing customer applications written using SFC Java
API due to rebranding. Also, the connectivity to the Refinitiv products will *not*
be impacted due to rebranding efforts and existing applications will continue to work.
However, starting with the SFC Java version 3.6.0.L1, all future fixes will be made
only on re-branded releases. Post July 2021, non-rebranded versions such as 3.5.6.L1
for example, will no longer be available for download due to licensing reasons. We
will continue to offer support for non re-branded versions of the API that includes
investigating the reported issues and recommend workarounds. Please note that a
workaround may not always be possible or feasible. Therefore, we recommend moving to
the re-branded versions of SFC Java API."
With this in mind, I would suggest to plan migrating the custom JSFC consumer to RTSDK Java EMA to benefit from the latest features, highly efficient implementation and API being open source (see on GitHub).
1
Answers
-
Hello @Paolo Parlapiano
If the client interested in EMA Java API, the client can check the following resources for more detail and overview:
0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛