This chart summarizes server-side dependency recommendations for past & current releases, and predictions for upcoming releases.
|Do not use: not yet available or tested with this version of LabKey|
|Recommended: fully supported and thoroughly tested with this version of LabKey|
|Supported in this version of LabKey, but with important caveats. See details below.|
|Upgrade ASAP: deprecated and no longer supported with this version of LabKey|
|Do not use: incompatible with this version of LabKey and/or past end of life (no longer supported by the organization that develops the component)|
|Microsoft SQL Server (Premium Feature)||2019|
LabKey Server requires a modern browser for many advanced features, and we recommend upgrading your browser(s) to the latest stable release. As a general rule, LabKey Server supports the latest version of the following browsers:
If you experience a problem with a supported browser feel free to search for, and if not found, post the details to the support forum so we're made aware of the issue.
We recommend using the latest point release of Eclipse Temurin 17 64-bit (currently 17.0.1+12), the community-supported production-ready distribution of the Java Development Kit produced by the Adoptium Working Group. For a short time, LabKey will allow JDK 16 with HotSpot JVM, though it is not recommended since public updates (i.e., patches to address security and reliability issues) are no longer provided for JDK 16.
You must run the Java 17 (or 16) JVM with four special flags --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.awt.font=ALL-UNNAMED to allow certain libraries to function properly. (Note that standard startup scripts in the most recent Tomcat versions add these flags automatically.) We will upgrade the libraries as soon as they fully support the changes that JDK 16 made in JEP 396.
LabKey Server has not been tested with other Java distributions such as Oracle OpenJDK, Oracle commercial Java SE, Amazon Corretto, Red Hat, Zulu, OpenJ9, etc.
LabKey requires Apache Tomcat 9.0.x; we strongly recommend upgrading to the latest point release (currently 9.0.58).
LabKey no longer supports Tomcat 8.5.x and earlier. LabKey does not yet support Tomcat 10.0.x or 10.1.x.
We recommend installing Tomcat using the binary distributions; if a package manager is used, the lib directory may be installed in a different location. Also, the packages sometimes include alternative versions of some components (like JDBC connection pools) that can cause incompatibilities.
We recommend not using the Apache Tomcat Native library; this library can interfere with SSL and prevent server access via LabKey's client libraries.
For installations using PostgreSQL as the primary database, we recommend using the latest point release of PostgreSQL 14.x (currently 14.1).
For those who can't transition to 14.x yet, LabKey continues to support PostgreSQL 13.x, 12.x, 11.x, and 10.x, though here also we strongly recommend installing the latest point release (currently 13.5, 12.9, 11.14, and 10.19) to ensure you have all the latest security, reliability, and performance fixes.
PostgreSQL provides instructions for how to upgrade your installation, including moving your existing data.
Premium Editions of LabKey Server have the option of using Microsoft SQL Server databases as the primary database and as external data sources. For these installations, we recommend using Microsoft SQL Server 2019 , which we've tested on both Windows and Linux.
LabKey continues to support SQL Server 2017, 2016, 2014, and 2012. LabKey does not support SQL Server 2008 R2 or earlier releases.
LabKey does not recommend a specific version of Linux, but you will need to use one that supports the versions of Tomcat, Java, your database, and any other necessary components for your version of LabKey Server.