Table of Contents

Search

  1. Preface
  2. Understanding Pipeline Partitioning
  3. Partition Points
  4. Partition Types
  5. Pushdown Optimization
  6. Pushdown Optimization 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
  26. POWERCENTERHELP

Advanced Workflow Guide

Advanced Workflow Guide

Stopping Real-time Sessions

Stopping Real-time Sessions

A real-time session runs continuously unless it fails or you manually stop it. You can stop a session by issuing a stop command in
pmcmd
or from the Workflow Monitor. You might want to stop a session to perform routine maintenance.
When you stop a real-time session, the Integration Service processes messages in the pipeline based on the following real-time sources:
  • JMS and WebSphere MQ.
    The Integration Service processes messages it read up until you issued the stop. It writes messages to the targets.
  • MSMQ, SAP, TIBCO, webMethods, and web service messages.
    The Integration Service does not process messages if you stop a session before the Integration Service writes all messages to the target.
When you stop a real-time session with a JMS or a WebSphere MQ source, the Integration Service performs the following tasks:
  1. The Integration Service stops reading messages from the source.
    If you stop a real-time recovery session, the Integration Service stops reading from the source after it recovers all messages.
  2. The Integration Service processes messages in the pipeline and writes to the targets.
  3. The Integration Service sends an acknowledgement to the source.
  4. The Integration Service clears the recovery table or recovery file to avoid data duplication when you restart the session.
When you restart the session, the Integration Service starts reading from the source. It restores the session and transformation state of operation to resume the session from the point of interruption.
If the real-time session hangs after you stop it, the session might remain in a stopping state. You can abort the real-time session if it remains in stopping mode. The Integration Service processes the messages that it read before you issued the stop.


Updated July 04, 2018