The following sections describe how to replace the default H2 databases with MariaDB, which is a drop-in replacement for MySQL:
Setting up the database and users
Follow the steps below to set up MariaDB. See Tested DBMSs for information on the MariaDB versions that we have tested the WSO2 products with.
Download, install and start MariaDB on your computer. See https://downloads.mariadb.org/.
You can install MariaDB standalone or as a galera cluster for high availability. Database clustering is independent of WSO2 product clustering. For more information on setting up a galera cluster, see the MariaDB Galera Cluster documentation.
For instructions on installing MariaDB on MAC OS, go to Homebrew.
- Log in to MariaDB as the root user (or any other user with database creation privileges).
mysql -u root -p
Enter the password when prompted.
In most systems, there is no default root password. Press the Enter key without typing anything if you have not changed the default root password.
- In the MySQL command prompt, create the database using the following command:
create database regdb;
- Give authorization of the database to the regadmin user as follows:
GRANT ALL ON regdb.* TO regadmin@localhost IDENTIFIED BY "regadmin";
- Once you have finalized the permissions, reload all the privileges by executing the following command:
- Log out from the MySQL prompt by executing the following command:
Setting up the drivers
Download the MySQL Java connector JAR file, and copy it to the <
Note that you must use the MySQL connector that is compatible with your MariaDB version. For example,
mysql-connector-java-5.1.36-bin.jar is compatible with MariaDB version 10.0.20. See Tested DBMSs for information on which version of a WSO2 product has been tested for compatibility with which version of MariaDB and MySQL connector.
Setting up datasource configurations
A datasource is used to establish the connection to a database. By default,
WSO2_CARBON_DB datasource is used to connect to the default H2 database, which stores registry and user management data. After setting up the MariaDB database to replace the default H2 database, either change the default configurations of the
WSO2_CARBON_DB datasource, or configure a new datasource to point it to the new database as explained below.
Edit the default datasource configuration in the <
aster-datasources.xmlfile as shown below.
Do not change the datasource name
WSO2_CARBON_DBin the below configuration.
The elements in the above configuration are described below:
Element Description url The URL of the database. The default port for MariaDB is 3306 username and password The name and password of the database user driverClassName The class name of the database driver maxActive The maximum number of active connections that can be allocated at the same time from this pool. Enter any negative value to denote an unlimited number of active connections. maxWait The maximum number of milliseconds that the pool will wait (when there are no available connections) for a connection to be returned before throwing an exception. You can enter zero or a negative value to wait indefinitely. minIdle The minimum number of active connections that can remain idle in the pool without extra ones being created, or enter zero to create none.
The indication of whether objects will be validated before being borrowed from the pool. If the object fails to validate, it will be dropped from the pool, and another attempt will be made to borrow another. validationQuery The SQL query that will be used to validate connections from this pool before returning them to the caller. validationInterval The indication to avoid excess validation, and only run validation at the most, at this frequency (time in milliseconds). If a connection is due for validation, but has been validated previously within this interval, it will not be validated again. defaultAutoCommit
This property is not applicable to the Carbon database in WSO2 products because auto committing is usually handled at the code level, i.e., the default auto commit configuration specified for the RDBMS driver will be effective instead of this property element. Typically, auto committing is enabled for an RDBMS drivers by default.
When auto committing is enabled, each SQL statement will be committed to the database as an individual transaction, as opposed to committing multiple statements as a single transaction.
For more information on other parameters that can be defined in the
master-datasources.xmlfile, see Tomcat JDBC Connection Pool.
- Add a new datasource with similar configurations as the
WSO2_CARBON_DBdatasource above to the <
master-datasources.xmlfile . Change its elements with your custom values. For instructions, see Setting up datasource configurations.
If you are setting up a separate database to store registry-related data, update the following configurations in the <
If you are setting up a separate database to store user management data, update the following configurations in the <
Creating database tables
To create the database tables, connect to the database that you created earlier and run the following scripts.
To create tables in the registry and user manager database (
WSO2CARBON_DB), use the below script:
You may have to enter the password for each command when prompted.
Restart the server.
You can create database tables automatically when starting the product for the first time by using the
-Dsetupparameter as follows:
Changing the identity/BPS/social databases
The topics above show how to change the
WSO2_CARBON_DB, which is used to store registry and user manager information. If you set up a separate database for identity, WSO2 Business Process Server (BPS), or social related data, the instructions are the same. In summary:
Add a new datasource configuration to the following files for each of the separate databases that you need to create.
For the identity database Add it to the <
For the BPS database Add it to the <
For the social database
Add it to the <
Create the database tables using the following scripts:
For the identity database Use
For the BPS database Use
For the social database
Update the following configurations, with the defined datasource name of the corresponding database configuration you added to the
If you are setting up a separate database to store identity related data, update the following configurations in the <