Explore topic-wise InterviewSolutions in Current Affairs.

There are various OPTIONS but BizTalk ALWAYS USES UTF-16 ENCODING for their SCHEMAS

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

• By default, BizTalk SERVER will EXAMINE only the namespace and the root node name of a message to identify and validate the SCHEMA, and will not detect extra elements in the message body.
• To perform a deep validation of a message format, you have to create a Custom Pipeline with the XML Disassembler COMPONENT

• BizTalk uses a COMBINATION of namespace#rootnode to DEFINE the schema type of a MESSAGE, thereby making a MessageType unique.
• In other words, BizTalk uses this combination to IDENTIFY and resolve schemas REFERENCES.

It's a node within a BizTalk Server SCHEMA that represents the outermost XML ELEMENT in the business DOCUMENT specified by the schema.

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

• 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.

DISTINGUISHED FIELD is a XPath alias to the field.To create it , right click the element-->Promote-->SHOW promotion-->Add

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

It can be of any LENGTH, no LIMITS.

It can be of any length, no limits.

255 CHARACTERS

255 characters

No. To PROMOTE XML RECORD its ContentType PROPERTY should be SET SimpleContent.

No. To promote XML record its ContentType property should be set SimpleContent.

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.

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.

• It is a script which when run installs the BIZTALK Schema Generator.
• It is USED when generating 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.

Right click the project in SOLUTION Explorer and SELECT Add GENERATED Items --> GENERATE Schemas.

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

• 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.

• Each message in BizTalk Server is considered a multi-part message and is MADE up of zero or more parts.
• Each message with one or more parts has one of these parts identified as the body part.
• Each part consists of a binary chunk of data which can represent an XML DOCUMENT, a flat FILE, a serialized .NET CLASS, or other binary stream of data.
• You use the body part of the message to identify the TYPE of the message that can be used for routing.

CUSTOM Date/time PROPERTY is only AVAILABLE for flat FILE schema.

Custom Date/time property is only available for flat file schema.

Yes, we can have a SCHEMA without target namespace and it's MESSAGE type will be the Root NODE.

Yes, we can have a schema without target namespace and it's message type will be the Root node.

• 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.

• 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 schema and deployed with some BizTalk Project including "SYSTEM" properties deployed with the GlobalPropertySchemas 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.

• A canonical SCHEMA is a design pattern, which is applied within a service oriented paradigm, and within BizTalk server context establish the loose coupling between systems.
• Through performing the TRANSFORMATION of messages from one system to canonical schema and from the canonical schema to message of another system, systems have no direct relation with each other.
• The 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.

Use the BLOCK DEFAULT PROPERTY to prevent or restrict the types of derivatives that can be used in instance messages for all data types defined by the schema being EDITED.

Use the Block Default property to prevent or restrict the types of derivatives that can be used in instance messages for all data types defined by the schema being edited.

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.

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.

XS:STRING

xs:string

• 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.

• YES, a schema (XSD) can have multiple root nodes.
• In case you have a schema with multiple root nodes you will end up with multiple message TYPES DECLARED in BizTalk,one for every root node.
• So when you want to create a message you will NEED to specify exactly which message type you are GOING to use! 

YES, as LONG as they are not in the same SCOPE.

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

YES, it's possible to CREATE CUSTOM data TYPES and it can be used ACROSS the schema. 

Yes, it's possible to create custom data types and it can be used across the schema. 

Target Namespace is to schema what a namespace is to .NET OBJECT and root NODE as a class name.

Target Namespace is to schema what a namespace is to .Net Object and root node as a class name.

• 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.

• 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 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.

The schema is basically a CONTRACT of your message and DEFINES it. The XML Schema definition (XSD) language defines the structure of an XML instance message, and this is the intended purpose of XSD, such SCHEMAS USE XSD in a straightforward way.

The schema is basically a contract of your message and defines it. The XML Schema definition (XSD) language defines the structure of an XML instance message, and this is the intended purpose of XSD, such schemas use XSD in a straightforward way.

The schema is basically a contract of your message and defines it. The XML Schema definition (XSD) language defines the structure of an XML instance message, and this is the intended purpose of XSD, such schemas use XSD in a straightforward way.

The schema is basically a contract of your message and defines it. The XML Schema definition (XSD) language defines the structure of an XML instance message, and this is the intended purpose of XSD, such schemas use XSD in a straightforward way.