What is message type and what is use?
It is defined as a document schema name space and document root node. format as <DocNameSpace>#<RootNodeName> . if there is no Document namespace then message type will be <Root Node name>
Based on Schema, BizTalk generate the message type. This message type is used in subscriptions, making it invaluable for the MessageBox for deciding what orchestrations and send ports should receive a published message. It is a property of Biz Talk system which is promoted in a pipeline. It is developed by using Document Name Space # Root Node Name. The message types manage the metadata, also called content properties which are used for creation of filters on send ports and a criterion named orchestrations-subscription is queried against the metadata
How to de-batch message or what is envelope schema.
BizTalk supports de-batching of xml envelopes out of box by leveraging the envelope property and the Body XPath property. And this need to be setup on receive pipeline XML disassembler component. For more details click here.
Can an Envelope schema consist of more than one schema type?
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.
Yes. Technically it is possible an Envelope schema can consist of more than one schema type.
How to handle fault message while de-batching (Recoverable Interchange Process)
This property is used to let you decide whether to suspend an entire batch of messages if at least one de-batched message fails in the disassemble or whether to allow the valid messages to be published and to suspend only the failed messages.
How many types of schemas?
- FlatFile Schema
- Property Schema
- FlatFile Schema Wizard
- JSON Schema Wizard
What Is Promoted Property in BizTalk Server?
The promotion of Prompted Fields/Properties is done in the message context by a pipeline called receive pipeline at the time when a message is received on a port. This task is performed by dis-assembler pipeline component (XML or a flat file dis-assembler). In addition to it, custom pipeline component could also be performing it. Click here for more details
Difference between distinguish field and promoted properties
Property Promotion in BizTalk is usually about taking values from incoming message and moving them into the context of the message, so they are easily accessible and usable for routing. And Distinguish field is mainly used in Orchestrations .
What is the difference between a Document Schema and a Property Schema?
A document schema is like any regular schema, whereas a Property schema consists of only child elements under a root node.
Document Schema is basically XML schema. An XML schema describes a business document that is represented in XML. Because Microsoft BizTalk Server uses XML as its canonical representation for business documents, inbound and outbound documents do not require any translation.
Property Schema in BizTalk is usually about taking values from incoming message and moving them into the context of the message, so they are easily accessible and usable for routing. 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. this schema specifies an unstructured collection of fields into which you can promote fields from within an instance message defined by a schema associated with your property schema.
What is the maximum length allowed for promoted properties?
What is the maximum length allowed for Distinguished fields?
It can be of any length, no limits.
What is the difference between complex type and simple type?
Simple element types will not contain other elements, they only contain data. Complex types define the organization of elements that contain other elements
How to handle json file in BizTalk
From BizTalk 2013 R2 & upper version, BizTalk also provides in-build REST service capability. Before this, there was required custom coding for Json file and rest services. Now it’s easy to create schema from Json file.
How to import schema
- In BizTalk Editor, open the schema to which you want to import, include, or redefine another schema. You can open a schema by double-clicking it in Solution Explorer.
- Select the Schema node at the top of the schema tree view.
- If necessary, press F4 to open the Visual Studio Properties window.
- In the Properties window, in the Advanced category, in the value portion of the Imports property, click the ellipsis (…) button.
- In the Imports dialog box, in the Import New Schema as list, select XSD Import, XSD Include, or XSD Redefine, as appropriate, and then click Add.
- In the BizTalk Type Picker dialog box, expand the Schema node in the project tree, select the schema that you want to import, include, or redefine, and then click OK.
- In the Imports dialog box, click OK.
How to Create Schemas That Use Other Schemas
XML Schema definition (XSD) language provides three different but related mechanisms for using one schema within another schema Click here for more details. These mechanisms are as bellow:
- Importing a schema
- Including a schema
- Redefining a schema
What is the difference between xsd:include and xsd:import?
The import element allows you to use schema components from any schema; The include element allows you to add all the components of an included schema to the containing schema.
- Use xsd:include to bring in an XSD from the same or no namespace.
- Use xsd:import to bring in an XSD from a different namespace.
What are un-typed messages, how does one create them?
A message created in BizTalk Orchestration is bound to a schema, this is a typed message. In un-typed messages, the message is bound to System.Xml.XmlDocument instead of a schema.
Can BizTalk have same schema in different application, or this question can be asked as can BizTalk have same message type for multiple applications
Its answer is yes, and it can be achieved by two ways:
- Create common schemas for multiple application and add this schema project in reference in respective application to use the schema
- Set up schema in Receive pipeline Xml Disassembler stage DocumnetSpecNames, for more details click here
What is canonical schema?
A canonical schema is a design pattern, which is applied within service oriented paradigm, and within BizTalk server context establish loose coupling between systems. Through performing transformation of messages from one system to canonical schema and from canonical schema to message of another system, systems have no direct relation with each other. Canonical schema can also be viewed as an internal schema in BizTalk and aid you in structuring your solution through best practice of creating separate projects for maps, orchestrations, internal and external schemas. Another advantage of using a canonical schema is that it reduces the number of transformations you need. If you need a to map a few types of inbound message coming from different parties to a few outbound messages, you can create a map to your canonical schema for each inbound schema and then a map from your canonical schema to each outbound schema. If for example you have three types of incoming that needs to be mapped to three types of outgoing messages, you will only need to build and maintain six maps instead of nine.
Can a flat file message be processed without a pipeline?
A Pipeline’s job is to convert any external format into XML, be it a flat file or EDI or anything else.
How to handle array list json file in BizTalk
JSON schema Wizard does not provide schema creation for array-list json files. for arraylist json file you need to create custom pipeline. Click here for custom pipeline for below requirement
What is <Any> element in schema?
Any Element node to indicate a location within an instance message where unknown elements may appear. Sometime there is not specified element or attribute or record in the schema, in that case you can use <any> element. It can process unknown element or attribute. 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.
Having an element like this will allow you to put anything in your XML at this point, but validation is not possible, because the schema has no description of what might appear.
Below links are available for other segment of Interview questions and Answers:
- Interview Questions And Answers – BizTalk Development Activity
- Interview Questions And Answers – BRE
- Interview Questions And Answers – Pipelines
- Interview Questions And Answers – Orchestration
- Interview Questions And Answers – Mapping
- Interview Questions And Answers – BAM
- Interview Questions And Answers – BizTalk Admin Console
- Interview Questions And Answers – BizTalk Architecture