This chart summarizes server-side dependency recommendations for past & current releases, and predictions for upcoming (*) releases.
|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||2016|
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 Java 8. We strongly recommend using the latest Java 8 runtime from Oracle, currently Java SE 8u152.
LabKey Server is not compatible with Java 9 and has not been tested with non-Oracle Java implementations (e.g., OpenJava, OpenJDK, IBM J9, etc.).
We recommend using the latest release of Apache Tomcat 8.5.x (currently 8.5.23).
LabKey continues to support older releases Tomcat 8.0.x and 7.0.x, though here also we strongly recommend installing the latest point release (currently 8.0.47 or 7.0.82). Note that Tomcat 7.0.x is not compatible with some advanced features of LabKey Server (e.g., Docker and RStudio integration) and the Apache Tomcat team has announced the end of life date for Apache Tomcat 8.0.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 release of PostgreSQL 10.x (currently 10.1).
For those who can't transition to 10.x yet, LabKey continues to support PostgreSQL 9.6, 9.5, 9.4, and 9.3, though here also we strongly recommend installing the latest point release (currently 9.6.6, 9.5.10, 9.4.15, and 9.3.20) 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 2016. LabKey continues to support and test on SQL Server 2014 and 2012. LabKey does not support SQL Server 2008 R2 or earlier releases.