Biztalk Data Bases

Message Box.
BiztalkMgmtDB.
BiztalkRouleEngineDB
BiztalkDTADB
BAMPrimary Import
BAM Archive
BAM Start Schema
SSODB
BAMAlertsNSMain
BAMAlertsApplication

BiztalkMgmtDB:
We can say this is brain for Biztalk,   it stores the Artifacts and GAC ed information.

BiztalkRouleEngineDB
This is for BRE.

BiztalkDTADB
This is for tracking DB

BAMPrimary Import
This DB stores all initial BAM  data.

BAM Archive

BAM Start Schema

SSODB
This is the SSO service

BAMAlertsNSMain
BAMAlertsApplication

Biztalk Message BOX

The message box is the place where everything in Biztalk happens.

Messages are immutable in Biztalk Message Box.

No subscribers are found, the message is still inserted into the Message Box.

Biztalk Message Flow

The following is the list of actors involved in receiving a message listed in the order in which they process the message.

1. Adapter
2. Pipeline
3. Map
4. Message Box

Streaming architectural principle in Biztalk.

Every component in Biztalk is a stream based component. Pipelines and maps use streaming to handle message in Biztalk

Publish Subscriber Model

Sequence of events in the Publish Subscriber Model,

1. Subscribers enlist their subscriptions.
2. The Subscription Manager tracks these subscriptions.

Architecture of Biztalk Server.

Biztalk Server is a .Net application built upon a set of SQL server databases that enable it to be both reliable and salable.  It is a publish subscribe massaging system built to achieve the loosely coupled, flexible design criteria of modern enterprise systems.

WHY BIZTALK

Biztalk enables business processing to happen faster, more easily and more reliability.

WHY NOT BIZTALK WHY WORKFLOW ( WWF)

If you don't need adapters to connect to the existing line of business systems, business activity monitoring to provide analytic and visibility, message format mapping, business rules, or iron clad reliability  you man not need Biztalk. If your solution only does for Web Services (WCF) in a homogeneous Microsoft environment with limited nee for tracking and monitoring, you may be able to simply use  WORKFLOW SERVICES on APP FABRIC and build a good solution.

GOALS OF BIZTALK

BizTalk's purpose is to enable the following goals:

1. Increasing reliability
2. Decoupling Systems
3. Providing reuse
4. Decreasing development time
5. Providing rich information to technical as well as business consumers.
6. Improving administration.
7. Providing a rich set of security options that can be controlled separately from the functionality of solution.

Increasing reliability:

-------------------------

Message Box