Export (0) Print
Expand All

Architecture: BizTalk Adapter Service

Updated: February 20, 2014

There are two terms that are very important to understand:


LOB Target

An LOB Target is your on-premise Line-of-Business (LOB) system and the operations (like SELECT or INSERT) exposed to your client applications. Specifically, the LOB Target controls the LOB system connection URI (for example, mssql://SQLServerName:1433//myDatabase), the schema operation (for example, SELECT) and connection credentials (for example, myUserName and myPassword).

An LOB Target can be used by multiple LOB systems and is hosted in a LOB Relay.

LOB Relay

An LOB Relay is a URL that provides a connection to the cloud using Service Bus Relays. A LOB Relay acts as a container for the LOB Targets and can be used with multiple LOB Targets.

A single LOB Relay can be used with multiple LOB Targets. This is cost-effective because you can connect to a LOB system and execute an operation using one endpoint. There are restrictions based on the security model. As a best practice, group the same security method in one LOB Relay. For example, use the same LOB Relay to host the LOB Targets that use message security.

BizTalk Adapter Service is separated into two distinct functions:

  • Development

  • Runtime


Developing applications is done on-premise. On the Development environment, the application developer uses Visual Studio to create an Microsoft Azure BizTalk Services application that includes a Line-of-Business (LOB) component, like SQL Server. Specifically, the Development environment utilizes the following components:

  • Visual Studio to create a Bridge Configuration

  • The LOB system client libraries (if applicable)

Using the BizTalk Services SDK provides information on creating a BizTalk Service project. Connect to LOB systems from a BizTalk Services Project provides information on adding a LOB component to a BizTalk Service project.


The Runtime computer hosts the BizTalk Adapter Service Runtime on-premise. The BizTalk Adapter Service runtime is responsible for the following:

  • Manages on-premise to cloud connectivity.

  • Supports multiple on-premise LOB systems using the adapters in the BizTalk Adapter Pack.

  • Routes to the different on-premise LOB systems using the adapters in the BizTalk Adapter Pack.

Runtime Components: BizTalk Adapter Service provides information on setting up the Runtime environment and the different components.

Process Flow

  1. On-premise, a Bridge Configuration application contains a LOB Target and is deployed to Microsoft Azure Service Bus. When deployed, the following occurs:

    • A Service Bus endpoint is created using your Service Namespace.

    • On the Runtime server on-premise, the Runtime monitors the LOB Relay in Service Bus.

    Deploying the BizTalk Service Project provides the details on deployment.

  2. When a message is received by the Bridge Configuration application, the Service Bus endpoint passes the message to the LOB Relay in Service Bus. On the on-premise Runtime server, the following occurs:

    • The runtime service confirms the LOB Target details in the configuration store database.

    • The runtime service executes the LOB operation (like INSERT or DELETE). A runtime WCF web service is created for every LOB Relay. So if there are 15 LOB Relays in the Bridge Configuration application, there will be at least 15 runtime WCF web services.

  3. When the LOB operation completes on the on-premise LOB system, the response is sent back to the Runtime service, goes to the Service Bus endpoint and is passed to the Bridge Configuration application in Service Bus.

See Also

Community Additions

© 2014 Microsoft