Introduction to BizTalk Server 2009

Editor's Notes

• #5: Today we will look at BizTalk and application integration Basic BizTalk Server functions BizTalk Server components Document transportation Document conversion Business process management How BizTalk Server processes messages Case study: an enterprise application integration scenario
• #6: So How do Enterprises Work Today? For example Company Contoso has multiple applications to serve their business needs. Hr System Erp System Ecommerse system An CRM application Each application requires data from every other application Each application has different data format The challenge is to integrate data in different format from Heterogeneous application. --------------- Further Contoso also deals with entities from external environment like Customers, Supplier , Banks, and Logistics. The data exchanged between the Customers can again be in different format like EDI, Xml SWIFT. ------------------- So this is the current scenario of How Enterprises Work Today.
• #7: To address the Integration of different applications. One option is to have Point – to – point Integration Architecture. The Advantages as u can see on the sides is Higher performance Tighter integration Easier to implement (but not always) The Disadvantages Increased complexity (With increase in the no of application the complexity further increased) Difficult to modify if we make a change at one point the other peers also required a change as such one change affected many systems. In a small Organization with five applications , the number of possible ways to directly connect these applications with all the permutation combination be 10. This leads to the so called “spaghetti” Problem.
• #8: To reduce the increasing complexity with increasing number of application an alternative was to use the Hub and spoke Integration Architecture. With a Hub at the center of the architecture this is a centralized processing machinery, the hub, accpept requests from multiple application, the spokes. Applications interact with the hub throuh adapters deployed on the hub, and as such, hub and spoke does not require any modification to the existing applications and supports a wide variety of transports. The major problem with this model was Central machine was a single point of failure. The scalability was limited to scalability of the central machine resource.
• #9: The New BizTalk Server 2006 topology goes beyond traditional integration paradigms of hub and spoke and point to point message bus described earlier. Biztalk server provides a hybrid architecture that takes advantage of key aspects of both models, namely scale-out for throughput and centralized management. The key is that although Biztalk server includes hublike properties such as centralized management, its internal architecture is bus like.
• #10: BizTalk Provides Integration development environment Integration runtime environment Integration framework
• #11: The basic functions of BizTalk server include: Document Transportation: Connecting applications within an organization or between organizations. Document Conversion: Converting documents from one format to another format. Manage business process through Orchestration: The automation, management, and monitoring of end-to-end processes.
• #12: These are the basic Biztalk server components that revolve around the Biztalk server 2006 engine. Information Worker services adds layers outside BizTalk server to provide extended functionalities. These services include Business Activity Services (BAS), Business Activity Monitoring (BAM) and Human Workflow Services (HWS). Enterprise single sign-on. Maintains user context and automatically sign on to receiving applications Business Rules Engine. Enabling developers to design BRE-enabled applications so that information workers can change policy without involving developers. Biztalk server Management and operation tools oversees business more effectively and forecasts improvements by continually analyzing process performance.
• #13: Adapters are software components that connect application resources with an integration system so that the application resources can interoperate with other connected applications. Adapters offer a no-coding approach to integration by providing simple, automated mapping of third-party technologies and data formats. BizTalk Server includes native adapters by default Web Services, File, FTP, HTTP, MSMQT, SMTP, SQL, EDI MSMQ, WebSphere MQ, POP3, WSS.
• #14: Document Conversion includes Message translation and Message transformation Message translation is the conversion between XML to and from native formats (non-XML) Message transformation is the conversion between 2 XML documents You can Performs computational and other data operations Automatically inserts the data from one message into another during runtime Some important Terminologies. Parsing: conversion from native to XML Serialization: conversion from XML to native Map: defines the correspondence between records and fields in two schemas
• #15: BizTalk Server lets you orchestrate your business processes by combining a runtime engine with a design-time tool called Orchestration Designer. Rather than expressing the steps in a programming language, this tool connects a series of shapes in a logical way.
• #16: A message is received through a receive adapter. The message is processed through a receive pipeline. This pipeline can contain components that perform tasks such as converting the message from its native format into an XML document. 3. The message is delivered to a database called Message Box database, which is implemented by using Microsoft SQL Server. 4.When a message arrives in the MessageBox database, that message is dispatched to its target orchestration, which takes whatever action the business process requires. 5. The result of this processing is typically another message, which is produced by the business process and saved in the MessageBox database. 6. The new message is processed by a send pipeline, which may convert it from the internal XML format used by BizTalk Server 2004 to the format required by its destination 7. The message is sent out through a send adapter, which uses an appropriate mechanism to communicate with the application for which this message is destined.
• #17: The warehouse inventory system is a stand-alone system that operates separately from the ERP System. The inventory system notices that the stock of an item is low and so issues a request to order more of that item. Any inventory request that comes from the warehouse should be declined if it exceeds 500 items. A request declined document is sent back to the inventory system if the order doesn’t meet the requirements. Otherwise, the order request is forwarded to the ERP system to prepare a purchase order.