|
Explain the purpose of BizTalk Orchestration XLANG Scheduler Engine.XLANG schedule running instances: Instantiation, execution, dehydration (occurs when the XLANG Scheduler Engine has to wait for greater than three minutes to receive a message) and re-hydration (occurs when the message arrives to the XLANG Scheduler Engine) are controlled by the XLANG Scheduler Engine.
When that instance is dehydrated, the current state of an XLANG schedule instance is saved to a SQL Server persistence database. After being instantiated, the XLANG Scheduler Engine continues the business process sequence until it becomes necessary to dehydrate the XLANG schedule. The XLANG Scheduler Engine re-hydrates on the arrival of a message. The XLANG schedule instance and business process sequence actions are continued to be performed till the schedule gets completed or till the XLANG Scheduler Engine waits for another message.Explain the purpose of BizTalk Orchestration XLANG Scheduler Engine.Activation, execution, dehydration and rehydration are controlled by XLANG Scheduler Engine. A small application can be created for passing the moniker of an XLANG schedule to the XLANG Scheduler Engine for activating XLANG schedule. The XLANG Scheduler Engine performs various actions within the XLANG schedule and the business process sequence can be continued until the dehydrating the XLANG schedule becomes necessary. When XLANG scheduler engine expects to wait for more than 3 minutes to receive a message, dehydrating an XLANGL schedule occurs. At the time of message arrival, the XLANG scheduler engine rehydrates the XLANG schedule instance and continues to perform all the actions in the business process sequence. This process continues until the schedule is completed or the XLANG schedule engine needs to wait for other message. For supporting dehydration, a persistence database must be configured.
|
