The following sections describe how to replace the default H2 databases with Oracle RAC.
Oracle Real Application Clusters (RAC) is an option for the Oracle Database for clustering and high availability in Oracle database environments. In the Oracle RAC environment, some of the commands used in
oracle.sql are considered inefficient. Therefore, the product has a separate SQL script
oracle_rac.sql for Oracle RAC. The Oracle RAC-friendly script is located in the
dbscripts folder together with other
To test products on Oracle RAC, rename
oracle.sql before running
Step 1: Setting up the Oracle RAC database and user
Follow the steps below to set up an Oracle RAC database.
- Set environment variables <
ORACLE_SIDwith the corresponding values
- Connect to Oracle using SQL*Plus as SYSDBA.
Create a database user and grant privileges to the user as shown below:
- Exit from the SQL*Plus session by executing the
Step 2: Copying the JDBC driver
Copy the Oracle JDBC libraries (for example, the
<ORACLE_HOME>/jdbc/lib/ojdbc14.jar file) to the
Remove the old database driver from the
<MB_HOME>/repository/components/dropins/ directory when you upgrade the database driver.
Step 3: Connecting the server to an Oracle database
Once you have setup the physical database as explained in the previous step, the next step is to enable the connectivity between your MB server and the database. This can be done by simply copying the relevant database drivers to your server, and then configuring the datasources in MB to link to the new database. See the instructions given below.
Setting up datasource configurations
After, you create a datasource to point to it in the following files:
Edit the default datasource configuration in the <
aster-datasources.xmlfile. Replace the
driverClassNamesettings with your custom values and also the other values accordingly 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.
For more information on other parameters that can be defined in the <
master-datasources.xmlfile, see Tomcat JDBC Connection Pool.
- Similarly, edit the database configurations in
<MB_HOME>/repository/conf/identity.xmlfiles as well.
Step 4: Creating the database tables
To create the database tables, connect to the database that you created earlier and run the following scripts in SQL*Plus:
To create tables in the registry and user manager database (
WSO2CARBON_DB), use the below script:
Restart the server.
You can create database tables automatically when starting the product for the first time by using the
-Dsetupparameter as follows: