Configuring FileCatalyst Workflow with MariaDB
Posted by John Tkaczewski, Last modified by Aly Essa on 30 April 2021 10:01 AM


MariaDB is a community-developed, commercially supported fork of the MySQL relational database management system (RDBMS), intended to remain free and open-source software under the GNU General Public License. Development is led by some of the original developers of MySQL, who forked it due to concerns over its acquisition by Oracle Corporation in 2009.

MariaDB maintains high compatibility with MySQL, ensuring a drop-in replacement capability with library binary parity and exact matching with MySQL APIs and commands. 


FileCatalyst Workflow v5.1 and newer builds


FileCatalyst Workflow can be configured to use MariaDB instead of MySQL, this functionality as of Workflow version 5.1. Here are the steps to configure Workflow to use MariaDB instead of MySQL.

1) Download the latest stable release of MariaDB

2) Install MariaDB. You must select a different port for MariaDB as by default it installs on port 3306 which is used by MySQL. If you are planning to run both DB's on the same server, the port must be different. For the example used in the KB, we will use port 3366.

3) Download MariaDB Connector/J 
a) select the latest stable version
b) select jar (not source)
c) select mariadb-java-client-version-number.jar to download

4) Place the jar file for the connector in the Workflow lib directory. Ex: C:\apache-tomcat-9.0.24\webapps\workflow\WEB-INF\lib

5) Restart Tomcat. 

6) When Workflow is back online sign in as the Super Admin. Navigate to the Modify Configuration section and click on Database Settings. Use the following configurations: 

Select My SQL from the Database type
Path: jdbc:mariadb://localhost:3366/ 
Diver name: org.mariadb.jdbc.Driver
Database name: fcworkflow
Username, Password as per your MariaDB installation
Click on Convert Existing Data. After few minutes you will see a success message. 

Your FileCatalyst Workflow instance will now be configured to use MariaDB instead of MySQL.

Comments (0)