docs.intersystems.com
Home  /  Application Development: Language Bindings and Gateways  /  Using Java with the InterSystems JDBC Driver  /  InterSystems Java Connectivity Options


Using Java with the InterSystems JDBC Driver
InterSystems Java Connectivity Options
[Back]  [Next] 
InterSystems: The power behind what matters   
Search:  


The InterSystems JDBC driver is at the core of all InterSystems IRIS™ Java solutions. It is a powerful Type 4 (pure Java) fully compliant implementation of the JDBC API, closely coupled to InterSystems IRIS for maximum speed and efficiency. The driver also underpins many other Java connectivity options:
Core Data Access APIs
The InterSystems JDBC driver supports three lightweight Java APIs that provide direct access to InterSystems IRIS databases via relational tables, objects, or multidimensional storage.
Important:
The Core Data Access APIs form an integrated suite of utilities that all share the same underlying JDBC connection context. All three can be used together, sharing the same databases, sessions, and transactions. Your application can use any combination of desired features from any part of the suite.
JDBC API for relational table access
The standard JDBC API provides SQL based access to relational tables. It supports the following features:
Detailed information is provided in later chapters of this book.
XEP API for object access
The XEP API is designed for extremely fast acquisition of data objects in real time, and can also be used as a convenient general purpose ORM interface. It supports the following features:
See Persisting Java Objects with InterSystems XEP for details.
Native API for multidimensional storage access
The Native API provides direct access to the tree-based sparse arrays (known as globals) of the InterSystems multidimensional storage model. It supports the following features:
See Using the Native API for Java for details.
Third Party Framework Support
Java frameworks such as Spark and Hibernate use JDBC to interact with databases, and include interfaces that can be implemented to take advantage of features unique to a specific database. The InterSystems IRIS Data Platform provides implementations of the Spark Data Source interface and the Hibernate Dialect interface.
Spark Data Source API
The InterSystems Spark Connector is an implementation of the Data Source API for Apache Spark. It is a plug-compatible replacement for the standard Spark jdbc data source, allowing the Spark data processing engine to make optimal use of the InterSystems IRIS Data Platform and its distributed data capabilities
See Using the InterSystems Spark Connector for details.
Hibernate Dialect
The InterSystems Hibernate Dialect is a fully compliant implementation of the Hibernate dialect interface, providing a customized interface between Hibernate and InterSystems IRIS. Like most major dialect implementations, it is included as part of the Hibernate distribution.
See the Hibernate Support chapter in the Implementation Reference for Java Third Party APIs for details.
InterSystems Gateways for Java
InterSystems Gateways are ObjectScript APIs that allow you to create custom interfaces between InterSystems IRIS and external databases or Java applications.
Object Gateway for Java
The Object Gateway provides an easy way access and manipulate Java classes and methods from within InterSystems IRIS. The Gateway allows you to import information from JAR files and create corresponding ObjectScript proxy objects on the server. The proxies can then be used in your ObjectScript applications to instantiate and manipulate the external Java objects as if they were native InterSystems IRIS objects.
See Using the Java Object Gateway for details.
SQL Gateway for Java
The InterSystems SQL Gateway connects InterSystems IRIS to external databases via JDBC. Various wizards can be used to create links to tables, views, or stored procedures in external sources. This allows you to read and store data in the external database just as you would on InterSystems IRIS, using objects and/or SQL queries. You even can generate class methods that perform the same actions as corresponding external stored procedures.
See Using the SQL Gateway for details.
Gateway applications are written in ObjectScript and run on the server. Both gateways can also use ODBC as an alternate connectivity option (providing access to .NET objects and ADO) without any major changes in your ObjectScript code. The Gateway books provide information on both JDBC and ODBC options.