BizTalk 2013 Recipes: A Problem-Solution Approach (Expert's Voice in BizTalk)
Mark Beckner, Kishore Dharanikota
Format: PDF / Kindle (mobi) / ePub
BizTalk 2013 Recipes provides ready-made solutions to BizTalk Server 2013 developers. The recipes in the book save you the effort of developing your own solutions to common problems that have been solved many times over. The solutions demonstrate sound practice, the result of hard-earned wisdom by those who have gone before.
Presented in a step-by-step format with clear code examples and explanations, the solutions in BizTalk 2013 Recipes help you take advantage of new features and deeper capabilities in BizTalk Server 2013. You’ll learn to integrate your solutions with the cloud, configure BizTalk on Azure, work with electronic data interchange (EDI), and deploy the growing range of adapters for integrating with the different systems and technologies that you will encounter.
You’ll find recipes covering all the core areas: schemas, maps, orchestrations, messaging and more. BizTalk Server 2013 is Microsoft’s market-leading platform for orchestrating process flow across disparate applications. BizTalk 2013 Recipes is your key to unlocking the full power of that platform.
functionality were removed in BizTalk 2010. The most notable was the Health and Activity Tracking (HAT) application and the ability to do administration of ports and orchestrations directly from Visual Studio using BizTalk Explorer. These were both central to a developer’s everyday use of BizTalk, and in many respects, it is unfortunate that these tools are gone. Everything is now centralized in the BizTalk Administration Console, and most of the functionality of HAT and BizTalk Explorer became
is message context. The message context includes all the instance-specific and exchange-specific data fields and essentially is the metadata that the messaging engine of BizTalk Server uses to process messages. As previously noted, instance-specific properties are those that pertain to a specific message instance, and they must be promoted explicitly during development. A common example of this type of property is an XML element containing a unique ID, which may capture an important data field
business process. Orchestrations can handle messages dynamically by interrogating promoted properties that hold key metadata elements of a message. For example, sales orders being delivered domestically may need to be handled differently than those being sent overseas. By capturing the destination country of an order in the document schema and flagging the element as a promoted property, this data element can easily be used as a decision point in the orchestration. Domestic orders could be
after the message is sent. • Dynamic one-way port: Dynamic indicates that properties will be set at runtime to define the ultimate destination of the message. One-way indicates that there will be no response back to BizTalk after the message is sent. • Dynamic solicit-response port: Dynamic indicates that properties will be set at runtime to define the ultimate destination of the message. Solicit-response indicates that there will be a response back to BizTalk after the message is sent.
Studio. 2. As shown in Figure 2-1, right-click the project name in the Solution Explorer and select Add ➤ Add New Item. Figure 2-1. Adding an item from the Solution Explorer 38 Chapter 2 ■ Document Schemas 3. The Add New Item dialog box will appear, as shown in Figure 2-2. Select Schema as the type of item, type in a name for the item, and click OK. Figure 2-2. Add New Item dialog box 4. To change the name of the root node, right-click the node, and select Rename. 5.