Developer testing c‐move - fli-iam/shanoir-ng GitHub Wiki

It can be challenging on the local dev environment to test the "download from PACS" feature. Here is how it works under Linux. The challenge is, that when you call the c-move on the pacs, the pacs has to resolve to the localhost from within his docker container to the "outside" ShUp:

  • Start your local Shanoir server instance, either with "docker compose up -d" or the "bootstrap.sh"

  • The backup PACS/DICOM server of Shanoir server starts automatically, as one microservice: dcm4chee-arc

  • You can import a dataset using the web GUI of Shanoir with a DICOM-ZIP file, to import data into the PACS

  • Access to the web GUI of dcm4chee-arc under http://localhost:8081/dcm4chee-arc/ui2/study/study

  • Click on submit to verify, if you have some DICOM files present after the import (to search and download)

  • Now switch to configure and add a new AET: http://localhost:8081/dcm4chee-arc/ui2/device/aelist

  • Create a new AET

  1. New device: name shanoir-uploader, enter "asdf" as institution name (if not I had storage errors), configure Installed true
  2. New network connection: name to shanoir-uploader and enter 172.17.0.1 as hostname and 44105 as port
  3. Network AE: enter SHANOIR-UPLOADER
  4. Set the new AE as "Accepted calling": select DCM4CHEE from the list and check the box

  • Click on apply to create the new AET

  • For ShanoirUploader: open the dicom_server.properties and change to local.dicom.server.host=172.17.0.1

  • Now start ShUp: you should be able to query with c-find and c-move the dcm4chee-arc DICOM server, when clicking on downloadOrCopy