Export Triggered Storage Commitment

Overview

Choose to trigger storage commitment of objects once they have been exported to the destination to ensure that the destination explicitly takes the responsibility for the safekeeping of the data into account.

Configuration

• Configure a Remote Application Entity for each of the system(s) acting as destination(s). Ensure that this destination is able to receive and respond to Storage Commitment requests.
• Also add a DICOM Exporter for each destination.
• Ensure that the Exporter has value configured for Storage Commitment SCP AE Title.

Storage Commitment may be triggered by :

• Export Rule Triggered Storage Commitment
• UI Export Triggered Storage Commitment

Testing

For testing purpose,

• Configure DCMQRSCP as a Remote Application Entity, since dcmqrscp tool can be used to simulate the Storage Commitment SCP.

• Additionally, you need to modify the Exporter you created above.

  • Using Archive UI : Go to Menu->Configuration, then on Devices page click on Edit of the dcm4chee-arc device. Go to Extensions and Edit extension of Device Extension. Again go to its Extensions and Edit extension of Archive Device. Go to its Child Objects and select the Exporter you created above. Modify the URI field to have value as dicom:DCMQRSCP. Add value in the field Storage Commitment SCP AE Title as DCMQRSCP and click Save.

  • Using LDAP : You may either create a LDIF file (e.g.):

      version: 1
      dn: dcmExporterID=STORESCP,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
      changetype: modify
      replace: dcmURI
      dcmURI: dicom:DCMQRSCP
      
      dn: dcmExporterID=STORESCP,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
      changetype: modify
      add: dcmStgCmtSCP
      dcmStgCmtSCP: DCMQRSCP
    

    and import it to the LDAP Server by using the ldapmodify command line utility.

    OR use the Add Attribute... and Add Value... function of Apache Directory Studio to add attributes on Exporter Descriptor level (e.g.: dcmExporterID=STORESCP) in the Archive Configuration.

Required dcm4che tools

• storescu (needed only for rule based export), simulating the external object source (e.g. modality) STORESCU, from which objects are being received.
• dcmqrscp simulating the storage commitment SCP

Verification

1. Add (as shown below) to one's dcm4che-tools/etc/dcmqrscp/ae.properties

         DCM4CHEE=localhost:11112
   

2. Start the dcmqrscp tool as shown below

         dcmqrscp -b DCMQRSCP:11113 --dicomdir /tmp/DICOMDIR
   

Monitoring Storage Commitment SCU Tasks

Go to the Menu->Monitoring page and click on Queues tab.

• Select Storage Commitment SCU Tasks from Queue dropdown, set one or more filters and query for the Storage Commitment SCU tasks. Count of Storage Commitment SCU tasks may also be obtained.
• One may reschedule/cancel/delete a single Storage Commitment SCU Task (icons available against each task, hover for info).
• For rescheduling bulk Storage Commitment SCU Tasks, select a Status and Reschedule all matching tasks from the All actions dropdown.
• For cancelling bulk Storage Commitment SCU Tasks, select either SCHEDULED or IN PROCESS as Status and Cancel all matching tasks from the All actions dropdown.
• For deleting bulk Storage Commitment SCU Tasks, select Delete all matching tasks from the All actions dropdown.