Chapter 10. Migration and expiring data and indexes 225
Resource Data
The following selections are possible for Resource Data: 
/SM590000Always Maintain in Cache: The resource data stays in cache forever, and it does not 
expire. 
/SM590000Cache Resource Data for xxx Days: The resource data stays in cache for xxx number of 
days before the data expires. 
/SM590000Restore Resources to Cache: The resource data is not in cache, and the resource data is 
requested. The resources are restored to cache from the storage manager. 
The ARSLOAD program saves one copy of a resource on each node for each application group. 
The resource can be stored multiple times, depending on how the ARSLOAD program compares 
the data. The ARSLOAD program compares the last 50 resources against the resource that is 
generated by the load. If a match is not found, a new resource is stored.
When the ARSLOAD program processes a resource group file, it checks the resource identifier 
to determine whether the resource is present on the system.
If the storage node identifies a client node in OAM or Virtual Storage Access Method (VSAM), 
the storage manager copies the resources to archive storage.
Document Data
For Document Data, the following selections are valid:
/SM590000Yes for Cache Data: Y ou can cache document data and resource data or only resource 
data. 
/SM590000No Cache: Document data is not stored in cache. 
/SM590000Cache Document Data for xxx Days: Document data is stored in cache for xxx number of 
days before the data expires.
10.3  Configuring for migration and expiration
Many customers choose to expire their document data and indexes somewhere in the range 
of 5 - 10 years. In one extreme, document and index data might expire daily. In another 
extreme, document and index data might never expire. 
Four typical lifecycle scenarios are common. The Content Manager OnDemand administrator 
selects the scenario to implement through various parameters (as shown in this section), 
which are on the Storage Management tab of the Application Group window. The four 
scenarios are illustrated in Figure 10-2 on page 222.
10.3.1  Migrating index data
Index migration is the process by which Content Manager OnDemand moves index data from 
the database to archive storage. Index migration optimizes database storage space. With 
index migration, you can maintain index data for a long time. Y ou typically migrate index data 
only after users no longer need to access the reports. However, for legal or other 
requirements, you often must maintain data for a number of months or years.