RTSDK Interactive Provider vs NonInteractive Provider

scott.kong
scott.kong Newcomer
edited February 17 in TREP APIs

Hi, we'd like to write a data publisher to TREP using RTSDK. This publisher will receive streaming data, do some translation and then publish the data to TREP.

We started with using the NonInteractive Provider since we need this process to publish data whenever it receives it. But during testing, we can't see the data in TREP.

Then we were told that NonInteractive Provider is not supported and we need to use Interactive Provider. However as per our understanding, when using Interactive Provider, TREP needs to login to our process and make subscriptions, which doesn't seem to fit to our purpose.

Would anyone having some experience in using RTSDK to publish data could share anything useful please?

Thanks and regards

Scott

Tagged:

Answers

  • Gurpreet
    Gurpreet admin

    Hello @scott.kong

    The difference between Ni and Interactive provider is the location of the cache. Ni provider is simple and RTMDS components take care of managing downstream connections and fanning out data. In case of interactive provider, this work has to be done in the application code, which is also responsible for receiving and disconnecting applications.

    Why is NiP not supported? The tutorials and the example apps which come with the RTSDK are the best starting point.

  • Jirapongse
    Jirapongse ✭✭✭✭✭

    @scott.kong

    You need to configured RTDS to support the Non-Interactive provider. Please contact the RTDS support team directly via MyAccount regarding the configurations.

    Then, you need to use the ADH or ADS monitor tool to verify if the published service is up.

  • scott.kong
    scott.kong Newcomer

    Thanks all for the hints!

Categories