Jump to content

Microsoft BizTalk Server

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by 212.159.196.72 (talk) at 10:49, 30 September 2016. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Microsoft BizTalk Server
Developer(s)Microsoft
Initial release19 December 2000; 23 years ago (2000-12-19)[1]
Stable release
2013 / 1 April 2013; 11 years ago (2013-04-01)[2]
Operating systemWindows 7 SP1, Windows 8, Windows Server 2008 R2 SP1, Windows Server 2012[2]
PlatformIA-32 or x64[2]
Size634.2 MB[2]
Available in9 languages[2]
List of languages
English, Chinese (Simplified), Chinese (Traditional), French, German, Italian, Japanese, Korean, Spanish
TypeApplication server
LicenseTrialware
Websitewww.microsoft.com/biztalk

Microsoft BizTalk Server (or simply "BizTalk") is an Inter-Organizational Middleware System (IOMS) [3] that enables companies to automate business processes, through the use of adapters which are tailored to communicate with different software systems used in an enterprise. Created by Microsoft, it provides enterprise application integration, business process automation, business-to-business communication, message broker and business activity monitoring.

BizTalk Server was previously positioned as both an application server and an application integration server[clarify]. Microsoft changed this strategy when they released the AppFabric server which became their official application server. Research firm Gartner consider Microsoft's offering one of their 'Leaders' for Application Integration Suites. While there is discussion of the product direction of BizTalk, especially with cloud software becoming more common, Microsoft continues to support and update the product and offer coverage at their popular conferences such as Worldwide Partner Conference.[4]

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.

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

History

Starting in 2000, the following versions were released:[5][6]

  • 2000 - BizTalk Server 2000
  • 2002 - BizTalk Server 2002
  • 2004 - BizTalk Server 2004 (First version to run on Microsoft .NET 1.0)
  • 2006 - BizTalk Server 2006 (First version to run on Microsoft .NET 2.0)
  • 2007 - BizTalk Server 2006 R2 (First version to utilize the new Windows Communication Foundation (WCF) via native adapter - (Release date 2 October 2007))
  • 2009 - BizTalk Server 2009 (First version to work with Visual Studio 2008)
  • 2010 - BizTalk Server 2010[7] (First version to work with Visual Studio 2010 and Microsoft .NET 4.0)
  • 2013 - BizTalk 2013 (First version to work with Visual Studio 2012 and Microsoft .NET 4.5)[8]
  • 2014 - BizTalk 2013 R2 (First version to work with Visual Studio 2013 and Microsoft .NET 4.5.1)[9]

Features

The following is an incomplete list of the technical features in the BizTalk Server:

Human-centric processes cannot be implemented directly with BizTalk Server and need additional applications like Microsoft SharePoint server.[citation needed]

Architecture

The BizTalk Server runtime is built on a publish/subscribe architecture, sometimes called "content-based publish/subscribe". Messages are published into BizTalk,transformed to the desired format, and then routed to one or more subscribers.[10]

BizTalk makes processing safe by serialization (called dehydration in Biztalk's terminology) - placing 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.

Adapters

BizTalk uses adapters for communications with different protocols, message formats, and specific software products. Some of the adapters are: EDI, File, HTTP, SFTP, FTP SMTP, POP3, SOAP, SQL, MSMQ, MLLP, Microsoft SharePoint Server, IBM mainframe zSeries (CICS and IMS) and midrange iSeries (AS/400) server, IBM DB2, IBM WebSphere MQ adapters.[11]

The WCF Adapter set[12] 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 LOB systems. Currently, this includes adapters for SAP and Oracle database, Oracle E-Business Suite, Microsoft SQL Server, MySQL, PeopleSoft Enterprise and Siebel Systems.

Additional adapters[13] (for Active Directory, for example) are available from third party Microsoft BizTalk core partners.

Alternatives

The main competitors are:

References

  1. ^ Jones, Allen (19 December 2000). "Microsoft Releases BizTalk Server 2000 to Manufacturing". Windows IT Pro. Penton Media. Retrieved 26 July 2013.
  2. ^ a b c d e "BizTalk Server 2013 Evaluation Edition". Download Center. Microsoft. 1 April 2013. Retrieved 26 July 2013.
  3. ^ "Inter-Organizational Information and Middleware System Projects: Success, Failure, Complexity, and Challenges" (PDF).
  4. ^ "Microsoft BizTalk's future is cloudy (no pun intended)".
  5. ^ Ganeline, Leonid (19 October 2010). "BizTalk: Timeline: Platform Support". Biztalkien. Self-published. Retrieved 27 July 2013.
  6. ^ "Microsoft BizTalk Server". MSDN. Microsoft. Retrieved 26 July 2013.
  7. ^ Foley, Mary Jo (23 March 2013). "BizTalk 2009 R2 gets a new name; still due in 2010". ZDNet. CBS Interactive. Retrieved 27 July 2013.
  8. ^ "Release Notes: BizTalk Server 2013 Beta". MSDN. Microsoft. Retrieved 27 July 2013.
  9. ^ "What's New in BizTalk Server 2013 and 2013 R2". MSDN. Microsoft. Retrieved 22 May 2014.
  10. ^ "Runtime architecture". MSDN. Microsoft. Retrieved 27 July 2013.
  11. ^ "BizTalk Adapters".
  12. ^ "WCF Adapters". MSDN. Microsoft. Retrieved 27 July 2013.
  13. ^ "BizTalk Server: List of Third-Party Adapters". MSDN. Microsoft. Retrieved 12 August 2015.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Microsoft_BizTalk_Server&oldid=741898984"