Creating a Gold Copy of Adobe CQ – Part 3 of 5- Sanity Check Configurations

by | Oct 28, 2013 | Adobe CQ, Web Content Management | 0 comments

This group of configurations can be performed after installing Adobe CQ, just as we did with the  previous group (See Part 2: Custom Configurations.) This group of configurations is slightly different in that they can also be applied after having your instance running for some time. You will need different configurations for different environments (CI, QA, STAGING, PRODUCTION, etc) so run-modes will be used to set configurations for proper environment. Here are the steps that need to be completed for Sanity Check Configurations:

  1. Version Purge: in a standard installation AEM creates a new version of a page or node when you activate a page after updating the content. This default behavior can be customized to meet your requirements. These versions are never purged, so the repository size will grow over time and therefore need to be managed. You must limit the total number of versions AEM will remember.
  2. Custom Bundle’s logs: You can set AEM to create a separate log file for your custom bundles and jsp files; this will be really helpful for developers and system administrators as messages will be logged in different files and at different levels.
  3. CQ WCM page statistics/CQ multivariate statistics: Disable Page statistics and multivariate testing statistics for all environments in case you use other statistical tools.
  4. CRX Bundle cache Size: This caches bundles, consisting of a node with all its properties. This is used by all bundle-based Persistence Managers.  The default size of BundleCache is 8MB. If this is too small it can cause an excessive number of read-accesses to the underlying persistence layer.
  5. DAM renditions: By default AEM creates multiple thumbnails for images uploaded to DAM. Should authors not use such images then DAM renditions might be disable.
  6. CQ HTML Library Manager Settings: Configure this to control the handling of client libraries (css or js); including, for example, how the underlying structure is seen. For production instances (enable Minify, enable Gzip, disable Debug, disable Timing) and For JS development (disable Minify, enable Debug, enable Timing, enable Debug console).
  7. Email Service Configuration: configure servers and credentials for email notifications, mainly for email campaigns.

Up to know we’ve performed basic configurations to customize our instances. The next group is a most set of configurations to ensure proper access. Think of Adobe CQ’s CRX as a Data Base Management System (DBMS) you wish to protect access to.


Need a bit more info on how Armedia can help you?

Feel free to schedule a 30-minute no-obligations meeting.


Submit a Comment

Your email address will not be published. Required fields are marked *