Applicable object: Microsoft BizTalk Server 2004
Introduction
This article describes the advantages of an enterprise application integration / business process management platform based on XML technology implementation, and specializes in the combination of InfoPathTM with BizTalk Server® 2004 to solve complex workflow issues, strict documentation requirements and application integration issues. Thereby creating flexible, agile companies.
Enterprise Application Integration Platform Based on XML and Web Services can greatly improve application efficiency. In the past two years, thousands of successful deployments have confirmed the efficiency improvement in this regard. In view of this attractive value, the technical supervisors began assessing and investigating large-scale strategic deployments of XML and Web service platforms.
XML-based enterprise application integration / business process management architecture provides a practical solution for any process-centric request. Controlled workflow, interaction between application integration interfaces or business partners can be processed by an organized XML structured document and information-documentation and information based on the context of information, form requirements, and business logic possibilities - - Workflow describes, edit, and execute. This development and process execution model is the basis for the Service Oriented Architecture, SOA example.
In the SOA example, XML metadata is precisely defined for the meaning and application of information in documents and information. No matter how this information is generated, any application that is able to resolve XML metadata can cognition, process, and transform. Conversely, regardless of how the original application is created, the web service can use XML to describe and reveal the application's method, so that it can be called by asynchronous XML information exchange. The Web service also provides a mechanism for transmitting all XML documents during the information exchange.
In order to make XML and Web services play a truly role in creating flexible processes, their features must be widely embedded in the host application, and can be used for end users and developers at any time; integrated platform must Use XML to connect a variety of different systems together; software development tools must be able to generate web services directly; the database must store XML metadata locally; personal productivity tools must be able to clearly parse, process and generate XML documents; and SOAP must As the underlying communication mechanism, all of these components communicate with each other.
If organizations give their knowledge workers accessible to the user-visible tools to create and deploy XML-based workflow applications, the achievement of agile companies is a big thing.
Microsoft is an advocate of SOA examples
Microsoft® has recognized the huge possibility of creating highly integrated organizations with efficient workflows. Unlike other information technology companies, Microsoft is not only based on XML-based new products, but also reconstructs its product lines around XML technology, which will be implemented to create agile enterprises.
BizTalk Server is a platform for Microsoft to integrate application integration, workflow automation, and business partners interaction. BizTalk Server is designed around the SOA paradigm. In the SOA paradigm, information and documentation and processing components with the interaction are based on XML and Web service technology.
In the upcoming Microsoft Office 2003, Microsoft uses the XML architecture as the underlying data structure of Word and Excel. Microsoft Office 2003 also introduces InfoPath - an XML-based application to create, provide and process various forms to resolve documentation requirements for complex workflows.
Through InfoPath, workflow participants can generate, analyze and collect structured information, and can exchange and interact with it. In the past, the above activities were typically limited to paper operations, or using digital expression. The form in the text processing or spreadsheet program can be easily accepted, but the information cannot be cognitive or processed if there is a lack of manual interference. Generation, transfer, extraction, manipulation, and adaptation of unsuccessful information is quite labor and cost, and the efficiency is extremely low. Workflow management challenge
Workflow management is a discipline that optimizes business tasks based on information flows between personnel and system. For any organization, human resources are the biggest expenses, thus improving the productivity of staff, can greatly enhance the economic and competitive status of the organization. Typically, we can attribute low efficiency of workflows:
· Build, Processing, and Processing Paper Documents
· Excessive information needed for completion tasks
· Time delay due to bottlenecks and priorities
· Delay caused by incompleteness or wrong information of a process
· Un guaranteed sequence dependencies in the process step
Different from other technologies, the Web greatly increases the efficiency of a large number of workflow tasks by allowing participants directly to their related functions and information. When the activity is composed of dispersed short-term transactions, processing services on the Web can do the best effect, and all steps can be completed at once next to the original participant's control (for example: performing a purchase task or check the order) .
However, Web-based interactions cannot fully solve the dynamic problem of documentation requirements and complex workflows. Documentation dynamics of complex workflows typically have the following features:
• Documentation Component part of a long-term multi-step process, where there are multiple participants create information, then perform delivery, swap repetitive operation, modification, or extension.
· In the process, participants may need to refer to the original information in any step.
· The information in the document determines its path selection and processing requirements.
· Documentation includes information derived or calculated by other information (ie "Automatic File Production").
· The identity of the document and participants can be verified at any time in the process.
Examples of such complex workflows include: spending report processing, insurance policy application form, financial statements, commercial bank letter, tax payment form, loan application form, and claim form processing. These workflows can include multiple documents and appendices that require throughout the flow lifecycle, where processes can be executed within an extended period and can involve multiple participants and applications.
Although the paper documentation is extremely efficient, the basic documentation requirements of the long-term workflow for multi-party workflows can be satisfied by the following ways:
· Reserved original format and context
· Combine the function of the document or the information it contains without affecting the integrity of the original document
· Features for authentication of participants in documents and creation or modify documents
· Since source data exists in the form of definition, guidance, and reference, it is easy to cognition, processing, and execute path selection.
· Application independence
Bring the workflow management into the digital era
To allow participants to accept digital solutions, the corresponding solution must support complex workflows and meet stringent documentation requirements. But after accepting a new solution, the true advantage is only displayed when the application is automatically and clearly switched and handled information. (In addition, the form in the text processing and the form in the spreadsheet program requires a large number of manual interventions when extracting and processing the information they collected.) For any digitization solution, let the information are functioning for many applications. They are all core problems. This problem adds a problem that simulates workflow and meets the requirements of document preparation, all of which can be properly resolved in XML solutions.
InfoPath provides such a solution. It is one of the first generation XML commercial productivity applications, where the information processed by the GUI expression layer and the application is based on XML technology. End users can design and work in visual height abstract functions without having to understand the underlying XML infrastructure.
The newly released BizTalk Server and Microsoft Office 2003 provide assistive XML and Web service features to display the corresponding concept of integration applications and automation processes along the function line, and communicate them to the corporate shareholders. We will review a large number of such functions and discuss how it supports and supplements in an enterprise workflow. Importance of XML technology in InfoPath
Adopt W3C XML architecture is one of the key strategic initiatives of Microsoft. This initiative uses BizTalk Server and Microsoft Office (alone or simultaneously combined with both) application integration and process automation.
The XML architecture is a standard definition of a wide range of basic data type units and structural components to create an XML document. It is a dictionary for abstract elements and attribute entities and organizational rules. When the XML document follows the Architecture "Dictionary", the application that can access the underlying architecture has an XML feature to clearly understand and process the meaning, functions, and usage of information in the document. As the web service agreement itself, each particular industry initiative for developing a set of exchange and processing information and the specific industry initiatives are based on the XML architecture. In Microsoft Office 2003, the local file format of Word, Excel, and InfoPath will be based on an XML architecture.
The underlying structure of the INFOPATH form consists of a template, XSLT style sheet, an embedder control, and a business logic instruction set that contains one or more XML architectures, where templates are controlled by the following route:
· Assign data type and constrain and confirm the value of the input form
· Control input information and the possibility and dependencies of each part of the form
· Generate automatic values, export values, and calculated values
· Call events, prompts, and instructions
· Provide access to remote information sources
· Enable digital signature merge
The end user creates a form template in the InfoPath Wysiwyg Design Tool. Form Templates do not require process program design, predefined XML templates or XSLT style sheets (although they will be the foundation of the template or therein). When the end user creates a table template by including the drag and drop control, the wizard, and dialog box, INFOPATE will define the XML architecture and processing instructions.
Conversely, when the InfoPath form is set according to the form template, INFOPATH generates an XML document containing input information and export information, while each message is marked with respective metadata. InfoPath handles instruction metadata as needed, and can also include digital signatures of the participants accessing the form. This document also contains references to template architecture and XSLT files, allowing any application with XML capabilities to use this document.
The XML document created by InfoPath is equivalent to the characteristics of paper from the paper in the traditional workflow through the following ways:
· Original digital signature document is always its original person.
• Document can be distributed in any number of objects anywhere, and protected to avoid unauthorized modifications.
· The document directory can be automatically written, and can perform processing and path selection according to the information in the document.
• The documentation can be combined with other XML documents while maintaining its original integrity.
How to use BizTalk Server and INFOPATH
Once INFOPATH creates form information and makes it can be used for XML according to the structured architecture, BizTalk Server becomes a highly practical enterprise-scale service entity for workflow automation. BizTalk Server combines the application integration and process automation of XML and Web service technology.
BizTalk Server has two core functions: First, as a process execution engine management step, application business logic, and call support applications for complex processes and / or transaction sets; Second, as a multi-transmission communication center, for applications and Process steps for information conversion and path selection. As a process execution engine, it can also record the status and variables of all active flows.
BizTalk Server provides a workflow process that can include thousands of Nodes with XML functions by providing a overlapping infrastructure. When BizTalk Server is used as a communication and process management center, the Microsoft Office 2003 application can be coordinated and monitored and monitored to workflow participation and make it compliant with reliability and performance specifications. This will make the overall dynamics and efficiency of the workflow processing and management of the enterprise. One of the examples of BizTalk Server collaborate with InfoPath to achieve a complete workflow function is: Publish and Subscribe MessageBox databases. BizTalk Server uses SQL Server to store every instance of incoming and outgoing information. When the flow wire is processed, the BizTalk Server saves it in the MessageBox database. BizTalk Server then sends information from the MessageBox database to a single process or multi-process application (ie BizTalk Server "Send Arrangement). It can also send information to the URL address, email address, and file location, etc. (ie "send port").
BizTalk Server uses publish / subscription logic when sending information. Depending on the type of document, specific values or variables in documents, and associated collections, send arrangements and send ports have specific bookings for specific information. The MessageBox database keeps these reservations, and send information (or "publish") to the application or participant according to it requests.
The importance of this workflow process / subscription communication is double:
• Allow multiple synchronization flows, applications, or participants to receive the same information in the design or runtime period, no need to create duplicate or excess information, or establish a path selection mechanism.
· Permanently record the information accepted and transmitted while logging the time and date of the information accepted and transmitted.
BizTalk Server workflow function
BizTalk Server 2004 also includes a complete development of features called: Human Workflow Services (HWS), which is designed to facilitate workflow management with InfoPath. The two main components of the BizTalk Server Workflow Services are: HWS project templates and HWS management control applications in the Business Process Designer.
The HWS project template in the business process designer is a general workflow process model that is designed and implemented for the BizTalk Server process development environment, including built-in architecture of activation, response, and synchronization information, and architecture templates for defining workflow tasks .
The HWS management control application combines the following workflow management resources:
· A built-in web service that provides interfaces for client applications (INFOPATH can be called directly)
• Constraint Manager, confirms and retrieves a group of activities performed at a specific time according to constraints associated with the fact that the same user, role, ownership, and the facts retrieved by the Knowledge Base Manager.
· A authentication tool that can intercept infoPath certificate credentials
· A relief tool for bringing scattered workflow tasks and activities into larger workflow activities
· Fact Retriever, to access and compile information and object properties from various resources, including InfoPath documentation
· A "process" for "processes" associated with workflow activities into a "process" associated with activities arrangements and information architecture
· Activity-type activity flow module for a cognitive workflow status information
With HWS, users can create, modify, and simulate workflows according to their respective needs, and then flexibly capture daily activities, and constantly incorporated it into the workflow is the core of the pregnancy 薷 薷WS is Activity Model, which can Track workflow activities and allow users to view workflow in real time. Activity Model is based on a predefined workflow (ie, a predefined model) or constraint, or simultaneously combines the activity into the workflow according to both. Constraint Manager stores information about personnel and organizations, and this information is evaluated by the rules that combine the process during operation. HWS makes information staff:
· Perform a workflow activity that is specific or a predefined model component
· Track the status of activities related to workflow
· Combine knowledge related to personnel and organization to promote workflow
· Combine knowledge related to business guidelines to guide workflow
BizTalk Server additional characteristics for workflow management
BizTalk Server also has the full functionality of monitoring and analyzing event handling and information properties. This monitoring and analysis activity is performed in a near real-time manner and can record constantly accumulated historical processes and communication information.
BizTalk Server Health and Active Trackler, Business Activity Monitor (BAM), and Tracking Profile Editor are three tools for setting, extracting, and displaying process information. These activities can indicate the operational status and performance specifications of the process and events, and can also provide an opportunity for building business intelligence based on the content and context of information.
InfoPath promotes the extensive deployment of automated workflow functions in the enterprise
Through InfoPath, knowledge workers who do not have programming skills can also create, distribute, and form a form that can generate XML structured information. For people who want to expand XML information and technology in the organization, it is of great significance in development, deployment and workflow.
From the development prospect, the InfoPath form provides the following high efficiency and advantages:
· Familiar and powerful creative environment, based on complete Microsoft Office writing and editing feature sets, such as: rich text format, hyperlinks, lists, tables, pictures, spell checks, find, automatic writing, and drag and drop editing.
· Built-in form control library, for example: Enter a large number of text entries, pull the list, scrollable list box, date collector (calendar control), check box, radio button, table duplicate, various buttons, A large number of other controls. All controls have configurable properties. In addition, InfoPath supports top-level design and functional flexible controls, including partial duplicate, partial selection, dynamic conditions formatting, and visualization, custom dialogs, and forms of more visual features.
• XML structured information is automatically generated by the GUI of the InfoPath form, which is an easy-to-understand and editable tree structure model. InfoPath can also import an existing document architecture and automatically generate a baseline form by the architecture. In addition, other applications can also edit the XSLT file (including the XML expression of the form GUI and controls). In InfoPath, the modified file will still have a complete function.
· The form accesses the database and web services through a simple dialog box. The InfoPath form is a web client, so the form designer can easily design a form that is connected to any database or published web service.
· Support to add digital signatures directly to the completed form. Digital signatures are always included in the format expression of the document and transmitted with the XML architecture expression of document information.
From the perspective of deployment and application, InfoPath also provides the following advantages:
· Simple form input and configurable controls promote the optimization reuse of the form template.
· Whether it is for web download sites or shared folders, or using email, infoPath's "release" tool can be easily and clearly distributed and all related resources (architecture, style sheets, template lists, etc.).
• Since the InfoPath form generates an XML document based on some architecture, the extraction and processing of information is extremely efficient. InfoPath interacts through simple dialog boxes, and these features, and other related features can be obtained from any application with XML features. · InfoPath's large functional controls and rich design functions achieve satisfactory and efficient end-user experience, can collect and create essential information efficiently, completely, accurately collected and created. The InfoPath form can provide a keen context prompt, real-time confirmation of the information has been entered, and real-time derivation and calculated information. Because the underlying architecture and style sheets are in the same location with the form on the end user computer, the user can fill in the form and all its features and local functions, without accessing the network. Once the access network, the database, and web services can be automatically applied to the form. At this time, the forms and all entered information can be submitted to the web service, database, or web site.
These features and advantages provide tempting reasons with XML-based personal productivity tools. Tools such as InfoPath promotes the creation and distribution of high quality information within the enterprise (that is, any extensive semantic structured information that has an extensive semantics) with an application that has an XML function. InfoPath not only has the characteristics of the requirements of the complex workflow, but also effectively replaces the web-based form function.
Conclusion: Taking higher productivity and more competitive functional development
The use of infoPath creates and distributes the rich semantic structure information to BizTalk Server to coordinate and manage workflows that meet any operation dependencies and performance requirements. Efficient workflows can be achieved in mutual utilization by interoperability XML architecture, Web services and XSLT, InfoPath and BizTalk Server.
We are entering the information technology era of the distributed process and the separation of the information as the application. The meaning, functionality and expression of information will be automatically described by using XML schema vocabulary and XML style table references, and embedded in the information itself. It can be created and released without having to process or apply information. Applications will be able to use information and use their own methods like other applications. Each process will be automated during operation based on the XML rule set, the interaction between the organized web service and information. The new application and business model will be developed by this example.
The first generation information technology infrastructure based on service-oriented architectural example is starting. Applications are widely used, such as: Microsoft Office Suite, can generate an XML document directly by architecture definition and processing instructions, and decoding open XML documents.
The next step is to let the applications with XML functions participate in the interaction of the event level based on their cognitive and processing capabilities that are discovered in the document. In essence, they will "actively respond content" and can perform automation flows between each other. This is also the basic premise of web services, and will redefine the functional concepts and actual functions of these applications. These applications will operate as a network client, operate in a web browser or email client, but at the same time, they can participate in the perfect automation interaction with any XML information source. Participants using these tools can also use their respective workflow functions, but efficiency is greatly improved because manual processing tasks that are independent of these functions are canceled.
Throughout the innovative features in BizTalk Server and Microsoft Office 2003, it is obvious that the XML function is increasing. The XML protocol (architecture, XSLT, and Web services) have achieved InfoPath and BizTalk Server. Conversely, BizTalk Server and InfoPath realize the application integration, automated workflow, and business partner applications for service-oriented architectural examples (a new development and process execution method).
All of the above discussion have significant significance, but all integrate all of them can promote efficiency and innovative solutions, thus responding to a large number of challenging problems. All in all, this is a global practice issue. More information:
http://www.microsoft.com/china/biztalk.
The information contained in this document represents the current view of the issued problem in the date of publication, Microsoft Corporation to the discussion. Because Microsoft must comply with changing market conditions, this document should not be understood as a Microsoft unilateral commitment, and Microsoft does not guarantee the accuracy after the information given in the date of publication.
This white paper is for reference only. For information in this document, Microsoft does not make any express, inspiring or statutory guarantees.
Compliance with all applicable copyright law is the user's responsibility. If the rights are not restricted by the rights set by the copyright law, if you do not have a clear written permission from Microsoft, it is not possible to copy, propagate in any form or means (electronic, mechanical, photocopying, recording, etc.) Any part of this article must not store or introduce it into the retrieval system.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights involved in this document. Unless explicitly expressed in any written license agreement in Microsoft, it does not mean that this document does not mean that you will also get these patents, trademarks, copyrights, or other intellectual property.
Unless otherwise specified, the company, organization, product, domain name, email address, logo, personnel, location, and events are purely fictional, which will not be referred to as an example, and should not mean any real company. , Organizational, product, domain name, email address, logo, personnel, location and event.