Ready to get started?

Download a free trial of the Bitbucket ODBC Driver to get started:

 Download Now

Learn more:

Bitbucket Icon Bitbucket ODBC Driver

The Bitbucket ODBC Driver is a powerful tool that allows you to connect with live data from Bitbucket, directly from any applications that support ODBC connectivity.

Access Bitbucket data like you would a database - read, write, and update Bitbucket 0, etc. through a standard ODBC Driver interface.

Use the CData ODBC Driver for Bitbucket in MicroStrategy Web



Connect to Bitbucket data in MicroStrategy Web 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 adding Bitbucket as external data in MicroStrategy Web and creating a simple visualization of 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:

  1. Go to Settings (the gear icon) and select Workspace Settings.
  2. In the Apps and Features section, select OAuth Consumers.
  3. Click Add Consumer.
  4. Enter a name and description for your custom application.
  5. 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.
  6. 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.
  7. Select which permissions to give your OAuth application. These determine what data you can read and write with it.
  8. To save the new custom application, click Save.
  9. 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).

Connect to and Visualize Bitbucket Data using MicroStrategy Web

Once you have created a database instance in MicroStrategy Developer and connected it to a project, you can perform a data import of Bitbucket data from MicroStrategy Web. Alternatively, you can create a new data source based on the ODBC Driver.*

  1. Open MicroStrategy Web and select your project.
  2. Click Add External Data, select Databases, and choose Select a Table as the Import Option.
  3. In the Import from Tables wizard, click to add a new data source.
    • Select DSN Data Sources
    • Set the DSN property to the previously configured DSN (CData Bitbucket Sys)
    • Set the Version property to Generic DBMS
    • Set the User and Password properties (or use filler values)
    • Set the Data Source Name
  4. After creating the data source, click to edit the catalog options and set the following queries and click OK.
    • SQL statement to retrieve tables available in the data source
      SELECT
        CatalogName NAME_SPACE,
        TableName TAB_NAME
      FROM
        SYS_TABLES
          
    • SQL statement to retrieve columns for the selected tables
      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
          
  5. Drag a table into the pane. Note: Since we create a live connection, we can import whole tables and utilize the filtering and aggregation features native to the MicroStrategy products.
  6. Click Finish, choose to the option to connect live, save the query, and choose the option to create a new dossier.
  7. Choose a visualization, choose fields to display, and apply any filters to create a new visualization of Bitbucket data. Data types are discovered automatically through dynamic metadata discovery. Where possible, the complex queries generated by the filters and aggregations will be pushed down to Bitbucket, while any unsupported operations (which can include SQL functions and JOIN operations) will be managed client-side by the CData SQL engine embedded in the driver.
  8. Once you have finished configuring the dossier, click File -> Save.

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


Note: connecting using a ODBC driver requires a 3- or 4-tier architecture.