Setting up MySQL

The following sections describe how to set up a MySQL database:

Setting up the database and users

Download and install MySQL on your computer.

For instructions on installing MySQL on MAC OS, go to Homebrew.
```
sudo apt-get install mysql-server mysql-client
```
Start the MySQL service. If you are using Linux, use the following command:
```
sudo /etc/init.d/mysql start
```
Log in to the MySQL client 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 <DATABASE_NAME>; 
```
For example:
```
create database regdb;
```
About using MySQL in different operating systems
For users of Microsoft Windows, when creating the database in MySQL, it is important to specify the character set as latin1. Failure to do this may result in an error (error code: 1709) when starting your cluster. This error occurs in certain versions of MySQL (5.6.x) and is related to the UTF-8 encoding. MySQL originally used the latin1 character set by default, which stored characters in a 2-byte sequence. However, in recent versions, MySQL defaults to UTF-8 to be friendlier to international users. Hence, you must use latin1 as the character set as indicated below in the database creation commands to avoid this problem. Note that this may result in issues with non-latin characters (like Hebrew, Japanese, etc.). The database creation command should be as follows:
mysql> create database <DATABASE_NAME> character set latin1;
For users of other operating systems, the standard database creation commands will suffice. For these operating systems, the database creation command should be as follows:.
mysql> create database <DATABASE_NAME>;

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:
```
FLUSH PRIVILEGES;
```
Log out from the MySQL prompt by executing the following command:
```
quit;
```

Setting up configuration files

The default datasource configuration are defined in the 2 files listed below, which are located in the <IoTS_HOME>/repository/conf/datasources directory.

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 WSO2_CARBON_DB and WSO2AM_DB datasources in the master-datasources.xml file by replacing the url, username, password and driverClassName settings with your custom values.

WSO2_Carbon_DB datasource

<datasource>
   <name>WSO2_CARBON_DB</name>
   <description>The datasource used for registry and user manager</description>
   <jndiConfig>
      <name>jdbc/WSO2CarbonDB</name>
   </jndiConfig>
   <definition type="RDBMS">
      <configuration>
         <url>jdbc:mysql://localhost:3306/WSO2CARBON_DB</url>
         <username>wso2carbon</username>
         <password>wso2carbon</password>
         <driverClassName>com.mysql.jdbc.Driver</driverClassName>
         <maxActive>50</maxActive>
         <maxWait>60000</maxWait>
         <minIdle>5</minIdle>
         <testOnBorrow>true</testOnBorrow>
         <validationQuery>SELECT 1</validationQuery>
         <validationInterval>30000</validationInterval>
      </configuration>
   </definition>
</datasource>

WSO2AM_DB datasource

<datasource>
   <name>WSO2AM_DB</name>
   <description>The datasource used for API Manager database</description>
   <jndiConfig>
      <name>jdbc/WSO2AM_DB</name>
   </jndiConfig>
   <definition type="RDBMS">
      <configuration>
         <url>jdbc:mysql://localhost:3306/WSO2AM_DB</url>
         <username>wso2carbon</username>
         <password>wso2carbon</password>
         <driverClassName>com.mysql.jdbc.Driver</driverClassName>
         <maxActive>50</maxActive>
         <maxWait>60000</maxWait>
         <testOnBorrow>true</testOnBorrow>
         <validationQuery>SELECT 1</validationQuery>
         <validationInterval>30000</validationInterval>
      </configuration>
   </definition>
</datasource>

WSO2_MB_Store_DB datasource

<datasource>
   <name>WSO2_MB_STORE_DB</name>
   <description>The datasource used for message broker database</description>
   <jndiConfig>
      <name>jdbc/WSO2MBStoreDB</name>
   </jndiConfig>
   <definition type="RDBMS">
      <configuration>
         <url>jdbc:mysql://localhost:3306/WSO2MB_DB</url>
         <username>wso2carbon</username>
         <password>wso2carbon</password>
         <driverClassName>com.mysql.jdbc.Driver</driverClassName>
         <maxActive>50</maxActive>
         <maxWait>60000</maxWait>
         <testOnBorrow>true</testOnBorrow>
         <validationQuery>SELECT 1</validationQuery>
         <validationInterval>30000</validationInterval>
         <defaultAutoCommit>false</defaultAutoCommit>
      </configuration>
   </definition>
</datasource>

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 and WSO2_ANALYTICS_PROCESSED_DATA_STORE_DB datasources in the <IoT_HOME>/analytics/repository/conf/datasources/analytics-datasources.xml file by replacing the url, username, password and driverClassNamesettings with your custom values and also the other values accordingly.

WSO2_Analytics_Event_Store_DB datasource

<datasource>
   <name>WSO2_ANALYTICS_EVENT_STORE_DB</name>
   <description>The datasource used for analytics record store</description>
   <definition type="RDBMS">
      <configuration>
         <url>jdbc:mysql://localhost:3306/ANALYTICS_EVENT_STORE</url>
         <username>wso2carbon</username>
         <password>wso2carbon</password>
         <driverClassName>com.mysql.jdbc.Driver</driverClassName>
         <maxActive>50</maxActive>
         <maxWait>60000</maxWait>
         <validationQuery>SELECT 1</validationQuery>
         <defaultAutoCommit>false</defaultAutoCommit>
         <initialSize>0</initialSize>
         <testWhileIdle>true</testWhileIdle>
         <minEvictableIdleTimeMillis>4000</minEvictableIdleTimeMillis>
      </configuration>
   </definition>
</datasource>

WSO2_Analytics_Processed_Data_Store_DB datasource

<datasource>
   <name>WSO2_ANALYTICS_PROCESSED_DATA_STORE_DB</name>
   <description>The datasource used for analytics record store</description>
   <definition type="RDBMS">
      <configuration>
         <url>jdbc:mysql://localhost:3306/ANALYTICS_PROCESSED_DATA_STORE</url>
         <username>wso2carbon</username>
         <password>wso2carbon</password>
         <driverClassName>com.mysql.jdbc.Driver</driverClassName>
         <maxActive>50</maxActive>
         <maxWait>60000</maxWait>
         <validationQuery>SELECT 1</validationQuery>
         <defaultAutoCommit>false</defaultAutoCommit>
         <initialSize>0</initialSize>
         <testWhileIdle>true</testWhileIdle>
         <minEvictableIdleTimeMillis>4000</minEvictableIdleTimeMillis>
      </configuration>
   </definition>
</datasource>

metrics-datasources.xml

This file contains the datasource required to enable the JVM metrics.

Edit the WSO2_METRICS_DB datasource in the metrics-datasources.xml file by replacing the url, username, password and driverClassName settings with your custom values and also the other values accordingly.

WSO2_Metrics_DB datasource

<datasource>
   <name>WSO2_METRICS_DB</name>
   <description>The default datasource used for WSO2 Carbon Metrics</description>
   <jndiConfig>
      <name>jdbc/WSO2MetricsDB</name>
   </jndiConfig>
   <definition type="RDBMS">
      <configuration>
         <url>jdbc:mysql://localhost:3306/WSO2METRICS_DB</url>
         <username>wso2carbon</username>
         <password>wso2carbon</password>
         <driverClassName>com.mysql.jdbc.Driver</driverClassName>
         <maxActive>50</maxActive>
         <maxWait>60000</maxWait>
         <testOnBorrow>true</testOnBorrow>
         <validationQuery>SELECT 1</validationQuery>
         <validationInterval>30000</validationInterval>
         <defaultAutoCommit>true</defaultAutoCommit>
      </configuration>
   </definition>
</datasource>

cdm-datasources.XML

This file contains the following default datasource configurations to configure WSO2 IoTS with the Connected Device Management Framework and for device management.

Edit the DM_DS datasource in the cdm-datasources.xml file by replacing the url, username, password and driverClassName settings with your custom values and also the other values accordingly.

DM_DS datasource

<datasource>
   <name>DM_DS</name>
   <description>The datasource used for CDM</description>
   <jndiConfig>
      <name>jdbc/DM_DS</name>
   </jndiConfig>
   <definition type="RDBMS">
      <configuration>
         <url>jdbc:mysql://localhost:3306/WSO2DM_DB</url>
         <username>wso2carbon</username>
         <password>wso2carbon</password>
         <driverClassName>com.mysql.jdbc.Driver</driverClassName>
         <maxActive>50</maxActive>
         <maxWait>60000</maxWait>
         <testOnBorrow>true</testOnBorrow>
         <validationQuery>SELECT 1</validationQuery>
         <validationInterval>30000</validationInterval>
      </configuration>
   </definition>
</datasource>

<PLUGIN_NAME>-datasources.xml

This file contains the following default datasource configurations to configure WSO2 IoTS with the Connected Device Management Framework and for device management.

Example:
Edit the Arduino_DB datasource in the arduino-datasources.xml file by replacing the url, username, password and driverClassName settings with your custom values and also the other values accordingly.

Example: Arduino_DB datasource

<datasource>
   <name>Arduino_DB</name>
   <description>The datasource used for the Arduino database</description>
   <jndiConfig>
      <name>jdbc/ArduinoDM_DB</name>
   </jndiConfig>
   <definition type="RDBMS">
      <configuration>
         <url>jdbc:mysql://localhost:3306/ArduinoDM_DB</url>
         <username>wso2carbon</username>
         <password>wso2carbon</password>
         <driverClassName>com.mysql.jdbc.Driver</driverClassName>
         <maxActive>50</maxActive>
         <maxWait>60000</maxWait>
         <testOnBorrow>true</testOnBorrow>
         <validationQuery>SELECT 1</validationQuery>
         <validationInterval>30000</validationInterval>
      </configuration>
   </definition>
</datasource>

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.

Setting up the drivers

Download the MySQL Java connector JAR file, and copy it to the <IoTS_HOME>/repository/components/lib directory.

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`	`<IoTS_HOME>/dbscripts/apimgt/mysql.sql`
`WSO2_MB_STORE_DB`	`<IoTS_HOME>/dbscripts/mb-store/mysql.sql`
`WSO2_METRICS_DB`	`<IoTS_HOME>/dbscripts/metrics/mysql.sql`
`DM_DS`	`<IoTS_HOME>/dbscripts/cdm/mysql.sql`
`<DEVICE_PLUGIN>_DB` Example: `Arduino_DB`	`<IoTS_HOME>/dbscripts/cdm/plugins/<DEVICE_PLUGIN>/mysq`l.sql Example: `<IoTS_HOME>/dbscripts/cdm/plugins/arduino/mysql.sql`

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 the WSO2 product instance as follows:
- For Linux:
```
wso2server.sh
```
- For Windows:
```
wso2server.bat
```

Using a startup parameter

You can create database tables automatically when starting the product for the first time by running the following command:

For Linux:
```
wso2server.sh -Dsetup
```

For Windows:
```
wso2server.bat -Dsetup
```