Make a few changes to configuration so that your new SHRINE instance can communicate with the i2b2 instance. First, you will need to make sure the PM and CRC cell urls are correctly defined within the shrine.conf file. These urls are what SHRINE uses to communicate with the i2b2 backend. 

  • In the shrine {} section set the i2b2BaseUrl to the top-level Url for your i2b2 wildfly server. This value will be substituted as needed in shrine.conf. 
shrine {
  i2b2BaseUrl = "" //The local i2b2's URL as observed from this tomcat server

If your i2b2 server uses publicly verifiable certificates enable SHRINE to use TLS server verification when communicating with their local i2b2 server with these settings in shrine.conf

shrine.pmEndpoint.tls.trustManager = "VerifyServerCerts"
shrine.adapter.crcEndpoint.tls.trustManager = "VerifyServerCerts"

Next add the SHRINE project into the pm_project_data table within the i2b2 database:

$ psql -U postgres i2b2
i2b2=# set search_path = public;
i2b2=# insert into PM_PROJECT_DATA (project_id, project_name, project_wiki, project_path, status_cd) values ('SHRINE', 'SHRINE Ontology', '', '/SHRINE', 'A');

Finally restart wildfly and tomcat.

1 Comment

  1. Marc-Danie Nazaire - Does shrine still need the SHRINE Ontology line in i2b2 now that shrine uses lucene for ontology terms?