Unable to Locate Config File Specified

This error is generated by the .sh or .bat scripts if they cannot locate the main configuration file specified as an input parameter. Make sure to specify either an absolute path, or a path relative to the directory from which you are running the script.

ENDECA_ROOT Is Not Set

This error is generated by the .sh or .bat scripts if the ENDECA_ROOT environment variable is not set. These scripts use ENDECA_ROOT to locate commons-logging.jar and servlet-api.jar.

Fatal Error in Running Queries: Error Establishing Connection to Retrieve Navigation Engine

This generally means you are trying to connect to an MDEX Engine that is not running. Check the main configuration file (conf.xml) and make sure that the host and port of the MDEX Engine are correct.

Cannot find endeca-sitemapgen jar file under <path>

This error is generated by the .sh or .bat scripts if they are unable to locate the sitemap_generator\lib\endeca-sitemapgen-<version>.jar file. The location of this file is computed from the location of the .sh or .bat scripts, with the assumption that those scripts have not been moved from their default locations. This file also needs to be included in the classpath when running the Sitemap Generator.

Unable to Locate Template Configuration File

The Sitemap Generator throws this exception if it is unable to find the template configuration file specified in the main configuration file. Remember to use either an absolute path, or a path relative to the location of the main configuration file, when specifying the template configuration file to use.

Can’t Find Output Files

Remember to use either an absolute path or a path relative to the location of the main configuration file, when specifying the target location for output files. If you are still unable to find the output files, the last line of the standard output should indicate the location where the files were written, such as:

INFO: Sitemap files output here: C:\Endeca\ToolsAndFrameworks\<version>\sitemap_generator\sitemap\*.xml

Sitemap Files Missing Values / Name of the Tag Output

If sitemap files that are output are missing values that were specified in the template configuration files, or contain the Name of the tag used in the template configuration files, such as: <a href="http://localhost:8006/discover/detail?id=">...</a> Or: <a href="http://localhost:8006/discover/detail?id=id">...</a>, those keys did not have corresponding values for that given record. In the above example, there is no property "id" specified in the QUERY_FIELD_LIST. Make sure such a property exists, and that it is included in the QUERY_FIELD_LIST in the main configuration file.

No Navigation Pages Created

If no navigation pages were created, then the dimensions listed in the NAVIGATION_PAGE_SPEC_LIST parameter in the main configuration file may not be included in the QUERY_FIELD_LIST. Make sure to add the dimensions to the QUERY_FIELD_LIST in the main configuration file.

Another possibility is that no records exist with the combination of dimensions that you have specified.

Errors Reading Search Term Queries

If errors occurred running search term queries, the problem may be that the search terms configuration file is not configured appropriately.

Please check your:

as well as the parameters for each query that failed.