Hub Admins Only
This section is intended for hub administrators only. For the ACT network, the hubs have already been set up and hosted at Harvard Catalyst, and remote sites should skip this section.
Here is a sample shrine.conf file for a system running SHRINE 4.0.0 , for a node supporting researchers and distributing queries.
shrine.conf
shrine { shrineHubBaseUrl = "https://localhost:6443" //The shrine hub's URL as observed from this tomcat server i2b2BaseUrl = "http://i2b2.example.com:9090" //The local i2b2's URL as observed from this tomcat server i2b2Domain = "exampleDomain" i2b2ShrineProjectName = "SHRINE" nodeKey = "somethingHub" //node key to get information from the hub about itself as a node. //shrineDatabaseType = "mysql" // "mysql" by default. It can be "sqlserver" "mysql" or "oracle" webclient { siteAdminEmail = "shrine-admin@example.com" } hiveCredentials { username = "demo" crcProjectId = "Demo" }//hiveCredentials hub { create = true messagequeue { blockingqWebApi { enabled = true //run shrine's MoM system at the hub. } }//messagequeue }//hub adapter { create = false }//adapter keystore { privateKeyAlias = "shrine-hub" caCertAliases = ["shrine-ca"] }//keystore steward { emailDataSteward { //provide the email address of the shrine node system admin, to handle bounces and invalid addresses from = "shrine-admin@example.com" //provide the email address of the shrine node system admin, to handle bounces and invalid addresses to = "shrine-steward@example.com" //provide the externally-reachable URL for the data steward externalStewardBaseUrl = ${shrine.shrineHubBaseUrl}/shrine-api/shrine-steward } }//steward }//shrine
It is rare but possible to have a set of patient data at the hub. Simply include the adapter section of shrine.conf from Chapter 8 in your shrine.conf .
All passwords are now stored in password.conf file in /opt/shrine/tomcat/lib instead of shrine.conf.
password.conf
shrine.hiveCredentials.password = "changeit"
TODO initial hub setup with the network lifecycle tool.
Overview
Content Tools