RTO - Service Discovery via Delivery Direct

Paolo Parlapiano
Paolo Parlapiano Contributor
in EMA

Hi LSEG,

in a client environment it is required to connect a EMA based application to RTO via Delivery Direct.

As a temporary solution to test a successful connection, the EMA application was using hardcoded values for host and port (EmaConfig-host-port.xml inside the attached zip). Thought not optimal, this configuration was working fine.

To enable Service Discovery, the configuration has been changed to use Location instead (EmaConfig-location.xml inside the attached zip).

However, after the change, the application is no longer able to connect to RTO.

From the logs, we can see that the application now tries to connect to refinitiv.com instead of refinitiv.biz.

*   Trying 75.2.0.254:443...
* connect to 75.2.0.254 port 443 from 0.0.0.0 port 53137 failed: Timed out
*   Trying 99.83.242.11:443...
* connect to 99.83.242.11 port 443 from 0.0.0.0 port 53143 failed: Timed out
* Failed to connect to api.refinitiv.com port 443 after 42082 ms: Couldn't connect to server
* Closing connection

From the "The Real-Time - Optimized Install and Config Guide", we understand that to use .biz endpoints, Service Discovery bypass should be used, but we're not sure to be in the right direction.

Could you please help us clarifying how the configuration should be changed to achieve this?

Thanks,

Paolo

EmaConfig.zip

Tagged:

Best Answer

  • Jirapongse
    Jirapongse ✭✭✭✭✭
    Answer ✓

    @Paolo Parlapiano

    Thank you for reaching out to us.

    Did you chage the tokenServiceUrlV2 and serviceDiscoveryUrl in OmmConsumerConfig to refinitiv.biz?

    1728386511324.png

    You may verify the connected server from the REST log.

Answers

Categories