Failure recovery for service calls

To avoid sending duplicate events to the destination application, you may want to prevent a recovery from automatically resubmitting all service calls that were in transit when a failure occurred. Before the server failure, you can configure a nontransactional collaboration to persist any service call event in the In-Transit state when a failure and recovery occurs. When InterChange Server Express recovers, the service call events remain in the In-Transit state, and you can use Flow Manager or Failed Event Manager to examine individual failed events and control when (or if) they are resubmitted.

To configure a collaboration to persist a failed service call in-Transit state, go to System Manager and select the Persist Service Call In Transit State check box in the Collaboration General Properties window.

Note:
If the collaboration is part of a collaboration group, setting this property implicitly applies the same property setting to all other collaborations in the group. Do not set one collaboration for Persist Service Call In Transit State unless you want all other collaborations in that collaboration group to have that setting as well. For transactional collaborations, it is recommended that you not set this property; clear the Persist Call In Transit State check box.

Copyright IBM Corp. 2004