Versions Compared

Old Version 2

changes.mady.by.user David Walend

Saved on

compared with

New Version Current

changes.mady.by.user Andrew Hendrix

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Warning
titleHub 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. 

...

 It is rare but possible to have a set of patient data at the hub. Simply include the adapter section of qep-and-adapter-shrine.conf from Chapter 8 in your shrine.conf ., tailored to your system as explained earlier in this chapter.


Set the shrine i2b2 user password in the All passwords are now stored in password.conf file in /opt/shrine/tomcat/lib instead of shrine.conf .

Code Block
themeRDark
titlepassword.conf
shrine.hiveCredentials.password = "changeit"


Next, configure the initial network structures and queues for the hub.

Download the shrine network lifecycle tool into /opt/shrine:

Code Block
languagebash
themeRDark
cd /opt/shrine


wget https://repo.open.catalyst.harvard.edu/nexus/content/groups/public/net/shrine/shrine-network-lifecycle-tool/4.0.0/shrine-network-lifecycle-tool-4.0.0-dist.zip -O shrine-network-lifecycle.zip unzip shrine-network-lifecycle.zip

cd shrine-network-lifecycle

Inside the conf directory, edit the override.conf file to use your database username and password:

Code Block
languagejs
themeRDark
shrine {
  queryEntryPoint{
    audit {
      database {
        dataSourceFrom = "testDataSource" //Can be JNDI or testDataSource . Use testDataSource for tests and command line tools, JNDI everywhere else
        testDataSource {
          driverClassName = "com.mysql.cj.jdbc.Driver" //JDBC driver class name
          url = "jdbc:mysql://localhost:3306/qepAuditDB?serverTimezone=UTC" //URL to your database
          credentials {
            username = "yourUserName"
            password = "yourDatabasePassword"

Next, create a file named network.conf to meet your needs. At a minimum include the network section and a section for the hub's QEP:

Code Block
languagejs
themeRDark
shrine {
  network {
    network {
      name = "Network Name"
      hubQueueName = "hub"
      adminEmail = "yourEmail@yourhospital.edu"
      momId = "HubQueue"
    }
    nodes = [
      {
        name = "Hub's QEP"
        key = "hub-qep"
        userDomainName = "network-hub"
        queueName = "shrinehub"
        sendQueries = "false"
        adminEmail = "yourEmail@yourhospital.edu"
        momId = "HubQepQueue"
      }
    ]
  }
}

Finally use the shrineLifecycle tool to set up the network:

Code Block
languagebash
themeRDark
./shrineLifecycle createNetwork network.conf