BizTalk Server Orchestration - Orchestration is getting dehydrated

Author

Orchestration is getting dehydrated

Sourav Dutta Gupta

2006-05-02, 1:19 am

Hi,

We are having problem with Orchestrations containing Loops and Delay shapes.
Our requirement is such that we need to call web services through our
orchestration. In doing so sometimes we need to implement pooling inside our
Orchestration, i.e., we need to send request continuously based on a specific
status code obtain from the response. And those pool request expects a time
gap of 2 secs, which we have provided by including a Delay shape. What we are
observing that sometimes while pooling the Orchestration is getting
Dehydrated. In the Orchestration designer we found that it is getting stuck
in the delay shape. We are really confused to find the exact problem. Is it a
problem with our design or in the service? How to track that?

Could any one give the solution?

Sam Vanhoutte

2006-05-04, 7:26 am

> What we are
> observing that sometimes while pooling the Orchestration is getting
> Dehydrated. In the Orchestration designer we found that it is getting
> stuck
> in the delay shape. We are really confused to find the exact problem. Is
> it a
> problem with our design or in the service? How to track that?

Dehydration is really what you need. This is BizTalk internally serializing
the state of your orchestration back to the messagebox database. This is
necessary to be high available. An orhcestration that was running on
server1 can be rehydrated on server2 (if they have the same hosts). If a
server is going down, you still have the state of your process in the
database.
Dehydration is done on receive/send shapes, delays, etc... Everything that
is in an atomic scope will be executed in memory, no dehydration takes place
there.

Best regards

Sam Vanhoutte
www.codit.be