Announcement: You can find the guides for Commerce 7.5 and later on the new Elastic Path Documentation site. This Developer Center contains the guides for Commerce 6.13.0 through 7.4.1.Visit new site

This version of Elastic Path Commerce is no longer supported or maintained. To upgrade to the latest version, contact your Elastic Path representative.

EP Commerce for Adobe Marketing Cloud Logging

EP Commerce for Adobe Marketing Cloud Logging

EP Commerce for Adobe Marketing Cloud provides Apache Sling Logging to record and consolidate system debug output. By default, logs write to the error.log file in the AEM log directory. For more information on AEM logging, see AEM Logging.

Configuring Logging

Logging is configured through the Adobe Web Console. Using Web Console, you can define the log level and the log file to write to. We recommend you create a specific log file by setting the Logger to com.elasticpath. This will allow you to adjust your log level separately. For more information on adding a logger, see Logging.

Logging Cortex JAX-RS Client Traffic

JAX-RS Client Traffic client traffic logging is disabled by default. You must have your logger set to debug or higher to log any traffic.

To enable the JAX-RS Client traffic logger:
  1. In AEM Web Console, open the Elastic Path JAX-RS Configured Client Provider.
  2. Add a new entry to the Client Configurators List called client-logging
  3. Open the Elastic Path JAX-RS Client Logging Configurator and enable Jersey Client Logging
If you need to log the responses from Cortex, enable Jersey Client Entity Logging as well.