Specifying the Duplicate Key
Duplicate detection is only as efficient as the duplicateKey
that is specified. You should try to pick a value that is unique for every message. For example, you may select the JMSMessageID header property for JMS messages. In the example in the previous section, orderID
is unique for each incoming order, so that would be a good choice for the value of the duplicateKey
.
The following illustrates specifying orderID
from the example above as the duplicateKey
value in the Checkpoint activity.