TeamcenterKnowledge

System Administration > File Management System > FMS components

FMS server cache

The FMS server cache (FSC) is the name of the FMS server cache server process. The FSC is a shared, secure, server level cache. It uploads and downloads files to other FSCs and to FCCs. An FSC can provide one or more modes of behavior, where each mode manages a type of data including volume files, cache files, transient files, and configuration files. A particular FSC can perform any or all of these functions simultaneously depending on your FMS configuration. All FSCs provide at least one mode in a properly configured FSC topology. You define configuration, volume and transient file modes explicitly in the FMS configuration files using XML statements. Cache server functionality is installed on each FSC, but is only used if the FSC does not have direct access to volume files. The various FSC modes are as follows: Configuration server (optional) One or more FSCs may be designated as a configuration server. An FSC configuration server reads the fmsmaster_fscid.xml configuration file and distributes that information to other FSCs and/or clients. The FSC configuration topology can be a single FSC or a tree of FSCs. The FSC configuration topology is separate from the FSC routing topology. Volume server (optional) An FSC may contain zero or more mounted volumes. An FSC serves volume data by reading/writing the file directly from local or mounted disk, and writing/reading that data onto a TCP port in HTTP protocol. Cache server (conditional) An FSC caches any data not directly available in a volume mounted on that FSC. An FSC routes and caches data from other FSCs if it does not have direct access to the volume containing the file. Transient file server (for Teamcenter four-tier configurations only, on each business logic server. Use FCC in transient file server mode with Teamcenter two-tier configurations). Each business logic server in four-tier mode writes and reads data from a temporary disk location. The FSC provides the capability to deliver this temporary data to or from the client. Each business logic server should have an FSC transient server to deliver the temporary data. The transient volume directory must reside on the same machine as the FSC and the Pool Server Manager. FSC basic functions are: Segment read file cache The FSC stores all file downloads as 16K file fragments in the read segment cache. Whole files are not stored. The segment cache uses the FMS fast cache. No purge policies are needed for the fast cache; it automatically purges file segments as needed. Segment write file cache The FSC stores all file uploads as 16K file fragments in the write segment cache. Whole files are not stored. WAN acceleration (optional) The FCC provides the capability to accelerate file downloads over high latency or noisy WAN lines. Required software is shipped as part of the base FMS install. Server configuration The FSC reads and distributes FMS configuration data across site FSCs and FCC processes. Client configuration The FSC processes the client configuration, analyzes the configuration, computes the configuration download for each client, and provides this information as a bootstrap download when the FCC process initializes. Failover (configuration dependent) The FSC provides the capability to fail over to alternate FSCs upon failure of a specific FSC. Failover is provided for access to both FSC configuration servers and FSC file servers. Whole file cache (WFC) The files are whole files on the disk and not in a virtual memory mapped disk space.

Source: https://docs.sw.siemens.com/documentation/external/PL20251212545240207/en-US/tc_help/AWAdmin/fhs4814155880506/uuc1737238583853/fgf1737238584066/genid_server_cache_58_3406.html · retrieved Fri Jul 31 2026 00:00:00 GMT+0000 (Coordinated Universal Time)