Rename the conf subdirectory to conf_storeus. This directory will hold the sitemap generator configuration for the CRS Store US site.

Make two copies of the conf_storeus subdirectory and its contents. Name the copies conf_storede and conf_homeus. These directories will hold the sitemap generator configuration for the CRS Store Germany and CRS Home sites.

Create three subdirectories to store the generated sitemap files. Name these directories sitemap_storeus, sitemap_storede, and sitemap_homeus.

Create the three configurations, as described below.

Copy the store.war/WEB-INF/endeca-seo-url-config.xml file into the three configuration directories. For example, the file for the CRS Home sitemap generator configuration would be:

conf_homeus/endeca-seo-url-config.xml

Edit the conf.xml file in each configuration directory and set the <URL_FORMAT_FILE> tag to endeca-seo-url-config.xml:

<URL_FORMAT_FILE>endeca-seo-url-config.xml</URL_FORMAT_FILE>

In the conf.xml files, edit the <INDEX_FILE> tag to specify the name and location where the sitemap index file should be written. (The location will be used for other sitemap files as well.) For example, in the conf_storede/conf.xml file, set this tag to:

<INDEX_FILE>../sitemap_storede/index.html</INDEX_FILE>

In the conf.xml files, configure the <MDEX_ENGINES> element:

For example, if the host name is myhost.example.com and the port number is 15000, the MDEX_ENGINES element in the conf_homeus/conf.xml file would be:

<MDEX_ENGINES>
  <ENGINE>
      <HOST>myhost.example.com</HOST>
      <PORT>15000</PORT>
      <ROOT_QUERY><![CDATA[N=0&Nr=product.siteId:homeSite]]></ROOT_QUERY>
      <ROLLUP_KEY>product.repositoryId</ROLLUP_KEY>
  </ENGINE>
</MDEX_ENGINES>

In the conf.xml files, edit the <QUERY_FIELD_LIST> element to remove the product.name <QUERY_FIELD> entry and change the product.brand.name entry to product.brand. The result should be:

<QUERY_FIELD_LIST>
<QUERY_FIELD>product.category</QUERY_FIELD>
<QUERY_FIELD>product.brand</QUERY_FIELD>
</QUERY_FIELD_LIST>

In the conf.xml files, edit the <NAVIGATION_PAGE_SPEC> elements to change the product.brand.name <DIMENSION_NAME> entries to product.brand and change all of the FULL_HIERARCHY attribute values to True. The result should be:

<NAVIGATION_PAGE_SPEC_LIST>
<NAVIGATION_PAGE_SPEC>
<DIMENSION_NAME FULL_HIERARCHY="True">product.category</DIMENSION_NAME>
</NAVIGATION_PAGE_SPEC>
<NAVIGATION_PAGE_SPEC>
<DIMENSION_NAME FULL_HIERARCHY="True">product.brand</DIMENSION_NAME>
</NAVIGATION_PAGE_SPEC>
<NAVIGATION_PAGE_SPEC>
DIMENSION_NAME FULL_HIERARCHY="True">product.category</DIMENSION_NAME>
DIMENSION_NAME FULL_HIERARCHY="True">product.brand</DIMENSION_NAME>
</NAVIGATION_PAGE_SPEC>
</NAVIGATION_PAGE_SPEC_LIST>

Edit the xml_template.xml file in each configuration directory and update the <loc> tags to reflect your production machine details (machine name, listen port, and context path). For example, if the machine name is myhost.example.com and the listen port is 7001, the settings in the conf_homeus/xml_template.xml file would be:

<DETAIL_LINK><![CDATA[
<url>
  <loc>http://myhost.example.com:7001/crs/homeus/detail**FORMATTED_URL\|XmlEscape**</loc>
  <lastmod>*TIMESTAMP*</lastmod>
</url>
]]></DETAIL_LINK>

<NAVIGATION_LINK><![CDATA[
<url>
  <loc>http://myhost.example.com:7001/crs/homeus/browse**FORMATTED_URL\|XmlEscape**/</loc>
  <lastmod>*TIMESTAMP*</lastmod>
</url>
]]></NAVIGATION_LINK>

<SEARCH_TERM_LINK><![CDATA[
<url>
  <loc>http://myhost.example.com:7001/crs/homeus/browse**FORMATTED_URL\|XmlEscape**</loc>
  <lastmod>*TIMESTAMP*</lastmod>
</url>
]]></SEARCH_TERM_LINK>

<STATIC_PAGE_LINK><![CDATA[
<url>
  <loc>http://myhost.example.com:7001/crs/homeus/**STATIC_PAGE\|XmlEscape**</loc>
  <lastmod>*TIMESTAMP*</lastmod>
</url>
]]></STATIC_PAGE_LINK>

Edit the searchterms.xml file in each configuration directory and set the <MDEXHOST> and <MDEXPORT> tags to the host name and port number of the machine the MDEX is running on. In addition, remove the existing <URL> tags from the file. For example, if the machine name is myhost.example.com and the port number is 15000, the contents of each searchterms.xml file would be:

<URLS>
<MDEXHOST>myhost.example.com</MDEXHOST>
<MDEXPORT>15000</MDEXPORT>
<DEFAULTQUERY><![CDATA[N=0]]></DEFAULTQUERY>
</URLS>

Run the ATG SitemapGeneratorService and SitemapWriterService components, as discussed in the ATG Sitemap Generator Components section.

Go to the Endeca sitemap_generator/bin directory and run the RunSitemapGen.sh (Unix) or RunSitemapGen.bat (Windows) command three times, each time specifying the conf.xml file for a different configuration. For example, on Windows the three commands would be:

RunSitemapGen.bat ..\conf_storeus\conf.xml
RunSitemapGen.bat ..\conf_storede\conf.xml
RunSitemapGen.bat ..\conf_homeus\conf.xml

Copy the navigation0.xml files that the generator creates in the Endeca sitemap directories to the Commerce Reference Store store.war directory. Rename each file to reflect the site it corresponds to. For example, copy the conf_storeus/navigation0.xml file to store.war/navigation_storeus.xml.

Add entries for these files to the siteindex.xml file created by the ATG SitemapIndexGenerator component. For example:

<sitemap>
  <loc>http://www.example.com/navigation_storeus.xml</loc>
</sitemap>