Discover how a bimodal integration strategy can address the major data management challenges facing your organization today.
Get the Report →Connect to Elasticsearch from a Connection Pool in WebLogic
Use the CData JDBC Driver for Elasticsearch to connect to Elasticsearch data from Web applications running on WebLogic.
The CData JDBC Driver for Elasticsearch enables you to follow standard procedures to integrate Elasticsearch data into Java Web applications. This article shows how to deploy the CData JDBC Driver for Elasticsearch in WebLogic Server.
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
Deploy the JDBC Driver in WebLogic Server
To deploy the driver, add the driver JAR to your classpath. The .lic file must be located in the same folder as the JAR. These files are located in the lib subfolder of the installation directory.
If you want to add the driver to all domains, prepend the path to the JAR to the WEBLOGIC_CLASSPATH environment variable in WL_HOME\common\bin\commEnv.cmd/sh. This script is located in WL_HOME\common\bin\. For example:
set WEBLOGIC_CLASSPATH=your-installation-directory\lib\cdata.jdbc.elasticsearch.jar;%WEBLOGIC_CLASSPATH%
In WebLogic 12.2.1 if you want to add the driver to a specific domain, you can simply place the driver JAR and .lic file into DOMAIN_HOME\lib; for example, ORACLE_HOME\user_projects\domains\MY_DOMAIN\lib. These files will be added to the server classpath at startup.
Earlier versions require that you manually add the driver to the classpath: Prepend the following to the PRE_CLASSPATH environment variable in setDomainEnv.cmd/sh. This script is located in the bin subfolder of the folder for that domain.
set PRE_CLASSPATH=your-installation-directory\lib\cdata.jdbc.elasticsearch.jar;%PRE_CLASSPATH%
After making these changes, restart the server.
Create a JDBC Data Source for Elasticsearch
After deploying the driver, log into the WebLogic Administration Console and create the connection.
- In the Domain Structure tree, click Services -> Data Sources -> New -> Generic Data Source.
-
On the JDBC Data Source Properties page, enter the following information:
- Name: Enter a user-friendly name; for example, elasticsearchjdbc.
- JNDI Name: Enter the path the JDBC data source will be bound to; for example, jdbc/Elasticsearch.
Database Type: Select Other.
-
Click Next to use the default options. On the last page, enter the following information and click Test Configuration:
- Driver Class Name: Enter the driver class, cdata.jdbc.elasticsearch.ElasticsearchDriver.
URL: Enter the JDBC URL. A typical JDBC URL is below:
jdbc:elasticsearch:Server=127.0.0.1;Port=9200;User=admin;Password=123456;
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.
Built-in Connection String Designer
For assistance in constructing the JDBC URL, use the connection string designer built into the Elasticsearch JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.
java -jar cdata.jdbc.elasticsearch.jar
Fill in the connection properties and copy the connection string to the clipboard.
- Database User Name: Enter the username, if not specified in the JDBC URL.
- Password: Enter the password, if not specified in the JDBC URL.
After selecting the server where you want to deploy the JDBC data source, you can now connect to Elasticsearch data.
More WebLogic Integration
The steps above show how configure the driver in a simple connection pooling scenario. For more use cases and information, see the JDBC sections in the WebLogic Data Sources chapter of the Oracle Fusion Middleware documentation.