Table of Contents

Search

  1. Preface
  2. Introduction to Transformations
  3. Transformation Ports
  4. Transformation Caches
  5. Address Validator Transformation
  6. Aggregator Transformation
  7. Association Transformation
  8. Bad Record Exception Transformation
  9. Case Converter Transformation
  10. Classifier Transformation
  11. Comparison Transformation
  12. Consolidation Transformation
  13. Data Masking Transformation
  14. Data Processor Transformation
  15. Decision Transformation
  16. Duplicate Record Exception Transformation
  17. Expression Transformation
  18. Filter Transformation
  19. Hierarchical to Relational Transformation
  20. Java Transformation
  21. Java Transformation API Reference
  22. Java Expressions
  23. Joiner Transformation
  24. Key Generator Transformation
  25. Labeler Transformation
  26. Lookup Transformation
  27. Lookup Caches
  28. Dynamic Lookup Cache
  29. Match Transformation
  30. Match Transformations in Field Analysis
  31. Match Transformations in Identity Analysis
  32. Normalizer Transformation
  33. Merge Transformation
  34. Parser Transformation
  35. Python Transformation
  36. Rank Transformation
  37. Read Transformation
  38. Relational to Hierarchical Transformation
  39. REST Web Service Consumer Transformation
  40. Router Transformation
  41. Sequence Generator Transformation
  42. Sorter Transformation
  43. SQL Transformation
  44. Standardizer Transformation
  45. Union Transformation
  46. Update Strategy Transformation
  47. Web Service Consumer Transformation
  48. Parsing Web Service SOAP Messages
  49. Generating Web Service SOAP Messages
  50. Weighted Average Transformation
  51. Window Transformation
  52. Write Transformation
  53. Appendix A: Transformation Delimiters

Developer Transformation Guide

Developer Transformation Guide

Execution Instances

Execution Instances

Specifies the number of threads that the Data Integration Service tries to create for the current transformation at run time. The Data Integration Service considers the Execution Instances value if you override the Maximum Parallelism run-time property on the mapping that contains the transformation. The default Execution Instances value is 1.
The Data Integration Service considers multiple factors to determine the number of threads to assign to the transformation. The principal factors are the Execution Instances value and the values on the mapping and on the associated application services in the domain.
The Data Integration Service reads the following values when it calculates the number of threads to use for the transformation:
  • The
    Maximum Parallelism
    value on the Data Integration Service. Default is 1.
  • Any
    Maximum Parallelism
    value that you set at the mapping level. Default is Auto.
  • The
    Execution Instances
    value on the transformation. Default is 1.
If you override the Maximum Parallelism value at the mapping level, the Data Integration Service attempts to use the lowest value across the properties to determine the number of threads.
If you use the default Maximum Parallelism value at the mapping level, the Data Integration Service ignores the Execution Instances value.
The Data Integration Service also considers the
Max Address Object Count
property on the Content Management Service when it calculates the number of threads to create. The
Max Address Object Count
property determines the maximum number of address validation instances that can run concurrently in a mapping. The
Max Address Object Count
property value must be greater than or equal to the
Maximum Parallelism
value on the Data Integration Service.

Rules and Guidelines for the Execution Instances Property

Consider the following rules and guidelines when you set the number of execution instances:
  • Multiple users might run concurrent mappings on a Data Integration Service. To calculate the correct number of threads, divide the number of central processing units that the service can access by the number of concurrent mappings.
  • In PowerCenter, the
    AD50.cfg
    configuration file specifies the maximum number of address validation instances that can run concurrently in a mapping.
  • When you use the default Execution Instances value and the default Maximum Parallelism values, the transformation operations are not partitionable.
  • When you set an Execution Instances value greater than 1, you change the Address Validator transformation from a passive transformation to an active transformation.

0 COMMENTS

We’d like to hear from you!