Architecture

System requirements & Hardware

WEDIA WMS is installed in minutes with no required programming knowledge. The CMS can be deployed on a minimum configuration: Dual Pentium Pro 2GHz, 1GB RAM, 1 GB HD. Note that WEDIA WMS Free Edition version is offered with an automatic installation (Tomcat servlet container and Hypersonic database). Click here to download WEDIA WMS Free Edition.  After download, the installation takes less than 5 minutes.

WEDIA WMS can be deployed on most of the standard middleware (application servers and databases). See also the requirements page for more technicals details.

Template

The appearance of a web page in WEDIA WMS is defined by JSP templates, while their functionalities are defined through contents, controls and rules. 

WEDIA WMS  :
- offers JSP tagLibs and Java API that can be used with any IDE (as Eclipse) and any revision control system (as Subversion).
- provides Ajax API sugar and Web 2.0 possibility
- proposes a native HTML structure to ease developement and maintenance
- supports Groovy scripts

WEDIA WMS adds a layout mecanism in order to ease the template integration.

Plugin

Plugins are independent composant living inside of WEDIA WMS.

WEDIA WMS comes with several pre-built plugins : multi language management, block management, SEO management, multimedia gallery,...All standard WEDIA WMS plugins are managed and supported by the WEDIA WMS product team (with subscription).

The WEDIA WMS developers can add or share their plugins. One plugin can be activate or desactivate.

For maintenance issues, it is strongly recommanded to never modify a plugin you are not the author. If you want to customize an existing plugin, you should duplicate and rename it.

A plugin includes application code, parameters, documentation, static ressources and java librairies (not mandatory).

Objectives from plugins :
- isolation of a simple or complex feature for reuse or sharing
- ease upgrade (new version library media, SEO, ...)
- enable / disable product feature. All main features as "multi language" are implemented by plugins. As an exemple, it's possible to enable the "web audience" plugin
- natural separation between standard product features and project customization

Extendable and personalized tools

WEDIA WMS is an "out of the box" solution. It can also be extended with external java libraries (web services, etc...) or javascript librairies (API Google Maps, API Twitter,...). Note that the standard back office can be customized easily by role and content type.

Deployment

A Backup-Restore module is provided. It allows to backup or deploy your application structure, contents and jsp. Backup-Restore module supports scripting.

The Backup-Restore module can be used to achieve:
- a full update (all templates, setting, content types and all data) => for exemple in order to init a new production server
- a partial update with just a few necessary elements => for exemple for update by patch

The Backup-Restore module is unconstrained environment. It is possible to backup / restore from a WEDIA WMS - Tomcat -  MySQL Windows platform, and restore on a another WEDIA WMS - WebLogic - Oracle Linux platform.

The module also allows deploying SQL database structures with a automatic management conflicts.

Contents backups can also be achieved using traditional backup tools (database, file system).

Dynamic Virtual Hosting

After setting up a WEDIA WMS application, dynamic virtual hosting allows you to use this same installation to spin-off several web sites, each with its own unique URL, look&feel and functionality.

For each site, you can add domains&subdomains and domains&subdomains by language.

For example, after a quick setup of subdomains by language, a user calls the home page from the english Wedia web site (en.wedia-group.com) : WEDIA WMS resolves automatically the english version homepage. Same for the Spanish version for the URL es.wedia-group.com.