Page History
...
| Warning | ||
|---|---|---|
| ||
If you are creating a hub use hub-and-qep-shrine.conf - and skip to SHRINE 4.2.0 Chapter 8.2 - Configuring a Hub. |
In this guide, we will refer to this file often and will go more in detail on configuring this file in the later chapters). Here is the example shrine.conf file from shrine-setup.zip. You will need to customize it for your own node on your network. In the example below, the first four lines in the shrine section define values for parameters that are used throughout the configuration file.
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
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 = "yourDomain" //a value for your domain that clearly identifies your institution.
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
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) To require users to be a member of a specific PM cell project, add the following to shrine.conf:
...
Overview
Content Tools