In recent years, most enterprises and organizations have made extensive investments
in several EAI systems and solutions that promise to solve the major integration
problem among their existing systems and resources. The business driver behind all
these traditional EAI projects is to integrate processes across third-party applications
as well as legacy systems to decrease the number of adapters one has to develop if
connecting two systems (Laroia & Sayavedra, 2003). Therefore, the traditional EAI
focuses (Haller, Gomez, & Bussler, 2005) on the message-based communication of
software applications interfaces, by pipelining different middleware technologies
and developing various adapters, connectors, and plug-ins to provide efficient messaging
support among heterogeneous systems, allowing their effective interconnection.
As traditional EAI efforts lack of an upper abstraction layer and standardized
architectures and implementations, a new integration challenge is emerging: the
interoperability among various vendor-dependent EAI systems and solutions. The
growth of the EAI market and the involvement of new EAI vendors have intensified
the integration problems identified, considering the standardization of integration
frameworks and architectures a necessity.
Pages:
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129