| Use |
Application to Application integration to allow seamless communication.
|
| Where does it belong? |
Member of the .Net Enterprise Server family.
|
| What does it do? |
Helps to develop, deploy and configure integrating applications to establish communication using messaging model and follow certain standards such as SOAP, XML and HTTP.
|
| What does it provide? |
Enterprise features such as scalability, transaction management, security and application communication co-ordination to streamline business.
|
| BTS Architecture |
It consists of two types of services: Messaging Services and Orchestration Services.
|
| Messaging Srevices |
Responsible for Receiving, Transforming, Routing and Delivery.
|
| Orchestration Srevices |
Responsible for business processes.
|
| Receive |
Receive documents in Push / Pull model and convert it to a Message. Two components are integral to Receive: Adapter and Pipeline.
|
| Adapter |
Adapters are .Net components following specific protocols and based on the BAF 2.0 (BizTalk Adapter Framework).
Adapters are of the following types:
-
Based on source: Native (out of the box) and Custom.
-
Based on usage: Technology Wide (FTP, File etc) and Application Wide (SQL, MSMQT).
-
Based on communication: Asynchronous (File, FTP etc) and Synchronous (SQL, HTTP etc). Synchronous Adapters are also known as Generic / Solicit. When BTS acts as a service consumer then the Synchronous Adapter is called Solicit RaR (Request and Response). When it acts as a service provider then the Synchronous Adapter is called Generic RaR.
-
Based on transaction support: Transactional (SMTP, SQL etc) and Non Transactional (File, FTP etc). Transactional Adapters with DTC support are called Distributed Transactional Adapters.
-
Based on batch support: Batch (File, SQL, FTP etc) and Sequential (HTTP, EDI etc).
-
Based on behavior: Static and Dynamic.
|
| Pipeline |
Pipeline components are used for pre and post Message processing. An Adapter can have only one Pipeline component. BTS by default comes with two Pipelines: XML Receive Pipeline and Pass Through Pipeline.
|
| Transform |
Transform services are responsible for one to one (XML to XML) transformation of messages. It is used by Receive, Delivery and Orchestration.
|
| Routing |
Routing services define the next action to be taken after a message is received. There are three types of Routing:
- Declarative Routing: Demands explicit route configuration.
'
- Context Routing: Incoming message holds the route information.
- PAS model: Loosely coupled Publish and Subscribe model.
|
| Send |
Comprises of Delivery Adapters and Pipelines
|
| Host Instance |
Messaging services and Orchestration Services together form a BTS Host Instance. Host Instance can be In Process or Isolated.
|
| Port |
It is the logical gateway to Messaging Services.
|
| Port Type |
It is a reusable entity which encapsulates the following information:
Message Type (the Schema information).
Communication Type (One way or RaR).
Port Type provides encapsulation by means of three port qualifiers: Private, Public and Internal.
|
| X Lang Scheduler |
It is the business process execution engine to Create, Manage, Destroy and Persist X Lang /s instances.
|
| How to develop BTS Application? |
BTS provides a number of tools tightly integrated with Visual Studio to design, build and deploy BTS applications.
Some of them are:
- BTS Explorer.
- ODX. (Orchestration Designer).
- BTS Project Templates.
|
|
Author's Profile
|
| Experience: | 5 year(s) | | Home page: | | | Member since: | Saturday, August 18, 2007 | | Level: | Starter | | Status: | [Member] | | Biography: | --
Sandeep Chanda |
|