Configuring AquaLogic Commerce Services
50 BEA AquaLogic Commerce Services Deployment Guide
• Consider disabling session replication
Session replication makes it possible to retain customer sessions when an application server is
down. However, this will slow down application servers to some extent. If it's not critical to
retain customer sessions, disabling replication can result in better performance.
Reverse Proxy Server
Reverse proxy servers are often used to cache static content to reduce load on application servers.
AquaLogic Commerce Services implements an image renderer which can render an image in any
desired size. This simplifies image management but also incurs CPU overhead each time an
image is rendered. However there is a little cpu overhead for the application server to use this
image renderer again and again on the same image. We recommend enabling caching for the
rendered images on a reverse proxy server.
Infrastructure
Ensure that enough network bandwidth is provided between the following servers.
• Internet and the reverse proxy server
• Reverse proxy server and the application servers
• Application servers and the database server
Storefront
Use the AquaLogic Commerce Services product cache
Ensure that the product retrieval strategy in use is the SingleCachingProductRetrieveStrategy.
The strategy to use is configured in the serviceSF.xml Spring configuration file. Check that all
objects which use a product retrieval strategy are using the
SingleCachingProductRetrieveStrategy. See ep-treecache.xml to fine tune this cache, which is
based on JBoss Cache.
Advanced optimization
Monitor JVM memory usage in JVM 5.0
You can use the following tools that ship with JVM 1.5 to monitor memory usage.
jstat -gc JVM_PROCESS_ID MONITORING_INTERVAL
e.g. jstat -gc 1234 5000
How to get a thread trace
A thread trace will help you see thread status and find thread blockers.
You can use the following command in Linux to get a thread trace.
kill -3 JVM_PROCESS_PID
