Changing to MySQL
By default, WSO2 IoT Server uses the embedded H2 database as the database for storing user management and registry data. Given below are the steps you need to follow in order to use a MySQL database for this purpose.
Before you begin
- Set up the database as explained in Setting up MySQL.
- Download the MySQL Java connector JAR file, and copy it to the <
IoTS_HOME>/lib
directory.
Setting up configuration files
The default datasource configurations are defined in the files listed below.
master-datasources.xml
This file contains the following default datasource configurations to configure IOTS with the Carbon database and the WSO2 API Manager database.
Edit the datasources in the <
IOTS_HOME>/conf/datasources/
master-datasources.xml
file by replacing theurl
,username
,password
anddriverClassName
settings with your custom values.metrics-datasources.xml
This file contains the datasource required to enable the JVM metrics.
Edit the
WSO2_METRICS_DB
datasource in the <IOTS_HOME>/conf/datasources/
metrics-datasources.xml
file by replacing theurl
,username
,password
anddriverClassName
settings with your custom values and also the other values accordingly.cdm-datasources.XML
This file contains the following default datasource configurations to configure WSO2 IoT Server with the Connected Device Management Framework and for device management.
Edit the
DM_DS
datasource in the <IOTS_HOME>/conf/datasources/
cdm-datasources.xml
file by replacing theurl
,username
,password
anddriverClassName
settings with your custom values and also the other values accordingly.<PLUGIN_NAME>-datasources.xml
This file contains the following default datasource configurations to configure WSO2 IoT Server with the Connected Device Management Framework and for device management.
Example:
Edit theArduino_DB
datasource in thearduino-datasources.xml
file by replacing theurl
,username
,password
anddriverClassName
settings with your custom values and also the other values accordingly.analytics-datasources.xml
This file contains the following default datasources used for summarization and to persist stream data. The database tables are created dynamically when running the spark script along with the required tables.
Example: Arduino publishes the temperature data that gets stored in this database.
Edit the
WSO2_ANALYTICS_EVENT_STORE_DB
andWSO2_ANALYTICS_PROCESSED_DATA_STORE_DB
datasources in the<IOTS_HOME>/wso2/analytics/conf/datasources/analytics-datasources.xml
file by replacing theurl
,username
,password
anddriverClassNamesettings
with your custom values and also the other values accordingly.
The datasource configuration options are as follows:
- url - The URL of the database.
username - The name of the database user.
- password - The password of the database user.
- driverClassName - The class name of the database driver.
- maxActive - The maximum number of active connections that can be allocated from this pool at the same time, or enter a negative value for no limit.
- 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.
- testOnBorrow - 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.
For more information on other parameters that can be defined in the
master-datasources.xml
file, see Tomcat JDBC Connection Pool.
Creating database tables
Create the following database tables either manually or automatically.
Database | DB Script name and Location |
---|---|
WSO2_CARBON_DB | <IOTS_HOME>/dbscripts/mysql.sql |
WSO2AM_DB |
|
WSO2_MB_STORE_DB | <IOTS_HOME>/wso2/broker/dbscripts/mb-store/mysql.sql |
WSO2_METRICS_DB | <IOTS_HOME>/dbscripts/metrics/mysql.sql |
DM_DS | <IOTS_HOME>/dbscripts/cdm/mysql.sql |
Example: |
Example: |
Using the script
You can create database tables manually by executing the following script:
Run the MySQL script individually for the latter mentioned databases that are provided with the product using the below command (outside the MySQL prompt):
mysql -u <USERNAME> -p -D<DATABASE-NAME> '<PATH-TO-MYSQL-DB-SCRIPT>';
For example:
mysql -u username -p -Dregdb '<IOTS_HOME>/dbscripts/mysql.sql';
Enter the password for each command when prompted.
- Start WSO2 IoT Server as follows:
For Linux:
./iot-server.sh
For Windows:
iot-server.bat
Using a startup parameter
You can create database tables automatically when starting the product for the first time by running the following command:
If you are using MySQL 5.7 you need to rename the mysql5.7.sql
file to mysql.sql
in the following directories:
<IOTS_HOME>/dbscripts
<IOTS_HOME>/dbscripts/identity
<IOTS_HOME>/dbscripts/apimgt
For Linux:
./iot-server.sh -Dsetup
For Windows:
iot-server.bat -Dsetup