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:
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:
These numbers are sequential. If you remove a breakpoint, the Designer renumbers them when you close and reopen the Breakpoint Editor.
The following figure shows the parameters in the Breakpoints section:
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=” 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:
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:
Evaluating Error Breakpoints
The Integration Service uses the following rules to evaluate error 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:
The following table summarizes the options when you set data breakpoint types and conditions:
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:
In this example, the Debugger pauses when both conditions are true.
The following figure shows multiple breakpoints within a single transformation:
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 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:
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:
Steps to Enter Breakpoints
Complete the following steps to enter breakpoints.
To enter breakpoints:
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.
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.
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:
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.
Tip:Select <<ALL INSTANCES>> in the Instance Name list to view all breakpoints for a mapping.
Using The Designer
Working With Sources
Working With Flat Files
Working With Targets
Mapping Parameters And Variables
Working With User-defined Functions
Using The Debugger
Viewing Data Lineage
Managing Business Components
Creating Cubes And Dimensions
Using The Mapping Wizards
All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.