Model Context Protocol (MCP) finally gives AI models a way to access the business data needed to make them really useful at work. CData MCP Servers have the depth and performance to make sure AI has access to all of the answers.
Try them now for free →Replicate Elasticsearch Data in Heroku for Use in Salesforce Connect
Replicate Elasticsearch data to a PostgreSQL database on Heroku and connect it to Salesforce using Salesforce Connect.
CData Sync is a standalone application that supports a wide range of replication scenarios, including replicating both sandbox and production instances into your database. By replicating Elasticsearch data to a PostgreSQL database in Heroku, you can access Elasticsearch external objects (via Salesforce Connect) alongside standard Salesforce objects.
About Elasticsearch Data Integration
Accessing and integrating live data from Elasticsearch has never been easier with CData. Customers rely on CData connectivity to:
- Access both the SQL endpoints and REST endpoints, optimizing connectivity and offering more options when it comes to reading and writing Elasticsearch data.
- Connect to virtually every Elasticsearch instance starting with v2.2 and Open Source Elasticsearch subscriptions.
- Always receive a relevance score for the query results without explicitly requiring the SCORE() function, simplifying access from 3rd party tools and easily seeing how the query results rank in text relevance.
- Search through multiple indices, relying on Elasticsearch to manage and process the query and results instead of the client machine.
Users frequently integrate Elasticsearch data with analytics tools such as Crystal Reports, Power BI, and Excel, and leverage our tools to enable a single, federated access layer to all of their data sources, including Elasticsearch.
For more information on CData's Elasticsearch solutions, check out our Knowledge Base article: CData Elasticsearch Driver Features & Differentiators.
Getting Started
Requirements
For this replication example, you need the following:
- CData Sync (trial or licensed), along with a license (full or trial) for Elasticsearch replication.
- A Heroku app with the Heroku Postgres and Heroku Connect add-ons provisioned.
- A Salesforce account.
Configure the Replication Destination
Using CData Sync, you can easily replicate data from Elasticsearch data to a PostgreSQL database on Heroku. For this article, you will need an existing PostgreSQL database on Heroku. To add your PostgreSQL database as a replication destination, navigate to the Connections tab.
- Click Add Connection.
- Select the Destinations tab and locate the PostgreSQL connector.
- 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 PostgreSQL connector. For more information about installing new connectors, see Connections in the Help documentation.
- To connect to PostgreSQL, set the following connection properties:
- Connection Name: Enter a connection name of your choice for the PostgreSQL connection.
- Server: Enter the host name or IP of the server that hosts the PostgreSQL database. The default server value is localhost.
- Auth Scheme: Select the authentication scheme. The default auth scheme is Password.
- Port: Enter the port number of the server that hosts the PostgreSQL database. The default port value is 5432.
- User: Enter the user ID provided for authentication with the PostgreSQL database.
- Password: Enter the password provided for authentication with the PostgreSQL database.
- Database: Enter the name of the database. If not specified, use the default database.
- Once connected, click Create & Test to create, test and save the connection.

You are now connected to PostgreSQL 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.

Configure the Elasticsearch Connection
You can configure a connection to Elasticsearch from the Connections tab. To add a connection to your Elasticsearch account, navigate to the Connections tab.
- Click Add Connection.
- Select a source (Elasticsearch).
- Configure the connection properties.
Set the Server and Port connection properties to connect. To authenticate, set the User and Password properties, PKI (public key infrastructure) properties, or both. To use PKI, set the SSLClientCert, SSLClientCertType, SSLClientCertSubject, and SSLClientCertPassword properties.
The data provider uses X-Pack Security for TLS/SSL and authentication. To connect over TLS/SSL, prefix the Server value with 'https://'. Note: TLS/SSL and client authentication must be enabled on X-Pack to use PKI.
Once the data provider is connected, X-Pack will then perform user authentication and grant role permissions based on the realms you have configured.
- Click Connect to Elasticsearch to ensure that the connection is configured properly.
- Click Save & Test to save the changes.
Configure Queries for Each Elasticsearch Instance
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, navigate to the Task tab in the Job, click Add Tasks, choose the table(s) from the list of Elasticsearch tables you wish to replicate into PostgreSQL, and click Add Tasks again.

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.

As you make changes using the interface, the SQL query used for the replication changes, going from something simple, like this:
REPLICATE [Orders]
to something customized and more complex, like this:
REPLICATE [Orders] SELECT [OrderName], [Freight] FROM [Orders] WHERE [ShipCity] = New York
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.

Once you have configured the replication job, click Save Changes. You can configure any number of jobs to manage the replication of your Elasticsearch data to PostgreSQL.
Run the Replication Job
Once all the required configurations are made for the job, select the Elasticsearch 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.

The Elasticsearch data tables are now replicated in Heroku PostgreSQL database.
Connect to Your Replicated Elasticsearch Data as an External Data Source
Once your Elasticsearch data is replicated to the PostgreSQL database on Heroku, configure the OData interface for Heroku and connect to the database as an external data source via Salesforce Connect.
Configure the OData Service for Heroku
The first part of connecting to Elasticsearch data replicated to a PostgreSQL database on Heroku is configuring the Heroku External Objects for the database.
- In your Heroku dashboard, click the Heroku Connect Add-On.
- Select External Objects. (If this is the first time using Heroku External Object, you will be prompted to create the OData service's login credentials)
- View the OData service URL and credentials (noting the URL and credentials to be used later from Salesforce Connect).
- In Data Sources, select which replicated tables to share.

Refer to the Heroku documentation for more detailed instructions.
Configure an External Data Source in Salesforce
After the OData service for Heroku is configured, we can connect to the replicated Elasticsearch data as an external data source from Salesforce Connect.
- In Salesforce, click Setup
- In the Administration section, click Data -> External Data Sources
- Set the data source parameter properties:
- External Data Source: the name you wish to display in the Salesforce user interface
- Name: a unique identifier for the API
- Type: Salesforce Connect: OData 4.0
- URL: Enter the OData endpoint from Heroku Connect (above)
- Format: JSON
- Set Authentication:
- Identity Type: Named Principal
- Authentication Protocol: Password Authentication
- Username: the Heroku Connect username
- Password: the Heroku Connect password
- Click Save.

Synchronize Elasticsearch Objects
After you have created the external data source in Salesforce, follow the steps below to create Elasticsearch external objects that reflect any changes in the data source. You will synchronize the definitions for the Elasticsearch external objects with the definitions for Elasticsearch tables.
- Click the link for the external data source you created.
- Click Validate and Sync.
- Select the Elasticsearch tables you want to work with as external objects and click Sync.

Access Elasticsearch Data as Salesforce Objects
At this point, you will be able to connect to and work with your replicated Elasticsearch entities as external objects just as you would with standard Salesforce objects, whether you are simply viewing the data or building related lists of external Elasticsearch data alongside standard Salesforce objects.
Download a 30-day free trial of CData Sync and replicate your Elasticsearch data for use with Salesforce Connect today!