|
Home > Archive > BizTalk Server Orchestration > August 2004 > Suggestions on debugging an orchestration
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Suggestions on debugging an orchestration
|
|
| Norton 2004-08-14, 5:48 pm |
| Ok, my orchestration runs fine but I need to show a few guys how to debug an
orchestration.
It might sound simple, but how do I get my orchestration to fail or stop
long enough to be able to go into HAT and put breakpoints in it.
Any ideas?
Thanks.
Norton
| |
| Competitve Dad 2004-08-15, 7:46 am |
| Norton,
I've only managed to do this by actually putting a message through without
debugging, then going to the Message Flow dialog for that message. From there
you can choose Orchestration Debugger, and then put a breakpoint where you
want it when the orchestration is displayed.
Next time you send a message it should break at the appropriate point.
Cheers,
Martin
"Norton" wrote:
> Ok, my orchestration runs fine but I need to show a few guys how to debug an
> orchestration.
>
> It might sound simple, but how do I get my orchestration to fail or stop
> long enough to be able to go into HAT and put breakpoints in it.
>
> Any ideas?
>
> Thanks.
>
> Norton
>
>
>
| |
| Norton 2004-08-15, 5:47 pm |
| So, are you saying that you put a message through that fails and then you go
and look at the message, or do you let a message go all the way through and
then look at the last 100 messages?
Thanks!
Norton
"Competitve Dad" <CompetitveDad@discussions.microsoft.com> wrote in message
news:4CBADFA6-9E0D-4ABB-B80B-35FC0F7BF29D@microsoft.com...[vbcol=seagreen]
> Norton,
>
> I've only managed to do this by actually putting a message through without
> debugging, then going to the Message Flow dialog for that message. From
> there
> you can choose Orchestration Debugger, and then put a breakpoint where you
> want it when the orchestration is displayed.
>
> Next time you send a message it should break at the appropriate point.
>
> Cheers,
>
> Martin
>
> "Norton" wrote:
>
| |
| Competitve Dad 2004-08-16, 7:50 am |
| Essentially my experience has been that you need an instance of a message
failure to get to the Orchestration Debugger. Once you can get to that from
Message Flow, then you can view the orchestration, stick a break point on
somewhere, and then stick another message through.
Seems crazy to have to do it that way, and I reckon there must be a "proper"
way, but that's certainly what I've done.
"Norton" wrote:
> So, are you saying that you put a message through that fails and then you go
> and look at the message, or do you let a message go all the way through and
> then look at the last 100 messages?
>
> Thanks!
>
> Norton
> "Competitve Dad" <CompetitveDad@discussions.microsoft.com> wrote in message
> news:4CBADFA6-9E0D-4ABB-B80B-35FC0F7BF29D@microsoft.com...
>
>
>
| |
| Neal Walters 2004-08-19, 2:48 am |
| From HAT, you can definitely select a successfully completed orchestration,
right-click and select "Orchestration Debugger" and view which paths it took.
However, I doubt you can do a "Debugger Attach" (to see actual message
values) unless you are in a failure, breakpoint, or suspend shape.
Also remember that when you set a breakpoint, it effects all following
orchestrations until you clear the breakpoint.
Neal Walters
http://Biztalk-Training.com - Free Biztalk Training Videos
|
|
|
|
|