Set the following properties to update the database properties.
Set the following properties to configure a JDBC connection:
|datasource.driver||The JDBC driver used to connect to the database. Note that the driver must be on the classpath of the web application.|
|datasource.url||The JDBC URL used to connect to the database.|
|datasource.username||The user of the database system that is used to connect to the database.|
|datasource.password||The password of the above user.|
datasource.driver=com.mysql.jdbc.Driver datasource.url=jdbc:mysql://127.0.0.1:3306/activiti?characterEncoding=UTF-8 datasource.username=alfresco datasource.password=alfresco
When using JDBC Connection Parameters, you can configure the following connection pool settings to suit the anticipated load:
|datasource.min-pool-size||The minimum number of connections in the connection pool. For example
|datasource.max-pool-size||The maximum number of connections in the connection pool. For example
|datasource.acquire-increment||The number of additional connections the system will try to acquire each time the connection pool is exhausted. For example
|datasource.preferred-test-query||The query used to verify that the connection is still valid. The value depends on the database:
|datasource.test-connection-on-checkin||Boolean value. If
|datasource.test-connection-on-checkout||Boolean value. If
|datasource.max-idle-time||The number of seconds a connection can be pooled before being discarded. For example
|datasource.max-idle-time-excess-connections||Number of seconds that connections in excess of
The connection pooling framework used is C3P0. It has extensive documentation on the settings described above.
JNDI data source
If a JNDI data source is configured in the web container or application server, the JNDI name should be set with the following properties:
|datasource.jndi.name||The JNDI name of the datasource. This varies depending on the application server or web container. For example
|datasource.jndi.resourceRef||Set whether the look up occurs in a J2EE container, that is, if the prefix
Example (on JBoss EAP 6.3):
The Process Services specific logic is written using JPA 2.0 with Hibernate as implementation. Note that the Process Engine itself uses MyBatis for full control of each SQL query.
Set the following properties.
|hibernate.dialect||Required. The dialect implementation that Hibernate uses. This is database specific.|
The following values are used to test Process Services.
hibernate.show_sql property can be set to
true if the SQL being executed needs to be printed to the log.