Design of a Service-Enabled Dependable Integration Environment

The aim of information systems integration is to make all the data sources, applications and business flows integrated into the new environment so that unwanted redundancies are reduced and bottlenecks and mismatches are eliminated. Two issues have to be dealt with to meet such requirements: the software architecture that supports resource integration, and the adaptor development tool that help integration and migration of legacy applications. In this paper, a service-enabled dependable integration environment (SDIE), is presented, which has two key components, i.e., a dependable service integration platform and a legacy application integration tool. For the dependable platform for service integration, the service integration bus, the service management framework, the dependable engine for service composition, and the service registry and discovery components are described. For the legacy application integration tool, its basic organization, functionalities and dependable measures taken are presented. Due to its service-oriented integration model, the light-weight extensible container, the service component combination-oriented p-lattice structure, and other features, SDIE has advantages in openness, flexibility, performance-price ratio and feature support over commercial products, is better than most of the open source integration software in functionality, performance and dependability support.




References:
[1] Cape Clear Software, “Service-Centric vs. Message-Centric ESBs”, CPV-DOC- 3066, 2005.
[2] Steve Vinoski, Integration with Web Service, IEEE Internet Computing, November/ December 2003, pp 75-77.
[3] Dave Chappell, Enterprise Service Bus, O'Reilly, June 2004.
[4] Rahul Sharma, Beth Stearns and Tony Ng, J2EE Connector Architecture and Enterprise Application Integration, Addison Wesley, 2001.
[5] Parker Shi, Suketu Gandhi, “Enterprise Application Integration”, Centre for Technology Innovation, vol.2 No.3, 2001.
[6] Mark Endrei, et al., “Patterns: Service-Oriented Architecture and Web Services”, IBM, April 2004.
[7] S. D. Halloway, Component Development for the Java Platform, Addison-Wesley, 2002.
[8] Markus Völter, “PluggableComponent – A Pattern for Interactive System Configuration”, Proc. EuroPLoP '99, 1999.
[9] Erich Gamma, et al. Design Patterns: Elements of Reusable Object-oriented Software, Addison Wesley Longman, Inc, 1998.
[10] Fuyang Peng and Lele Tang, Architectural Design of a Component-Based Application Integration Framework,Proc. WSEAS 2007.
[11] Martin Fowler, “Inversion of Control Containers and the Dependency Injection pattern”, http://www.martinfowler.com, accessed on July 5,2015.
[12] Douglas Schmidt, et al., Pattern-Oriented Software Architecture—Patterns for Concurrent and Networked Objects, Volume 2, John Wiley & Sons, Ltd, 2000.
[13] “PicoContainer 1.2 documentation”, http://www.picocontainer.org. accessed on May 20,2014.