...

Overview

Your Self-managed Snaplex (Groundplex) allows access to endpoints that are in your network firewall. As a SnapLogic Org admin, you might typically involve your network admin or DevOps team from an organization to define the network settings of the Groundplex. Your Snaplex makes outbound HTTPS requests to the SnapLogic Control Plane. In addition to the SnapLogic Control Plane, the Snaplex also makes WebSocket Secure (WSS) outbound connections with the Control Plane, which uses this connection to send inbound control messages to the Snaplex. WSS is an extension of HTTPS that provides a standards-compliant and secure message-passing mechanism. The Groundplex does not require inbound network connectivity. The only requirement is outbound connectivity to the SnapLogic Control Plane over the HTTPS port 443.

A Groundplex also makes outbound connections to any endpoints referenced in a Pipeline. If the Pipeline running on the Snaplex communicates with Salesforce and Redshift endpoints, then the Snaplex makes outbound connections with Salesforce and Redshift databases. The protocol depends on the endpoint. Fore  For example, Salesforce Snaps use an HTTPS connection, and Redshift Snaps use a TCP connection, over TLS (SSL) optionally, to establish the JDBC connection.

...

HTTP Port Configuration

Use the Node Properties tab to change port values.

You can change the default values:

• 8090 for the JCC node

• 8091 for the FeedMaster node

HTTP Port Customization

You can customize the HTTP port configuration used by the JCC node. On the Node Properties tab in the Update Snaplex dialog, you can specify a value in the HTTP Port field.

...

jcc.jetty_port = 8090

HTTPS Port Customization

You can customize the HTTPS port configuration used by the JCC node. On the Node Properties tab in the Update Snaplex dialog, you can specify a value in the HTTPS Port field.

...

jcc.cc_secure_port = 8888

FeedMaster Broker Port Customization

You can customize the FeedMaster node port configuration used by the JCC node. The default is 8089. On the Node Properties tab in the Update Snaplex dialog, add the following entry in the Global properties table:

...

The port used should be unique and cannot be the same as the ports used for the HTTP and HTTPS services.

HTTP Connection Pooling

Outbound HTTP connections created to the SnapLogic cloud or to any other HTTP endpoints are placed in a connection pool by default. You can configure the properties for the pool in etc/global.properties by adding them to the Update Snaplex dialog, Node Properties tab, Global properties table.

...

The http_client_socket_timeout must be set to higher than the maximum child Pipeline execution time. 

HTTP Proxy Configuration

In the typical HTTP Proxy configuration, the proxy forwards 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.

...

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

Reverse Proxy Configuration

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.

...

Troubleshooting Snaplex Communication

This article covers some basic troubleshooting tips to test communication with the Snaplex.

...