Current dcm4chee version (v2.10.15) does not support to store received objects into separate storage locations conditioned by any criteria. As workaround multiple instances of the File System Management Service may be deployed, each attached to its own bundle of DICOM services: in particular to an additional DICOM Server, Query Retrieve SCP, Storage Commit Service and Storage SCP service.
Step by Step instruction
- Move configuration of JMX object names, JMS queue names and Scheduler Timer IDs from XMBean descriptors (conf/xmdesc/*-xmbean.xml) to JMX service descriptors (deploy/*-service.xml) - partly already done in dcm4chee-2.10.5: DCMEE-378, DCMEE-384, DCMEE-389.
- Create copies of JMX service descriptors and modify JMX object names, JMS queue names and Scheduler Timer IDs appropriate. E.g.:
- Start the application. You will get an
exception, because both DICOM servers are configured to listen on the same port. Change the port of one of the deployed DICOM Server to a different number using the JMX console and restart the application.
- Change the RetrieveAETitle of the second File System Management Service and also the CalledAETitle of the new deployed DICOM services to a different value (e.g. DCM4CHEE2), using the JMX Console. Also add an Application Entity configuration entry for the new value, using the AE Management Page of the Web interface.
- Change the DefaultStorageDirectory of the second File System Management Service to the directory path, where objects received by the Storage SCP attached to the second DICOM server shall be stored.
- After receiving objects by both servers, two File System records should have be initalized. E.g.:
|
|