Table of Contents

Search

  1. Preface
  2. Introduction to Informatica Data Engineering Integration
  3. Mappings
  4. Mapping Optimization
  5. Sources
  6. Targets
  7. Transformations
  8. Python Transformation
  9. Data Preview
  10. Cluster Workflows
  11. Profiles
  12. Monitoring
  13. Hierarchical Data Processing
  14. Hierarchical Data Processing Configuration
  15. Hierarchical Data Processing with Schema Changes
  16. Intelligent Structure Models
  17. Blockchain
  18. Stateful Computing
  19. Appendix A: Connections Reference
  20. Appendix B: Data Type Reference
  21. Appendix C: Function Reference

Blaze Engine Execution Plan Details

Blaze Engine Execution Plan Details

You can view details of the Blaze engine execution plan in the Administrator tool and Developer tool.
In the Developer tool, the Blaze engine execution plan appears as a workflow. You can click on each component in the workflow to get the details.
The following image shows the Blaze execution plan in the Developer tool: The image shows a graphical display of the workflow execution plan. The flow begins with a start task followed by three different pre-session tasks. These are followed by a main session task and a post session task.
The Blaze engine execution plan workflow contains the following components:
  • Start task. The workflow start task.
  • Command task. The pre-processing or post-processing task for local data.
  • Grid mapping. An Informatica mapping that the Blaze engine compiles and distributes across a cluster of nodes.
  • Grid task. A parallel processing job request sent by the Blaze engine executor to the Grid Manager.
  • Grid segment. Segment of a grid mapping that is contained in a grid task.
  • Tasklet. A partition of a grid segment that runs on a separate DTM.
In the Administrator tool, the Blaze engine execution plan appears as a script.
The following image shows the Blaze execution script:
In the Administrator tool, the Blaze engine execution plan has the following details:
  • Script ID. Unique identifier for the Blaze engine script.
  • Script. Blaze engine script that the Data Integration Service generates based on the mapping logic.
  • Depends on. Tasks that the script depends on. Tasks include other scripts and Data Integration Service tasks, like the Start task.

0 COMMENTS

We’d like to hear from you!