In this article

...

The proxy settings are configured per the standard JRE settings. These are exposed in the Node Proxies tab of your Snaplex in SnapLogic Manager.

jcc.http.proxyHost = myproxy.example.com
jcc.http.proxyPort = 3128
jcc.http.nonProxyHosts = localhost|127.*|[::1]|MYHOSTNAME|*.example.com
jcc.https.proxyHost = myproxy.example.com
jcc.https.proxyPort = 3128
jcc.https.nonProxyHosts = localhost|127.*|[::1]|MYHOSTNAME|*.example.com
jcc.http.proxyUser=proxyuser
jcc.http.proxyPassword=proxypass

Configuring the Script Snap

...

to Use a HTTP Proxy

HTTP-compatible Snap Packs can leverage an use a HTTP proxy configured in the Snaplex’s Network the Node Proxies configuration tab tab of a Snaplex within the SnapLogic Manager web application. However However, the Script Snap is different because allows you can to write Scripts to scripts that call external processes (e.g.processes (for example: curl) and  and these scripts will not be aware of any proxy configuration set configurations within the SnapLogic application. 

curl You can be configured use curl to use configure a proxy directly via the --proxy argument. To enforce proxy usage across all usages of the Script Snap, set the http_proxy and/or https_proxy environment variables within a special the following file:

/etc/sysconfig/jcc. 

Environment variables declared within this file will be the /etc/sysconfig/jcc file are visible to the Snaplex application (OS-level env vars will not be). This file (and directory) may environment variables are not visible). If the /etc/sysconfig directory and /etc/sysconfig/jcc file does not exist in your Snaplex, so you may have to create them (similar to the instructions on the Configuring a custom JRE version page), substituting the equivalent values for run the following command with your own username/password (if authentication is required), proxy-ip-address, and port (you could also add https_proxy) .For exampleto create them:

sudo mkdir -p /etc/sysconfig; sudo sh -c "echo 'export http_proxy=username:password@proxy-ip-address:port' >> /etc/sysconfig/jcc"

Once this file is After the file and its directory are created, run one of these the following commands to restart restart the Snaplex application: 

/opt/snaplogic/bin/jcc.sh restart
 
c:\opt\snaplogic\bin\jcc.bat restart

The http_proxy/https_proxy environment variable is now active within the SnapLogic product.   You can now run your Script that calls script to call the external process.

For example, the following Script Snap uses the subprocess library to execute curl and adds the response body to the output document.

# Import the interface required by the Script snap.
from com.snaplogic.scripting.language import ScriptHook
import subprocess

class TransformScript(ScriptHook):
    def __init__(self, input, output, error, log):
        self.input = input
        self.output = output
        self.error = error
        self.log = log

    # The "execute()" method is called once when the pipeline is started
    # and allowed to process its inputs or just send data to its outputs.
    def execute(self):
        self.log.info("Executing Transform script")
        while self.input.hasNext():
            try:
                # Read the next input document, store it in a new dictionary, and write this as an output document.
                inDoc = self.input.next()
                proc = subprocess.Popen(['curl','https://www.snaplogic.com'], stdout=subprocess.PIPE)
                (out, err) = proc.communicate()
                outDoc = {
                    'original' : out
                }
                self.output.write(inDoc, outDoc)
            except Exception as e:
                errDoc = {
                    'error' : str(e)
                }
                self.log.error("Error in python script")
                self.error.write(errDoc)

        self.log.info("Script executed")

    # The "cleanup()" method is called after the snap has exited the execute() method
    def cleanup(self):
        self.log.info("Cleaning up")

# The Script Snap will look for a ScriptHook object in the "hook" variable. The snap will then call the hook's "execute" method.
hook = TransformScript(input, output, error, log)

On execution, the proxy access log shows the request being routed through the proxy.

Troubleshooting

To verify if outbound requests are permitted from the Snaplex node, run:

...

The above configuration is the typical HTTP Proxy configuration, a forward proxy, which can forward requests to any endpoint. You can use the same HTTP proxy for connecting with the SnapLogic control plane and also for connecting to other REST endpoints, such as Salesforce. Forward HTTP proxy type is the most flexible method for integrating multiple endpoints. In some scenarios, your network operations team can configure a reverse proxy instead of a forward proxy. In that case, all requests to the proxy are directly sent to the SnapLogic control plane. For example, if https://myproxy.test.com/ is the proxy server, a request will return the status from the SnapLogic control plane.

For example:

...

To enable the Snaplex to work with the reverse proxy, add the following information to your Snaplex properties:

...

• Adding the SnapLogic Platform to your Allowlist

• Configuring the Script Snap to use a configured HTTP proxy environment variable