Hello @Rishabh.Maheshwary

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

Hello @Rishabh.Maheshwary

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)

@Rishabh.Maheshwary

You can also refer to the MACHINE READABLE NEWS OVER ELEKTRON - INTRODUCTION FOR DEVELOPERS video.

Hello @Rishabh.Maheshwary

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).