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. The
following are some of the important things that you need to take account of for
properly configuring a BizTalk Server.
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 BizTalk. By means of a global setting, this number
can be increased, but this may become a pain after a certain point. In case you
leave all the features configured in an individual process, you may end up with
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.
No comments:
Post a Comment