Orchestration Statuses
I was surprised to find out there's some confusion around the possible statuses a deployed orchestration can be in, but after spending 20 minutes browsing MSDN I realised I simply couldn't find one clear description of those, so here's my attempt -
An orchestration deployed into BizTalk server can be in one of four states -
An orchestration deployed into BizTalk server can be in one of four states -
- Unenlisted (unbound) – the process has been deployed to the server, but is unconfigured (host and/or port bindings are not set), unsubscribed and is not running.
- Unenlisted (bound) - the process is configured, but is still unsubscribed and is not running.
- Enlisted (stopped) – the process is fully configured, subscriptions have been created, but it is stopped.
- Started – process is ready to run (and will do so when activated by a message)
Labels: Admin console, BizTalk, orchestration
2 Comments:
Hi Yossi,
what is the reason for the first option:
Unenlisted (unbound).
After I import the application.msi file and then import the bindings it should not have been unenlisted unbound state. What could be the issue here.
Thanks,
Sunil
By
sunil, at 24/05/2011, 11:51
If after importing a binding file your process is still Unenlisted (Unbound) chances are that the binding file did not contain configuration for that process.
By
Yossi Dahan, at 29/05/2011, 08:10
Post a Comment
<< Home