Week # 05: Enterprise Integration Architecture & Technical Integration Architecture

1. Week # 05:Enterprise Integration Architecture & Technical Integration Architecture IS5314 – eBusiness Systems Integration Sem B, 2012-13 Dr. Daniel Tse Email: iswktse@cityu.edu.hk Office: P7812 Phone: 3442-8519 Office Hours: Tuesday 3:00pm to 6:00pm or by Appointment Dr. Narsi Bolloju (Course Examiner) Email: narsi.bolloju@cityu.edu.hk Office: P7809 Phone: 3442-7545 Office Hours: Wednesday 2:30pm to 5:20pm or by Appointment

2. Overview Moving from integration requirements to architectures Mapping integration requirements model to a suitable enterprise integration architecture Components of an enterprise integration architecture (TIA, DIA, SIA, PIA) Technical integration architecture Roadmap to integration technologies

3. Moving from Integration Requirements to Enterprise Integration Architecture Integrated infrastructure should address all or most of the current integration requirements, and flexible enough to support future integration requirements support different types of integration across business processes & rapid deployment of business solutions accommodate best suitable integration technologies from different vendors The entire process is complex, resource intensive, and challenging.

5. Service Integration Architecture Data/ Information Integration Architecture Business Process Integration Architecture Components of anEnterprise Integration Architecture Technical Integration Architecture

6. EIA Layer and its relationship to other layers http://www.aier.de/research/enterprisearchitecture.html

7. Mapping Integration Requirements Model to Enterprise Integration Architecture Identify a suitable TIA with a mix of bus-based, hub-and-spoke based and point-to-point connectivity solutions Study data/information integration requirements and identify suitable DIA components Decide whether service and event integration is required; if so, identify reusable services and required SOA/EDA components Decide whether process integration is required; if so, identify appropriate PIA components Review EIA comprising one or more of TIA, SOA/EDA, DIA and PIA, and verify that the overall objectives of enterprise integration can be met with the EIA

8. Technical Integration Architecture Defines underlying technologies for all integration solutions Includes components and/or tools for messaging, application interfaces, translation and transformation, routing, and transaction process monitoring & management

9. Alternative Topologies for Connectivity

10. Service Integration Architecture Defines loosely coupled, reusable business services Part of enterprise application architecture to provide language-, platform-, data source-, location-independent services Employs technologies such as CORBA, Java EE, .NET

11. http://www.esri.com/news/arcnews/summer06articles/spatially-enabling.htmlhttp://www.esri.com/news/arcnews/summer06articles/spatially-enabling.html

12. Data/Information Integration Architecture Provides enterprise-wide view of data contained in disparate systems including data warehouses/data marts Metadata repository required for maintaining the value, meaning and integrity of data across applications

13. Data/Information Integration Architecture http://www-128.ibm.com/developerworks/db2/library/techarticle/0206roth/0206roth.html

14. Process Integration Architecture Models business processes that possibly cut across organizational boundaries with the objective to improve the process and increase efficiency Maximizes business agility (business process changes and/or additions) Includes business process models, process managers and process monitors.

15. http://msdn.microsoft.com/en-us/library/bb264584.aspx

16. TIA defines … Overall integration topology (combination of hub-and-spoke, bus-based and point-to-point) Common, standardized technical services that support different styles of integration Service levels that must be supported A comprehensive security framework Focus on the ability to leverage existing (legacy) systems

17. TIA specification describes … HOW and WHEN each of different tools and interfaces is used (guidance for the development team) Specifications for the Languages supported Tools for integration Tools for configuration and administration Standard interfaces (available open interfaces)

18. Best Practices in TIA Maintain architecture specification periodically Typical effort for developing this specification about 2 to 3 months Obtain inputs from all stakeholders Plan globally and implement locally Implement quality metrics to justify infrastructure investments

19. Roadmap to Integration Technologies Source: http://www.ebizq.net/vendors?show=road_map

20. Summary • Requirements  Architectures  Technologies • Enterprise Integration Architecture • TIA – Combination of Point to Point, Hub and Spoke, Bus-based topologies • SOA/EDA – ESB, Service Repositories, Complex Event Processing • DIA – Data access from different sources, transformations and integration • PIA – Process modeling, simulation and integration • Integration technologies to support above architectures

21. References Enterprise Integration - Chapters 4 to 6 http://hubpages.com/hub/Systems-Integration-Explained http://hubpages.com/hub/Integration-Architecture-Explained