Komponenty a moduly

ALBIQ consists of well selected technological components as can be seen in subsequent figure. More options of some parts of the system are available for a company in order to choose by its specific constraints and preferencies. This powerful framework provides rule engine, along with other functional engines, which are integrated into the service application layer. Business rules can be invoked on every service call, even on the service to service call. Services are invoked by XML messages and the messaging being an integrated part of ALBIQ.


System modules

System services are necessary for correct ALBIQ processing. All these may be used also by the rule engine or business logic:

  • Service Registry – all the services have to be registered in service registry
  • GUI definition – definitions of graphical user interface
  • List settings – store of private/public settings of lists
  • Property service – store of all properties of the sytem
  • Client command – sending of the commands to clients (Comet support)
  • File upload – support of processing of the electronic files
  • Audit log – auditing of information for the system
  • Users and Roles – Information about users and assignment  of their roles
  • Proces engine – support for process automatization
  • Rule engine – support for rules definition and execution 

Business modules

We develop business services with reusability in mind. These ALBIQ modules are now utlized in many production systems:

  • Mail service – for sending and receiving emails
  • Scheduler service – for scheduling some repeatable operations
  • Script service – for scripting some actions in other languages than Java (Groovy, JPython, etc.)
  • Report service – for starting reports from reporting system