Automate BigCommerce Data Replication to Azure Data Lake

Always-on applications rely on automatic failover capabilities and real-time data access. CData Sync integrates live BigCommerce data into your Azure Data Lake instance, allowing you to consolidate all of your data into a single location for archiving, reporting, analytics, machine learning, artificial intelligence and more.

Configure Azure Data Lake as a Replication Destination

Using CData Sync, you can replicate BigCommerce data to Azure Data Lake. To add a replication destination, navigate to the Connections tab.

1. Click Add Connection.
2. Select Azure Data Lake as a destination.

3. Enter the necessary connection properties. To connect to Azure Data Lake, set the following properties, depending on your version of Azure Data Lake Storage:

   Azure Data Lake Storage Gen1

   • Generation: Must be set to 1.
   • Account: The name of the Azure Data Lake Store account.
   • Path: The path to store the replicated file (the root directory by default).
   • TenantId: The tenant ID.
   • OAuthClientId: The application ID for the Azure Directory web application (see the CData Sync Help for more information).
   • OAuthClientSecret: The key generated for the Azure Directory web application (see the CData Sync Help for more information).

   Azure Data Lake Storage Gen2

   • Generation: Must be set to 2.
   • Access Key: The access key used to authenticate (see the CData Sync Help for more information).
   • Account: The name of the Azure Data Lake Store account.
   • FileSystem: The file systems used for this account.
   • Path: The path to store the replicated file (the root directory by default).
4. Click Test Connection to ensure that the connection is configured properly.
5. Click Save Changes.

Configure the BigCommerce Connection

You can configure a connection to BigCommerce from the Connections tab. To add a connection to your BigCommerce account, navigate to the Connections tab.

1. Click Add Connection.
2. Select a source (BigCommerce).
3. Configure the connection properties.
   
   

   BigCommerce authentication is based on the standard OAuth flow. To authenticate, you must initially create an app via the Big Commerce developer platform where you can obtain an OAuthClientId, OAuthClientSecret, and CallbackURL. These three parameters will be set as connection properties to your driver.

   Additionally, in order to connect to your BigCommerce Store, you will need your StoreId. To find your Store Id please follow these steps:

   1. Log in to your BigCommerce account.
   2. From the Home Page, select Advanced Settings > API Accounts.
   3. Click Create API Account.
   4. A text box named API Path will appear on your screen.
   5. Inside you can see a URL of the following structure: https://api.bigcommerce.com/stores/{Store Id}/v3.
   6. As demonstrated above, your Store Id will be between the 'stores/' and '/v3' path paramters.
   7. Once you have retrieved your Store Id you can either click Cancel or proceed in creating an API Account in case you do not have one already.
4. Click Connect to ensure that the connection is configured properly.
5. Click Save Changes.

Configure Replication Queries

CData Sync enables you to control replication with a point-and-click interface and with SQL queries. For each replication you wish to configure, navigate to the Jobs tab and click Add Job. Select the Source and Destination for your replication.

Replicate Entire Tables

To replicate an entire table, click Add Tables in the Tables section, choose the table(s) you wish to replicate, and click Add Selected Tables.

Customize Your Replication

You can use the Columns and Query tabs of a task to customize your replication. The Columns tab allows you to specify which columns to replicate, rename the columns at the destination, and even perform operations on the source data before replicating. The Query tab allows you to add filters, grouping, and sorting to the replication.

Schedule Your Replication

In the Schedule section, you can schedule a job to run automatically, configuring the job to run after specified intervals ranging from once every 10 minutes to once every month.

Once you have configured the replication job, click Save Changes. You can configure any number of jobs to manage the replication of your BigCommerce data to PostgreSQL.