SummaryYou've learned several important features about BizTalk Orchestration in this chapter. You started with an exploration of orchestration transactions, and the three transaction styles-short-lived, long-running, and timed-and you saw their application in different business scenarios. You also learned about XLANG Schedule throttling, a useful feature that allows you to control how many active XLANG Schedule instances are running at a time, hence controlling how much resources can be used for each type of orchestration on the system. This feature significantly boosts the scalability of XLANG Schedules on BizTalk Server. You learned about orchestration correlation features, which allow you to correlate documents to their corresponding XLANG Schedule instances, and you also learned about dehydration and rehydration of XLANG Schedules, which are BizTalk Server's way of persisting running schedules to disk to free up system memory used by the schedules, boosting the system resources on that server. Combining the dehydration/rehydration feature, orchestration correlation, and long-running transaction support in BizTalk Orchestration, you have an excellent solution for handling large amounts of workflow that can take hours or even days to complete, while still using minimum amounts of system resources. Dynamic ports is another feature covered in this chapter that adds value to BizTalk Orchestration. With dynamic ports, your orchestrations now have the ability to decide where to send the document at runtime, as opposed to having to specify the destination at design time. Last, but not least, you looked at how to leverage Web services with BizTalk Orchestration. You looked at a sample stock quote service that exposes the services of an orchestration as aWeb service, hence making the services of BizTalk Orchestration available to multiple clients across the Internet at the same time. In the next chapter, I'll show you what BizTalk Server offers from a programming perspective, and what you can achieve with BizTalk Server APIs.