WADO in CONQUEST 1.4.16

romeokaka · Apr 21st 2011

Hi,

help required on this issue.

New WADO option is added ing web server. I have tried to configure it with OVIYAM. This is the status window. OVIYAM search all data but unable to show images.

[CONQUESTSRV16] UPACS THREAD 218: STARTED AT: Thu Apr 21 10:26:42 2011
[CONQUESTSRV16] Calling Application Title : "OVIYAM "
[CONQUESTSRV16] Called Application Title : "CONQUESTSRV16 "
[CONQUESTSRV16] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 16352
[CONQUESTSRV16] Presentation Context 0 "1.2.840.10008.5.1.4.1.2.2.1" 1
[CONQUESTSRV16] (StudyRootQuery) search level: IMAGE
[CONQUESTSRV16] C-Find (StudyRoot) located 1 records
[CONQUESTSRV16] UPACS THREAD 218: ENDED AT: Thu Apr 21 10:26:42 2011
[CONQUESTSRV16] UPACS THREAD 218: TOTAL RUNNING TIME: 0 SECONDS

I have done the httpd.conf configuration acconding to ur previous posts.

Listen 3333
NameVirtualHost *:3333
<VirtualHost localhost:3333>
ServerAdmin mymail@server.org
DocumentRoot /
ServerName localhost
ErrorLog logs/wado-error.log
CustomLog logs/wado-access.log common
ScriptAlias / "D:/wamp/Apache2/cgi-bin/web6/dgate.exe/"
</VirtualHost>

i have tested these settings and working fine.

http://127.0.0.1:3333/dgate.exe i can search and view patients from this link. How the new WADO options will work.

Regards.

marcelvanherk · Apr 21st 2011

Hm,

The root of the web server should now be for you (i.e., without the dgate.exe):

http://127.0.0.1:3333

This port should also honor WADO requests. Is there any way you can moinitor the requests. The conquest log is a search. Maybe enable high level debug logging and see if it makes any requests? The find xxx on server option in the conquest web pages end at image level with WADO requests, so you can then see what they should look like in conquest logs. You (only) have to set the correct webscriptaddress in the dicom.ini in cgi-bin though.

Marcel

WADO in CONQUEST 1.4.16

Participate now!

Share