Futica Content Management System

Futica Content Management System (FCMS) is developed using the very latest technologies like 100% Java/J2EE/XML platform independent system.

Default Enterprise FCMS includes the powerful JBOSS J2EE Cluster/Application Server, the stable Apache Front end web server, the fast MySQL database server and the popular Redhat Linux Operating System.

We can custom design features, if they are not supplied as Out-of-the-box functionality

Out of box Features

Dynamic and static content publishing

Browser-enabled work environment

Fully browser based using a customizable HTML workplace, which is similar to a file system. Supported browsers are: 

• MS Internet Explorer version 5.5 or higher on MS Windows 
• Netscape version 6.2 or higher on MS Windows, Macintosh and Linux 

Multi-Language

Supports the following languages: English, German and Italian. It is easy to implement languages by simply adding other language files.

Dynamic and static content publishing

The system is fully database driven. So, the managed website will be generated dynamically from the database. To guarantee a high performance output from databases, FCMS comes with an extensive caching, For other reasons sometimes you need a static version of your website or parts of your website. FCMS has a static export function to improve performance. You can choose for every folder if the content is delivered on the fly by dynamic page rendering or from the static version.

Asset Management

All pictures and files are managed in galleries to avoid data redundancies and easy handling of media files. FCMS supports the import of the common file types. The galleries can be quickly accessed from the WYSIWYG editor to preview pictures and adding them by drag and drop. You can manage a various range of galleries with variable access rights.

Integrated user management and permission system

Access to individual parts of the FCMS user interface, directories and files is controlled by the user and access permission management function. This guarantees an optimal overview and controlled access to protected areas. Every resource in FCMS has an owner, an associated user group and specific access rights (divided into read, write and visible) that can be assigned to the owner, the group and all others. This permission system is like the permission system known from UNIX or LINUX systems.

Project-based publishing

The project mechanism is similar to a typical work environment with work and live server. InFCMS content is maintained in projects. Projects are views to one existing copy of the online version. The number of projects is unlimited. Changes can be reviewed and approved and thoroughly tested before the project is published. You can also undo all unpublished changes (new/changed/deleted pages) to one or all pages in a project. You can define access and publishing rules for every project. This project mechanism avoids the need of a workserver.

Workflow and Task Management

Workflow for publishing content is set-up by default through roles and rights for these roles. The integrated workflow enables you to create tasks for your team members. Tasks can be accepted, forwarded, completed and recycled. You can post queries, messages and comments. All tasks remain in the system, so that a documentation of processes and responsibilities is created.

Template mechanism

The XML template mechanism using dynamic page rendering allows a strict separation of content and layout and a unitary display of content for a consistent corporate design. Every template is combined by two parts: the template XML file and an associated Java class. The Java class controls the rendering of the template file and includes dynamic content like navigation or personalisation. In simple cases the default template class can be used, for special purposes a customised class is needed. 

Each page is combined by several templates: The frame template for the corporate design, the content template as a container for the content and a body template for the edited content. Each template can call sub templates to include the rendered output. E.g. the frame template normally calls a navigation template to include the dynamic generated navigation. 

Combination of a template class and a template XML file is called an element. These elements can be combined in several ways. As described above elements can nest sub elements and several master elements can share sub elements. 

Element caching system

Internal page element caching mechanism that really speeds up page delivery.

Each element (a combination of a XML template file and a Java class) has its own caching space. 

Once an element is called its rendered output and its calls for sub elements will be stored as an element variant in this cache. (Each element has at least one variant. A personalized element has a variant for each user; a news-displaying element has a variant for each news that should be displayed.) All following calls for a variant will be delivered directly from the cache without rendering time. If a part of an element will be changed (like changing the XML template file) it results in a cleanup of the elements caching space to keep up to date.

Personalization

You can set up a ��web user management�� module, where you can add web users or the site visitors can register. You can use it for Newsletter mailings as well as for operating extranet zones with personalized content according to the collected user data.

Module System for additional applications

Standard interfaces enable you to integrate extension packages to the basic functionality. There is also a generic master module, which simplifies the development of extensions

A module is a collection of XML template files and Java classes. These files are organized in an Import/Export ZIP file. A module contains additional information like module name, description, author and version number. After the assembly of all resources in FCMS via the workplace the module can be exported. With such a module you can extend other FCMS systems like a production system. It��s fully integrated into the FCMS workplace and permission system. 

There are several standard interfaces to extend the core system. You can add administration items, views or resource types via the module system and extend the functionality of FCMS and its workplace. A module is an easy way to distribute FCMS extensions. 

Versioning

The page's history enables you to track which changes were made when and by whom. All of the previous versions are archived and can be restored, enabling you to access older versions at any time.

Scheduling System

Integrated scheduling system to invoke a method on a module java class at a specific time (periodically). The management of this scheduling is cron-like known from UNIX or LINUX systems. To create a schedulable module the class has to implement the interface I_CmsCronJob.

Synchronization Mechanism

The synchronization mechanism is used to synchronize files in the Virtual File System and their corresponding files in the Server File System. It��s a feature for development only. It speeds up the development cycle because you can modify the file on your Server File System with your favourite application and update the file in the file system

SSL-Support

A resource can be marked as https-only. These resources will only be delivered if the scheme of the request is set to https. The link replacement will automatically create correct https links to this https-marked resource. For this SSL-Support a web server with SSL-module and certificate has to be set up.

Import / Export of Content

Export portions or the complete website. The resources will be written to a zip-file. Additional information like properties or access rights will be stored in a single manifest file. This saved zip-file can be imported again into the same or another system. With this mechanism it is possible to archive snapshots of the website or to travel content from one system to another.

Application Server Integration / EJB Support

Application server environment provides facilities for making use of distributed object architectures, particularly with regard to Enterprise Java Beans technology. Using these techniques, processes behind the web site may be structured and distributed in a component oriented way.

Server sided presentation logic and business logic can be developed strictly separated, according to the four-tier architecture described in the J2EE Application Model: FCMS takes care of the presentation of the data, using the integrated template engine and master templates for displaying it in a general layout, while the generation of the content data is relocated to the EJB. 

FCMS can run directly on an J2EE aware Application Server like BEA Web logic, IBM Web sphere ,Oracle or Orion.

PDF / WAP Support

Deliver content in PDF or WAP format. To support these formats corresponding master templates are needed. 

Search Engine Support

A module for the java search engine ��lucene�� is used to search the managed website for end users.

Load Balancing/High Availability 

High traffic the load can be spread to several FCMS instances and Cluster Application Servers. 

Meta Tags

Meta tags created and attached to every resource in order to store individual information for indexing and management of information. This information is used for functions like building the dynamic template navigation or delivering Meta name information for search engines. The user can easily change the value of the properties. 

Any kind of properties and functions can easily be added, e.g. for storing target email addresses at email forms or to display output of dedicated news channels. 

Online-Help System

Integrated context-based online-help