Ready to get started?

Learn more about CData Connect Cloud or sign up for free trial access:

Free Trial

Analyze Azure Data Lake Storage Data in Infragistics Reveal



Use CData Connect Cloud to create on OData API on top of Azure Data Lake Storage data and visualize live Azure Data Lake Storage data in Infragistics Reveal.

Reveal, an offering from Infragistics, serves as a data visualization tool that seamlessly integrates with CData Connect Cloud. Together, they empower users to deliver dynamic dashboards using real-time data from a diverse range of data sources, including Azure Data Lake Storage data. In this article, we will guide you through the process of connecting to Azure Data Lake Storage via Connect Cloud and subsequently linking Connect Cloud with Infragistics Reveal to construct a straightforward dashboard.

Connect to Azure Data Lake Storage from Infragistics Reveal

To work with live Azure Data Lake Storage data in Infragistics Reveal, we need to connect to Azure Data Lake Storage from Connect Cloud, provide user access to the connection, and create OData endpoints for the Azure Data Lake Storage data.

(Optional) Add a New Connect Cloud User

As needed, create Users to connect to Azure Data Lake Storage through Connect Cloud.

  1. Navigate to the Users page and click Invite Users
  2. Enter the new user's email address and click Send to invite the user
  3. You can review and edit users from the Users page

Add a Personal Access Token

If you are connecting from a service, application, platform, or framework that does not support OAuth authentication, you can create a Personal Access Token (PAT) to use for authentication. Best practices would dictate that you create a separate PAT for each service, to maintain granularity of access.

  1. Click on your username at the top right of the Connect Cloud app and click User Profile.
  2. Oa the User Profile page, scroll down to the Personal Access Tokens section and click Create PAT.
  3. Give your PAT a name and click Create.
  4. The personal access token is only visible at creation, so be sure to copy it and store it securely for future use.

Connect to Azure Data Lake Storage from Connect Cloud

CData Connect Cloud uses a straightforward, point-and-click interface to connect to data sources.

  1. Log into Connect Cloud, click Connections and click Add Connection
  2. Select "Azure Data Lake Storage" from the Add Connection panel
  3. Enter the necessary authentication properties to connect to Azure Data Lake Storage.

    Authenticating to a Gen 1 DataLakeStore Account

    Gen 1 uses OAuth 2.0 in Azure AD for authentication.

    For this, an Active Directory web application is required. You can create one as follows:

    1. Sign in to your Azure Account through the .
    2. Select "Azure Active Directory".
    3. Select "App registrations".
    4. Select "New application registration".
    5. Provide a name and URL for the application. Select Web app for the type of application you want to create.
    6. Select "Required permissions" and change the required permissions for this app. At a minimum, "Azure Data Lake" and "Windows Azure Service Management API" are required.
    7. Select "Key" and generate a new key. Add a description, a duration, and take note of the generated key. You won't be able to see it again.

    To authenticate against a Gen 1 DataLakeStore account, the following properties are required:

    • Schema: Set this to ADLSGen1.
    • Account: Set this to the name of the account.
    • OAuthClientId: Set this to the application Id of the app you created.
    • OAuthClientSecret: Set this to the key generated for the app you created.
    • TenantId: Set this to the tenant Id. See the property for more information on how to acquire this.
    • Directory: Set this to the path which will be used to store the replicated file. If not specified, the root directory will be used.

    Authenticating to a Gen 2 DataLakeStore Account

    To authenticate against a Gen 2 DataLakeStore account, the following properties are required:

    • Schema: Set this to ADLSGen2.
    • Account: Set this to the name of the account.
    • FileSystem: Set this to the file system which will be used for this account.
    • AccessKey: Set this to the access key which will be used to authenticate the calls to the API. See the property for more information on how to acquire this.
    • Directory: Set this to the path which will be used to store the replicated file. If not specified, the root directory will be used.
  4. Click Create & Test
  5. Navigate to the Permissions tab in the Add Azure Data Lake Storage Connection page and update the User-based permissions.

Add Azure Data Lake Storage OData Endpoints in Connect Cloud

After connecting to Azure Data Lake Storage, create OData Endpoints for the desired table(s).

  1. Navigate to the OData page and click Add to create new OData endpoints
  2. Select the Azure Data Lake Storage connection (e.g. ADLS1) and click Next
  3. Select the table(s) you wish to work with and click Confirm

With the connection and OData endpoints configured, you are ready to connect to Azure Data Lake Storage data from Infragistics Reveal.

Create a Dashboard in Reveal

With Connect Cloud configured, we can visualize Azure Data Lake Storage data in Reveal.

  1. Log into Reveal and click Dashboards -> New
  2. Click Data Sources -> OData Feed
  3. Specify the Connect Cloud OData API endpoint URL (found on the OData page): https://cloud.cdata.com/api/odata/service
  4. Select Generic Credentials and
    • Set Username to a Connect Cloud username (e.g. user@mydomain.com)
    • Set Password to the PAT for the user
  5. Select the entity you wish to visualize
  6. Select fields and choose a chart type

More Information & Free Trial

At this point, you have created a simple dashboard from live Azure Data Lake Storage data. For more information on creating OData feeds from Azure Data Lake Storage (and more than 100 other sources), visit the Connect Cloud page. Sign up for a free trial and start working live Azure Data Lake Storage data in tools that consume OData APIs.