Monitor your BizTalk environment using PowerShell – Old dehydrated instance monitoring

A while ago Sandro and I wrote a few blogposts about how to do some basic monitoring by using PowerShell. He wrote a post on how to monitor the SQL Server agent jobs and a post on how to monitor disk space:

http://www.biztalkadminsblogging.com/index.php/blog-archive/item/95-monitor-your-biztalk-environment-using-powershell-sql-agent-jobs-monitoring

http://www.biztalkadminsblogging.com/index.php/blog-archive/item/92-monitor-your-biztalk-environment-using-powershell-disk-space-monitoring

I wrote a post on how to monitor your environment for suspended instances:

http://www.biztalkadminsblogging.com/index.php/blog-archive/item/115-monitor-your-biztalk-environment-using-powershell-%E2%80%93-suspended-instance-monitoring

In this blog entry I want to discuss the organization of host and host instances in your BizTalk Group.

Central in this discussion is the application landscape pictured below.

As the official documentation specify, in addition to the high availability aspects of the host instance configuration, you should separate sending, receiving, processing, and tracking functionality into multiple hosts. This provides flexibility when configuring the workload in your BizTalk group and is the primary means of distributing processing across a BizTalk group.

This also will allows you to stop one host without affecting other hosts. For example, you may want to stop sending messages to let them queue up in the MessageBox database, while still allowing the inbound receiving of messages to occur.

The last couple of months this blog received large numbers of spam-comments. Unfortunately captcha’s etc. did not do their work. To prevent this large numbers of spam comments we made the decision to only allow bloggers to write comments.

If you ever want to comment on something, have a question or a remark please use the contact us to stay in contact with us: http://www.biztalkadminsblogging.com/index.php/contact-us

Microsoft Internet Information Services (IIS) provides a Web application infrastructure for many BizTalk Server features. BizTalk Server requires IIS for the following features:

• HTTP adapter
• SOAP adapter
• Windows SharePoint Services adapter
• Secure Sockets Layer (SSL) encryption
• BAM Portal

And you can enable this features by using the Server Manager (check BizTalk 2010 Installation and Configuration – Enable Internet Information Services (Part 1))

In alternative you can also enable these features by using PowerShell.