Discover Refinitiv
MyRefinitiv Refinitiv Perspectives Careers
Created with Sketch.
All APIs Questions & Answers  Register |  Login
Ask a question
  • Questions
  • Tags
  • Badges
  • Unanswered
Search:
  • Home /
  • TREP APIs /
  • RFA /
avatar image
Question by rvaratharajan · Dec 07, 2017 at 05:14 PM · rfanipposting

Difference between NIP and Posting

Can someone advise what are the differences between Non-interactive Publisher and Consumer Posting ?

I see both can contribute the data to TREP

People who like this

0 Show 0
Comment
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Reply

  • Sort: 
avatar image
REFINITIV
Best Answer
Answer by jirapongse.phuriphanvichai · Dec 12, 2017 at 03:33 AM

Yes, both can contribute the data to TREP.

1. Posting is used by consumers to push content into any cache within the TREP. Consumers connect to ADS and then use OMM post messages to post the content. The posting capability offers optional acknowledgments per posted message. The two types of posting are:

  • On-Stream Post: Before a client application can send an On-Stream Post, the client must first open (request) a data stream for an item. After the data stream is opened, the client application can then send a post. The route of the post is determined by the route of the data stream.
  • Off-Stream Post: In an Off-Stream Post, the client application can send a post for an item via a login stream, regardless of whether a data stream first exists. The route of the post is determined by the configuration of the TREP.

Moreover, posting also supports OMM-Based Contributions. Through such posting, clients can contribute data to a device on the head-end or a custom-provider. In the following example, the OMM consumer sends an OMM post to the ATS Application or Elektron. The traffic of posting flows from bottom to top.

2. Non-Interactive Provider is a broadcast-publishing type of provider. Its main purpose is to make their services available to consumers through TREP infrastructure components. Typically, Non-Interactive Providers connect to ADH in order to publish the data. After it connects to TREP, it will start sending information for any supported item and domain. The main benefit of this scenario is that all publishing traffic flows from top to bottom: the way a system normally expects updating data to flow.

Comment

People who like this

0 Show 1 · Share
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

avatar image
daniel.wray · Jul 14, 2020 at 12:04 PM 0
Share

Am I right in surmising that posting can only add / edit RICs on an existing service (cache) with its own provider, while setting up your own provider allows (requires?) the creation of a dedicated service?

EG, I can use posting to add internal RICs to my existing ELEKTRON_DD service, but if I want to have a dedicated internal service, I need to set up a provider and configure ADH to source a separate service from that?

Watch this question

Add to watch list
Add to your watch list to receive emailed updates for this question. Too many emails? Change your settings >
10 People are following this question.

Related Questions

migration MarketDataItemCont.setBuffer -> OMM Post

Activate full message logs for RSSL connections in RFA C++

Requesting bid price at snap times via RFA

Specific FID in Responses

RWF version discrepancy and how RFA handles it

  • Feedback
  • Copyright
  • Cookie Policy
  • Privacy Statement
  • Terms of Use
  • Careers
  • Anonymous
  • Sign in
  • Create
  • Ask a question
  • Spaces
  • Alpha
  • App Studio
  • Block Chain
  • Bot Platform
  • Calais
  • Connected Risk APIs
  • DSS
  • Data Fusion
  • Data Model Discovery
  • Datastream
  • Eikon COM
  • Eikon Data APIs
  • Elektron
    • EMA
    • ETA
    • WebSocket API
  • Legal One
  • Messenger Bot
  • Messenger Side by Side
  • ONESOURCE
    • Indirect Tax
  • Open PermID
    • Entity Search
  • Org ID
  • PAM
    • PAM - Logging
  • ProView
  • ProView Internal
  • Product Insight
  • Project Tracking
  • Refinitiv Data Platform
    • Refinitiv Data Platform Libraries
  • Rose's Space
  • Screening
    • Qual-ID API
    • Screening Deployed
    • Screening Online
    • World-Check One
    • World-Check One Zero Footprint
  • Side by Side Integration API
  • TR Knowledge Graph
  • TREP APIs
    • CAT
    • DACS Station
    • Open DACS
    • RFA
    • UPA
  • TREP Infrastructure
  • TRIT
  • TRKD
  • TRTH
  • Thomson One Smart
  • Transactions
    • REDI API
  • Velocity Analytics
  • Wealth Management Web Services
  • World-Check Data File
  • Explore
  • Tags
  • Questions
  • Badges