System architecture


Xima® Formcycle is a pure Java application that can be run on any operating system that supports Java and has installed an application server such as Tomcat or JBoss. It is based upon a modularized or layer oriented component architecture. All interaction with a database is managed by the Java Database Connectivity API (Jdbc).

System architecture without a frontend server

Architecture of Xima® Formcycle when run with only a single master server.
ModuleDescription
API (REST)REST interface for administrative settings. May be used to integrate the Xima® Formcycle interface into other programs.
API (RPC)Provides access to form records, states, workflow processing, actions and more.
CommonServices and functions common to all layers.
DAOData access object, for accessing the database (Jdbc databases) or the file system.
FrontendAdministration interface
LogicLogic layer of the application.
Logic (Plug In)Provides support for custom plugins that provide additional functionality.

System architecture with an optional frontend server

Architecture of Xima® Formcycle when using both a master server as well as a frontend server.

Setting up a frontend server may be useful for the following use cases:

  • network installation, such as local intranet + DMZ
  • load distribution
  • splitting (multiple client, each with their own frontend server)
  • customer specific extensions (such as integrating Xima® Formcycle into existing user interfaces)
ModuleDescription
API (RPC)Provides access to form records, states, workflow processing, actions and more.
BSVBidirectional socket connection between the master server and the frontend server.
CommonServices and functions common to all layers.
FrontendStatus information of the current server, or own interfaces