Microsoft BizTalk Server 2000 Presented 21/01/2001 by Avner Zaitlin 21/01/2001 Internet DB Seminar 1 The Problem Building business-to-business (B2B) ecommerce systems presents many challenges to the system architect. Often, each company involved stores their data and documents in formats that are different from the formats used by the other participating companies. These companies need a way to integrate what tend to be vastly different systems. 21/01/2001 Internet DB Seminar 2 Product Overview BizTalk Server 2000 unites, in a single product: 21/01/2001 Enterprise application integration. Business-to-business integration Advanced BizTalk Orchestration technology. Allow developers, IT professionals, and business analysts to easily build dynamic business processes that span applications, platforms, and businesses over the Internet. Internet DB Seminar 3 Primary benefits Faster time to market Secure reliable B2B trading Quickly build, manage and track distributed business processes that integrate applications and business partners. Leverage and support XML & Windows 2000 security services to define and support trading partner relationship. Lower integration costs 21/01/2001 Leverage open standards and specifications in order to integrate disparate applications within and between organizations. Internet DB Seminar 4 Scenarios Trading partners Business process integration Enable businesses to link their multiple business processes. Automated procurement Enable information interchange among trading partners. Enable businesses to source goods and services with one-one or one-many vendors. Business to business portals 21/01/2001 Enable business to business intermediaries to automate content aggregation and management. Internet DB Seminar 5 BizTalk Server agreement An agreement defines the rules for exchanging data between two or more organizations: 21/01/2001 Source and destination organizations At least one document specification Document envelopes Security settings Transport settings Internet DB Seminar 6 Agreement types Outbound agreement Inbound agreement Defines the rules for sending documents. Defines the rules for accepting documents. An open agreement 21/01/2001 A special type that defines a single organization. The missing trading partner information is provided when the document is submitted to BizTalk. Internet DB Seminar 7 Document Specifications Document specifications define the structure of a business document in a way that is independent of the underlying data format. BizTalk represents document specifications internally with XDR (Will be replaced by XML Schema Definition Language - XSDL). A business document’s physical format may be XML, UN/EDIFACT EDI, X12 EDI, positionally delimited flat files , or commaseparated values. 21/01/2001 Internet DB Seminar 8 Document Specifications (Cont.) Document specifications are required to define the translation from the original document format to the BizTalk Server 2000 intermediate XML format. Business analysts must review schema initiatives in their industries, perform gap analysis between published specifications and internal business requirements, and negotiate details with trading partners. 21/01/2001 Internet DB Seminar 9 Document Specifications Editor 21/01/2001 Internet DB Seminar 10 Document Specifications Source XDR 21/01/2001 Internet DB Seminar 11 Document transformation The BizTalk Mapper transforms a document from the internal XML representation of an inbound document to the internal XML representation of an outbound document. This mapping allows BizTalk Server 2000 to alter the schema (transformation) and data format (translation) of business documents. The BizTalk Mapper uses standard XSLT technology to internally represent mapping rules. 21/01/2001 Internet DB Seminar 12 Document transformation (Cont.) Microsoft XSLT implementation provides COM and scripting language integration. BizTalk Mapper take advantage of this integration to provide built-in reusable components called functoids (String, Mathematical, Logical, Date, Conversion etc). Functoids allows the developer to define custom script logic that will be applied to source data values during the execution of a map. 21/01/2001 Internet DB Seminar 13 BizTalk Mapper 21/01/2001 Internet DB Seminar 14 BizTalk Mapper Compiled XSLT 21/01/2001 Internet DB Seminar 15 Pipelines Pipelines tie together the built-in or custom processing steps during a data interchange. Certificate identification and processing rules are defined within a pipeline. Custom components may be inserted into a pipeline. 21/01/2001 Internet DB Seminar 16 Transport Services BizTalk Server 2000 supports the following transport services: HTTP, HTTPS, SMTP, MSMQ, FTP, file, and fax. Documents may also be sent with a custom COM. 21/01/2001 Internet DB Seminar 17 Receive functions Receive Functions allow applications to submit business documents to BizTalk. FTP, file, and message queuing are supported receive functions. 21/01/2001 Internet DB Seminar 18 Receive functions (Cont.) The FTP receive function polls a given location and uses FTP to send files to BizTalk. The file receive function is invoked by a file system event when activity occurs in the defined directory. The source file is copied and submitted to BizTalk . The message queuing receive function provides event-based integration with MSMQ to read messages from a queue and submit the message body to BizTalk . 21/01/2001 Internet DB Seminar 19 Architecture and Tools The BizTalk Server uses Windows 2000 Server and Microsoft SQL Server to implement document interchange engine. A standard deployment may include one or more BizTalk servers configured as a group. Server groups share document specifications and maps through the Windows 2000 Web Distributed Authoring and Versioning (WebDAV) service. 21/01/2001 Internet DB Seminar 20 Architecture and Tools (Cont.) The servers share working interchange data by accessing a set of shared SQL Server queues. Four SQL Server queues are used during the processing of a document: scheduled queue, work queue, retry queue, and suspended queue. 21/01/2001 Internet DB Seminar 21 BizTalk Server 2000 Deployment 21/01/2001 Internet DB Seminar 22 Document Processing Business data is submitted to BizTalk as text. The server selects the appropriate parser based on the agreement. The parser looks up the document specification defined in the agreement, and uses it to create intermediate XML representations of the submitted business data. If the parsing step fails, the document will be placed in the suspended queue. 21/01/2001 Internet DB Seminar 23 Document Processing (Cont.) The server validate the structure and grammar of the document. The server loads the map defined in the agreement’s pipeline configuration and applies the transformation to the document. The document is serialized. The document is transported. 21/01/2001 Internet DB Seminar 24 Security SSL support is provided through the built-in HTTPS transport service. Documents may also be encoded using builtin S/MIME encoding components. The Public Key Cryptography System (PKCS) for encrypting and decrypting document is supported. Digital signatures may be applied to outbound messages and verified on inbound messages. 21/01/2001 Internet DB Seminar 25 Management and Analysis Tools BizTalk Management Desk allows the recreation and configuration of trading partner agreements and all associated properties (organizations, distribution lists, document specifications, envelopes, transport protocols, security settings, and pipelines). Microsoft Management Console (MMC) 21/01/2001 Using this console, groups, queue activity, receive functions and individual servers may be managed remotely or locally. Internet DB Seminar 26 BizTalk Management Desk 21/01/2001 Internet DB Seminar 27 Microsoft Management Console (MMC) 21/01/2001 Internet DB Seminar 28 BizTalk Orchestration (BTO) BizTalk Orchestration is a new technology for creating and orchestrating business processes that span time, organizations, applications and people. BTO is based on a new application of XML called XLANG, which is a language created to define the semantics of business processes and to bind process activities to software implementations. 21/01/2001 Internet DB Seminar 29 BizTalk Orchestration Goals Separation of Definition from Implementation. The process definition must not be tied to or driven by implementation details and vice versa. Dynamic Processes. “Any to Any” Integration. 21/01/2001 The process must be able to communicate and interact with any of the constituent parts of the implementation of the process. Internet DB Seminar 30 BTO Overview BizTalk Orchestration makes a distinct separation between the process definition and the underlying implementation. It allows the process to be modified and maintained without breaking the underlying software implementations, and vice versa. 21/01/2001 Internet DB Seminar 31 BTO Overview (Cont.) It allows flexibility of hardware and software choice. The underlying implementations can be upgraded or changed entirely without throwing away the work done to define the process. It makes it easy to add new elements and new participants to the process. 21/01/2001 Internet DB Seminar 32 BizTalk Orchestration form 21/01/2001 Internet DB Seminar 33 BizTalk Framework 2.0 BizTalk Framework provides detailed specifications for the construction of BizTalk Documents and Messages, and their secure transport over a number of Internet-standard transport and transfer protocols. 21/01/2001 Internet DB Seminar 34 Microsoft .NET Enterprise Servers Microsoft Application Center 2000 Microsoft BizTalk Server 2000 Microsoft Commerce Server 2000 Microsoft Exchange 2000 Microsoft Host Integration Server 2000 Microsoft Internet Security and Acceleration Server 2000 Microsoft Mobile Information 2001 Server Microsoft SQL Server 2000 21/01/2001 Internet DB Seminar 35 Case study - Marks & Spencer Business Challenge Marks & Spencer needed to ensure that point-of-sale (POS) data from its stores was transmitted to its data center as quickly as possible. Solution 21/01/2001 Microsoft Windows® 2000 Server in each store, connected through a LAN to POS terminals running a Windows client. Internet DB Seminar 36 Case study (Cont.) Solution (Cont.) 21/01/2001 Transactions flow from each POS terminal to the server, where every 60 seconds they are aggregated, converted to an XML message, and sent to the corporate data center using the Microsoft Message Queuing Services (MSMQ) BizTalk Server 2000 receives the XML messages, load balances them across all of the BizTalk processing servers, examines their contents, and intelligently routes the data to the appropriate application in the correct format. Internet DB Seminar 37 Case study (Cont. 2) 21/01/2001 Internet DB Seminar 38 References Product site: http://www.microsoft.com/biztalk Biztalk.org: http://www.biztalk.org/BizTalk/default.asp Case studies: http://www.microsoft.com/servers/net/casestudies.htm Microsoft Message Queue (MSMQ): http://www.microsoft.com/msmq XSL Transformation (XSLT): http://www.w3.org/TR/xslt S/MIME Specification: http://www.ietf.org/rfc/rfc2633.txt 21/01/2001 Internet DB Seminar 39