Integrate your user, device and group data with our xMatters EPIC (Export Plus Import Controller) synchronization utility. EPIC supports extracting information from your employee record systems and synchronizing it with xMatters.
EPIC Client versions
As of version 5.5.264, the CloudSync feature is no longer available in the EPIC client. It was intended only for premises deployments and is no longer required.
Versions 5.5.77 and lower of the EPIC client are not supported and will not connect to xMatters.
For more information, refer to the following articles, or contact xMatters Support:
To upgrade your EPIC client, download and configure it according to the directions in the EPIC documentation.
Note: Edit the new configuration files instead of copying the old configuration files from your previous installation, because the new configuration files may contain additional properties or different version information.
As of the 5.5.273 release, the EPIC client supports Eclipse Temurin OpenJDK version 8 (previously distributed as AdoptOpenJDK).
Note: 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 the EPIC client from a previous version.
The EPIC client also supports Java 8.
The EPIC client has been tested using the Oracle JVM with different Windows, OSX, and Linux environments.
The EPIC documentation is available online.
EPIC Client - 5.5.288
Supports Eclipse Temurin OpenJDK (version 8) and Java 8
Download (118 MB)
Added version 5.5.275.1 which includes a hotfix for an issue that was preventing the client from working properly on some Windows machines.
Hi Javier! Let me look into this and get back to you.
Hi Javier! I've confirmed that the EPIC client will not be impacted by the changes to the Oracle JRE in regards to MD5. The jars used by the EPIC client are not signed using MD5, only the download .zip file uses MD5.
Regarding this article by Oracle, will this impact the current version of EPIC (which is MD5 signed) and if so will there be new EPIC versions made available before the date specified?