|
Home > Archive > BizTalk Server > June 2004 > Web Services Best Practices
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 |
Web Services Best Practices
|
|
|
| Hi,
What is the best practice for companies to send decisions on long running business processes? i.e should the third party push the response back to a web service URL we supply or some other method? Does anyone know of any examples of doing this?
thanks
--
John
| |
| Christof 2004-06-20, 11:08 pm |
| Need more context on your scenario in order to answer your concerns...
If your question is like "should use pull our push with our partner's data",
my answer would be: let your partner push the data you need. The way
around, don't let them poll your biztalk server but rather call a URL that
they listen on. Retries will handle failovers.
Regards,
Christof
"John" <John@discussions.microsoft.com> wrote in message
news:A0A84641-4579-46DE-A230-B48FB0AC4680@microsoft.com...
> Hi,
>
> What is the best practice for companies to send decisions on long running
business processes? i.e should the third party push the response back to a
web service URL we supply or some other method? Does anyone know of any
examples of doing this?
>
> thanks
>
> --
> John
| |
| Nick Malik 2004-06-20, 11:08 pm |
| Usually, these details are worked out in a Trading Partner Agreement (or
TPA). That is a document, and agreement between people, about how you will
manage this communication channel. Examples abound.
While it can appear versatile to have a message identify it's return port,
it is often not a good idea. The reason is that, in long running
transactions, you don't know WHEN the response will come. If you want to
move your return address to another location, you'd have to support two
locations until every long running process that has the old address has
completed (which may take months).
I'd recommend that you specify an interface that both side will use, and
allow the actual addresses of the return ports be specified and managed by
people.
HTH,
--- Nick
"John" <John@discussions.microsoft.com> wrote in message
news:A0A84641-4579-46DE-A230-B48FB0AC4680@microsoft.com...
> Hi,
>
> What is the best practice for companies to send decisions on long running
business processes? i.e should the third party push the response back to a
web service URL we supply or some other method? Does anyone know of any
examples of doing this?
>
> thanks
>
> --
> John
| |
| Christof 2004-06-20, 11:08 pm |
| While Nick is right, in addition when using HTTP, a best practice is alway
to use DNS aliases as well... This way the actual endpoint destination may
be changed without bothering your partners with this kind of internal
details...
"Nick Malik" <nickmalik@hotmail.nospam.com> wrote in message
news:D_CAc.110522$3x.57578@attbi_s54...
> Usually, these details are worked out in a Trading Partner Agreement (or
> TPA). That is a document, and agreement between people, about how you
will
> manage this communication channel. Examples abound.
>
> While it can appear versatile to have a message identify it's return port,
> it is often not a good idea. The reason is that, in long running
> transactions, you don't know WHEN the response will come. If you want to
> move your return address to another location, you'd have to support two
> locations until every long running process that has the old address has
> completed (which may take months).
>
> I'd recommend that you specify an interface that both side will use, and
> allow the actual addresses of the return ports be specified and managed by
> people.
>
> HTH,
> --- Nick
>
> "John" <John@discussions.microsoft.com> wrote in message
> news:A0A84641-4579-46DE-A230-B48FB0AC4680@microsoft.com...
running[vbcol=seagreen]
> business processes? i.e should the third party push the response back to a
> web service URL we supply or some other method? Does anyone know of any
> examples of doing this?
>
>
|
|
|
|
|