International Journal of Information Technology and Computer Science (IJITCS)
IJITCS Vol. 5, No. 7, 8 Jun. 2013
Cover page and Table of Contents: PDF (size: 556KB)
Integration of Independent Applications and EAI Systems using Service Oriented Enterprise Bus and Open System Application Development Standards
Full Text (PDF, 556KB), PP.1-11
Views: 0 Downloads: 0
Author(s)
Quist-Aphetsi Kester
1,*
Koumadi Koudjo M
2
Nii.Narku Quaynor
3
Index Terms
Integration, Interoperability, Service Oriented Architecture, Open System Application, Enterprise Application Integration
Abstract
Businesses today are dependent on custom enterprise software and web applications from independent software developers and software companies. This creates a lot of problems such as integration, interoperability, security, and system maintenance. Enterprise Application Integration (EAI) and Business-to-Business integration control several key technologies and swift advancement in technology to meet the increasing needs for integration in the enterprise which often results in a lot of challenges due to differences between one proprietary approach and another. This paper seeks to provide an approach of integrating independent applications and EAI systems by using Web services standards and open application development standards in dealing with the challenges faced in integrating applications. This will make it possible for organizations to add a new layer of abstraction that is open, standards-based, and easy to integrate with any new or existing system and also make easy for data discovery as well as building of new concepts from existing data. The combination of Service Oriented Architecture and Web services will be used to provide a rapid integration solution and also publishing services in a manner that new concepts can easily be built from existing services.
Cite This Paper
Quist-Aphetsi Kester, Koumadi Koudjo M, Nii.Narku Quaynor, "Integration of Independent Applications and EAI Systems using Service Oriented Enterprise Bus and Open System Application Development Standards", International Journal of Information Technology and Computer Science(IJITCS), vol.5, no.7, pp.1-11, 2013. DOI:10.5815/ijitcs.2013.07.01
Reference
[1]Gable, and Julie, “Enterprise application integration”, Information Management Journal, March/April, 2002.
[2]David S. Linthicum (1999). Enterprise Application Integration p6.
[3]Understanding Enterprise Application Integration - The Benefits of ESB for EAI (2012). Available: http://www.mulesoft.com/enterprise-application-integration-eai-and-esb
[4]Enterprise Application Integration & Service Oriented Architecture (2012). Available: http://www.managementstudyguide.com/enterprise-application-integration-service-oriented-architecture.htm
[5]Prof. Paul A. Strassmann .What is a Service Oriented Architecture - George Mason University, November 19, 2007
[6]Qusay H. Mahmoud, (2005). Service-Oriented Architecture (SOA) and Web Services: The Road to Enterprise Application Integration (EAI) .Available: http://www.oracle.com/technetwork/articles/javase/soa-142870.html
[7]Web Services Architecture Usage Scenarios, W3C Working Group Note, H. He, H. Haas, D. Orchard, 11 February 2004 Available: http://www.w3.org/TR/2004/NOTE-ws-arch-scenarios-20040211/
[8]Rahul Sharma Beth Stearns Tony Ng (2001).J2EE Connector Architecture and Enterprise Application Integration.pp1-3.
[9]Dongjin Yu et al.(2009)” Service Oriented Enterprise Application Integration and its Implementation Based on Open Source Software” Proceedings of the Second Symposium International Computer Science and Computational Technology(ISCSCT ’09). p.229
[10]George Fernandez (2006), “A Federated Approach to Enterprise Integration”. Thesis pp.10-11.
[11]Web Services Glossary, W3C, 2004, [online]http://www.w3.org/TR/2004/NOTE-ws-gloss-20040211
[12]Builder, C., Bankes, S., and Nordin, R., Command Concepts: A Theory Derived from the Practice of Command and Control, RAND Corporation, 1999.
[13]Ren, M. and K. Lyytinen (2008) "Building Enterprise Architecture Agility and Sustenance with SOA," Communications of the Association for Information Systems 22(1), pp. 75-86.
[14]Papazoglou, M. P., and D. Georgakopoulos, D. (2003) “Service-Oriented Computing,” Communications of the ACM, 46(10), pp. 24-49.
[15]Schulte, S., Repp, N., Berbner, R., Steinmetz, and R. Schaarschmidt (2007) "Service-Oriented Architecture Paradigm: Major Trend or Hype for the German Banking Industry?" Proceedings of the 13th Americas Conference on Information Systems (AMCIS).
[16]Teti, F. (2006) “Develop a Service-Oriented Architecture Methodology,” Database Advisor Magazine, http://websphereadvisor.com/doc/17991 (current Oct. 15, 2007).
[17]Kwon, T. and R. Zmud (1987) “Unifying the Fragmented Models of Information Systems Implementation,” in R.J. Boland and R. Hirschheim (Eds.), Critical Issues in Information Systems Research, New York: Wiley.
[18]Haines, M. (2007) “The Impact of Service-Oriented Application Development of Software Development Methodology,” Proceedings of the 40th Annual Hawaii International Conference on System Sciences (HICSS).
[19]Kester, Q. A., Gyankumah, G. N., & Kayode, A. I. (2012). Using Web Services Standards for Dealing with Complexities of Multiple Incompatible Applications. International Journal of Information Technology, 4.
[20]Bell, M. (2008) Service-Oriented Modeling: Service Analysis, Design, and Architecture, New York: Wiley.
[21]XML Information Set, W3C Recommendation, J. Cowan, R. Tobin, 24 October 2001 Available: http://www.w3.org/TR/2001/REC-xml-infoset-20011024/
[22]Ervin Ramollari1 et al. A Survey of Service Oriented Development Methodologies. The 2nd European Young Researchers Workshop on Service Oriented Computing .2007.