This list was originally created by the Microsoft BizTalk support team. Feel free to add to it.
Do not let suspended instances accumulate. They should be handled promptly by either being terminated or successfully resubmitted. If these items reach in the thousands, performance can be impacted. MsgBox Viewer also breaks
down the suspended instances by host.
919776 Description of the SQL Server Agent jobs in BizTalk Server
Read suggested related topics:
This is really a nice checklist and all in one place for a BizTalk Admin .. Kudos ..
Good assembly of actions and resources for BizTalk administrators.
Great job guys - very useful and actionable content.
BizTalk MsgBoxViewer is not integrated with BizTalk360: soa-thoughts.blogspot.com/.../biztalk360-new-v25-releasemessage-box.html
Steef-Jan Wiggers intend to say BizTalk MsgBoxViewer is NOW integrated with BizTalk360 www.biztalk360.com/.../tour.aspx (just a single character changed the whole meaning :-))
Regarding your point "Know what is running in each host", "Consider creating a chart of the artifacts running in each host. This will also help determine if too many items are running in a host or if a host is being underutilized."
BizTalk360 (http://www.biztalk360.com) tackles this exact issue seamlessly by giving a container view for the BizTalk Host, you'll know exactly what's running inside the host. The blog post explains this functionality, please take a look at the topic "4. Host Container View"
Sorry, Saravana I made a typo I definitely want to communicate that BizTalk360 and MBV go hand in hand.
Mandi- Added reference of PAL also whcih i found very usefull for me.
In addition to this, creating an internal WIKI or sharepoint site to keep track of all applications, known error and with solution is also a good tip.. :)
I felt like adding two more points that are very important, keeping a good framework and disaster recovery plan of the environment. Other than that, a very good article, will be useful for many people! Great work Mandi!