Website navigation:
EAI Integration Models
Basically there are three integration models or EAI approaches which are outlined here in short. The pros and cons of the specific models are presented. The relevant approaches´ technologies are detailed in the following.
Data Level Integration is the integration of systems by the exchange of information on the level of data management, e.g. like as in databases via JDBC. This marks the entry level of EAI and is offered by a lot of systems and tools. In the majority of cases there is no need of system changes or enhancement for the integration of the systems, the integration is done manually in the target application or by selected interfaces. Both means a very tight coupling of the systems which implies that changes in one system result in the need of many further changes in the network. Generally this is very complex and boosts maintenance and development costs.
Message Level Integration realises integration on a message exchange basis. This type of asynchronous communication enables a better controllable information exchange and a loose coupling. In contrast to the data level integration, message exchange is supported directly or indirectly by the systems to be integrated. The existing systems need an interface allowing the sending and receiving of messages. This infrastructure can be established in a cost-efficient way using technically matured products. If realised properly this can reduce development costs significantly, in particular regarding the integration maintenance. This is particularly given by the loose coupling of systems which guarantees an easy expandability and adaptability of the systems.
Process Level Integration extends the message level and supports the integration on a business process basis. The EAI middle ware acts here as a process- or workflow- engine which undertakes the routing of the information in the complete system on the basis of flexibly defined workflows. If there is a need of process oriented integration, this approach is the best way to implement an integration concept. By the use of a process engine, the coupling of the underlying systems and the involved user interaction can be adapted flexibly to the current business model.
Data Level Integration is the integration of systems by the exchange of information on the level of data management, e.g. like as in databases via JDBC. This marks the entry level of EAI and is offered by a lot of systems and tools. In the majority of cases there is no need of system changes or enhancement for the integration of the systems, the integration is done manually in the target application or by selected interfaces. Both means a very tight coupling of the systems which implies that changes in one system result in the need of many further changes in the network. Generally this is very complex and boosts maintenance and development costs.
Message Level Integration realises integration on a message exchange basis. This type of asynchronous communication enables a better controllable information exchange and a loose coupling. In contrast to the data level integration, message exchange is supported directly or indirectly by the systems to be integrated. The existing systems need an interface allowing the sending and receiving of messages. This infrastructure can be established in a cost-efficient way using technically matured products. If realised properly this can reduce development costs significantly, in particular regarding the integration maintenance. This is particularly given by the loose coupling of systems which guarantees an easy expandability and adaptability of the systems.
Process Level Integration extends the message level and supports the integration on a business process basis. The EAI middle ware acts here as a process- or workflow- engine which undertakes the routing of the information in the complete system on the basis of flexibly defined workflows. If there is a need of process oriented integration, this approach is the best way to implement an integration concept. By the use of a process engine, the coupling of the underlying systems and the involved user interaction can be adapted flexibly to the current business model.
© 2013 X-INTEGRATE Software & Consulting GmbH Im Mediapark 2 50670 Köln
Contact
