DSS Rest API and Azure

Hi, client mine wrote:
"We are experiencing performanceproblems in our testenvironment and therefore one of our application developers went through your document on REST-API and found a section with a recommendation NOT to use this in combination with Azure. We have plans to migrate our application using Azure during 2023."
Is this correct, is DSS REST API and Azure not a recommended combination?
Best Answer
-
Thanks for reaching out to us.
It is not a bug in the SDK. It is a limitation when using the SDK on Azure. You may contact the product team to enhance the SDK to run properly on Azure.
If the application runs less than 240 seconds, it should not be a problem.
Otherwise, you can try the following code to disable keep-alive.
public void ConnectToServer(string dssUserName, string dssUserPassword)
{
ExtractionsContext.SetRequestHeaders(() =>
{
return new Dictionary<string, string>{
{ "Connection", "close" }
};
});
extractionsContext = new ExtractionsContext(dssUri, dssUserName, dssUserPassword);
}The code sets the value of the "Connection" request header to "close" before creating the ExtractionsContext. I found this solution on StackOverflow.
I hope that this information is of help.
0
Answers
-
Further,
”Don’t use with Azure” comment in the document called “DataScope Select Best Practices & Fair Usage Policy” (from April 2023) here:
From the document:
"Do Not Use the SDK to Host Applications in Azure
We do not recommend using the DataScope Select SDK for applications hosted in Azure. Azure is not
tested with the DataScope Select SDK and therefore, not directly supported.The SDK uses the
regular.NET Framework class HttpClient with keep-alive enabled. The Azure Load Balancer may reuse
existing connection after some period of inactivity (240 seconds by default) and ignores the keep-alive
settings of an open connection. As a result, SDK clients who host their applications in Azure may
experience intermittent disconnects."
Client's questions regarding this are:
- Is this something that you plan to fix during 2023, so that the SDK will be supported for applications hosted in Azure?
- If we only use the connections for less than 240 seconds, can we ignore this issue? Our connections are usually only used for 10-20 seconds.
0 -
Hi @Jirapongse
Jupiter (Refinitiv Access) client is planning to use Azure for DSS API, please confirm if its recommended or not.
Also pls confirm the best authentication method to use when calling DSS from Azure
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 中文论坛