These are the list of interview questions which every BizTalk 2004/2006 developer needs to know and answer
BizTalk is essentially Asynchronous. It can exhibit some synchronous behavior, if an Orchestration is converted into a web service.
Please refer to this article New functoids in BizTalk 2006
A document schema is like any regular schema, whereas a Property schema consists of only child elements under a root node.
Yes. Technically it is possible.
A Pipeline's job is to convert any external format into XML, be it a flat file or EDI or anything else.
It is possible to process multiple messages, without an envelope.
When a property is Promoted, it is exposed to the orchestration/send port filters etc.
The rule here is, if you dont want the schema element to appear in send port filters/debugging information then make it a distinguished field.
A message type consists of the TargetNamespace#RootElement name.
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.
Refer to Binding models in BizTalk
A filter on the Send Port is the first step to enable subscriptions in BizTalk.
Refer to the article known as "Convoy Deep Drive" on MSDN
A 'Delay' is very much similar to a sleep on the current thread. A 'Listen' shape is used to wait for an incoming resource, with a timeout period.
A Call Orchestration returns the control back to the caller. A Start Ochestration shape starts the orchestration in a non-deterministic way.
A "Message Assignment" shape is used to create a new message and assign values to it. A Expression shape is used to assign values to variables and also write 'if' conditions.
An Orchestration does NOT support recursion.
It is used to invoke a new instance of an Orchestration.
A Nested Orchestration can be started without an Activatable receive
Yes it is necessary. There are cases where a .NET component need not be Serializable.
This needs to be set, when a variable is shared across the branches of a parallel shape.
Refer to HOW To Compensate a Transaction in a BizTalk Orchestration
Refer to Parallel Branching and Scoping in BizTalk Orchestrations - Advanced Concepts
First create a Correlation type and then create an instance of it.
Refer to Parallel Branching and Scoping in BizTalk Orchestrations - Advanced Concepts
Refer to HOW To Compensate a Transaction in a BizTalk Orchestration
Refer to HOW To Compensate a Transaction in a BizTalk Orchestration
It is NOT possible, since it forms a cyclic dependency.
The Incoming data format, The Business process and The Outgoing data format.
Refer to Using the MSI installer wizard for deploying applications created in BizTalk Server 2006
| You must Sign In to use this message board. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
