Administering the FCC for TCCS

The FMS client cache (FCC) provides a private user-level cache, just as web browsers provide a read file cache. The FCC also provides a high-performance cache for both downloaded and uploaded files. The FCC provides proxy interfaces to client programs and connectivity to the server caches and volumes. Use the fcc.xml file to manage FCC behavior, such as connection time-outs and the maximum number of retries. Use the fccstat utility to administer and obtain run-time statistics from the FCC. Consider the following behaviors when working with the FCC as it runs with TCCS: Setting the initialize parameter of the FMSClientCache element to true in the tccs.xml file enables FCC functionality when TCCS starts. This is the default value. The only tccs.xml file the FCC accesses is the one stored in the TCCS configuration directory. Any other tccs.xml files are ignored. HTTP configuration parameters in the tccs.xml file are also applied to the FCC connections to an FMS server cache (FSC). Note TCCS and all its container applications run simultaneously. Starting, stopping, or reconfiguring TCCS (or any of its applications) propagates the same action to all. Note Native FCC does not run in the TCCS container.