Specifications per node type of the database servers when files
The following table shows the recommended virtual memory (VM) If Liquibase finds an empty database schema it initializes the databaseīy creating all the needed tables, sequences, etc.įor this process to work, the application needs schema editing permissions The database schema is created by the Flowable Work on its initial startup So other database implementations may also work but they are not officially The following databases are officially supported and tested with Flowable Work: Databaseįlowable Work uses a standard JDBC connection and database interfaces You can deploy Flowable Work to any Servlet 3.1 or later compatible containerīut at least Tomcat 8.5.x is required and Tomcat 9.X is recommended.
Java 8, 11 or 17 is required.Įxplicit build support is provided for the following build tools: Build Toolįollowing embedded servlet containers are supported: Name Development įlowable Work is built on Java and Spring Boot. The number of users and the expected number and size of the documents. Memory and disk space requirements depend on the specific use cases modeled, Your own requirements may vary from the values stated here depending on your particular usage scenario. The following prerequisites are based on experience with production systems and average user and data volumes. Reverse proxy functions as well as load balancing between clustered instances of the Flowable ServerĪre handled by any WebSocket capable load balancer such as NGINX.įlowable Design is used to create the application models (BPMN, CMMN, DMN, Forms) and deploy themīundled as apps to the Flowable Work server.įlowable Control provides information about runtime state of processes, cases, tasks, etc.įor lightweight use-cases it is possible to only use the required dependencies. ThisĪ JMS/STOMP compatible customer specific messaging queue implementation. Multi node clustering are achieved with the help of a messaging queue. To ensure high performance query and reporting of data a clusterable index server based onĮlasticsearch is used in addition to the database.Ĭonnection to additional communication adapters (like WeChat, WhatsApp, LINE, Facebook, etc.) and stateless The communication between the Flowable application happens through the Flowable REST APIs. It is possible, but not mandatory, to use the same database for all Flowable applications. Persistence is provided using a JDBC interface allowing for connection to the most commonly used database implementations.ĭatabase initialization and migration are automatically handled by the server by using
It can be served directly by the Flowable Server or by any HTTP server. The Flowable Front End is a decoupled JavaScript browser application written inĬommunicating with the servers REST API over HTTP(S) and WebSockets with the help of Spring Boot web application providing its functionality over a stateless REST API. The Flowable Server is designed as a Java based WeChat Adapter ( Optional for Flowable Engage Only).WhatsApp Adapter ( Optional for Flowable Engage Only).WebSockets / SockJS ( Flowable Engage Only).JMS / STOMP-compatible queue, such as ActiveMQ ( Flowable Engage Only).It is based on commonly used application frameworks, components and protocols such as: Where Flowable Work is referenced, this will also apply for Flowable Engage Architecture Overview įlowable Work is a highly dynamic case management applicationĪnd also allows real time communication between its users. Most steps are identical for both products but where they apply to just one of the products, this is clearly indicated.
HOW DOES STICKY PASSWORD CREATE ACCESS TOKEN INSTALL
The document describes basic information needed to install Flowable Engage or Flowable Work. Detailed Installation of Flowable Engage or Flowable Work
0 kommentar(er)
