 |
|
|
|
|
|
|
|
 |
 |
|
|
 |
|
|
| | Enterprise Application Integration (EAI)
|
| |
Enterprise Application Integration (EAI) and Data Synchronization are System-To-System integration
approaches which address the need to move information between different software applications.
|
|
 |
EAI is a computing term for the plans, methods, and tools aimed at modernizing,
consolidating, and coordinating the existing computer applications in an enterprise.
This approach is typically utilized when an enterprise is adding or migrating to a new set of applications
and wants to utilize existing legacy applications and databases.
EAI may involve developing a new total view of an enterprise's business and its current applications.
This approach involves seeing how existing applications fit into the new view,
and then devising ways to efficiently reuse what applications already exist,
while deciding what new software applications need to be added.
|
An EAI approach may very often involve dedicated software called middleware to orchestrate the
information flow. Middleware creates a hub-and-spoke type architecture (as shown below)
reducing the number of interconnections. EAI solutions focus on the integration of processes; not just data.
|
| | 
|
| |
EAI is characterized by the following:
|
|
 |
Focus on application/process integration over data integration |
|
Effort to create a hub-and-spoke architecture to reduce the number of interconnections |
|
May involve dedicated software to orchestrate the information flow: middleware |
|
Although it may involve specific products, EAI is not a product - rather EAI is an approach
|
Data Synchronization
Data Synchronization (Synch) products are related to EAI in that they both represent forms of
System-To-System integration. Synch products focus on data integration as opposed to
process integration, and are usually very specific as to the systems they integrate.
They are also called "point-to-point" integration products.
|
|
|
Synch products are sufficient for many 2-system integrations |
|
They are sometimes used as specific spokes in an EAI architecture |
|
They range in operating mode: from immediate (triggered by inserts and updates) to
periodic batch processing
|
How do EAI and Data Synchronization systems relate to Veraterm?
Veraterm enhances both EAI and Data Synchronization solutions by improving data access workflow
between the user and multiple database applications. Veraterm provides a complete
"view" of information by combining data from multiple systems.
"System-to-system" integration solutions do not necessarily provide complete views
of information from any one place, since not all data is (or needs to be) shared
between all systems in the hub.
For example, given the presence of just two systems
|
|
|
Contact Management (ie: ACT! or Goldmine) |
|
Accounting (ie: QuickBooks Pro or Great Plains)
|
These two systems are only synchronized at the contact-customer demographic level.
The contact management system does not contain the invoices found in the accounting system;
and the accounting system does not contain the record of phone calls found in the contact management system.
Each of the two systems has different purposes. Information from both systems is
needed for a complete view of a contact or customer.
The Veraterm System not only can provide a combined view of information, but it does so
automatically from within a user's document. This intelligent data access process
is used to enhance workflow and increase productivity. Veraterm, therefore, does
not compete with EAI solutions and Data Synchronization products; rather Veraterm is
complimentary to their functionality.
|
| |
 User-To-System Integration
|
|
