Creating Breakpoints - Informatica

Before you run the Debugger, use the Breakpoint Editor in the Mapping Designer to create breakpoint conditions in a mapping. You can create data or error breakpoints for transformations or for global conditions. When you run the Debugger, the Integration Service pauses the Debugger when a breakpoint evaluates to true. You can review and modify transformation data, and then continue the session.

Note:You cannot create breakpoints for mapplet Input and Output transformations.

A breakpoint can consist of an instance name, a breakpoint type, and a condition. When you enter breakpoints, set breakpoint parameters in the following order:

  1. Select the instance name. Choose to create a global breakpoint or a breakpoint against a single transformation within the mapping or mapplet.
  2. Select the breakpoint type. Choose to evaluate error or data conditions. You can also choose the number of rows to skip for the breakpoint type.
  3. Enter the condition. Enter data conditions for global or transformation data breakpoints. You cannot enter conditions for error breakpoints.

After you set the instance name, breakpoint type, and optional data condition, you can view each parameter in the Breakpoints section of the Breakpoint Editor:

  • Instance name. From the Instance Name parameter.
  • Breakpoint enabled flag. Enable in the View Breakpoints section.
  • Breakpoint number. The Designer assigns a number based on the quantity of breakpoints you create in the mapping.
  • These numbers are sequential. If you remove a breakpoint, the Designer renumbers them when you close and reopen the Breakpoint Editor.

  • Breakpoint type. From the Breakpoint Type section.
  • Number of rows to skip. From the Breakpoint Type section.
  • Data condition. From the Condition section.

The following figure shows the parameters in the Breakpoints section:

Creating Break points

For the Lookup transformation, LKP_Store, the check indicates the breakpoint is enabled. “#2” is the sequential breakpoint number, “Data” indicates the breakpoint type, “0” indicates the number of breakpoint rows to skip, and “STORE_ID=[2641]” is the data condition.

Selecting the Instance Name

When you select the instance name, you can create a breakpoint for an individual transformation, or you can create a global breakpoint:

  • Transformation instance. Select a transformation from a mapping or mapplet to configure a breakpoint condition that the Integration Service evaluates when it processes that transformation. The naming convention for transformations within mapplets is MappletName.TransformationName.
  • Global instance. Select Global to configure a breakpoint condition that the Integration Service evaluates when it processes each transformation in the mapping.

Creating Error Breakpoints

When you create an error breakpoint, the Debugger pauses when the Integration Service encounters error conditions such as a transformation error or calls to the ERROR function.

You also set the number of errors to skip for each breakpoint before the Debugger pauses:

  • If you want the Debugger to pause at every error, set the number of errors to zero.
  • If you want the Debugger to pause after a specified number of errors, set the number of errors greater than zero. For example, if you set the number of errors to five, the Debugger skips five errors and pauses at every sixth error.

Evaluating Error Breakpoints

The Integration Service uses the following rules to evaluate error breakpoints:

  1. The Integration Service encounters a null input value, and the port contains a user-defined default value of ERROR ( ).
  2. The Integration Service encounters an output transformation error, and the port contains the system default value of ERROR ( ). The following errors are considered transformation errors:
  3. Data conversion errors, such as passing a string to date
  4. Expression evaluation errors, such as dividing by zero
  5. Calls to the ERROR function in an expression
  6. The Integration Service encounters a null input value or transformation output error, and the port contains a user-defined default value of ABORT ( ).
  7. The Integration Service encounters a fatal error.
  8. If the Integration Service encounters an error when it processes a transformation, it evaluates error breakpoints for that transformation and global error breakpoints. If any error breakpoint evaluates to true, the Debugger pauses and does not evaluate data breakpoints.

Note:When the Integration Service encounters a fatal error or an ABORT, the Debugger breaks even if it has not reached the configured number of errors to skip.

Creating Data Breakpoints

When you create a data breakpoint, the Debugger pauses when the data breakpoint evaluates to true. You can set the number of rows to skip or a data condition or both. You have the following options when you set data breakpoints:

  • If you want the Debugger to pause at every row, set the number of rows to zero and do not set a data condition.
  • If you want the Debugger to pause after a specified number of rows passes through the transformation, set the number of rows greater than zero. For example, if you set the number of rows to three, the Debugger skips three rows of data and pauses every fourth row.
  • If you want the Debugger to pause each time the data meets a data condition, enter the data condition and set the number of rows set to zero.
  • If you want the Debugger to pause at designated intervals when a row meets the data condition, you can enter the data condition and set the number of rows greater than zero. For example, if you set the number of rows to three, the Debugger skips three breakpoint rows that meet the condition and pauses at every fourth row.

The following table summarizes the options when you set data breakpoint types and conditions:

Creating Data Break points

Entering the Data Breakpoint Condition

When you create a data condition, you enter a global parameter or a parameter for a single transformation. You have different options depending on the selected instance and the type of condition you create.

Use the following syntax when you evaluate a transformation against a port or constant value:

<port> <operator> <type> <value>

Use the following syntax when you check for null and default values, either globally or in a transformation:

<port> <operator>

For a single transformation, you can enter multiple conditions within one breakpoint if you want the Debugger to pause when all the conditions are true. You can also enter multiple breakpoints for a single transformation if you want the Debugger to pause when at least one condition is true.

The following figure shows multiple conditions within a single breakpoint:

Entering the Data Break point Condition

In this example, the Debugger pauses when both conditions are true.

The following figure shows multiple breakpoints within a single transformation:

Entering the Data Break point Condition

In this example, the Debugger pauses when either condition is true.

The following table describes the condition parameters for transformation and global data breakpoints:

Entering the Data Break point Condition

Entering a Transformation Data Condition

When you enter a transformation data condition, you can select a specific port in the transformation, or you can select from the following port parameters:

  • Row type. Insert, update, delete, reject, or filtered.
  • Row ID. Row number passing through the transformation.
  • Any port. When you choose <<ANY-PORT>>, you can enter a condition that the Integration Service evaluates for every port in the transformation. Use the ISNULL or ISDEFAULT operator to test for null or error default values.

Note:For best results with port-to-port comparison, use ports that have the same datatype. When you compare ports that have different datatypes, the Integration Service converts the datatype of the upstream port to the datatype of the downstream port before it compares the ports, which might result in an invalid comparison.

Entering a Global Data Condition

When you enter a global data condition, enter a condition that the Integration Service evaluates null and error default values in every port in every transformation. You can choose <ANY-PORT> <ISNULL> or <ANY-PORT> <ISDEFAULT>.

Using ISNULL and ISDEFAULT

You can create ISNULL and ISDEFAULT conditions in transformation and global data breakpoints. When you use the ISNULL or ISDEFAULT operator, you cannot use the type or value in the condition.

When you create an ISNULL condition, the Debugger pauses when the Integration Service encounters a null input value, and the port contains the system default value.

When you create an ISDEFAULT condition, the Debugger pauses in the following circumstances:

  • The Integration Service encounters an output transformation error, and the port contains a user-defined default value of a constant value or constant expression.
  • The Integration Service encounters a null input value, and the port contains a user-defined default value of a constant value or constant expression.

Steps to Enter Breakpoints

Complete the following steps to enter breakpoints.

To enter breakpoints:

  1. In a mapping, open the Breakpoint Editor in one of the following ways:
    • Press Alt+F9.
    • Click Mappings > Debugger > Edit Breakpoints.
    • Right-click a transformation or mapplet and choose Edit Breakpoint.
  2. Note:You can right-click any portion of an iconized transformation or mapplet. If the transformation or mapplet is in normal view, right-click the title bar.

  3. Select the instance name in the Instance Name section.
  4. Click Add to add a new breakpoint.
  5. If you select <<ALL INSTANCES>> and click Add, the Designer prompts you to choose a specific transformation or a global instance.

    You can click OK to create an unconditional data breakpoint.
  6. Select the Breakpoint Type.
  7. If you select a data breakpoint type, you can enter the condition. Enter multiple conditions if you want the Integration Service to evaluate multiple conditions.
  8. Repeat steps 2 to 5 for each breakpoint.
  9. Click OK.

Editing a Breakpoint

You might want to review breakpoints before or during a Debugger session. You can edit, disable, or remove breakpoints within the Breakpoint Editor.

To edit breakpoints:

  1. In a mapping, open the Breakpoint Editor in one of the following ways:
    • Press Alt+F9.
    • Click Mappings > Debugger > Edit Breakpoints.
    • Right-click a transformation and choose Edit Breakpoint.
  2. Note:You can right-click over any portion of an iconized transformation or mapplet. If the transformation is in normal view, right-click over the title bar.

  3. Select an instance name in the Instance Name section.
  4. Tip:Select <<ALL INSTANCES>> in the Instance Name list to view all breakpoints for a mapping.

  5. Select a breakpoint in the Breakpoints section.
  6. Change the condition or breakpoint type.
  7. Clear the check box by a breakpoint to disable it. You can enable the breakpoint again by selecting the check box.
  8. Create a new breakpoint using the instructions above for creating breakpoints.
  9. Click the Remove button to remove a selected breakpoint.
  10. Click the Remove All button to remove all breakpoints for the selected instance. If you want to remove all breakpoints in the mapping, select <<ALL INSTANCES>>.

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

Informatica Topics