integration with dcm4chee-arc v5.22.6 #36
Comments
|
Any help ? |
|
I don't know where did you get the configuration but it doesn't match to the documentation, you can make the integration:
|
|
actually i follow these steps in link https://nroduit.github.io/en/getting-started/dcm4chee/#for-dcm4chee-arc-light i hope quickly answer. |
|
Your configuration doesn't match of the two possible configurations (first used weasis version at the server side, second only used the client installation): IID_PATIENT_URL=../../weasis-pacs-connector/weasis?patientID={{patientID}}&access_token={{access_token}} IID_PATIENT_URL=../../weasis-pacs-connector/weasis?patientID={{patientID}}&cdb&access_token={{access_token}} If it doesn't work, you should have a look on weasis-pacs-connector logs (from wildfly console) or dcm4chee logs. Did you try the most simple configuration: https://nroduit.github.io/en/basics/customize/integration/#download-directly-with-dicomweb-restful-services |
|
Thanks a lot for reply . these line from server.log in dcm4chee : 2020-12-23 12:40:36,178 INFO [org.dcm4che3.net.Dimse] (EE-ManagedExecutorService-default-Thread-12) DCM4CHEE<-PACS-CONNECTOR(4) << 1:C-FIND-RSP[pcid=1, status=ff00H 2020-12-23 12:40:36,234 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-5) DCM4CHEE<-PACS-CONNECTOR(4): close Socket[addr=localhost/127.0.0.1,port=54639,localport=11112] 2020-12-23 12:40:36,300 INFO [org.dcm4che3.net.Dimse] (EE-ManagedExecutorService-default-Thread-12) DCM4CHEE<-PACS-CONNECTOR(6) << 1:C-FIND-RSP[pcid=1, status=ff00H |
|
In logs everything seems to be OK. The manifest is created. The configuration of the URLs mentioned above is still wrong: -IID_STUDY_URL=../../weasis-pacs-connector/weasis?&studyUID={{studyUID}}&target=_self&access_token={{access_token}}
+IID_PATIENT_URL=../../weasis-pacs-connector/weasis?patientID={{patientID}}&access_token={{access_token}}
-IID_PATIENT_URL=../../weasis-pacs-connector/weasis?&patientID={{patientID}}&target=_self&access_token={{access_token}}
+IID_STUDY_URL=../../weasis-pacs-connector/weasis?studyUID={{studyUID}}&access_token={{access_token}}but it seems that importing URL from a Docker environment variable requires to escape '&' or try without weasis-pacs-connector: |
|
could u tell me where i check logs , manifest ? |
|
I'm not sure that dcm4chee update the URLs from Docker environment variable, so could you provide here the values from dcm4chee: Configuration > Devices > dcm4chee-arc > Extensions > Edit extension > Child Objects > Web Applications > DCM4CHEE |
|
this from UI as you refer |
|
It seems correct. So the problem is else where. Can you open weasis from https://nroduit.github.io/en/demo/ |
|
yes, it's work to open weasis if i install locally and click launch from demo page. |
|
Read the last item of Warning box |
|
i know last issue from certificate |
|
This is an expected behavior. If you replace 'weasis' by 'viewer' in the URLs it will used Java Webstart (not recommended and requires an installation of Java 8 on the client). Some more information: |
|
Thanks for reply |
|
Which issue? |
|
Not open weais viewer from dcm4chee if remove weasis from local machine. |
|
As I said above it is an expected behavior when using weasis-protocol. |
|
so, it's issue from dcm4chee side ? |
|
It is not an issue but a requirement. The 'weasis://' URI must be registered with a local installation of Weasis. |
|
so, if i not install weasis locally we can not open viewer right ? |
|
Yes, if you are on Windows, it should suggest an App from the Microsoft Store where Weasis is registered. |
|
It works in the same way as you smart phone when requiring a specific application. |
|
thanks for your time . |
|
i am sorry for more interruption |
|
weasis-pacs-connector is a service that generates the launch configuration and the xml manifest for the images. So you need to follow the syntax described here. The second configuration is a direct configuration of the launcher inside the URI (with parameters that are injected by dcm4chee or other PACS) and the XML is build on the client side (from Weasis 3.6.0). If you do not have specific needs you should use this configuration. |
Weais viewer not running but query reach to dcm4chee
steps : 1- deploy weasis.war,weasis-pacs-connector.war to wildlfy using http
configure dcm4chee by adding
IID_PATIENT_URL=../../weasis-pacs-connector/weasis?&patientID={}&target=_self
IID_STUDY_URL=../../weasis-pacs-connector/weasis?&studyUID={}&target=_self
Also for
IID_PATIENT_URL=http://localhost:8080/weasis-pacs-connector/weasis://$dicom:rs --url "http://192.168.1.7:8080/dcm4chee-arc/aets/DCM4CHEE/rs/studies" -r "&patientID=2168068" -r " --query-ext "&includedefaults=false"
IID_STUDY_URL=http://localhost:8080/weasis-pacs-connector/weasis://$dicom:rs --url "http://192.168.1.7:8080/dcm4chee-arc/aets/DCM4CHEE/rs/studies" -r "&studyID=1.2.840.113619.2.358.3.2831172914.667.1504680361.584" -r " --query-ext "&includedefaults=false"
Not query or open weasis viewer
also, how to enable logging in log server of dcm4chee arc (jboss wildfly) for weasis and weasis-pacs-connector
For dcm4hcee secure version 5.22.6 if i install weasis viewer locally (.deb package) :
if using http it open and running but if calling using https it open without any images and give error
"issue for certificate is : error in loading xml maifest from https://URL:8443/weasis-pacs-connector/RequestManifest?id=13"
"server response : javax.net.ssl.sshHandshakeException: PKIX path building failed: sun.security.provider.certpath"
The text was updated successfully, but these errors were encountered: