

Changing to IBM DB2¶

By default, MWARE ESB uses the embedded H2 database as the database for storing user management and registry data. Given below are the instructions you need to follow in order to use IBM DB2 for this purpose.

Setting up IBM DB2¶

The following sections describe how to set up a IBM DB2 database to replace the default H2 database in your MWARE product:

Setting up the database and users
Setting up the drivers
Executing db scripts to create tables on IBM DB2 database

Setting up the database and users¶

Follow the instructions below to set up a IBM DB2 database:

Create the database using the following command:
```
db2 CREATE DATABASE <DATABASE_NAME>
```
Before issuing an SQL statement, establish the connection to the database using the following command:
```
db2 CONNECT TO <DATABASE_NAME> user <USER_NAME> using <PASSWORD>
```

Grant required permissions for users as follows:

db2 <AUTHORITY> ON DATABASE TO USER <USER_NAME>

For example:

db2 GRANT DBADM, CREATETAB, BINDADD, CONNECT, CREATE_NOT_FENCED, IMPLICIT_SCHEMA, LOAD ON DATABASE TO USER sharedadmin

Disconnect from the database using the following command:
```
db2 DISCONNECT CURRENT
```

Setting up the drivers¶

Unzip the MWARE ESB pack. Let's refer to this as <API-M_HOME>.
Download the IBM DB2 JDBC driver.
Copy it to the <API-M_HOME>/repository/components/lib/ directory in all the nodes of the cluster.

Executing db scripts to create tables on IBM DB2 database¶

To create tables in the registry and user manager database (WSO2_SHARED_DB), execute the relevant script as shown below.
```
db2 CONNECT TO <DATABASE_NAME> user <USER_NAME> using <PASSWORD>
db2 -td/ -vmf '<API-M_HOME>/dbscripts/db2.sql';
```

To create tables in the apim database (WSO2AM_DB), execute the relevant script as shown below.

db2 CONNECT TO <DATABASE_NAME> user <USER_NAME> using <PASSWORD>
db2 -td/ -vmf '<API-M_HOME>/dbscripts/apimgt/db2.sql';

Changing the database to IBM DB2¶

Creating the datasource connection to IBM DB2

Creating the datasource connection to IBM DB2¶

A datasource is used to establish the connection to a database. By default, WSO2_SHARED_DB and WSO2AM_DB datasource are configured in the deployment.toml file for the purpose of connecting to the default H2 databases.

After setting up the IBM DB2 database to replace the default H2 database, either change the default configurations of the WSO2_SHARED_DB and WSO2AM_DB datasource, or configure a new datasource to point it to the new database as explained below.

Note

If you are configuring API-M in a distributed setup, do the changes in all the MWARE ESB components.

Follow the instructions below to change the type of the default datasource.

Open the <API-M_HOME>/repository/conf/deployment.toml configuration file and locate the [database.shared_db] and [database.apim_db] configuration elements.

You simply have to update the URL pointing to your IBM DB2 database, the username, and password required to access the database and the IBM DB2 driver details as shown below.

Element	Description
type	The database type used
url	The URL of the database. The default port for IBM DB2 is 50000
username and password	The name and password of the database user
driverClassName	The class name of the database driver
validationQuery	The SQL query that will be used to validate connections from this pool before returning them to the caller.

Sample configuration is shown below:

Format

type = "db2"
url = "jdbc:db2://localhost:50000/<DATABASE_NAME>"
username = "<USER_NAME>"
password = "<PASSWORD>"
driver = "com.ibm.db2.jcc.DB2Driver"
validationQuery = "SELECT 1 FROM SYSIBM.SYSDUMMY1"

Example

[database.apim_db]
type = "db2"
url = "jdbc:db2://localhost:50000/apim_db"
username = "apimadmin"
password = "apimadmin"
driver = "com.ibm.db2.jcc.DB2Driver"
validationQuery = "SELECT 1 FROM SYSIBM.SYSDUMMY1"

[database.shared_db]
type = "db2"
url = "jdbc:db2://localhost:50000/shared_db"
username = "sharedadmin"
password = "sharedadmin"
driver = "com.ibm.db2.jcc.DB2Driver"
validationQuery = "SELECT 1 FROM SYSIBM.SYSDUMMY1"

You can update the configuration elements given below for your database connection.

Element	Description
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.
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	This property is not applicable to the Carbon database in MWARE 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 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.
commitOnReturn	If `defaultAutoCommit =false`, then you can set `commitOnReturn =true`, so that the pool can complete the transaction by calling the commit on the connection as it is returned to the pool. However, If `rollbackOnReturn =true` then this attribute is ignored. The default value is false.
rollbackOnReturn	If `defaultAutoCommit =false`, then you can set `rollbackOnReturn =true` so that the pool can terminate the transaction by calling rollback on the connection as it is returned to the pool. The default value is false.

Sample configuration is shown below:

Format

type = "db2"
url = "jdbc:db2://localhost:50000/<DATABASE_NAME>"
username = "<USER_NAME>"
password = "<PASSWORD>"
driver = "com.ibm.db2.jcc.DB2Driver"
validationQuery = "SELECT 1 FROM SYSIBM.SYSDUMMY1"
pool_options.<OPTION-1> = <VALUE-1>
pool_options.<OPTION-2> = <VALUE-2>
...

Example

[database.apim_db]
type = "db2"
url = "jdbc:db2://localhost:50000/apim_db"
username = "apimadmin"
password = "apimadmin"
driver = "com.ibm.db2.jcc.DB2Driver"
validationQuery = "SELECT 1 FROM SYSIBM.SYSDUMMY1"
pool_options.maxActive = 100
pool_options.maxWait = 10000
pool_options.validationInterval = 10000

[database.shared_db]
type = "db2"
url = "jdbc:db2://localhost:50000/shared_db"
username = "sharedadmin"
password = "sharedadmin"
driver = "com.ibm.db2.jcc.DB2Driver"
validationQuery = "SELECT 1 FROM SYSIBM.SYSDUMMY1"
pool_options.maxActive = 50
pool_options.maxWait = 30000

Info

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

Restart the server.

Note

To give the Key Manager, Publisher, and Developer Portal components access to the user management data with shared permissions, JDBCUserStoreManager has been configured by default. For more information, refer Configuring Userstores.
Info

Changing WSO2CARBON_DB to IBM DB2

By default WSO2CARBON_DB will be an embedded H2 database and it is not necessary to change it to another database. But if you have a requirement to change it, you can follow the below steps. (When changing the carbon database, make sure that each server node have its own WSO2CARBON_DB. If you don't want to change the carbon database, then you can ignore this section.)
- Create tables in the carbon database (WSO2CARBON_DB) using the script <API-M_HOME>/dbscripts/db2.sql.
- Open the <API-M_HOME>/repository/conf/deployment.toml configuration file. Locate the [database.local] configuration element and update the URL pointing to your IBM DB2 database, the username, and password required to access the database and the IBM DB2 driver details similarly as explained before.
Example
```
[database.local]
type = "db2"
url = "jdbc:db2://localhost:50000/carbon_db"
username = "carbonadmin"
password = "carbonadmin"
driver = "com.ibm.db2.jcc.DB2Driver"
validationQuery = "SELECT 1 FROM SYSIBM.SYSDUMMY1"
```

Top