03-21-06 08:09 AM
Hi,
The orchestration and messaging engines are very robust, so a normal shut
down should not normally generate any problems. If you are really concerned
about not losing any data, you could try the following:
Dissabling the receive ports and waiting for all the messages to pass
through the system will ensure you dont have any data in transit.
Using the admin tool to stop the BizTalk host instances is generally better
than using the serivces controller app, or just shutting down the server, as
it allows all the running orchestrations to dehydrate to the database
effectivly.
Regards,
Alan
--
The Bloggers Guide to BizTalk
http://geekswithblogs.com/asmith
"Eric Payne" wrote:
> Is there a proper way to reboot a BizTalk 2004 server?
> Meaning, first shut down this server then shut down that service now it is
> ok to reboot.
>
> I remeber back in the exchange 5.5 days if you didn't first shut down the
> exchange store the server would hang on reboot, just wondering if there is
> anything like that for BizTalk 2004. I have a server that takes 17 minutes
> to reboot, which I think is way to long.
>
> Thanks
>
>
>
[ Post a follow-up to this message ]
|