|
Home > Archive > BizTalk Server Orchestration > February 2005 > Orchestation as a web service
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 |
Orchestation as a web service
|
|
| Brian C 2005-02-14, 5:50 pm |
| I have the following scenario...
I have an orchestration that I am exposing as a Web service. I have a local
application that will 'call' my orchestration and pass me an 'ID'. I then
use that ID to call a stored proc that returns a large 'Order' in XML. I
need to send that XML to a vendor who will fill the order. They will
immediately send confirmation back to me saying 'YES' or 'NO' if the file is
acceptable... then at some point, I will receive confirmation that the order
has been filled.
Here are my questions...
My vendor can only receive transactions via XML using https, BUT they can
post to any web service as long as I can provide the WSDL associated with my
objects. So, what is the best way to do this?
Do I send them my transaction using https, and then look for the immediate
response in a web service I create, or do I use the https response they will
send back (I hope I'm not botching terminology on this, I've never done http
in BizTalk). Then, do I create a different web service that will look for
the order fullfilment they will send to me. Concerning the order
fullfilment, I will need to use Correlation to keep track of the order,
because the order may not be filled for a few days or even weeks... does
that have influence on how things should be done?
Thanks in advance!
Brian
We can post to any Web Service they have on their end provided they give us
the WSDL associated with their objects. On our end, we do not support Web
Services to receive transactions. They will have to post the transactions
to us via XML.
| |
| Matt Milner 2005-02-15, 2:47 am |
| Sounds like you have a good plan. Post to their HTTP site with your
document and then wait to receive their response on your web service. You
can use correlation to get the response back into your orchestration (be
sure to use an XML receive pipeline on your web service). You can also use
correlation on the order fulfillment as you described.
matt
"Brian C" <brian.cesafsky@midwestwireless.com> wrote in message
news:O%23HJfWuEFHA.2572@tk2msftngp13.phx.gbl...
>I have the following scenario...
>
> I have an orchestration that I am exposing as a Web service. I have a
> local application that will 'call' my orchestration and pass me an 'ID'.
> I then use that ID to call a stored proc that returns a large 'Order' in
> XML. I need to send that XML to a vendor who will fill the order. They
> will immediately send confirmation back to me saying 'YES' or 'NO' if the
> file is acceptable... then at some point, I will receive confirmation that
> the order has been filled.
>
> Here are my questions...
> My vendor can only receive transactions via XML using https, BUT they can
> post to any web service as long as I can provide the WSDL associated with
> my objects. So, what is the best way to do this?
>
> Do I send them my transaction using https, and then look for the immediate
> response in a web service I create, or do I use the https response they
> will send back (I hope I'm not botching terminology on this, I've never
> done http in BizTalk). Then, do I create a different web service that
> will look for the order fullfilment they will send to me. Concerning the
> order fullfilment, I will need to use Correlation to keep track of the
> order, because the order may not be filled for a few days or even weeks...
> does that have influence on how things should be done?
>
> Thanks in advance!
>
> Brian
> We can post to any Web Service they have on their end provided they give
> us the WSDL associated with their objects. On our end, we do not support
> Web Services to receive transactions. They will have to post the
> transactions to us via XML.
>
>
|
|
|
|
|