Digital Publishing Solution (DPS 2015) is now part of Adobe Experience Manager Mobile.

There are several factors that can cause network communication problems between the Adobe Experience Manager (AEM) and the Adobe Experience Manager Mobile On-Demand Services:

  • Firewall block necessary hosts or ports
  • Proxy server configuration or authentication

The most common problems are: 1. Adobe Experience Manager Mobile servers are blocked by the IT department and need to be white-listed 2. Corporate proxy server needs authentication (or was given invalid credentials) to connect to external servers.

Check with the IT department that the Adobe Experience Manager servers are not being blocked. The following domains should be white-listed to ensure that communications with the necessary servers are allowed. See our knowledge base article for further infomation.

If problems still persist, it will be useful to enable network logging from the Adobe Experience Manager connection. See the Enabling Logging section below the white-lists for instructions.

White-list The Following Servers

Adobe Experience Manager Mobile Portal

  • http://aemmobile.adobe.com
  • https://aemmobile.adobe.com
  • https://adobedigitalpublishingportal.d1.sc.omtrdc.net
  • https://ps*.pubnub.com (will vary based on load balancing, for example, https://ps14.pubnub.com)
  • https://dpm.demdex.nethttps://adobe.demdex.net
  • https://wwwimages2.adobe.com 
  • https://ims-na1.adobelogin.com (identity management service)
  • https://amas.publish.adobe.io (account management and authorization service)
  • https://authorization.publish.adobe.io (authorization service)
  • https://pecs.publish.adobe.io (producer service)
  • https://ings.publish.adobe.io (ingestion service)
  • https://ps.publish.adobe.io (product service) 
  • https://migs.publish.adobe.iohttps://geo*.adobe.com (may vary, for example, https://geo2.adobe.com)
  • https://universal.iperceptions.com
  • https://origin.adobe-dcfs.com
  • http://www.adobe.com
  • https://www.adobe.com
  • https://mobilemarketing.adobe.com
  • https://omniture.tt.omtrdc.net
  • https://adobe.tt.omtrdc.net
  • https://my.omniture.com
  • https://www.omniture-static.com
  • https://sc-css-1.omniture.com
  • https://scripts.omniture.com
  • https://ab.publish.adobe.io
  • https://dps-ab-prod-s3-service-*.s3.amazonaws.com (will vary, for example, https://dps-ab-prod-s3-service-1xe1vppi79wya.s3.amazonaws.com)
  • https://s3.amazonaws.com
  • https://rps.publish.adobe.io
  • https://fonts.adobe.com
  • https://use.typekit.net
  • https://p.typekit.net
  • https://sstats.adobe.com
  • https://universal.iperceptions.com 
  • https://helpx.adobe.com (support)
  • https://api.behance.net (Behance integration
  • )https://assets.adobedtm.com
  • https://universal.iperceptions.com
  • https://*.vo.msecnd.net (will vary, for example, https://az452423.vo.msecnd.net)
  • https://*.cloudfront.net (will vary, for example, https://d13itkw33a7sus.cloudfront.net)

Adobe Experience Manager Mobile Apps (Including Adobe Preflight)

  • http://adobepublish*.sc.omtrdc.net (analytics service, will vary based on the data center used by a given application, for example, http://adobepublishdallas1.sc.omtrdc.net)
  • https://edge.publish.adobe.com (source of content downloads)
  • https://mobile-collector.newrelic.com (performance and crash logs)
  • https://es.publish.adobe.com (entitlement service)
  • https://cs.publish.adobe.com (configuration service)
  • https://rps.publish.adobe.io (rich push service)
  • https://logs.aemmobile.adobe.com (debug logging)

Adobe Experience Manager Mobile Web Viewer

  • https://viewer.aemmobile.adobe.com
  • https://edge.publish.adobe.com (content source)
  • https://es.publish.adobe.com (entitlement service)
  • http://adobedigitalpublishingjupiter*.sc.omtrdc.net (analytics service, will vary based on data center location, for example, http://adobedigitalpublishingjupitersanjose.sc.omtrdc.net)

Enable Logging in AEM Instance

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

  • Go to the Web Console or http://localhost:4502/system/console/configMgr
  • 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 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
      • com.adobe.dps --> to see all the messages related to forming requests to and processing responses from the DPS cloud connections
      • com.adobe.client.ims --> to see the interactions with the authentication layer which is IMS
      • com.adobe.cq.mobile.dps --> to see processing steps in the AEM Mobile bundles related to DPS
  • Hit save to persist the settings
  • Check the dps.log file for message and adjust the level if necessary

This log will provide the details of each call made to the servers along with the return value received. For example:

{tls}->http://proxy.server:80->https://ims-na1.adobelogin.com:443][total kept alive: 0; route allocated: 1 of 25; total allocated: 1 of 100]
06.12.2016 15:44:39.941 impl.execchain.MainClientExec Opening connection {tls}
->http://proxy.server:80->https://ims-na1.adobelogin.com:443
06.12.2016 15:44:40.350 impl.conn.HttpClientConnectionOperator Connecting to proxy.server/10.132.11.173:80
06.12.2016 15:44:40.351 impl.conn.HttpClientConnectionOperator Connection established 10.18.91.134:57664<->10.132.11.173:80
06.12.2016 15:44:40.351 headers http-outgoing-17732 >> CONNECT ims-na1.adobelogin.com:443 HTTP/1.1
06.12.2016 15:44:40.351 headers http-outgoing-17732 >> Host: ims-na1.adobelogin.com
06.12.2016 15:44:40.351 headers http-outgoing-17732 >> Proxy-Connection: Keep-Alive
06.12.2016 15:44:40.351 wire http-outgoing-17732 >> "CONNECT ims-na1.adobelogin.com:443 HTTP/1.1[\r][\n]"
06.12.2016 15:44:40.351 wire http-outgoing-17732 >> "Host: ims-na1.adobelogin.com[\r][\n]"
06.12.2016 15:44:40.351 wire http-outgoing-17732 >> "Proxy-Connection: Keep-Alive[\r][\n]"
06.12.2016 15:44:40.351 wire http-outgoing-17732 >> "[\r][\n]"
06.12.2016 15:44:40.353 wire http-outgoing-17732 << "HTTP/1.1 400 Bad Request[\r][\n]"
06.12.2016 15:44:40.353 wire http-outgoing-17732 << "Content-Type: text/html[\r][\n]"
06.12.2016 15:44:40.353 wire http-outgoing-17732 << "Date: Tue, 06 Dec 2016 20:44:39 GMT[\r][\n]"
06.12.2016 15:44:40.353 wire http-outgoing-17732 << "Connection: close[\r][\n]"
06.12.2016 15:44:40.353 wire http-outgoing-17732 << "Content-Length: 34[\r][\n]"
06.12.2016 15:44:40.353 wire http-outgoing-17732 << "[\r][\n]"
06.12.2016 15:44:40.353 wire http-outgoing-17732 << "Bad Request (Invalid URL)"
06.12.2016 15:44:40.353 headers http-outgoing-17732 << HTTP/1.1 400 Bad Request
06.12.2016 15:44:40.353 headers http-outgoing-17732 << Content-Type: text/html
06.12.2016 15:44:40.353 headers http-outgoing-17732 << Date: Tue, 06 Dec 2016 20:44:39 GMT
06.12.2016 15:44:40.353 headers http-outgoing-17732 << Connection: close
06.12.2016 15:44:40.353 headers http-outgoing-17732 << Content-Length: 34

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy