If the directory/file paths specified in this guide do not exist in your WSO2 product, see Directory Structure of WSO2 Products to locate the paths applicable to your product.

Versions Compared


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

NOTES TO WRITERS: Please add an intro sentence and a TOC at the beginning of your hosting page:


The following sections describe how to replace the default H2 databases with IBM Informix:

Table of Contents



set up IBM Informix to replace the default H2


database in your WSO2 product:

Table of Contents


Download the latest version of IBM Informix and install it on your computer.



Do the following changes to the default database when creating the Informix database.

  • Use

    Define the page size as 4K or higher when creating the dbspace as shown in the following command (i.e. denoted by -k 4) :

    Code Block
    onspaces -c -S testspace4 -k 4 -p /usr/informix/logdir/data5.dat -o 100 -s 3000000
  • Add the following system environment variables.

    Code Block
    export DB_LOCALE=en_US.UTF-8
    export CLIENT_LOCALE=en_US.UTF-8
  • Create


    an sbspace other than the dbspace by executing the following command:

    Code Block
    onspaces -c -S testspace4 -k 4 -p /usr/informix/logdir/data5.dat -o 100 -s 3000000
  • Add the following entry to the <INFORMIX_HOME>/etc/onconfig file,


    and replace the given example sbspace name (i.e. testspace4) with your sbspace name:

    Code Block
    SBSPACENAME testspace4

Setting up Informix JDBC drivers



Use Informix JDBC driver version 3.70.JC8, 4.10.JC2 or higher.


What's next

By default,


Follow the steps below to change the type of the default WSO2_CARBON_DB datasource.

  1. Edit the default datasource configuration in the <PRODUCT_HOME>/repository/conf/datasources/m aster-datasources.xml file as shown below.

    Code Block
                <description>The datasource used for API Manager database</description>
                <definition type="RDBMS">
                        <!-- IP ADDRESS AND PORT OF DB SERVER -->
                        <validationQuery>SELECT 1</validationQuery>

    The elements in the above configuration are described below:


    The URL of the database. The default port for a DB2 instance is 50000.

    You need to add the following configuration when specifying the connection URL as shown in the example above:


    Add the following configuration to the connection URL when specifying it as shown in the example above: CLIENT_LOCALE=en_US.utf8;DB_LOCALE=en_us.utf8;IFX_USE_STRENC=true;

    username and passwordThe name and password of the database user
    driverClassNameThe class name of the database driver
    maxActiveThe 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.
    maxWaitThe 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.
    minIdleThe 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.
    validationQueryThe SQL query that will be used to validate connections from this pool before returning them to the caller.
    validationIntervalThe 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 <PRODUCT_HOME>/repository/conf/datasources/ master-datasources.xml file, see Tomcat JDBC Connection Pool.


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.

  1. Add a new datasource with similar configurations as the WSO2_CARBON_DB datasource above to the <PRODUCT_HOME>/repository/conf/datasources/ master-datasources.xml file . Change its elements with your custom values. For instructions, see Setting up datasource configurations.
  2. If you are setting up a separate database to store registry-related data, update the following configurations in the <PRODUCT_HOME>/repository/conf/ registry.xml file.

    Code Block
    <dbConfig name="wso2registry">
  3. 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.xml file.

    Code Block
    	<Property name="dataSource">jdbc/MY_DATASOURCE_NAME</Property>

Creating database tables

To create the database tables, connect to the database that you created earlier and run the following scripts.

  1. To create tables in the registry and user manager database (WSO2CARBON_DB ), use the below script:

    Code Block
  2. Restart the server.


    You can create database tables automatically when starting the product for the first time by using the -Dsetup parameter as follows:

    • For Windows: <PRODUCT_HOME>/bin/wso2server.bat -Dsetup

    • For Linux: <PRODUCT_HOME>/bin/wso2server.sh -Dsetup



Note to writers: Add this content at the end of the page if any of the additional databases is relevant to your product.

Changing the identity/storage/product-specific databases

The topics above show how to change the WSO2_CARBON_DB, which is used to store registry and user manager information. If you changed the product-specific database that come by default or set up a separate database for identity or storage related data, the instructions are the same. In summary:


Add a new datasource configuration to the following files for each of the separate databases that you need to create.

For the identity databaseAdd it to the <PRODUCT_HOME>/repository/conf/datasources/<check the correct path and add file name (something like master-datasources.xml)>
For the storage databaseAdd it to the <PRODUCT_HOME>/repository/conf/datasources/<check the correct path and add file name (something like master-datasources.xml)
For the product-specific databaseAdd it to the <PRODUCT_HOME>/repository/conf/><check the correct path and add file name (something like api-manager.xml)


Create the database tables using the following scripts:

For the identity databaseUse <PRODUCT_HOME>/dbscripts/identity/<check the correct path and add file name (something like mysql.sql)>
For the storage databaseUse <PRODUCT_HOME>/dbscripts/storage/<check the correct path and add file name (something like /mysql/resoucre.sql)>
For the product-specific databaseUse  <PRODUCT_HOME>/dbscripts/<check the correct path and add file name (something like /apimgt/mysql.sql)> 

Update the following configurations, with the defined datasource name of the corresponding database configuration you added to the <PRODUCT_HOME>/repository/conf/datasources/master-datasources.xml file.

If you are setting up a separate database to store identity related data, update the following configurations in the <PRODUCT_HOME>/repository/conf/identity.xml file.

Code Block
		<!-- Include a data source name (jndiConfigName) from the set of datasources defined in master-datasources.xml -->


all WSO2 products are configured to use the embedded H2 database. To configure your product with IBM Informix, see Changing to IBM Informix.