This action might not be possible to undo. Are you sure you want to continue?
configure the Debugger. The Debugger runs a workflow for each session type. You can choose from the following Debugger session types when you configure the Debugger: Use an existing non-reusable session: The Debugger uses existing source, target, and session configuration properties. When you run the Debugger, the Integration Service runs the non-reusable session and the existing workflow. The Debugger does not suspend on error. Use an existing reusable session: The Debugger uses existing source, target, and session configuration properties. When you run the Debugger, the Integration Service runs a debug instance of the reusable session and creates and runs a debug workflow for the session. Create a debug session instance: You can configure source, target, and session configuration properties through the Debugger Wizard. When you run the Debugger, the Integration Service runs a debug instance of the debug workflow and creates and runs a debug workflow for the session The following figure shows the windows in the Mapping Designer that appears when you run the Debugger:
Note: You cannot create breakpoints for mapplet Input and Output transformations . 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 .
If you discard target data. When you create an ISDEFAULT condition. Display target data: You can select the target instances you want to display in the Target window while you run a debug session. To clear a selected mapplet. and the port contains a user-defined default value of a constant value or constant expression. . the Debugger pauses when the Integration Service encounters a null input value. Running an Existing Session in Debug Mode If you choose to run an existing session in debug mode.If you want the Debugger to pause after a specified number of errors. you cannot use the type or value in the condition. the Integration Service does not connect to the target . press the Ctrl key and select the mapplet.The Integration Service encounters a null input value. you can select the following target options: Discard target data: You can choose to load or discard target data when you run the Debugger . When you click Finish. and the port contains the system default value. When you use the ISNULL or ISDEFAULT operator. set the number of errors to zero. the Debugger Wizard displays a list of all sessions in the current folder that use the mapping. the Debugger pauses in the following circumstances: . Using ISNULL and ISDEFAULT You can create ISNULL and ISDEFAULT conditions in transformation and global data breakpoints. Select the mapplets from this dialog box that you want to debug.If you want the Debugger to pause at every error.The Integration Service encounters an output transformation error. set the number of errors greater than zero. You also set the number of errors to skip for each breakpoint before the Debugger pauses: . You must either change the properties of the session or choose to create a debug session for the mapping. You cannot run the Debugger against a session configured with multiple partitions or a session configured to run on a grid. and the port contains a userdefined default value of a constant value or constant expression. the Debugger skips five errors and pauses at every sixth error. if the mapping includes mapplets. Select the session you want to use. Set Target Options On the last page of the Debugger Wizard. When you create an ISNULL condition. . For example. the Debugger displays the mapplet instance dialog box. . if you set the number of errors to five.
Note: To enable multiple users to debug the same mapping at the same time. You cannot complete the following tasks for transformations in the mapplet: . . Paused: the Integration Service encounters a break and pauses the Debugger . the Designer expands it to display the individual transformations when the Debugger runs. When you do not select a mapplet to debug. .Step to a transformation instance. The Debugger does not use the high availability functionality . When you select a mapplet to debug.Monitor or modify transformation data. The Debugger can be in one of the following states: Initializing: The Designer connects to the Integration Service. the Designer does not expand it in the workspace.Edit breakpoints. Running: The Integration Service processes the data. .Evaluate expressions. each user must configure different port numbers in the Tools > Options > Debug tab. The following table describes the different tasks you can perform in each of the Debugger states: .
You can view the final value for Sequence Generator and Normalizer transformations in the transformation properties. 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.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 .
Instance window: When the Debugger pauses. Monitoring the Debugger When you run the Debugger. . When you continue the session. you can view transformation data and row information in the Instance window. . You can step to connected transformations in the mapping.Close the Designer. such as Target Designer.Notifications tab: Displays messages from the Repository Service. Data movement: Monitor data as it moves through transformations. even if they do not have an associated breakpoint. . the current instance displays in the Instance window. you can monitor the following information: Session status: Monitor the status of the session. Target window: View target data for each target in the mapping. .Debugger tab: The debug log displays in the Debugger tab. You cannot step to the following instances: . Change null data to not-null: Clear the null column. . such as Save. The Designer prompts you to confirm that you want to make this change. Note: Dynamic partitioning is disabled during debugging.Use the Navigator.Designer Behavior When the Debugger starts.Edit or close the mapping. .Mapplets not selected for debugging Modifying Data When the Debugger pauses.Session Log tab: The session log displays in the Session Log tab. You can make the following modifications to the current instance when the Debugger pauses on a data breakpoint : Modify output data: You can modify output data of the current transformation. Breakpoints: Monitor data that meets breakpoint conditions.Perform repository functions. . the Integration Service validates the data. Output window: The Integration Service writes messages to the following tabs in the Output window: . and enter a value in the value column to change null data to not-null. Change not-null to null: Select the null column to change not-null data to null.Targets .Switch to another tool in the Designer. It performs the same validation it performs when it passes data from port to port in a regular session. and the current instance indicator displays on the transformation in the mapping.Unconnected transformations . you cannot perform the following tasks: . Target data: Monitor target data on a row-by-row basis.Sources . The Mapping Designer displays windows and debug indicators that help you monitor the session: Debug indicators: Debug indicators on transformations help you follow breakpoints and data flow.Close the folder or open another folder. .
and the row type is filtered. Filter. you can change the row type to Insert . you can change the row type from insert to filtered.Mapplets that are not selected for debugging . Router transformation: All output ports. After you change data. Java transformation: Ports in output groups other than the current output group.Output ports when the Debugger pauses on an error breakpoint . If you want to pass the filtered row to the next transformation or target. you can refresh the cache before you continue the session . Lookup transformation: NewLookupRow port for a Lookup transformation configured to use a dynamic cache. Likewise. the rows are not passed through the output ports to the next transformation or target. the Designer processes the request for the current transformation. for a group that meets the group condition. and you can see if the data you enter is valid. Additionally. Custom transformation: Ports in output groups other than the current output group. or Router transformation row types . Sequence Generator transformation: CURRVAL and NEXTVAL ports. you can change the row type to override the group condition evaluation for user defined groups. For Router transformations. Rank transformation: RANKINDEX port.Input or input/output ports .Modify row types: Modify Update Strategy. you cannot change data associated with the following: . When you issue the Refresh command. if the group condition evaluates to false. The Instance window displays <no data available>. You can change the data again before you continue the session Restrictions You cannot change data for the following output ports: Normalizer transformation: Generated Keys and Generated Column ID ports. For example.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue listening from where you left off, or restart the preview.