Export (0) Print
Expand All

Team Foundation Server Proxy Config File

Team Foundation Server Proxy has an XML configuration file that maintains information that is required for the proxy configuration. This topic describes the nodes in this file and their effect on the configuration of Team Foundation Server Proxy.


The configuration file for Team Foundation Server Proxy contains the following XML nodes:

Node

Explanation

<ProxyConfiguration>

This node is the root element of the file, as in the following example:

<ProxyConfiguration 
    xlmns:xsd="http://www.w3.org/2001/XMLSchema" 
    xlmns:xsi="http://www.w3.org/2001/SMLSchema-instance">
<!-- Additional notes omitted for clarity -->
</ProxyConfiguration>

<Servers>

This node contains one or more <Server> nodes that correspond to one or more instances of Visual Studio Team Foundation Server or team project collections from which the proxy server caches files.

Each <Server> node contains a <Uri> node that specifies either a computer that is running Team Foundation Server or a single team project collection on Team Foundation Server. 

  • If you specify a computer that is running Team Foundation Server, the proxy can cache files from all collections on that server.

  • If you specify a single team project collection, the proxy can cache files only from that collection.

For example, the Servers node might resemble the following example if the proxy were caching version control files from every collection on a server that is named TfsServer, using the default values for port and virtual directory:

<Servers>
    <Server>
        <Uri>http://tfsserver:8080/Tfs</Uri>
    </Server>
</Servers>

The Servers node might resemble the following example if the proxy were caching version control files from collection0 on a server that is named TfsServer, using the default values for port and virtual directory:

<Servers>
    <Server>
        <Uri>http://tfsserver:8080/Tfs/Collection0</Uri>
    </Server>
</Servers>

The Servers node might resemble the following example if the proxy were caching version control files from collection0 on a server that is named TfsServer1, and version control files from every collection on a server that is named TfsServer2, with both servers using the default values for port and virtual directory:

<Servers>
    <Server>
        <Uri>http://tfsserver1:8080/Tfs/Collection0</Uri>
    </Server>
    <Server>
        <Uri>http://tfsserver2:8080/Tfs/ </Uri>
    </Server>
</Servers>

<CacheRoot>

This node contains the root directory of the file cache. This directory contains one folder for each application tier for which the proxy is configured. For example, the CacheRoot node might resemble the following example with a single entry in the Servers node:

<CacheRoot>C:\Program Files\Microsoft Team Foundation Server 2010\Version Control Proxy\_tfs_data</CacheRoot>

<CacheLimitPolicy>

This node specifies at what point the proxy will run the clean-up routine to remove stale files. You can configure this node in either of the following ways:

  • Use a <PercentageBasedPolicy> node to run the clean-up routine when a specified percentage of available disk space is filled.

    For example, the CacheLimitPolicy node might resemble the following example if the proxy were set to run the clean-up routine when the cache fills 75 percent of the total disk space:

    <CacheLimitPolicy>    
        <!-- Cache limit expressed as percentage of disk space -->
        <PercentageBasedPolicy>75</PercentageBasedPolicy>    </CacheLimitPolicy>
    
  • Use a <FixedSizeBasedPolicy> node to run the clean-up routine when a specified amount of disk space (in megabytes) is filled.

    For example, the CacheLimitPolicy might resemble the following example if the proxy were set to run the clean-up routine when the cache fills 500 megabytes:

    <CacheLimitPolicy>
        <!-- Cache limit expressed as MB -->
        <FixedSizeBasedPolicy>500</FixedSizeBasedPolicy>
    </CacheLimitPolicy>
    

<StatisticsPersistTime>

This node indicates how frequently (in hours) cache performance statistics should be written to disk. For example, the StatisticsPersistTime node might resemble the following example if the proxy were set to write statistics to disk every hour:

<StatisticsPersistTime>1</StatisticsPersistTime>

Changing Proxy Configuration Settings

To change the proxy configuration, you must open the Proxy.config file in a text or XML editor and manually change the values. After you save the file, you must recycle the application pool before the changes will take effect. For more information, see How to: Connect Team Foundation Server Proxy to Team Foundation Server and How to: Change Cache Settings for Team Foundation Server Proxy.

Community Additions

ADD
Show:
© 2014 Microsoft