Microsoft BizTalk Server, often referred to as simply "BizTalk", is an Enterprise Service Bus. Through the use of "adapters" which are tailored to communicate with different software systems used in an enterprise, it enables companies to automate business processes. Created by Microsoft, it provides the following functions: Enterprise Application Integration, Business Process Automation, Business-To-Business Communication, Message broker, and Business Activity Monitoring. Recently the BizTalk Server is repositioned not only as the Application Integration Server but also as the Application Server.
In a common scenario, BizTalk enables companies to integrate and manage automated business processes by exchanging business documents such as purchase orders and invoices between disparate applications, within or across organizational boundaries. Human-centric processes cannot be implemented directly with BizTalk Server and need additional applications like Microsoft SharePoint server.
Development for BizTalk Server is done through Microsoft Visual Studio. A developer can create transformation maps transforming one message type to another (for example an XML file can be transformed to SAP IDocs, etc.). Messages inside BizTalk are implemented through the XML documents and defined with the XML schemas in XSD standard. Maps are implemented with the XSLT standard. Orchestrations are implemented with the WS-BPEL compatible process language xLANG. Schemas, maps, pipelines and orchestrations are created visually using graphical tools within Microsoft Visual Studio. The additional functionality can be delivered by .NET assemblies that can be called from existing modules—including, for instance, orchestrations, maps, pipelines, business rules.
Contents |
The following is an incomplete list of the technical features in the BizTalk Server:
The BizTalk Server runtime is built on a publish/subscribe architecture, sometimes called "content-based publish/subscribe". Messages are published into the BizTalk, transformed to desired format, and then routed to one or more subscribers.[3]
BizTalk makes processing safe by serialization (called dehydration in Biztalk's terminology) messages into a database while waiting for external events, thus preventing data loss. This architecture binds BizTalk with Microsoft SQL Server. Processing flow can be tracked by administrators using an Administration Console. BizTalk supports the transaction flow through the whole line from one customer to another. BizTalk orchestrations also implement long-running transactions.
See.[4] BizTalk uses adapters for communications with different protocols, message formats, and specific software products. Some of the adapters are: EDI, File, HTTP, FTP, SFTP, SMTP, POP3, SOAP, SQL, MSMQ, Microsoft SharePoint Server, IBM mainframe zSeries (CICS and IMS) and midrange iSeries (AS/400) server, IBM DB2, IBM WebSphere MQ adapters. The WCF Adapter set[5] was added with 2006 R2. It includes: WCF-WSHttp, WCF-BasicHttp, WCF-NetTcp, WCF-NetMsmq, WCF-NetNamedPipe, WCF-Custom, WCF-CustomIsolated adapters. Microsoft also ships a BizTalk Adapter Pack that includes WCF-based adapters for Line of Business (LOB) systems. Currently, this includes adapters for SAP, Oracle database, Oracle E-Business Suite, Microsoft SQL Server, MySQL, PeopleSoft Enterprise and Siebel Systems.
The main competitors are: