Storage objects
The storage management criteria that you specify on the library server determines where and when Content Manager OnDemand stores reports and how it maintains them.
Figure 1 shows the primary Content Manager OnDemand storage objects.
An administrator creates a Content Manager OnDemand application for each report that is to be stored on the system. Applications with similar storage characteristics can be placed into a collection called an application group.
When you load a report into Content Manager OnDemand, you assign it to an application group. The application group identifies a storage set. The storage set contains one or more storage nodes. A storage node identifies an object server on which data is stored. Content Manager OnDemand will automatically store a copy of the report in cache storage on the object server, unless you specify otherwise. A storage node can also identify an external storage manager for archive storage. If a storage node specifies OAM, VSAM, or another external storage manager, then Content Manager OnDemand automatically stores a copy of the report in archive storage, which is managed by the external storage manager that is specified in the storage node definition.
One or more application groups can specify the same storage set. However, a storage set can write to only one (archive) storage node at a time. This means that all of the data that is written to a storage node will be maintained using the same policy, for example, the type of media, the devices, the length of time to maintain data on the system, and so forth.
If you use an external storage manager to maintain reports in archive storage, you should specify the same storage management criteria to Content Manager OnDemand and the external storage manager. For example, the Life of Data and Indexes, which is used by Content Manager OnDemand, and the retention period used by the external storage manager should be the same value.