Page History

...

1. CM Notification Forwarding Check: When forwarding CM Notification NCMP will not check the content to see if the is a valid active subscription. It is assumed that the DMI Plugin as acted on the 'delete subscription' request (that request is NCMPs responsibility). And of course there wil be timing issues it also possible a CM Notification was send just after the subscription-delete was send (from client) but before the whole change had acted upon that. 
2. Retry: NCMP wil only report will only report when actions are pending or rejected. NCMP will not implement a retry mechanism
3. Wildcards: Wildcards or similar functionality where one string represent 0 or more xpaths is not covered as part of this requirement but it should be kept in mind as a future possibility
4. Dynamic Topic: Topic for CM Data Notifications back to client will be hardcode for now. 
   Study shoudl consider compatibility with an 'ALL' cm handles options

...

• We have the below configuration managed by CPS-NCMP
  
  

  #	cmhandle	dmi-plugin
  1	ch-1	dmi-1
  2	ch-2	dmi-1
  3	ch-3	dmi-2

  
  

1. We get a Subscription Create Request with unique subscription-id and a list of predicates(list of targets , datastore and list of filters)
   
   

   Code Block
   title Subscription Create Request
   { "subscriptionId" : "A-10", "predicates" : [ { "targets": [ch-1,ch-2], "datastore" : "ncmp-datastore:passthrough-operational", "datastore-xpath-filter" : ["p1/c1","p2/c2"] }, { "targets": [ch-3], "datastore" : "ncmp-datastore:passthrough-operational", "datastore-xpath-filter" : ["p3/c3"] } ] }

   
   
   

2. We persist the incoming request as is in our persistent store using a relevant subscription model ( this model also needs to be revised )

3. We also maintain a distributed datastructure in Hazelcast to keep track of the request and response to the client.
   
   

   SubscriptionId	dmi-plugin	affectedCmHandles	status
   A-10	dmi-1	["ch-1","ch-2"]	PENDING
   A-10	dmi-2	["ch-3"]	PENDING

   
   

   
   

4. Read the requests from the distributed data structure and form the request for the DMI-Plugin and publish it to the internal kafka channel.
5. If the DMI-Plugin responds back within the configured time , so the request will either be ACCEPTED or REJECTED.
   1. if whole subscription request is ACCEPTED , update the distributed data structure and then store the subscription to the ActiveSubscriptions in cps-cache.
   2. if whole subscription request is REJECTED , update the distributed data structure and send back the response to the client.

   3. if the DMI Plugin fails to respond then the status would remain PENDING only as there is no change.
      
      
      

      SubscriptionId	dmi-plugin	affectedCmHandles	status
      A-10	dmi-1	["ch-1","ch-2"]	ACCEPTED
      A-10	dmi-2	["ch-3"]	REJECTED

      
      
      

6. We store the "ActiveSubscriptions" using a new model which will look like below.
   
   

   SubscriptionId	cmHandle	filter
   A-10	ch-1	p1/c1
   A-10	ch-1	p2/c2
   A-10	ch-2	p1/c1
   A-10	ch-2	p2/c2

   
   
   

7. Now based on whatever we have in the distributed map , we will send the response to the clients and may be clear the in-memory structure if required.
   
   

Proposed JIRAs

...