Eksportér (0) Udskriv
Udvid alt
EN
Dette indhold er ikke tilgængeligt på dit sprog, men her er den engelske version.

About Azure BizTalk Services

Updated: September 14, 2014

Using the different offerings from Microsoft Azure, users can create applications that run on the cloud. However, given the fact that these applications operate in their own ‘space’ on the cloud but at the same time need to interact with other on-premise or cloud applications, there is a need to bridge the message and transport protocol mismatch between these disparate applications. Bridging these mismatches is the realm of integration. There can be different forms of integration:

 

Type Purpose Azure BizTalk Services Offering

Enterprise Application Integration (EAI)

Enterprise Application Integration can be further divided into two broad components:

  • Bridging message-related mismatch in different sources and formats. This kind of integration bridges mismatches between message transport protocols, message structures, and message formats between two disparate systems. This may also include message validation, message transformation, and subsequent routing to other systems.

  • Integrating different Line-of-Business (LOB) applications. This integrates business processes and applications that span different LOB applications, such as SAP and SQL Server.

Electronic Data Interchange (EDI)

Integrating commerce transactions between businesses over industry or vertical-specific standards, such as X12, etc.

BizTalk Services provides a BizTalk Services Portal on the cloud that enables you to manage your EDI message transactions with trading partners.

For more information, see EDI, AS2, and EDIFACT Messaging in Azure BizTalk Services.

Microsoft provides these integration capabilities as part of through Microsoft Azure BizTalk Services. This section provides details on how each of these integration requirements is addressed by BizTalk Services.

See Also

Concepts

BizTalk Services

Vis:
© 2014 Microsoft