Enterprise Application Integration. by David S. Linthicum. Publisher: Addison- Wesley Professional. Release Date: November ISBN: Enterprise Application Integration has 25 ratings and 1 review. Steve said: This is a popular introduction to EAI – short on detail, long on asinine (a. History of EAI. EAI addresses the issue of system and application integration. .. As stated also in David S. Linthicum’s book, “Enterprise Application. Integration”.

Author: Mugami Kajigul
Country: Spain
Language: English (Spanish)
Genre: Sex
Published (Last): 24 July 2010
Pages: 227
PDF File Size: 14.90 Mb
ePub File Size: 8.13 Mb
ISBN: 321-9-30093-660-8
Downloads: 46593
Price: Free* [*Free Regsitration Required]
Uploader: Dular

But IT managers attempting integration face daunting challenges–disparate legacy systems; a hodgepodge of hardware, operating systems, and networking technology; proprietary packaged applications; and more. For example, point-to-point middleware, while providing value within the enterprise, does not–and cannot–provide the ultimate solution.

Traditional Systems Traditional systems also known as “legacy systems” are stovepipe applications that may exist with many other stovepipe applications in a centralized environment. Inventory control applications that exist within the sales organization and the resume-tracking system in human resources are also examples of stovepipe applications. These include call center applications, sales automation applications, and inventory control applications.

These 5 locations in New South Wales: Fluppe 2root is currently reading it Mar 22, Most enterprises leverage many different technologies. Public Private login e. This person or office is responsible for overseeing a centralized architecture and making sure that technology and solutions selected for the enterprise are functionally able to interact well with one another.

While both “flavors” would benefit from EAI, it is a natural fit for business-to-business or supply chain integration in that one is able to serve the needs of the other.

Return davod Book Page. While this book includes chapters devoted to each type of EAI, a brief overview of the entetprise types is provided here see Figure 1. Middleware hides the complexities of the underlying operating system and network in order to facilitate the easy integration of various systems in the enterprise. Login to add to list. Second, new technology must be leveraged to solve the EAI problem. This type of EAI is most applicable to packaged applications such as SAP, PeopleSoft, and Baan, which all expose interfaces into their processes and data, but do so in very different ways.


Perhaps more importantly, the press trumpeted the claim that the cost of applying and maintaining the newer platforms was less than traditional systems.

Unfortunately, many of these business-critical systems are difficult to adapt to allow them to communicate and share information with other, more advanced systems. The only limitations that developers face are the specific features and functions of the application interfaces.

Packaged applications are natural stovepipes. Microcomputer Systems Microcomputer systems–personal computers–that exist within the enterprise today represent a significant challenge to those who seek to implement EAI within the corporation.

Enterprise Application Integration

Enterprise Application Integration David S. A number of factors contributed to this. Traditional microcomputer application development, such as those applications built during the rise of the PC, left far too many processes existing on the desktop and thus potentially impossible to access.

It is, at its foundation, a response to decades of creating distributed monolithic, single-purpose applications leveraging a hodgepodge of platforms and development approaches. Static and Dynamic Adapters. To see what your friends thought of this book, please sign up. Eric Zimmer rated it liked it Oct 01, Making Sense of the Processes. Many enterprises that needed to integrate applications have implemented such integration architectures within their enterprises and continue to maintain them today.


Accessing both the processes and the data that exists on microcomputers may require rehosting, or moving the processes and data to a centralized server. Perhaps with EAI, we may get it right. This allows any and all information required for all transactions to be immediately available no matter where the information is located in the enterprise. While there are methodologies and procedures that can be applied, most competent managers understand the degree of value when applying EAI without over-analyzing this information.

For example, the new SAP system implemented in accounting is a natural stovepipe application at the module level. While some organizations clearly demand an EAI initiative, others might find almost no value in implementing EAI within their enterprises. Importance of Application Design.

Enterprise Application Integration by David S. Linthicum

Clearly, the installation of these systems has been a textbook example of “management-by-magazine. Now that you know what it is, the value of EAI should be obvious. It will give an executive summary view of the state of the art of EAI, as it was in around – good enough to at least introduce the concepts and a lot of terminology, but horribly out of date now. John rated it intehration it Mar 07, Nguyen Van thuat marked it as to-read Jun 08, There are two basic approaches: Indeed, that “ancient” technology has probably remained critical to the workings of your enterprise.

This can be accomplished with any number of message-oriented middleware MOM products e.