jump to navigation

EAI project strategies-2. Requirements July 27, 2009

Posted by Terry.Cho in Architecture, EAI.
Tags: ,
6 comments
First pesepctive, EAI system requirements.
Waht is EAI system requirement. Commonly EAI system requirements are defined based on business like below.
Internal integration
This is integrating internal enterprise system. A lot of these types of integrations are “on-line”(real time).
Sometimes it uses XA based distributed transaction to support data integrities.
External integration
This type is B2B integration. System is located on external of the enterprise.
One of interest thing of this type is using dedicated network like dedicated TCP/IP or X.25 network
It impacts EAI architecture style. For example we have 2 X.25 line for some company. But we have 10 EAI system instances. What shall we do?
We have to consume request by all of the EAI instances and route the request to EAI instances that has been connected to X.25 line.
And we have to think about fail over when the X.25 connected EAI instance down.
In B2B style integration, it is very hard to use XA based distributed transaction. So we need another way to support data integraities like by using transaction trace logs etc.
Batch
In integration world there are two requirement about Batch. (Bulk data integration.)
One is for online business and the other one is for data anlaysis.
First thing is handling transaction data in online system. Apply data changes to the other system.
It happened about a few seconds later after original change has been made. We call it as “Defered or Near-Realtime”.
In this case, because it is online transaction data, integrity of the data is very important. So someimes XA is used.
Sencond case is for data analysis. Aggreate data into data warehouse and generate report. EAI has a role to gather data to warehouse.
This job is usally happened after office hour and amount of data is very huge. Commonly EAI doesn’t not handle this type of data trasfer.
This is ETL (Extract Transform Loading) area.
Simply i summarized EAI system business boundary based on business type.
But when we design EAI architecture, we have to think about MEP (message exchange patterns)-Sync,Async,Fire & Forget,Master Detail and Multiplicities (1:N,1:1 etc)
In addition OAM (Operation, Administration and Monitoring) requirements are defined in this phase.

First pesepctive, EAI system requirements.

Waht is EAI system requirement. Commonly EAI system requirements are defined based on business like below.

eaitype

Internal integration

This is integrating internal enterprise system. A lot of these types of integrations are “on-line”(real time). Sometimes it uses XA based distributed transaction to support data integrities.

External integration

This type is B2B integration. System is located on external of the enterprise. One of interest thing of this type is using dedicated network like dedicated TCP/IP or X.25 network.  It impacts EAI architecture style. For example we have 2 X.25 line for some company. But we have 10 EAI system instances. What shall we do? We have to consume request by all of the EAI instances and route the request to EAI instances that has been connected to X.25 line. And we have to think about fail over when the X.25 connected EAI instance down.

In B2B style integration, it is very hard to use XA based distributed transaction. So we need another way to support data integraities like by using transaction trace logs etc.

Batch

In integration world there are two requirement about Batch. (Bulk data integration.)

One is for online business and the other one is for data anlaysis. First thing is handling transaction data in online system. Apply data changes to the other system. It happened about a few seconds later after original change has been made. We call it as “Defered or Near-Realtime”.In this case, because it is online transaction data, integrity of the data is very important. So someimes XA is used.

Sencond case is for data analysis. Aggreate data into data warehouse and generate report. EAI has a role to gather data to warehouse. This job is usally happened after office hour and amount of data is very huge. Commonly EAI doesn’t not handle this type of data trasfer. This is ETL (Extract Transform Loading) area.

Simply i summarized EAI system business boundary based on business type. But when we design EAI architecture, we have to think about MEP (message exchange patterns)-Sync,Async,Fire & Forget,Master Detail and Multiplicities (1:N,1:1 etc) In addition OAM (Operation, Administration and Monitoring) requirements are defined in this phase.