Hitachi fixed content device

An IBM® Content Cortex fixed storage area can use the Hitachi Content Platform as the fixed content device for storing content element files. The content can belong to documents from different object stores. In addition, the object stores can belong to different Content Cortex domains.

The Content Platform Engine component that migrates the content files to the Hitachi device is the fixed content provider.

The content files on the Hitachi device are stored in a directory tree that has a structure similar to a file store directory tree. Use the Hitachi Namespace browser, to manually create the base directory for the directory tree. The directory tree is created automatically by the fixed content provider. The fixed content provider specifies the directory path and name for a file when placing the file on the device.

Hitachi Content Platform supports data shredding, which ensures that content data is overwritten in a way that prevents future recovery. For Hitachi device files, when the storage area deletion method is set to Destroy or Purge, the Content Platform Engine issues Hitachi Content Platform purge deletion calls to shred the data before removing the file. For staging area files, data scrubbing is performed according to the deletion method configured for the associated storage area.

Hitachi Content Platform indexing is not used by the Content Platform Engine because direct Hitachi queries bypass the Content Cortex security model. Hitachi content indexing is turned off by the Content Platform Engine during content creation. When Hitachi content indexing is turned off, the content that is created by the Content Platform Engine on the Hitachi device is not included in the Hitachi index information.