tinashe
|
Posted: July 06, 2010 10:41 by tinashe
|
|
I have installed OpenEMPI/OpenPIXPDQ on Ubuntu Linux 10.04. Am running the two applications with the following configuration: 1) Jboss-4.0.5.GA 2) openpixpdq-1.1 3) openempi-2.0.4 4) sun-java-6 jdk 5) postgresql 8.4 I have copied the openpixpqd.war file and openempi-webapp-web-2.0.4 into the JBOSS_HOME/server/default/deploy..... Then copied the postgres adapter to ~/server/default/lib, as well as the openempi and openpixpdq adapters. also changed port on which Jboss is running...now port 80... the database which was requested when i ran Jboss initially was openempi2 and i created one and uploaded the schema in openempi-2.0.4/conf/create_database_schema.sql However, I would like to ask the following with regards to OpenEMPI installation on Linux: 1) is this the correct schema file to use, or use the one in openpixpdq 2) if it is, how can i correct the error when starting PIX/PDQ Server in OpenEMPI, where i get an error message that the iheActor.xml classpath cannot be resolved. 3) further more, i can create load the iheActor.xml file in PIX/PQD dashboard and select all servers to start running...PIX Manager, Supplier etc, and Register a new patient 4) However, the patient despite which gender i set to, is saved as female 5) Would like to information on how to start the PIX/PQD server in OpenEMPI and be able to search and manipulate patient information... 6) Would like to ask for more information on how to use OpenPIXPDQ Message Samples Thanks...in advance |
OpenEMPI/OpenPIXPDQ Integration: linux
Replies: 2 - Last Post: November 26, 2010 13:01
by: odysseas
by: odysseas
showing 1 - 3 of 3
Csaba Toth
|
Posted: November 23, 2010 17:58 by Csaba Toth
|
|
1.) I would always use the schema supplied with OpenEMPI, because that's what reflects the source code. If the schema doesn't reflect the persistent classes of the sourcecode, you'll get an error from the Hibernate ORM sublayer of the application. I don't know what schema is supplied with OpenPIXPDQ, but if you use OpenEMPI, always use it's own. 2.) I don't use PIX/PDQ, but I see that other people have problem about this. I think this issue will be addressed, or maybe it is already fixed? 4.) That's probably a bug, open up an issue about that 5.) After deploying OpenEMPI you can say Start PIXPDQ server and Stop PIXPDQ server in the admin menu. Sorry about the late answers. |
odysseas
|
Posted: November 26, 2010 13:01 by odysseas
|
|
1. You should use the schema that is provided with the OpenEMPI distribution to create the openempi database. I believe that it should be the same with that distributed with OpenPIXPDQ 1.1 but not sure about that. 2. This is an issue we unfortunately introduced in the 2.1.0 release which will be fixed in the 2.1.1 release coming up very soon. Here is a workaround until the next release. In a directory where you have the openempi-webapp-web-2.1.0.war file create the following two subdirectories WEB-INF WEB-INF/classes Copy the PIX/PDQ configuration files into the classes directory (IheActors.xml and all the files that it points to) Update the war file by adding the files through: jar uvf openempi-webapp-web-2.1.0.war WEB-INF You should now be able to deploy PIX/PDQ through the OpenEMPI console successfully. If you are still having trouble here, post another message and we will help you out. 3. We deploy PIX/PDQ into OpenEMPI as an embedded service so you don't need to deploy it separately yourself. 4. The issue you are seeing here is because you are using the OpenEMPI that is embedded within the OpenPIXPDQ release. As I mentioned in 3, we have embedded OpenPIXPDQ into our releases since we have a much more frequent release cycle and we are able to fix issues that come up and make them available to users more quickly. The issue you are describing has been resolved in the OpenEMPI adapter that is in our release but the release of OpenEMPI in OpenPIXPDQ is an older version and there won't be a release of OpenPIXPDQ until after the Connectathon next year, as far as I know. 5. If you succeed in starting OpenPIXPDQ then you should be able to use the OpenEMPI console to search for patients that are added/updated in the system through the PIX/PDQ interface. 6. There are message samples on the OpenPIXPDQ site that you can use. We also have a complete JUnit test suite for the PIX/PDQ interface that have message embedded within them. Let me know if you are able to make progress now. Odysseas |
Replies: 2 - Last Post: November 26, 2010 13:01
by: odysseas
by: odysseas







