Note: If you are joining a network, make sure you are choosing a version of SHRINE that is compatible with the network you are joining. SHRINE 4.2 is not backwards compatible with previous versions. As of now, the hubs on the ENACT network are running SHRINE version 3.1. Therefore, all downstream nodes on the ENACT network must use SHRINE 3x or earlier. 

When installing SHRINE from scratch, we generally recommend these minimum requirements for best performance, as these are the conditions that we test the software in:

Operating SystemRPM-based LinuxCentOS 7 Core

Web Browser

Google Chrome 111Google Chrome 111.0.5563.147 or better
Processor2 cores4 or more cores
Hard Drive Space30GB100GB
Java JDK

Any JDK version "17.0.5" 2022-10-18 LTS

OpenJDK 64-Bit Server VM Zulu17.38+21-CA

Apache Tomcat9.0



Ver 15.1 Distrib 10.11.5-MariaDB, for Linux (x86_64) using readline 5.1

i2b2 Version1.7.13


Kafka (Optional)3.3.1


Apache Proxy (Optional)2.4.54


Do not install SHRINE and i2b2 on the same operating system or physical hardware. Both SHRINE's Tomcat and i2b2's Wildfly servers are optimized to make maximum use of a system's resources. Either can starve the other for processing time or memory to the point of stalling both of them.

We strongly advise against placing SHRINE behind an application proxy for anything other than SHRINE's SAML implementation. Misconfigured application proxies frequently interfere with SHRINE's networking needs and make troubleshooting very difficult. If you must use a proxy, proceed with caution. Maintain an ability to test SHRINE without the proxy to help bracket problems between SHRINE and your proxy. See TODO for how to configure Apache Proxy, Shibboleth, and SHRINE to authenticate users with SAML.