WEASIS does not work in dcm4chee-arc

[Alexandr Kuznetsov]

Hello. My rain dance have been going on for two days. but I can’t configure the connection of weasis to dcm4chee-arc.

Applications installed on the server:

Values
IID_STUDY_URL = https: //192.168.88.62: 8443 / IHEInvokeImageDisplay? RequestType = STUDY & studyUID = {}
IID_PATIENT_URL = https: //192.168.88.62: 8443 / IHEInvokeImageDisplay? RequestType = PATIENT & patientID = {}
or
IID_STUDY_URL = http: //192.168.88.62: 8080 / IHEInvokeImageDisplay? RequestType = STUDY & studyUID = {}
IID_PATIENT_URL = http: //192.168.88.62: 8080 / IHEInvokeImageDisplay? RequestType = PATIENT & patientID = {}
lead to 404 error - Not Found

Values
IID_STUDY_URL = https: //192.168.88.62: 8443 / weasis-pacs-connector / weasis? & StudyUID = {} & target = _self & access_token = {}
IID_PATIENT_URL = https: //192.168.88.62: 8443 / weasis-pacs-connector / weasis? & PatientID = {} & target = _self & access_token = {}
or
IID_STUDY_URL = .. / .. / weasis-pacs-connector / weasis? & StudyUID = {} & target = _self & access_token = {}
IID_PATIENT_URL = .. / .. / weasis-pacs-connector / weasis? & PatientID = {} & target = _self & access_token = {}
A suggestion about opening in some application appears.

My server.log:

But neither javaws, established weasis does not open the link.. What am I doing wrong???

I would be grateful for any answer.

Thank you for your time.

[Shefki Esadi]

Hi,
try something like this:

`IID_STUDY_URL=https://192.168.88.62:8443/weasis-pacs-connector/weasis?studyUID={}&target=_self`
`IID_PATIENT_URL=https://192.168.88.62:8443/weasis-pacs-connector/weasis?patientID={}&target=_self`

It seams that weasis changed the strucutr of the url, for this structure you have to have the newest changes of the UI otherwise it will not work see this issue that I fixed;

Best Regards
Shefki Esadi

[Alexandr Kuznetsov]

Thanks for the answer.

But that does not work. The browser opens a new window and offers to select a program to open the link.

Is this related to version 21?
Or put an older weasis?

среда, 4 марта 2020 г., 12:02:19 UTC+2 пользователь Shefki Esadi написал:

[Vrinda Nayak]

Have you installed Weasis package on your system correctly and followed all other steps as mentioned here. I have updated Invoke Image Display wiki page to reflect the urls used by latest versions of Weasis.

[Alexandr Kuznetsov]

Thanks for the answer.

I apologize for my stupidity. :)

Yes, I followed the steps described in https://nroduit.github.io/en/getting-started/dcm4chee/#for-dcm4chee-arc-light
And here https://github.com/dcm4che/dcm4chee-arc-light/wiki/Invoke-Image-Display
in the section Using Archive UI -> Secure Archive (both UI and RESTful secured)

Do you need to use the Archive UI and LDAP configuration at the same time?
Do I need to enter the LDAP container to use:

docker exec -i -t ldap /bin/sh ??

"Using LDAP

One may either create a LDIF file and import it to the LDAP Server by using the ldapmodify command line utility."

How to do it?

I went to the LDAP server and created a file weasis.ldif with the given contents.
Then I entered the command

ldapmodify -x -f weasis.ldif

Received:
modifying entry "dcmWebAppName = DCM4CHEE, dicomDeviceName = dcm4chee-arc, cn = Devices, cn = DICOM Configuration, dc = dcm4che, dc = org"
ldap_modify: Strong (er) authentication required (8)
additional info: modifications require authentication

Respectfully,

Alexandr

среда, 4 марта 2020 г., 15:25:02 UTC+2 пользователь Vrinda Nayak написал:

[Vrinda Nayak]

- Do you need to use the Archive UI and LDAP configuration at the same time?

No, either update the configuration using archive UI or using LDAP.

[Alexandr Kuznetsov]

I couldn’t do it in any way, nor in another.
It looks like my dances with a tambourine will be long. Or I will be disappointed with this server and will use the good old 2.18.3

The setting is very user-unfriendly. :(

среда, 4 марта 2020 г., 19:27:26 UTC+2 пользователь Vrinda Nayak написал:

[Vrinda Nayak]

Make sure you have the

- latest versions of weasis.war and weasis-pacs-connector.war deployed in your wildfly. Also, in your $WILDFLY_HOME/standalone/configuration location, dicom-dcm4chee-arc.properties and weasis-pacs-connector.properties files are present.

- DCM4CHEE Web Application has the IID_STUDY_URL and IID_PATIENT_URL configured. Since you are using secure version, your URLs shall be

         IID_PATIENT_URL=../../weasis-pacs-connector/weasis?patientID={}&access_token={}&target=_self

    IID_STUDY_URL=../../weasis-pacs-connector/weasis?studyUID={}&access_token={}&target=_self

- Depending on your operating system, weasis package has been installed as a software.

[Alexandr Kuznetsov]

Hi!

dcm4chee-arc deployed in a docker on the  Debian 10 virtual server.

I reinstalled everything again according to the instructions. I enclose screenshots.
I look through the archive in the Mozilla browser in Xubuntu 18.04. Also in Windows 10.
Both systems have weasis 3.5.4 installed/
To Xubuntu from the package weasis_3.5.4-1_amd64.deb. In Windows installer Weasis-3.5.4-x86-64.msi.

The result is the same.

When you click on the eye icon, it is suggested to launch the link in the Weasis application. But no action is taken.
I'm desperate

In this case, the following is displayed in the log:

2020-03-05 21:07:56,503 INFO  [org.dcm4chee.arc.export.mgt.impl.ExportScheduler] (EE-ManagedScheduledExecutorService-default-Thread-4) start ExportScheduler.execute()
2020-03-05 21:07:56,506 INFO  [org.dcm4chee.arc.export.mgt.impl.ExportScheduler] (EE-ManagedScheduledExecutorService-default-Thread-4) finished ExportScheduler.execute()
2020-03-05 21:08:14,646 INFO  [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Accept connection Socket[addr=/127.0.0.1,port=33485,localport=11112]
2020-03-05 21:08:14,648 INFO  [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-39) DCM4CHEE<-PACS-CONNECTOR(18) >> A-ASSOCIATE-RQ
2020-03-05 21:08:14,648 INFO  [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-39) DCM4CHEE<-PACS-CONNECTOR(18) << A-ASSOCIATE-AC
2020-03-05 21:08:14,649 INFO  [org.dcm4che3.net.Dimse] (EE-ManagedExecutorService-default-Thread-39) DCM4CHEE<-PACS-CONNECTOR(18) >> 1:C-FIND-RQ[pcid=1, prior=0
  cuid=1.2.840.10008.5.1.4.1.2.2.1 - Study Root Query/Retrieve Information Model - FIND
  tsuid=1.2.840.10008.1.2 - Implicit VR Little Endian]
2020-03-05 21:08:14,649 INFO  [org.dcm4chee.arc.query.scp.CommonCFindSCP] (EE-ManagedExecutorService-default-Thread-39) DCM4CHEE<-PACS-CONNECTOR(18): Process C-FIND RQ:
(0008,0020) DA [] StudyDate
(0008,0030) TM [] StudyTime
(0008,0050) SH [] AccessionNumber
(0008,0052) CS [STUDY] QueryRetrieveLevel
(0008,0090) PN [] ReferringPhysicianName
(0008,1030) LO [] StudyDescription
(0010,0010) PN [] PatientName
(0010,0020) LO [] PatientID
(0010,0021) LO [] IssuerOfPatientID
(0010,0030) DA [] PatientBirthDate
(0010,0040) CS [] PatientSex
(0020,000D) UI [{}] StudyInstanceUID
(0020,0010) SH [] StudyID

2020-03-05 21:08:14,659 INFO  [org.dcm4che3.net.Dimse] (EE-ManagedExecutorService-default-Thread-40) DCM4CHEE<-PACS-CONNECTOR(18) << 1:C-FIND-RSP[pcid=1, status=0H
  cuid=1.2.840.10008.5.1.4.1.2.2.1 - Study Root Query/Retrieve Information Model - FIND
  tsuid=1.2.840.10008.1.2 - Implicit VR Little Endian]
2020-03-05 21:08:14,660 INFO  [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-39) DCM4CHEE<-PACS-CONNECTOR(18) >> A-RELEASE-RQ
2020-03-05 21:08:14,661 INFO  [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-39) DCM4CHEE<-PACS-CONNECTOR(18) << A-RELEASE-RP
2020-03-05 21:08:14,714 INFO  [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) DCM4CHEE<-PACS-CONNECTOR(18): close Socket[addr=localhost/127.0.0.1,port=33485,localport=11112]
2020-03-05 21:08:40,565 INFO  [org.dcm4chee.arc.audit.AuditScheduler] (EE-ManagedScheduledExecutorService-default-Thread-2) start AuditScheduler.execute()
2020-03-05 21:08:40,567 INFO  [org.dcm4che3.net.audit.AuditLogger] (EE-ManagedScheduledExecutorService-default-Thread-2) Send audit message to /127.0.0.1:514
2020-03-05 21:08:40,568 INFO  [org.dcm4chee.arc.audit.AuditScheduler] (EE-ManagedScheduledExecutorService-default-Thread-2) finished AuditScheduler.execute()
2020-03-05 21:08:43,728 INFO  [org.dcm4chee.arc.ian.scu.IANScheduler] (EE-ManagedScheduledExecutorService-default-Thread-2) start IANScheduler.execute()
2020-03-05 21:08:43,734 INFO  [org.dcm4chee.arc.ian.scu.IANScheduler] (EE-ManagedScheduledExecutorService-default-Thread-2) finished IANScheduler.execute()

In Xubuntu, only the initial Weasis logo is displayed and immediately disappears. In Windows 10, nothing happens at all.

I hope for help

Good luck!

четверг, 5 марта 2020 г., 11:37:26 UTC+2 пользователь Vrinda Nayak написал:

[Vrinda Nayak]

The archive logs look fine. My installation with archive and weasis (where it works as shown in screenshots attached in previous post) is on linux.
Someone from weasis team needs to help out here.

[Alexandr Kuznetsov]

But it doesn’t work for me, both in Linux and Windows. Although weasis is installed and works locally well.

Thanks for the answer and the time I have taken.

I hope someone from the weasis team helps :)

Best regards!

четверг, 5 марта 2020 г., 22:06:48 UTC+2 пользователь Vrinda Nayak написал:

[Wagner Castro]

On Linux install icedtea and do a test.

--
You received this message because you are subscribed to the Google Groups "dcm4che" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dcm4che/10cb62ca-9005-41a8-affb-5de0d7ef808d%40googlegroups.com.

--

[Alexandr Kuznetsov]

Thanks for the advice. IcedTea installed :)

пятница, 6 марта 2020 г., 19:07:05 UTC+2 пользователь Wagner Castro написал:

On Linux install icedtea and do a test.

Em sex., 6 de mar. de 2020 às 12:48, Alexandr Kuznetsov <alexandr....@gmail.com> escreveu:

But it doesn’t work for me, both in Linux and Windows. Although weasis is installed and works locally well.

Thanks for the answer and the time I have taken.

I hope someone from the weasis team helps :)

Best regards!

четверг, 5 марта 2020 г., 22:06:48 UTC+2 пользователь Vrinda Nayak написал:

The archive logs look fine. My installation with archive and weasis (where it works as shown in screenshots attached in previous post) is on linux.
Someone from weasis team needs to help out here.

--
You received this message because you are subscribed to the Google Groups "dcm4che" group.

To unsubscribe from this group and stop receiving emails from it, send an email to dcm...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/dcm4che/10cb62ca-9005-41a8-affb-5de0d7ef808d%40googlegroups.com.

--

[Nicolas Roduit]

Unfortunately, there have been several changes in the different components and there are several ways to configure the integration of Weasis into dcm4chee, which can make quite a few combinations possible. Try to use the new release.

For a quick installation, I advise you to simply configure the 2 properties without using weasis-pacs-connector (without any server-side installation), then just install Weasis (native installer) on your running system and that's all.

It would be nice to only have to configure docker-compose.env for running Weasis from dcm4chee UI, for instance:

IID_PATIENT_URL=weasis://$dicom:rs --url "http://192.168.0.31:8080/dcm4chee-arc/aets/DCM4CHEE/rs" -r "&patientID={}" --query-ext "&includedefaults=false" -H "Authorization: &access_token={}"

IID_STUDY_URL=weasis://$dicom:rs --url "http://192.168.0.31:8080/dcm4chee-arc/aets/DCM4CHEE/rs" -r "&studyUID={}" --query-ext "&includedefaults=false" -H "Authorization: &access_token={}"

It doesn't work for me even though these 2 variables are dcm4che-slapd environment variables. Another improvement will be to have a variable to get the RS URL of dcm4chee.

For a more advanced installation with weasis-pacs-connector, follow this documentation. Let me know if there's anything wrong.

In the next release, I will try to provide a docker package for weasis-pacs-connector and weasis.

[Vrinda Nayak]

Regarding the 2 dcm4che-slapd environment variables issue, related issue has been re-opened and fixed.

[gunterze]

Correct link to corresponding issue: https://github.com/dcm4che/dcm4chee-arc-light/issues/2241

[Luis Alberto Caballero Perez]

Tengo la solucion, por un modico costo les puedo hacer la reconfiguracion de su servidor, todo inbox. saludos.

[Alexandr Kuznetsov]

Thank you all for the answers.

In the new version 5.22 and Weasis 3.6.0 everything works fine.

вторник, 3 марта 2020 г., 20:07:30 UTC+2 пользователь Alexandr Kuznetsov написал:

[Nicolas Roduit]

I've just updated the documentation to make it a little clearer.

[zaka]

Hello!

I've done clean test install of dcm4chee-arc v5.22.2 in unsecured mode and everything seems work fine, except for Weasis (3.0.6). When I try to open a patient or a study in the viewer, Weasis starts and fires "No images have been found with given parameters"! The arc's log also confirms this problem:

00:27:50,363 INFO  [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Accept connection Socket[addr=/127.0.0.1,port=55197,localport=8104]
00:27:50,386 INFO  [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-5) DCM4CHEE<-PACS-CONNECTOR(1) >> A-ASSOCIATE-RQ
00:27:50,389 INFO  [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-5) DCM4CHEE<-PACS-CONNECTOR(1) << A-ASSOCIATE-AC
00:27:50,424 INFO  [org.dcm4che3.net.Dimse] (EE-ManagedExecutorService-default-Thread-5) DCM4CHEE<-PACS-CONNECTOR(1) >> 1:C-FIND-RQ[pcid=1, prior=0

  cuid=1.2.840.10008.5.1.4.1.2.2.1 - Study Root Query/Retrieve Information Model - FIND
  tsuid=1.2.840.10008.1.2 - Implicit VR Little Endian]

00:27:50,453 INFO  [org.dcm4chee.arc.query.scp.CommonCFindSCP] (EE-ManagedExecutorService-default-Thread-5) DCM4CHEE<-PACS-CONNECTOR(1): Process C-FIND RQ:

(0008,0020) DA [] StudyDate
(0008,0030) TM [] StudyTime
(0008,0050) SH [] AccessionNumber
(0008,0052) CS [STUDY] QueryRetrieveLevel

(0008,0061) CS [] ModalitiesInStudy

(0008,0090) PN [] ReferringPhysicianName
(0008,1030) LO [] StudyDescription
(0010,0010) PN [] PatientName
(0010,0020) LO [{}] PatientID
(0010,0021) LO [] IssuerOfPatientID
(0010,0030) DA [] PatientBirthDate
(0010,0040) CS [] PatientSex
(0020,000D) UI [] StudyInstanceUID
(0020,0010) SH [] StudyID

00:27:50,477 INFO  [org.dcm4che3.net.Dimse] (EE-ManagedExecutorService-default-Thread-6) DCM4CHEE<-PACS-CONNECTOR(1) << 1:C-FIND-RSP[pcid=1, status=0H

  cuid=1.2.840.10008.5.1.4.1.2.2.1 - Study Root Query/Retrieve Information Model - FIND
  tsuid=1.2.840.10008.1.2 - Implicit VR Little Endian]

00:27:50,485 INFO  [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-5) DCM4CHEE<-PACS-CONNECTOR(1) >> A-RELEASE-RQ
00:27:50,486 INFO  [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-5) DCM4CHEE<-PACS-CONNECTOR(1) << A-RELEASE-RP
00:27:50,511 INFO  [stdout] (pool-13-thread-1) 2020-06-01 00:27:50,497 [ool-13-thread-1] WARN  o.w.d.m.t.ManifestBuilder Empty patient list
00:27:50,514 INFO  [stdout] (pool-13-thread-1) 2020-06-01 00:27:50,514 [ool-13-thread-1] INFO  o.w.d.m.t.ManifestBuilder Build Manifest in 227 ms [id=1]
00:27:50,547 INFO  [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) DCM4CHEE<-PACS-CONNECTOR(1): close Socket[addr=localhost/127.0.0.1,port=55197,localport=8104]

So what I did wrong? I've only changed default dicom port to 8104. DCM4CHE's utils (5.22.2) and Horos works fine.

суббота, 21 марта 2020 г., 21:48:07 UTC+5 пользователь Nicolas Roduit написал:

[Santiago Gala]

The format for IID_STUDY_URL has changed, now instead of {} you should use {{patientID}} . The documentation is not yet fixed, I guess...

See change in issue #2540: https://github.com/dcm4che/dcm4chee-arc-light/issues/2540 

Regards

Santiago

--
You received this message because you are subscribed to the Google Groups "dcm4che" group.

To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dcm4che/a178d611-c13b-48ea-93e6-2512cce2601b%40googlegroups.com.

[Nicolas Roduit]

Yes, the configuration has changed and I just updated the documentation, see this post.

To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+unsubscribe@googlegroups.com.

[zaka]

Thanks! Weasis start working with correct IID_PATIENT_URL and IID_STUDY_URL. But 'IID_PATIENT_URL_TARGET=_self' and 'IID_STUDY_URL_TARGE=_self' doesn't avoid to open a new empty window in the browser (Firefox). May be a 'IID_STUDY_URL_TARGE' is a typo? Anyway 'IID_STUDY_URL_TARGE' or 'IID_STUDY_URL_TARGET' breaks Weasis launching on study level for me.

понедельник, 1 июня 2020 г., 17:27:19 UTC+5 пользователь Nicolas Roduit написал:

To unsubscribe from this group and stop receiving emails from it, send an email to dcm...@googlegroups.com.

[Nicolas Roduit]

The target parameter is IID_URL_TARGET=_self and it cannot be passed directly in the docker-compose.env file.

[Gunter Zeilinger]

On Tuesday, June 2, 2020 8:21 AM, Nicolas Roduit <nicolas...@gmail.com> wrote:

The target parameter is IID_URL_TARGET=_self and it cannot be passed directly in the docker-compose.env file.

Should work now. Pushed dcm4che/slapd-dcm4chee:2.4.48-22.2 including the fix. So re-pulling

$ docker pull dcm4che/slapd-dcm4chee:2.4.48-22.2

should be sufficient.

dcm4che-dockerfiles/slapd-dcm4chee:2.4.48-22.2

To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/dcm4che/b9c3c5c7-813f-417d-8b80-1fc9b68382b8%40googlegroups.com.

[Nicolas Roduit]

After updating dcm4che/slapd-dcm4chee:2.4.48-22.2 and from a fresh installation, IID_URL_TARGET=_self is imported from docker-compose.env as expected but the value of IID_STUDY_URL is not imported. And IID_PATIENT_URL is imported correctly.

On Tuesday, June 2, 2020 at 12:33:15 PM UTC+2, gunterze wrote:

[Gunter Zeilinger]

Oops. Should be fixed. re-pull dcm4che/slapd-dcm4chee:2.4.48-22.2.

Thx, gunter

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

To view this discussion on the web visit https://groups.google.com/d/msgid/dcm4che/f797d150-3393-45e9-a421-bfd379a0fd89%40googlegroups.com.