trna via elektron on DACS

i have a client in Abu dhabi (ADIA) who have subscribed to TRNA via Elektron SAAs and also have DACS at their premises. The client is a little lost on how he can start using the data after the DACS id has been created by the client admin. Can someone please help?
Best Answer
-
Hello @Rishabh.Maheshwary1
What is the API that the client currently using?
OMM
The Open Message Model (OMM) is a collection of message header and data constructs that running in Elektron/TREP infrastructure. If the client connects to Elektron via RSSL connection, the client is already using OMM interface.
Application ID and Position
Application ID: The DACS application ID. If the server authenticates with DACS, the consumer application might need to pass in a valid ApplicationId. This must be unique for each application. IDs from 1 to 256 are reserved for permanent market data applications. These are assigned by Refinitiv and will be uniform across all client systems. IDs from 257 to 65535 are available for site-specific use.
- Datatype: ASCII
- Range: 1-65535
- Example Value: 256
Position: DACS position. If the server is authenticating with DACS, the consumer application might need to pass in a valid position which is an IP Address of the consumer machine in "IP Address/Hostname" or "IP Address/net" string format.
- Datatype: ASCII
- Format: IP Address/hostname or IP Address/net
- Example: 192.168.1.1/net
0
Answers
-
Hello @Rishabh.Maheshwary1
To consume news e.g. TRNA, the client can start with one of the following tutorials
- EMA Consumer - Request & Decode Machine Readable News(EMA C++)
- ETA Consumer - Request and Decode Machine Readable News(ETA C)
- EMA Consumer - Request & Decode Machine Readable News(EMA Java)
- ETA Tutorial 6 - Request & Decode Machine Readable News(ETA Java)
0 -
You can also refer to the MACHINE READABLE NEWS OVER ELEKTRON - INTRODUCTION FOR DEVELOPERS video.
0 -
Hello @Rishabh.Maheshwary1
Please note that once you have setup DACS permission on your site, you need pass three parameters with the OMM Login request message to login.
- Application ID
- Position
- Username (DACS ID)
You can find more detail in this [EMA C++] State: Closed / Suspect / Not entitled / 'A21: A required argument was NULL question (It can be applied to any Elektron SDK APIs).
0 -
@wasin.w could you please describe what OMM is? Also, could you tell me what the Application ID and Position would mean. Sorry if i sound super naive on this.
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
- 687 Datastream
- 1.4K DSS
- 622 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
- 255 ETA
- 557 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
- 276 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
- 678 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
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 91 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛