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 Bitbucket in MicroStrategy
Connect to Bitbucket data in MicroStrategy Developer using the CData ODBC Driver for Bitbucket.
MicroStrategy is an analytics and mobility platform that enables data-driven innovation. When you pair MicroStrategy with the CData ODBC Driver for Bitbucket, you gain database-like access to live Bitbucket data from MicroStrategy, expanding your reporting and analytics capabilities. In this article, we walk through creating a database instance for Bitbucket in MicroStrategy Developer and creating a Warehouse Catalog based on Bitbucket data.
The CData ODBC Driver offers unmatched performance for interacting with live Bitbucket data in MicroStrategy due to optimized data processing built into the driver. When you issue complex SQL queries from MicroStrategy to Bitbucket, the driver pushes supported SQL operations, like filters and aggregations, directly to Bitbucket 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 Bitbucket data using native MicroStrategy data types.
Connect to Bitbucket as an ODBC Data Source
Information for connecting to Bitbucket follows, along with different instructions for configuring a DSN in Windows and Linux environments (the ODBC Driver for Bitbucket must be installed on the machine hosting the connected MicroStrategy Intelligence Server).
For most queries, you must set the Workspace. The only exception to this is the Workspaces table, which does not require this property to be set, as querying it provides a list of workspace slugs that can be used to set Workspace. To query this table, you must set Schema to 'Information' and execute the query SELECT * FROM Workspaces>.
Setting Schema to 'Information' displays general information. To connect to Bitbucket, set these parameters:
- Schema: To show general information about a workspace, such as its users, repositories, and projects, set this to Information. Otherwise, set this to the schema of the repository or project you are querying. To get a full set of available schemas, query the sys_schemas table.
- Workspace: Required if you are not querying the Workspaces table. This property is not required for querying the Workspaces table, as that query only returns a list of workspace slugs that can be used to set Workspace.
Authenticating to Bitbucket
Bitbucket supports OAuth authentication only. To enable this authentication from all OAuth flows, you must create a custom OAuth application, and set AuthScheme to OAuth.
Be sure to review the Help documentation for the required connection properties for you specific authentication needs (desktop applications, web applications, and headless machines).
Creating a custom OAuth application
From your Bitbucket account:
- Go to Settings (the gear icon) and select Workspace Settings.
- In the Apps and Features section, select OAuth Consumers.
- Click Add Consumer.
- Enter a name and description for your custom application.
- Set the callback URL:
- For desktop applications and headless machines, use http://localhost:33333 or another port number of your choice. The URI you set here becomes the CallbackURL property.
- For web applications, set the callback URL to a trusted redirect URL. This URL is the web location the user returns to with the token that verifies that your application has been granted access.
- If you plan to use client credentials to authenticate, you must select This is a private consumer. In the driver, you must set AuthScheme to client.
- Select which permissions to give your OAuth application. These determine what data you can read and write with it.
- To save the new custom application, click Save.
- After the application has been saved, you can select it to view its settings. The application's Key and Secret are displayed. Record these for future use. You will use the Key to set the OAuthClientId and the Secret to set the OAuthClientSecret.
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 Bitbucket 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 Bitbucket Sys]
Driver = CData ODBC Driver for Bitbucket
Description = My Description
Workspace = myworkspaceslug
Schema = Information
For specific information on using these configuration files, please refer to the help documentation (installed and found online).
Create a Bitbucket Database Instance in MicroStrategy Developer
You can connect to Bitbucket in MicroStrategy Developer by adding a database instance based on the CData ODBC Driver for Bitbucket.*
- 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 Bitbucket 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.
![The configured database instance.](../articles/odbc-microstrategy-3.png)
With the database instance configured, you will now be able to connect to Bitbucket data from the Warehouse Catalog and Data Import.
Connect to Bitbucket Data from the Warehouse Catalog
Once you have created a database instance based on the ODBC Driver for Bitbucket, 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 Bitbucket 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.