5. To configure client schedule information for the new cache object: a. Click the Client Schedule tab. A list of all cache objects written to the Document Manager Client Cache appears. b. You can select one or more of these objects and alter the frequency of client-side updates by taking any of the following actions: •
Select the Do not store cache data locally. Remove immediately after use check box to remove temporarily stored client cache on the user’s computer when the user exits the DB2 Document Manager Desktop. Attention: This option is not recommended.
•
In the Update Frequency list, choose one of the following options: Each Access: Each time the user accesses a component of the DB2 Document Manager Desktop, such as a menu, the Desktop requests the DB2 Document Manager server to determine whether the menu cache object has been updated. If so, the DB2 Document Manager Desktop updates cache for the menu. Each Session: Each time the user starts a DB2 Document Manager Desktop session and logs into a library environment, the client cache is checked for update. Interval: The Desktop checks the DB2 Document Manager server for new cache files at the specified interval. Choose the frequency interval and increment to the right of Update Frequency. Calendar: Choose a calendar interval of Daily, Weekly, or Monthly.
c. Click Set to post the changes to the cache object list. d. Click Apply to post the changes to the library environment. 6. The Purge Schedule tab (Figure 13-2 on page 395) enables you to configure the purging of client cache objects. Purging removes the data files representing the client cache in the DB2 Document Manager client subdirectory. To configure the purge schedule for the new cache object: a. Click the Purge Schedule tab. b. Set the client cache to purge by taking any of the following actions: •
Click Purge Now to force the removal of client cache data files even though the frequency does not call for the action.
•
Choose one of the following options from the Frequency list: Never: The client cache is never updated automatically.
394
Performance Tuning for Content Manager