XERP Topology...
Each module from Data To Presentation is made up of the following...
*DAL project,
*WCF Data Service Project,
*Domain Project and a
*Client.WPF project...

The DAL Project will house the entity model and the tables defined to the entity model and will serve as the conduit to the DataBase...

The Service Project will consist of a WCF Data Service and serve as the conduit to deliver the data to the Client Layers Domain Project...

The Domain Project will have reference to the WCF Data Service and house all of CRUD calls...

The WPF.Client Project will be the MVVM it utilizes both the WCF Data Service for its modeling which is nothing more then a projection of the DAL Layers Entity... As well it consumes the Domain Layer to broker CRUD in the View model... And of course it will contain the view that brokers the data to the client for human interaction...

We use the CompanyMaintenance as an example from DAL to Client you can see how it is traversed through the XERP Topology...

XERP Topology.gif

It is important to note that XERP is extremely modularized so that their will be hundreds of these modularly linked projects in the same format...
One for Order, One For Quote, one for Part and so on... in some instances multiple UI's may utilize the same Domain and DAL when it is prevelant to do so... But for the most part and general rule of thumb each modularized build will target a specific functionality and shape its DAL to Client Presentation accordingly; providing hundreds of Entities that are very paired to the targeted functionality they are to present...

XERP Server Configuration Diagram...
With the above topology for mentioned configuring 100's of entities in one place is required and extensive work was done to allow for just that...

Using the diagram below you can see that XERP has a special XML Config file that is navigated to from the Web Config that is published to the Application/Web Servers Build Folder... Each XERP WCF Data Service will share this Web Config from the build folder allowing XERP to be placed any where on the physical Application/Web server as long as the Web Config is fixated to implore XERP as to where to look for the Special XML Config File...
As well the meta data for the entity is parsed out of the entity config string and placed as a string property in the DalUtility Class for the given modular DAL Project. Allowing us the parse the entity meta data and the fixed SQL connection string apart and back together again at any given moment w/o having the string in its entirity in the Web Config...
Server Config Diagram.gif

Last edited Sep 21, 2012 at 9:00 PM by MattPaulson, version 3

Comments

No comments yet.