user manual

Storefront
BEA AquaLogic Commerce Services Deployment Guide 41
• Storefront – <ALCS_APP_HOME>\commerceServices\WEB-INF\conf\spring\commons\
• Commerce Manager – <ALCS_APP_HOME>\commerceServicesManager\WEB-
INF\conf\spring\commons\
Within the velocityProperties bean definition, the following properties can be configured.
• file.resource.loader.cache – Set this value to "true" for production to cache templates in
Velocity's loader. Set this value to "false" for development so that changes to templates will
take effect immediately.
• velocimacro.library.autoreload – This parameter enables/disables automatic reloading of
Velocity macros. Set this value to "false" for production. For development, setting this value
to "true" will allow changes to Velocity macros to take effect without restarting the server.
• velocimacro.messages.on – Set this value to "false" for production for improved
performance. When developing Velocity templates, this value can be set to "true" to see
Velocity logging and debugging information.
• runtime.log.logsystem.class – Set this value to
org.apache.velocity.runtime.log.NullLogSystem as shown below for production.
<entry
key="runtime.log.logsystem.class"><value>org.apache.velocity.
runtime.log.NullLogSystem</value></entry>
Product Cache
AquaLogic Commerce Services implements a special cache for Storefront product information
only. The underlying cache mechanism is JBoss Cache and configuration for this instance of
JBoss Cache is in ep-treecache.xml (see the ep-treecache.xml section for details). There are
several caching strategies that are available to choose from and the nature of each strategy is
described below. The strategies are configured in ServiceSF.xml.
Tree Cache file locations:
• ep-treecache.xml is located in
<WL_HOME>\samples\commerce\commerceApp\commerceServices\W
EB-INF\classes\
• ServiceSF.xml is located in
<WL_HOME>\samples\commerce\commerceApp\commerceServices\W
EB-INF\conf\spring\service\
Configuring AquaLogic Commerce Services to use a particular
caching strategy
Caching strategies are configured in the serviceSF.xml Spring configuration file. There are
several places in this file where the caching strategy to be used is specified by referencing the
bean id of the strategy. See below for an example.
<bean id="productViewService"