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:
| Minimum | Recommended | |
| Operating System | RPM-based Linux | CentOS 7 Core |
Web Browser | Google Chrome 83 | Google Chrome 89 or better |
| Processor | 2 cores | 4 or more cores |
| Memory | 4GB | 8GB |
| Hard Drive Space | 30GB | 100GB |
| Java JDK | Any JDK version "11.0.6" 2020-01-14 LTS | OpenJDK 64-Bit Server VM Zulu17.38+21-CA |
| Apache Tomcat | 8.5.39 | 9.0.73 |
| MariaDB | 5.5 | Ver 15.1 Distrib 5.5.68-MariaDB |
| i2b2 Version | 1.8.1 | 1.8.1 |
Note: CentOS7 is the OS that SHRINE was tested against. We expect SHRINE to work just fine in other linux distros as long a the supported version of Tomcat and Java are being used.
For i2b2 1.7.12a - we have observed a lot of success with i2b2's "quick install" option. If you have not yet installed i2b2 1.7.12a please consider that path first.
Do not install SHRINE and i2b2 on the same operating system. Both SHRINE's Tomcat and i2b2's Wildfly servers are optimized to make maximum use of the operating system's resources. Either can starve the other for processing time or memory to the point of stalling both systems.
We strongly advise that you avoid placing SHRINE behind an application proxy. Misconfigured application proxies frequently interfere with SHRINE's networking needs. They offer no benefits in a SHRINE network and make troubleshooting very difficult. If you must run an application proxy, we ask that you configure your proxy to not intercept or modify any of SHRINE's network traffic.
Overview
Content Tools