Biztalk Schema Interview Preparation Guide

Download PDF

It can be but it should be avoided in the projects that uses BizTalk EDI engine as during run time there can be conflicts with this and expected results might not be seen.

Yes, it is possible, both are the ways to utilize already existing schema. The only condition is the schema which is included should have same TargetNamespace or no namespace.

Property schema is a special type of schema, not created to describe messages. Instead, it describes context properties. It consists of only child node under a root node.

It's a node within a BizTalk Server schema that represents the outermost XML element in the business document specified by the schema.

It is a script which when run installs the BizTalk Schema Generator. It is used when generating a schema from existing items. It's likely to get error first time or after updates "WFX to XSD Schema generation module is not installed". Then this script can be used to install the schema generator.

Long running transaction support CD properties of ACID. It is not practical to lock transaction for a long time. This transaction can run indefinitely and can be dehydrated also.

An <Any> element in a schema designates a specific location in the schema where new elements or attributes can be added. When BizTalk uses the schema to process a message containing unknown elements or attributes in the designated location, the schema will still consider the message valid.

Correlation types define a set of properties on which you will be correlating messages. These can be any properties which were previously defined in a property and deployed with some BizTalk Project including "system" properties deployed with the GlobalPropertySchemas Jump which is installed as part of the base BizTalk install. A correlation set defines a set of properties and values for these properties that a message must contain to be processed by a particular orchestration.

BizTalk uses a combination of namespace#rootnode to define the schema type of a message, thereby making a MessageType unique (for example: http://mynamespace.com#MyRootNode). In other words, BizTalk uses this combination to identify and resolve schemas references.

An Orchestration can have more than one instance running simultaneously. Even though each of those multiple instances perform the same action, it does it on different data contained within a message. Correlation is a process of associating an incoming message with the appropriate instance of an orchestration. For Example: If your orchestration issues a purchase order, receives an invoice, and sends a payment, the developer must make certain that the invoice message is received by the orchestration instance which corresponds to the orchestration that sent the Purchase Order. Without correlation, it would be possible to send out an invoice for thousands of items even though the purchase order is for one.

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.

By default, the BizTalk Editor will set the namespace of a schema to http://ProjectName.SchemaName.

The Distinguished field is an XPath alias to the field.To create it , right-click the element-->Promote-->Show promotion-->Add

BizTalk Editor resides within the Microsoft Visual Studio shell. Some of the functionality within BizTalk Editor relies upon existing user interface elements within the Visual Studio shell.

BizTalk can automatically create the schema from DTD, well formed XML, XDR. To do this schema generator is used.

These are all node properties.
☛ Group Max Occurs: Specifies the maximum number of times that to the underlying group content of the selected All Group node can occur.
☛ Group Min Occurs: Specifies the minimum number of times that the underlying group content of the selected All Group node can occur.
☛ Max Occurs: Specifies the maximum number of times that the element corresponding to the selected Record node can occur.
☛ Min Occurs: Specifies the minimum number of times that the element corresponding to the selected Record node can occur.

Yes, as long as they are not in the same scope.

There are various options but BizTalk always uses UTF-16 encoding for their schemas.

Right-click the project in Solution Explorer and select Add Generated Items --> Generate Schemas.

Yes, it's possible to create custom data types and it can be used across the 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.

When an orchestration has been idle for a while, the orchestration engine will save the state information of the instance and free up memory resources.

It follows full ACID properties Atomicity, Consistency, Isolation and Durability. If you require full ACID properties on the data for example, when the data must be isolated from other transactions. You must use atomic transactions exclusively. When an atomic transaction fails, all states are reset as if the orchestration instance never entered the scope.

When a message is received, or else when a timeout has expired, the orchestration engine can be automatically triggered to rehydrate the instance – it is at this point that the orchestration engine loads the saved instance of the orchestration into memory, restores the state, and runs it’s from the point it left off.

Yes. http://schemas.microsoft.com/BizTalk/2003 and http://www.w3.org/2001/XMLSchema are added by BizTalk when creating a schema.

255 characters