| Nabeel Prior 2005-02-15, 7:55 am |
| I don't know much about the scheduling adapter that was mentioned in the
other thread.
What I did in a similar situation was create an orchestration that receives
a poll from a simple SQL statement every 30 seconds (or however short the
polling needs to happen). This orchestration then called a web service to
process the message further.
This is detailed in my posting at:
http://www.brainjar.co.za/blog.aspx...hestration.html
--
Kind Regards,
Nabeel Prior
Web: http://www.brainjar.co.za
Blog: http://www.brainjar.co.za/blog.aspx
"NL" <NL@discussions.microsoft.com> wrote in message
news:40872065-5759-4B0C-A82C-0BE6790D4B70@microsoft.com...[vbcol=seagreen]
> Thank you very much for your input!
>
> The reasons to go the web service route vs. SQL Adapter are mainly to be
> able to re-use business and data access objects (.NET code) across the
> organization. That way, for example, the web site, the intranet
> applications
> and BizTalk orchestrations can use common components, as well as avoid
> placing business logic in stored procedures...
>
> I would definitely be interested in finding out more about the scheduling
> adapter that would eliminate the need for "ever-looping" orchestration!
>
> Thanks again for your help!
>
> NL
>
>
> "Nabeel Prior" wrote:
>
|