In this article

Configuring the Script Snap to Use

...

an HTTP Proxy

HTTP-compatible Snap Packs can use a an HTTP proxy configured in the Node Proxies configuration tab of a Snaplex within SnapLogic Manager. However, the Script Snap allows you to write scripts that call external processes (for example:, curl), and these scripts will are not be aware of proxy configurations within the SnapLogic application. 

...

Environment variables declared within the /etc/sysconfig/jcc file are visible to the Snaplex application (OS-level environment variables are not visible). If the /etc/sysconfig directory and /etc/sysconfig/jcc file does do not exist in your Snaplex, run the following command with your own username/password (if authentication is required), proxy-ip-address, and port (you could also add https_proxy) to create them:

...

The Snaplex process creates outbound WebSocket connections to the SnapLogic cloud to be able to process incoming requests from the cloud. If running several nested Pipelines, or Pipelines using ForEach, there could be timeout errors if no connection is available to process an inbound request. By default, 20 connections are created. This can be increased if a higher number of cloud-triggered Pipelines need to be run concurrently on the Snaplex node. The maximum allowed value is 60. Setting this too high causes increased network overhead. If this has to be set to a larger value, it is an indication that more nodes need to be added to the Snaplex. Pipeline execution requests are automatically load-balanced across the available nodes.

To increase this limit, change the default of 20 to a higher value: in . In the etc/global.properties by adding it to the Update Snaplex dialog, Node Properties tab, Global properties table:

...