Design And Implement Of IEAI Server

The design of software architecture has been attached importance more and more in course of developing modern software. Software architecture not only can direct each process of development, but also can affect the life-cycle of post-development, and especially can decrease the cast and difficulty of software maintenance and software evolvement. I designed the architecture of iEAI Server that is a critical part of iEAI system which is a product of Changchun ideal technology Ltd.This paper analyzed the function requirement of iEAI Server at first. It analyzed the remote communication means between client and server, the function of data marshal and unmarshal and the data security while communicating. Then it analyzed other function of iEAI Server. This paper used UML to model requirement in course of analysis.After analyzed the requirement of iEAI Server, I introduced four kinds of important system architecture patterns which are Layer, MVC, Broker and Microkernel. Then I introduced their characteristics of implement and their highlights, and designed the system architecture of iEAI Server, that is called iEAIKernel- Based iEAI Server architecture design blue print, which referenced four kinds of system architecture patterns mentioned above.In this architecture, the iEAI Server was decomposed into several components, such as system communication service, distributed server's cluster manager, message service, security service, repository service, workflow engine, Web service and log service, etc. Every component has its interface which will be used by other components to forward service requirement to it.In most case, function invoking is the main means of communication between a component and other component. However, it is not the case in this paper. This paper used request/respond technique , which was coordinated by iEAI Kernel. All of components must be registered in iEAI Kernel at the beginning of bootstrap of iEAI Server. A component packs a service into a Request pack when it need a service which is provided by another component, then forwards the Request pack to iEAI Kernel. When received the Request pack, iEAI Kernel forwards it to the corresponding service provider. After received the Request pack, the service provider executes corresponding service, makes a Response pack when finished service and forward the Response pack to iEAI Kernel. When received the Response pack, iEAI Kernel forwards it back to the sender of the Request pack. The difference between the communications this paper used and function invoking is the former relaxed the coupling of every component of iEAI Server, enhanced the maintainability of system and the reusability of each component. Because each component doesn't need to know the location of service provider when it requests a service, the one thing it should know is the iEAI Kernel, therefore this communication method implements the location- independent of components. This method also makes us easy to deploy a distributed running environment.Beside of the responsibility for coordination communications between components, the iEAI Kernel is still responsible for iEAI Server's bootstrap, initialization and shutdown, and for managing components, such as each component's loading, start, initialization and stop. When we need to add or remove a component, we should only to modify a few of lines code of iEAI Kernel. The modification to iEAI Kernel doesn't affect the added or removed component and other service component. So the architecture of this paper enhanced the expendability and the contractility of iEAI Server.After introduced the architecture of iEAI Server, I designed and implemented part of components of iEAI Server.At last, some problems that should be dealt with in the further are pointed out, which include more effective arithmetic of marshal and unmarshal and dynamic substitution and upgrade of component.