Setting up with Remote Derby

Follow the below instructions to set up the remote Derby database.

Preparing the Derby Database

1. Use the wget command to download and save Apache Derby to your computer.

2. Install Apache Derby on your computer.

Tip

You can find installation instructions here.

3. Go to the <derby-installation directory>/bin directory and run the Derby network server start script. Usually, it is named startNetworkServer.

Setup Configuration Files

1. Edit the default database configuration defined in the master-datasources.xml file located at $GREG_HOME/repository/conf/datasources directory of the deployed registry instance as below. Both the database configurations in registry.xml and user-mgt.xml refer this data source.

Note

Replace the following settings with your own custom values:

       <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.ClientDriver</driverClassName>
                    <maxActive>80</maxActive>
                    <maxWait>60000</maxWait>
                    <minIdle>5</minIdle>
                    <testOnBorrow>true</testOnBorrow>
                    <validationQuery>values 1</validationQuery>
                    <validationInterval>30000</validationInterval>
                </configuration>
            </definition>
        </datasource>

The Database Configuration Options

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 negative 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, or <= 0 to wait indefinitely.
minIdle - The minimum number of active connections that can remain idle in the pool without extra ones being created or 0 to create none.

Note

In contrast to the embedded registry, in the remote registry, you will set the database driver name (the driverName element) to the value org.apache.derby.jdbc.ClientDriver and the database URL (the url element) to the database remote location.

Setup Drivers

Copy derby.jar, derbyclient.jar and derbynet.jar from $DERBY_HOME/lib in to $GREG_HOME/repository/components/extensions directory (to the class path of the WSO2 Governance Registry web application).

Create Database

Automatic Database Creation

1. The first time you start the registry, run it with the -Dsetup option so that it will create the Derby database.

For Windows:

wso2server.bat -Dsetup

For Linux:

wso2server.sh -Dsetup

2. The WSO2 Governance Registry is configured to run using a remote Apache Derby database.

Manual Database Creation

1. Run the ij tool located in the <derby-installation directory>/bin directory.

2. Create the registry database and connect to it using the following command inside the ij prompt:

Note

Replace the database file path, user name, and password in the below command to suit your requirements.

connect 'jdbc:derby://localhost:1527/db;user=regadmin;password=regadmin;create=true';

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

exit;

4. Log in to the ij tool with the username and password you just used to create the database.

connect 'jdbc:derby://localhost:1527/db' user 'regadmin' password 'regadmin';

5. Run the Derby scripts for both the registry and user manager (embedded inside the Registry) databases, provided with the WSO2 Governance Registry, using the following command:

run 'GREG_HOME/dbscripts/derby.sql';

6. Restart the WSO2 Registry instance. Now WSO2 Governance Registry is running using a remote Apache Derby database.