Any way to configure ns not to run again to avaoid dupes
we received duplicate notifications not because of maching rules but because
The Ns started events generation. But it was stopped before the
notifications are generated. Again It was restarted resulting NS to generate
events again.Now It has processed all the events resulting in duplicates.
Can any one help me how I can go about it.
The best solution appears to me is to use unique key( natural key) on events
chronicle. But that is not acceptable to client for valid reasons.
I am told that there is a configuration setting in ADF to prevent ns to
produce events till notifications are generated.
Thanks in advance.
--Knowledge gets doubled when shared