Tip: You can maintain separate droidConfig.xml and
filters.txt input configuration files for each of your stores or locales,
depending on your business needs.
droidConfig.xml
The site content crawler configuration file contains variables and parameters that determine the
site content crawler behavior.Variables
hostname
storePathDirecttory
langId
storeId
catalogId
language
localename
filterDir
port
The variables that are specified in the site content crawler configuration file are then
used to populate values further in the configuration file.Parameters
initialLocations
The starting URL for the site content crawler.
Important: You must update the
starting URL for the site content crawler to operate correctly.
The jndi name of the JDBC data source for example,
<jndiName>jdbc/jndiName</jndiName>. It is only used when you run the crawler
through URL. When this parameter is specified, the crawler can use that data source to update the
database after the crawling finishes.
filters.txt
The filters configuration file determines whether URLs are included or ignored by the site
content crawler.
You can update the filters configuration file by using regular expressions to include or ignore
values.
Important: You must update the filters configuration file to include your
WebSphere Commerce host name.
The default sample values contain ignores such as excluding URLs containing email or FTP links,
or pages that require logging on to the site.
SiteMap.jsp
The site map, which is used by web browsers and external search engines, contains pointers to
the different starter store pages
StaticContentSitemap.jsp
The static site map contains pointers to the static content files that are in the WebSphere
Commerce database.
The URL that is passed from the configuration file to the site content crawler
is: