EAI project strategies-1. Approach July 24, 2009Posted by Terry.Cho in Architecture, EAI.
Even if EAI (Enterprise Application Integration) has been introduced a few years ago. Enterprise Application Integration is still important in Enterprise Architecture. From this post i will explain a strategies to success EAI project.
How to approach EAI project ?
There is 4 perspectives to sucess EAI project.
First, requirement for EAI. Define target integrated business system (ERP,CRM,SCM etc). What kinds of interface will be used? (Socket? WebService? EJB? IIOP? MQ etc). How can we trace transaction and fault. What is target performance. What is message exchange patterns (Sync/Async/Batch etc).
In common EAI system can have a lot of capabilities, but no one can implement all of things. We have to extract EAI requirement based on customer’s requirement & environment.
After defining requirement, we can design conceptual architecture.
One of differences EAI is, EAI integrated other systems. It means it has a lot of “Communication” in the project. We have to sync EAI interface between sender side of business unit and receiver side of business unit. In Enterprise , number of interface usually over 300~400 number. So managing communication and collaboration for implementing interface between different business units.
Development & Production Enviroment (Deploy)
As i mentioned in “Process”, EAI project has a dependency to other business system implementation project. In their implementation phase, EAI system has to provide integration between development environment of other business system. In addition EAI project team also has to have their own development environment.
In case of EAI system, it can have dedicated network line for B2B for example X.25 etc. So we have to consider deployment plan with the network line migration plan.
From next post i will explain about these 4 perspects with more detail.