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 →How to load Oracle Sales data into Elasticsearch via Logstash
Introducing a simple method to load Oracle Sales data using the ETL module Logstash of the full-text search service Elasticsearch and the CData JDBC driver.
Elasticsearch is a popular distributed full-text search engine. By centrally storing data, you can perform ultra-fast searches, fine-tuning relevance, and powerful analytics with ease. Elasticsearch has a pipeline tool for loading data called "Logstash". You can use CData JDBC Drivers to easily import data from any data source into Elasticsearch for search and analysis.
This article explains how to use the CData JDBC Driver for Oracle Sales to load data from Oracle Sales into Elasticsearch via Logstash.
Using CData JDBC Driver for Oracle Sales with Elasticsearch Logstash
- Install the CData JDBC Driver for Oracle Sales on the machine where Logstash is running.
-
The JDBC Driver will be installed at the following path (the year part, e.g. 20XX, will vary depending on the product version you are using). You will use this path later. Place this .jar file (and the .lic file if it's a licensed version) in Logstash.
C:\Program Files\CData\CData JDBC Driver for OracleSalesCloud 20XX\lib\cdata.jdbc.oraclesalescloud.jar
- Next, install the JDBC Input Plugin, which connects Logstash to the CData JDBC driver. The JDBC Plugin comes by default with the latest version of Logstash, but depending on the version, you may need to add it.
https://www.elastic.co/guide/en/logstash/5.4/plugins-inputs-jdbc.html - Move the CData JDBC Driver’s .jar file and .lic file to Logstash's "/logstash-core/lib/jars/".
Sending Oracle Sales data to Elasticsearch with Logstash
Now, let's create a configuration file for Logstash to transfer Oracle Sales data to Elasticsearch.
- Write the process to retrieve Oracle Sales data in the logstash.conf file, which defines data processing in Logstash. The input will be JDBC, and the output will be Elasticsearch. The data loading job is set to run at 30-second intervals.
- Set the CData JDBC Driver's .jar file as the JDBC driver library, configure the class name, and set the connection properties to Oracle Sales in the form of a JDBC URL. The JDBC URL allows detailed configuration, so please refer to the product documentation for more specifics.
- Username: Set this to the user name that you use to log into your Oracle Cloud service.
- Password: Set this to your password.
- HostURL: Set this to the Web address (URL) of your Oracle Cloud service.
Oracle Sales uses Basic authentication over SSL; after setting the following connection properties, you are ready to connect:
Executing data movement with Logstash
Now let's run Logstash using the created "logstash.conf" file.
logstash-7.8.0\bin\logstash -f logstash.conf
A log indicating success will appear. This means the Oracle Sales data has been loaded into Elasticsearch.
For example, let's view the data transferred to Elasticsearch in Kibana.
GET oraclesalescloud_table/_search { "query": { "match_all": {} } }

We have confirmed that the data is stored in Elasticsearch.

By using the CData JDBC Driver for Oracle Sales with Logstash, it functions as a Oracle Sales connector, making it easy to load data into Elasticsearch. Please try the 30-day free trial.