The BizTalk Framework is a set of guidelines for driving the consistent adoption of XML to enable e-Commerce and application integration.
It is initiated by Microsoft and supported by a wide range of organizations.
The BizTalk Framework is an open framework for B2B exchange, It is implemented across all major platforms and most major B2B products.
BizTalk provides costs savings when used in internal IT projects and can be used in externally focused solutions too.
BizTalk Server 2000 is based on the BizTalk Framework. It provides the infrastructure and tools to enable B2B eCommerce and process integration.
BizTalk enables companies to integrate and manage business processes by exchanging business documents between business applications within or across organizational boundaries.
BizTalk has a website called www.biztalk.org which is a "repository" and "gateway" for BizTalk to enable dissimilar business applications to exchange structured documents with each other.
How many Biztalk Components are there?
BizTalk Server Administration
What is direct binding?
Direct binding in Biztalk Server 2004 can be used to send messages from one Orchestration to another and can also be used to send messages directly into the message box.
In Direct Binding, properties like BTS.SPID, BTS.ReceivePortID, etc are not exploited automaticaly by orchestration ports.
So, BizTalk does not manage the binding of orchestration ports to messaging Receive and Send ports.
Developers can control subscriptions and message context to route messages.
External binding configuration cannot be used with directly bound orchestration ports.
Direct binding is the most flexible model but You cannot configure your orchestration ports using binding files. More programming needs to be done to fully exploit the flexibility on offer.
Is there possible to make atomic transaction as two way communication?
No...Because atomic doesn't have property to maintain
Explain Message Type (i.e. BTS.MessageType) and how is it used in BizTalk?
Message Type 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. Messaging engines are prompted by these properties. Disassembler pipeline prompts BTS Message Type during parsing the message and specifies the message type. It is defined as a document schema name space and document root node.