业务流程集成演变及发展(ppt20).pptVIP

* Generation 1 Traditional EAI was concerned mainly about 2 things: Connectivity -- Providing connectivity and translation of events or messages to and from many different systems including legacy systems, packaged and custom-built applications, and proprietary message formats like IBM MQ series Messaging Bus technology that was the backbone of EAI – transporting messages from one place to another Need to be very efficient and scalable – support billions of messages Transactional and reliable – Guaranteed once and only once delivery of messages This resulted in some key benefits: Removed point-to-point complexities Applications were now insulated and could be added, changed or upgraded without effect on rest of the integration This is particularly so if you use best practices called “Common Information Models (CIM)” to access application data. Traditional EAI was therefore very helpful in solving simple data synchronization problems, such as: Propagating a customer address change to many other systems that needed that information Product catalog or pricing changes Update of inventory availability status * Business Process Integration added the key capability of managing business processes to Traditional EAI … and we were one of the pioneers in this move to a new Generation of Integration technology Business Process Integration allows the business process itself to coordinate all of the information flows required for Integration. To do this it provides the following: Graphical models and design tools to describe a business process An execution engine that can interpret the process models and automate flow of data across systems, applications and partners Integrated workflow tools and user interface to handle exceptions to the process Real-time monitoring with the ability to drill down and identify any part of the business process All of this leverages traditional EAI -- in providing access to a wide variety of messaging platforms, systems and applications The