DCM4CHE Apparent Conflict

Historical record of a forum that was for discussion of the setup, configuration, and use of OnePacs for research and educational purposes (non-clinical use).

Please direct any support inquiries through the standard OnePacs ticketing and support system.

The "Announcements" forum will continue to be active and contain announcements related to the OnePacs system.
Locked
jacintor
Posts: 85
Joined: Fri Nov 23, 2012 5:56 am

DCM4CHE Apparent Conflict

Post by jacintor » Tue Nov 17, 2015 7:39 am

Hello,

One of our clients keeps complaining that they cannot send us studies every now and then. In the past, the solution was restarting the computer and CT scan. However, this is no longer working. We have found our that the client is using a second teleradiology group, whose software is also based on DCM4CHE. Our gateway portal does not even open anymore. We have already reinstalled the gateway 4 times and we keep getting the same message on the browser (Google Chrome): HTTP Status 404 - /onepacsgateway. The request source /onepacsgateway is not available.

There are two postgre versions installed: 9.2 (onepacs) and 9.3 (competitor).

How can we solve this besides asking the client to buy a new computer dedicated to us? Should we uninstall postgre version 9.2 or 9.3?

Please send us your suggestions.

Thanks!

Rodrigo

jeremy
Posts: 140
Joined: Wed Nov 26, 2008 8:34 am

Re: DCM4CHE Apparent Conflict

Post by jeremy » Tue Nov 17, 2015 10:16 am

Hello -

The recommendation from the Gateway installation guide https://onepacshelp.com/display/T5/OneP ... tion+Guide is that "Software - The computer should only be used for the OnePacs Gateway." Therefore, it is recommended that the OnePacs Gateway be installed on its own computer (either real or virtual). Generally speaking, a computer that fits the minimum requirements for the OnePacs Gateway can be acquired for a very modest price.

You should NOT generally uninstall either version of postgresql as uninstalling any database server would likely render any dependent applications unavailable and would remove relevant data.

Without knowing other specifics it is difficult to give other advice.

1. The Gateway may be running into port conflicts and you may attempt to run it using alternative ports.

Stop the OnePacs Gateway service in the windows services
Edit the file at C:\onepacs\gateway\server\default\conf\jboss-service.xml
Replace "ports-onepacs" with "ports-onepacs-alt"
Save the file
Restart the service
If successful, change desktop shortcuts and start menu shortcuts to use port 18080 instead for the gateway and jmx shortcuts for the gateway web application (portal). http://localhost:18080/onepacsgateway

2. Depending on the existing hardware, the client may consider using virtual environments.

Regards

Locked