UCF Housekeeping
| May 2006 | |
| Contributed by - Lani Hardage-Vergeer, EMC Documentum Tech Pubs |
Abstract
UCF content transfer files can be cleaned up on the client at a configurable interval. This tip looks at the configuration needed to enable this cleanup.
Configuration
Content that is viewed on the client can be removed automatically by UCF at a configurable housekeeping interval. This interval is specified by the option house.keeping.interval. You can add this option to the UCF client configuration file ucf.installer.config.xml. On the application server, this file is located under the application root, in the following path:
Add the following option element to the <configuration> element and set the value to the number of days after which housekeeping will be performed:
<option name="house.keeping.interval">
<value>7</value>
</option>
|
Note:The housekeeping is performed at the next user login after the housekeeping interval.
You can force the installation of this new client configuration file by changing the application version number in the <app> element, adding a letter. Do not change the numeric parts of the version, as future upgrades or hotfixes from Documentum may not take effect on the clients due to conflicting version numbers. For example, you would change this:
<app id="shared" version="5.3.0.214" compatibilityVersion="5.3.0"/>
|
to
<app id="shared" version="5.3.0.214a" compatibilityVersion="5.3.0"/>
|
When the forced reinstall (or upgrade) occurs, only the binaries are replaced. Existing values in the configuration file on the client, ucf.client.config.xml, are not changed; the existing value has precedence over values configured in ucf.installer.config.xml. Configuration options that are not present in the ucf.client.config.xml but are present in ucf.installer.config.xml, such as the housekeeping option, are propagated from ucf.installer.config.xml during reinstall or upgrade.
|
