How to configure a Remote Engine with HTTPS proxy (Winter'17)

Talend Version          Winter ‘17 (TIC)

Summary

 
Additional Versions Fall '17 (TIC)
Product Talend Integration Cloud
Component Remote Engine TIC HTTPS proxy connection
Problem Description

When using an HTTPS proxy, some additional configuration steps need to be done.

For example:

<httpsproxyHost>: 96.239.193.241
<httpsproxyPort>: 8080
<httpsproxyUser>: talendproxy
<httpsproxyPassword>: 13!)4543G

 

If those steps are not taken, some errors might appear in the remote engine's karaf log, in addition to the fact that flows won't be running successfully on the remote engine:

ActiveMQ Task-1 | FailoverTransport | 190 - org.apache.activemq.activemq-osgi - 5.13.3 | Failed to connect to [https://msg.integrationcloud.talend.com:443]
Problem root cause  
Solution or Workaround

Here are general steps to get the remote engine working with HTTPS proxy:

  1. Install Remote Engine (RE) but do not pair it. If the service was running, stop it before making any changes.

     

  2. Modify the following files within the Remote Engine Installation folders:

    1. Add the following lines to the etc\system.properties file:

      https.proxyHost=<proxyServer>
      https.proxyPort=<proxyPort>
      https.nonProxyHosts=127.0.0.1|localhost
      https.proxyUser=<proxyUser>
      https.proxyPassword=<proxyPassword>

      img2.png

       

    2. Add the following line to the etc\org.talend.ipaas.rt.pairing.agent.cfg file:

      amq.proxy=96.239.193.241:8080
      img3.png

      Note: Starting with the Fall '17 release, the remaining steps in this section are not necessary if there is no password.

    3. Add this line to the etc\org.ops4j.pax.url.mvn.cfg file:

      org.ops4j.pax.url.mvn.settings=${karaf.home}/settings.xml

       

    4. Add the attached settings.xml file to the root folder of the RE installation folder, and modify it as follows:

      <proxies>
        <proxy>
          <protocol>https</protocol>
          <host>96.239.193.241</host> 
          <port>8080</port> 
          <username>talendproxy</username> 
          <password>13!)4543G</password> 
          <nonProxyHosts>localhost|127.0.0.1</nonProxyHosts> 
         </proxy> 
      </proxies>

      img4.png

       

    5. Modify the file etc/org.talend.eventlogging.sender.jms.cfg as follows:

      from

      # JMS connection url
      sender.destination.jms.url = failover:(https://msg.integrationcloud.talend.com:443)

      to

      # JMS connection url
      sender.destination.jms.url = failover:(https://msg.integrationcloud.talend.com:443?proxyHost=96.239.193.241&proxyPort=8080&proxyuser=talendproxy&proxyPassword=13!)4543G)

      Warning!

      If your proxy password or/and proxyLogin contains special characters it will need to be encoded.

      So in the case of proxyPassword = 13!)4543G, using www.urlencoder.org (for example) produces 13%21%294543G%0D%0A.

      # JMS connection url
      sender.destination.jms.url = failover:(https://msg.integrationcloud.talend.com:443?proxyHost=96.239.193.241&proxyPort=8080&proxyuser=talendproxy&proxyPassword=13%21%294543G%0D%0A)

      img5.png

       

    6. Modify the file etc/org.talend.ipaas.rt.eventsource.amq.cfg, in a similar way to step e.

      from

      activemq.broker.url = failover:(https://msg.integrationcloud.talend.com:443)

      to

      activemq.broker.url = failover:(https://msg.integrationcloud.talend.com:443?proxyHost=96.239.193.241&proxyPort=8080&proxyuser=talendproxy&proxyPassword=13%21%294543G%0D%0A)

      img6.png

       

  3. Start RE and pair it.

     

JIRA ticket number  
Version history
Revision #:
10 of 10
Last update:
‎03-21-2018 01:36 PM
Updated by:
 
Labels (1)