Altova SchemaAgent 2025

Navigation: Introduction > Configuring Search Paths

Viewing the Configuration File

The set of supported files managed by LocalServer or SchemaAgent Server, respectively, is defined in an XML file called SchemaAgentServerCfg.xml, which is by default stored in the Documents folder.

This file defines the search paths, and what paths or folders are scanned for schema files. The SchemaAgentServerCfg.xml file looks something like this:

<?xml version="1.0" encoding="UTF-8"?>
<SearchPaths XMLSchema=".xsd" MapForce=".mfd" XML=".xbrl,.xml" XSL=".xsl,.xslt" WSDL=".wsdl">
<Path recursive="1" user="" auth="000000">s:\schemas-mydir\</Path>
<Path recursive="0" user="" auth="000000">X:\schemas\</Path>
<Path recursive="1" user="" auth="000000">http://test.webdav.org/dav</Path>
<Path recursive="1" user="" auth="000000">\\Server1\Share1\Dir1\Schemadata</Path>
<Path recursive="1" user="jsmith" auth="k04EKS">ftp://myftpserver</Path>
</SearchPaths>

Note that any number of search paths can be defined, and search paths can include paths on a local machine, network paths (mapped drive letters and UNC paths), as well as folders on WebDAV servers and FTP access.

After search paths have been defined, LocalServer or SchemaAgent Server, respectively, retrieves all files with defined file extensions in individual search paths and builds an internal map of the relationships between the supported files in a search path. It is this mapping of relationships that enables SchemaAgent clients to present data about file relationships graphically. Further, if an IIR or file manipulation change is made in a SchemaAgent client, it is this mapping that enables the automatic updating of such changes in related files in the search path.