Update shrine.conf
- Remove the shrine.ontology.versionTerm property
- HUB nodes only: Remove the shrine.hub.networkhealth property if defined.
Updated shrine.conf
shrine { shrineHubBaseUrl = "https://shrine-hub.faraway.com: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 = "testNode" //node key to get information from the hub about this 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 keystore { privateKeyAlias = "shrine-node1" 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 = "https://shrine.example.com:6443/shrine-api/shrine-steward" } }//steward }//shrine
(Optional) Change the default logo
The logo in the top left of the webclient can be changed by specifying a file path or URL to an image ((PNG, JPG, GIF, etc). Image can be any size, it will be resized to fit the header.
webclient.logo = "/path/to/image.png"
(Optional) Change the default network name
The default name is SHRINE but the network name can be changed by setting the webclient.name property. For best display results, the network name should be 75 characters or less.
webclient.name = "My SHRINE"
(Optional) Client side proxy options
Client side proxy settings can now be configured using the -D option on tomcat startup(https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/net/doc-files/net-properties.html#Proxies).
-Dhttps.proxyHost=<proxy host> -Dhttps.proxyPort=<proxy port>
Overview
Content Tools
2 Comments
David Walend
Do we want to mention the client side proxy configs that shrine can support from tomcat's start-up via -D ? Or leave them out? Drew might have an opinion. I'm not sure what the right answer is.
Marc-Danie Nazaire
I think it makes sense to document them here.