Generic Storage - dcm4che/dcm4chee-arc-light GitHub Wiki

Overview

User has the choice to configure one or more storages as per his application needs. In cases where the disks may be full or where one wants to store parallely when there are multiple concurrent or sequential associations to the archive, then one may add more than one storage.

The storage shall be referenced on :

Archive device level for : Series Metadata Storage
Application Entity level for : Object Storage and/or Metadata Storage

User has the option to reference the same storage for all three purposes or may choose to create different storage descriptors and reference one for each type of storage purpose. This can be seen in sample configuration file provided by the archive.

Using Archive UI

Go to Menu -> Configuration, then on Devices page, use Edit Device of dcm4chee-arc device.
Go to Extensions and Edit Extension of Device Extension. Again go to its Extensions and Edit extension of Archive Device.
Then next go to its Child Objects and + (Add) a Storage Descriptor.
Enter values in fields Storage ID and Storage URI. One may choose to add values in other fields as well as required and Save.

Depending on one's application needs, one may choose to reference this storage on Archive device level for storing series metadata. One may also reference this storage on Application Entity level for storing objects and/or its metadata.

To reference the storage on Archive device level for Series Metadata Storage purpose:

Go back to the Device page
Use Edit Device of 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 Attributes
Check on the Series Metadata Storage ID list the value(s) of Storage ID that was used while creating the Storage Descriptor in Step 4.

To reference the storage on Application Entity level for Object Storage and/or Metadata Storage purpose:

Go back to dcm4chee-arc device level
Go to Child Objects and select an application entity from Network AEs which should reference this storage.
Go to its Extensions of Network AE Extension.
Again go to its Extensions and Edit Extension of Archive Network AE field.
Go to Attributes
Check on the Object Storage ID and/or Metadata Storage ID lists the value(s) of Storage ID that was used while creating the Storage Descriptor in Step 4.

Using LDAP

In default configuration, there is one File System Storage configured with

Attribute	Value
dcmStorageID	fs1
dcmURI	${jboss.server.data.url}/fs1/
dcmProperty	pathFormat={now,date,yyyy/MM/dd}/{0020000D,hash}/{0020000E,hash}/{00080018,hash}
dcmProperty	checkMountFile=NO_MOUNT
dcmInstanceAvailability	ONLINE
dcmDigestAlgorithm	MD5

and referenced on Application Entity level.

One may modify the Storage by

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

  version: 1
  dn: dcmStorageID=fs1,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
  dcmInstanceAvailability: ONLINE
  dcmProperty: pathFormat={now,date,yyyy/MM/dd}/{0020000D,hash}/{0020000E,hash}/{00080018,hash}
  dcmProperty: checkMountFile=NO_MOUNT
  dcmDigestAlgorithm: MD5
  objectClass: dcmStorage
  dcmStorageID: fs1
  dcmURI: ${jboss.server.data.url}/fs1/

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

or use the Edit Value function of Apache Directory Studio.

One may reference this storage on Archive Device level (for Series Metadata Storage purpose) and/or on Application Entity level (for Object Storage and/or Metadata Storage purpose)