If Orch-A calls Orch-B using the "Call Orch" shape - it looks to me like the
Orch-B never shows up in HAT. So when Orch-B blow up or you just want to see
the debugger to see the data flow, is there a way to do it?

The site that I'm at usually uses direct binding and does a send/receive to
essentially call another orchestration - but then you have to deal with the
problem of setting the correlation (especially the hassle if it is in a
loop).

Thanks,
Neal Walters
http://Biztalk-Training.com - Learn Biztalk With Videos

[ Post a follow-up to this message ]

Neal,  Called orchestrations don't get their own "schedule" which means the
tracking information used by the HAT debugger isn't there.  So you can't
debug called orchestrations.  One good reason not to use them IMO.


Jon Flanders [MVP]
http://www.masteringbiztalk.com
http://www.quicklearn.com/workflow.htm

> If Orch-A calls Orch-B using the "Call Orch" shape - it looks to me
> like the Orch-B never shows up in HAT. So when Orch-B blow up or you
> just want to see the debugger to see the data flow, is there a way to
> do it?
>
> The site that I'm at usually uses direct binding and does a
> send/receive to essentially call another orchestration - but then you
> have to deal with the problem of setting the correlation (especially
> the hassle if it is in a loop).
>
> Thanks, Neal Walters http://Biztalk-Training.com - Learn Biztalk With
> Videos
>

[ Post a follow-up to this message ]

So what alternative is there to re-usability?  Suppose I have a big
orchestrations, and there are two points in it where I need to
check-inventory in a loop (and that process is about 12 orch shapes).  I
don't want redundant code, and I'm lazy at heart.

The site that I'm at has many orchestrations that are all "called" by direct
binding and correlation.  But there are so many issues setting up correlatio
n
in loops!

Neal Walters
http://Biztalk-Training.com


"Jon Flanders" wrote:

> Neal,  Called orchestrations don't get their own "schedule" which means th
e
> tracking information used by the HAT debugger isn't there.  So you can't
> debug called orchestrations.  One good reason not to use them IMO.
>
>
> Jon Flanders [MVP]
> http://www.masteringbiztalk.com
> http://www.quicklearn.com/workflow.htm
> 
>
>
>

[ Post a follow-up to this message ]

With Biztalk2004 + SP1 you could drill down the called orchestration in
orchestration debugger.
We will have the same functionality for BizTalk 2006.

Do you have SP1 installed?



thnx

[ Post a follow-up to this message ]

Yes, of course we have SP1.  What's the trick to drill down?

Thanks,
Neal


"Vishal Chowdhary" wrote:

> With Biztalk2004 + SP1 you could drill down the called orchestration in
> orchestration debugger.
> We will have the same functionality for BizTalk 2006.
>
> Do you have SP1 installed?
>
>
>
> thnx
>
>
>
>
>

[ Post a follow-up to this message ]

right click at the point where the orchestration is being called and say '
View Called Orchestration' and you will be able to drill down.

[ Post a follow-up to this message ]

Wow thanks!  I guess it seems obvious but I wouldn't have thought of that.

Neal Walters
http://Biztalk-Training.com

"Vishal Chowdhary" wrote:

> right click at the point where the orchestration is being called and say '
> View Called Orchestration' and you will be able to drill down.
>
>

[ Post a follow-up to this message ]