[satisfied] it is very convenient for enterprise developed workflow platform - learning and reference - integrating distributed projects

WeChat official account SteveCode reply: flowable can get source code.


Deployment and operation of flowable UI

Download flowable-6.6.0 from the official website: https://github.com/flowable/flowable-engine/releases/download/flowable-6.6.0/flowable-6.6.0.zip

Compress the flowable-6.6.0 \ wars \ flowable UI in the package War dropped into Tomcat and ran
open http://localhost:8080/flowable-ui login with account: admin/test

Enter app Model creates a process and then exports it to the project for use, or configures apache-tomcat-9.0.37 \ webapps \ flowable UI \ WEB-INF \ classes \ flowable default Properties connect to the local database

Configure it like this:

# This is needed to force use of JDK proxies instead of using CGLIB
# The default domain for generating ObjectNames must be specified. Otherwise when multiple Spring Boot applications start in the same servlet container
# all would be created with the same name (com.zaxxer.hikari:name=dataSource,type=HikariDataSource) for example

# Expose all actuator endpoints to the web
# They are exposed, but only authenticated users can see /info and /health abd users with access-admin can see the others
# Full health details should only be displayed when a user is authorized
# Only users with role access-admin can access full health details
# Spring prefixes the roles with ROLE_. However, Flowable does not have that concept yet, so we need to override that with an empty string

# Examples are for Keycloak
#spring.security.oauth2.client.registration.keycloak.client-name=Flowable UI Keycloak


# DATABASE&nullCatalogMeansCurrent=true







# If uncommented, the datasource will be looked up using the configured JNDI name.
# This will have preference over any datasource configuration done below that doesn't use JNDI
# Eg for JBoss: java:jboss/datasources/flowableDS

# Set whether the lookup occurs in a J2EE container, i.e. if the prefix "java:comp/env/" needs to be added if the JNDI
# name doesn't already contain it. Default is "true".

# Connection pool (see https://github.com/brettwooldridge/HikariCP#configuration-knobs-baby)

# 10 minutes
# 5 minutes
# test query for H2, MySQL, PostgreSQL and Microsoft SQL Server
#spring.datasource.hikari.connection-test-query=select 1
# test query for Oracle
#spring.datasource.hikari.connection-test-query=SELECT 1 FROM DUAL
# test query for DB2
#spring.datasource.hikari.connection-test-query=SELECT current date FROM sysibm.sysdummy1

# Default Task Executor (will be used for @Async)

# Task scheduling






# The maximum file upload limit. Set to -1 to set to 'no limit'. Expressed in bytes
# The maximum request size limit. Set to -1 to set to 'no limit'.
# When multiple files can be uploaded this needs to be more than the 'max-file-size'.

# For development purposes, data folder is created inside the sources ./data folder



# Rest API in task application

# If false, disables the rest api in the task app

# Configures the way user credentials are verified when doing a REST API call:
# 'any-user' : the user needs to exist and the password need to match. Any user is allowed to do the call (this is the pre 6.3.0 behavior)
# 'verify-privilege' : the user needs to exist, the password needs to match and the user needs to have the 'rest-api' privilege
# If nothing set, defaults to 'verify-privilege'

# Enable form field validation after form submission on the engine side

# Flowable Admin Properties

# Passwords for rest endpoints and master configs are stored encrypted in the database using AES/CBC/PKCS5PADDING
# It needs a 128-bit initialization vector (http://en.wikipedia.org/wiki/Initialization_vector)
# and a 128-bit secret key represented as 16 ascii characters below
# Do note that if these properties are changed after passwords have been saved, all existing passwords
# will not be able to be decrypted and the password would need to be reset in the UI.

# Flowable IDM Properties

#flowable.idm.ldap.user=uid=admin, ou=system

# Keycloak



# Enable and configure JMS

# Enable and configure RabbitMQ

# Enable and configure Kafka

be careful:

You need to copy the java driver jar (MySQL connector java XXX. Jar) to apache-tomcat-9.0.37 \ webapps \ flowable rest \ WEB-INF \ lib

mysql 8.X remember to replace the current version

Flow chart Description:

  1. Events are usually used to model what happens in the process life cycle. In the diagram, there are two circles: start and end.
  2. A sequence flow is a connector between two elements in a process. In the picture is [arrow line segment].
  3. The gateway is used to control the flow of execution. In the picture is [diamond (with X in the middle)]
  4. user task is used to model tasks that need to be executed manually. In the picture is [rectangle].

Description of flow sheet:

1. All database tables of Flowable are represented by ACT_ start. The second part is the two character identifier that explains the purpose of the table. The naming of service API s also roughly conforms to this rule.

2,ACT_RE_: 'RE 'stands for repository. The table with this prefix contains "static" information, such as process definitions and process resources (pictures, rules, etc.).

3,ACT_RU_: 'RU 'stands for runtime. These tables store runtime information, such as process instance, user task, variable, job, and so on. Flowable saves run-time data only in the running process instance, and deletes records at the end of the process instance. This ensures that the runtime table is small and fast.

4,ACT_ HI_: ' 'Hi' stands for history. These tables store historical data, such as completed process instances, variables, tasks, and so on.

5,ACT_GE_: General data. Use in multiple places.

General data sheet:

act_ge_bytearray: binary data table, such as byte stream file of process definition, process template and flow chart;
act_ge_property: property data sheet (not commonly used);

History table

  1. act_ hi_ Act Inst: History node table, which stores the node information of process instance operation (including start, end and other non task nodes);
  2. act_hi_attachment: historical attachment table, which stores the attachment information uploaded by the historical node (not commonly used);
  3. act_hi_comment: historical opinion form;
  4. act_hi_detail: History detail table, which stores some information about node operation (not commonly used);
  5. act_hi_identitylink: historical process personnel table, which stores candidate and handling personnel information of each process node. It is often used to query the completed tasks of a person or department;
  6. act_hi_procinst: historical process instance table, which stores the historical data of process instances (including running process instances);
  7. act_hi_taskinst: historical process task table, which stores historical task nodes;
  8. act_hi_varinst: process history variable table, which stores the variable information of the process history node;
    Process definition table:
  9. act_re_deployment: subordinate information table, which stores process definition and template deployment information;
  10. act_re_procdef: process definition information table, which stores process definition related description information, but its real content is stored in act_ ge_ In the bytearray table, it is stored in bytes;
  11. act_re_model: process template information table, which stores process template related description information, but its real content is stored in act_ ge_ In the bytearray table, it is stored in bytes;

Process runtime tables (6, RuntimeService interface operation tables)

  1. act_ru_task: the runtime process task node table, which stores the task node information of the running process. It is important and is often used to query the to-do tasks of personnel or departments;
  2. act_ru_event_subscr: monitoring information table, not commonly used;
  3. act_ru_execution: the runtime process execution instance table, which records the branch information of the running process (when there is no sub process, its data corresponds to the data in the act_ru_task table one by one);
  4. act_ru_identitylink: runtime process personnel table, which is important and is often used to query the to-do tasks of personnel or departments;
  5. act_ru_job: runtime scheduled task data table, which stores the scheduled task information of the process;
  6. act_ru_variable: runtime process variable data table, which stores the variable information of each node of the running process;

User table

  1. act_id_group: user group information table, which selects candidate group information corresponding to the node;
  2. act_id_info: user extension information table, which stores user extension information;
  3. act_id_membership: relationship table between users and user groups;
  4. act_id_user: user information table, which selects the handler or candidate information in the corresponding node;

Process engine API and service

1. The repository service is likely to be the first service to use the Flowable engine. This service provides operations for managing and controlling deployments and process definitions. Manage static information,

2. RuntimeService is used to start a new process instance of the process definition.

3. IdentityService is simple. It is used to manage (create, update, delete, query...) groups and users.

4. FormService is an optional service. In other words, Flowable can run well without it without sacrificing any functions.

5. The HistoryService exposes all historical data collected by the Flowable engine. To provide the ability to query historical data.

6. ManagementService is usually not used when writing user applications with Flowable. It can read the information of the database table and the original data of the table, and also provide the query and management operation of the job.

7. Dynamic bpmnservice can be used to modify parts of the process definition without redeploying it. For example, you can modify the handler setting of a user task in the process definition, or modify the class name in a service task.

Video Explanation

Documentation help:

  1. Return the error report of task
  2. Integrated swagger documentation
  3. json map parameter passing analysis

Code structure

swagger path: http://localhost:8089/doc.html

Keywords: Java Mybaits Spring Boot Distribution Flowable

Added by dannon on Sun, 06 Feb 2022 22:25:25 +0200