- This topic has 4 replies, 1 voice, and was last updated 9 years, 6 months ago by
.
-
Posts
-
-
I am writing two applications, each has approximatly 12 orchestrations. Is there any reasons to create two Hosts (app1BizTalkServerApplication and app2BizTalkServerApplication) or just load them into the same. They can coexist in the same Host, I have tested this and using two hosts is a bit complicated since I need to remember to change the default host to the correct one when deploying.
But if there is some performance or some other good reason to separate these two applications Orchestrations into separate hosts then I will do so. Currently I would prefer to keep them in the same Host.
-
Basic Logic!
If you have 2 physical BizTalk servers in your BizTalk group and you distribute the load to 2 physical hosts on the 2 machines; for sure there is a benefit, otherwise, I dont think so!
-
-
These might be helpful,
http://webservices.sys-con.com/read/90092.htm
http://dotnet.sys-con.com/read/121831_1.htm
-
-
-
Is there any chance that while in production you will need to update one of the applications but not the other? Generally when you install an application you need to bounce the host(s) that the applicaiton is dependent upon. This could lead to a disruption for application(s) that do not require updating.
Also, if you get into a situation where you need to scale your apps out, you may be limited because everything is tighly coupled within one host. You essentially need to scale out your whole app when you may just need to scale out the Send, Process or Receive function(s)
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.