In order to ensure users to get more stable and secure experience when they use the esProc product lines, we have updated and optimized the Professional / Enterprise / Standard / Desktop esProc installation packages that are downloaded after March 26, 2026. Users can upgrade the esProc JRE based on their security regulations and business requirements under the premise of ensuring environmental compatibility to adapt to personalized usage scenarios.

Here are the specifications about the esProc product’s built-in runtime environment and relevant precautions bout version upgrade:

The built-in version information

The esProc built-in runtime environments for different versions are:

1. Professional Edition/Enterprise Edition: With built-in Tomcat 8.5.23 and JRE 1.8.0;

2. Standard Ediiton/Destop Edition: With built-in JRE 1.8.0.

All the above environments have undergone routine compatibility and stability tests and can meet the requirements of most general business scenarios.

Possible upgrade problems and solutions

Due to compatibility differences caused by component version iterations, the following issues may arise during upgrade to a higher version. Solutions are listed below:

• Maybe the higher version JDK does not support the ODBC data source

Take OracleJdk as an example. Starting from JDK 9, support for JDBC-ODBC Bridge was officially stopped. So, JDK 9 and higher version cannot use the ODBC data sources. Users can use a JDBC source to replace an ODBC one.

• Using a higher version of JDK for esProc on Mac may cause server startup error

Take JRE 25 as an example. When running esProc with a high-version JDK in a Mac environment, due to version compatibility restrictions, the esProc server’s graphical interface and headless HTTP service may fail to start properly.

• In the higher version JDK environment, cloud service related JAR files need to be migrated

Tomcat and JDK have version compatibility dependencies and must be used in matching combinations. If you upgrade JDK to a high version, a compatible high-version Tomcat is required. As Tomcat of high versions have completely replace the underlying dependency fromjavax.servlettojakarta.servlet. the use of a high-version JDK and Tomcat for cloud services requires migrating and converting the relevant JAR files. Apache Tomcat officially provides a dedicated migration tool, and users can also directly follow the steps below to complete the conversion:

1. Download the official migration tool

URL: https://tomcat.apache.org/download-migration.cgi

It is recommended to download the shaded version (all-in-one integrated package), which requires only a single JAR file to complete the conversion.

2. Prepare the file directory

Put the downloaded migration tool jar file in the specified directory (such as root directory of D drive);

Create two folders under the directory: javaxlib and jakartalib;

Put all jar files to be converted in javaxlib folder.

3. Run the conversion command

Open the command line in the directory where the tool is located and execute the following command:

java -jar jakartaee-migration-1.0.8-shaded.jar ./javaxlib ./jakartalib -profile=EE

After the execution completes and a success prompt appears, the newly converted JAR files will be in thejakartalibfolder.

For any specific issues you have during the upgrade process, please feel free to contact our technical support team for assistance.