IBM FileNet P8, Version 5.2.1            

Retention for content stored in fixed storage areas

You can use FileNet® P8 to set retention for objects. The retention that you specify for an object can later be applied to the object content after it is checked in to a fixed storage area.

You can configure a fixed storage area to support one of two content storage modes: aligned or unaligned. In the aligned storage mode, object retention is synchronized with FileNet P8 and enforced by the fixed content device. In unaligned mode, retention is enforced by the Content Platform Engine.

In aligned mode, all the object retention settings are fully supported on the IBM® Tivoli® Storage Manager, Hitachi, and Centera fixed content devices. The NetApp Snaplock device supports a limited set of retention features.

Table 1. Actions and implications in aligned and unaligned mode
Actions Aligned mode Unaligned mode
Checking in object content If the object content is checked in to a fixed storage area, the retention setting of the object is copied to the fixed storage area. The object content is checked in to the fixed storage area, but retention is not applied to the content.
Deleting an object Retention is not set on the content, but the retention setting of the content on the fixed device is always examined before the FileNet P8 delete request is accepted. Same as aligned mode.
Enforcing object retention Retention is synchronized between FileNet P8 and the fixed storage area. Retention dates are consistent between an object in FileNet P8 and the associated content in the fixed storage area. Retention is managed by Content Platform Engine. When Content Platform Engine stores content on a fixed content device, you can use retention management to set and enforce the retention date for that content. The retention date is enforced by Content Platform Engine only. Content Platform Engine does not tell the fixed content device to enforce the date.

In unaligned mode, if you configure the fixed content device to enforce retention, you create a potential conflict between the retention dates that are enforced on the fixed content device and on Content Platform Engine.

Moving content programmatically from 1 fixed storage area to another. If the source area is a fixed storage area in aligned mode, and the retention period of the object did not expire, the operation to move the content fails. If the source area is a fixed storage area in unaligned mode, no restrictions apply. If the target area is a fixed storage area in aligned mode, the retention setting for the object is copied to the fixed storage area.


Last updated: March 2016
p8pcb040.htm

© Copyright IBM Corporation 2016.