Biztalk Interview Questions and Answers
Question - 121 : - When you use Call Orchestration shape vs Start Orchestration shape?
Answer - 121 : -
A Call Orchestration returns the control back to the caller. A Start Ochestration shape starts the orchestration in a non-deterministic way.
Question - 122 : - Does BizTalk Orchestrations support recursion?
Answer - 122 : -
An Orchestration does NOT support recursion.
Question - 123 : - What is the purpose of the property “Activate” in a Receive shape?
Answer - 123 : -
It is used to invoke a new instance of an Orchestration.
Question - 124 : - Can an orchestration Start without an Activatable receive?
Answer - 124 : -
A Nested Orchestration can be started without an Activatable receive
Question - 125 : - Is it necessary for all .NET components being called from an Orchestration be Serializable?
Answer - 125 : -
Yes, it is necessary. There are cases where a .NET component need not be Serializable.
Question - 126 : - When do we need set the property “Synchronized” = true for a scope?
Answer - 126 : -
This needs to be set, when a variable is shared across the branches of a parallel shape.
Question - 127 : - How does one enable Correlations in BizTalk?
Answer - 127 : -
First create a Correlation type and then create an instance of it.
Question - 128 : - What is Hosts and Host Instances?
Answer - 128 : -
- A host is a logical representation of a Microsoft Windows process that executes BizTalk Server artifacts such as send ports and orchestrations. A host instance is the physical representation of a host on a specific server.
- A host can be either an in-process host, which means it is owned and managed by BizTalk Server, or an isolated host, which means that the BizTalk Server code is running in a process that is not controlled by BizTalk Server. A good example of an isolated host is Internet Information Services (IIS), which hosts the receive functionality of the HTTP and SOAP adapters.
- Hosts are defined for an entire BizTalk Server group; a collection of BizTalk Servers that share configuration, MessageBoxes, ports, and so on.
Question - 129 : - What is a Message Type (i.e. BTS.MessageType) and how is it used in BizTalk?
Answer - 129 : -
Message Type is a BizTalk System property that is promoted inside a Pipeline. It is made up of Document Name Space # Root Node Name.
Question - 130 : - What are different types of BizTalk Schemas?
Answer - 130 : -
- XML schema: An XML schema defines the structure of a class of XML instance messages. Because this type of schema uses XML Schema definition (XSD) language to define the structure of an XML instance message, and this is the intended purpose of XSD, such schemas use XSD in a straightforward way.
- Flat file schema: A flat file schema defines the structure of a class of instance messages that use a flat file format, either delimited or positional or some combination thereof. Because the native semantic capabilities of XSD do not accommodate all of the requirements for defining the structure of flat file instance messages—such as the various types of delimiters that might be used for different records and fields within the flat file—BizTalk Server uses the annotation capabilities of XSD to store this extra information within an XSD schema. BizTalk Server defines a rich set of specific annotation tags that can be used to store all of the required additional information.
- Envelope schema: An envelope schema is a special type of XML schema. Envelope schemas are used to define the structure of XML envelopes, which are used to wrap one or more XML business documents into a single XML instance message. When you define an XML schema to be an envelope schema, a couple of additional property settings are required, depending on such factors as whether there is more than one root record defined in the envelope schema
- Property schema: A property schema is used with one of the two mechanisms that exist within BizTalk Server for what is known as property promotion. Property promotion is the process of copying specific values from deep within an instance message to the message context. From the message context, these values are more easily accessed by various BizTalk Server components. These components use the values to perform actions such as message routing. Promoted property values can also be copied in the other direction, from the more easily accessible message context back into the depths of the instance message, just before the instance message is sent to its destination. A property schema is a simple version of a BizTalk schema that plays a role in the process of copying promoted properties back and forth between the instance message and the message context.