HTTP Proxy Setup (4.0)
 is capable of routing outgoing HTTP traffic through an HTTP proxy. It is useful but not limited to a network setup where the execution context has limited access to the internet. A configuration has to be performed on each Execution Context (EC) that is required to run HTTP traffic through a proxy.
Proxy support is available for:
HTTP APL functions
HTTP Batch agent
GCP PubSub Subscriber agent
GCP PubSub Publisher agent
GCP BigQuery agent
HTTP/2 Client agent
Salesforce Streaming agent
Web Services agents
This chapter has the following sections:
Configuring the System Properties
You can configure a set of system properties when creating ECDs in Desktop, see Creating an EC Deployment (4.0) in order to use the Proxy functionality.
Note!
At least one of these properties has to be set to use HTTP Proxy:
http.proxyHost
https.proxyHost
Bypassing Proxy Configuration
It is possible to provide a list of destination hosts that should not be routed through the proxy. Check the Proxy Properties table in EC Properties(3.2) for how to configure it.
Note!
Here the IP(v4) address of the cluster running the Usage Engine EC Deployment should be added to the list of non proxy hosts for example we can configure something like below. In this example, 10.43.0.1 is the cluster IP. This is necessary as we do not support proxy for internal servers.
http.nonProxyHosts = 10.43.0.1 | other.ip.addrs | 192.168.1.18
Authenticating the Proxy Server
Usage Engine supports basic authentication for HTTP proxy. The username and password are configured using the system properties file. Check the Proxy Properties table in EC Properties(3.2).
Example Configuration
Here is an example of configuring the system properties to use HTTP Proxy.
Use the EC Deployment - EC Advanced Properties editing process to edit the system properties. See, Editing an EC Deployment(3.2).
EC Deployment Overview
Edit System Properties