Preliminaries
Create two IAM accounts: an admin to set up and modify the network using the shrineNetworkLifecycle command line tool, and one for the hub tomcat process to use to send and receive messages. That admin account will need : TODO - and how to do it
Configure the Hub
In tomcat's shrine.conf in the hub, turn off the in-tomcat messaging by setting shrine.hub.messagequeue.blockingWebApi.enabled to it's default false value by removing it:
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 }//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
Configure shrineNetworkLifecycle
The shrineNetworkLifecycle needs some additional configuration to use the AWS admin account. In
network.conf
Overview
Content Tools