SHRINE gets its configuration from a configuration file named shrine.conf in /opt/shrine/tomcat/lib. If you are installing a downstream (non-hub) node, copy the shrine-setup/qep-and-adapter-shrine.conf file from shrine-setup.zip to tomcat's lib directory. If you are creating a hub use hub-and-qep-shrine.conf instead. (ACT participants should configure their hosts as downstream nodes.)
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.
(Optional) To require users to be a member of a specific PM cell project, add the following to shrine.conf:
All passwords are now stored in password.conf file in /opt/shrine/tomcat/lib instead of shrine.conf.
The nodeKey value will be used to identify your node from the Hub. This value must be a unique alphanumeric identifier in your network. If you have any questions, please contact the hub administrator for more information.
Choose a custom value for your domain parameter that clearly identifies your institution. Do not leave it at its default values.