Ema Java library and user_list.txt file

In the LPC 1.4 install guide, section 7.3, it discusses the layout of the user_list.txt file. Column 1 is the “username provided by the datafeed client application”. First, I’m assuming that “data file client application” is the application I wrote that is ultimately consuming the rate info.
Does this username correspond to anything configured on the Refinitiv side, or is this just an easy way for the application to indirectly reference the data in user_list.txt? In our user_list.txt, we have one user defined, let’s call it “X”. In my application i am doing this:
EmaFactory.createOmmConsumer(config.host(“host_name”).username(“X”));
This “X” in the Java code needs to match the “X” in user_list.txt, but does it have to match anything else? If we changed the user_list.txt file to be “Y” and updated the Java code to be ”Y”, would that still work, or would something be out of sync somewhere.
If I understand the overall process, we’ll need to update the user_list.txt with the new ServiceID and secret. But for my question, the scope is just on the column 1 value, assuming everything else stays the same.
Best Answer
-
Thank you for reaching out to us.
The LPC allows legacy or existing real-time applications to consume data from Refinitiv Real-Time Optimized (RTO) on Cloud. Legacy or existing real-time applications use user names to login to the server while RTO uses client id and client secret.
The Refinitiv Real-Time Legacy Protocol Converter maps the user name to a Service ID account listed in the user_list.txt file. Therefore, the user names in the user_list.txt file must match the user names used by legacy or existing real-time applications.
As far as I know, this username doesn't correspond to anything configured on the Refinitiv side.
0
Answers
-
Hello @shawn bower
The RTSDK Java/EMA Java API can connect to RTO directly without the need of LPC server (see ex113_MP_SessionMgmt, ex450_MP_QueryServiceDiscovery, and ex451_MP_OAuth2Callback_V2 examples). Could you please let us know why you are using the LPC with EMA?
0 -
0
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
- 690 Datastream
- 1.4K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 559 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 279 Open PermID
- 45 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 716 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
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛