• Print
  • Share


  • Updated on 01 May 2018
  • 1 minute to read
  • Contributors

The BizTalk server uses a publish-subscribe messaging engine architecture and the heart of this architecture is the BizTalk MessageBox database (BizTalkMsgBoxDb). The message box is a Microsoft SQL server database that is responsible to store the messages, message properties, subscriptions, orchestration states, tracking data and many such information. A BizTalk server group may have one or more MessageBox databases into which the messages are written. Service Instances and States When a message enters the BizTalk server, the service instances (receive ports, orchestrations, send ports) process the messages and there are occasions when the service instances can move to different states such as:

  • Ready to Run
  • Active
  • Dehydrated
  • Completed
  • Suspended (Resumable)
  • Suspended (Non-Resumable)
  • Pending

For instance - when the message is being sent to an external web service and the service is unavailable; the send port service instance will try its maximum to send the message to the endpoint. If the message can't be sent, the send port will use the Retry mechanism to send the message again after some time. If the retry mechanism fails as well, the send port service instance will suspend itself with the Suspended (Resumable) state. This means that when the web service is up and running at a later point in time, the administrator can resume the service instance to send the message. There may be situations when the service instance will suspend itself to a non-resumable state, which means the message can no longer be processed. In this case, the administrator has no other choice but to terminate the service instance.

Was this article helpful?