|
Home > Archive > BizTalk Server Framework > August 2004 > Hiw to schedule 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 |
Hiw to schedule orchestration
|
|
| Ashish Shukla 2004-08-17, 2:56 am |
| Hi Everyone
I have to read data from a SQL 6.5 server. Since SQL adapter with BizTalk
server 2004 does not work with SQL 6.5 I have written my own component to
access data. But the only way to schedule an orchestration is to use SQL
adapter and the SQL adapter will run as polling service and will get the data
from SQL server and instantiate the orchestration. Is there a way that I can
build orchestration which gets invoked automatically after a certain time.
Please help.
Thanks and Regards
Ashish Shukla
| |
| Gilles [MSFT] 2004-08-17, 5:50 pm |
| Hello, Ashish,
>I have to read data from a SQL 6.5 server. Since SQL adapter with BizTalk
>server 2004 does not work with SQL 6.5 I have written my own component to
>access data.
I am not exactly sure what kind of component you wrote and what kind of work it performs so I might be off.
Please correct me if I am wrong.
>But the only way to schedule an orchestration is to use SQL
>adapter and the SQL adapter will run as polling service and will get the data
>from SQL server and instantiate the orchestration.
I assume that your orchestration starts with a receive shape, marked as "activate". This means that every time a message that
matches the schema expected by your receive shape is picked up by BizTalk, it will be fed to a new instance of your orchestration.
It sounds (but again, I am not sure I really understood your issue) that you would like to start an orchestration and have it call your
component to retrieve data from SQL 6.5 at specific intervals. You can do this. However, this is not a very good design.
A better way to do this would be to package your component that reads from SQL 6.5 as an adapter. This way, your component
could do all the polling it wants (and you would have control over this in your code). When data need to be retrieved, then your
adapter can produce a message and send it to BizTalk. You will then be able to take full advantage of BizTalk messaging.
Now you do not have to worry about starting an orchestration to perform polling.
In general, an orchestration should not be attempting to handle some protocol. Handling a protocol and getting messages is the
duty of adapters.
Thanks.
-Gilles.
| |
| user@domain.invalid 2004-08-18, 2:47 am |
| Thanks a lot Gilles. The component that I use takes certain parameters,
like connection string, stored procedure name etc and fethes the data
and returns the resultset. I will try what you have suggested but I
would still prefer if somehow orchestration could be scheduled.
Thanks again
Regards
Ashish Shukla
Gilles [MSFT] wrote:
> Hello, Ashish,
>
>
>
>
> I am not exactly sure what kind of component you wrote and what kind of work it performs so I might be off.
> Please correct me if I am wrong.
>
>
>
>
> I assume that your orchestration starts with a receive shape, marked as "activate". This means that every time a message that
> matches the schema expected by your receive shape is picked up by BizTalk, it will be fed to a new instance of your orchestration.
>
> It sounds (but again, I am not sure I really understood your issue) that you would like to start an orchestration and have it call your
> component to retrieve data from SQL 6.5 at specific intervals. You can do this. However, this is not a very good design.
>
> A better way to do this would be to package your component that reads from SQL 6.5 as an adapter. This way, your component
> could do all the polling it wants (and you would have control over this in your code). When data need to be retrieved, then your
> adapter can produce a message and send it to BizTalk. You will then be able to take full advantage of BizTalk messaging.
> Now you do not have to worry about starting an orchestration to perform polling.
>
> In general, an orchestration should not be attempting to handle some protocol. Handling a protocol and getting messages is the
> duty of adapters.
>
> Thanks.
> -Gilles.
| |
| Christof [MVP] 2004-08-18, 5:52 pm |
| Several options:
- have an activate receive on the orchestration that is exposed as a
webservice. Some custom coded windows service could call this webservice
once in a while...
- create an "orchestrationscheduler" adapter that is configurable and sends
messages into the message box at regular times...
- create kind of "schedule" orchestration that loops and has a wait shape in
it...
Best regards,
Christof
--
Christof [Microsoft BizTalk Server MVP]
<user@domain.invalid> wrote in message
news:Or7%23vhNhEHA.3928@TK2MSFTNGP11.phx.gbl...
> Thanks a lot Gilles. The component that I use takes certain parameters,
> like connection string, stored procedure name etc and fethes the data
> and returns the resultset. I will try what you have suggested but I
> would still prefer if somehow orchestration could be scheduled.
>
> Thanks again
> Regards
> Ashish Shukla
>
>
>
> Gilles [MSFT] wrote:
BizTalk[vbcol=seagreen]
to[vbcol=seagreen]
work it performs so I might be off.[vbcol=seagreen]
data[vbcol=seagreen]
"activate". This means that every time a message that[vbcol=seagreen]
BizTalk, it will be fed to a new instance of your orchestration.[vbcol=seagreen]
you would like to start an orchestration and have it call your[vbcol=seagreen]
do this. However, this is not a very good design.[vbcol=seagreen]
from SQL 6.5 as an adapter. This way, your component[vbcol=seagreen]
in your code). When data need to be retrieved, then your[vbcol=seagreen]
able to take full advantage of BizTalk messaging.[vbcol=seagreen]
polling.[vbcol=seagreen]
protocol. Handling a protocol and getting messages is the[vbcol=seagreen]
>
|
|
|
|
|