There is no doubt that the Microsoft BizTalk is a wonderful product; however, there are many people who have been disappointed with bad experiences with this product. That is because it is not made to work in a correct manner. Most of the people are of assumption that it does not demand proper installation and configuration and it will work in the way that they desire. But this is definitely not the case. People do the same when it comes to the SQL Server. The following are some of the important things that you need to take account of for properly configuring a BizTalk Server.
First is the case of hosts. It is not right that the server is configured out of the box with one Host and Host Instance. If you include more than one BizTalk server in the Group, a SingleHost is probably required that is implemented on one of the Servers and must not be started at the other for adapters such as SharePoint, ftp, MSMQ, etc. For the isolated processes, a different host is recommendable. At the very least, it is highly useful that you make the host configuration as: Receive-Send-Orchestration-Tracking. Even in the BizTalk development machine, these hosts can be made. This is so because of a number of reasons with one of the important being the resources. It is true that there multiple threads in the thread pool of a process in .NET. By means of a global setting, this number can be increased, but this may become a pain after a certain point. Similar is the case with the BizTalk server that also needs a number of threads for operation. In case you leave all the features configured in an individual process as it is by default, you may end up with what is known as the thread starvation in a production environment. This will lead to slowing down the working of the server.
Apart from this, as a matter of fact, you will most possibly need to have separate user accounts for all of the hosts. As a result, between the parts of application, you will have tight security controls. Although, security aspect may be overlooked on the development machine, but any servers such as Production, UAT, Integration, etc. will surely avail advantages from this. You will be in a position to outline the BizTalk solution and evaluate the BizTalk server performance by separating the processing, sending and receiving. You also have the option to connect perfmon logs to each of the service as it is appropriate without the need for tracking the messages received in the Orchestration host per second.
First is the case of hosts. It is not right that the server is configured out of the box with one Host and Host Instance. If you include more than one BizTalk server in the Group, a SingleHost is probably required that is implemented on one of the Servers and must not be started at the other for adapters such as SharePoint, ftp, MSMQ, etc. For the isolated processes, a different host is recommendable. At the very least, it is highly useful that you make the host configuration as: Receive-Send-Orchestration-Tracking. Even in the BizTalk development machine, these hosts can be made. This is so because of a number of reasons with one of the important being the resources. It is true that there multiple threads in the thread pool of a process in .NET. By means of a global setting, this number can be increased, but this may become a pain after a certain point. Similar is the case with the BizTalk server that also needs a number of threads for operation. In case you leave all the features configured in an individual process as it is by default, you may end up with what is known as the thread starvation in a production environment. This will lead to slowing down the working of the server.
Apart from this, as a matter of fact, you will most possibly need to have separate user accounts for all of the hosts. As a result, between the parts of application, you will have tight security controls. Although, security aspect may be overlooked on the development machine, but any servers such as Production, UAT, Integration, etc. will surely avail advantages from this. You will be in a position to outline the BizTalk solution and evaluate the BizTalk server performance by separating the processing, sending and receiving. You also have the option to connect perfmon logs to each of the service as it is appropriate without the need for tracking the messages received in the Orchestration host per second.