Skip to main content
main-content

Über dieses Buch

Gain an in depth view of optimizing the performance of BizTalk Server. This book provides best practices and techniques for improving development of high mission critical solutions. You'll see how the BizTalk Server engine works and how to proactively detect and remedy potential bottlenecks before they occur.

The book starts with an overview of the BizTalk Server internal mechanisms that will help you understand the optimizations detailed throughout the book. You'll then see how the mechanisms can be applied to a BizTalk Server environment to improve low and high latency throughput scenarios. A section on testing BizTalk server solutions will guide you through the most frequently adopted techniques used to develop solutions such as performance and unit testing as part of the development cycle.

With BizTalk Server 2016 you'll see how to apply side-by-side versioning to your solutions to reduce the chances of downtime, You'll also review instrumentation techniques using Event Traces for windows and business activity monitoring (BAM). While the book is focused on the latest version of BizTalk Server, most of the topics discussed will also work with BizTalk Server 2013R2.

What You'll Learn

Review BizTalk Server internals and how the message engine works

Understand BizTalk Server architecture

Gather and analyze BizTalk Server performance data Develop BizTalk Server performance solutions

Use advanced troubleshooting tools to help diagnose your platform

Who This Book Is For

Those who have strong BizTalk and .NET Framework knowledge and want to get their BizTalk Server knowledge to the next level

Inhaltsverzeichnis

Frontmatter

Chapter 1. Revealing the Black Box

Abstract
Most of the people who start their journey with BizTalk Server are usually not aware of how BizTalk Server receives, process, and sends messages. They instinctively believe that it is something that just happens, driven by a mysterious hidden force. While at the beginning this can be something even pleasant, when you deploy a solution to production and problems arise, troubleshooting BizTalk Server without knowing how the engine works can create confusion, delays, and in the worst of the scenarios, frustration. During my career as a premier field engineer, I have assisted customers with several critical situations, and you would be surprised how many times I heard the sentence:
Agustín Mántaras

Chapter 2. Performance Analysis

Abstract
Analyzing performance data is not an easy task. There are dozens of performance counters, and if you do not know how to analyze the information correctly, that can mislead you in so many ways and eventually it will cause you get the wrong conclusion. Additionally, hardware and features are rapidly evolving, and your performance testing and analysis methodologies may need to evolve as well. However, as performance counters are always based on samples over time, you can apply the concepts detailed in this chapter to make your life easier when trying to find an issue or a bottleneck. In this chapter, you will learn general analysis techniques that you can use to troubleshoot performance issues. Although the examples used focus on BizTalk Server, you could extrapolate them to any other software that exposes their performance counters.
Agustín Mántaras

Chapter 3. Performance Tools

Abstract
In this chapter, you learn how to use the most common performance tools that will help you find bottlenecks and resolve performance issues in your BizTalk Server environment.
Agustín Mántaras

Chapter 4. Optimizing the BizTalk Platform

Abstract
Probably one of the most missed tasks when designing BizTalk Server solutions is the specification phase. Most of the integration development focuses on providing the business functionality without taking into consideration the impact on performance once the application goes live.
Agustín Mántaras

Chapter 5. Instrumenting BizTalk Solutions

Abstract
In software development, instrumentation refers to the ability of an application to monitor business processes, diagnose issues by revealing debugging information, and expose performance indicators.
Agustín Mántaras

Chapter 6. Developing High-Performance Solutions

Abstract
In previous chapters, you learned how to optimize the BizTalk Server environment based on application priority levels and performance SLA definitions. Additionally, in Chapter 5, you learned how to instrument your BizTalk Server solutions using ETW, customer performance counters, and BAM to enhance system monitoring. Now it’s time to discuss the most common optimizations that you, as a developer, will need to know to develop robust BizTalk Server solutions.
Agustín Mántaras

Chapter 7. Decreasing Downtime

Abstract
In the previous chapter, you have learned how to develop solutions to improve schemas definitions, orchestrations, and pipelines.
Agustín Mántaras

Chapter 8. Monitoring Using BizTalk 360

Abstract
This chapter is focused on using the BizTalk 360 tool to monitor the BizTalk Server platform. Once your BizTalk solutions are deployed into the production environment, it is important that the BizTalk Server team be aware of the issues that are occurring on a daily basis to proactively increase the health of the platform. For instance, you need to be notified if a receive location or host is down.
Agustín Mántaras

Chapter 9. Testing BizTalk Server Solutions

Abstract
BizTalk Server solutions frequently integrate highly critical business processes where the integrated parties define very restricted service level agreements. Most of these applications rank high on the application priority level and must run 24x7 with downtime. In this situation, developing a successful testing architecture will make a huge difference in finding application bugs, performance bottlenecks, issues with new application versions, and in detecting problems when scaling the BizTalk Server platform.
Agustín Mántaras

Chapter 10. A BizTalk Server Tale

Abstract
In this chapter, I am going to tell you a story. This is the story about a fictitious customer (ACME corporation) that decides to start with BizTalk Server as its integration system. Because at the beginning they start only with one non-mission critical application, the sizing of the initial environment is small. Gradually, they add more and more applications, so they have to figure out a way to improve the platform. Even though this is an imaginary exercise, the situations described here are quite common with each evolving BizTalk server customer.
Agustín Mántaras

Backmatter

Weitere Informationen

Premium Partner

    Bildnachweise