...
- We receive an event of type : subscriptionDeleted from the client ( EDM DME ) containing the subscription clientId and subscription name along with datastore and dataCategory details ( Delete Subscription CM Event DMEtoNCMP )
- We check in NCMP that we have an ongoing subscription using clientId and subscriptionName.
- If we have ongoing subscription , we forward the event to dmi-plugins so that the changes are applied in the devices managed by dmi-plugin as well. ( Delete Subscription CM Event )
- Now if the dmi-plugins have applied the request then we get an event back from dmi-plugin and NCMP will process that event and based on that it will delete the ongoing subscription request from the database itself. If the response from DMI plugins is accepted ( i.e it can delete the subscriptions from the underlying devices and no subscription delete request are in PENDING or REJECTED state )Then we delete the subscriptions from the DB as well. ( Delete Subscription CM Event )
- After processing the received event from DMI , NCMP will send the final event to the client (EDMDME). ( Delete Subscription CM Event )
Subscription Delete Sequence Diagram
...
DME to NCMP
Subscription Delete Event
...