anchor.diff:  
   === Database table names explained
   
  -The database names of Flowable all start with *ACT_*. The second part is a two-character identification of the use case of the table. This use case will also roughly match the service API.
  -
  -* *ACT_RE_**: 'RE' stands for +repository+. Tables with this prefix contain 'static' information such as process definitions and process resources (images, rules, etc.).
  -* *ACT_RU_**: 'RU' stands for +runtime+. These are the runtime tables that contain the runtime data of process instances, user tasks, variables, jobs, etc. Flowable only stores the runtime data during process instance execution, and removes the records when a process instance ends. This keeps the runtime tables small and fast.
  -* *ACT_ID_**: 'ID' stands for +identity+. These tables contain identity information, such as users, groups, etc.
  -* *ACT_HI_**: 'HI' stands for +history+. These are the tables that contain historic data, such as past process instances, variables, tasks, etc.
  -* *ACT_GE_**: +general+ data, which is used in various use cases.
  +The database names of Flowable all start with *ACT_DMN_*.
  +
  +// * *ACT_RE_**: 'RE' stands for +repository+. Tables with this prefix contain 'static' information such as process definitions and process resources (images, rules, etc.).
  +// * *ACT_RU_**: 'RU' stands for +runtime+. These are the runtime tables that contain the runtime data of process instances, user tasks, variables, jobs, etc. Flowable only stores the runtime data during process instance execution, and removes the records when a process instance ends. This keeps the runtime tables small and fast.
  +// * *ACT_ID_**: 'ID' stands for +identity+. These tables contain identity information, such as users, groups, etc.
  +// * *ACT_HI_**: 'HI' stands for +history+. These are the tables that contain historic data, such as past process instances, variables, tasks, etc.
  +// * *ACT_GE_**: +general+ data, which is used in various use cases.
   
   
   [[databaseUpgrade]]
  
positive.code: 
  === Creating the database tables
  
  The easiest way to create the database tables for your database is to:
  
  * Add the flowable-engine jars to your classpath
  * Add a suitable database driver
  * Add a Flowable configuration file (__flowable.cfg.xml__) to your classpath, pointing to your database (see <<databaseConfiguration,database configuration section>>)
  * Execute the main method of the _DbSchemaCreate_ class
  
  However, often only database administrators can execute DDL statements on a database. On a production system, this is also the wisest of choices. The SQL DDL statements can be found on the Flowable downloads page or inside the Flowable distribution folder, in the +database+ subdirectory. The scripts are also in the engine jar (__flowable-engine-x.jar__), in the package __org/flowable/db/create__ (the __drop__ folder contains the drop statements). The SQL files are of the form
  
  ----
  flowable.{db}.{create|drop}.{type}.sql
  ----
  
  Where __db__ is any of the <<supporteddatabases,supported databases>> and __type__ is
  
  * *engine:* the tables needed for engine execution. Required.
  * *identity:* the tables containing users, groups and memberships of users to groups. These tables are optional and should be used when using the default identity management as shipped with the engine.
  * *history:* the tables that contain the history and audit information. Optional: not needed when history level is set to _none_. Note that this will also disable some features (such as commenting on tasks) which store the data in the history database.
  
  *Note for MySQL users:* MySQL version lower than 5.6.4 has no support for timestamps or dates with millisecond precision. To make things even worse, some version will throw an exception when trying to create such a column but other versions don't. When doing auto-creation/upgrade, the engine will change the DDL when executing it. When using the DDL file approach, both a regular version and a special file with _mysql55_ in it are available (this applies on anything lower than 5.6.4). This latter file will have column types with no millisecond precision in it.
  
  Concretely, the following applies for MySQL version
  
  * *<5.6:* No millisecond precision available. DDL files available (look for files containing __mysql55__). Auto creation/update will work out of the box.
  * *5.6.0 - 5.6.3:* No millisecond precision available. Auto creation/update will NOT work. It is advised to upgrade to a newer database version anyway. DDL files for _mysql 5.5_ could be used if really needed.
  * *5.6.4+:* Millisecond precision available. DDL files available (default file containing __mysql__). Auto creation/update works out of the box.
  
  
  Do note that in the case of upgrading the MySQL database later on and the Flowable tables are already created/upgraded, the column type change will have to be done manually!
  
  
  [[database.tables.explained]]
  
negative.code: ----
  
  
  Note that Flowable DMN does not ship with a library that allows to define such a data source. So you have to make sure that the libraries are on your classpath.
  
  The following properties can be set, regardless of whether you are using the JDBC or data source approach:
  
  