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
  26. POWERCENTERHELP

Advanced Workflow Guide

Advanced Workflow Guide

Rules and Guidelines for Concurrent Workflows

Rules and Guidelines for Concurrent Workflows

Use the following rules and guidelines for concurrent workflows:
  • You cannot reference workflow run instances in parameter files. To use separate parameters for each instance, you must configure different parameter files.
  • If you use the same cache file name for more than one concurrent workflow instance, each workflow instance will be valid. However, sessions will fail if conflicts occur writing to the cache.
  • You can use
    pmcmd
    to restart concurrent workflows by run ID or instance name.
  • If you configure multiple instances of a workflow and you schedule the workflow, the Integration Service runs all instances at the scheduled time. You cannot run instances on separate schedules.
  • Configure a worklet to run concurrently on the worklet General tab.
  • You must enable a worklet to run concurrently if the parent workflow is enabled to run concurrently. Otherwise the workflow is invalid.
  • You can enable a worklet to run concurrently and place it in two non-concurrent workflows. The Integration Service can run the two worklets concurrently.
  • Two workflows enabled to run concurrently can run the same worklet. One workflow can run two instances of the same worklet if the worklet has no persisted variables.
  • A session in a worklet can run concurrently with a session in another worklet of the same instance name when the session does not contain persisted variables.
The following transformations have restrictions with concurrent workflows:
  • Aggregator transformation.
    You cannot use an incremental aggregation in a concurrent workflow. The session fails.
  • Lookup transformation
    . Use the following rules and guidelines for Lookup transformations in concurrent workflows:
    • You can use static or dynamic lookup cache with concurrent workflows.
    • When the cache is non-persistent, the Integration Service adds the workflow run ID as a prefix to the cache file name.
    • When the cache is an unnamed persistent cache, the Integration Service adds the run instance name as a prefix to the cache file name.
    • If the cache is a dynamic, unnamed, persistent cache and the current workflow is configured to allow concurrent runs with the same instance name, the session fails.
    • If the lookup cache name is parameterized, the Integration Service names the cache file with the parameter value. Pass a different file name for each run instance.
  • Sequence Generator transformation.
    To avoid generating the same set of sequence numbers for concurrent workflows, configure the number of cached values in the Sequence Generator transformation.


Updated July 04, 2018