API Credentials

Hi
I have to use Elektron Java API. Are the credentials for using Websocket API and Java API same?
I have Machine id,Machine password, position and client id for Websocket API but for Java API I require host name,service name and user name.
Thanks
Best Answer
-
Hi @dhruv.arora
Since you have been provided with a MachineID, this would suggest that the ERT in Cloud is the be data delivery mechanism you should be using.
If you had a TREP server available to you, you would have been provided with a hostname + username by your Market Data team or your Refinitiv Account team.
If you would like further information on System Architecture, how the APIs work and other concepts, I recommend you read the API_ConceptsGuide.pdf which can be found in the Java\Ema\Docs folder of the ElektronSDK which you downloaded previously.
0
Answers
-
Hi @dhruv.arora
The credentials/login parameters you require will be determined by the connection endpoint e.g. if you are connecting to say an onsite TREP/ADS server you require the hostname and username - if you are connecting to ERT in Cloud, then you use the MachineID, Machine Password etc - regardless of if you are using WebSocket API or Elektron SDK Java API.
For using your MachineID etc with Elektron Java API please refer to the Elektron Message API or Elektron Transport API QuickStart for ERT in Cloud type connection.
You will note that both these two QuickStarts both required MachineID, Password and ClientID as parameters.
0 -
Hi @dhruv.arora, Please see this QuickStart guide to get you started. There is a separate section for connection to ERT Cloud vs TREP. The credentials you need will depend on which endpoint you are trying to connect to.
For the local TREP connection, you can use your existing DACS login/application ID etc for using websocket API. For connection to ERT Cloud infrastructure, you will need a new set of credentials, which are different from your local TREP creds. Please talk to your Refinitiv account manager on how you can get a trial account.
0 -
Hi Umer, I have created the keystore file using keytool. Can you please let me know, which examples should i look into , where I can use machineid/userid, password and keystore file ? I downloaded Elektron SDK - Java - 1.5.0.L1 and in directory, java examples are given which ask for host name, username and service name. Can you please point me towards examples where I can use Machineid, password,clientid and keystore file ?
0 -
Umer Nalla I have created the keystore file using keytool. Can you please let me know, which examples should i look into , where I can use machineid/userid, password and keystore file ? I downloaded Elektron SDK - Java - 1.5.0.L1 and in directory, java examples are given which ask for host name, username and service name. Can you please point me towards examples where I can use Machineid, password,clientid and keystore file ?
0 -
Hi @dhruv.arora
Excellent - so once you created the Keystore file, did you actually run through the Build and run an ERT in Cloud example step and successfully consume some data?
You will note that the EMA Quickstart uses the EMA consumer example 450 and the ETA QuickStart uses ETA example VAConsumer.
In addition to the above two examples, EMA also has example 113 which also allows an ERT in Cloud connection using MachineID etc.
If you need further assistance, please advise which Elektron SDK API you are using - EMA or ETA - so we can be more specific rather than providing general assistance for both APIs?
0 -
I am using EMA. I understand that EMA is high level API and ETA is low level API. We want to consume real time data. I could see, you mentioned of TREP/ADS server , which requires host name and service name. Can you please guide me, which one should be used ERT or TREP? And how are they different ?
Thanks , Dhruv
0
Categories
- All Categories
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 33 Data Model Discovery
- 682 Datastream
- 1.4K DSS
- 613 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
- 248 ETA
- 552 WebSocket API
- 37 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
- 2 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.8K Refinitiv Data Platform
- 622 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
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 191 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 84 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛