In AEM Mobile (AEMM), to find out more about the failing call flow we always need to recommend turning on debug logging for the connector

To turn on debug logging we should communicate what we always communicate to customers in this situation:

Logging

To set up logging of activities that happen in the integration go to:

• the Web Console or http://localhost:4502/system/console/configMgr (adapt the hostname:port “localhost:4502” to point to the AEM instance that you are troubleshooting)
• Select “OSGI”, then “Configuration” from the menu
• Find the section where the Sling Loggers are defined (search for "Apache Sling Logging Logger Configuration")
• Create a new factory configuration by clicking on the plus sign
• Enter the following properties
• • Log Level: start with Debug or switch directly to Trace
  • Log File: logs/dps.log
  • Message Pattern: unless you have a convincing reason to change it leave it to the default (this should be "{0,date,dd.MM.yyyy HH:mm:ss.SSS} *{4}* [{2}] {3} {5}")
  • Logger, add the following loggers

  • • org.apache.http --> if you want to see the activity at the wire between the DPS cloud services and your AEM instance

    • com.adobe.dps --> to see all the messages related to forming requests to and processing responses from the DPS cloud connection

    • com.adobe.cq.mobile.dps --> to see processing steps in the AEM Mobile bundles related to DPS

    • In rare cases you want com.adobe.client.ims --> to see the interactions with the authentication layer which is Adobe’s IMS

• Hit save to persist the settings
• Check the dps.log file for message and adjust the level if necessary