BizTalk has many different application states. Understanding these states can be the difference between being a genius and a scapegoat. Modification of a BizTalk state is usually the result of an action that has taken place. In many cases, altering these states is due to an upcoming deployment, and we need to ensure that we allow messages that are currently being processed to complete without letting new messages into the BizTalk application. I am sure there are many horror stories out there about an inexperienced admin who accidently terminated some inflight messages because they did not understand these states.
There are three Runtime Application states. Setting these states is usually based upon explicit actions by an administrator, but can also occur if system resource(s), such as a source system, is not available. Do note that the following states do not account for Host Instances being online or offline. We can have an application...