Storefront
BEA AquaLogic Commerce Services Deployment Guide 39
Using the env.config value to disable an index build will also disable the index
build for the Commerce Manager when it is built, so be careful to remember
whether index building is enabled or not in your current environment
Building the promotion rule base
Rules are read from the database periodically as invoked by the Quartz scheduler. The scheduler
is configured in the quartz.xml configuration file. This configuration file specifies parameters for
how often the rule base is to be "recompiled." For performance reasons, the rule base should not
be recompiled more than once every few minutes.
For demonstrations and testing, the recompile frequency can be set to a shorter interval such as
three seconds so that rules defined in the Commerce Manager will take effect immediately in the
Storefront. However, any caching of the rules objects will prevent updates to the set of rules in
use. Therefore, it is necessary to turn off caching in hibernate-config.xml file if rules are to take
effect immediately (see the hibernate-config.xml section).
Updating the product cache
Depending on your Product Caching Strategy, you may need to periodically update the Product
Cache so that changes in product information take effect in the Storefront. If you are using the
default caching strategy, it is essential to enable the quartz update product cache job; it is initially
configured to run 30 seconds after startup, and then every hour after that. Please see the Product
cache section for more information about product caching.
treecache.xml
The Hibernate persistence framework used in AquaLogic Commerce Services can be configured
to use JBoss Cache to cache persistent domain objects. The configuration for this caching
behavior is specified in treecache.xml which is found in the following application-specific paths.
• Storefront – <ALCS_APP_HOME>\commerceServices\WEB-INF\classes\
• Commerce Manager – <ALCS_APP_HOME>\commerceServicesManager\WEB-
INF\classes\
The objects that will be cached are listed in hibernate-config.xml (see the hibernate-config.xml
section for details).
Warning
Currently, the use of Hibernate caching is not recommended due to a bug in the
JBoss Cache eviction policy. It is disabled by default in hibernate-config.xml.
