Page History

...

First, ask your hub admin for the base url for your hub. That admin will ask you for your public IP address so that the hub can open an inbound firewall hole for your system. "Inbound" access is from the perspective of the hub.   In most cases,  Generally if a downstream site can reach the Internet without restrictions, then no firewall configuration is necessary on the downstream side.

Second, ensure that you can reach the hub's tomcat service from your shrine host with this curl command. (Substitute the right DNS name for the hub.) In the example below, if your command executes successfully, you will receive a "pong 200" response:

...

shrineHubBaseUrl = "https://shrine-hub.faraway.com:6443"


shrine {...}

Fourth, tell your hub admin that you are ready to run a test query. He will need to know your node key (from your shrine.conf), your preferred node name, your i2b2 user domain, and your sys admin email address.

...

The hub admin will run this curl shrine lifecycle command to add your node to the network.:

curl -u username:password -w "\n%{response_code}\n" -k -X PUT "https://shrine-hub.faraway.com:6443/shrine-api/hub/createNode/yourNodeKey?nodeName=your%20Node%20Name&userDomain=yourDomain&adminEmail=you@example.com&sendQueries=false"

# The hub admin will run
./shrineLifecycle createNode key=yourNodeKey name="Your Hospital Name" userDomainName=yourHospital queueName=yourHospital adminEmail="yourEmail@yourHospital.edu" momId="yourHospital" sendQueries="false"

After you hear from your hub admin that they have run that command start tomcat: Start tomcat.

sudo service shrine start

...

# The hub admin will run
curl -u username:password -w "\n%{response_code}\n" -k -X PUT "https://shrine-hub.faraway.com:6443/shrine-api/hub/modifyNode/yourNodeKey?sendQueries= 
./shrineLifecycle modifyNode yourNodeKey sendQueries="true"

Once your hub admin has done that, use your browser to run another test query to see results from your node listed with the others.