Search on this blog

Search on this blog

Live Demo

Get i2b2
View Categories

13.4.4 Data Source Configuration

3 min read

Table of Contents

Step 8: Configure the data sources for the IM Cell #

The IM cell needs to communicate with your i2b2 database and in order to do this it needs to know where the tables for the imdata and hivedata reside. Therefore the eighth and final step in the cell configuration process is to configure the data sources for the IM Cell. This information is configured in the im-ds.xml file.

 

Things to keep in mind when configuring your datasources: #

 

  • The imdata and hivedata tables were created during the chapter on Data Installation.

 

  • The IMBootStrapDS points to the data source for your WORK_DB_LOOKUP table which is a hivedata table.
    • The and need to match the database user you set up for your hivedata. In the i2b2 demo database this is i2b2hive and demouser.

 

  • The IMDemoDS points to the data source for your imdata tables.
    • The and need to match the database user you set up for your imdata. In the i2b2 demo database this is i2b2imdata and demouser.

 

  • The needs to have the following:
    • The correct JDBC information for your type of database.
    • The correct location of the database containing your imdata or hivedata tables. (These may or may not reside in the same location)

 

  • Both the and need to accurately reflect the type of database you are connecting to.

 

Steps to configure data sources #


The following steps define how to configure your data sources for the IM Cell. These steps include example configurations for Oracle, PostreSQL and SQL Server.

 

1. The im-ds.xml file is located in the following directory:
YOUR_I2B2_SRC_DIRedu.harvard.i2b2.imetcjboss
2. Open the im-ds.xml file to configure your data sources. (see examples shown below)

 

Oracle Database Configuration #

 


	jdbc:oracle:thin:@localhost:1521:xe
	oracle.jdbc.OracleDriver
	ojdbc6.jar
	
		i2b2hive
		demouser
	
	
		false
		false
	
	
		false
	


	jdbc:oracle:thin:@localhost:1521:XE
	oracle.jdbc.OracleDriver
	ojdbc6.jar
	
		i2b2imdata
		demouser
	
	
		false
		false
	
	
		false

 

PostgreSQL Database Configuration #

 


	jdbc:postgresql://localhost:5432/i2b2
	org.postgresql.Driver
	postgresql-9.2-1002.jdbc4.jar
	
		i2b2hive
		demouser
	
	
		false
		false
	
	
		false
	


	jdbc:postgresql://localhost:5432/i2b2
	org.postgresql.Driver
	postgresql-9.2-1002.jdbc4.jar
	
		i2b2imdata
		demouser
	
	
		false
		false
	
	
		false

 

SQL Server Database Configuration #

 


	jdbc:sqlserver://localhost:1433
	com.microsoft.sqlserver.jdbc.SQLServerDriver
	sqljdbc4.jar
	
		i2b2hive
		demouser
	
	
		
		false
	
	
		false
	


	jdbc:sqlserver://localhost:1433
	com.microsoft.sqlserver.jdbc.SQLServerDriver
	sqljdbc4.jar
	
		i2b2imdata
		demouser
	
	
		
		false
	
	
		false
3. If your environment has multiple projects pointing to different data sources then copy the section for each project data source.
4. Update the jndi-name and pool-name to reflect the name of the second project .
Example:   A second project called Demo2 would have the following entry:

 

Second Data Source Configuration #

 


	jdbc:oracle:thin:@localhost:1521:XE
	oracle.jdbc.OracleDriver
	ojdbc6.jar
	
		i2b2imdata
		demouser
	
	
		false
		false
	
	
		false

Note

The above example is for an Oracle database. If your database is SQL Server or PostgreSQL then you will need to copy the section for your type database connection. Do not use this one as it will not work.

5. Save the changes and close the file.


What are your Feelings