If an orchetartion is published as a web service, how to you configure a
BizTalk 2004 Group so that if one biztalk server fails a second biztalk
server will take over without interruption to the service

Thanks

Tim

[ Post a follow-up to this message ]

Put the web service on both machines and setup Network Load balancing. This
way the client hits both serves or the one that is up.

matt


"TimG" <TimG@discussions.microsoft.com> wrote in message
news:13B168B9-6439-4DCE-B532-C47A1CA2C752@microsoft.com...
> If an orchetartion is published as a web service, how to you configure a
> BizTalk 2004 Group so that if one biztalk server fails a second biztalk
> server will take over without interruption to the service
>
> Thanks
>
> Tim

[ Post a follow-up to this message ]

Thanks for that Matt

Is it best practice to publish the web service to the the biztalk server or
to  an external web server ?

Do you know of any white papers/links which demonstrate best practice
concerning publishing orchestrations as webservices

Regards

Tim

"Matt Milner" wrote:

> Put the web service on both machines and setup Network Load balancing. Thi
s
> way the client hits both serves or the one that is up.
>
> matt
>
>
> "TimG" <TimG@discussions.microsoft.com> wrote in message
> news:13B168B9-6439-4DCE-B532-C47A1CA2C752@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]

I don't know of any white papers.  I think it depends on your environment
and your requirements, but publishing the web service through reverse proxy,
using ISA for example, allows for the biztalk servers to be outside your DMZ
but your web service to be available in the DMZ.  This is often considered
best practice as it allows your biztalk server to be protected.

Matt


"TimG" <TimG@discussions.microsoft.com> wrote in message
news:10C727BD-FFB0-41F2-96A4-6714D9378EC9@microsoft.com...[vbcol=seagreen]
> Thanks for that Matt
>
> Is it best practice to publish the web service to the the biztalk server
> or
> to  an external web server ?
>
> Do you know of any white papers/links which demonstrate best practice
> concerning publishing orchestrations as webservices
>
> Regards
>
> Tim
>
> "Matt Milner" wrote:
> 

[ Post a follow-up to this message ]

Thanks again Matt

So is it correct to say  that by publishing the web services by reverse
proxy using ISA answers my initial question ( if one biztalk server fails
then a second one will take over)

Regards

Tim

"Matt Milner" wrote:

> I don't know of any white papers.  I think it depends on your environment
> and your requirements, but publishing the web service through reverse prox
y,
> using ISA for example, allows for the biztalk servers to be outside your D
MZ
> but your web service to be available in the DMZ.  This is often considered
> best practice as it allows your biztalk server to be protected.
>
> Matt
>
>
> "TimG" <TimG@discussions.microsoft.com> wrote in message
> news:10C727BD-FFB0-41F2-96A4-6714D9378EC9@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]

You'll need to use network load balancing to achieve that.  Use NLB on two
biztalk servers to host your web service, then use ISA to publish this NLB
web service out.  Now ISA might be your Single Point of Failure, but you can
do some fault tolerance there as well.

Matt


"TimG" <TimG@discussions.microsoft.com> wrote in message
news:C4B4043A-00D9-43CB-9A72-13D2C0AD6463@microsoft.com...[vbcol=seagreen]
> Thanks again Matt
>
> So is it correct to say  that by publishing the web services by reverse
> proxy using ISA answers my initial question ( if one biztalk server fails
> then a second one will take over)
>
> Regards
>
> Tim
>
> "Matt Milner" wrote:
> 

[ Post a follow-up to this message ]

Thanks again for that Matt

This is prob the last question of the issue... I presume using standard
edition would be ok in this scenario ?

Tim

"Matt Milner" wrote:

> You'll need to use network load balancing to achieve that.  Use NLB on two
> biztalk servers to host your web service, then use ISA to publish this NLB
> web service out.  Now ISA might be your Single Point of Failure, but you c
an
> do some fault tolerance there as well.
>
> Matt
>
>
> "TimG" <TimG@discussions.microsoft.com> wrote in message
> news:C4B4043A-00D9-43CB-9A72-13D2C0AD6463@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]

Actually, I believe you need enterprise edition for any biztalk deployment
which involves more than one server in a biztalk group.  Check the biztalk
site for information on the differences in editions:
http://www.microsoft.com/biztalk/

Matt


"TimG" <TimG@discussions.microsoft.com> wrote in message
news:B4B21EA9-0384-4B0B-BC5F-CB96817D4A92@microsoft.com...[vbcol=seagreen]
> Thanks again for that Matt
>
> This is prob the last question of the issue... I presume using standard
> edition would be ok in this scenario ?
>
> Tim
>
> "Matt Milner" wrote:
> 

[ Post a follow-up to this message ]