Page Comparison

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

...

...

...

Preparing the Derby Database

...

Setup Configuration Files

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

<currentDBConfig>derby-db</currentDBConfig>       <datasource>
            <name>WSO2_CARBON_DB</name>
            <description>The datasource used for registry and user manager</description>
            <jndiConfig>
                <name>jdbc/WSO2CarbonDB</name>
            </jndiConfig>
            <dbConfig<definition nametype="derby-dbRDBMS">
                <configuration>
                    <url>jdbc:derby://localhost:1527/db;create=true</url>
                    <userName>regadmin</userName>
                    <password>regadmin</password>
                  <driverName>org  <driverClassName>org.apache.derby.jdbc.ClientDriver</driverName>driverClassName>
                    <maxActive>80</maxActive>
                    <maxWait>60000</maxWait>
                    <minIdle>5</minIdle>
    </dbConfig>                <testOnBorrow>true</testOnBorrow>
                    <validationQuery>values 1</validationQuery>
                    <validationInterval>30000</validationInterval>
                </configuration>
            </definition>
        </datasource>

The Database Configuration Options

• url - The URL of the database.
• userName username - The name of the database user.
• password - The password of the database user.
• driverName 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.

2. Edit the user-mgt.xml file located in the $GREG_HOME/repository/conf directory of the deployed instance as below.

Image Removed

<Configuration>
        ...
        <Property name="url">jdbc:derby://localhost:1527/db;create=true</Property>
        <Property name="userName">regadmin</Property>
        <Property name="password">regadmin</Property>
        <Property name="driverName">org.apache.derby.jdbc.ClientDriver</Property>
        <Property name="maxActive">50</Property>
        <Property name="maxWait">60000</Property>
        <Property name="minIdle">5</Property>
    </Configuration>

Setup Drivers

Place  

...

Setup Drivers

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

...

Create Database

...

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

Image RemovedImage Added

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

...

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