Export Rule - dcm4che/dcm4chee-arc-light GitHub Wiki
An Export Rule is needed when one wants to export the objects to a destination, as they are received by the archive, without having the need to manually export the objects using UI and RESTful services. One may refer Rule based export.
An Export Rule may be created on :
- 
Archive Device level - to forward instances received by any Application Entity of the Archive :
Go to
Menu->Configuration, then onDevicespage click onEditof thedcm4chee-arcdevice. Go toExtensionsandEdit extensionofDevice Extension. Again go to itsExtensionsandEdit extensionofArchive Device. Go to itsChild objectsand select+ Add a new Export Ruleagainst the fieldExport Rule. Enter the values forName,Attribute Entity,Exporter IDand one or more optional values and clickSave. 
OR
- 
Application Entity level - to forward instances received by this Application Entity of the Archive
Go to
Menu->Configuration, then onDevicespage click onEditof thedcm4chee-arcdevice. Go to itsChild Objectsand select anApplication Entityfrom theNetwork AEsdropdown. Go toExtensionsandEdit extensionofNetwork AE Extension. Again go to itsExtensionsandEdit extensionofArchive Network AE. Go to itsChild objectsand select+ Add a new Export Ruleagainst the fieldExport Rule. Enter the values forName,Attribute Entity,Exporter IDand one or more optional values and clickSave. 
One may either create a LDIF file to add attributes either on :
- 
Archive Device level (e.g.):
version: 1 # Sample configuration for forwarding of received instances # The Export Rule specifies on which entity level the export shall be triggered, how long the export shall be # delayed after the receive of the last instance of the entity, and optionally additional conditions which # have to be matched by the instance to trigger the export dn: cn=Forward to STORESCP,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org objectClass: dcmExportRule cn: Forward to STORESCP dcmEntity: Series dcmDuration: PT1M dcmExporterID: STORESCP # Only export CT and MR Series received by DCM4CHEE from FORWARD between Monday and Friday #dcmProperty: ReceivingApplicationEntityTitle=DCM4CHEE #dcmProperty: SendingApplicationEntityTitle=FORWARD #dcmProperty: Modality=CT|MR #dcmSchedule: dayOfWeek=1-5 
OR
- 
Archive AE level (e.g.):
version: 1 # Sample configuration for forwarding of received instances # The Export Rule specifies on which entity level the export shall be triggered, how long the export shall be # delayed after the receive of the last instance of the entity, and optionally additional conditions which # have to be matched by the instance to trigger the export dn: cn=Forward to STORESCP,dicomAETitle=DCM4CHEE,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org objectClass: dcmExportRule cn: Forward to STORESCP dcmEntity: Series dcmDuration: PT1M dcmExporterID: STORESCP # Only export CT and MR Series received by DCM4CHEE from FORWARD between Monday and Friday #dcmProperty: ReceivingApplicationEntityTitle=DCM4CHEE #dcmProperty: SendingApplicationEntityTitle=FORWARD #dcmProperty: Modality=CT|MR #dcmSchedule: dayOfWeek=1-5and 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 its New Entry... function to create corresponding Export Rule entries. OR directly use the New Entry... function of Apache Directory Studio to create corresponding Export Rule entries on Device Level (e.g.:
dicomDeviceName=dcm4chee-arc) or on Application Entity Level (e.g:dicomAETitle=DCM4CHEE) of the Archive Configuration. 
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.
One may refer to Export Rule to understand the description of attributes.
Refer ISO-8601 Duration format for more know-how on Durations.
Go to the Control tab on Configuration page in archive UI and reload the configuration.