EAI project strategies-3. EAI Implementation Process July 27, 2009Posted by Terry.Cho in Architecture, EAI.
Tags: EAI, Implentation, Process, Strategies
add a comment
Second is delivery process of EAI project.
In perspective of traditional water-fall model, to do item is like below.
In this phase we define “What to do EAI system ?”
1) Define interface type
It is about, what business systems are integrated? What is techical interface type of the system (EJB,IIOP,MQ,Web Service etc). In this phase, decide to what interface use XA.
2) Define MEP (Message Exchange Pattern)
Gather requirement of MEP. Sync,Async,Real time, Near real time and multiplicities (1:1,1:N etc)
3) Define Message structure
Define message format. What header fields are required? What format will be used? (MFL?Text?XML? etc)
After finishing Analysis phase, we understand the EAI system what will do.
1) Design architecture
Based on requirement from analysis phase. Design architecture and system.
2) Implement prototype
With the design, prioritize most critical functionalities and design and implement prototype.
3) Test with prototype
Valdating prototype and enhance architecture
4) Gather interface list
Gather interface list what business system and functional will be integrated.
EAI project has a dependency to schedule of other business systems. Based on interface list and integration schedule, EAI system arrange their interface implementation schedule.
Important thing in design phase is validate architecture. After validating the architecture, EAI team implement interface with validated architecture by factory job.
Removing risk in design phase is important because architecture related changes are requires a lot of resource and time. So removing risk in beginning phase enables reduce cost.
1) Implement interface
Implement interface based on schedule. EAI interface implementation impacts business team implementation. Because business system communicates by using EAI system.
2) Step by step transition
Transition (Deployment) plan in EAI is very important. As i mentioned lot of time EAI system has dependencies to other system and it also has dedicated network line (X.25 etc)/
So during implementation interfaces deployed in development system. After validating the interface, it is deployed to staging system. Other business system connected the staging system.
Finally all of implementation has been finished and ready to move production, EAI system is deployed into production environment.
I will describe more about deployment environment later.
3) Monitoring and fix
After starting deploying interface to staging system. (Open interface to business team). EAI project team monitors the interfaces. The interfaces always has errors like “Table comlumn mismatch”,”Message type missmatch” etc.
The error let the interface down and it brings complain from business development team.
In implementation phase, support business team to follow up their schedule by matching EAI interface implementation schedule. If delay is occurred, business team try to responsibilities to EAI team for the schedule delay.
And there are many requirement change like number of interfaces, type etc. So in the implementation phase, interface schedule management is very important.
As i mentioned EAI project has a lot of dependencies to other system or project and their are many requirement changes about interfaces. In EAI project how to manage schedule and environment is very important to success EAI project
EAI project strategies-2. Requirements July 27, 2009Posted by Terry.Cho in Architecture, EAI.
Tags: EAI, Requiements
First pesepctive, EAI system requirements.
Waht is EAI system requirement. Commonly EAI system requirements are defined based on business like below.
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.
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.
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.