Talk:Microsoft BizTalk Server

message: See the  Microsoft Certified Professional talk page why this article is tagged.
--ddezeure 14:35, 18 July 2006 (UTC)
thread_title:  Neutrality / Commercialism in edits regarding MS & Cisco certification 

message: This page reads like a product brochure. It presents a mountain of unsubstantiated claims ("easy integration", "popular among small businesses"). It has no "criticisms" section and makes no mention of ANY drawbacks the product has. PR spam is a big problem on Wikipedia owing to our high Google pagerank - pages like this are frequently targetted by PR companies as a free billboard. I'm adding the advertisement and sources tags. Kwertii 20:24, 16 April 2007 (UTC)
thread_title:  Advertisement/Press release-like style 

message: Although bipin targeted to medium to large enterprises
What is bipin?  Is that supposed to be "being"?--WPaulB (talk) 17:00, 18 April 2008 (UTC)
replies: text: Thanks for the edit.  I had time to go through the history to day and foudn that it was nonsense inserted by a repeated-vandalism IP.--WPaulB (talk) 14:40, 23 April 2008 (UTC)
thread_title:  What? 

message: BizTalk 2009 aka 2006 R3 is available - download is here. Maybe add/change (TBD) in article?  —Preceding unsigned comment added by ABeLina (talk • contribs) 08:43, 20 April 2009 (UTC)
thread_title:  2009 available 

message: It does not belong into category Middleware. Middleware is the glue that makes programs such as BizTalk Server possible, in this case most probably .NET. .NET is a middleware. BizTalk instead seems to be an application set, maybe "an Office", that concentrates on cooperation, "processes" (method schemes), and business interfaces. ... said: Rursus (mbork³) 12:10, 21 November 2009 (UTC)
replies: text: Oh, fool me! Middleware is a Buzzword, of course Microsoft BizTalk Server is a "MiddleWare". I spoke with mom on the telephone 2 hours ago, via the telephone middleware. But still: the article Microsoft BizTalk Server needs some more precise categorisation. ... said: Rursus (mbork³) 12:26, 21 November 2009 (UTC)

text: Er, yes it is - your statement is completely and absolutely wrong.  .NET is a Framework (as per it's formal name) and comprises of a code library and virtual runtimes for the execution of software code.  Middleware is the name given to a system that enabled connectivity and communication between processes and systems.  Middleware is exactly what BizTalk is. 2010-10-14T11:14:00  —Preceding unsigned comment added by 194.73.178.250 (talk) 11:11, 14 October 2010 (UTC)
thread_title: Not middleware

message: This article's lead statement is that BizTalk Server is an Enterprise Service Bus (ESB).  In fact, BizTalk Server has always been positioned as an Enterprise Application Integration (EAI) server.  ESB is a layer on top of a Service-Oriented Architecture (SOA) and Microsoft provides these capabilities in BizTalk Server as a collection of components and documents in the "ESB Toolkit".  The ESB Toolkit is not part of the default installation of BizTalk Server and I therefore believe the opening statement of the article is misleading.--Sir Crispalot 14:22, 19 September 2011 (UTC)
replies: text: I totally agree with that statement. Have a look at Microsoft's website on BizTalk. They call it a "Integration and connectivity server solution" a.k.a. EAI (platform). --79.220.221.98 (talk) 07:31, 9 August 2012 (UTC)
thread_title: Not ESB

message: BizTalk Server is in the 2012 Gartner Magic Quadrant for Application Infrastructure for Systematic Application Integration Projects. --hulmem (talk) 22:05, 21 December 2014 (UTC)
thread_title:  Notability