BizTalk 2013 Recipes | springerprofessional.de

Springer Professional

nach oben

2013 | Buch

Kapitel lesen Erstes Kapitel lesen

BizTalk 2013 Recipes

A Problem-Solution Approach

verfasst von: Mark Beckner, Kishore Dharanikota

Verlag: Apress

Enthalten in: Springer Professional "Wirtschaft+Technik" , Springer Professional "Technik" , Springer Professional "Wirtschaft"

Einloggen, um Zugang zu erhalten

Über dieses Buch

BizTalk 2013 Recipes provides ready-made solutions to BizTalk Server 2013 developers. The recipes in the book save you the effort of developing your own solutions to common problems that have been solved many times over. The solutions demonstrate sound practice, the result of hard-earned wisdom by those who have gone before.

Presented in a step-by-step format with clear code examples and explanations, the solutions in BizTalk 2013 Recipes help you take advantage of new features and deeper capabilities in BizTalk Server 2013. You’ll learn to integrate your solutions with the cloud, configure BizTalk on Azure, work with electronic data interchange (EDI), and deploy the growing range of adapters for integrating with the different systems and technologies that you will encounter.

You’ll find recipes covering all the core areas: schemas, maps, orchestrations, messaging and more. BizTalk Server 2013 is Microsoft’s market-leading platform for orchestrating process flow across disparate applications. BizTalk 2013 Recipes is your key to unlocking the full power of that platform.

Anzeige

Inhaltsverzeichnis

Frontmatter

Chapter 1. Recent Developments

Abstract

The two latest releases of BizTalk (2010 and 2013) provide a number of new features that will aid developers and increase the ability of the platform to support solutions built on it.

Mark Beckner, Kishore Dharanikota

Chapter 2. Document Schemas

Abstract

The BizTalk tool set enables exchanging information among computer systems. Each area of BizTalk’s rich set of capabilities addresses the common development tasks of building an integration solution. For example, BizTalk has tools for the common task of translating information from a structure understood by a source computer system into a structure understood by a destination computer system. Other BizTalk tools focus on defining integration processes or patterns of information flows.

Mark Beckner, Kishore Dharanikota

Chapter 3. Document Mapping

Abstract

At the core of integration projects is the need to exchange data. When systems are required to pass data, the data must either be in a common format or the systems must have a way in which to map the data from one system to another. Historically, mapping was spread across multiple components and entities, such as the database layer, the data access layer, and even the publishing and consuming systems themselves. When additional systems were added to the integration, or requirements around the mapping logic changed, many systems and components involved in the integration would need to be customized. Integration applications, such as BizTalk Server, offer a centralized and organized platform for handling mapping and provide tools to aid in the development of these mappings.

Mark Beckner, Kishore Dharanikota

Chapter 4. Messaging and Pipelines

Abstract

Messaging is the core functionality provided within BizTalk Server. On a very basic level, it is the plumbing that moves messages from one location to another. A number of different parts or objects make up this plumbing, taking actions at each step of a message’s path through BizTalk Server. Generally speaking, messaging objects can be split into two categories: receive and send. Figure 4-1 outlines the stages a message goes through as it is processed.

Mark Beckner, Kishore Dharanikota

Chapter 5. Orchestrations

Abstract

If publish/subscribe messaging capabilities are at the heart of BizTalk, then process orchestration capabilities are BizTalk’s brain. A BizTalk orchestration can define a complex integration process, coordinating the flow of information when simple data synchronization will not suffice. BizTalk provides a graphical design tool for defining these integration processes. These orchestration capabilities build upon the foundational publish/subscribe architecture of the BizTalk messaging runtime.

Mark Beckner, Kishore Dharanikota

Chapter 6. Adapters

Abstract

The BizTalk engine uses adapters to communicate with outside systems, and adapters start and end any process within BizTalk. Adapters come in three basic flavors: protocol adapters, database adapters, cloud adapters and ERP adapters. In addition to these, BizTalk 2013 comes with several more protocol adapters and a new tier of adapters used to facilitate communication with the Microsoft Azure Service Bus (cloud adapters).

Mark Beckner, Kishore Dharanikota

Chapter 7. Business Rules Framework

Abstract

Business processes are changing at an unprecedented speed, and the IT systems that power business processes are being asked to keep up. In today’s environment, to maintain a market advantage, organizations must react quickly to new markets, shifting consumer demand, shifting cost structures, and shifting business differentiators. The IT changes required to support dynamic business policies are taxing IT departments in terms of cycle time and hard costs.

Mark Beckner, Kishore Dharanikota

Chapter 8. EDI Solutions

Abstract

BizTalk has been moving into the EDI (Electronic Document Interchange) space for a number of years. In early versions of BizTalk, EDI was accomplished with third-party adapters and a lot of development and configuration performed outside of the platform. With the release of BizTalk Server 2006 R2, EDI became a prominent part of the platform. With the advent of BizTalk Server 2010, all aspects of the EDI life cycle, including schemas, mapping, workflow processing, and trading partner management are fully developed and available.

Mark Beckner, Kishore Dharanikota

Chapter 9. Deployment

Abstract

At the core of every BizTalk project is the necessity to deploy an integration project to the BizTalk execution environment. Given the complexity of the product, and the rich features it provides, this task has often been difficult and time-consuming. Every experienced BizTalk developer understands the time requirements to deploy, enlist, and start BizTalk artifacts, keeping in mind dependencies and ordering the steps accordingly. BizTalk has great functionality for this, so that a minimum of time is spent deploying solutions, and more time is available to develop new return-on-investment-producing solutions.

Mark Beckner, Kishore Dharanikota

Chapter 10. Administration and Operations

Abstract

Integration solutions play a key role in many organizations’ technology offerings. While much time and effort are typically spent on the actual implementation of these solutions, administration and maintenance tasks are often treated as second-class citizens. This reality can have costly consequences, as downtime of integration points can have large financial impacts on businesses.

Mark Beckner, Kishore Dharanikota

Chapter 11. Business Activity Monitoring

Abstract

BizTalk implementations can be generally defined as business processes, and business processes generally create metrics and data, which are needed for reporting purposes. The ability to rapidly generate and access such metrics and reports about business processes is essential to many parties, including managers, developers, and integration partners. One of the core components of BizTalk Server 2010 is the Business Activity Monitor (BAM) framework, which allows you to create, deploy, and view information about running or previously run processes. BAM implementations publish the metrics and reports and make them available to users through custom interfaces, which are updated in near real time as data progresses through the system. This chapter will introduce the steps necessary to build, deploy, and access BAM implementations.

Mark Beckner, Kishore Dharanikota

Chapter 12. Cloud Solutions

Abstract

In this new era of integration, enterprises must not only communicate with internal services effortlessly but also extend workflows beyond organizational boundaries. They are in need of cloud-enabled, managed services and an Internet service bus. Microsoft’s Windows Azure Service Bus caters to such needs. Also, BizTalk Server, being central to Microsoft’s hybrid integration strategy, is improved significantly on the cloud-readiness front.

Mark Beckner, Kishore Dharanikota

Backmatter

Titel: BizTalk 2013 Recipes
verfasst von: Mark Beckner
Kishore Dharanikota
Copyright-Jahr: 2013
Verlag: Apress
Electronic ISBN: 978-1-4302-6374-6
Print ISBN: 978-1-4302-6373-9
DOI: https://doi.org/10.1007/978-1-4302-6374-6

Premium Partner