Skip to main content
Announcements
NEW: Seamless Public Data Sharing with Qlik's New Anonymous Access Capability: TELL ME MORE!

Talend Integration Cloud: How to configure a Remote Engine with HTTPS proxy

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
TalendSolutionExpert
Contributor II
Contributor II

Talend Integration Cloud: How to configure a Remote Engine with HTTPS proxy

Last Update:

Jan 22, 2024 9:35:30 PM

Updated By:

Jamie_Gregory

Created date:

Apr 1, 2021 6:00:40 AM

This article applies to Talend Winter ´17.

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]

Resolution

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>

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

      amq.proxy=96.239.193.241:8080

      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>

    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=talend...)
      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=talend...)

    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=talend...)

  3. Start RE and pair it.
Version history
Last update:
‎2024-01-22 09:35 PM
Updated by: