What are the differences between the Access Point 'platform.rdp' and 'desktop.workspace' within the
Recently, I requested and received permission for KOSPI and KOSDAQ data from the Korea Exchange (KRX). Therefore, I am trying to obtain a Chain RIC list for the indices using the refinitiv-data package. However, when the session in the refinitiv-data.config.json file is set as 'platform.rdp', as shown in Picture 1, it returns a warning and does not retrieve the data. When I modify the session to 'desktop.workspace', I can obtain the data successfully.
So, What is the reason for not being able to retrieve the data with the rdp session, despite having permission? And, What are the differences between 'platform.rdp' and 'desktop.workspace'?
"default": "platform.rdp", -> This Point!!
"platform": {
"rdp": {
"app-key": "YOUR APP KEY GOES HERE!",
"username": "YOUR RDP LOGIN OR MACHINE GOES HERE!",
"password": "YOUR RDP PASSWORD GOES HERE!"
},
"deployed": {
"app-key": "YOUR APP KEY GOES HERE!",
"realtime-distribution-system": {
"url" : "YOUR DEPLOYED HOST:PORT GOES HERE!",
"dacs" : {
"username" : "YOUR DACS ID GOES HERE!",
"application-id" : 256,
"position" : ""
}
}
}
},
"desktop": {
"workspace": {
"app-key": "YOUR APP KEY GOES HERE!"
}
}
}
Best Answer
-
Thanks for reaching out to us.
The Refinitiv Data Library can retrieve data from the Refinitiv Data Platform (platform.rdp) and the desktop application running on the same machine (desktop.workspace).
With the platform.rdp session, the library establishes the connection to the Refinitiv Data Platform on Cloud. However, with the desktop.workspace session, the library retrieves the data via the desktop application (Refinitiv Eikon or Refinitiv Workspace) running on the same machine so you need to run the desktop application on the same machine to use the desktop.workspace session.
For more information, please refer to the Refinitiv Data Library for Python overview.
The permission may be different between the platform.rdp session and the desktop.workspace session. Please contact your Refinitiv Account team or Sales team directly to verify the permission.
I hope that this information is of help.
0
Answers
-
Thank you Jirapongse After contacting the sales representative, it has been confirmed that this issue is related to the contractual relationship with the product.
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 中文论坛