The product defines a four layer software architecture.
The presentation layer exists in two different forms:
The layer of the application logic, which executes defined Use Cases as Application Server on the web server.
The layer, in which production data is saved secure and persistently according to open, platform independent standards (Persistence).
The Reference Architecture layer, in which the product is installed and operated. See also “Reference Architecture and Installation”.
The product uses open source software libraries. You can find the corresponding copyright comments and terms of license on the product DVD in the directory <DVD drive>\Additions\Open Source Licenses.
Fabasoft app.ducx allows partners and customers to develop content based vertical applications (Composite Content Applications), for example to manage insurance claims or personnel files. These applications utilize all the advantages of Fabasoft Folio like scalability and platform independence. Fabasoft app.ducx fully integrates with Eclipse, a professional, freely available and platform independent development environment for Microsoft Windows and Linux.
Besides the classical extension of the object model, it is also possible to add additional metadata to objects without programming knowledge based on a graphical form editor.
Fabasoft app.test is a non-stop use case based test environment for Composite Content Applications based on Fabasoft Folio. Tests that have been recorded can be run in parallel on different operating systems. Fabasoft app.test is part of the Fabasoft DUCX family and therefore enables numerous applications such as Fabasoft Folio, Fabasoft Mindbreeze Enterprise and E-Services to be integrated via Liferay Portal. By implementing and running the tests on various platforms, the functionality can be tested in various environments. Thanks to Fabasoft app.test, it can be confirmed in just a few steps automatically that Composite Content Applications are working reliably on all supported platforms.
The product specifies interface calls on the basis of SOAP and XML. So it is possible to implement solutions, which import incomings for example.