Book Image

(MCTS): Microsoft BizTalk Server 2010 (70-595) Certification Guide

By : Johan Hedberg, Kent Weare , Morten la Cour
Book Image

(MCTS): Microsoft BizTalk Server 2010 (70-595) Certification Guide

By: Johan Hedberg, Kent Weare , Morten la Cour

Overview of this book

<p>Microsoft BizTalk Server 2010 is an Integration and connectivity server solution that enables organizations to easily connect disparate systems. Developing Business Process and Integration Solutions by Using Microsoft BizTalk Server 2010 (70-595) is the certification exam for professionals who need to integrate multiple disparate systems, applications, and data as well as automate business processes by using BizTalk Server.<br /><br /><i>(MCTS): Microsoft BizTalk Server 2010 (70-595) Certification Guide</i> will show you how to prepare for and pass the Microsoft BizTalk Server 2010 (70-595) exam and become a Microsoft Certified Technology Specialist (MCTS) in Microsoft BizTalk Server 2010. <br /><br />Packed with practical examples and Q&amp;As, <i>(MCTS): Microsoft BizTalk Server 2010 (70-595) Certification Guide</i> covers the keys skills in the exam and starts by showing you how to configure a Messaging Architecture. The book then dives into BizTalk Artifacts such as creating Schemas and Pipelines, creating Maps and creating Orchestrations. It then moves on to topics such as debugging and exception handling, deploying, tracking and administrating a BizTalk Server 2010 solution, integrating Web Services and Windows Communication Foundation (WCF) Services and implementing Extended Capabilities. Additional practical resources are also included that will enable you to approach the Microsoft BizTalk Server 2010 (70-595) exam with ease, including certification test taking tips and tricks and sample certification test questions.</p>
Table of Contents (18 chapters)
(MCTS): Microsoft BizTalk Server 2010 (70-595) Certification Guide
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface

Developing BizTalk Artifacts


  1. 1. Answer: b

    A distinguished field is used only to create an alias for xpath statements for expressions in Orchestrations. The Body xpath property of the root node is used with envelope Schemas to point out the node that contains the body of the document. Changing the Default Property Schema Name property on the schema file only affects what the filename of the created property schema will be when you do a Quick Promotion.

  2. 2. Answer: c

    The Pre-assemble and Assemble stage are stages in a send Pipeline and would do nothing to affect the XML in a receive. Therefore the Decode stage, the Receive Pipeline stage before the Disassemble stage (that throws the exception), is correct.

  3. 3. Answer: c

    Maps are configured on Receive Ports. As the Orchestration needs the canonical format you need a Map that transforms to the canonical format. As the files are received into BizTalk, configuring a Send Port is pointless. Pipelines in general, the XMLReceive Pipeline or the Validate document structure property of the XML Disassembler has nothing to do with Maps.

  4. 4. Answer: d

    As both the external component and the Orchestration are .NET components, they will load into the Host Instances memory. When they are updated on disk or in the GAC they will not be refreshed unless the Host Instances are restarted (or a sufficient amount of time passes for the assemblies to unload). Storing the value in BizTalk's configuration file also requires a Host Instance restart for the BizTalk Server to retrieve the new value as the config file is read only when the service starts.

  5. 5. Answer: a

    Scope and their Synchronized property ensure that data being read is not simultaneously written to by other branches of a Parallel shape. It has nothing to do with this scenario. As we are sending a message out and receiving a response we need to initialize the correlation set on the Receive shape and follow it on the Send shape. The Ordered Delivery property makes sure that messages are delivered to the Orchestration in the same order that they were written to the MessageBox.