IBM DB2
IBM DB2 is a Relational DataBase Management System (RDBMS) introduced by IBM. It delivers advanced data management and analytics capabilities for your transactional and warehousing workloads. DB2 is supported across Linux, Unix and Windows operating systems.
The IBM DB2 connector by IConduct enables the user to seamlessly manage the data in an integrated data flow across IBM DB2 and company’s business applications. The connection is empowered by Open Database Connectivity (ODBC). This standard application programming interface (API) allows for accessing database management systems (DBMS) using SQL as a standard for accessing the data.
To configure the IBM DB2 connector, follow the instructions below:
- In the Admin Navigation tree, select Connections and click New.

Connections Section in the Admin Navigation Tree
- Scroll down to the Database Servers section and select the IBM DB2 item from the list.

Connector Selection Page
- In the ODBC Provider work area, fill in the following fields and click Save.

Connection Work Area
Fields | Description |
---|---|
Connection* |
A new connection name. Enter a connection alias here. |
Is Active |
Toggles connector’s activity at interface execution. Enable the checkbox to activate the connection for execution. |
Cloud Agent |
The LAN you are working with. Select "IConduct" for cloud systems and your corporate agent for internal systems. |
Implementation Type* |
Defines the implementation type. Select from the drop-down list:
|
Is Source |
This connection entity is available as a data source for Import (writing to Schema). Enable the checkbox to ensure data import. |
Is Target |
This connection entity is available as a data target that receives data from schema to current data container. Enable the checkbox to ensure data export. |
Timeout |
The length of time (in milliseconds) the IConduct platform waits for a response from the connection provider before returning a timeout error. Set the time value to stop the system from connection attempts. |
Query |
The box is intended for entering a query. You can test the defined query by clicking Test Query once the connection is saved. It’s recommended to test the query after the connection testing. |
DateTime Format |
Allows defining the date and time formats appropriate for the connection. Recommended Format: yyyy-MM-dd HH:mm:ss |
Connection String* |
A string that specifies information about a data source and the means of connecting to it. Refer to this page for more information about the IBM DB2 connection strings. General ODBC connection string example: DSN=myDsn;Uid=myUsername;Pwd=; See the IBM DB 2 connection string explanation in the table below. |
Username |
The username used for impersonation. |
Password |
The password to username used for impersonation. |
Domain |
Not used in this connector. |
* - mandatory fields
IB DB2 connection string breakdown example:
Driver=$HOME/db2_cli_odbc_driver1/lib/libdb2.a;Database=myDataBase;Hostname=myServerAddress;
Port=1234;Protocol=TCPIP;Uid=myUsername;Pwd=myPassword;
Fields | Description |
---|---|
Driver |
The full name of the installed IBM DB2 ODBC driver. Driver=$HOME/db2_cli_odbc_driver1/lib/libdb2.a |
Databse |
The database alias (for a cataloged database). The maximum size of the Database keyword is 255 bytes. Database=myDataBase |
Hostname |
The server name with an optional port number for a direct connection. Use either the IPv4 notation (server name|ip address[:port]) or the IPv6 notation. Hostname=myServerAddress |
Port |
The port number specified when launching the cluster. If you have a firewall, ensure that this port is open for use. Port=1234 |
Protocol |
The communication protocol used between the CreateConnection() and the database server. Protocol=TCPIP |
UID |
The login account. Required, unless the client machine is trusted by the host machine. Uid=myUsername |
PWD |
The password associated with the User ID. Required if the client machine or user account is not trusted by the host. Prohibited unless a User ID is given. Pwd=myPassword |
Once the connection is saved, you can test if it is successful. Click Test Connection in the toolbar. If the created connection works, you will receive a success message.

Testing the Connection