Using dynamic service ports

In all the BizTalk solutions we've built so far in this book, the focus was on static ports with URIs set immediately after the code was deployed. However, there exist a number of legitimate cases where BizTalk does not know where to distribute a message until additional runtime-only context is provided. For example, when you configure a send port with an SMTP adapter in BizTalk Server, you are required to explicitly provide the recipient's email address. Any time this port is invoked, that particular email address is applied. But what if the corresponding message could be emailed to any of a number of addresses? You could choose to set up a series of static send ports and summon each one individually, based on decision logic from the orchestration. However, this is not a particularly flexible mechanism as it requires changes to the orchestration whenever an email target is added or removed. A better strategy is to apply dynamic ports and perform a runtime query...