Automated Continuous BambooHR Replication to MongoDB

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

Configure MongoDB as a Replication Destination

Using CData Sync, you can replicate BambooHR data to MongoDB. To add a replication destination, navigate to the Connections tab.

1. Click Add Connection.
2. Select MongoDB as a destination.
3. Enter the necessary connection properties. To connect to MongoDB, set the following:
   • Server: Set this to the name or address of the server where your MongoDB instance is running. You can specify the port here or in Port.
   • Database: Set this to the database you want to read from and write to.

   Connecting to CosmosDB with the MongoDB API

   To obtain the connection string needed to connect to a Cosmos DB account using the MongoDB API, log in to the Azure Portal, select Azure Cosmos DB, and select your account. In the Settings section, click Connection String and set the following values.

   • Server: Set this to the Host value, the FQDN of the server provisioned for your account. You can also specify the port here or in Port.
   • Port: Set this to the port.
   • Database: Set this to the database you want to read from and write to.
   • User: Set this to the database user.
   • Password: Set this to the user's password.

4. Click Test Connection to ensure that the connection is configured properly.
5. Click Save Changes.

Configure the BambooHR Connection

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

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

   Start by setting the Profile connection property to the location of the BambooHR Profile on disk (e.g. C:\profiles\bamboohr.apip). Next, set the ProfileSettings connection property to the connection string for BambooHR (see below).

   BambooHR API Profile Settings

   In order to authenticate to BambooHR, you'll need to provide your API Key. To generate an API key, log in and click your name in the upper right-hand corner of any page to get to the user context menu. If you have sufficient permissions, there will be an "API Keys" option in that menu to go to the page, where you can create a new API Key. Additionally, you will need to set the Domain, found in the domain name of your BambooHR account. For example if your BambooHR account is acmeinc.bamboohr.com, then the Domain should be 'acmeinc'. Set both the API Key and Domain in the ProfileSettings property to connect.

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 BambooHR data to MongoDB.