anchor.diff:  
   Flowable provides several web applications to demonstrate and leverage the functionality provided by the Flowable project:
   
  -* Flowable IDM: the identity management application that provides single-sign-on authentication functionality for all the Flowable UI applicatons and for users with the idm admin privilege it also provides functionality to manage users, groups and privileges.
  -* Flowable Modeler: the modeler application that allows for modeling processes, forms, decision tables and application definitions.
  -* Flowable Task: the runtime task application that provides functionality to start process instances, edit task forms, complete tasks and query on tasks and process instances.
  -* Flowable Admin: an admin application that allows for querying the BPMN, DMN, form and content engines and provides several options to change process instances, tasks and jobs etc. The admin application connects to the engines through the REST API that is deployed together with the Flowable Task app and the Flowable REST app.
  -
  -The Flowable IDM is required to be present for all other apps to be able to authenticate. The WAR files for each app can be deployed to the same servlet container (like Apache Tomcat), but can also be deployed on different servlet containers. Because the same cookie is used for authentication for each app, the apps need to run on the same domain.
  +* Flowable IDM: an IDentity Management application that provides single sign-on authentication functionality for all the Flowable UI applicatons, and, for users with the IDM administrative privilege, it also provides functionality to manage users, groups and privileges.
  +* Flowable Modeler: an application that allows users with modeler privileges to model processes, forms, decision tables and application definitions.
  +* Flowable Task: a runtime task application that provides functionality to start process instances, edit task forms, complete tasks and query on tasks and process instances.
  +* Flowable Admin: an administrative application that allows users with admin privilege to query the BPMN, DMN, form and content engines and provides several options to change process instances, tasks, jobs and so on. The admin application connects to the engines through the REST API that is deployed together with the Flowable Task app and the Flowable REST app.
  +
  +The Flowable IDM is required for all other apps to enable authenticatation. The WAR files for each app can be deployed to the same servlet container (such as Apache Tomcat), but can also be deployed on different servlet containers. Because the same cookie is used for authentication with each app, the apps need to run on the same domain.
   
   
   [[uiAppInstallation]]
   
   === Installation
   
  -Like mentioned before, all four UI apps can be deployed together on the same Tomcat server and to get started this is probably the easiest approach. You can also choose to only install the Modeler app for example, but make sure the Flowable IDM app is always running/deployed as well. For this installation guide we'll describe the installation of all four apps to a Tomcat server.
  +As mentioned before, all four UI apps can be deployed together on the same Tomcat server, and to get started this is probably the easiest approach. You can choose to only install the Modeler app, for example, but make sure the Flowable IDM app is always running/deployed as well. For this installation guide we'll describe the installation of all four apps to a Tomcat server.
   
   1. Download a recent stable version of link:$$http://tomcat.apache.org$$[Apache Tomcat].
   2. Download the latest stable link:$$http://www.flowable.org/downloads.html$$[Flowable 6 version].
  
positive.code: |datasource.max-pool-size|The maximum datasource pool size
  |datasource.acquire-increment|Determines how many connections at a time c3p0 will try to acquire when the pool is exhausted
  |datasource.preferred-test-query|Defines the query that will be executed for all connection tests
  |datasource.test-connection-on-checkin|Test the connection when checking in in the pool
  |datasource.test-connection-on-checkout|Test the connection on checkout from the pool
  |datasource.max-idle-time|Seconds a Connection can remain pooled but unused before being discarded. Zero means idle connections never expire
  |datasource.max-idle-time-excess-connections|Number of seconds that Connections in excess of minPoolSize should be permitted to remain idle in the pool before being culled
  
negative.code: 4. Startup the Tomcat server by running the bin/startup.sh (Mac OS and Linux) or bin/startup.bat (Windows) script.
  5. Open a web browser and go to link:$$http://localhost:8080/flowable-modeler$$[http://localhost:8080/flowable-modeler].
  
  All Flowable UI apps should now be running with an H2 in-memory database and the following login screen should be shown in your web browser:
  
  image::images/flowable_idm_login_screen.png[align="center"]
  
  By default, the Flowable IDM application will create an admin user that has privileges to all the Flowable UI apps. You can login with admin/test and the browser should redirect to the Flowable Modeler application:
  
  image::images/flowable_modeler_startup_screen.png[align="center"]
  
  Usually, you will want to change the default H2 in-memory database configuration to a MySQL or Postgres (or other persistent database) configuration. You can do this per app by changing the flowable-ui-app.properties file in the WEB-INF/classes/META-INF directory of each app. But it's easier to copy the flowable-ui-app.properties file from one of the apps or get it from link:$$https://github.com/flowable/flowable-engine/blob/master/modules/flowable-ui-task/flowable-ui-task-app/src/main/resources/META-INF/flowable-ui-app/flowable-ui-app.properties$$[Github], and put it in the Tomcat lib folder. The UI applications will first look at a flowable-ui-app.properties file available on the classpath directly and this configuration will have precedence over the configuration file in the WAR. To change the default configuration to MySQL the following changes are needed to the properties file:
  
  [source,linenums]
  ----
  