Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
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]
Here are general steps to get the remote engine working with HTTPS proxy:
Install Remote Engine (RE) but do not pair it. If the service was running, stop it before making any changes.
Modify the following files within the Remote Engine Installation folders:
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>
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