Home  /  Application Development: Language Bindings and Gateways  /  Persisting Java Objects with InterSystems IRIS XEP  /  Introduction

Persisting Java Objects with InterSystems IRIS XEP
[Back]  [Next] 
InterSystems: The power behind what matters   

InterSystems IRIS™ provides Java APIs for easy database access via SQL tables and objects. See Using JDBC with InterSystems IRIS for SQL table access. This book discusses the API for object access.
XEP (eXpress Event Persistence) is a lightweight Java API that provides high-performance Java persistence technology for simple to medium complexity object hierarchies. XEP projects the data in Java objects as persistent events (database objects that store a persistent copy of the data fields), accessing the InterSystems IRIS database over a TCP/IP link. XEP is optimized for transaction processing applications that require extremely high speed data persistence and retrieval.
Installation and Configuration
This section provides specifies requirements and provides instructions for installing InterSystems IRIS and configuring your environment to use XEP.
Required Environment Variables
In order to run XEP applications, the following environment variables must be properly set on all platforms:
Required Files
All XEP applications require JAR files isc-jdbc-3.0.0.jar and isc-xep-3.0.0.jar. There are separate versions of these files for each supported version of Java, located in subdirectories of <install-dir>/dev/java/lib (for example, <install-dir>/dev/java/lib/JDK18 contains the files for Java 1.8).
Your CLASSPATH environment variable must include the full paths to these files. Alternately, they can be specified in the Java command line classpath argument.
Configuration for Windows
Configuration for UNIX® and Related Operating Systems
XEP Sample Applications
XEP sample applications are available from GitHub (see “Downloading Samples from GitHub”). The following sample programs are available:
Supporting files provide test data for the sample programs. See the JavaDoc included in the sample package for detailed documentation of these programs.
Run the samples with command line argument -h for a list of available command line options.