Query Retrieve using C MOVE and C GET - dcm4che/dcm4chee-arc-light GitHub Wiki

The test is to verify that Retrieve Cache is used when query/retrieve is being done from a Nearline storage. This means that object(s) are first copied to the retrieve cache from nearline and then sent to destination.

Note : It is assumed here, that series metadata accumulation is not enabled.

• Go to Configuration page of Archive UI, Devices tab and edit dcm4chee-arc device. Edit extension of Device Extension, next Edit extension of Archive Device and then to Attributes section.
• Ensure that one does NOT have any values set for fields Series Metadata Storage ID, Aggregate Series Metadata Delay and Update Series Metadata Polling Interval and Save.

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 a C-Move request on Study/Series/Instance level and verify the NumberOfRemainingSuboperations and NumberOfCompletedSuboperations in pending and final C-MOVE RSP. Also verify in the Wildfly server log that retrieve cache storage is being used for copying of object(s). Refer an example of log which shows the log of C-MOVE done on Study level and its corresponding Wildfly server logs. Verify Storage IDs of Study private attribute on Study/Series/Object level as fs1,retrieve-cache and Other Storage Sequence private attribute on Object level shall have the retrieve-cache storage ID.

3. Trigger a C-Get request on Study/Series/Instance level and verify the NumberOfRemainingSuboperations and NumberOfCompletedSuboperations in pending and final C-MOVE RSP. Also verify in the Wildfly server log that retrieve cache storage is being used for copying of object(s). Refer an example of log which shows the log of C-Get done on Series level and its corresponding Wildfly server logs. Verify Storage IDs of Study private attribute on Study/Series/Object level as fs1,retrieve-cache and Other Storage Sequence private attribute on Object level shall have the retrieve-cache storage ID.

4. Repeat the steps 2 and 3, for Studies/Series Level with some instances already on the retrieve cache. To do this you may either store additional objects of study (repeating point 1) and then trigger C-Move/C-Get; or do steps 2 and 3 on Series/Instance level and then then trigger C-Move/C-Get on Study level. Verify again the NumberOfRemainingSuboperations and NumberOfCompletedSuboperations in pending and final C-MOVE RSP. Also verify in the Wildfly server log that retrieve cache storage is being used for copying of object(s). Also verify Storage IDs of Study private attribute on Study/Series/Object level as fs1,retrieve-cache and Other Storage Sequence private attribute on Object level shall have the retrieve-cache storage ID.