The settings in the ATG base configuration layer are optimized for application development, but are not appropriate for a production environment. When you’re ready to deploy your Nucleus-based application in a production environment, enable the settings in the liveconfig configuration layer. This layer overrides many of the default configuration settings with values that are more appropriate for a deployed site. For example, the liveconfig configuration layer improves performance by reducing error checking and detection of modified properties files.

To enable liveconfig, you can use the –liveconfig argument for runAssembler (see the Assembling Applications section of the ATG Platform Programming Guide), or add the following line to the WEB-INF/ATG-INF/dynamo.env file in the atg_bootstrap.war module of your EAR file:

atg.dynamo.liveconfig=on

JBoss Note: If you are using ATG Portals with JBoss, and you use the –liveconfig flag when you create your EAR file, you must also have a lock manager configured and running in order to create or edit communities. See the Locked Caching section of the ATG Repository Guide for information on lock management.

To disable liveconfig in an application in which it is currently enabled, either reassemble the application without the –liveconfig flag, or remove or set the liveconfig value to off in WEB-INF/ATG-INF/dynamo.env file in the atg_bootstrap.war module.