JNDI Datasource Configuration not working

Flowable Application
1

Hi All,

This is my first post and I am just starting out with Flowable. I have successfully deployed all the war files included in the flowable-6.5.0.zip archive to my Tomcat 9 server and changed the database properties in each application’s .properties file to point to my Postgres server. All worked well and I could see the tables were created using pgAdmin.

I then discovered that I could use the JNDI Datasource Configuration as described in the documentation. So I created two files called “flowable-idm.xml” and “flowable-task.xml” in the “…tomcat\conf\Catalina\localhost” folder with the following content:

<?xml version="1.0" encoding="UTF-8"?>
<Context antiJARLocking="true" path="/flowable-task">
	<Resource auth="Container"
        		name="jdbc/flowableDB"
        		type="postgres"
        		description="JDBC DataSource"
        		url="jdbc:postgresql://localhost:5432/flowable"
        		driverClassName="org.postgresql.Driver"
        		username="flowable"
        		password="flowable"
        		defaultAutoCommit="false"
        		initialSize="5"
        		maxWait="5000"
        		maxActive="120"
        		maxIdle="5"/>
</Context>

The only difference between the two files being ‘path="/flowable-idm"’ for the flowable-idm.xml file.

I know Tomcat reads these files because I got startup errors initially when I had errors in the files stemming from what I suspect is an error in the documentation where it shows type=“javax.sql.DataSource” for connecting to a MySql database. I suspect that this should be “mysql”. Anyway, I “fixed” it (I think) as shown above and the errors went away.

Note, I removed all other war files and left only “flowable-idm.war” and “flowable-task.war” in the webapps folder. I also created the flowable database and user and granted the necessary permissions.

The applications deploy and I can log into the UI (flowable-task) using the admin test user. However, it appears the H2 database is being used and not the flowable database in Postgres since no tables are created in the database.

What am I missing? I’d appreciate any help.

2

Never mind. I got it working by putting an application.properties file in the lib folder as described here and elsewhere.