Persisting .NET Objects with InterSystems IRIS XEP
XEP is a lightweight API that provides high-performance .NET technology for persisting simple to moderately complex object hierarchies. XEP projects the data in .NET objects as persistent events
(database objects that store a persistent copy of the data fields) in an InterSystems IRIS™ database. XEP is optimized for applications that must acquire and persist data at the highest possible speed.
The following sections provide instructions for including XEP when installing InterSystems IRIS, and for configuring your environment to use the XEP API.
The .NET Framework, version 2.0, 4.0, or 4.5.
Computers that run your .NET client applications do not require InterSystems IRIS, but they must have a connection to the InterSystems IRIS Server and must be running a supported version of the .NET Framework.
If InterSystems IRIS has been installed with security level 2, open the Management Portal and go to [System Administration] > [Security] > [Services]
, select %Service_CallIn
, and make sure the Service Enabled
box is checked.
If you installed InterSystems IRIS with security level 1 (minimal) it should already be checked.
Your .NET project must include references to the following files. Different versions of these files are located in appropriately named subdirectories of <install-dir>/dev/dotnet/bin
(for example, <install-dir>/dev/dotnet/bin/v4.0.30319
contains the file for .NET 4.0). Use the appropriate files for the release that will be used to compile your project:
In order to run XEP applications:
The InterSystems IRIS User
namespace must exist and must be writable.
environment variable must include <install-dir>/bin
. If your PATH
includes multiple instances of <install-dir>/bin
(for example, if you have installed more than one instance of InterSystems IRIS) only the first one will be used, and any others will be ignored.
is a program that runs all of the other sample applications in sequence. Run this application with command line argument -h
for a list of available command line options.
tests basic functionality such as connecting, importing a schema, storing, querying, updating and deleting XEP events. It also exercises most of the supported data types.
is the most basic XEP test program. It connects to the database, imports a simple class containing only one string field, then stores and loads a number of objects corresponding to that class.
is an example that demonstrates the XEP full inheritance model. It tracks airline flight information such as times, locations, personnel, and passengers.
The sample package includes supporting files that provide test data for the applications. See the help files included in the sample package for detailed documentation of these programs.