The following sections describe how to replace the default H2 databases with embedded Derby:
Setting up the database
Follow the steps below to set up an embedded Derby database:
- Download Apache Derby.
Install Apache Derby on your computer.
For instructions on installing Apache Derby, see the Apache Derby documentation.
Setting up the drivers
derbynet.jar from the <
directory to the <
PRODUCT_HOME>/repository/components/extensions/ directory (the classpath of the WSO2 Carbon web application).
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 to 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
Edit the default datasource configuration in the <
aster-datasources.xmlfile as shown below.
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 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 committingis 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.
Configuring new datasources to manage registry or user management data
Follow the steps below to configure new datasources to point to the new databases you create to manage registry and/or user management data separately.
- 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
You can create database tables by executing the database scripts as follows:
- Run the
ijtool located in the
<DERBY_HOME>/bin/directory as illustrated below:
- Create the database and connect to it using the following command inside the
Replace the database file path in the above command with the full path to your database.
- Exit from the the
ijtool by typing the
- Log in to the
ijtool with the username and password that you set in
connect 'jdbc:derby:repository/database/WSO2CARBON_DB' user 'regadmin' password 'regadmin';
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:
Now the product is running using the embedded Apache Derby database.
- Restart the server.
You can create database tables automatically when starting the product for the first time by using the
-Dsetup parameter as follows:
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 the value
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
Changing the product-specific/identity/storage databases
The topics above show how to change the
WSO2_CARBON_DB , which is used to store registry and user manager information. If you changed the product-specific database that come by default or set up a separate database for identity related data, the instructions are the same. In summary:
Add the datasource to the
master-datasources.xmlfile. The datasource for the product-specific database is already there in the
master-datasources.xmlfile by the name
Create the database tables using the following scripts:
For the product-specific database
Use the scripts in
For the identity database
Use the scripts in