If the directory/file paths specified in this guide do not exist in your WSO2 product, see Directory Structure of WSO2 Products to locate the paths applicable to your product.
||
Skip to end of metadata
Go to start of metadata

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

Before you begin

You need to set up the embedded Derby before following the steps to configure your product with Embedded Derby. For more information, see Setting up 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.

Edit the default datasource configuration in the <PRODUCT_HOME>/repository/conf/datasources/master-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:

ElementDescription
urlThe URL of the database. The default port for a DB2 instance is 50000.
username and passwordThe name and password of the database user.
driverClassNameThe class name of the database driver.
maxActiveThe 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.
maxWaitThe 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.
minIdleThe 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.
validationQueryThe SQL query that will be used to validate connections from this pool before returning them to the caller.
validationIntervalThe 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.

The following elements are available only as a WUM update and is effective from 14th September 2018 (2018-09-14).  For more information, see Updating WSO2 Products.
This WUM update is only applicable to Carbon 4.4.11 and will be shipped out-out-the-box with Carbon versions newer than Carbon 4.4.35. For more information on Carbon compatibility, see Release Matrix.

ElementDescription
commitOnReturnIf defaultAutoCommit=false, then you can set commitOnReturn=true, so that the pool can complete the transaction by calling the commit on the connection as it is returned to the pool. However, If rollbackOnReturn=true then this attribute is ignored. The default value is false.
rollbackOnReturnIf defaultAutoCommit=false, then you can set rollbackOnReturn=true so that the pool can terminate the transaction by calling rollback on the connection as it is returned to the pool. The default value is false.

Configuring the connection pool behavior on return
When a database connection is returned to the pool, by default  the product rolls back the pending transactions if defaultAutoCommit=true . However, if required you can disable the latter mentioned default behavior by disabling the ConnectionRollbackOnReturnInterceptor, which is a JDBC-Pool JDBC interceptor, and setting the connection pool behavior on return via the datasource configurations by using the following options.

Disabling the ConnectionRollbackOnReturnInterceptor is only possible with the WUM update and is effective from 14th September 2018 (2018-09-14). For more information on updating WSO2 API Manager, see Updating WSO2 Products. This WUM update is only applicable to Carbon 4.4.11.

  • Configure the connection pool to commit pending transactions on connection return
    1. Navigate to either one of the following locations based on your OS.
      • On Linux/Mac OS:  <PRODUCT_HOME>/bin/wso2server.sh/
      • On Windows:  <PRODUCT_HOME>\bin\wso2server.bat 
    2. Add the following JVM option:

      -Dndatasource.disable.rollbackOnReturn=true \
    3. Navigate to the <PRODUCT_HOME>/repository/conf/datasources/master-datasources.xml file.
    4. Disable the defaultAutoCommit by defining it as false.
    5. Add the commitOnReturn property and set it to true for all the datasources, including the custom datasources.

      <datasource>
           ...
           <definition type="RDBMS">
               <configuration>
                     ...
      			   <defaultAutoCommit>false</defaultAutoCommit>
      			   <commitOnReturn>true</commitOnReturn>	
      			   ...
               </configuration>
           </definition>
      </datasource>
  • Configure the connection pool to rollback pending transactions on connection return

    1. Navigate to the <PRODUCT_HOME>/repository/conf/datasources/master-datasources.xml file.
    2. Disable the defaultAutoCommit by defining it as false.

    3. Add the rollbackOnReturn property to the datasources.

      <datasource>
           ...
           <definition type="RDBMS">
               <configuration>
                     ...
      			   <defaultAutoCommit>false</defaultAutoCommit>	
      			   <rollbackOnReturn>true</rollbackOnReturn>
      			   ...
               </configuration>
           </definition>
      </datasource>

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.

You can create database tables automatically when starting the product for the first time by using the -Dsetup parameter as follows.

  • For Windows: <PRODUCT_HOME>/bin/wso2server.bat -Dsetup

  • For Linux: <PRODUCT_HOME>/bin/wso2server.sh -Dsetup


Deprecation of -DSetup

When proper Database Administrative (DBA) practices are followed, the systems (except analytics products) are not granted DDL (Data Definition) rights on the schema. Therefore, maintaining the -DSetup option is redundant and typically unusable. As a result, from January 2018 onwards WSO2 has deprecated the  -DSetup option. Note that the proper practice is for the DBA to run the DDL statements manually so that the DBA can examine and optimize any DDL statement (if necessary) based on the DBA best practices that are in place within the organization.

The product is configured to run using an embedded Apache Derby database.

In contrast to setting up with remote Derby, when setting up with the embedded mode, set the database driver name (the driverClassName element) to org.apache.derby.jdbc.EmbeddedDriver and the database URL (the url element) to the database directory location relative to the installation. In the above sample configuration, it is inside the <DERBY_HOME>/WSO2_CARBON_DB/ directory.

  • No labels