Connect to Azure Data Lake Storage Data in RunMyProcess through Connect Cloud


Use CData Connect Cloud to create on OData API for Azure Data Lake Storage Data and connect to Azure Data Lake Storage data in Akorbi Digital RunMyProcess.

Akorbi Digital RunMyProcess makes it easy to create applications for complex business applications, such as budget application and contract management. CData Connect Cloud creates a live connection to Azure Data Lake Storage and can be used to generate an OData API (natively supported in RunMyProcess) for Azure Data Lake Storage. By pairing RunMyProcess with CData Connect Cloud, you get true cloud-to-cloud connectivity to all your SaaS and cloud-based Big Data and NoSQL sources - no need to migrate your data or write your own integrations. Simply connect to Connect Cloud from RunMyProcess as you would any other REST service and get instant, live access to your Azure Data Lake Storage data.

In this article, we walk through connecting to Azure Data Lake Storage from CData Connect Cloud and accessing Azure Data Lake Storage data through an OData feed in RunMyProcess.

Connect to Azure Data Lake Storage from RunMyProcess

To work with live Azure Data Lake Storage data in RunMyProcess, we need to connect to Azure Data Lake Storage from Connect Cloud, provide user access to the connection, and create a Workspace for the Azure Data Lake Storage data.

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 Sources, and then 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 Entra ID (formerly 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 "Entra ID" (formerly Azure AD).
    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 a Personal Access Token

When connecting to Connect Cloud through the REST API, the OData API, or the Virtual SQL Server, a Personal Access Token (PAT) is used to authenticate the connection to Connect Cloud. It is best practice to create a separate PAT for each service to maintain granularity of access.

  1. Click on the Gear icon () at the top right of the Connect Cloud app to open the settings page.
  2. On the Settings page, go to the Access Tokens section and click Create PAT.
  3. Give the 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.

Configure Azure Data Lake Storage Endpoints for RunMyProcess

After connecting to Azure Data Lake Storage, create a workspace for your desired table(s).

  1. Navigate to the Workspaces page and click Add to create a new Workspace (or select an existing workspace).
  2. Click Add to add new assets to the Workspace.
  3. Select the Azure Data Lake Storage connection (e.g. ADLS1) and click Next.
  4. Select the table(s) you wish to work with and click Confirm.
  5. Make note of the OData Service URL for your workspace, e.g. https://cloud.cdata.com/api/odata/{workspace_name}

With the connection, PAT, and Workspace configured, you are ready to connect to Azure Data Lake Storage data from RunMyProcess.

Retrieve Azure Data Lake Storage Data from RunMyProcess DigitalSuite Studio

With the connection to Azure Data Lake Storage and OData endpoints created, we are ready to add Azure Data Lake Storage data to RunMyProcess for Retrieval.

Create a Provider

  1. Log into RunMyProcess and open DigitalSuite Studio.
  2. Click Resources to bring up the Resources page, then select then the CONNECTORS tab.
  3. Click the + (New Provider) button to create a new provider, choose the account to use, then click Confirm.
  4. In the provider settings page, configure the following properties.
    • URL: Set the OData endpoint in the Connect Cloud OData page: https://cloud.cdata.com/api/odata/{workspace_name}.
    • Authentication Schema: Select Login/Password.
    • Login: Specify a CData Connect Cloud username (e.g. [email protected]).
    • Password: Specify the PAT of the Connect Cloud user.
  5. Fill in the same properties in the ACCEPTANCE and TEST tabs. Note: You can copy the configured settings by clicking 'Copy this configuration button,' then pasting the content in the new tab by clicking 'Paste previously copied configuration.'
  6. Click Save to save the properties.

Retrieve Azure Data Lake Storage Data by Creating a Connector

  1. In the CONNECTORS tab, click the button with three dots to create the provider, then select Add connector from the menu.
  2. In the following page, set Connector URL to the OData endpoint configured in Connect Cloud (e.g. https://cloud.cdata.com/api/odata/{workspace_name})
  3. Click Save then Launch to test the connector execution. Click Launch test to execute. The process is successful if you get the JSON response of your configured table information.

More Information & Free Trial

Now, you have created a provider and connector to retrieve Azure Data Lake Storage data. For more information on creating OData feeds from Azure Data Lake Storage (and more than 100 other data sources), visit the Connect Cloud page. Sign up for a free trial and start working with live Azure Data Lake Storage data in RunMyProcess.

Ready to get started?

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

Free Trial

In this article

Related articles