RWF data via HMDS WebSocket API

Options
rares_patacean
rares_patacean LSEG
edited May 30 in WebSocket API

Hi Team,

Currently in the WebSocket API documentation, the protocol mentioned is only tr_json2.

Is there any possibility to use RWF via HMDS WebSockets? This will ensure a better transport rate and maybe also a lower load on the backend ADSs.

Thank you,
Rares

Tagged:

Answers

  • Gurpreet
    Gurpreet admin

    @rares_patacean

    Why not use the RSSL/OMM for connecting to HMDS? EMA API is quite easy to use - see the SDK and the examples here.

  • rares_patacean
    rares_patacean LSEG

    The authentication model we use with HMDS is token based "AuthnToken", does EMA API support this type of authentication?

  • Gurpreet
    Gurpreet admin
    https://community.developers.refinitiv.com/discussion/comment/126058#Comment_126058

    https://github.com/Refinitiv/Real-Time-SDK/tree/825c4c2113da5389d5f927cfbcadd7c2be495b18/Java/Ema/Examples/src/main/java/com/refinitiv/ema/examples/training/consumer/series400/ex430_MP_Authentication

  • rares_patacean
    rares_patacean LSEG

    @Gurpreet , I've had couple of tries but it seems that a HMDS endpoint, such as: wss://emea1-ws-fo-hmds.ppe.platform.refinitiv.com:443/WebSocket, that includes the path does not work fine.

    When I set for Consumer host the value: emea1-ws-fo-hmds.ppe.platform.refinitiv.com/WebSocket, I get:

    2025-07-18 17:20:13.306 WARNING com.refinitiv.ema.access.ChannelCallbackClient reactorChannelEventCallbackloggerMsgClientName: ChannelCallbackClientSeverity: WarningText: Received ChannelDownReconnecting event on channel Channel_1RsslReactor Channel is nullError Id 0Internal sysError 0Error Location Reactor.processWorkerEventError text Reconnection failed: java.nio.channels.UnresolvedAddressExceptionloggerMsgEnd

    If I don't use the path Websocket the socket can't be established. I think using the specified path is a constraint from HMDS Platform.

    Can you please advise?

    In our WebSocket implementation with HMDS, would it be possible to use the RWF encoding of JSON messages, if we specify the rssl.rwf for Websocket Protocols, thus leveraging the RWF benefits?

    Thanks,

    Rares

Categories