For EMA application, is that better to implement with LPC?
Considering the internet connection not so stable as direct connect, is that better to ask the client to use LPC to take the job of token refresh and runs the EMA app behind it? in comparison with the EMA application directly connect to RTO via internet. And any other benefits?
Best Answer
-
Hi @Frederic
The use of LPC is only advised as a last resort where the client is refusing/unable to convert their legacy API application to a newer Strategic API that supports RTO.
As you know LPC is acting as a bridge/middleware between the legacy API application and RTO. If your customer is finding their RTO connection is not stable, I would not expect LPC to improve the stability of their RTO connection.
Therefore, I would not recommend an EMA application using LPC to source data from RTO.
0
Answers
-
or they should accept that the quality is as such.
Besides that, any network tool may validate the data connection quality for RTO?
0 -
HI @Frederic
That is something to take up with the RTO team and product owners.
EMA is designed to try and recover from RTO disconnect whenever possible.
I assume your client is using ChannelSet to specify more than one region location - so that EMA can try to connect to different regions if required?
Enterprise Message API (EMA) - Configuration Overview | Refinitiv Developers
0 -
The issue is they have 4 applications (2 in docker and 2 on PC without docker) using the same machine id (we are asking 'back office' to add more), only 1 applications met such issue and the others look good.
0 -
You will need to check with your network/comms team to determine the stability of your Internet connections. RTO offers standard and premium resiliency for connection recovery. Please read the RTO manuals to understand the offerings.
I saw that you are using the same machine ID among your applications. This may be used only if you are not using the ID simultaneously among applications. If you use the ID simultaneously (not a Refinitiv recommendation), disconnections and timeouts will occur because the authentication system gets confused about token ownership among the applications.
0 -
Many thanks0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 684 Datastream
- 1.4K DSS
- 614 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 248 ETA
- 552 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 640 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 191 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛