no connect Real-Time Managed Distribution

s61670

Please help.

There is a signed contract for Real-Time Managed Distribution Service

We were given an EaaS_SHD PDF document that has information on (Refinitiv Subscriber #; Destination IP Address; USER ID; Feed Service Names; SSL Port; RSSL Port)

From the Real-Time-SDK-2.0.3.L2.win library we took the code:

AppClient client;
        OmmConsumer consumer( OmmConsumerConfig().host( "localhost:14002" ).username( "user" ) );
        consumer.registerClient( ReqMsg().serviceName( "DIRECT_FEED" ).name( "IBM.N" ), client );
        sleep( 60000 );    

instead of localhost in various combinations substituted data from the document (Destination IP Address), where we substituted the username (USER ID), no connection.

Can you tell me, maybe the code is wrong? Or the data is not filled in correctly?

AppClient client;
        OmmConsumer consumer( OmmConsumerConfig().host( "10.***.***.**:14002" ).username( "EM1_****_*******" ) );
        consumer.registerClient( ReqMsg().serviceName( "hEDD" ).name( "IBM.N" ), client );
        sleep( 60000 );    

umer.nalla

Hi @s61670

Please use port 14002 - 8101 is for legacy SSL connection - RT-SDK does not support 8101

s61670

VPN connected (CiscoAnyConnect Security Mobility Client)

umer.nalla

Hi @s61670

You have not provided any information on what actually happens when you run the example.

Can you describe what actually happens when you run the example - log out + trace etc - so we can understand the situation?

You can enable trace by setting XmlTraceToStdout or XmlTraceToFile in the EMAConfig.xml which should be placed in the working directory. See the EMACPP_Configuide.pdf for more details.

s61670

the link does not open EMACPP_Configuide.pdf

umer.nalla

Hi @s61670

Sorry - that is not a link - bad formatting on the website.

The EMACPP_ConfigGuide.pdf is included with the RT-SDK package in the Cpp-c\EMA\Docs folder.

OR you can download from the following page:
RT-SDK C++ Documentation | Refinitiv Developers

umer.nalla

Hi @s61670

Please include any console or EMA log file output as well as any trace.

s61670

This is the error

s61670

Port 14002 was also used.

We tried different combinations, the result is the same, no connection.

umer.nalla

Hi @s61670

Is it the same error message for 14002?

I will have to raise a ticket with the RTMDS team - so they can investigate - as it does not sound like an API issue.

nick.zincone

Hi @s61670

Just to confirm, does the error output always say <ip>:8101 despite selecting a different port? That is, if you put in something like 10.10.10.10:14002 or 10.10.10.10:9999 the error output always states: 10.10.10.10:8101?

s61670

Additional information on errors:

    AppClient client;
    OmmConsumerConfig config("Path_To_EmaConfig.xml");
    OmmConsumer consumer(
        config.
        host("1**.***.***.**:14002").
        username("EM1_****_*******").
consumerName("Consumer_4"));
    consumer.registerClient(
        ReqMsg().
        serviceName("hEDD").
        name("IBM.N"), client);