Exchange JDBC Driver

Enterprise-class JDBC Connectivity

The Exchange JDBC Driver offers the most natural way to access Microsoft Exchange data from any Java/J2EE application. Simply use the Exchange Driver to connect and access data just as you would access any traditional database. The drivers is completely self-contained - no additional software installation is required!

• Access Microsoft Exchange data through widely available tools. The JDBC interface offers the greatest accessibility to Microsoft Exchange data from Java based applications and developer technologies.
• Advanced wire-protocol SSL security for remote connectivity.
• Faster application deployment and configuration.

Connect To Microsoft Exchange From BI, ETL, & Reporting Tools

JDBC is the most widely supported interface for connecting Java-based applications with data. All kinds of BI, Reporting, ETL, Database, and Analytics tools offer the ability to read and write data via JDBC connectivity.

• Aqua Data Studio
• Cisco Information Server
• CloverETL
• ColdFusion
• Crystal Reports
• DBeaver
• DbVisualizer
• IBM WebSphere
• Informatica
• IntelliJ
• JBoss
• Jetty
• KNIME
• NetBeans IDE
• Oracle WebLogic
• Oracle WareHouse Builder
• RazorSQL
• ... and many more!

The Exchange Driver wraps the complexity of accessing Microsoft Exchange services in an easy-to-integrate, pure Java JDBC Driver. Applications then access Microsoft Exchange through the Exchange Driver with simple Transact-SQL.

The CData JDBC Driver for Exchange hides the complexity of accessing data and provides additional powerful security features, smart caching, batching, socket management, and more.

Microsoft Exchange Application Integration

The Exchange Driver has the same JDBC architecture as the JDBC drivers for MySQL and OLEDB, including Connection, Statement and ResultSet objects. Because of this you can now access Microsoft Exchange data in an easy, familiar way. You can use the Exchange Driver through popular IDEs (Eclipse, IntelliJ, NetBeans, etc.), in code through familiar classes, and in data controls available through Swing, Eclipse SWT Widgets, etc.

For example:

Connection conn = 
	DriverManager.getConnection("jdbc:microsoftexchange:user=myuseraccount;password=mypassword;");

boolean ret = stat.execute("SELECT * FROM Folders");
ResultSet rs=stat.getResultSet();
while(rs.next()){
  for(int i=1;i<=rs.getMetaData().getColumnCount();i++)
  {
    System.out.println(rs.getMetaData().getColumnName(i) +"="+rs.getString(i));
  }
}

More Than Read-Only: Full Update/CRUD Support

Exchange Driver goes beyond read-only functionality to deliver full support for Create, Read Update, and Delete operations (CRUD). Your end-users can interact with the data presented by the Exchange Driver as easily as interacting with a database table.

Connection conn = 
	DriverManager.getConnection("jdbc:microsoftexchange:user=myuseraccount;password=mypassword;");
	
String query = "UPDATE Folders SET Where= ..."; 

PreparedStatement pstmt = conn.prepareStatement(query);
pstmt.setString(1, "Location");
pstmt.setString(2, "UID");
pstmt.execute();
int count=pstmt.getUpdateCount();

Driver Features

• Pure Java Type 4/5* Drivers: 100% Java architecture based drivers that implement the native protocol without reliance on client-side libraries.
  * Our drivers fit the definition of Type 5 drivers; however, there are only 4 official JDBC Driver types.
• All-in-One Deployment: Single JAR that supports JDBC 3.0 and JDBC 4.0 specification and JVM versions 1.5 and above.
• Certified Compatibility*: Our drivers undergo extensive testing and are certified to be compatible with leading analytics and reporting applications like SAP Crystal Reports, Pentaho, Business Objects, Crystal Reports and many more.
  * Please visit our knowledge base to access how-to articles.
• Developer Friendly: Design-time support for all major Java IDEs, including Eclipse, IntelliJ, and NetBeans.
• JDBC Remoting: Our exclusive remoting feature allows hosting the JDBC connection on a server to enable connections from various clients on any platform (Java, .NET, C++, PHP, Python), using any standards-based technology (ODBC, JDBC, etc.). JDBC Remoting is enabled using the popular MySQL wire protocol server.
• Replication and Caching: Our replication and caching commands make it easy to copy data to local and cloud data stores such as Oracle, SQL Server, Google Cloud SQL, etc. The replication commands include many features that allow for intelligent incremental updates to cached data.
• String, Date, Numeric SQL Functions: The driver includes a library of over 50 functions that can manipulate column values into the desired result. Popular examples include Regex, JSON, and XML processing functions.
• Collaborative Query Processing: Our drivers enhance the data source's capabilities by additional client-side processing, when needed, to enable analytic summaries of data such as SUM, AVG, MAX, MIN, etc.
• Easily Customizable and Configurable: The data model exposed by our JDBC Drivers can easily be customized to add or remove tables/columns, change data types, etc. without requiring a new build. These customizations are supported at runtime using human-readable schema files that are easy to edit.
• Secure Connectivity: Includes standard Enterprise-class security features such as TLS/ SSL data encryption for all client-server communications.

Enterprise-Class Remoting

MySQL/SQL Database entry points for Microsoft Exchange Data

The CData JDBC drivers include powerful fully-integrated remoting capabilities that makes Microsoft Exchange data accessible from virtually anywhere. The drivers include the optional ability to accept incoming SQL and MySQL client connections and service standard database requests.

With the CData JDBC drivers, users can interact with Microsoft Exchange data from any client that supports SQL Server or MySQL: from web & mobile applications, to CRM and CMS systems, BI tools like SQL Server Analysis Services, and even through popular management applications like MySQL Workbench.

• Access Microsoft Exchange data from virtually any application that can access external data. Applications that can access SQL Server or MySQL data can now connect to Microsoft Exchange with this driver.
• Connect Microsoft Exchange data with popular BI tools like SQL Server Analysis Services.
• Enable enterprise Microsoft Exchange data integration through SQL Linked Server connectivity
• Includes support for the MySQL and SQL (TDS) remote access protocols - industry standards for remote database connectivity.
• Offers advanced wire-protocol SSL security for remote connectivity

Connect to Microsoft Exchange Data from Code

The Microsoft Exchange Driver offers a standard SQL Server or MySQL interface to data, with read/write (CRUD) support. This powerful remoting features makes it easy to connect your applications with Microsoft Exchange data regardless of your solution architecture.

Use one of the standard client libraries for accessing SQL/MySQL from .NET, Java, PHP, Python, Ruby, Objective-C, etc. to start your integration with Microsoft Exchange.

JDBC Driver Performance

With traditional approaches to remote access, performance bottlenecks can spell disaster for applications. Regardless if an application is created for internal use, a commercial project, web, or mobile application, slow performance can rapidly lead to project failure. Accessing data from any remote source has the potential to create these problems. Common issues include:

1. Network Connections - Slow network connections and latency issues are common in mobile applications.
2. Service Delays - Delays due to service interruptions, resulting in server hardware or software updates.
3. Large Data - Intentional or unintentional requests for large amounts of data.
4. Disconnects - Complete loss of network connectivity.

The CData JDBC Driver for Exchange solves these issues by supporting powerful smart caching technology that can greatly improve the performance and dramatically reduce application bottlenecks.

Smart Caching

Smart caching is a configurable option that works by storing queried data into a local database. Enabling smart caching creates a persistent local cache database that contains a replica of data retrieved from the remote source. The cache database is small, lightweight, blazing-fast, and it can be shared by multiple connections as persistent storage.

Caching with our JDBC Drivers is highly configurable, including options for:

• Auto Cache - Maintain an automatic local cache of data on all requests. The provider will automatically load data into the cache database each time you execute a SELECT query. Each row returned by the query will be inserted or updated as necessary into the corresponding table in the cache database.
• Explicit Cache - Cache only on demand. Developers decide exactly what data gets stored in the cache and when it is updated. Explicit caching provides full control over the cache contents by using explicit execution of CACHE statements.
• No Cache - All requests access only live data and no local cache file is created.

This powerful caching functionality increases application performance and allows applications to disconnect and continue limited functioning without writing code for additional local storage and/or data serialization/deserialization.

More information about JDBC Driver caching and best caching practices is available in the included help files.

Getting Started with Microsoft Exchange JDBC Driver

Working with the new Exchange JDBC Driver is easy. As a 100% pure Java JDBC Driver, the Exchange Driver integrates seamlessly with popular IDEs like Eclipse, IntelliJ and NetBeans, as well as any Java/J2EE application.

Eclipse Integration - Data Explorer

As a JDBC Driver, Exchange JDBC Driver can be used to access and explore Microsoft Exchange data directly from the Data Source Explorers included in popular java IDEs.