Skip to main content


To enable Java developers to leverage the scalability, connectivity, and reliability of the HealthShare® Health Connect, Health Connect supports several types of connections to and from Java applications.

Get acquainted

InterSystems Java Connectivity Options

Java IDEs

Using Java with InterSystems Software

Try it

Java Quick Start

Experience Java and InterSystems IRIS

Designing a Java Connection Strategy

Connect a Java application to InterSystems IRIS

JDBC API for relational access

The JDBC (Java Database Connectivity) API enables you to perform operations on HealthShare® Health Connect data using SQL.

Health Connect includes a high-performance Type 4 JDBC database driver that complies with the JDBC 4.2 specification. The driver accepts the following connection URL (or connection string):


where the variables represent the Health Connect instance host’s IP address, the instance’s superserver port, and a namespace on the instance

Using JDBC with InterSystems IRIS

First Look: JDBC and InterSystems Databases

Using the JDBC Driver

JDBC API Reference

JDBC documentation

XEP API for high-speed object access

The XEP (Express Event Persistence) API provided by InterSystems enables Java applications to store and retrieve objects that adhere to simple or moderately complex schemas from HealthShare® Health Connect. More specifically, XEP projects Java objects as persistent events, which are persistent database objects that store the state of Java objects.

XEP is optimized for applications that must handle high throughput, such as transaction processing applications.If you use XEP for object persistence, you can avoid the overheard of object-relational mapping.

First Look: XEP Object Persistence with InterSystems IRIS

Using XEP with Java Applications

Persisting Java Objects with InterSystems XEP

Java XEP API Reference

Native API for direct access to data

The Native API for Java provides direct access to globals, the tree-based sparse arrays that form the basis of the InterSystems multidimensional storage model and underlie the HealthShare® Health Connect object and SQL interfaces. The Native API exposes these native data structures, which provide very fast, flexible storage and retrieval. The Native API also enables your Java application to work with Health Connect objects as easily as if they were native Java objects, and includes the ability to call Health Connect class methods and routines.

Using the Native API for Java

First Look: InterSystems Native API for Java

Using the InterSystems Native API for Java

Native APIs

Hibernate API for complex object data models

The Hibernate API is a third-party tool that maps complex Java data classes to HealthShare® Health Connect. Health Connect includes a Hibernate dialect.

Using Hibernate with InterSystems IRIS

Hibernate Support

Connect InterSystems IRIS to an external application

Using the Java Gateway

For instantiating external Java objects and manipulating them like native objects in Health Connect

Using the InterSystems SQL Gateway

For connecting to external databases via JDBC

Using the InterSystems Spark Connector

For using Health Connect as an Apache Spark data source

Explore more

First Look: The Java Gateway and InterSystems Products

Stock Trading with Java

Using a Java Shared Memory Connection

InterSystems Developer Community