Replicate Multiple Bitbucket Accounts

CData Sync is a standalone application designed to support a variety of replication scenarios, such as replicating both sandbox and production instances into your database. It includes a web-based interface that simplifies the management of multiple Bitbucket connections. In this article, we demonstrate how to use the web app to replicate multiple Bitbucket accounts into a single database.

Configure Replication Destinations

Using CData Sync, you can replicate data from Bitbucket to any number of databases, both cloud-based and on-premises. In this example, we use SQLite as the replication destination to demonstrate the process. To add it as a destination, navigate to the Connections tab.

For each destination database:

1. Click Add Connection. 👁 Add a new connection.
   
2. Select the Destinations tab and locate the SQLite connector. 👁 Configure a Destination connection to SQLite.
   
3. Click the Configure Connection icon at the end of that row to open the New Connection page. If the Configure Connection icon is not available, click the Download Connector icon to install the SQLite connector. For more information about installing new connectors, see Connections in the Help documentation.
4. To connect to SQLite, set the following connection properties:
   • Connection Name: Enter a connection name of your choice.
   • Data Source: Enter the path to the database. You can replicate to an existing database or to a new one. The application must have permission to access the database.
👁 Enter the connection details.

5. Once connected, click Create & Test to create, test and save the connection.

You are now connected to SQLite and can use it as both a source and a destination.

NOTE: You can use the Label feature to add a label for a source or a destination.

👁 Add a label.

Configure the Bitbucket Connection

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

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

   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.
   👁 Configuring a Source connection (Salesforce is shown).
   
4. Click Connect to Bitbucket to ensure that the connection is configured properly.
5. Click Save & Test to save the 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.

👁 Select Source and Destination connections for the replication.

Replicate Entire Tables

To replicate an entire table, navigate to the Task tab in the Job, click Add Tasks, choose the table(s) from the list of Bitbucket tables you wish to replicate into SQLite, and click Add Tasks again.

👁 Choose the account table to replicate (Salesforce is shown).

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 with the help of SQL queries. 👁 Configure a replication Transform.

The statement below caches and incrementally updates a table of Bitbucket data:

REPLICATE Issues;

You can specify a file containing the replication queries you want to use to update a particular database. Separate the replication statements with semicolons. The following options are useful when replicating multiple Bitbucket accounts into the same database:

• Use a different table prefix in the REPLICATE SELECT statement:

  REPLICATE PROD_Issues SELECT * FROM Issues;
  

• Alternatively, use a different schema:

  REPLICATE PROD.Issues SELECT * FROM Issues;
  

Schedule Your Replication

Select the Overview tab in the Job, and click Configure under Schedule. You can schedule a job to run automatically by configuring it to run at specified intervals, ranging from once every 10 minutes to once every month.

👁 Schedule your job to run automatically.

Once you have configured the replication job, click Save Changes. You can configure any number of jobs to manage the replication of your Bitbucket data to disparate on-premises, cloud-based, and other databases.

Run the Replication Job

Once all the required configurations are made for the job, select the Bitbucket table you wish to replicate and click Run. After the replication completes successfully, a notification appears, showing the time taken to run the job and the number of rows replicated.

👁 Run the job.

Free Trial & More Information

Now that you've seen how to replicate and configure multiple jobs to manage the replication of your Bitbucket data to various on-premises, cloud-based, and other databases, visit our CData Sync page to learn more and download a free 30-day trial. Start consolidating your enterprise data today!

As always, our world-class Support Team is ready to answer any questions you may have.