IBM Support

SitemapGenerate fails to create the site map XML files in WebSphere Commerce Version 7.0 Feature Pack 3 or 4

Technote (troubleshooting)


Attempts to run SitemapGenerate without the maxUrlNumber parameter result in the site map XML files not being generated when using IBM WebSphere Commerce Version 7.0 Enterprise with Feature Pack 3 or Feature Pack 4.


There are no exceptions reported, but the sitemap xml files are not generated as expected.


The command registry database table (CMDREG) is missing information on an expected command mapping for This is common if the store published was a Feature Pack 3 or higher store archive.

The Feature Pack 3 or higher store archive files include the following XML snippet within the command.xml file to define a mapping for in the command registry database table:


Diagnosing the problem

Check the CMDREG database table to confirm that the implementing class definition exists for the interface. This can be accomplished using the following SQL:

select * from cmdreg where storeent_id = <storeId> and interfacename = ''

Resolving the problem

If no rows were returned, insert the row into the database table. For example:

insert into cmdreg (storeent_id, interfacename, classname, target) values (<storeId>, '', '', 'Local')

After inserting the record into the CMDREG database table, refresh the command registry using the WebSphere Commerce Administration Console, or restart the application server.

Related information

Creating and scheduling the SitemapGenerate job
CMDREG database table
Updating registry components

Document information

More support for: WebSphere Commerce Enterprise
Store Models / Store Development

Software version: 7.0

Operating system(s): AIX, Linux, Solaris, Windows

Reference #: 1592265

Modified date: 28 August 2014