A brief description of the Biz Talk essentials

1. Introduction to BizTalk A brief description of the BizTalk essentials

3. Web-based development and execution environment: Loosely-coupled, long running business processes Standard gateway to send/receive documents Services to ensure data integrity, delivery, security

4. BizTalk Server – High-Level Architecture

6. BizTalk Messaging Engine

8. Orchestrations hold the logic behind business processes (not written in code but graphically designed with organized shapes – conditions, loops, etc…) and can use the Business Rules Engine (a simpler way to express complex sets of rules used in a business process).

9. Orchestrations create subscriptions to indicate the type of messages they expect. Messages that arrive in the Message Box are dispatched to appropriate orchestrations. Orchestration usually sends a message back in Message Box upon completion.

10. The outbound message is processed by a Send Pipeline (converted from internal XML) and delivered through a Send Adapter to the target (e.g. saved file, Web Service call, …).More details on Sending / Receiving Messages, Adapters, Pipelines, Subscriptions: http://msdn.microsoft.com/en-us/library/aa560031(v=BTS.10).aspx More details on Schemas, Mappings, Orchestrations, Business Rules Engine: http://msdn.microsoft.com/en-us/library/aa561630(v=BTS.10).aspx

11. Quick Glossary Host: logical representation of a runtime process (adapters & orchestrations); can have multiple instances on different servers (and a server can have multiple hosts); can run in-process (win service) or isolated (non-BizTalk process – e.g. ASP.NET worker) Adapter: connectivity to the outside world (usually in charge of transport, data agnostic, on the receive end, in charge of listening / pooling endpoint). Pipeline: data processing & validations (normalize/denormalize data to/from XML – Note: BizTalk does not always require XML)

12. Quick Glossary Subscription: a set of conditions, representing the interest of an orchestration for a certain message (data from the message is written in the context and evaluated against subscriptions to determine routing) MessageBox: implemented as a SQL database; publish/subscribe design (in case of multiple subscribers each receives a copy of the message) MessageAgent: receives the message (once it has passed thru an Adapter & Pipeline), writes properties in the Message Box DB (e.g. MessageType), finds subscriptions (SP call), inserts message (SP call, subsequent calls in case of multiparts), adds reference to host instance queue.

13. Quick Glossary Orchestration: implementation of the business processes with a graphical shape-based designer (drag’n’drop); can be invoked by a new message or by another orchestration OrchestrationEngine: manages stateless execution of orchestrations; on wait/delay stages it can dehydrate orchestrations (serialize orchestration state to the MessageBox and remove from memory) and rehydrate them (reverse process) as needed BusinessActivityMonitoring: visibility into the processing within business solutions; uses terms that any data consumer can use; based on a wish list and a DB infrastructure for instrumentation data, a Tracking Profile can be generated (deployable at runtime); data is available within a BAM Portal (or accessible on SQL server via SQL Reports, queries, etc…). RulesEngine: abstract business logic from code, allow changes & control for business owners

14. Development Roles Business analyst: define rules & behavior for a business process, define process flow (what info is sent to each app, mapping between business documents) Developer: create BizTalk application that implements the above – define XML schemas, specify detailed mappings, create orchestrations Administrator: set up communication / endpoints, deploy BizTalk application

15. Thank you! Stay tuned for the next slideshow in the BizTalk Series!