(r3) XeoArchitecture < WebXEO

WebXEO Web>XeoPrimer>XeoArchitecture (revision 3) (raw view)~~EditAttach~~

-- Main.PedroRio - 14 Dec 2010
---+ XEO Architecture

XEO is a Java framework and XEO Applications are deployed in a J2EE Application Server (such as JBOSS, GlashFish). XEO's Architecture will be explained by layers (with a complete overview at the end). XEO is structured in three horizontal layers, which are set upon each other. The layers are XEO Data Layer, XEO Core System and XEO Client Controller Layer.

XEO's Data Layer, depicted in figure Arch.1, has two components. The Database Driver component and the component. The Database Driver is the connection to the DBMS where instances of XEO Object Models are to be saved while the Virtualization layer (at the time of writing not fully implemented) is the component which allows the use of other data sources (such as web services, XML databases, LDAP, etc..) for object instances.

<img width="987" alt="Architechture1.png" src="http://wiki.itds.pt/pub/WebITDS/XeoArchitecture/Architechture1.png" title="Architechture1.png" height="226" />

__Figure Arch.1 - XEO Architecture, only including its Data Layer__

In the second layer, XEO Core System, you find the XEO Engine. The XEO is responsible for all the abstractions seen in the [[XeoPrimerConcepts][XEO Concepts]] section, as well as some other features, such as XEOQL (XEO Query Language), which is a SQL-esque language used in XEO to query instances of XEO Models, or the XEO Java API which is the primary method of defining custom behavior for XEO Models. The XEO Core System layer is depicted in figure Arch.2, bellow. Even in runtime, XEO Models are grouped in XEO Packages (again, merely a logical grouping).

<img width="992" alt="Architechture2.png" src="http://wiki.itds.pt/pub/WebITDS/XeoArchitecture/Architechture2.png" title="Architechture2.png" height="600" />

__Figure Arch.2 - XEO Architecture with Data Layer and Core System Layer__

Above XEO's Core System Layer is the XEO Client Layer, which deals with the rendering of web-pages for user interaction. XEO Web Components have built-in security mechanisms, which allow to create rules where users may or may not see certain components in a given viewer (or see a viewer altogether). The XEO Client Controller Layer is depicted in figure Arch.3.

<img width="1008" alt="XEO Client Layer" src="http://wiki.itds.pt/pub/WebITDS/XeoArchitecture/Architechture3.png" title="XEO Client Layer" height="777" />

__Figure Arch.3 - XEO Data Layer, Core System Layer with the added Client Layer__

The XEO Framework not only allows for great customization of its XEO Models, has querying and security mechanisms (as well as a web layer) but can also be extended with the concept of a XEO Module. A XEO Module is a way of adding new features to XEO (which can be installed separately from the main framework). A XEO Module may define a set of XEO Models, have its own API, include existing Java libraries and interact with XEO's Java API to create the desired features. Presently, the XEO framework has been extended with two modules, one to allow interaction with XEO Model instances via web services (REST and SOAP) and one to integrate with a Business Process Management (BPM) engine. The ability to interact directly with XEO's Java API allows for modules to integrate in the Core System Layer, Data Layer or the Client Layer, as depicted in figure Arch.4

<img width="1008" alt="XEO Modules" src="http://wiki.itds.pt/pub/WebITDS/XeoArchitecture/Architechture4.png" title="XEO Modules" height="777" />

__Figure Arch.4 - Complete XEO Runtime Architecture__

In the next chapter we'll describe a sample application (which we'll use throughout the documentation, building an incrementally complex application), [[XeoPrimerLibraryIntroduction][read more]].

<strong> ___ </strong>

Attachments

Topic attachments
I	Attachment	Action	Size	Date	Who	Comment
png	Architechture1.png	manage	19.8 K	2011-03-18 - 09:31	PedroRio
png	Architechture2.png	manage	50.3 K	2011-03-18 - 09:32	PedroRio
png	Architechture3.png	manage	34.7 K	2010-12-14 - 14:44	PedroRio	XEO Client Layer
png	Architechture4.png	manage	49.0 K	2010-12-14 - 14:50	PedroRio	XEO Modules

Topic revision: r3 - 2011-03-18 - PedroRio

No permission to view TWiki.WebTopBar

No permission to view TWiki.WebBottomBar