Enlist, Unenlist, Start and Stop BizTalk subscriber State | Uses and their difference with an example in BizTalk Server
Today I will explain very confusing BizTalk subscriber states i.e. enlist, unenlist, start and stop so lets begin with following details- Required: Atleast one receive location (Publisher). One or more orchestration (both Publisher and subscriber). Also atleast one send port (Subscriber). Enlist state: Enlist is prestate before Start subscriber state either in send port or in orchestration that means when we enlist a send port or orchestration then message publish at receive location then it firstly check subscriber (either send port or orchestration) and this case it is available in BizTalk MessageBoxDB but message will be not move further process. Its only available in suspended state with resumable condition. In short when we enlist send port or orchestration then it make availability in MessageBoxDB. Start state: If send port or orchestration is in Start state then when message received by receive location port then message is ready to move further process without g