Connection to IBM DB2
Support for IBM DB2 as a data source is in preparation and will become generally available for SaaS customers in an upcoming release. This page describes what the connection will require, so you can prepare access on the database side in advance.
This connector will become GA for SaaS customers soon. Please contact your DQC support team for further infos!
What to prepare
The connection will follow the same pattern as the other database connectors: a read-only technical user, network access from the platform, and the coordinates of the target database.
Field | Example | Description |
|---|---|---|
Name | Logistics_DB | A descriptive name for this connection |
User | dqcreader | DB2 user with read-only access |
Password | your_password_here | Password for the specified user |
Host | db2.company.internal | DNS name or IP address of the DB2 server |
Port | 50000 | Default DB2 port; 50001 is commonly used for TLS-secured connections |
Database name | LOGISTIC | Name of the target database |
Schema | LOGISTICS (optional) | Default schema for unqualified table names |
Prepare a read-only user
Create a dedicated technical user and grant it the right to connect and to read the relevant tables:
GRANT CONNECT ON DATABASE TO USER dqcreader;
GRANT SELECT ON TABLE logistics.shipments TO USER dqcreader;
GRANT SELECT ON TABLE logistics.carriers TO USER dqcreader;As with every other connector, avoid administrative or shared credentials and keep the grants limited to the tables you want to check.
Whitelist the DQC Platform IP address
Allow inbound connections from the following static IP address in your firewall or security group:
3.123.94.228Availability
SaaS: general availability planned for an upcoming release
Private cloud: available on request — talk to your DQC contact about the timeline
Learn more: Supported data sources