Date: Fri, 29 Mar 2024 06:31:24 -0400 (EDT) Message-ID: <560820311.936.1711708284234@prodopencatalystconfluence.catalyst> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_935_1373399695.1711708284230" ------=_Part_935_1373399695.1711708284230 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
In SHRINE networks, it is important that each node uses its own = distinct i2b2 domain name. SHRINE uses both the i2b2 domain name and the i2= b2 user name to identify a user.
By default, i2b2 uses the domain name "i2b2demo", which= prevents remote nodes from determining where a query originated.
If you have no other applications which depend on the i2b2 domain being = named "i2b2demo", you may rename the existing "i2b= 2demo" domain in the i2b2 database, and update the appropriate SHR= INE configuration files. In order to rename an existing i2b2 domain, follow= the instructions below.
NOTE: These instructions assume that Postgres is b= eing used as the i2b2 database engine, but the queries are simple enough th= at they should be easily translated to other database engines if need be.= p>
Replace "newdomain" in these examples with the name of = the domain you would like to use. The name should be short and able to uniq= uely identify your institution. (If needed, replace "i2b2demo" with the name of your existing i2b2 domain.)
i2b2 Database
In the i2b2hive database, run the following q= ueries:
psql i2b2hive UPDATE crc_db_lookup SET C_DOMAIN_ID =3D 'newdomain' WHERE C_DOMAIN_ID =3D = 'i2b2demo'; UPDATE im_db_lookup SET C_DOMAIN_ID =3D 'newdomain' WHERE C_DOMAIN_ID =3D '= i2b2demo'; UPDATE ont_db_lookup SET C_DOMAIN_ID =3D 'newdomain' WHERE C_DOMAIN_ID =3D = 'i2b2demo'; UPDATE work_db_lookup SET C_DOMAIN_ID =3D 'newdomain' WHERE C_DOMAIN_ID =3D= 'i2b2demo';
In the i2b2pm database, ru= n the following query:
psql i2b2pm UPDATE pm_hive_data SET DOMAIN_NAME =3D 'newdomain' WHERE DOMAIN_NAME =3D '= i2b2demo';
If you make use of the i2b2 admin webclient and the plain i2b2 webclient= , make sure to update the lstDomains block in th= e i2b2_config_data.js file for each of those com= ponents as follows:
i2b2_config_data.js - lstDomains
domain:&nb=
sp; "newdomain" ,
|
For example, these files can be found in:
/var/www/html/admin/i2b2_config_data.js
/var/www/html/webclient/i2b2_config_data.js
Replace "newdomain" in all the above examples with the = name of the domain you would like to use. The name should be short and able= to uniquely identify your institution.
In the example shrine.conf file we use a top-level property to define th= e domain. Change that to your new domain name:
i2b2Domain =3D "new= Domain" shrine {...}
After this, restart SHRINE&n= bsp;to make the changes take effect. You should start seeing references to = the new domain name in the Message Log as well a= s the shrine_query_history database after runnin= g a query.