Overview
Enterprise Application Integration is an integration framework is a set of technologies and services, a middleware for the integration of systems and applications are possible across the enterprise.
Chain management applications (for inventory management and shipping) Management Solutions (customer relationship management for existing and potential customers), applications (business intelligence to find patterns from existing data from operations) and other types of applications (data such as personal data management, healthcare, internal communications, etc.) usually can not connect to exchange data or business rules. For this reason, these applications are sometimes called islands of automation or silos of information. This lack of communication leads to inefficiencies, in which identical data is stored in multiple locations, or simple processes can not be automated.
application integration (EAI), the process of linking these applications in a single organization together is to simplify and automate business processes as possible while at the same time to avoid radical changes to existing applications or data structures. In the words of Gartner Group, EAI is pass the exchange of data and business processes among connected applications or data sources nrestricted in enterprise.1]
A major challenge is that EAI of the various systems should often linked with each other on different operating systems to live, the use of solutions of various databases and other computer languages, and in some cases, existing systems, which created no longer supported by manufacturer originally. In some cases, these systems are “stove pipe” systems because they are components that are bundled in ways that change very difficult in any façon.Améliorer connectivity

does exist, if the integration without is applied according to a structured approach to EAI, point to point connections grow within an organization. The dependencies are added to the blue, resulting in a tangle that is difficult to maintain. This is often referred to spaghetti, an allusion to the programming language equivalent to spaghetti code. For example:.
The number of connections are necessary to a fully meshed connections from point to point, with points given is of n by It integrates applications for full ten point to point or 45 point to point connections are required.
However, EAI is not only the exchange of data between applications focused, they are to exchange business data and business processes. Analysts participate middleware EKI is the system of systems that examine large-scale interdisciplinary problems involves multiple heterogeneous, distributed systems, the built-in. Networks at various levels

limit EAI EAI can be used for various purposes:
data (information) integration: ensuring that information in different systems maintained constant This is also known as EII (Enterprise Information Integration)
vendor independence .. Extracting business policies or rules from applications and their implementation in the EAI system, so even if one of the applications business is replaced by the use of another supplier to the trade rules can not be reused implemented
common front. An EAI system could front a cluster applications and offers a single interface to access and in accordance with these requirements and users must learn to protect interact with various software.

models EAI integration models are two patterns to implement the EAI systems: mediation

Here, the EAI system acts as an intermediary or broker between the interface (or communication) from multiple applications, whenever. an interesting event occurs in an application (for example, adds new information, new transaction completed, etc.) an integration module in the EAI system is notified. The module then changes to other relevant applications. Federation

In this case, the EAI system is used together as a front for many applications. All are in front of the “outside world” in one of the applications-ended by the EAI system. The EAI system is configured so that only the relevant information and interfaces to uncover the underlying applications to the outside world, and performs all interactions with the underlying applications on behalf of the applicant.
Both models are often simultaneously. The same system can be used multiple EAI applications are kept in sync (mediation), the service requests from external users against these applications (federation).

access modes EAI supports access asynchronous and synchronous models, the former being typical in the case of mediation and in this case Federation.

models for the life of an operation integration could be short (eg maintenance data in sync between two applications could be completed within one second) or long (for example, one of the steps could EAI System . involve interaction with the last application of workflow man on the approval of a loan, the hours or days) will

EAI topologies There are two major topologies: hub-and-spoke, and bus. Each has advantages and disadvantages. In the “Hub and Spoke, the EAI system in the center (hub), and interacts with applications via the spokes. In the model bus, the system EAI is the bus (or as a module residing in a message . Bus existing message-oriented middleware implemented)

Technologies Several technologies are in the implementation of the various components used in the EAI system: Bus
/ Hub
This is usually by increasing the standard middleware products (application server, message bus) or implemented as a standalone program (not implemented not so used, middleware), as its own middleware.

The demand for connectivity Bus / hub of applications by a number of adapters (also male). These are programs that know how to interact with an application of the underlying management. The adapter performs two-way communication, the execution of requests from the hub of the demand and on the hub when an event of interest occurs in the knowledge application (inserts a new record, a transaction is completed, etc..) adapter can be built specifically for an application (such as libraries with the client application service provider ) or a specific class of applications (for example, can interact with any application using a standard protocol such as SOAP or SMTP). The adapter can be in the same process space as the bus / hub or run will be stored in a remote place interact with the hub / bus through the industry standard protocols such as message queues, Web services, or even a proprietary protocol. can be independently created by the vendor in the Java world, standards such as JCA adapter.
data format and processing
have all the adapters to convert data to / from all formats of other applications, EAI systems usually before, a separate program (or common) .. The data format EAI system usually is a service for data transformation and for the conversion between application-specific formats and common this is in two stages. the adapter converts information on the format of the application for a common format of the bus Then, place names on this semantic transformations (transformation of postal code, splitting / fusion objects from one application to objects in other applications, and so on) applied.
The integration module
An EAI system could in multiple concurrent integration operations at any time to participate, and processes each kind of integration by another module integration . moduli integration subscribe to events of specific types and process notifications that they receive at these events occur, these modules can be implemented in different ways. on the Java-based EAI systems, these could web applications or EJBs or even POJOs that meet the specifications of the system for transactions EAI.Support

for process integration uses the EAI system also provides transactional consistency across applications by executing all operations integration across all applications in a globally distributed transaction (with two-stage protocols or compensating transactions).

communication architectures currently there are many variants of thought on what is the best infrastructure, component model, the structure and standards for enterprise application integration. It seems consensus to give you that four essential elements for an architecture for the integration of applications modern society.
a central broker, security, access and communication technologies can handle this through integration servers (such as the school setting Interoperability (SIF ) zone are achieved Integration Server) or similar software such as Enterprise Service Bus (ESB) model, which acts as a SOAP service-oriented manager.
An independent data model on a standard data structure. It seems that the use of XML and XML style sheets has become the de facto and in some cases legal standard.
A connector, or a model where each agency, the application or the interface can use a single component that can speak natively that the application and the communication with the central broker.
A system that defines the APIs, data flows and the rules of engagement for the system, so that integrated components to be with him in a standardized way interface.
Although other approaches have been explored how to connect to the database or on the user interface, they were not found to scale or be able to solve. Individual applications can publish messages to the central broker and subscribe to receive messages from this agent . Each application requires a single connection with the broker. This approach is highly scalable, centralized control and highly scalable.
enterprise application integration in technologies such as message-oriented middleware (MOM) and presentation of data technologies such as XML middleware. Other technologies, the use of EAI to include Web services come within service-oriented architecture as a means of integration. Enterprise Application Integration are more centered on the data. In the near future it will include content integration and business process is.

Traps EAI implementation in 2003 was reported to fail 70% of all EAI projects. Most of these errors are not the software itself or technical difficulties, but because of management problems. European Integration Consortium Chairman Steve Craggs seven major pitfalls of companies with EAI systems outlined has performed and explains the solutions to these problems.

The constantly changing nature of EAI is dynamic and requires dynamic project managers to manage their implementation œuvre.Pénurie />
EAI EAI requires knowledge of many subjects and aspects.

competing standards in the field of EAI, the paradox is that EAI standards themselves are not universal.
EAI tool is a paradigm
EAI is not a tool but a system and must be conducted as such.
create interfaces is an art
engineering solution is not sufficient. The solutions need to Service users will be negotiated to reach consensus on the final result. The lack of consensus on interface designs leads to excessive effort to switch between different data systems exigences.Perte />
information seemed irrelevant in an early . stage may become crucial tard.Responsabilisation />

D Other potential problems may arise in these areas:

needs EAI implementations should be extensible and modular, so that changes futurs.Le protectionism

applications whose data often belong to different ministries, the technical, cultural and political factors have do not use their data with other ministèresAvantages together pros and cons

access to information in real-time
systems optimized processes and helps increase organizational efficiency
manages the information across multiple systems integrity
The ease of development and maintenanceInconvénients

The high cost of initial development, especially for small and medium enterprises (SMEs)
require a fair amount of business design at the front, many managers are not able to check whether ready to invest in most EAI projects usually start the effort point to point, increase very rapidly unmanageable as the number of applications
The Future to the EAI are
EAI technologies still being developed and there is still no consensus on the ideal approach or the right set of technologies a company used to be. A common mistake is to other proprietary technologies, the open and extensible claim used to create, but vendor lock-in.

See also Business Management Semantic integrate

Integration of Enterprise Information Integration Enterprise

Enterprise Integration Patterns Enterprise Service Bus
Enterprise Reference Architecture and Methodology

Appliance Integration Competency Centers Generalized integration platform integration

Straight Through Processing Integration System
health initiatives and organizational level 7

Open Knowledge Initiative OSS through Java
Schools Interoperability Framework (SIF) solutions commercialesAvolution

Axway Frends iron – “Iron frends page Frends Technology
IBM WebSphere Message Broker iBOLTObjets

Interwoven Artix ESB Integration IONA Technologies
Microsoft BizTalk Server – Microsoft BizTalk Server Page “MOND Technologies

Oracle Service Bus (formerly BEA AquaLogic Service Bus)
Oracle BPEL Process Manager
Pervasive Software software progress

reconfigurable computing environment

Software AG webMethods soft sterling share trading

Sun Java CAPS

TIBCO Project Open source Apache Apache ActiveMQ

Camel ServiceMix Apache Apache Synapse

FUSE ESB (Enterprise ServiceMix)
FUSE Mediation Router (enterprise Camel)
FUSE Message Broker (Enterprise ActiveMQ)
Integration Server JitterBitMuleSource openAdaptor

OpenESB PEtALS ESBIntégration spring

Talend Virtuoso Universal Server-Reference ^

In its April 2001 report to AIIM International, “Enterprise Applications: a study of industry in the world: the adoption of e-business and technology documents, 2000-2001″ is defined, Gartner EAI as “unrestricted use of data and business processes between all connected applications and data sources within the company.
Gable, Julie (March / April 2002). “Integration of enterprise applications.” Journal of Management Information. http://findarticles.com/p/articles/mi_qa3937/is_200203/ai_n9019202. Retrieved 22/01/2008.Trotta ^
, Gian (12/15/2003). “Dancing Around ‘bear trap’ EAI”. http://www.ebizq.net/topics/int_sbp/features/3463.html. . Retrieved 6/27/2006
Categories: Enterprise Application Integration
BizTalk