TM Forum Community

 View Only
  • 1.  Listener and hub Queries

    Posted May 16, 2022 09:19
      |   view attached
    I am pretty new with the TMF 641 APIs.I follow the tmf swagger.

    1 - What is the difference between listener api and hub api.
    2- Does the id present in response of listener is same as hub api response id.

    I attached the response.


    Shivam Chauhan

  • 2.  RE: Listener and hub Queries

    TM Forum Member
    Posted May 17, 2022 01:44
    Hi Shivan,
    the listener is a service (Observer in GoF pattern) provided  by another system to be notified by the SOM service. It is registered at the hub (Observable) to be invoked when a notification is due. The id is the id that the hub assigns to the listener and which can be used e.g. to de-register the listener later.


    Andreas Schlueter

  • 3.  RE: Listener and hub Queries

    TM Forum Member
    Posted May 17, 2022 03:26
    Thanks Andreas for your answer. I'll provide some additional info:
    The Open API design pattern prescribes events that are raised as part of an API implementation, typically as a result of operation invocation (e.g. entityxxxxcreated, entityyyyystatuschanged, etc.). We have two paradigms for handling these events:
    • hub and listener - This is a point-to-point paradigm. The software system that raises events (typically an implementation of an API) publishes a hub end-point. Software systems that want to subscribe to the events register at the hub, giving a callback endpoint as part of the registration. The event raising software system will invoke each callback endpoint to communicate the events to the subscribing systems.
    • event queue - This is a distributed paradigm. TMF688 (event management) allows event providers to raise events, and event consumers to subscribe to events, wrapping queue or messaging systems (Kafka, Rabbit, etc.)
    Hope it helps

    Jonathan Goldberg
    Amdocs Management Limited
    Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.