Notes on Running XLANG Schedules
This section contains some notes on running and designing XLANG schedules. Also see Chapter 10 for using the Orchestration Designer and Chapter 13, “Advanced BizTalk Orchestration.”
Dehydrated schedules consume few precious system resources, such as CPU, memory, and semaphores. For an action that receives a message from an outside application, consider what wait time you want to assign. Any wait time less than 180 seconds causes the XLANG schedule to never dehydrate, unless the group manager is deliberately shut down. The default value is 0 seconds.
Use components that can persist to disk, where possible. This allows the XLANG Scheduler Engine the flexibility to dehydrate the schedules when appropriate. If the ...
Get BizTalk™ Unleashed now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
