...
| Warning |
|---|
Note that for Oracle 11g it is recommended to use the ojdbc6.jar file with API Manager 1.10.0. |
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 Oracle RAC 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.
...
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/m aster-datasources.xml file as shown below.
| Code Block | ||
|---|---|---|
| ||
<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:oracle:thin:@(DESCRIPTION=(LOAD_BALANCE=on)
(ADDRESS=(PROTOCOL=TCP)(HOST=racnode1) (PORT=1521))
(ADDRESS=(PROTOCOL=TCP)(HOST=racnode2) (PORT=1521))
(CONNECT_DATA=(SERVICE_NAME=rac)))</url>
<username>regadmin</username>
<password>regadmin</password>
<driverClassName>oracle.jdbc.driver.OracleDriver</driverClassName>
<maxActive>80</maxActive>
<maxWait>60000</maxWait>
<minIdle>5</minIdle>
<testOnBorrow>true</testOnBorrow>
<validationQuery>SELECT 1 FROM DUAL</validationQuery>
<validationInterval>30000</validationInterval>
</configuration>
</definition>
</datasource> |
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. |
| 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 <PRODUCT_HOME>/repository/conf/datasources/ |
...
master-datasources.xml file, see Tomcat JDBC Connection Pool. |
Configuring new datasources 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 <PRODUCT_HOME>/repository/conf/datasources/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 <
PRODUCT_HOME>/repository/conf/registry.xmlfile.Code Block language xml <dbConfig name="wso2registry"> <dataSource>jdbc/MY_DATASOURCE_NAME</dataSource> </dbConfig>
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.xmlfile.Code Block language xml <Configuration> <Property name="dataSource">jdbc/MY_DATASOURCE_NAME</Property> </Configuration>
...