...
Shrine now accesses the DSA's database directly from inside shrine-api.war. It no longer needs a special QEP user to authenticate to the Data Steward service. Delete that user from the PM cell, and remove this section from shrine.conf:
...
Remove includeAggregateResults
Remove the formerly required "includeAggregateResults = false" from shrine.conf .
Code Block |
---|
|
includeAggregateResults = false |
In SHRINE 2.0.0, you will need additional parameters to configure the behavior of the webclient. Please add this section in shrine.conf:
Code Block |
---|
language | bash |
---|
theme | RDarkrdark |
---|
|
webclient {
domain = "i2b2demo"
name = "SHRINE"
siteAdminEmail = "email@example.com"
usernameLabel = "User Name"
passwordLabel = "User Password"
defaultNumberOfOntologyChildren = 10000 // the number of children to show when an ontology folder is expanded.
queryFlaggingInstructions = "Enter instructions for flagging queries here"
flaggingPlaceholderText = "Enter placeholder text for the query flagging text input field"
flaggingIconInstructions = "Enter text for when user mouses over the flagging information icon in the header of the Query History here"
} |
The webclient has hard-coded default values for the userNameLabel, passwordLabel, and defaultNumberOfOntologyChildren fields if they are not configured; userNameLabel defaults to "SHRINE User", passwordLabel defaults to "SHRINE Password", and defaultNumberOfOntologyChildren defaults to 10000.
...
Redirect webclient, steward, and dashboard to old URL links
Info |
---|
Before you perform these steps, please make sure your Tomcat version is at least 8.5.x, but please do not install Tomcat version 9! |
The URL to the SHRINE Webclient has changed from https://shrine_url:6443/shrine-webclient to https://shrine_url:6443/shrine-api/shrine-webclient.
...
<Host name="localhost" appBase="webapps"
unpackWARs="true" autoDeploy="true">
<Valve className="org.apache.catalina.valves.rewrite.RewriteValve" />
2. Create a file name rewrite.config in conf/Catalina/localhost with the following contents
RewriteRule ^/shrine-webclient/* /shrine-api/shrine-webclient
RewriteRule ^/steward/* /shrine-api/shrine-steward
RewriteRule ^/shrine-dashboard/* /shrine-api/shrine-dashboard
...
Code Block |
---|
language | bash |
---|
theme | RDark |
---|
title | shrine.conf |
---|
|
shrineHubBaseUrl = "https://shrine_hub_url:6443" //The shrine hub's URL as observed from this tomcat server
i2b2BaseUrl = "http://localhost:9090" //The local i2b2's URL as observed from this tomcat server
i2b2Domain = "i2b2demo" //recommended to change this to a unique domain
i2b2ShrineProjectName = "SHRINE"
shrine {
nodeKey = "unique-node-name" //node key to get information from the hub about this node
shrineDatabaseType = "mysql" //can be oracle, mysql, sqlserver
messagequeue {
blockingq {
serverUrl = ${shrineHubBaseUrl}/shrine-api/mom //point this to the network hub
}
}
webclient {
domain = ${i2b2Domain}
name = ${i2b2ShrineProjectName}
siteAdminEmail = "email@example.com"
usernameLabel = "User Name"
passwordLabel = "User Password"
defaultNumberOfOntologyChildren = 10000 // the number of children to show when an ontology folder is expanded.
queryFlaggingInstructions = "Enter instructions for flagging queries here"
flaggingPlaceholderText = "Enter placeholder text for the query flagging text input field"
flaggingIconInstructions = "Enter text for when user mouses over the flagging information icon in the header of the Query History here"
}
pmEndpoint {
url = ${i2b2BaseUrl}/i2b2/services/PMService/getServices
}
ontEndpoint {
url = ${i2b2BaseUrl}/i2b2/services/OntologyService/
}
hiveCredentials {
domain = ${i2b2Domain}
username = "demo"
password = "demouser"
crcProjectId = "Demo"
ontProjectId = ${i2b2ShrineProjectName}
}
breakdownResultOutputTypes {
PATIENT_AGE_COUNT_XML {
description = "Age patient breakdown"
}
PATIENT_RACE_COUNT_XML {
description = "Race patient breakdown"
}
PATIENT_VITALSTATUS_COUNT_XML {
description = "Vital Status patient breakdown"
}
PATIENT_GENDER_COUNT_XML {
description = "Gender patient breakdown"
}
} //end breakdown section
hub {
client {
serverUrl = ${shrineHubBaseUrl}
}
}
queryEntryPoint {
broadcasterServiceEndpoint {
url = ${shrineHubBaseUrl}/shrine/rest/broadcaster/broadcast
}
}
adapter {
crcEndpoint {
url = ${i2b2BaseUrl}/i2b2/services/QueryToolService/
}
adapterMappingsFileName = "AdapterMappings.csv"
//crcRunQueryTimeLimit = "30 seconds" // in seconds, use quotes. default 30 seconds
} //end adapter section
keystore {
file = "/opt/shrine/shrine.keystore"
password = "password"
privateKeyAlias = "your_private_key_alias"
keyStoreType = "JKS"
caCertAliases = ["shrine-hub-ca"]
} //end keystore section
steward {
createTopicsMode = Approved //the default is Pending - the most secure - but most sites use Approved
emailDataSteward {
sendAuditEmails = false //false to turn off the whole works of emailing the data steward
//interval = "1 day" //Audit researchers daily
//timeAfterMidnight = "6 hours" //Audit researchers at 6 am. If the interval is less than 1 day then this delay is ignored.
//maxQueryCountBetweenAudits = 30 //If a researcher runs more than this many queries since the last audit audit her
//minTimeBetweenAudits = "30 days" //If a researcher runs at least one query, audit those queries if this much time has passed
//You must provide the email address of the shrine node system admin, to handle bounces and invalid addresses
//from = "shrine-admin@example.com"
//You must provide the email address of the data steward
//to = "shrine-steward@example.com"
//subject = "Audit SHRINE researchers"
//The baseUrl for the data steward to be substituted in to email text. Must be supplied if it is used in the email text.
//stewardBaseUrl = "https://example.com:6443/shrine-api/shrine-steward/"
externalStewardBaseUrl = "https://example.com:6443/shrine-api/shrine-steward/"
//Text to use for the email audit.
//AUDIT_LINES will be replaced by a researcherLine for each researcher to audit.
//STEWARD_BASE_URL will be replaced by the value in stewardBaseUrl if available.
//emailBody = """Please audit the following users at STEWARD_BASE_URL at your earliest convenience: AUDIT_LINES"""
//note that this can be a multiline message
//Text to use per researcher to audit.
//FULLNAME, USERNAME, COUNT and LAST_AUDIT_DATE will be replaced with appropriate text.
//researcherLine = "FULLNAME (USERNAME) has run COUNT queries since LAST_AUDIT_DATE."
}
} //end databasesteward {section
dataSourceFrom = "JNDI"
} jndiDataSourceName = "java:comp/env/jdbc/stewardDB"
slickProfileClassName = "slick.jdbc.MySQLProfile$"
//slick.jdbc.H2Profile$
//slick.jdbc.PostgresProfile$
//slick.jdbc.SQLServerProfile$
//slick.jdbc.JdbcProfile$
//slick.jdbc.OracleProfile$
} //end steward database section
} //end steward section
} //end shrine |
Warning |
---|
title | New nodeKey parameter |
---|
|
The nodeKey parameter will be used to identify your node from the Hub, so we advise that it should be a relatively unique identifier along with the network in which you are in, ie. HarvardProdNode or similar. If you have any questions, please contact the network administrator for more information. |
Changes to SHRINE databases
In SHRINE 2.0.0, there are a couple of database changes that you will need to perform to accommodate the new tables and structures needed for SHRINE to work properly.
...
Warning |
---|
title | New nodeKey parameter |
---|
|
The nodeKey parameter will be used to identify your node from the Hub, so we advise that it should be a relatively unique identifier along with the network in which you are in, ie. HarvardProdNode or similar. If you have any questions, please contact the network administrator for more information. |
Changes to SHRINE databases
In SHRINE 2.0.0, there are a couple of database changes that you will need to perform to accommodate the new tables and structures needed for SHRINE to work properly.
Remove the PRIVILEGED_USER table and associated constraints and sequences from your database
Code Block |
---|
|
use shrine_query_history;
DROP TABLE PRIVILEGED_USER; |
Drop the column of actual patient counts from the adapter's COUNT_RESULT table
Shrine no longer needs to store the actual (and mildly sensitive) actual count of patients from the CRC in its COUNT_RESULT table. In mysql remove it from the shrine_query_history database with
Code Block |
---|
|
use shrine_query_history;
ALTER TABLE COUNT_RESULT DROP COLUMN ORIGINAL_COUNT; |
Drop the column of actual patient counts from the adapter's BREAKDOWN_RESULT table
Shrine no longer needs to store the actual (and mildly sensitive) actual count of patients from the CRC in its BREAKDOWN_RESULT table. In mysql remove it from the shrine_query_history database with
Code Block |
---|
|
use shrine_query_history;
ALTER TABLE BREAKDOWN_RESULT DROP TABLECOLUMN PRIVILEGEDORIGINAL_USERVALUE; |
Drop the column of actual patient counts from the adapter's COUNT_RESULT table
...
Add a status column for queries at the QEP
Add a status column to qepAuditDB's previousQueries table to support updates in query status with :
MySQL:
shrine_query_history;
ALTER TABLE COUNT_RESULT DROP COLUMN ORIGINAL_COUNT; Drop the column of actual patient counts from the adapter's BREAKDOWN_RESULT table
...
qepAuditDB;
ALTER TABLE previousQueries ADD COLUMN status VARCHAR(255) NOT NULL DEFAULT 'Before V26'; |
MS SQL:
shrine_query_history BREAKDOWN_RESULT DROP COLUMN ORIGINAL_VALUE; Add a status column for queries at the QEP
Add a status column to qepAuditDB's previousQueries table to support updates in query status with :
MySQL:
previousQueries ADD status VARCHAR(MAX) NOT NULL DEFAULT 'Before V26'; |
ORACLE:
Code Block |
---|
|
use qepAuditDB;
ALTER TABLE "previousQueries" ADD COLUMN "status" VARCHARVARCHAR2(255256) NOT NULL DEFAULT 'Before V26' NOT NULL; |
MS SQL
Added table QUERY_PROBLEM_DIGESTS
MySQL:
rdarkALTER TABLE previousQueries ADD COLUMN 'status' VARCHAR(MAX)create table QUERY_PROBLEM_DIGESTS (NETWORKQUERYID BIGINT NOT NULL, CODEC TEXT NOT NULL, STAMP TEXT NOT NULL, SUMMARY TEXT NOT NULL, DESCRIPTION TEXT NOT NULL, |
DEFAULT'Before V26';ORACLE:
Code Block |
---|
|
use qepAuditDB;
ALTER TABLE "previousQueries" ADD COLUMN "status" VARCHAR2(256) DEFAULT 'Before V26' NOT NULL; |
Added table QUERY_PROBLEM_DIGESTS
TEXT NOT NULL, CHANGEDATE BIGINT NOT NULL);
create index queryProblemsNetworkIdIndex on QUERY_PROBLEM_DIGESTS(NETWORKQUERYID); |
MS SQLMySQL:
Code Block |
---|
language | sqlSQL |
---|
theme | RDarkrdark |
---|
|
use qepAuditDB;
create table "QUERY_PROBLEM_DIGESTS" ("NETWORKQUERYID" BIGINT NOT NULL, "CODEC" TEXTVARCHAR(MAX) NOT NULL, "STAMP" TEXTVARCHAR(MAX) NOT NULL, "SUMMARY" TEXTVARCHAR(MAX) NOT NULL, "DESCRIPTION" TEXTVARCHAR(MAX) NOT NULL, "DETAILS" TEXTVARCHAR(MAX) NOT NULL, "CHANGEDATE" BIGINT NOT NULL);
create index "queryProblemsNetworkIdIndex" on "QUERY_PROBLEM_DIGESTS" ("NETWORKQUERYID"); |
MS SQLORACLE:
Code Block |
---|
|
use qepAuditDB;
create table "QUERY_PROBLEM_DIGESTS" ("NETWORKQUERYID" BIGINTNUMBER(19) NOT NULL,"CODEC" VARCHAR(MAX256) NOT NULL,"STAMP" VARCHAR(MAX256) NOT NULL,"SUMMARY" VARCHAR(MAX)CLOB NOT NULL,"DESCRIPTION" VARCHAR(MAX)CLOB NOT NULL,"DETAILS" VARCHAR(MAX)CLOB NOT NULL,"CHANGEDATE" BIGINTNUMBER(19) NOT NULL);
create index "queryProblemsNetworkIdIndex" on "QUERY_PROBLEM_DIGESTS" ("NETWORKQUERYID"); |
Added table RESULTS_OBSERVED
ORACLEMySQL:
Code Block |
---|
|
use qepAuditDB;
create table "QUERY_PROBLEM_DIGESTS" ("NETWORKQUERYID" NUMBER(19) NOT NULL,"CODEC" VARCHAR(256) NOT NULL,"STAMP" VARCHAR(256) NOT NULL,"SUMMARY" CLOB NOT NULL,"DESCRIPTION" CLOB table RESULTS_OBSERVED (NETWORKQUERYID BIGINT NOT NULL,"DETAILS" CLOB CHECKSUM BIGINT NOT NULL,"CHANGEDATE" NUMBER(19) OBSERVEDTIME BIGINT NOT NULL);
create index "queryProblemsNetworkIdIndex"resultsObservedQueryIdIndex on "QUERY_PROBLEM_DIGESTS" ("NETWORKQUERYID"); |
Added table RESULTS_OBSERVED
RESULTS_OBSERVED(NETWORKQUERYID);
create index resultsObservedChecksumIndex on RESULTS_OBSERVED(CHECKSUM); |
MS SQLMySQL:
Code Block |
---|
|
use qepAuditDB;
create table "RESULTS_OBSERVED" ("NETWORKQUERYID" BIGINT NOT NULL, "CHECKSUM" BIGINT NOT NULLNOTNULL, "OBSERVEDTIME" BIGINT NOT NULL);
create index "resultsObservedQueryIdIndex" on "RESULTS_OBSERVED" ("NETWORKQUERYID");
create index "resultsObservedChecksumIndex" on "RESULTS_OBSERVED" ("CHECKSUM"); |
MS SQLORACLE:
Code Block |
---|
|
use qepAuditDB;
create table `RESULTS"RESULTS_OBSERVED`OBSERVED" (`NETWORKQUERYID` BIGINT"NETWORKQUERYID" NUMBER(19) NOT NULL,`CHECKSUM` BIGINT"CHECKSUM" NUMBER(19) NOT NULL,`OBSERVEDTIME` BIGINT NOT NULL"OBSERVEDTIME" NUMBER(19) NOT NULL);
create index "resultsObservedQueryIdIndex" on "RESULTS_OBSERVED" ("NETWORKQUERYID");
create index "resultsObservedQueryIdIndexresultsObservedChecksumIndex" on "RESULTS_OBSERVED" ("NETWORKQUERYID");
create index "resultsObservedChecksumIndex" on "RESULTS_OBSERVED" ("CHECKSUM"); |
...
Make sure you have setenv.sh defined for Tomcat startup
For SHRINE 2.0.0 in addition to the 2.0.1 ACT ontology, we will need to make sure that Tomcat has enough resources to load the ontology and its larger Adapter Mappings file. To do this, you will need to define a setenv.sh file within the tomcat/bin directory:
Code Block |
---|
language | SQLbash |
---|
theme | rdark |
---|
|
use qepAuditDB;
create table "RESULTS_OBSERVED" ("NETWORKQUERYID" NUMBER(19) NOT NULL,"CHECKSUM" NUMBER(19) NOT NULL,"OBSERVEDTIME" NUMBER(19) NOT NULL);
create index "resultsObservedQueryIdIndex" on "RESULTS_OBSERVED" ("NETWORKQUERYID");
create index "resultsObservedChecksumIndex" on "RESULTS_OBSERVED" ("CHECKSUM");#!/bin/bash# Set Tomcat options to prevent hanging thread on shutdown
export CATALINA_OPTS=" -XX:MaxPermSize=256m -Dakka.daemonic=on "
# Set Tomcat options to prevent resource problems with larger ontology v2.0.1
CATALINA_OPTS="$CATALINA_OPTS -server -Xms1024m -Xmx2048m -Duser.timezone=America/New_York |
Start SHRINE
Warning |
---|
|
At this time, please reach out to the network hub administrator so that they can add your individual node to the network with the "nodeKey" that was identified in shrine.conf. Once added to the hub, your node should then start sending and receiving queries. You'll also need to tell the admin your domain parameter, so that the domain will be associated with the nodeKey on the hub. |
The only thing left to do at this point is start SHRINE back up. Simply do the following:
...
Code Block |
---|
|
https://your_shrine_host:6443/shrine-api/shrine-dashboard |
This is a sample screenshot of the upgraded 2.0.0 dashboard:
...