Setting up an IBM DB2

Follow the steps given below to set up the required IBM databases for your Micro Integrator.

Tip

ESB Micro Integrator requires databases for the following scenarios:

Prerequisites

Download the latest version of DB2 Express-C and install it on your computer.

For instructions on installing DB2 Express-C, see this ebook.

Setting up the database and users

The following IBM DB scripts are stored in the <MI_HOME>/dbscripts/db2 directory of your Micro Integrator. First, select the scripts that are required for your deployment.

You can run the scripts on one database instance or set up separate instances for each requirement. For convenience, it is recommended to set up separate databases for each use case.

Script Description
db2_cluster.sql This script creates the database tables that are required for cluster coordination (i.e., coordinating the server nodes in your VM deployment).This is only applicable if you have stateful integration artifacts deployed in a clustered setup.
db2_user.sql This script creates the database tables that are required for storing users and roles. This is only required if you have configured an RDBMS user store.
db2_transaction_count.sql This script creates the database tables that are required for storing the transaction counts. This is only required if you want to monitor transaction counts in your deployment.

Create the databases and then create the DB tables by pointing to the relevant script in the <MI_HOME>/dbscripts/db2 directory.

Create the database using either DB2 command processor or DB2 control center as described below.

Using the DB2 command processor

  1. Run DB2 console and execute the db2start command on a CLI to open DB2.
  2. Create the database using the following command:
    create database clusterdb
  3. Before issuing an SQL statement, establish the connection to the database using the following command:
    connect to clusterdb user <USER_ID> using <PASSWORD>

  4. Grant required permissions for users as follows:

    connect to DB_NAME
grant <AUTHORITY> on database to user <USER_ID>

    For more information on DB2 commands, see the DB2 Express-C Guide.

Using the DB2 control center

  1. Open the DB2 control center using the db2cc command:

  2. Right-click All Databases in the control center tree (inside the object browser), click Create Database, and then click Standard and follow the steps in the Create New Database wizard.

  3. Click User and Group Objects in the control center tree to create users for the newly created database.
  4. Give the required permissions to the newly created users.

Setting up DB2 JDBC drivers

Copy the DB2 JDBC drivers (db2jcc.jar and db2jcc_license_c0u.jar) from the <DB2_HOME>/SQLLIB/java/ directory to the MI_HOME/lib/ directory.

<DB2_HOME> refers to the installation directory of DB2 Express-C, and <MI_HOME> refers to the directory where you run the MWARE product instance.

Connecting the database to the server

Open the deployment.toml file in the <MI_HOME>/conf directory and add the following sections to create the connection between the Micro Integrator and the relevant database. Note that you need separate configurations corresponding to the separate databases (clusterdb, userdb, and transactiondb).

[[datasource]]
id = "WSO2_COORDINATION_DB"
url="jdbc:db2://SERVER_NAME:PORT/clusterdb"
username="root"
password="root"
driver="com.ibm.db2.jcc.DB2Driver"
pool_options.maxActive=50
pool_options.maxWait = 60000
pool_options.testOnBorrow = true
[[datasource]]
id = "WSO2CarbonDB"
url="jdbc:db2://SERVER_NAME:PORT/userdb"
username="root"
password="root"
driver="com.ibm.db2.jcc.DB2Driver"
pool_options.maxActive=50
pool_options.maxWait = 60000
pool_options.testOnBorrow = true
[[datasource]]
id = "WSO2_TRANSACTION_DB"
url="jdbc:db2://SERVER_NAME:PORT/transactiondb"
username="root"
password="root"
driver="com.ibm.db2.jcc.DB2Driver"
pool_options.maxActive=50
pool_options.maxWait = 60000
pool_options.testOnBorrow = true
[transaction_counter]
enable = true
data_source = "WSO2_TRANSACTION_DB"
update_interval = 2

About User DB

If you replace 'WSO2CarbonDB' with a different id in the user DB configuration, you also need to list the id as a datasource under the [realm_manager] section in the deployment.toml file as shown below.

[realm_manager]
data_source = "new_id"

Otherwise the user store database id defaults to 'WSO2CarbonDB' in the realm manager configurations..

See the descriptions of database connection parameters.

Top