How to send UUID using EMA for HMDS/RTO

Zeno

Hello,

We are working with multiple LSEG services and we are using EMA to manage them all.
We create multiple connections/sessions/OmmConsumers that connect to the same order of endpoints/Channels. We connect using an access token.

We were told that when connecting, we should send the UUID as well such that the routing for the multiple connections end up at the same ADS/their backend server.

But here is the questions as we were told multiple things from multiple directions.

We are sending the UUID as "setPosition" when creating the OmmConsumerConfig, and we send it in the format of "127.0.0.1/<UUID>", where "<UUID>" is the UUID which we take from a JWT when an access token is generated, but we were also told to send the UUID in "tunnelingObjectName", directly without any extra information.

Is that necessary/correct?

If it is, is it enough to only set tunnelingObjectName and position? How exactly should they be set for both properties, so that we know they are correctly sent and parsed?

Do we also have to set other properties alongside them?

Thanks

wasin.w V3

Hello @Zeno

It seems the HMDS has special requirements that the "normal" Real-Time Platform (RTDS and RTO) does not have. By default, the ADS server and RTO do not need the UUID.

• Deployed RTDS (ADS) requires DACS Username
• RTO requires Authentication Token ( AutnToken for RDP https://api.refinitiv.com:443/auth/oauth2/<version>/token access token)

The UUID is the information that the Authentication System (DACS or whatever system) gets and verifies under the hood after it received a DACS username or AuthnToken from the Real-Time Platform.

By default, the Position, together with ApplicationId, helps the upstream infrastructure component to identify the client connection.

Regarding the tunnelingObjectName, its purpose is as follows:

You can see that the interfaces do not mention anything about UUID because the "normal" Real-Time platform does not require UUID. We, Developer Relations team also does not have access to HMDS server, so we cannot answer this question.

I strongly suggest you try with your code to find which one give you the result you need.

If both of them do not work or you need more information about connecting to the HMDS, I strongly suggest you contact the Real-Time APIs Support Team (RDC) and HMDS Support team to work together.

• You can contact the Real-Time APIs Support team via the premium support.