Content Comparison

...

{
   "clientId":"SCO-9989752",
   "subscriptionName":"cm-subscription-001",
   "dmiName":"ncmpDmiPlugin",
   "cmHandleIdToStatus":{
      "CmHandle1":"accepted",
      "CmHandle2":"declined"
   }
}

Notes

TBU...

1. dmiName in Output Schema is populated from application.yml of DMI-plugin.
2. DMI-plugin subscribes to the topic to consume Input Schema given in application.yml of DMI-plugin.

	dmi:
		service:
			name: ${DMI_SERVICE_NAME:ncmp-dmi-plugin}
	app:
		dmi:
			avc:
				subscription-topic: ${DMI_CM_AVC_SUBSCRIPTION:ncmp-dmi-cm-avc-subscription-${dmi.service.name}}

NCMP to Client-Apps

Proposed outcome (Schema 5)

...

// Any logic if we want to discuss and make decision

Implementation proposal of DMI Response Timeout

Given that a Subscription Create Event has been received by the NCMP and that NCMP is going to forward that subscription to multiple DMI Plugins.

1. The NCMP with create a new thread