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|
|Use with caution: either deprecated or not yet fully supported / tested 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||2017|
LabKey Server requires a modern browser for many advanced features, such as locking data table column headers in place when scrolling, creating charts, or visualizing security group relationships. To take advantage of all features, we recommend upgrading your browser(s) to the latest release. Since this is not always possible, the LabKey team attempts to maintain basic compatibility and fix major issues with the following browsers:
As a general rule, LabKey Server supports the latest version of the browsers listed above. To review and download the latest versions, click the links provided.
If you experience a problem with a supported browser feel free to post the details to the support forum so we're made aware of the issue.
LabKey Server requires Oracle OpenJDK 12, Oracle's production-ready open-source build of the Java Development Kit. We strongly recommend installing the latest point release, currently 12.0.1. OpenJDK 12 is the only version of Java receiving public updates (i.e., regular patches to address security and reliability issues); as a result, LabKey does not support Java 8, 9, 10, or 11. You may want to familiarize yourself with recent changes to the Java licensing and release schedule that affect every LabKey deployment; see this post on the LabKey blog.
LabKey Server has not been tested with other Java distributions such as the Oracle commercial Java SE, AdoptOpenJDK, Amazon Corretto, Red Hat, Zulu, OpenJ9, etc.
We recommend using the latest point release of Apache Tomcat 9.0.x (currently 9.0.19).
LabKey continues to support older versions 8.5.x and 7.0.x, though we strongly recommend installing the latest point release of each (currently 8.5.40 or 7.0.94); older point releases have major compatibility issues and security vulnerabilities. Do not use Tomcat 9.0.14 or 8.5.37; these were released with a serious bug that prevents our build from compiling JSP files. Note that Tomcat 7.0.x is not compatible with some advanced features of LabKey Server (e.g., Docker and RStudio integration). Tomcat 8.0.x is no longer supported as it has reached end of life; it has been superseded by Tomcat 8.5.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 11.x (currently 11.2). Do not use PostgreSQL 11.0; it was released with a serious bug that makes 11.0 incompatible with LabKey and many other applications.
For those who can't transition to 11.x yet, LabKey continues to support PostgreSQL 10.x, 9.6.x, 9.5.x, and 9.4.x, though here also we strongly recommend installing the latest point release (currently 10.7, 9.6.12, 9.5.16, and 9.4.21) 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 database.
For installations using Microsoft SQL Server as the primary database, we recommend using Microsoft SQL Server 2017, which we've tested on both Windows and Linux. We continue to support and test on SQL Server 2016, 2014, and 2012. LabKey does not support SQL Server 2008 R2 or earlier releases.