LSEG Real-Time SDK Proxy Settings
We have been trying to get real time market feed through the following tutorials:
Download Center > Product Family > mds api > LSEG Real-Time SDK
and using the following JAVA example codes
Since we are under an organization, a proxy setting is required for outside connections. So we went through the example code and found that there is an option to configure proxy.
Under ConsumerRto class > main() , there an options.proxy() method is available but we do not know how to configure it properly. Is this the correct way to configure proxy? Can somebody guide us through this? Could you give us an example of how to configure proxy?
Best Answer
-
Hello @terapon1
According to the EMA Java reference guide (available in the SDK package or download here), the proxy relate properties of the ServiceEndpointDiscoveryOption class is as follows:
- proxyHostName:Specifies the address or hostname of the HTTP proxy server
- proxyPort: Specifies the port number of the HTTP proxy server
- proxyUserName: Specifies the proxy user name to authenticate.
- proxyPassword: Specifies the proxy password to authenticate.
The properties functions are already described by its name.
Example: If your environment proxy is
- corporate-proxy.example.com:8080
- Proxy username: admin
- Proxy password: proxy_password1234
That means:
- Your proxy hostname is corporate-proxy.example.com
- Your proxy port is 8080
- Your proxy username is admin
- Your proxy password is proxy_password1234
I hope this information helps.
1
Answers
-
hi @wasin.w
I would like to ask further about proxy settings. In the LSEG real-time SDK example, there is another proxy settings near the end of the code. It is part of the OmmConsumerConfig Class.
Apart from the proxy settings at the beginning of the code (ServiceEndpointDiscoveryOption Class). Do I have to configure the proxy at the OmmConsumerConfig Class as well? Why is it necessary to configure proxy 2 times? I was able to get pass the ServiceEndpointDiscoveryOption part but now stuck at the OmmConsumerConfig part. Any recommendations?
Thanks in advance.
0 -
Hello @terapon1
This is the information of those OmmConsumerConfig methods on the EMA Reference Guide document (available in the SDK package).
If your environment has proxy/firewall for the HTTP operations, an application needs to set the REST Proxy information because the API needs to connect to the https://api.refinitiv.com REST API endpoint for authentication.
0 -
I have set the necessary configurations. The program returns me this specific message that loops every 5 seconds. This means the connection is unsuccessful? Or perhaps the configuration is incorrect?
0 -
Hello @terapon1
The error message indicates that the API cannot connect to the ADS server via the RSSL connection. An application may need to set the proxy information (hostname, port, username, and password) for the RSSL connection as well (the RTO connection = HTTP REST + RSSL connection).
I checked on the EMA Java ex450 example, the example code when setting the proxy with the RSSL connection is as follows:
consumer = EmaFactory.createOmmConsumer(config.consumerName("Consumer_1").clientId(clientId).clientSecret(clientSecret).config(configDb) .tunnelingProxyHostName(proxyHostName).tunnelingProxyPort(proxyPort) .tunnelingCredentialUserName(proxyUserName).tunnelingCredentialPasswd(proxyPassword).tunnelingCredentialDomain(proxyDomain) .tunnelingCredentialKRB5ConfigFile(proxyKrb5Configfile));
Could you please try to set the tunnelingProxyHostname(), tunnelingProxyPort(), tuennelingCredentialUsername(), and tunnelingCredentialPassword() configurations?
Example:
consumer = EmaFactory.createOmmConsumer(config.consumerName("Consumer_1").clientId(clientId).clientSecret(clientSecret).config(configDb) .tunnelingProxyHostName("corporate-proxy.example.com").tunnelingProxyPort("8080") .tunnelingCredentialUserName("admin").tunnelingCredentialPasswd("proxy_password1234");
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
- 685 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 252 ETA
- 556 WebSocket API
- 38 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 652 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
- 104 UPA
- 193 TREP Infrastructure
- 228 TRKD
- 917 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛