Page History
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
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"); |
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 | ||||
|---|---|---|---|---|
| ||||
#!/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. |
...
Overview
Content Tools