EPIC client system requirements

This section describes the system requirements for running the EPIC client.

Proxy server support

EPIC synchronization can be run through a proxy server. The following table summarizes deployments known to be successful in the lab or field:

Proxy Server Working Deployment
Apache 2.2.3 xMatters Test Lab
Blue Coat 5 Field (production)
NTLM xMatters Test Lab


The EPIC client requires Java 17 or Eclipse Temurin OpenJDK version 17 (previously distributed as AdoptOpenJDK). The location of the Java Development Kit (JDK) or Java Runtime Environment (JRE) must be defined by the JAVA_HOME system variable or included directly on the system PATH.

Other tools (such as Pentaho ETL) may have their own Java requirements. Before running these tools on the same system as the EPIC client, verify that they use a compatible version of Java.

Versions of the EPIC client prior to 5.5.273 are not compatible with OpenJDK. If you are running an older version of the EPIC client and want to use OpenJDK, you must upgrade the EPIC client. For more information about upgrading your EPIC client, see Upgrading to a new version of the EPIC client.

You can download and install the OpenJDK version 17 here. https://adoptium.net/temurin

Operating systems

The EPIC client has been tested using the Oracle JVM with different Windows, OSX, and Linux environments.

System memory

The EPIC client validates data in-memory before it begins the data synchronization process. The amount of memory required to perform this validation depends on the amount of data that is being synchronized to xMatters. The EPIC client requires four Megabytes of memory to validate one Megabyte of uncompressed data. (This ratio is approximate and depends on the properties of the uncompressed data.)

To calculate the amount of memory that EPIC requires, multiply the size of the uncompressed (unzipped) data by four. To do this for ZipSync mode, unzip the ZipSync input file, calculate the total size of the CSV files, and multiply this value by four. For example, if your ZipSync input file is 6.6 Megabytes, and the combined size of the unzipped CSV files is 78.5 Megabytes, the EPIC client requires approximately 314 Megabytes of RAM.

The EPIC client sets the Java Virtual Machine (JVM) to use a maximum of 800 Megabytes of memory. If this limit is exceeded, or if your system runs out of memory, the EPIC client fails and your data is not synchronized to xMatters. If required, you can increase the amount of memory that is available to the JVM. To do this, edit the epic file (Mac/Linux) or epic.bat file (Windows) and modify the value of DEFAULT_JVM_OPTS. For more information about configuring JVM memory usage, refer to the Java documentation.