This content has been marked as final. Show 2 replies
Resending was initially one of the prerequisites of the product. But the way we configured it in IC 9.0.2 didn't work as expected. We used a setup called messagewarehouse; copy all published messages to an Andvanced Queue.
The problem is that republishing the message uses the original CBR-options. And most of the republish events are used for a specific subscriber.
This method is now stopped
A new option that we will test after our migration to 10g is to setup a retentention per queue. Every Queue should be able to hold messages for a given time. It probably will affect performance.
We need to investigate this too. Hopefully others can give us comments about this option.
Almost forgot to mention!
In our current design of integrations we have a mechanism in the publish-application to be able to "synchronize", i.e. a function to send ALL (active) records.
In some cases it is also necessary for the first use.
Unfortunately not all integrations are fit for this option e.g. publishing transactions only and not end-states.