Discover how a bimodal integration strategy can address the major data management challenges facing your organization today.
Get the Report →Use the CData ODBC Driver for Jira in MicroStrategy
Connect to Jira data in MicroStrategy Developer using the CData ODBC Driver for Jira.
MicroStrategy is an analytics and mobility platform that enables data-driven innovation. When you pair MicroStrategy with the CData ODBC Driver for Jira, you gain database-like access to live Jira data from MicroStrategy, expanding your reporting and analytics capabilities. In this article, we walk through creating a database instance for Jira in MicroStrategy Developer and creating a Warehouse Catalog based on Jira data.
The CData ODBC driver offers unmatched performance for interacting with live Jira data in MicroStrategy due to optimized data processing built into the driver. When you issue complex SQL queries from MicroStrategy to Jira, the driver pushes supported SQL operations, like filters and aggregations, directly to Jira 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 Jira data using native MicroStrategy data types.
About Jira Data Integration
CData simplifies access and integration of live Jira data. Our customers leverage CData connectivity to:
- Gain bi-directional access to their Jira objects like issues, projects, and workflows.
- Use SQL stored procedures to perform functional actions like changing issues status, creating custom fields, download or uploading an attachment, modifying or retrieving time tracking settings, and more.
- Authenticate securely using a variety of methods, including username and password, OAuth, personal access token, API token, Crowd or OKTA SSO, LDAP, and more.
Most users leverage CData solutions to integrate Jira data with their database or data warehouse, whether that's using CData Sync directly or relying on CData's compatibility with platforms like SSIS or Azure Data Factory. Others are looking to get analytics and reporting on live Jira data from preferred analytics tools like Tableau and Power BI.
Learn more about how customers are seamlessly connecting to their Jira data to solve business problems from our blog: Drivers in Focus: Collaboration Tools.
Getting Started
Connect to Jira as an ODBC Data Source
Information for connecting to Jira follows, along with different instructions for configuring a DSN in Windows and Linux environments (the ODBC Driver for Jira must be installed on the machine hosting the connected MicroStrategy Intelligence Server).
To connect to JIRA, provide the User and Password. Additionally, provide the Url; for example, https://yoursitename.atlassian.net.
When you configure the DSN, 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.
Windows
If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.
Linux
If you are installing the CData ODBC Driver for Jira in a Linux environment, the driver installation predefines a system DSN. You can modify the DSN by editing the system data sources file (/etc/odbc.ini) and defining the required connection properties.
/etc/odbc.ini
[CData JIRA Sys]
Driver = CData ODBC Driver for Jira
Description = My Description
User = admin
Password = 123abc
Url = https://yoursitename.atlassian.net
For specific information on using these configuration files, please refer to the help documentation (installed and found online).
Create a Jira Database Instance in MicroStrategy Developer
You can connect to Jira in MicroStrategy Developer by adding a database instance based on the CData ODBC Driver for Jira.*
- Open MicroStrategy Developer and select a Project Source.
- Navigate to Administration -> Configuration Managers -> Database Instances and right-click to add a new instance.
- Name the instance, select Generic DBMS as the database connection type, and create a new database connection.
- In the database connection wizard, name the connection and create a new Database Login name, using filler values for the user and password.
- Select the DSN that you configured earlier as the ODBC data source (i.e., CData JIRA Sys).
- Select the newly created database connection.
- In the Project Source, right-click the project and open the Project configuration.
- Navigate to Database Instances and select the newly created database instance.
- 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 Jira data from the Warehouse Catalog and Data Import.
Connect to Jira Data from the Warehouse Catalog
Once you have created a database instance based on the ODBC Driver for Jira, you can connect to data from the Warehouse Catalog.
- Select your project and click Schema -> Warehouse Catalog.
- 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 CatalogName NAME_SPACE, TableName TAB_NAME 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
- To retrieve the list of tables, use the following query:
- Select tables to be used in the project.
If you are interested in connecting to Jira from other MicroStrategy products, you can read about connecting from MicroStrategy Web and connecting from MicroStrategy Desktop.
Note: connecting using a ODBC driver requires a 3- or 4-tier architecture.