This site contains the documentation that is relevant to older WSO2 product versions and offerings.
For the latest WSO2 documentation, visit https://wso2.com/documentation/.
Setting up IBM Informix
The following sections describe how to replace the default H2 databases with IBM Informix:
Download the latest version of IBM Informix and install it on your computer. Create the database and users in Informix. For instructions on creating the database and users, see Informix product documentation. Do the following changes to the default database when creating the Informix database. Add the following system environment variables. Download the Informix JDBC drivers and copy them to your WSO2 product's Use Informix JDBC driver version 3.70.JC8, 4.10.JC2 or higher. A datasource is used to establish the connection to a database. By default, Follow the steps below to change the type of the default Edit the default datasource configuration in the < 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: testOnBorrow This property is not applicable to the Carbon database in WSO2 products 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 an 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. For more information on other parameters that can be defined in the < 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. If you are setting up a separate database to store registry-related data, update the following configurations in the < If you are setting up a separate database to store user management data, update the following configurations in the < To create the database tables, connect to the database that you created earlier and run the following scripts. To create tables in the registry and user manager database ( Restart the server. You can create database tables automatically when starting the product for the first time by using the For Windows: For Linux: Prerequisites
Creating the database
-k 4
) :
onspaces -c -S testspace4 -k 4 -p /usr/informix/logdir/data5.dat -o 100 -s 3000000
export DB_LOCALE=en_US.UTF-8
export CLIENT_LOCALE=en_US.UTF-8
onspaces -c -S testspace4 -k 4 -p /usr/informix/logdir/data5.dat -o 100 -s 3000000
<INFORMIX_HOME>/etc/onconfig
file, andreplace the given example sbspace name (i.e. testspace4
) with your sbspace name:
SBSPACENAME testspace4
Setting up Informix JDBC drivers
<PRODUCT_HOME>/repository/components/lib/
directory. Setting up datasource configurations
WSO2_CARBON_DB
datasource is used to connect to the default H2 database, which stores registry and user management data. After setting up the IBM Informix 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. Changing the default WSO2_CARBON_DB datasource
WSO2_CARBON_DB
datasource.PRODUCT_HOME>/repository/conf/datasources/m
aster-datasources.xml
file as shown below.<datasource>
<name>WSO2AM_DB</name>
<description>The datasource used for API Manager database</description>
<jndiConfig>
<name>jdbc/WSO2AM_DB</name>
</jndiConfig>
<definition type="RDBMS">
<configuration>
<!-- IP ADDRESS AND PORT OF DB SERVER -->
<url>jdbc:informix-sqli://localhost:1533/AM_DB;CLIENT_LOCALE=en_US.utf8;DB_LOCALE=en_us.utf8;IFX_USE_STRENC=true;</url>
<username>wso2carbon</username>
<password>wso2carbon</password>
<driverClassName>com.informix.jdbc.IfxDriver</driverClassName>
<maxActive>80</maxActive>
<maxWait>60000</maxWait>
<testOnBorrow>true</testOnBorrow>
<validationQuery>SELECT 1</validationQuery>
<validationInterval>30000</validationInterval>
<defaultAutoCommit>false</defaultAutoCommit>
</configuration>
</definition>
</datasource>
Element Description url CLIENT_LOCALE=en_US.utf8;DB_LOCALE=en_us.utf8;IFX_USE_STRENC=true;
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. defaultAutoCommit PRODUCT_HOME>/repository/conf/datasources/
master-datasources.xml
file, see Tomcat JDBC Connection Pool. Configuring new datasources to manage registry or user management data
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.PRODUCT_HOME>/repository/conf/
registry.xml
file.<dbConfig name="wso2registry">
<dataSource>jdbc/MY_DATASOURCE_NAME</dataSource>
</dbConfig>
PRODUCT_HOME>/repository/conf/
user-mgt.xml
file.<Configuration>
<Property name="dataSource">jdbc/MY_DATASOURCE_NAME</Property>
</Configuration>
Creating database tables
WSO2CARBON_DB
), use the below script:<PRODUCT_HOME>/dbscripts/informix.sql
-Dsetup
parameter as follows:<PRODUCT_HOME>/bin/wso2server.bat -Dsetup
<PRODUCT_HOME>/bin/wso2server.sh -Dsetup
Changing the product-specific/identity 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 related data, the instructions are the same. In summary:
Add the datasource to the
master-datasources.xml
file. The datasource for the product-specific database is already there in themaster-datasources.xml
file by the nameWSO2AM_DB
. Change its elements with your custom values.Create the database tables using the following scripts:
For the product-specific database Use
<PRODUCT_HOME>/dbscripts/identity/application-mgt/informix.sql
For the identity database Use
<PRODUCT_HOME>/dbscripts/identity/informix.sql
Update the following configurations, with the defined datasource name of the corresponding database configuration you added to the <
PRODUCT_HOME>/repository/conf/datasources/m
aster-datasources.xml
file.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.<dbConfig name="wso2registry"> <dataSource>jdbc/WSO2CarbonDB</dataSource> </dbConfig>
If you are setting up a separate database to store user management related data, update the following configurations in the<
PRODUCT_HOME>/repository/conf/
user-mgt.xml
file.<Configuration> <Property name="dataSource">jdbc/WSO2CarbonDB</Property> </Configuration>
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.
<JDBCPersistenceManager> <DataSource> <!-- Include a data source name (jndiConfigName) from the set of datasources defined in master-datasources.xml --> <Name>jdbc/WSO2CarbonDB</Name> </DataSource> </JDBCPersistenceManager>