IBM FileNet P8, Version 5.2.1            

Content storage

You can store content in an OpenStack-conformant cloud storage device, in a file system, in the object store database, or in a fixed content storage system. From the user or programmer perspective, the storage location is transparent and is defined based on document class configuration, storage policies, or storage areas.

A cloud or file storage device can be attached to an advanced storage area. An advanced storage area provides high availability content storage and disaster recovery through use of replication and replica repair. This capability is accomplished without relying on any special features of the underlying storage devices, so advanced storage areas can be applied to commodity storage. An advanced storage area supports heterogeneous storage devices and leverages the Content Platform Engine sweep service and server communication service for replication, content deletion, and abandoned content backout.

A file storage area is an area that contains document content in a directory tree on a local or shared network drive. The disk drive can be a Windows NTFS volume, a UNIX file system, or an IBM® General Parallel File System (GPFS™).

A database storage area converts document content into binary large objects (BLObs) for storage in the database that is specified as the object store database.

A fixed content storage system is an external repository that acts like a virtual storage area for the Content Platform Engine system. Content Federation Services provides connectivity and configuration for the repository. Fixed content storage systems potentially provide extremely large storage capacity and typically provide WORM (write once, read many) and retention capabilities. You can use FileNet® Image Services as a fixed content storage system, as well as other storage systems such as Tivoli® Storage Manager.



Last updated: October 2015
p8sov014.htm

© Copyright IBM Corporation 2015.