Manual Matching of Unknown Target Host Names

During a DFS Crawl, the Crawler tries to match target host names to the host names of existing applications in the File Access Manager database.

When the Crawler is unable to match specific hosts, it attempts to match hosts via DNS lookups, and to find valid matching alias names (for example, a host name displayed as an IP address).

If a search cannot find host names or cannot match host name aliases to an existing host in the File Access Manager database, it is possible to configure matching hosts manually.

1. Create an *.xml file with the following structure:

   <?xml version="1.0"?>

   <mappings>

   <key name="hostA">AlternateHostA</key>

   <key name="hostB">172.66.12.12</key>

   </mappings>

   In the example above, “hostA” is a host name of a link target to be matched manually. “AlternateHostA” is the host name to which “hostA” will be matched.

   “AlternateHostA” should be a host name of an existing application in File Access Manager.

2. Add the following key to the DFS Permissions Collector’s service “app.config”.

   "<add key="dfsMappings" value="C:\myMappings.xml"/>"

3. Replace "C:\myMappings.xml" with the path that points to the configuration file.

4. Restart the DFS Permissions Collector service.