Retrieve Cache for Export - dcm4che/dcm4chee-arc-light GitHub Wiki

The test is to verify that Retrieve Cache is used when study is exported to a destination. This means that object(s) are first copied to the retrieve cache from nearline storage and then used for exporting the study to destination.

1. Store object(s) to archive using storescu tool

   storescu -c DCM4CHEE@hostname:11112 /path-tostudy                                             
   

   Below is a snippet of Request - Response logs

   13:10:41,374 INFO  - STORESCU->DCM4CHEE(1) << 1:C-STORE-RQ[pcid=7, prior=0
     cuid=1.2.840.10008.5.1.4.1.1.2 - CT Image Storage
     iuid=1.3.12.2.1107.5.8.1.12345678.199508041417040742898 - ?
     tsuid=1.2.840.10008.1.2 - Implicit VR Little Endian
   
   13:10:41,444 INFO  - STORESCU->DCM4CHEE(1) >> 1:C-STORE-RSP[pcid=7, status=0H
     cuid=1.2.840.10008.5.1.4.1.1.2 - CT Image Storage
     iuid=1.3.12.2.1107.5.8.1.12345678.199508041417040742898 - ?
     tsuid=1.2.840.10008.1.2 - Implicit VR Little Endian
   

2. Trigger Synchronous Export of study by going to Studies page of archive UI. One would see in the Wildfly server log as follows :

    16:24:02,194 DEBUG [org.dcm4chee.arc.retrieve.impl.CopyToRetrieveCacheTask] (default task-29) Got next finished copy to retrieve cache                                                                                                      
    16:24:02,194 DEBUG [org.dcm4chee.arc.retrieve.impl.RetrieveServiceImpl] (default task-29) Read Instance[
    iuid=1.3.12.2.1107.5.8.1.12345678.199508041417040742898,cuid=1.2.840.10008.5.1.4.1.1.2] from Location[pk=9688, 
    systemID=retrieve-cache, path=2018/05/28/5E9204E8/5E9C00D5/6459578D, tsuid=1.2.840.10008.1.2, size=529440, status=OK, objectType=DICOM_FILE]  
   

3. Repeat Step 1 and trigger Export of objects either using Export Rule as explained in Forwarding of received instances or go to Studies page and manually trigger an Export by selecting Queued Exporter option and selecting a DICOM Exporter. One would see again in the Wildfly server logs, log similar to the one indicated in Step 2.