LD Library Configurations

BryanAlvin.Buenaventura

Hi Team, we received a query related to python set up and he wanted to have a training on how to navigate in dept the python program.

So far what we have done are the following:

1. I've provided the link for the configuration process: LSEG's Refinitiv Data Library for Python and its Configuration Process | Devportal along with the file itself Example.DataLibrary.Python/Configuration/lseg-data.config.json at lseg-data-examples · LSEG-API-Sam….
   
   2. Client also added follow-ups 
   
   what should i fill here. our LSEG username and password for desktop apllication.? "username": "YOUR LDP LOGIN OR MACHINE GOES HERE!", "password": "YOUR LDP PASSWORD GOES HERE!"
   
         Provided to the client: 
   1. As stated within the "Configuration file" section: You need to enter this information, namely : your    App Key (which is necessary) your Login Username (which is not necessary) your Password (which is not   necessary) Then circling back to your question, the username and password is your LSEG Workspace   username and password as well.
   
   
   3. Client has further questions about the script showing: "YOUR DEPLOYED HOST:PORT GOES HERE!".
   
   
   Client is requesting for a remote session to help with the configuration installment. Would anyone be able to join?

Client's preferred time for meeting: Time preference is 10am to 12noon Atlantic standard time . OR 2pm to 4pm

Jirapongse

@BryanAlvin.Buenaventura

Thank you for reaching out to us.

The LSEG Data Library for Python can connect to three platforms (Desktop, RDP, and RTDS) depending on the sessions.default configuration.

1. Desktop (desktop.workspace) session requires the following configurations.

       "desktop": {

            "workspace": {
  "app-key": "YOUR APP KEY GOES HERE!"

            }

2. RDP (platform.ldp) session requires the following configurations.

 "platform": {

            "ldp": {
"app-key": "YOUR APP KEY GOES HERE!",

                "username": "YOUR LDP LOGIN OR MACHINE GOES HERE!",

                "password": "YOUR LDP PASSWORD GOES HERE!"

            },

3. RTDS (platform.deployed) session requires the following configurations.

"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" : ""

                    }

                }

            }

In this case, I assume that the client is a Workspace user so the client needs to use the desktop.workspace session.

First, set the default session to "desktop.workspace".

    "sessions": {

        "default": "desktop.workspace",

Then, set an application key in the app-key setting.

        "desktop": {

            "workspace": {

                "app-key": "YOUR APP KEY GOES HERE!"

            }

The client can use the App Key Generate tool in Workspace to generate application keys.

The client needs to run the code on the same machine as the Workspace application and can refer to the Eikon Data API and Refinitiv Data Library - Troubleshooting article to verify the connection problem.

To set up a call, please reach out to the client’s account team or sales team to confirm whether the call is necessary. We offer numerous examples, tutorials, articles, and use cases. These resources should be sufficient for users to begin using the LSEG Data Library for Python. Moreover, the client can post questions directly on this forum to receive prompt responses.