Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • To create tables for the registry and user manager database, use the following script: 
    <PRODUCT_HOME>/dbscripts/h2.sql
  • To create tables for the product specific databases,  use the following script:
    <PRODUCT_HOME>/<PRODUCT_NAME>/dbscripts/h2.sql
  • Excerpt
    hiddentrue

    NOTE TO WRITERS: Add the following content only i f it is applicable to your product.

    To create tables for the  identity databases , use the following script:

    NOTE TO WRITERS: Add the following content only i f it is applicable to your product.

    Code Block
    languagepowershell
    <PRODUCT_HOME>/dbscripts/<PRODUCT_NAME>/h2.sql
    Excerpt
    hiddentrue
  • To create tables for the  storage databases , use the following script:

    Code Block
    languagepowershell
    <PRODUCT_HOME>/dbscripts/storage/h2.sql

Follow the steps below to run the script in web console:

...

  1. Edit the default datasource configuration defined in the  master-datasources.xml file, located in the <PRODUCT_HOME>/repository/conf/datasources/ directory instance, as follows. The database configurations in registry.xml and user-mgt.xml refer to this datasource.

    Info

    Replace the urlusernamepassword and driverClassName settings with your custom values and also the other values accordingly in the master-datasources.xml file as shown below.

    Code Block
    languagehtml/xml
    <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:h2:tcp://localhost/~/registryDB;create=true</url>
                   <username>regadmin</username>
                   <password>regadmin</password>
                   <driverClassName>org.h2.Driver</driverClassName>
                   <maxActive>80</maxActive>
                   <maxWait>60000</maxWait>
                   <minIdle>5</minIdle>
                   <testOnBorrow>true</testOnBorrow>
                   <validationQuery>SELECT 1</validationQuery>
                   <validationInterval>30000</validationInterval>
               </configuration>
          </definition>
    </datasource>

    Following are the datasource 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 enter a negative value 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. 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.
    • 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. 

      Info

      For more information on other parameters that can be defined in the  master-datasources.xml  file, see  Tomcat JDBC Connection Pool

    Excerpt
    hiddentrue
    NOTE TO WRITERS: Add the following content as the second step, and replace <PRODUCT_HOME>/repository/conf/<PRODUCT_NAME>/<PRODUCT_NAME>.xml, with the correct folder path of your product.
  2. If you changed the product specific database, add the datasource configuration in the    <PRODUCT_HOME>/repository/conf/<PRODUCT_NAME>/<PRODUCT_NAME>.xml file as well. 

    NOTE TO WRITERS: Add the following content only i f it is applicable to your product.

    Info

    This step is not relevant if you changed the registry and user manager database.

    Excerpt
    hiddentrue
  3. If you changed the databases used for identity and storage , copy the WSO2_CARBON_DB datasource configuration for each of them in < PRODUCT_HOME>/repository/conf/datasources/master-datasources.xml file and replace its default values with your custom values. Excerpt
    hiddentrue
    NOTE TO WRITERS: Add the following content only i f it is applicable to your product.
  4. Replace the default values in the datasource configurations of the following files with your custom values accordingly, to point to the created registry and user manager, identity and storage databases.

    • <PRODUCT_HOME>/repository/conf/identity.xml
    • <PRODUCT_HOME>/repository/conf/user-mgt.xml
    • <PRODUCT_HOME>/repository/conf/registry.xml