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 →Connect to MongoDB Data from a Connection Pool in Jetty
The MongoDB JDBC Driver supports connection pooling: This article shows how to connect faster to MongoDB data from Web apps in Jetty.
The CData JDBC driver for MongoDB is easy to integrate with Java Web applications. This article shows how to efficiently connect to MongoDB data in Jetty by configuring the driver for connection pooling. You will configure a JNDI resource for MongoDB in Jetty.
About MongoDB Data Integration
Accessing and integrating live data from MongoDB has never been easier with CData. Customers rely on CData connectivity to:
- Access data from MongoDB 2.6 and above, ensuring broad usability across various MongoDB versions.
- Easily manage unstructured data thanks to flexible NoSQL (learn more here: Leading-Edge Drivers for NoSQL Integration).
- Leverage feature advantages over other NoSQL drivers and realize functional benefits when working with MongoDB data (learn more here: A Feature Comparison of Drivers for NoSQL).
MongoDB's flexibility means that it can be used as a transactional, operational, or analytical database. That means CData customers use our solutions to integrate their business data with MongoDB or integrate their MongoDB data with their data warehouse (or both). Customers also leverage our live connectivity options to analyze and report on MongoDB directly from their preferred tools, like Power BI and Tableau.
For more details on MongoDB use case and how CData enhances your MongoDB experience, check out our blog post: The Top 10 Real-World MongoDB Use Cases You Should Know in 2024.
Getting Started
Configure the JDBC Driver for Salesforce as a JNDI Data Source
Follow the steps below to connect to Salesforce from Jetty.
Enable the JNDI module for your Jetty base. The following command enables JNDI from the command-line:
java -jar ../start.jar --add-to-startd=jndi
- Add the CData and license file, located in the lib subfolder of the installation directory, into the lib subfolder of the context path.
-
Declare the resource and its scope. Enter the required connection properties in the resource declaration. This example declares the MongoDB data source at the level of the Web app, in WEB-INF\jetty-env.xml.
<Configure id='mongodbdemo' class="org.eclipse.jetty.webapp.WebAppContext"> <New id="mongodbdemo" class="org.eclipse.jetty.plus.jndi.Resource"> <Arg><Ref refid="mongodbdemo"/></Arg> <Arg>jdbc/mongodbdb</Arg> <Arg> <New class="cdata.jdbc.mongodb.MongoDBDriver"> <Set name="url">jdbc:mongodb:</Set> <Set name="Server">MyServer</Set> <Set name="Port">27017</Set> <Set name="Database">test</Set> <Set name="User">test</Set> <Set name="Password">Password</Set> </New> </Arg> </New> </Configure>
Set the Server, Database, User, and Password connection properties to connect to MongoDB. To access MongoDB collections as tables you can use automatic schema discovery or write your own schema definitions. Schemas are defined in .rsd files, which have a simple format. You can also execute free-form queries that are not tied to the schema.
-
Configure the resource in the Web.xml:
jdbc/mongodbdb javax.sql.DataSource Container -
You can then access MongoDB with a lookup to java:comp/env/jdbc/mongodbdb:
InitialContext ctx = new InitialContext(); DataSource mymongodb = (DataSource)ctx.lookup("java:comp/env/jdbc/mongodbdb");
More Jetty Integration
The steps above show how to configure the driver in a simple connection pooling scenario. For more use cases and information, see the Working with Jetty JNDI chapter in the Jetty documentation.