FPCPathMapping Object

The FPCPathMapping object represents a mapping of an external path to an internal path on a server published by a Web publishing rule. The external path is the public path used by users in their incoming requests, and the internal path is the private path to the published directory on the Web server.

Path mappings are used in Web publishing rules. Before forwarding a request to the published Web server, Forefront TMG checks the (external) path specified in the request. If a path mapping is found for the path specified in the request, Forefront TMG replaces the path specified in the request by the corresponding internal path. Note that the external path in each path mapping must be distinct and unique. For more information, see FPCWebPublishingProperties.

Paths may be specified in any of the following formats:

  • Full path (for example, /mypath/default.htm).
  • Prefix (for example, /pictures/travel/* or /*, but not /mypath*/ or /mypath*).

This object is an element of an FPCPathMappings collection.

Dd436290.bkbutton(en-us,MSDN.10).png Click here to see the Forefront TMG object hierarchy.


The FPCPathMapping object defines the following methods.

Method Description


Reads the object's configuration information from persistent storage, discarding any changes to the configuration that were not saved.


Writes the current values of all of the object's properties to persistent storage.


The FPCPathMapping object defines the following properties.

Property Description


Gets the external path for the mapping.


Gets the internal path for the mapping.


Gets a Boolean value that indicates whether the external path is the same as the internal path.

Interfaces for C++ Programming

This object implements the IFPCPathMapping interface.


Client Requires Windows 7 or Windows Vista.
Server Requires Windows Server 2008 R2 or Windows Server 2008 x64 Edition with SP2.
Version Requires Forefront Threat Management Gateway (TMG) 2010.

Declared in Msfpccom.idl.

See Also

COM Objects

Send comments about this topic to Microsoft

Build date: 6/30/2010