Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

DTM integration proxy settings

Avatar

Level 3

Hi,

We are trying to integrate DTM with AEM 6.2 (service pack 1) but we are getting timeout issues.

We got the proxy settings configuration under com.day.commons.httpclient and am able to connect to analytics server. So, we are assuming there are no issues with proxy settings. 

We debugged bit more, and found that the DTM is using org.apache.http.impl.client.CloseableHttpClient to get client connection. In earlier releases, it is using org.apache.commons.httpclient.HttpClient.

(please check http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manage...  to verify that earlier versions are using  org.apache.commons.httpclient.HttpClient)

We added proxy details under org.apache.http.proxyconfigurator (Apache HTTP Components Proxy Configuration) as well with no luck.

Below is the error we are getting when trying to connect to DTM.   

21.04.2017 14:22:36.655 *ERROR* [0:0:0:0:0:0:0:1 [1492748514233] POST /etc/cloudservices/dynamictagmanagement/ret/jcr:content.companies.json HTTP/1.1] com.adobe.cq.dtm.impl.util.DTMConfigurationUtil Failed to obtain a response from the DTM API Server.
org.apache.http.conn.HttpHostConnectException: Connect to api.omniture.com:443 [api.omniture.com/192.243.232.77] failed: Connection timed out: connect
        at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:140)
        at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:318)
        at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:363)
        at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:219)
        at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
        at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)
        at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
        at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
        at com.adobe.cq.dtm.impl.util.DTMConfigurationUtil.callDTMApi(DTMConfigurationUtil.java:212)
        at com.adobe.cq.dtm.impl.servlets.DTMCompaniesServlet.doPost(DTMCompaniesServlet.java:62)
        at org.apache.sling.api.servlets.SlingAllMethodsServlet.mayService(SlingAllMethodsServlet.java:149)

1 Accepted Solution

Avatar

Correct answer by
Level 3

Hi Guys,

If you are looking for solution for above issue, we need to use new org.apache.http.proxyconfigurator configuration for DTM.

Below is the response from DTM development team.

Note that between AEM 6.1 and AEM 6.2, the DTM code-base has been updated to use the new Apache HttpComponents instead of the legacy Apache Commons HttpClient which is EOL.

This change requires an additional Proxy Configuration under /system/console/org.apache.http.proxyconfigurator.

View solution in original post

0 Replies

Avatar

Level 3

Hi Prince,

yeah, i followed those links but no luck, we are getting same exception. Have you integrated DTM with AEM 6.2 over proxy?

Avatar

Correct answer by
Level 3

Hi Guys,

If you are looking for solution for above issue, we need to use new org.apache.http.proxyconfigurator configuration for DTM.

Below is the response from DTM development team.

Note that between AEM 6.1 and AEM 6.2, the DTM code-base has been updated to use the new Apache HttpComponents instead of the legacy Apache Commons HttpClient which is EOL.

This change requires an additional Proxy Configuration under /system/console/org.apache.http.proxyconfigurator.

Avatar

Level 1

Make changes to "Apache HTTP Components Proxy configuration" and it should work.