Upgrading the EPIC client from a previous version

To see whether you need to update the EPIC client, compare the version of your EPIC client to the most recent version.

• To view the most recent version of the EPIC client, go to the EPIC client download page at support.xmatters.com.
• To verify the version of the EPIC client running on your system, navigate to the EPIC client installation folder and open the /log/epic.log file. The first line of this file indicates the version number of your EPIC client; for example:

... INFO - E.P.I.C. Control Client 5.5.297 r##### ...

If you are not using the most recent version of the EPIC client, proceed with these upgrade instructions.

The latest version of the EPIC client is configured to work with OpenJDK 17, which must be installed on the system that hosts the EPIC client. If this system also hosts other tools, such as Pentaho ETL, you should ensure that they are compatible with AdoptOpenJDK or move them to another system before upgrading your Java environment.

Note: The EPIC Client version 5.5.297 also supports Oracle's Java 17. If you have already installed a version of the EPIC client with Java 17, you do not need to install AdoptOpenJDK.

To install OpenJDK 17:

1. Stop any active EPIC process and pause any scheduled jobs that may cause EPIC processes to start.
2. Download OpenJDK 17 from AdopOpenJDK install it according to the instructions.
   • Don't forget that 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.
3. Resume any paused jobs or processes.

Patching an EPIC client requires overwriting your existing EPIC client files with the new EPIC client files. The EPIC client does not include an installer.

It is recommended to complete these steps on a non-production or staging environment before upgrading your production deployment.

1. Back up the current EPIC client: Create a backup copy of the existing EPIC client installation directory and store it in a safe location. You may also want to create backup copies of any scripts you use to launch the EPIC synchronization process. This ensures that you can restore the original EPIC client if you encounter complications while configuring the new one.
2. Stop EPIC processes: Ensure that there are no EPIC processes currently running, and that there are no scheduled jobs that might start an EPIC process while you are applying the upgrade.
3. Download and extract the EPIC client:  You can download the EPIC client (epic-client-5.5.297.zip) from support.xmatters.com. Once downloaded, extract it to a new location on your system.
4. Configure the settings files: Configure the new EPIC client to use the same settings as the previous version. To do this, open the config/transport.properties file in the original EPIC client and copy the settings to the same file in the new EPIC client:
5. Copy any other customized configuration files or backups from the old installation folder into the matching location in the new installation folder.
6. Deploy the new EPIC client: Now that the new EPIC client is configured, you can deploy it by using one of the following methods:
   • Overwrite the original EPIC client files with the new EPIC client files.
   • Configure scripts to point to the new EPIC installation directory.
7. Test the installation: Run any script or scheduled job that starts the EPIC synchronization process. You can then view the version of the EPIC client in the log file located in the /log/epic.log file of the EPIC installation directory.
   The log message that contains the EPIC client version should look something like this:
   2016-11-03 16:18:28,214 20327 [main] com.xmatters.epic.client.Main INFO - E.P.I.C. Control Client 5.5.297 r10436
8. Re-enable scheduled jobs: Once you have confirmed that the EPIC client is working properly, you can re-enable any paused scheduled jobs.