...

Considerations Before You Begin

We design designed SHRINE with the best default values for most settings to minimize customization. However, SHRINE supports some high-level customizations to better fit your institutions' practices.


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.1 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. 

Database

SHRINE provides schemas for downstream nodes that support mysql/mariadb, Oracle, and MS SQL server. See XXX SHRINE 4.1.0 Chapter 6 - Install and Configure a Database Service.

Authentication

By default SHRINE uses the i2b2 PM cell to authenticate and authorize users. See XXX SHRINE 4.1.0 Chapter 9 . Starting in SHRINE 4.0 SHRINE can be configured to use Shibboleth. See XXX SHRINE 4.1.0 Appendix A - Setting up SSO - with Shibboleth SP 3.

Considerations for a

...

Network

We only supply a mysql/mariadb schema for the hub's database.

SHRINE uses message-oriented middleware to support reliable asynchronous communication. By default a SHRINE network needs no additional configuration, but can be configured to use AWS SQS or Kafka to minimize the impact of hub maintenance. See XXX SHRINE 4.1.0 Chapter 8.2 - Configuring a Hub.