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

Recovery Queue and Recovery Topic

Recovery Queue and Recovery Topic

The Integration Service stores message IDs in a recovery queue or recovery topic for real-time sessions that are enabled for recovery and include the following source and target types:
  • JMS source with JMS or WebSphere MQ targets
  • WebSphere MQ source with JMS or WebSphere MQ targets
The Integration Service temporarily stores message IDs and commit numbers in a recovery queue or recovery topic that you created in the JMS provider or in WebSphere MQ. The commit number indicates the number of commits that the Integration Service committed to the target. During recovery, the Integration Service uses the commit number to determine if it wrote the same amount of messages to all targets. The messages IDs and commit numbers are verified against the recovery queue or recovery topic to ensure that no data is lost or duplicated.
The Integration Service uses the same recovery queue or recovery topic for all queue targets in each session. Create multiple recovery queues or recovery topics for sessions to improve performance.
If you do not specify the recovery queue or recovery topic name in the session properties or in the JMS connection object, the Integration Service stores recovery information in the recovery file. For optimal performance, configure the recovery queue or recovery topic name instead of the recovery file.

0 COMMENTS

We’d like to hear from you!