it in a standardized way. Although other approaches like connecting at the database or user-interface level have been explored, they have not been found to scale or be able to adjust. Individual applications can publish messages to the centralized broker and subscribe to receive certain messages from that broker. Each application only requires one connection to the broker. This central control approach can be extremely scalable and highly evolvable. Enterprise Application Integration is related to middleware technologies such as message-oriented middleware (MOM), and data representation technologies such as XML or JSON. Other EAI technologies involve using web services as part of service-oriented architecture as a means of integration. Enterprise Application Integration tends to be data centric. In the near future, it will come to include content integration and business processes. Implementation pitfalls In 2003 it was reported that 70% of all EAI projects fail. Most of these failures are not due to the software itself or technical difficulties, but due to management issues. Integration Consortium European Chairman Steve Craggs has outlined the seven main pitfalls undertaken by companies using EAI systems and explains solutions to these problems. Constant change: The very nature of EAI is dynamic and requires dynamic project managers to manage their implementation. Shortage of EAI experts: EAI requires knowledge of many issues and technical aspects. Competing standards: Within the EAI field, the paradox is that EAI standards themselves are not universal. EAI is a tool paradigm: EAI is not a tool, but rather a system and should be implemented as such. Building interfaces is an art: Engineering the solution is not sufficient. Solutions need to be negotiated with user departments to reach a common consensus on the final outcome. A lack of consensus on interface designs leads to excessive effort to map between various systems' data requirements. Loss of detail: Information that seemed unimportant at an earlier stage may become crucial later. Accountability: Since so many departments have many conflicting requirements, there should be clear accountability for the system's final structure. Other potential problems may arise in these areas: Lack of centralized co-ordination of EAI work. Emerging Requirements: EAI implementations should be extensible and modular to allow for future changes. Protectionism: The applications whose data is being integrated often belong to different departments that have technical, cultural, and political reasons for not wanting to share their data with other departments See also Enterprise architecture framework Strategies for