Table of Contents

Search

  1. Preface
  2. Understanding Pipeline Partitioning
  3. Partition Points
  4. Partition Types
  5. Pushdown Optimization
  6. Pushdown Optimization and Transformations
  7. Real-time Processing
  8. Commit Points
  9. Row Error Logging
  10. Workflow Recovery
  11. Stopping and Aborting
  12. Concurrent Workflows
  13. Grid Processing
  14. Load Balancer
  15. Workflow Variables
  16. Parameters and Variables in Sessions
  17. Parameter Files
  18. FastExport
  19. External Loading
  20. FTP
  21. Session Caches
  22. Incremental Aggregation
  23. Session Log Interface
  24. Understanding Buffer Memory
  25. High Precision Data

Advanced Workflow Guide

Advanced Workflow Guide

Message Recovery for SAP IDoc, TIBCO, and webMethods Sources

Message Recovery for SAP IDoc, TIBCO, and webMethods Sources

You can enable message recovery for sessions with SAP IDoc, TIBCO, and webMethods sources to recover messages that the Integration Service failed to process. The Integration Service can restore the state of operation from the point of interruption.
The Integration Service completes the following tasks to process messages using recovery files:
  1. The Integration Service reads a message from the source.
  2. The Integration Service writes the message to the recovery file.
  3. The Integration Service sends an acknowledgement to the source to confirm it read the message. The source deletes the message. The Integration Service repeats steps 1 through 3 until the flush latency is met.
  4. The Integration Service processes the messages and writes them to the target. The target commits the messages.
  5. The Integration Service clears the recovery file.
The following image shows how the Integration Service processes messages using the recovery file: The Integration Service reads a message from the source. Then, the Integration Service writes the message to the recovery file. The Integration Service sends an acknowledgement to the source to confirm it read the message. The source deletes the message. The Integration Service repeats steps 1 through 3 until the flush latency is met. The Integration Service processes the messages and writes them to the target. The target commits the messages. The Integration Service clears the recovery file.


Updated November 14, 2019