Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Look up keyword
Like this
4Activity
0 of .
Results for:
No results containing your search query
P. 1
Using the Debugger

Using the Debugger

Ratings: (0)|Views: 34|Likes:
Published by ypraju

More info:

Published by: ypraju on Dec 21, 2009
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less

08/24/2010

pdf

text

original

 
Using the Debugger 
By PenchalaRaju.Yanamala
Using the Debugger Overview
You can debug a valid mapping to gain troubleshooting information about dataand error conditions. To debug a mapping, you configure and run the Debugger from within the Mapping Designer. The Debugger uses a session to run themapping on the Integration Service. When you run the Debugger, it pauses atbreakpoints and you can view and edit transformation output data.You might want to run the Debugger in the following situations:
Before you run a session.
After you save a mapping, you can run some initialtests with a debug session before you create and configure a session in theWorkflow Manager.
After you run a session.
If a session fails or if you receive unexpected resultsin the target, you can run the Debugger against the session. You might alsowant to run the Debugger against a session if you want to debug the mappingusing the configured session properties.
Debugger Session Types
You can select three different debugger session types when you configure theDebugger. The Debugger runs a workflow for each session type. You canchoose from the following Debugger session types when you configure theDebugger:
Use an existing non-reusable session.
The Debugger uses existing source,target, and session configuration properties. When you run the Debugger, theIntegration 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, theIntegration Service runs a debug instance of the reusable session and createsand runs a debug workflow for the session.
Create a debug session instance.
You can configure source, target, andsession configuration properties through the Debugger Wizard. When you runthe Debugger, the Integration Service runs a debug instance of the debugworkflow and creates and runs a debug workflow for the session.
 
Debug Process
To debug a mapping, complete the following steps:1.
Create breakpoints.
Create breakpoints in a mapping where you want theIntegration Service to evaluate data and error conditions.2.
Configure the Debugger.
Use the Debugger Wizard to configure theDebugger for the mapping. Select the session type the Integration Service useswhen it runs the Debugger. When you create a debug session, you configure asubset of session properties within the Debugger Wizard, such as source andtarget 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 debuggingsession and workflow. The Integration Service reads the breakpoints andpauses the Debugger when the breakpoints evaluate to true.4.
Monitor the Debugger.
While you run the Debugger, you can monitor thetarget data, transformation and mapplet output data, the debug log, and thesession log. When you run the Debugger, the Designer displays the followingwindows:
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 modifydata and see the effect on transformations, mapplets, and targets as the datamoves through the pipeline. You can also modify breakpoint information.The Designer saves mapping breakpoint and Debugger information in theworkspace 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 theDebugger configuration to the other PowerCenter Client machine.
 
Creating Breakpoints
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 theDebugger, the Integration Service pauses the Debugger when a breakpointevaluates to true. You can review and modify transformation data, and thencontinue the session.
Note:
You cannot create breakpoints for mapplet Input and Outputtransformations.A breakpoint can consist of an instance name, a breakpoint type, and acondition. When you enter breakpoints, set breakpoint parameters in thefollowing order:1.
Select the instance name.
Choose to create a global breakpoint or abreakpoint against a single transformation within the mapping or mapplet.2.
Select the breakpoint type.
Choose to evaluate error or data conditions. Youcan also choose the number of rows to skip for the breakpoint type.3.
Enter the condition.
Enter data conditions for global or transformation databreakpoints. 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

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->