Welcome!

Microservices Expo Authors: Dalibor Siroky, Elizabeth White, Pat Romanski, John Katrick, Liz McMillan

Related Topics: Microservices Expo

Microservices Expo: Article

BizTalk Server 2004: Too Hot to Handle?

Where to successfully apply BizTalk Server technology

Recent trends in IT such as service-oriented architecture (SOA) and Web sevices, in conjunction with the still-increasing popularity of the .NET framework, put Microsoft's BizTalk Server in the center of attention for CIOs, CTOs, architects, and enterprise developers. Apparently everyone who is involved with the Microsoft platform now wants to implement BizTalk. Frequently we see that BizTalk is not implemented in areas where the benefits of the technology can be maximized. This leads to disappointment about the value of BizTalk, even though the problem is in the application of the technology instead of in the technology itself. In this article I will point out where, how, and when the third generation of BizTalk Server can provide real business value.

BizTalk Server Is Hot
In March 2005 BizTalk Server (BTS) reached an implementation base of 4,000 organizations. Microsoft states that these 4,000 implementations in four years make BTS the fastest-growing integration server on the market. Ever since it was first released, BTS has held a firm spot in the upper right quadrant of Gartner's magic quadrants for application integration and orchestration tools.

It's no wonder BizTalk is the center of attention for anyone who has a Microsoft infrastructure or who develops, designs, or architects Microsoft-based solutions. However to fully grasp the benefits of BizTalk Server, we should know where to successfully apply BizTalk Server technology.

A Brief History of BizTalk Server
To fully understand what BizTalk is and what it can do for you and your company, we should delve into the history of the product.

The first version of BizTalk, BTS 2000, was the result of two separate server products on which Microsoft development teams were working. On one side was the development of the messaging infrastructure and the BizTalk Framework (a.k.a. BTF, a SOAP 1.1 extension and XML framework aimed at integrating e-commerce applications), and on the other side there was the development of an extension to COM+ called COM+ Scheduler, which we now know as the Orchestration Engine. Nine months before BTS 2000's shipment in December 2000, Microsoft decided to merge both development teams in order to create one single solution for application integration and XML messaging.

Fewer than two years later Microsoft released the next version of BTS, named BTS 2002. This version contained a few improvements over the BTS 2000 version, and was generally more for administrators than for developers and end users. Additionally BTS 2002 offered some new functionality such as an HTTP receive function and increased Web service support.

Then, in 2004 (as the name suggests), BizTalk Server 2004 (formerly code-named Jupiter, which Steve Ballmer affectionately termed "BizTalk on steroids") was released. BTS 2004 is the first version that is fully based on the .NET framework, and which is written in fully managed code. The differences between it and the 2002 version are tremendous. Any BTS 2000 developer could learn to operate the BTS 2002 version within a day, but the BTS 2004 version is a different story. Development tools are now integrated in Visual Studio.NET, thereby perhaps adhering less strongly to the principle "code less, configure more" that was used throughout the BTS 2000 and BTS 2002 products.

In today's version, we can still see the two pillars of the product: messaging and orchestration. However a big difference with the BTS 2000 and 2002 versions is that by default, orchestration is used within the messaging tasks, even if the messaging task is straightforward and does not need the advanced options of orchestration. There is a way to work around this, but it is not as straightforward as using an orchestration for this task.

The Road to Choosing BizTalk Server
The key to assessing whether implementing a BizTalk-based solution will help your company is to look at it from an architectural perspective. At Capgemini we have developed the Integrated Architecture Framework (IAF) that defines architecture by means of contextual, conceptual, logical, and physical models, which progressively analyze an architectural need and refine a solution.

The architectural levels of the IAF are:

  • Contextual: answers the "where" question. Delivers contextual information and key principles that define the architecture. Focuses on the company and its environment.
  • Conceptual: answers the "what" question. Defines the architecture on a high abstraction level. Focuses on which business problem the solution/architecture should solve.
  • Logical: answers the "how" question. Defines what services are needed to implement the desired architecture. Focuses on the solution for the problem stated at the conceptual level.
  • Physical: answers the "with what" question. Defines the products and technologies with which the solution can be realized.
Starting from the contextual level, we should analyze all levels of the architecture, and see where and how BizTalk fits into the picture. This should eventually lead to a well-founded choice for the BizTalk platform, or for an alternative.

What we often see is companies deciding to implement BizTalk regardless of whether analysis on the upper levels justifies this implementation. The right order to choose any technology at the physical level is to progressively analyze all levels, beginning with the contextual level. We must first understand the problem before we supply a solution. Now that we have our analytical framework, let's see how we can apply it to BizTalk.

Where
The .NET framework has come a long way since it was first introduced about five years ago. On the eve of the launch of the .NET framework version 2.0, even the open source community has embraced the (unofficial) .NET framework, called Mono. Even though .NET is now available for Linux and Unix, BizTalk is still seen as a product exclusively for the Microsoft/Intel platform. To a certain extent this makes sense, as BizTalk Server 2004 runs only on Windows Server, and relies heavily on Microsoft SQL Server for its internal databases. BizTalk offers great opportunities to connect to other platforms, particularly through the broad application of open standards such as BPEL, SOAP, WSDL, XSD, and HTTP to name a few. Also, there are many adapters available to connect to other platforms. The use of open standards and the broad availability of adapters make BizTalk a great player in heterogeneous, mixed Windows-Unix-Linux environments. However the question remains as to whether it is wise to implement BizTalk as the only Intel-based system in a Unix or Linux environment.

If the where question tends to exclude BizTalk as a serious option, then you must have very strong arguments on the what and how sections to ultimately justify the choice for BizTalk.

What
The what question focuses on the business problem that needs to be solved. It states the requirements for the solution. Typical business problems in these areas may be:

  • "We need to shorten the time to market for new applications or automated support for business processes"
  • "We want to automate the processing of claims"
  • "We need to be able to exchange data with our trading partner"
  • "We want to reduce operational costs"
  • "We want to offer a new service to our customers"
    Also, business problems may already be stated in the form of an envisioned solution:
  • "We need to implement an SOA to provide business agility"
  • "We must use EAI tools to connect our Billing application to our Order application to streamline our procurement process"

More Stories By Loek Bakker

Loek Bakker is a senior consultant at Capgemini, the Netherlands. He specializes in architecture, SOA, and Microsoft.NET. Within Capgemini he is a lead architect for BizTalk-based integration solutions.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


@MicroservicesExpo Stories
How is DevOps going within your organization? If you need some help measuring just how well it is going, we have prepared a list of some key DevOps metrics to track. These metrics can help you understand how your team is doing over time. The word DevOps means different things to different people. Some say it a culture and every vendor in the industry claims that their tools help with DevOps. Depending on how you define DevOps, some of these metrics may matter more or less to you and your team.
For many of us laboring in the fields of digital transformation, 2017 was a year of high-intensity work and high-reward achievement. So we’re looking forward to a little breather over the end-of-year holiday season. But we’re going to have to get right back on the Continuous Delivery bullet train in 2018. Markets move too fast and customer expectations elevate too precipitously for businesses to rest on their laurels. Here’s a DevOps “to-do list” for 2018 that should be priorities for anyone w...
If testing environments are constantly unavailable and affected by outages, release timelines will be affected. You can use three metrics to measure stability events for specific environments and plan around events that will affect your critical path to release.
In a recent post, titled “10 Surprising Facts About Cloud Computing and What It Really Is”, Zac Johnson highlighted some interesting facts about cloud computing in the SMB marketplace: Cloud Computing is up to 40 times more cost-effective for an SMB, compared to running its own IT system. 94% of SMBs have experienced security benefits in the cloud that they didn’t have with their on-premises service
DevOps failure is a touchy subject with some, because DevOps is typically perceived as a way to avoid failure. As a result, when you fail in a DevOps practice, the situation can seem almost hopeless. However, just as a fail-fast business approach, or the “fail and adjust sooner” methodology of Agile often proves, DevOps failures are actually a step in the right direction. They’re the first step toward learning from failures and turning your DevOps practice into one that will lead you toward even...
DevOps is under attack because developers don’t want to mess with infrastructure. They will happily own their code into production, but want to use platforms instead of raw automation. That’s changing the landscape that we understand as DevOps with both architecture concepts (CloudNative) and process redefinition (SRE). Rob Hirschfeld’s recent work in Kubernetes operations has led to the conclusion that containers and related platforms have changed the way we should be thinking about DevOps and...
While walking around the office I happened upon a relatively new employee dragging emails from his inbox into folders. I asked why and was told, “I’m just answering emails and getting stuff off my desk.” An empty inbox may be emotionally satisfying to look at, but in practice, you should never do it. Here’s why. I recently wrote a piece arguing that from a mathematical perspective, Messy Desks Are Perfectly Optimized. While it validated the genius of my friends with messy desks, it also gener...
The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Microservices being modular these are faster to change and enables an evolutionary architecture where systems can change, as the business needs change. Microservices can scale elastically and by being service oriented can enable APIs natively. Microservices also reduce implementation and release cycle time and enables continuous delivery. This paper provides a logical overview of the Mi...
The next XaaS is CICDaaS. Why? Because CICD saves developers a huge amount of time. CD is an especially great option for projects that require multiple and frequent contributions to be integrated. But… securing CICD best practices is an emerging, essential, yet little understood practice for DevOps teams and their Cloud Service Providers. The only way to get CICD to work in a highly secure environment takes collaboration, patience and persistence. Building CICD in the cloud requires rigorous ar...
The enterprise data storage marketplace is poised to become a battlefield. No longer the quiet backwater of cloud computing services, the focus of this global transition is now going from compute to storage. An overview of recent storage market history is needed to understand why this transition is important. Before 2007 and the birth of the cloud computing market we are witnessing today, the on-premise model hosted in large local data centers dominated enterprise storage. Key marketplace play...
The cloud revolution in enterprises has very clearly crossed the phase of proof-of-concepts into a truly mainstream adoption. One of most popular enterprise-wide initiatives currently going on are “cloud migration” programs of some kind or another. Finding business value for these programs is not hard to fathom – they include hyperelasticity in infrastructure consumption, subscription based models, and agility derived from rapid speed of deployment of applications. These factors will continue to...
Some people are directors, managers, and administrators. Others are disrupters. Eddie Webb (@edwardawebb) is an IT Disrupter for Software Development Platforms at Liberty Mutual and was a presenter at the 2016 All Day DevOps conference. His talk, Organically DevOps: Building Quality and Security into the Software Supply Chain at Liberty Mutual, looked at Liberty Mutual's transformation to Continuous Integration, Continuous Delivery, and DevOps. For a large, heavily regulated industry, this task ...
Following a tradition dating back to 2002 at ZapThink and continuing at Intellyx since 2014, it’s time for Intellyx’s annual predictions for the coming year. If you’re a long-time fan, you know we have a twist to the typical annual prediction post: we actually critique our predictions from the previous year. To make things even more interesting, Charlie and I switch off, judging the other’s predictions. And now that he’s been with Intellyx for more than a year, this Cortex represents my first ...
"Grape Up leverages Cloud Native technologies and helps companies build software using microservices, and work the DevOps agile way. We've been doing digital innovation for the last 12 years," explained Daniel Heckman, of Grape Up in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
The Toyota Production System, a world-renowned production system is based on the "complete elimination of all waste". The "Toyota Way", grounded on continuous improvement dates to the 1860s. The methodology is widely proven to be successful yet there are still industries within and tangential to manufacturing struggling to adopt its core principles: Jidoka: a process should stop when an issue is identified prevents releasing defective products
We seem to run this cycle with every new technology that comes along. A good idea with practical applications is born, then both marketers and over-excited users start to declare it is the solution for all or our problems. Compliments of Gartner, we know it generally as “The Hype Cycle”, but each iteration is a little different. 2018’s flavor will be serverless computing, and by 2018, I mean starting now, but going most of next year, you’ll be sick of it. We are already seeing people write such...
Defining the term ‘monitoring’ is a difficult task considering the performance space has evolved significantly over the years. Lately, there has been a shift in the monitoring world, sparking a healthy debate regarding the definition and purpose of monitoring, through which a new term has emerged: observability. Some of that debate can be found in blogs by Charity Majors and Cindy Sridharan.
It’s “time to move on from DevOps and continuous delivery.” This was the provocative title of a recent article in ZDNet, in which Kelsey Hightower, staff developer advocate at Google Cloud Platform, suggested that “software shops should have put these concepts into action years ago.” Reading articles like this or listening to talks at most DevOps conferences might make you think that we’re entering a post-DevOps world. But vast numbers of organizations still struggle to start and drive transfo...
Let's do a visualization exercise. Imagine it's December 31, 2018, and you're ringing in the New Year with your friends and family. You think back on everything that you accomplished in the last year: your company's revenue is through the roof thanks to the success of your product, and you were promoted to Lead Developer. 2019 is poised to be an even bigger year for your company because you have the tools and insight to scale as quickly as demand requires. You're a happy human, and it's not just...
"Opsani helps the enterprise adopt containers, help them move their infrastructure into this modern world of DevOps, accelerate the delivery of new features into production, and really get them going on the container path," explained Ross Schibler, CEO of Opsani, and Peter Nickolov, CTO of Opsani, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.