Hi,

One:How do I execute 2 seperate sprocs in sequence from
the one orchestration.

Two:Also I would like to execute the 2nd sproc twice.
how do I accomplish this?

thanks

[ Post a follow-up to this message ]

One work around can be creating a stored proc which calls both of the
stored procedure (using the exec statement if its SQL Server)

But not very sure whether it suits your need.

Hope it helps...
Abhishek Saraswat

"Matt" <anonymous@discussions.microsoft.com> wrote in message news:<03a801c53a66$29d8b3b0$a4
01280a@phx.gbl>...
> Hi,
>
> One:How do I execute 2 seperate sprocs in sequence from
> the one orchestration.
>
> Two:Also I would like to execute the 2nd sproc twice.
> how do I accomplish this?
>
> thanks

[ Post a follow-up to this message ]

Every time you call a stored procedure, you use Send/Receive shapes.
You basically send the SP name and parms, then receive back any ouput.
So since you control where the Send/Receive shapes go, you control when and
how to call the stored procedures.

Neal Walters
http://Biztalk-Training.com
http://VBScript-Training.com


"Matt" wrote:

> Hi,
>
> One:How do I execute 2 seperate sprocs in sequence from
> the one orchestration.
>
> Two:Also I would like to execute the 2nd sproc twice.
> how do I accomplish this?
>
> thanks
>

[ Post a follow-up to this message ]

Matt,

I just saw your earlier post on "Launching an Orchestration from Stored
Proc".  I had the same confusion when I started.

A Receive Port using the SQL Adapter can be used to start or trigger or
orchestration.  But once you are in the orchestration, you cannot have
another "activating receive".  Thus, once you are in the orchestration, you
must use the Send shape to call the next stored procedure (and the Receive
shape to get the output back if any).  Each Send/Receive shape will be
connected to a two-way Send port.  (You can connect a Send shape to a one-wa
y
Send port if you want to just call a SP and not wait for the results, but
this results in an async orchestration - i.e. the next step runs without
waiting for the SP to finish, and you cannot use the Try/Catch on a one-way
Send port - instead, you if SQL fails, you have to use the secondary
transport protocol).   You do want to consider scope blocks (for the
try/catch) so you can do something when SQL goes wrong.  You can also set th
e
retries in your Send port.

Neal Walters
http://Biztalk-Training.com
http://VBScript-Training.com



"Neal Walters" wrote:
[vbcol=seagreen]
> Every time you call a stored procedure, you use Send/Receive shapes.
> You basically send the SP name and parms, then receive back any ouput.
> So since you control where the Send/Receive shapes go, you control when an
d
> how to call the stored procedures.
>
> Neal Walters
> http://Biztalk-Training.com
> http://VBScript-Training.com
>
>
> "Matt" wrote:
> 

[ Post a follow-up to this message ]

Thanks for the reply,

Thats what I tried,  2 receive ports and it gave me that
spill about having to setup some correlation activity.

I will try your suggestion about having a send port to
launch the 2nd sproc I think this will work.  What about
launching the 2nd sproc twice?
Do I use a loop shape?

>-----Original Message-----
>Matt,
>
>   I just saw your earlier post on "Launching an
Orchestration from Stored
>Proc".  I had the same confusion when I started.
>
>   A Receive Port using the SQL Adapter can be used to
start or trigger or
>orchestration.  But once you are in the orchestration,
you cannot have
>another "activating receive".  Thus, once you are in the
orchestration, you
>must use the Send shape to call the next stored
procedure (and the Receive
>shape to get the output back if any).  Each Send/Receive
shape will be
>connected to a two-way Send port.  (You can connect a
Send shape to a one-way
>Send port if you want to just call a SP and not wait for
the results, but
>this results in an async orchestration - i.e. the next
step runs without
>waiting for the SP to finish, and you cannot use the
Try/Catch on a one-way
>Send port - instead, you if SQL fails, you have to use
the secondary
>transport protocol).   You do want to consider scope
blocks (for the
>try/catch) so you can do something when SQL goes wrong.
You can also set the
>retries in your Send port.
>
>Neal Walters
>http://Biztalk-Training.com
>http://VBScript-Training.com
>
>
>
>"Neal Walters" wrote:
> 
Send/Receive shapes.[vbcol=seagreen] 
back any ouput.[vbcol=seagreen] 
you control when and[vbcol=seagreen] 
from[vbcol=seagreen] 
>.
>

[ Post a follow-up to this message ]

I tried making send & receive shapes along with ports for
each sproc but I keep getting a 'message unconstructed'
error when I build it



>-----Original Message-----
>Matt,
>
>   I just saw your earlier post on "Launching an
Orchestration from Stored
>Proc".  I had the same confusion when I started.
>
>   A Receive Port using the SQL Adapter can be used to
start or trigger or
>orchestration.  But once you are in the orchestration,
you cannot have
>another "activating receive".  Thus, once you are in the
orchestration, you
>must use the Send shape to call the next stored
procedure (and the Receive
>shape to get the output back if any).  Each Send/Receive
shape will be
>connected to a two-way Send port.  (You can connect a
Send shape to a one-way
>Send port if you want to just call a SP and not wait for
the results, but
>this results in an async orchestration - i.e. the next
step runs without
>waiting for the SP to finish, and you cannot use the
Try/Catch on a one-way
>Send port - instead, you if SQL fails, you have to use
the secondary
>transport protocol).   You do want to consider scope
blocks (for the
>try/catch) so you can do something when SQL goes wrong.
You can also set the
>retries in your Send port.
>
>Neal Walters
>http://Biztalk-Training.com
>http://VBScript-Training.com
>
>
>
>"Neal Walters" wrote:
> 
Send/Receive shapes.[vbcol=seagreen] 
back any ouput.[vbcol=seagreen] 
you control when and[vbcol=seagreen] 
from[vbcol=seagreen] 
>.
>

[ Post a follow-up to this message ]

Neal:
Similar, but not quite the same:  I can called an orchestration (thus it
does NOT have an "activation" receive port).  I still want to process a
receive; i.e., when I get to that point I want to "hang" until a msg comes
in.  Should this become an Activation port even though we were "activated" b
y
being called from another orchestration?  I am getting the same
"self-correlating port" error message as in this initial thread.
--
Chuck Duncan
Always Willing To Help
Always Anxious to Learn


"Neal Walters" wrote:
[vbcol=seagreen]
> Matt,
>
>    I just saw your earlier post on "Launching an Orchestration from Stored
> Proc".  I had the same confusion when I started.
>
>    A Receive Port using the SQL Adapter can be used to start or trigger or
> orchestration.  But once you are in the orchestration, you cannot have
> another "activating receive".  Thus, once you are in the orchestration, yo
u
> must use the Send shape to call the next stored procedure (and the Receive
> shape to get the output back if any).  Each Send/Receive shape will be
> connected to a two-way Send port.  (You can connect a Send shape to a one-
way
> Send port if you want to just call a SP and not wait for the results, but
> this results in an async orchestration - i.e. the next step runs without
> waiting for the SP to finish, and you cannot use the Try/Catch on a one-wa
y
> Send port - instead, you if SQL fails, you have to use the secondary
> transport protocol).   You do want to consider scope blocks (for the
> try/catch) so you can do something when SQL goes wrong.  You can also set 
the
> retries in your Send port.
>
> Neal Walters
> http://Biztalk-Training.com
> http://VBScript-Training.com
>
>
>
> "Neal Walters" wrote:
> 

[ Post a follow-up to this message ]