TeamcenterKnowledge

System Administration > File Management System > FMS configuration files > FMS client configuration file

General FCC configuration parameters

The following table lists general parameters defined in the FMS client configuration file (FMS_HOME/fcc.xml). See the FMS_HOME/fcc.xml.template file for all available elements. Name Default value Description FCC_LogFile $HOME\fcc.log|/tmp/ $USER/fcc.log Defines the name of the FCC log file. The value to the left of | is used for Windows hosts. The value to the right of | is used for Linux hosts. FCC_LogLevel WARN Defines the FCC logging level. Valid values, in order of increasing detail, are OFF, ERROR, WARN (the default), INFO, DEBUG, and TRACE. (SEVERE can be used as a synonym for ERROR.) Caution Setting FCC_LogLevel to DEBUG or TRACE produces a large volume of logging output. Avoid using these logging levels in production environments. FCC_TraceLevel Defines the FCC trace filtering level, allowing you to filter the log output to specific diagnostic areas. Valid values are PERF, CACHE, CLIENT, FSC, and ADMIN. Enter a combination of any of these values, separated by |, for example: CACHE|CLIENT|FSC|ADMIN Note PERF outputs requested information in only enough detail to replay a series of events for diagnostic purposes. Defining this value invalidates all other values for this parameter. FCC_WANThreshold 256K Defines the minimum file size allowed for the FCC to use WAN acceleration for FSC downloads. The minimum value is 32K. Reducing the value may improve performance when processing relatively small files. FCC_MaxWANSources 10 Defines the maximum number of network sockets (from 2 to 10) that can be used for each file download. Decreasing this value allows more requests to be handled simultaneously. Increasing this value allows processes to be processed more quickly. FCC_WANChunkSize 256K Defines the maximum size of a file segment (or chunk) the FCC is allowed to request. The minimum size is 32K. The maximum size is 5M. Raising this value reduces the number of parallel requests, which may result in performance improvements when bandwidth is limited. FCC_ProxyPipeName \.\pipe\FMSClientPipe| /tmp/FMSClientPipe Defines the base name of the set of FIFOs (pipes) used to communicate with the FCCClientProxy. The value must exactly match the value of the FCC_PROXYPIPENAME environment variable set in the client application environment. The value to the left of | is used for Windows hosts. The value to the right of | is used for Linux hosts. Note Siemens Digital Industries Software recommends you do not set this parameter except under certain circumstances where it may be required. If you have questions, contact your Siemens Digital Industries Software representative. FCC_FSCConnectionRetry Interval 5000 Defines how often (in milliseconds) the FCC attempts to reconnect to FSCs it has determined are offline or malfunctioning. FCC_StatusFrequency 1000 Defines how often (in milliseconds) the FCC sends status callback messages to the client during a lengthy transport operation. FCC_EnableDirectFSC Routing true Determines whether the FCC routes data requests on volumes mounted within the local FCC group to FSCs which mount these volumes. If set to false, the FCC routes all requests to an assigned FSC for forwarding to the appropriate volume server. FCC_IdleTimeoutMinutes Not applicable. This parameter is obsolete. Use the maxidletime attribute in the tccs.xml file instead; setting the idle time out for TCCS and all its contained applications, including the FCC. FCC_TransientFileFSCSource ticketuri Determines whether to use the uniform resource identifier (URI) contained in every transient file ticket. Note If your network uses IPv6 (128-bit) addresses, use the hostname in URIs and do not use the literal addresses, so the domain name system (DNS) can determine which IP address should be used. Transient file ticket URIs are defined with the Default_Transient_Server preference, which specifies a default transient file server location. This parameter applies only to a four-tier transient file accessed using an FCC. It is ignored during two-tier transient file access and regular volume access. If set to ticketuri, the FCC routes four-tier transient file requests using the ticket URI list, failing over to the directfscroutes list and then the assignedfsc list. If set to parentfsc, the FCC ignores the ticket URI list, and routes four-tier transient file requests using only the information obtained from the parentfsc element (such as the directfscroutes list and the assignedfsc list).

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