Applications deployed in RTF do not inherit proxy settings from the RTF cluster. You need to configure the proxy for each application. There are two approaches:
1. Configure the proxy at Runtime level so all the outbound components running in the Runtime can use the proxy. This approach is documented here at How to configure proxy in RTF (RunTime Fabric)http.nonProxyHosts=localhost|*.svc.cluster.local|*.monitoring.svc.cluster.local http.proxyHost=172.19.0.23 http.proxyPort=3128 https.proxyHost=172.19.0.23 https.proxyPort=3128 com.ning.http.client.AsyncHttpClientConfig.useProxyProperties=true2. Configure at each component level. This is useful if only certain components are allowed in the proxy.
This article is #2 approach and explains how to configure a proxy for API manager agent in RTF.
anypoint.platform.proxy_host=hostname anypoint.platform.proxy_port=port anypoint.platform.proxy_username=username anypoint.platform.proxy_password=password
001116932

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.