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

Configuring Concurrent Workflows of the Same Name

Configuring Concurrent Workflows of the Same Name

You can enable a workflow to run concurrently without defining unique instance names. You can run more than one instance of the same workflow name. The PowerCenter Integration Service distinguishes between each workflow instance by a run identifier number, or run ID. Each workflow run has a unique run ID. ThePowerCenter Integration Service appends the run ID to the workflow and session log names, recovery file names, and other temporary file names to create separate files for each workflow.
Run concurrent workflows with the same instance name when the workflows read from a real-time source, such as a message queue or web service. For example, you manage data from multiple project teams. Create a workflow that reads data from a message queue that determines the source data and targets. You can run the instance multiple times concurrently and pass different connection parameters to the workflow instances from the message queue.


Updated June 03, 2019