DICOM Exporter - dcm4che/dcm4chee-arc-light GitHub Wiki

An exporter is needed if one intends to store objects from archive to a remote destination using the Export queue. An export of objects can be done in two ways :

• Rule based
• UI triggered DICOM Queued Export

• Configure a Remote Application Entity for each of the system(s) acting as destination(s). Archive is pre-configured by default with a storescp device which can act as a remote destination emulating the storescp tool where DICOM objects can be stored.

There are two ways to Create an Exporter using the Configuration page of Archive UI.

1. Using Create Exporter wizard :
   • Use Configuration page -> Devices tab. In More Functions select Create Exporter. Select the archive device to which Exporter needs to be connected to. On Exporter section, enter the values for Exporter ID, URI (eg. dicom:STORESCP. Note that STORESCP here is the Remote AE acting as destination), Queue Name and Application Entity (AE) title. Optionally choose to configure one or more optional configurations and Apply.
   • If one wants to add more optional values to the Exporter, use Configuration page -> Devices tab. Select dcm4chee-arc -> Extensions -> Edit extension -> Device Extension -> Extensions -> Edit extension -> Archive Device. In its Child objects from the list of Exporter Descriptor select the Exporter created above. Choose to optionally configure one or more of the other configurations and Save.
2. Create Exporter via Configurator :
   • Use Configuration page -> Devices tab. Select dcm4chee-arc -> Extensions -> Edit extension -> Device Extension -> Extensions -> Edit extension -> Archive Device.
   • In its Child objects select + Add a new Exporter against the field Exporter Descriptor.
   • Enter the values for Exporter ID, URI (eg. dicom:STORESCP. Note that STORESCP here is the Remote AE acting as destination), Queue Name and Application Entity (AE) title. Optionally choose to configure one or more optional configurations and Save.

One may either

• create a LDIF file (e.g.):

    version: 1
    # The Exporter object, specifies the type and destination of the export,
    # which local AE shall perform the forward, and which JMS Queue shall be used to queue Export
    # Tasks ready to be performed, and optionally to defer the export to specified times
    dn: dcmExporterID=STORESCP,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
    objectClass: dcmExporter
    dcmExporterID: STORESCP
    dcmURI: dicom:STORESCP
    dicomAETitle: DCM4CHEE
    dcmQueueName: Export1
    dicomDescription: Generic DICOM Exporter (Unrejected Instances & Rejection Notes except Retention Expired)
    # defer export after business hours (between 6 pm and 6 am, or at any time on Saturday and Sunday)
    #dcmSchedule: hour=18-6 dayOfWeek=*
    #dcmSchedule: hour=* dayOfWeek=0,6
  

  and import it to the LDAP Server by using the ldapadd command line utility or the LDIF Import... function of Apache Directory Studio

• or directly use the New Entry... function to create corresponding Exporter entries.

Note that STORESCP mentioned in the dcmURI is acting as the destination of objects exported from the archive.

Note that some of the attributes in the above example have been commented out; these only show the possible configurations (one may choose to add them or set with different values based on one's application needs) related to schedules and properties.

Refer Exporter Descriptor to understand the description of attributes.

Go to the Control tab on Configuration page in archive UI and reload the configuration.