Use the CData JDBC Driver for DB2 in MicroStrategy



Connect to DB2 data in MicroStrategy Developer using the CData JDBC Driver for DB2.

MicroStrategy is an analytics and mobility platform that enables data-driven innovation. When you pair MicroStrategy with the CData JDBC Driver for DB2, you gain database-like access to live DB2 data from MicroStrategy, expanding your reporting and analytics capabilities. In this article, we walk through creating a database instance for DB2 in MicroStrategy Developer and create a Warehouse Catalog for the DB2 data.

The CData JDBC Driver offers unmatched performance for interacting with live DB2 data in MicroStrategy due to optimized data processing built into the driver. When you issue complex SQL queries from MicroStrategy to DB2, the driver pushes supported SQL operations, like filters and aggregations, directly to DB2 and utilizes the embedded SQL engine to process unsupported operations (often SQL functions and JOIN operations) client-side. With built-in dynamic metadata querying, you can visualize and analyze DB2 data using native MicroStrategy data types.

Connect to DB2 in MicroStrategy Developer

You can connect to DB2 in MicroStrategy Developer by adding a database instance based on the CData JDBC Driver for DB2.* Before you begin, you will need to install the JDBC Driver for DB2 on the machine hosting the MicroStrategy Intelligence Server that your instance of MicroStrategy Developer is connected to.

  1. Open MicroStrategy Developer and select a Project Source.
  2. Navigate to Administration -> Configuration Managers -> Database Instances and right-click to add a new instance.
  3. Name the instance, select Generic DBMS as the database connection type, and create a new database connection.
  4. In the database connection wizard, name the connection and create a new Database Login name, setting the user and password for DB2.
  5. On the Advanced tab for the connection wizard, set the additional connection string parameters as follows.
    • Add the JDBC keyword to the connection string.
    • Set MSTR_JDBC_JAR_FOLDER to the path of the directory containing the JAR file for the JDBC driver. (C:\Program Files\CData JDBC Driver for DB2\lib\ on Windows.)
    • Set DRIVER to cdata.jdbc.db2.DB2Driver, the driver class.
    • Set URL to the JDBC URL for the DB2 driver, which contains the necessary connection properties.

      Set the following properties to connect to DB2:

      • Server: Set this to the name of the server running DB2.
      • Port: Set this to the port the DB2 server is listening on.
      • Database: Set this to the name of the DB2 database.
      • User: Set this to the username of a user allowed to access the database.
      • Password: Set this to the password of a user allowed to access the database.

      You will also need to install the corresponding DB2 driver:

      • Windows: Install the IBM Data Server Provider for .NET.

        On Windows, installing the IBM Data Server Provider is sufficient, as the installation registers it in the machine.config.

      • Java: Install the IBM Data Server Driver for JDBC.

        In the Java version, place the IBM Data Server Driver JAR in the www\WEB-INF\lib\ folder for this application.

      Built-in Connection String Designer

      For assistance in constructing the JDBC URL, use the connection string designer built into the DB2 JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

      java -jar cdata.jdbc.db2.jar

      Fill in the connection properties and copy the connection string to the clipboard.

      When you configure the JDBC URL, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing reports and visualizations.

    Typical additional connection string properties follow:

    JDBC;MSTR_JDBC_JAR_FOLDER=PATH\TO\JAR\;DRIVER=cdata.jdbc.db2.DB2Driver;URL={jdbc:db2:Server=10.0.1.2;Port=50000;User=admin;Password=admin;Database=test;};
  6. Ensure that you have not selected an ODBC data source (this will trigger MicroStrategy to use the additional connection string parameters to build the database instance) and click OK.
  7. Click OK to close the database instance wizard.
  8. In the Project Source, right-click the project and open the Project configuration.
  9. Navigate to Database Instances, select the newly created database instance, and click OK.
  10. Close MicroStrategy Developer and restart the connected MicroStrategy Intelligence Server to complete the database instance creation.

With the database instance configured, you will now be able to connect to DB2 data from the Warehouse Catalog and Data Import.

Connect to DB2 Data from the Warehouse Catalog

Once you have created a database instance based on the JDBC Driver for DB2, you can connect to data from the Warehouse Catalog.

  1. Select your project and click Schema -> Warehouse Catalog.
  2. In the Read Settings for the Catalog, click Settings and set the queries to retrieve the schema:
    • To retrieve the list of tables, use the following query: SELECT * FROM SYS_TABLES
    • To retrieve the list of columns for selected tables, use the following query: SELECT DISTINCT CatalogName NAME_SPACE, TableName TAB_NAME, ColumnName COL_NAME, DataTypeName DATA_TYPE, Length DATA_LEN, NumericPrecision DATA_PREC, NumericScale DATA_SCALE FROM SYS_TABLECOLUMNS WHERE TableName IN (#TABLE_LIST#) ORDER BY 1,2,3
  3. Select tables to be used in the project.

Using the CData JDBC Driver for DB2 in MicroStrategy, you can easily create robust visualizations and reports on DB2 data. Read our other articles on connecting to DB2 in MictroStrategy Web and connecting to DB2 in MicroStrategy Desktop for more information.


Note: Connecting using a JDBC Driver requires a 3- or 4-Tier Architecture.

Ready to get started?

Download a free trial of the IBM DB2 Driver to get started:

 Download Now

Learn more:

IBM DB2 Icon IBM DB2 JDBC Driver

Rapidly create and deploy powerful Java applications that integrate with IBM DB2.