Two keywords “Complexity” and “Sustainability” came out from two different 2010 CEO study one by UN Global Compact-Accenture and other one by IBM. CIO/CTO can address these two issues from multiple areas. I think Application Integration is one of the hottest areas which are very complex and most enterprises are spending lot of money and time in business applications support. Cloud computing model can encapsulate the operation complexity, but sustainability and cost containment can only be achieved by addressing the vexing issues. I am exploring EAI in this article.
In most organization applications are running in silos or partially integrated, they are yet to achieve fully integrated systems. Therefore, they are missing numerous opportunities to help their business growth. IT is trying to come out of silo scenario in their IT operation environment for some time through optimization, virtualization, systems integration, etc. programs. Unfortunately even today, most of the IT department facing the challenge of making their IT operating environment simple, and how to support their business to sustain rapid changes and dynamic business environment? This article will give an overview of EAI which is one of the topics of my white papers series that address the pain points of those areas relate to the keywords “Complexity” and “Sustainability”. .
Enterprise Application Integration is a subsystem. It is not a core business function but enable the interaction between multiple business applications that can be one or more integrated business systems, components, external business partners systems, and other business unit systems to provide one or more business systems. EAI architecture defines a framework to:
• Facilitate interaction between endpoints
• Enable distributed operation of business components
• Insulated end points
• Provide an infrastructure that is scalable and extensible
• Explore to use the existing infrastructure services
• Enable reuse of end points
• Enable phased approach to implementation
• Enable easy maintainability
In almost every case, an EAI subsystem will be implemented using packaged integration applications. As a result, product selection plays a central role in the specification of an EAI architecture. This paper focuses on the preparation of the conceptual EAI Component Model. Architecture design should be carried out within the scope of total system development, and with respect to the related EAI techniques.
Prior to initiating product selection the component model need to be elaborated to a specification level. Both product selection and component model specification need to be well documented. The only EAI unique aspect to specification of the component model is the use of the EAI Attributes Blueprint as the consolidated source of parameters for the model.
The EAI Conceptual Architecture should be expressed through a number of work products like Architecture Decision and Architecture Model in the context of enterprise’s EA blueprint, and its Component Model diagram. To develop the EAI architecture five basic steps need to be followed:
1. Make initial architecture decision
2. Identify EAI services
3. Create multiple nodes or partition the systems
4. Identify EAI categories
5. Apply the architecture pattern
In this white paper I have provided an approach to the creation of a conceptual level system component model specific to EAI and other sub products require to implement EAI in a complex IT Environment of an enterprise. Please contact me for the white paper.
