Hello everyone - Can I have your comments on this issue please? I’m not a broker person - do forgive the newbie questions below.
I have a source Integration Server publishing documents to a broker. The document setting are: ‘Storage Type’ = ‘Guaranteed’ and ‘Discard’ = ‘False’. A trigger on a destination Integration Server subscribes to the published documents, and invokes a DB interface service to inject them to an external database. In summary, this is the setup:
Source IS -> Broker -> Destination IS -> External Database
What is the best approach to make this setup reliable in the face of system failure? For instance, if the external database does down, the trigger still subscribes to the document, but the DB interface service returns failure. Does the trigger notify the broker the document is still unprocessed, or is the document now irretrievably ‘gone’ from the broker?
If so, do we need to tweak the trigger’s ‘Max attempts’ and ‘Retry interval’ settings, or the DB interface service’s ‘Retry on IS Runtime Exception’ settings?
What happens if the Destination IS now also goes down - will the retries currently being processed be lost?
Someone mentioned the best approach for reliable delivery is to disable the subscribing trigger as soon as the service it invokes (in this case the DB interface service) starts failing. Is this correct?
Regards and Best Wishes for the New Year!