Skip to content

Change to Oracle RAC

By default, WSO2 Identity Server uses the embedded H2 database as the database for storing user management and registry data. Given below are the steps you need to follow in order to use Oracle RAC for this purpose.


Datasource configurations

A datasource is used to establish the connection to a database. By default, WSO2_IDENTITY_DB and WSO2_SHARED_DB datasources are used to connect to the default H2 database.

  • WSO2_SHARED_DB - The datasource which stores registry and user management data.
  • WSO2_IDENTITY_DB - The datasource specific to the identity server which stores identity related data.

After setting up the Oracle RAC database, you can point the WSO2_IDENTITY_DB or WSO2_SHARED_DB or both to that Oracle RAC database by following the instructions given below.


Change the default datasource

Minimum configurations for changing default datasource to Oracle RAC

You can configure the datasource by editing the default configurations in <IS-HOME>/repository/conf/deployment.toml.

Following are the basic configurations and their descriptions.

Element Description
username and password The name and password of the database user
type The type of the database
hostname The hostname of the host where the database is hosted
port The port of the database
name The name of the database

A sample configuration is given below.

  1. WSO2_IDENTITY_DB

    1. Configure the deployment.toml file.

      [database.identity_db]
      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)))"
      username = "regadmin"
      password = "regadmin"
      driver = "oracle.jdbc.OracleDriver"
      [database.identity_db.pool_options]
      maxActive = "80"
      maxWait = "60000"
      minIdle = "5"
      testOnBorrow = true
      validationQuery="SELECT 1 FROM DUAL"
      validationInterval="30000"
      defaultAutoCommit=false
      
    2. Execute database scripts.

      Navigate to <IS-HOME>/dbscripts. Execute the scripts in the following files against the database created.

      • <IS-HOME>/dbscripts/identity/oracle_rac.sql
      • <IS-HOME>/dbscripts/consent/oracle_rac.sql
  2. WSO2_SHARED_DB

    1. Configure the deployment.toml file.

      [database.shared_db]
      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)))"
      username = "regadmin"
      password = "regadmin"
      driver = "oracle.jdbc.OracleDriver"
      [database.shared_db.pool_options]
      maxActive = "80"
      maxWait = "60000"
      minIdle = "5"
      testOnBorrow = true
      validationQuery="SELECT 1 FROM DUAL"
      validationInterval="30000"
      defaultAutoCommit=false
      
    2. Execute database scripts.

      Execute the scripts in the <IS-HOME>/dbscripts/oracle_rac.sql file against the database created.

  3. If you have a requirement in using workflow feature follow, Change the default database of BPS database

  4. Download the Oracle RAC JDBC driver for the version, you are using and copy it to the <IS_HOME>/repository/components/lib folder


Advanced database configurations

Apart from the basic configurations specified above, WSO2 Identity Server supports some advanced database configurations as well.

  • WSO2_IDENTITY_DB related configurations that should be added to the deployment.toml file.

    [database.identity_db.pool_options]
    maxActive = "80"
    maxWait = "360000"
    minIdle ="5"
    testOnBorrow = true
    validationQuery="SELECT 1"
    validationInterval="30000"
    defaultAutoCommit=false
    commitOnReturn=true
    
  • WSO2_SHARED_DB deployment.toml related configurations that should be added to the deployment.toml file.

    [database.shared_db.pool_options]
    maxActive = "80"
    maxWait = "360000"
    minIdle ="5"
    testOnBorrow = true
    validationQuery="SELECT 1"
    validationInterval="30000"
    defaultAutoCommit=false
    commitOnReturn=true
    

The elements in the above configuration are described below:

maxActive This is 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 This is 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. Enter zero to create none.

testOnBorrow

This indicates whether objects will be validated before being borrowed from the pool. If the object fails to be validated, it will be dropped from the pool and another attempt will be made to borrow another.

defaultAutoCommit

Indicates whether to commit database changes automatically or not
validationInterval This is the indication to avoid excess validation and only run validation after the specified 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.
defaultAutoCommit

This property is not applicable to the carbon database in WSO2 Identity Server because auto committing is usually handled at the code level, i.e., the default auto commit configuration specified for the RDBMS driver will be effective instead of this property element. Typically, auto committing is enabled for RDBMS drivers by default.

When auto committing is enabled, each SQL statement will be committed to the database as an individual transaction, as opposed to committing multiple statements as a single transaction.

Info

For more information on other parameters that can be defined in the <IS_HOME>/repository/conf/deployment.toml file, see Tomcat JDBC Connection Pool.

Support for case-sensitive usernames

Usernames in WSO2 Identity Server are case-insensitive by default. If you wish to enable case-sensitive usernames, configure the following properties.

To enable the case-sensitivity for the primary user store, open the deployment.toml file found in the <IS-HOME>/repository/conf/ directory and add the following configurations to the primary user store.

[user_store.properties]
CaseInsensitiveUsername = false
UseCaseSensitiveUsernameForCacheKeys = false

For secondary user stores, add the following configurations to the <userstore>.xml file found in the <IS_HOME>/repository/deployment/server/userstores directory.

<Property name="CaseInsensitiveUsername">false</Property>
<Property name="UseCaseSensitiveUsernameForCacheKeys">false</Property>
The database indexes are created using LOWER() functions to support case-insensitive usernames for the related tables. Therefore, remove the LOWER() functions from the related index creation queries in the scripts at <IS_HOME>/dbscripts/.

Eg:

CREATE UNIQUE INDEX INDEX_UM_USERNAME_UM_TENANT_ID ON UM_USER(LOWER(UM_USER_NAME), UM_TENANT_ID);