Python scripts inside of the Docker container to connect to Workspace that is running outside

We're migrating from Eikon to LSEG Workspace. As a part of this process we need to rewrite our application that uses different APIs. We're going to use LSEG Data Library for Python. Do you have any recommendations on how we can run our Python scripts inside of the Docker container and connect to the LSEG Workspace that is running outside of that container?
Answers
-
Hello @avinash.sonde
There are multiple ports starting from 9000 which can possibly be used by the API to connect to Workspace. If you start your Docker application and map all these ports to the host, you should be able to run the app within docker.
For e.g:
docker run -it -p 9000-9100:9000-9100/tcp ...
0 -
I don't know which Docker image you are using and how you plan to run your scripts. You can take this as a starting point and implement the port mapping part into your command.
0 -
We’re using lseg-data python module from
.What is the difference between refinitiv-data-library and lseg-data?
They all have very similar description. What are the differences?
The main API page:
has a link to lseg-data. So I assume this is the latest and correct python package to use.I’ve checked this tutorial
and this sample config:
and they do not say anything where I can provide an address to LSEG Workspace.
- Use environment variables or a configuration file to pass the LSEG Workspace credentials and connection details to your Python script.
- In your Python script, use the LSEG Data Library for Python to connect to the LSEG Workspace and perform the necessary operations.
Could you provide the sample configuration?
0 -
I think the library is not designed to run in a docker container when using the desktop session.
There are two reasons.
- The library will find the TCP port used by the LSEG Workspace by reading the .portInUse file on the LSEG Workspace machine. This file is not available in the docker container.
- The Data API Proxy only supports the localhost connection. I am not sure if the container can access the localhost of the docker host machine. I tested with the host.docker.internal and it doesn't work
To use the library in the docker container, you need to use the platform.ldp session instead. This session will directly connect to the Data Platform session on Cloud.
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 中文论坛