Running the Debugger - Informatica

When you complete the Debugger Wizard, the Integration Service starts the session and initializes the Debugger. After initialization, the Debugger moves in and out of running and paused states based on breakpoints and commands that you issue from the Mapping Designer. The Debugger can be in one of the following states:

  • Initializing. The Designer connects to the Integration Service.
  • Running. The Integration Service processes the data.
  • Paused. The Integration Service encounters a break and pauses the Debugger.

Note:To enable multiple users to debug the same mapping at the same time, each user must configure different port numbers in the Tools > Options > Debug tab.

The Debugger does not use the high availability functionality.

Initializing State

When you run the Debugger, the Designer connects to the Integration Service, and the Integration Service initializes the session. During initialization, the Designer closes the Navigator window and disables functions, such as switching to another tool, saving the repository, or opening a folder. These functions remain disabled until the Debugger stops.

Running State

When initialization completes, the Debugger moves to the paused state and waits for the command to continue processing. When you continue, the Debugger moves to the running state. The Integration Service transforms data and evaluates data against break point conditions. The Debugger remains in the running state until the Integration Service encounters a breakpoint, you issue a break command, or the session ends.

Paused State

The Debugger pauses when the Integration Service encounters a break. The following break conditions cause the Debugger to pause:

  • The Integration Service encounters a configured breakpoint condition.
  • You instruct the Integration Service to continue to an instance that does not have an associated breakpoint.
  • You issue a manual break command.
  • The Integration Service encounters a fatal error.
  • The Integration Service completes evaluation of all data. The Debugger tab displays a message that the session is complete. When you continue the session, the Debugger clears the Target and Transformation windows.

While the Debugger pauses, you can review and modify transformation output data. The Debugger remains paused until you continue or end the session.

Debugger Tasks

You can perform multiple tasks when you run the Debugger. The type of information that you monitor and the tasks that you perform can vary depending on the Debugger state. For example, you can monitor logs in all three Debugger states, but you can only modify data when the Debugger is in the paused state. You can complete the following types of tasks:

  • Monitor the session. While the Integration Service runs the Debugger, the Mapping Designer displays indicators and windows to help you monitor the session.
  • Modify data and breakpoints. When the Debugger pauses, you can modify output data, row indicators, and breakpoint conditions.
  • Evaluate expressions. When the Debugger pauses, you can invoke the Expression Editor and evaluate an expression against the current data in a transformation. The Debugger returns the result of the expression in a message box. You can enter expressions using ports in the selected transformation. You can also evaluate mapping variables.
  • Issue commands to the Integration Service. You can issue commands to the Integration Service, such as break, continue, or stop.

The following table describes the different tasks you can perform in each of the Debugger states:

Debugger TasksDebugger Tasks

Working with Persisted Values

When you run the Debugger against mappings with sequence generators and mapping variables, the Integration Service might save or discard persisted values:

  • Discard persisted values.The Integration Service does not save final values of generated sequence numbers or mapping variables to the repository when you run a debug session or you run a session in debug mode and discard target data.
  • Save persisted values.The Integration Service saves final values of generated sequence numbers and mapping variables to the repository when you run a session in debug mode and do not discard target data. You can view the final value for Sequence Generator and Normalizer transformations in the transformation properties.

Designer Behavior

When the Debugger starts, you cannot perform the following tasks:

  • Close the folder or open another folder.
  • Use the Navigator.
  • Perform repository functions, such as Save.
  • Edit or close the mapping.
  • Switch to another tool in the Designer, such as Target Designer.
  • Close the Designer.

All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

Informatica Topics