GitHub Reporting and Star Schemas in OBIEE

The CData ODBC Driver for GitHub is a standard database driver that can integrate real-time access to GitHub data into your data warehouse or directly into your reporting tool. This article shows how to bypass the data warehouse and import operational GitHub data into Oracle Business Intelligence Enterprise Edition (OBIEE).

See the knowledge base for ODBC integrations with ETL tools like Informatica PowerCenter. For an ETL solution into Oracle Warehouse Builder, use the driver with the Oracle ODBC Gateway to Access GitHub Data as a Remote Oracle Database.

Connect to GitHub as an ODBC Data Source

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.

GitHub uses the OAuth 2 authentication standard. To authenticate using OAuth, create an app to obtain the OAuthClientId, OAuthClientSecret, and CallbackURL connection properties. See the Getting Started chapter of the CData help documentation for an authentication guide.

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.

Import GitHub Metadata

Follow the steps below to use the OBIEE Client Tools to import GitHub metadata into an OBIEE repository. You can then integrate GitHub data into your business models.

1. Open the Administration Tool and click File -> New Repository.

2. In the Connection Type menu, select ODBC 3.5 and select the CData DSN.
3. Select the metadata types you want to import under the Relational Sources option and then select GitHub tables. 👁 Tables to be imported into the repository. (Salesforce is shown.)
   

You can now create star schemas based on GitHub tables: 👁 Fact and dimension tables. (Salesforce is shown.)