Open Enterprise Master Patient Index: User Forum: What is the recommended way to set up PostgreSQL support in JBoss with OpenEMPI

Mailing Lists
Message Forums
» Developer Forum
» User Forum
Downloads
» Downloads
Issue Tracking
» Issue Tracking
Project chat room
» chat
Source Code Repository
» Source Code Repository
Website
» Home
Wiki
» Wiki
WikiHomePage
» WikiHomePage

» Open Health Tools Site

Open Enterprise Master Patient Index was started in October 2009, is owned by odysseas, and has 12 members.

» Join This Project

What is the recommended way to set up PostgreSQL support in JBoss with OpenEMPI

» Back to forum topics

5 posts

Replies: 4 - Last Post: June 09, 2010 17:20
by: Csaba Toth

« Older Topic » Newer Topic

showing 1 - 5 of 5

Csaba Toth

Posted: April 07, 2010 16:44 by Csaba Toth

» Permalink

There are several very different suggestions on the internet how to set up PostgreSQL with JBoss.

What is sure that:
- I have to add PostgreSQL JDBC driver jar
- I have to supply a postgresql-ds.xml file

Questions about the JDBC driver: there's a JDBC3 and a JDBC4 driver available with the newest PostgreSQL. I could see during OpenEMPI build that it downloaded JDBC3 jar sometimes. Does that mean we should use also JDBC3? I've seen on the internet, that some people found some very serious error which comes with the lates JDBC3 driver & XA mode. Should we worry about that?
Should we copy the jar file into the deployment's lib directory ($(JBOSS_HOME)\server\default\lib\)?

Next question is: what kind of postgresql-ds.xml file should I use?

My postgresql-ds.xml is based on the xml which can be found in the JBoss's example directory ($(JBOSS_HOME)\docs\examples\jca). The JNDI name is PosgresDS, and it defines a local-tx type datasource, so not an XA type. Is that ok? What do you suggest.

Other questions: several tutorials advise to delete and/or replace files. What's your suggestion about that? Should we do such thing normally during development?
Example for file deletions / rpelacements: hsqldb-ds.xml, jms service xml files.

For example look at the "Tuning JBoss" section here:
https://www.darkcornersoftware.com/confluence/display/MINA/Installation+0.2.x

odysseas	Posted: April 07, 2010 20:39 by odysseas » Permalink
	The way we have OpenEMPI setup you don't need to define a JBoss Data Source in JNDI for it. OpenEMPI does not use the managed data source but rather creates its own connection pool so you don't need to configure postgresql-ds.xml. That is not to say that you couldn't change OpenEMPI to use a managed data source but that is not the default, out-of-the-box configuration.

Csaba Toth	Posted: April 08, 2010 13:56 by Csaba Toth » Permalink
	I want to use OpenEMPI the way it meant to be. I'll remove the Postgres-DS.xml. What about the JDBC driver jar? Should I put it anywhere any version?

odysseas	Posted: April 08, 2010 20:19 by odysseas » Permalink
	There is no reason to explicitly add a JDBC driver as one is included in the war file. In the future as we move towards supporting multiple databases, the JDBC will not be explicitly included in the war file. Odysseas

Csaba Toth	Posted: June 09, 2010 17:20 by Csaba Toth » Permalink
	So supporting multiple databases is not straight forward right now? That's what I'll have to do now somehow, because I want to do matching and not a deduplication.

Replies: 4 - Last Post: June 09, 2010 17:20
by: Csaba Toth

« Older Topic » Newer Topic