Using online demo server

1,066 views
Skip to first unread message

Thibaut Bourquardez

unread,
Jan 26, 2015, 4:34:33 AM1/26/15
to dcm...@googlegroups.com
Hello, 

I'm trying to install weasis viewer for testing and seeing how to configure it in order connect it to an existing PACS server.

I would like to connect to online demo server (http://dicom.vital-it.ch:8089/dcm4chee-web3) but i don't know how to configure weasis. I installed it on JBoss AS 7

1) I downloaded weasis.war, weasis-pacs-connector.war and dcm4chee-web-weasis.jar

2) I putted weasis.war and weasis-pacs-connector.war into standalone\deployments directory (I commented the balise "exclude-subsystems" in the file jboss-deployment-structure.xml in the directory WEB-INF in weasis-pacs-connector.war - it caused errors when JBoss server started)

3) I created a module on JBoss 7 : modules\org\weasis\weasis-pacs-connector\main, where i putted dcm4chee-web-weasis.jar, and the file weasis-connector.properties
In this file, I tried to configure the connection to online demo server like this : 
pacs.aet=DCM4CHEE
pacs.host=130.223.121.62
pacs.port=11112

but it doesn't work. I get this error when i try to access this url : http://localhost:8080/weasis-pacs-connector/viewer?patientID=9702672 : 

10:07:59,192 ERROR [org.weasis.dicom.op.CFind] (pool-13-thread-2) findscu: Connection refused: connect: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method) [rt.jar:1.6.0_43]
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351) [rt.jar:1.6.0_43]
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213) [rt.jar:1.6.0_43]
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200) [rt.jar:1.6.0_43]
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) [rt.jar:1.6.0_43]
at java.net.Socket.connect(Socket.java:529) [rt.jar:1.6.0_43]
at org.dcm4che3.net.Connection.connect(Connection.java:951) [dcm4che-net-3.3.4.jar:3.3.4]
at org.dcm4che3.net.ApplicationEntity.connect(ApplicationEntity.java:541) [dcm4che-net-3.3.4.jar:3.3.4]
at org.dcm4che3.tool.findscu.FindSCU.open(FindSCU.java:237) [weasis-dicom-tools-0.9.6.jar:]
at org.weasis.dicom.op.CFind.process(CFind.java:148) [weasis-dicom-tools-0.9.6.jar:]
at org.weasis.dicom.wado.BuildManifestDcmQR.buildFromPatientID(BuildManifestDcmQR.java:65) [classes:]
at org.weasis.servlet.ServletUtil.getPatientList(ServletUtil.java:221) [classes:]
at org.weasis.dicom.wado.thread.ManifestBuilder.call(ManifestBuilder.java:73) [classes:]
at org.weasis.dicom.wado.thread.ManifestBuilder.call(ManifestBuilder.java:26) [classes:]
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [rt.jar:1.6.0_43]
at java.util.concurrent.FutureTask.run(FutureTask.java:138) [rt.jar:1.6.0_43]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [rt.jar:1.6.0_43]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [rt.jar:1.6.0_43]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_43]

I guess i may have to configure the wado server but i can't find any information : 
##### Base URL of the WADO server
pacs.wado.url=${server.base.url}/wado

Thank you for your help
Thibaut

Nicolas Roduit

unread,
Jan 26, 2015, 7:51:11 AM1/26/15
to dcm...@googlegroups.com
Yes, it is because the DCM4CHEE AET is not trusted for C-FIND (I don't give the public access for dicom operations). You can try with http://www.dicomserver.co.uk which accepts all the calling AET.

I haven't tried but it should work. The WADO server URL is:

Thibaut Bourquardez

unread,
Jan 26, 2015, 10:26:35 AM1/26/15
to dcm...@googlegroups.com
Thank you for the answer. 

Il connected successfully to dicomserver.co.uk (but i realized that the file weasis-connector.properties was not used even if it was in the module in JBoss 7.1.1, i must modify the file weasis-connector-default.properties into the war)

##########  PACS properties ########## 
# AET, hostname and port of the PACS
pacs.aet=DCM4CHEE
pacs.host=213.165.94.158
pacs.port=104

##### Base URL of the WADO server

It seems that it get some informations, it downloads things during about 2 minutes but images are not displayed. blank fields are displayed with "0%" in the left bar, but each ones disappears before being loaded...
It's very strange... 

I think i will install DCM4CHE and import some images to make tests.

Thanks

Nicolas Roduit

unread,
Jan 26, 2015, 11:53:29 AM1/26/15
to dcm...@googlegroups.com
You did not put the wado url that I gave you above.

Thibaut Bourquardez

unread,
Jan 27, 2015, 3:39:14 AM1/27/15
to dcm...@googlegroups.com
Hello, 
yes i did but i changed to see if it would work better... but not

##########  PACS properties ########## 
# AET, hostname and port of the PACS
pacs.aet=DCM4CHEE
pacs.port=11112

##### Base URL of the WADO server

When i call this url : 

in java console, i have those errors : 
...
27.01.2015 09:32:53.807 *ERROR* [pool-35-thread-4]() org.weasis.core.api.util.FileUtil Not a DICOM file
27.01.2015 09:32:53.808 *ERROR* [pool-35-thread-3]() org.weasis.core.api.util.FileUtil Not a DICOM file
...

It seems that the viewer can't open images it received, maybe not proper format

Thibaut Bourquardez

unread,
Jan 27, 2015, 3:57:14 AM1/27/15
to dcm...@googlegroups.com
My apologies, actually it works!!

i didn't properly saved the configuration file into the war : 


##########  PACS properties ########## 
# AET, hostname and port of the PACS
pacs.aet=DCM4CHEE
pacs.host=213.165.94.158
pacs.port=11112


##### Base URL of the WADO server

Thank you... 

The only problem remaining is that it doesn"t seem to take care of the weasis-connector.properties file placed into jboss 7.1.1 module...  

Thibaut Bourquardez

unread,
Jan 27, 2015, 4:35:48 AM1/27/15
to dcm...@googlegroups.com
Finally, i solved my problem of jboss module...

I shouldn't rename weasis-connector-default.properties to weasis-connector.properties. 

So, in summary, to make it works with jboss AS 7.1.1 : 

1) I downloaded weasis.war and weasis-pacs-connector.war

2) I putted weasis.war and weasis-pacs-connector.war into standalone\deployments directory 

3) I commented the balise "exclude-subsystems" in the file jboss-deployment-structure.xml in the directory WEB-INF in weasis-pacs-connector.war - it caused errors when JBoss server started (unknown balise)

4) I created a module on JBoss 7 : modules\org\weasis\weasis-pacs-connector\main, where i putted and the file weasis-connector-default.properties
In this file, I configure the connection to online demo server www.dicomserver.co.uk like this : 
##########  PACS properties ########## 
# AET, hostname and port of the PACS
pacs.aet=DCM4CHEE
pacs.host=213.165.94.158
pacs.port=11112

##### Base URL of the WADO server


When i try to access to the patient 123456789 : http://localhost:8080/weasis-pacs-connector/viewer?patientID=123456789 it works!!

Thank you for your help!

Nicolas Roduit

unread,
Jan 28, 2015, 2:12:50 AM1/28/15
to dcm...@googlegroups.com
Did you follow the instructions here for configuring the module of JBoss? I think the problem comes from the version of JBoss you are using (it is recommended to use 7.2+ or 8.x).
Reply all
Reply to author
Forward
0 new messages