service oriented architecture an integration blueprint

www.it-ebooks.info Service-Oriented Architecture: An Integration Blueprint A real-world SOA strategy for the integration of heterogeneous Enterprise systems Successfully implement your own enterprise integration architecture using the Trivadis Integration Architecture Blueprint Guido Schmutz Daniel Liebhart Peter Welkenbach P U B L I S H I N G professional expertise distilled BIRMINGHAM - MUMBAI www.it-ebooks.info Service-Oriented Architecture: An Integration Blueprint A real-world SOA strategy for the integration of heterogeneous Enterprise systems Copyright © 2010 Packt Publishing All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews. Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the authors, nor Packt Publishing, and its dealers and distributors will be held liable for any damages caused or alleged to be caused directly or indirectly by this book. Packt Publishing has endeavored to provide trademark information about all of the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information. First published: June 2010 Production Reference: 1160610 Published by Packt Publishing Ltd. 32 Lincoln Road Olton Birmingham, B27 6PA, UK. ISBN 978-1-849681-04-9 www.packtpub.com Cover Image by Sandeep Babu (sandyjb@gmail.com) www.it-ebooks.info Credits Authors Guido Schmutz Daniel Liebhart Peter Welkenbach Reviewers Albert Blarer Tony Fräfel Christoph Pletz Patrick Blaser Karsten Krösch Acquisition Editor James Lumsden Development Editor Stephanie Moss Technical Editor Ishita Dhabalia Indexer Rekha Nair Editorial Team Leader Gagandeep Singh Project Team Leader Lata Basantani Project Coordinator Sneha Harkut Proofreader Sandra Hopper Graphics Nilesh Mohite Geetanjali Sawant Alwin Roy Production Coordinator Alwin Roy Cover Work Alwin Roy www.it-ebooks.info Foreword Developing integration solutions is not a simple task, despite the fact that the integration of individual databases, applications, and complete systems is increasingly becoming part of software engineers’ day-to-day work. In addition, developers of Enterprise Service Buses (ESBs); Enterprise Information Integration (EII) infrastructures; messaging systems; service-oriented architecture (SOA) frameworks; Extract, Transform, and Load (ETL) tools; and software for data integration, all take very different approaches, and many organizations already have one or more different integration solutions in place. The Trivadis Integration Architecture Blueprint is the result of work on a large number of projects (not all of them successful), of detailed discussions with customers and specialists, and of careful study of the technical literature. The development of the integration blueprint took several months, as the main objective was to structure the integration solution in such a way that standardized, tried-and-tested basic components could be combined to form a functioning whole, with the help of tools and other products. It was also important that the solution met customers’ requirements, and could be implemented without the excessive use of resources. We believe that by structuring the integration layer into different, clearly dened levels and layers, and by assigning best practice patterns to these layers, we can make the process of developing integration solutions signicantly simpler in practice. The concept behind the Trivadis Integration Architecture Blueprint was developed by the authors, together with Fernand Hänggi and Albert Blarer, and formulated by Daniel Liebhart, Guido Schmutz, and Peter Welkenbach. Large parts of the book have been revised several times by the authors, and have also been the subject of intense debates in workshops. We would like to thank the reviewers Albert Blarer, Patrick Blaser, Christoph Pletz, and Karsten Krösch and, in particular, Tony Fräfel for his detailed input. Further technical information is available on our website ( www.trivadis.com) in the download area and the blog (under Know-How Community). www.it-ebooks.info We would like to thank everyone who has contributed to this book in any way. This includes, in particular, the reviewers and our patient colleagues who were always prepared to discuss things in detail, and clarify any number of aspects of the book. We would also like to thank our customers and business partners, with whom we have worked on a variety of projects that have given us many interesting and enriching experiences. Finally, we would like to thank our colleagues, friends, families, the proofreaders, and the publishers for their patience. www.it-ebooks.info About the Authors Guido Schmutz has worked as a software developer, IT consultant, lead architect, trainer, and coach for more than 20 years. As head of the Application Development area of the Trivadis Technology Center, he has written numerous technical publications, developed IT strategies, courses, and technocircles and spoken at international conferences. Guido Schmutz is responsible for innovating, designing, and implementing many data warehouse, customer relationship management (CRM), customer satisfaction measurement (CSM), management information system (MIS), and Enterprise Application Architecture (EAI) solutions for international banks, pharmaceutical companies, public authorities, and logistics companies. He specializes in enterprise architecture, bi-temporal data management, Java Persistence, and the Spring framework. You can contact him at guido.schmutz@trivadis.com. Daniel Liebhart has more than 20 years experience of IT, and 10 years experience of managing IT services and product development. His industry and technical knowledge covers the design, architecture, implementation, and operation of complex, international systems in telecommunications, nancial services, logistics, and the manufacturing industry. Daniel Liebhart is passionate about IT. He has received a number of awards and he gives lectures on software architecture and business informatics at the Hochschule für Technik in Zurich. You can reach him at daniel.liebhart@trivadis.com. www.it-ebooks.info Peter Welkenbach works as a consultant, senior architect, and trainer in the elds of requirement engineering, object-oriented methodologies, software engineering, and quality management. He has more than 20 years experience of designing and implementing complex information systems for banks, automotive manufacturers, and pharmaceutical companies. For 10 years he has been a technology evangelist for Java technology and the use of the corresponding frameworks in customer projects. His current technical focus is model-driven software development, the Unied Modeling Language (UML), aspect-oriented programming, Java Server Faces (JSF), asynchronous Java Script, and XML (AJAX) and architecture design methodology. Peter Welkenbach is a course developer, author of numerous publications, and speaker at JAX and international Oracle conferences. He has been using Spring in numerous customer projects since it rst appeared in summer 2003. You can get in touch with Welkenbach at peter.welkenbach@trivadis.com. www.it-ebooks.info www.it-ebooks.info Table of Contents Preface 1 Chapter 1: Basic Principles 7 Integration 7 Concepts 9 A2A, B2B, and B2C 10 Integration types 11 Information portals 11 Shared data 11 Shared business functions 12 Differences between EAI and SOA 12 Semantic integration and the role of data 13 Enterprise Application Integration (EAI) 14 Levels of integration 16 Messaging 16 Publish/subscribe 17 Message brokers 18 Messaging infrastructure 20 Enterprise Service Bus 21 The core functions of an ESB 21 The structure of an ESB 22 Middleware 23 Middleware communication methods 23 Middleware base technologies 24 Routing schemes 25 Integration architecture variants 26 Point-to-point architecture 27 Hub-and-spoke architecture 28 Pipeline architecture 29 Service-oriented architecture 30 www.it-ebooks.info [...]... of integration, and is intended as an introduction to integration technology and terminology You will: • Learn the basic concepts, which are often used in the context of integration architecture • Grasp an overview of the different architecture variants, such as point-to-point, hub-and-spoke, pipeline, and service- oriented architecture (SOA) • Learn about service- oriented integration with an explanation... Execution Language (BPEL) The application of process modeling Summary Chapter 3: Integration Architecture Blueprint Dissecting the Trivadis Integration Architecture Blueprint Standards, components, and patterns used Structuring the integration blueprint The road to the integration blueprint Applications and integration Layers in the integration solution Information flow and roles Information flow and building... implementation variants The Trivadis Integration Architecture Blueprint indicates how integration architectures can be implemented in practice It achieves this by representing common integration approaches, such as Enterprise Application Integration (EAI); Extract, Transform, and Load (ETL); event-driven architecture (EDA); and others, in a clearly and simply structured blueprint It creates transparency in... an explanation of both the process and the workflow integration patterns • Understand the different types of data integration and the accompanying patterns • Gain an understanding of Enterprise Application Integration (EAI) and Enterprise Information Integration (EII), and an indication of how direct connection, broker, and router patterns should be used • Understand developments in SOA resulting from... events • Understand the integration technologies of the future: grid computing and extreme transaction processing (XTP) Integration The term integration has a number of different meanings A fundamental knowledge of the terms and concepts of integration is an essential part of an integration architect's toolkit There are many ways of classifying the different types of integration From an enterprise-wide... possible, for example transforming input and output data by using canonical models and standardized formats for business documents These models and formats can be predefined for different industries as reference models [EDI (FIPS 1993), RosettaNet (Damodaran 2004), and so on] Transformation rules can be generated and stored on the basis of reference models, in the form of data cards and transformation cards... developers and theoretical concepts The Trivadis Integration Architecture Blueprint shows how to structure, describe, and understand existing application landscapes from the perspective of integration The process of developing new systems is significantly simplified by dividing the integration architecture into process, mediation, collection and distribution, and communication layers The blueprint makes... whole by means of distributed and independent service calls that are orchestrated through an ESB and, if necessary, a process engine A fundamental technique for integration is the usage of design patterns These include process and workflow patterns in a service- oriented integration, federation, population, and synchronization of patterns in a data integration, and direct connection, broker, and router... broken down into integration portals, shared data integration, and shared function integration Portals integrate applications at a user interface level Shared data integration involves implementing integration architectures at a data level, and shared function integration at a function level • Semantic integration: One example of a semantic integration approach is the use of model-based semantic repositories... result, function -oriented organizations have difficulties in reacting in an appropriate, agile fashion to rapidly changing markets, customer requirements, and technologies Process -oriented organizations, on the other hand, are considerably more flexible and, from an IT perspective, have the support of corresponding process -oriented concepts, such as SOA and EDA Process -oriented organizations need to . systems; service- oriented architecture (SOA) frameworks; Extract, Transform, and Load (ETL) tools; and software for data integration, all take very different approaches, and many organizations. and patterns used 92 Structuring the integration blueprint 94 The road to the integration blueprint 97 Applications and integration 98 Layers in the integration solution 100 Information ow and. book. Chapter 3, Integration Architecture Blueprint, describes the Trivadis Integration Architecture Blueprint. The process of layering integration solutions is fully substantiated, and each step