Table of Contents


  1. Preface
  2. Using the Designer
  3. Working with Sources
  4. Working with Flat Files
  5. Working with Targets
  6. Mappings
  7. Mapplets
  8. Mapping Parameters and Variables
  9. Working with User-Defined Functions
  10. Using the Debugger
  11. Viewing Data Lineage
  12. Comparing Objects
  13. Managing Business Components
  14. Creating Cubes and Dimensions
  15. Using the Mapping Wizards
  17. Datatype Reference
  18. Configure the Web Browser

Debug Process

Debug Process

To debug a mapping, complete the following steps:
  1. Create breakpoints.
    Create breakpoints in a mapping where you want the Integration Service to evaluate data and error conditions.
  2. Configure the Debugger.
    Use the Debugger Wizard to configure the Debugger for the mapping. Select the session type the Integration Service uses when it runs the Debugger. When you create a debug session, you configure a subset of session properties within the Debugger Wizard, such as source and target location. You can also choose to load or discard target data.
  3. Run the Debugger.
    Run the Debugger from within the Mapping Designer. When you run the Debugger, the Designer connects to the Integration Service. The Integration Service initializes the Debugger and runs the debugging session and workflow. The Integration Service reads the breakpoints and pauses the Debugger when the breakpoints evaluate to true.
  4. Monitor the Debugger.
    While you run the Debugger, you can monitor the target data, transformation and mapplet output data, the debug log, and the session log. When you run the Debugger, the Designer displays the following windows:
    • Debug log.
      View messages from the Debugger.
    • Target window.
      View target data.
    • Instance window.
      View transformation data.
  5. Modify data and breakpoints.
    When the Debugger pauses, you can modify data and see the effect on transformations, mapplets, and targets as the data moves through the pipeline. You can also modify breakpoint information.
The Designer saves mapping breakpoint and Debugger information in the workspace files. You can copy breakpoint information and the Debugger configuration to another mapping. If you want to run the Debugger from another PowerCenter Client machine, you can copy the breakpoint information and the Debugger configuration to the other PowerCenter Client machine.
The following figure shows the windows in the Mapping Designer that appears when you run the Debugger:
In addition to the mapping, the Debugger displays the debug log, session log, Instance window, and Target window.
  1. Debugger log.
  2. Session log.
  3. Instance window.
  4. Target window.

Updated June 25, 2018