Changing to Embedded Derby

The following sections describe how to replace the default H2 database with embedded Derby: 

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 Embedded Derby database to replace the default H2 database, either change the default configurations of the WSO2_CARBON_DB datasource, or configure a new datasource and point it to the new database as explained below.

Changing the default WSO2_CARBON_DB datasource

Follow the steps below to change the type of the default WSO2_CARBON_DB datasource.

1. Edit the default datasourceconfigurationin the <PRODUCT_HOME>/repository/conf/datasources/m aster-datasources.xml file as shown below.

   <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:derby://localhost:1527/db;create=true</url>
                  <username>regadmin</username>
                  <password>regadmin</password>
                  <driverClassName>org.apache.derby.jdbc.EmbeddedDriver</driverClassName>
                  <maxActive>80</maxActive>
                  <maxWait>60000</maxWait>
                  <minIdle>5</minIdle>
                  <testOnBorrow>true</testOnBorrow>
                  <validationQuery>SELECT 1</validationQuery>
                  <validationInterval>30000</validationInterval>
   			   <defaultAutoCommit>false</defaultAutoCommit>
            </configuration>
        </definition>
   </datasource>

   The elements in the above configuration are described below:

   Element	Description
   url	The URL of the database. The default port for a DB2 instance is 50000.
   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 should elapse (when there are no available connections in the pool) before the system throws 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. 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.
   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 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 <PRODUCT_HOME>/repository/conf/datasources/ master-datasources.xml file, see Tomcat JDBC Connection Pool.

Configuring new datasources to manage registry or user management data

Follow the steps below to configure new datasources to point to the new database(s) you create to manage registry and/or user management data separately.

1. Add a new datasource with similar configurations as the  WSO2_CARBON_DB datasource above to the <PRODUCT_HOME>/repository/conf/datasources/ master-datasources.xml file. Change its elements with your custom values. For instructions, see Setting up datasource configurations.

2. If you are setting up a separate database to store registry-related data, update the following configurations in the <PRODUCT_HOME>/repository/conf/ registry.xml file.

   <dbConfig name="wso2registry">
   	<dataSource>jdbc/MY_DATASOURCE_NAME</dataSource>
   </dbConfig>

3. If you are setting up a separate database to store user management data, update the following configurations in the <PRODUCT_HOME>/repository/conf/ user-mgt.xml file.

   <Configuration>
   	<Property name="dataSource">jdbc/MY_DATASOURCE_NAME</Property>
   </Configuration>

Creating database tables

You can create database tables by executing the database scripts as follows: 

1. Run the ij tool located in the <DERBY_HOME>/bin/ directory as illustrated below:
   
2. Create the database and connect to it using the following command inside the ij prompt:

   connect 'jdbc:derby:repository/database/WSO2CARBON_DB;create=true';

   Replace the database file path in the above command with the full path to your database.

3. Exit from the ij tool by typing the exit command.

   exit;

4. Log in to the ij tool with the username and password that you set in registry.xml and user-mgt.xml:
   connect 'jdbc:derby:repository/database/WSO2CARBON_DB' user 'regadmin' password 'regadmin';

5. Use the scripts given in the following locations to create the database tables:

   • To create tables for the registry and user manager database (WSO2CARBON_DB), run the below command:

     run '<PRODUCT_HOME>/dbscripts/derby.sql';

     Now the product is running using the embedded Apache Derby database.

6. Restart the server.