1. TOPIC 7 Enterprise Application Architecture (EAI)

2. Content Architectures Middleware What is EAI A Typical EAI System EAI Benefits Conclusion

3. Enterprise Application Integration (EAI) Provides the means to share data between different applications without writing custom interfaces. Example: – Consider a company that wants to do build an eCommerce portal. – Has a number of legacy applications (or even an ERP solution in place) – Need build the web-based eCommerce infrastructure and link with systems that do functions like process orders, manage inventory, ship products – The company decides to use a major courier service for delivery of products ordered from the web site. – The company wants an ODS for analysis of transactions taking place on the site

4. Example One solution – custom Interfaces Issues? eCom Site Courier Shipping Inventory Order System ODS

5. Example eCom Site Courier Shipping Inventory Order System ODS EAI Alternative – employ EAI solution

6. Advantages of EAI Cost effectiveness Time to market Scalability Ability to deal with complex environments

7. EAI Components Business Rule Component: to allow the applications to understand your business processes. Business Logic Modules (i.e. supply planning, sales order processing. Methods for business process management.) Transformation tools (to define how to map data from one system to another)

8. EAI Components …. Cont… Data Acquisition Component: to allow access to the Data Source and Target Interfaces (i.e. Siebel, SAP, PeopleSoft, ODBC, Oracle, CICS, IMS) - note that the data acquisition component is crucial to EAI success. Most vendors refer to these interfaces as "adapters“ Adapters understand the data structures associated with applications and the means by which to access the data. (SAP/ABAP). map heterogenous data formats, interfaces and protocols into a common model and format. Hide heterogeneity and present uniform view of layers below.

9. EAI Components …… Cont…. System Development Component: to allow programmers to design and test custom requirements - Design tools (for business process design, debugging, and testing)

10. EAI - Components System Control Component: Should have the following features: – Management tools (for application-specific monitoring) – Directory tools (for locating other applications on different platforms), particularly support for the Lightweight Directory Access Protocol (LDAP) – Commitment control management mechanisms (for control of business-level logical units of work) – Strong support for metadata management

11. EAI - Components – Message Brokers (to control transactions, control security, and perform event notification. The product should also include the capability to "bridge" messages between different messaging systems (facilitates the interaction among adapters) – Scalability for high-volume transaction throughput. It is almost impossible to know at implementation time what the data volumes will be in the future – therefore, EAI must be scalable. – Support for varying levels of fault tolerance, load balancing, and failover for mission-critical systems. Workflow enablement is a key requirement to reduce latency between distributed processes.

12. Typical EAI system integrating application (contains the composition logic) message broker SmartQuotation DBMS applications SmartForecastingXYZ SmartQuotation adapter database adapter SmartForecasting adapter e-mail adapter XYZ adapter

13. Message Brokers Message oriented middleware Supporting integration of heterogenous systems Logic for routing messages Filtering and processing messages

14. Old message-based interoperability inventory management payment- system month-end closing shipping message-oriented middleware dispacher new PO

15. Message Brokers inventory management payment- system month-end closing shipping message broker dispacher new PO

16. Difference senderreceiver message broker core In basic MOM it is the sender who specifies the identity of the receivers. With message brokers, custom message routing logic can be defined at the messae broker level or at the queue level.

17. Routing logic sender‘s identity message type message content Definition – message broker level – queue level

18. What is EA? Its not technical! Aligning IT to business. Answering all of the enterprise needs Transverse view. knowing and managing the current situation, paving the road for the wanted one. Implementation of information management Enforce homogeneous solutions and enable “One system” to the users.

19. Architectures 1 layer architecture – monolithic Information Systems – presentation, application logic, and resource management were merged into a single tier 2 layer architecture – separation of presentation layer from other 2 layers (app + resource) – became popular as 'server/client' systems 3 layer architecture – can be achieved by separating RM (resource management) from application logic layer

20. Multi-tier Architectures Where to put the business-logic? – Client tier -> NO! Fat clients Reimplementing it for each different type of client Redistributing clients after each software update – Data tier -> NO! Vendor and technology dependence grows Different applications have different needs for the same data Performance issues in resource usage

21. Multi-tier Architectures Where to put the business-logic? – Middle tier -> YES! Business logic has its own tier Web browsers HTML, Java GUI clients C++, VB, Java Client tier user interfaces Web Server Middleware Server Middle tier business logic Data tier data sources Databases Legacy Systems

22. Middleware I Allows communication – through a standard language – across different platforms – between legacy and moderm applications Takes care of – transactions between servers – data conversion – authentication – communications between computers

23. Middleware II Provides runtime environment for components in the middle-tier – Component lifecyle and management – Transaction, event and security services – Provides connections to databases, mainframes and legacy systems Seperates client-tier from the data source – Clean seperation of user-interfaces and presentation logic from the data source

24. Middleware III Main use today: Legacy wrapping for thin client architectures User interfaces Business logic Data sources Client-tier (GUI applications, browsers) Middle-tier (CORBA/EJB/COM server) Data-tier (databases, mainframes)

25. Importance of EAI A step forward in the evolution of middleware Integrates applications and enterprise data sources so that they can easily share business processes and data. Integration is done without significant changes of applications and data sources.

26. Middleware EAI Middleware

27. ERP System Legacy System Databases CRM System Enterprise Portal Application Financial System SCM System Internal Applications (Java,C,C++) EAI

28. 28/31 Example: a simple supply chain purchase order deliver goods write invoice order atricle check availability document customer-contact not available Ordering System Warehouse Controlsystem CRM System ERP System Manufacturing System Financial System Business Process Management

29. EAI benefits: Lower development costs – Integration is simpler because systems are more loosely coupled than in object brokers Lower opportunity costs – Integration is done more quickly – corresponding cost savings reachieved sooner Lower maintenance effort – adapters extract the interaction with external systems – significant advantage from the software engineering point of view

30. Conclusion Enterprises integrate their applications – less expensive than replacement – more efficient than „information islands“ Enterprises must establish web-presence and make business services available to web- clients

31. Workflow Management Systems

32. Content Overview The parts of a WfMS WfMS requirements WfMS and other Middleware WfM and the Web

33. Why WfMS Originally for office automation Automate administrative processes among human participants and applications Facilitate definition and maintenance of integration logic Processes can be interpreted and modified by business people

34. What is a WfMS Software platform to – Design – Develope – Execute – Analyse workflow processes integrate different Services, Applications and human participants

35. The parts of a WfMS Workflow definition – Workflow definition Languages Workflow engine Design interface Monitoring tools and reporting capabilities User Interface Workflow Architecture

36. The parts of a WfMS Workflow definition Workflow engine Workflow Instance User Interface / Application Monitoring Resource repository

37. The Workflow definition Formal description of a business logic Specified by a directed graph Defines order of execution of process nodes – Work node – Routing node – Start and completion nodes Once designed, definitions can be “applied” to the process engine

38. 38/31 The Workflow engine Retrieve Wf definition Determine nodes to be executed – routing node – work node Place work into the work queue – resource accomplishes work OR invoke method of resource API monitor inbound queue for completion messages determine next node to be executed Wait until Work is completed Place work Into work queue Determine nodes out of WF definition

39. The Workflow engine (2) Resource Broker Workflow engine resource1 resource2 resource3 Inbound queue Outbound queues Workflow Definition 1 2 34 5

40. Monitoring Tools track and monitor individual work requests review resource productivity and work volume analysis quickly search for and identify a work request provide feedback on performance issues Get information about bottlenecks in the process Analysis to implement changes to the workflow process

41. User Interface Separate work list management from workflow management access and action work requests individuals have a single work list requests from different workflows

42. Workflow Architectures Highly centralized Architecture Tasmanager parts of Scheduler Async. centralized Architecture Tasmanager no longer part of Scheduler Calling Program not blocked No immediate action of called Program

43. WfMS Requirements Scale Dynamic resource selection and assignment Performance management Sophisticated Failure handling

44. WfMS and other Middleware Act in many ways as EAI tools emphasis on programming in the large Focus on workflow that manages integration Combine WfMS and EAI into a single system

45. WfMS and other Middleware (2) WfMS WfMS Adapter Message Broker Smart quotation adapter database adapter forecasting adapter E-mail adapter ….. Smart quotation DBMS Application Smart Forecasting

46. WfM and the Web Services have to be described Protocols to communicate with the Service – SOAP Formats and protocols for invoking the Service – WSDL Must be easy to find Search Services by creteria – UDDI

47. Web Service Integration Outsource Services Search for business partners Establish partnership Enable Service communication Exchange of messages Services may not be invoked in right order New requirements: Get list of Services that fullfill them Compose new Web Service - Publish Service Internal details hidden from User

48. 48/31 Advantages of WfMS Rapid process design and maintainance Failure and exception handling Catering for performance and high availability Workflow design with graphical interface

49. Disadvantages of WfMS Expensive software licenses Complex installation and operation Heavy-weight platforms