Warming the cache is when we want to preemptively fetch repository items from the database in anticipation of future use. This article address how to warm the cache for optimal web page performance, explaining the following: determining whether warming is really necessary, fixing root cause of latency, limiting warming to active items, item size reduction, avoiding warming items that result in excessive startup delay, among other techniques.

JVM settings are a much discussed topic among Oracle Commerce clients. Optimal settings can only be obtained after tuning activities, which can take many iterations of collecting data, analyzing logs and fine-tuning JVM settings. These settings are unique to each client and therefore not possible to have a “one size fits all” solution. This article provides some JVM settings that can be used as a starting point as a way of providing guidance to those who are starting on the journey to configure and/or setup their environment. Restricted to versions 7 and 8 of the Hotspot JVM.

You can quickly install Oracle ATG Commerce and configure it in Oracle Public Cloud (OPC) using Oracle-provided images from the Oracle Cloud Marketplace. These images are based on the Oracle ATG Commerce provisioning process.

A predefined configuration template and corresponding orchestration files are provided; allowing the end user to have an ATG demo environment running quickly.

Oracle ATG Commerce provisioning tool set allows for rapid deployment of the ATG Commerce stack. The tool set contains three components that can be used independently or together to create a Cloud provisioning, software installation and software configuration solution.

The Oracle ATG Commerce stack is comprised of several integrated software packages. All tools are written in Python and tested against Solaris SPARC and Oracle Linux, but will likely work on any flavor of Linux/Unix with an appropriate Python interpreter.

This article contains tips on how to optimize one-off queries returned in Endeca. One tip is to scan for stand-alone Endeca queries in the code. It also recommends improving queries by limiting which properties to return on a record, limiting the number of records to return, and omitting supplemental objects.

This set of tools allows management of Oracle ATG Commerce Content Administration (a.k.a The BCC) via REST services. These tools facilitate managing an Oracle ATG Commerce installation in the cloud environment without the need to manually use the BCC.

These tools also enable bursting, or auto-scaling an ATG cluster, and ATG instances can be added or removed from an existing cluster without the need to manually modify the BCC topology.

This error happens because the version of the tag library (taglib) in your running web app does not match the version of the updated taglib in DAS. This article shows you how to fix this problem by updating your project’s tag library, i.e. copy the DAS tag libraries to your application. Maintaining an updated, supported environment avoids harmful side effects that could occur as a result of running an environment with mismatching version of the tag libraries.

A company’s website is but one piece of the puzzle in a customer’s journey. This journey is a “sales funnel,” where thousands or even millions of potential customers are filtered down, nurtured and guided toward a sale. In an online retail environment, this maps quite well to Oracle Marketing Cloud, Oracle Content Marketing, WebCenter Sites and Oracle Commerce. Having all touchpoints managed end-to-end is what “Modern Marketing” is all about.

Assets in catalogs and related assets have grown exponentially in e-commerce. The fastest way to access these assets is the local, in-memory caching, but it’s limited by heap size growth, increased database pressure, etc. This white paper discusses an alternative: external caching. A coherence grid enables application caching to scale horizontally by many orders of magnitude when compared with traditional in-memory caching.

Global debugging can help solve complex problems in an ATG Commerce application. This debugging overrides the loggingDebug settings of all components, in all scopes, regardless of their individual loggingDebug settings. This is achieved through an entry in a single file that appears at the end of the CONFIGPATH, which is how it overrides all other settings. You can configure other settings globally in this file as well, but this post will focus on debugging.