...

The Groundplex is a local server running on hardware , that may be virtual, provisioned by the customeryou, and must conform to the following minimum specifications:

...

For improved security, the Groundplex machine timestamp is verified to check if it is in sync with the timestamp on the SnapLogic cloudCloud. Running a time service on the Groundplex node will ensure ensures that the timestamp is always kept in sync.

...

Network Throughput Guidelines

You should consider that , when running, a Groundplex requires connectivity to the SnapLogic Integration Cloud when running, as well as connectivity to the cloud Cloud applications which may be used in the processes/Pipelines created and run in the your solution. To optimize performance, we recommend the following network throughput guidelines:

...

To communicate with the SnapLogic Integration Cloud, SnapLogic On-premises Snaplex uses a combination of HTTPS requests and WebSockets communication over the TLS (SSL) tunnel. In order for this combination to operate effectively, you must configure the firewall must be configured to allow the following network communication requirements:

...

In the SnapLogic Platform, the Snaps tactually communicate to and from the applications. The protocols and ports required for application communication are mostly determined by the endpoint applications themselves, and not by SnapLogic. It is common for cloudCloud/SaaS applications to communicate using HTTPS, although older applications and non-cloud/SaaS applications might have their own requirements. 

...

• Snaplex – Data processing on Groundplex, Cloudplex, and eXtremeplex nodes occur principally in-memory as streaming, which is unencrypted.

• Larger dataset – When larger datasets are processed that exceed the available compute memory, some Snaps like Sort and Join, which process multiple documents, writes write Pipeline data to the local disk as unencrypted during Pipeline execution to help optimize the performance. These temporary files are deleted when the Snap/Pipeline execution completes. You can update your Snaplex to point to a different temporary location in the Global properties table of the Node Properties tab in the Update Snaplex dialog:

...

Snaplex Network Binding

By default, the Snaplex starts a Snaplex starts and binds to the localhost network interface on port 8090. Any clients can connect to the JCC only if the client is also running on the same machine. This default is chosen since the Snaplex is does not be receiving receive any inbound requests normally. It instead Instead, it uses an outbound WebSocket connection to receive its requests from the SnapLogic cloud Cloud services. If requests need to be sent to the Snaplex from the customer network, then the Snaplex should be configured to you should configure the Snaplex to listen on its network interfaces. This would be required when a feed URL Pipeline execution request is done by pointing directly at the Snaplex host instead of pointing at the cloud Cloud URL. To do this, set (default is 127.0.0.1):

...

in the etc/global.properties by adding it to the Update Snaplex dialog, Node Properties tab, Global properties table.

If you need to configure the hostname used by the Snaplex needs to the Snaplex to be configured to be a different value than the machine name (for example newname.mydomain.com), add:

...

• For Snaplex instances with FeedMaster nodes, the load balancer should point to the FeedMaster nodes, like https://fm-node1.example.com:8084 and https://fm-node2.example.com:8084.
  A FeedMaster node can process Triggered and Utra Task requests, a JCC can process only Triggered Task requests. In the latter case, it is easier to use the FeedMaster node as the load balancer endpoint. The Ultra Task load balancer field value needs to be updated in the Snaplex settings with the load balancer URL.

• If there are no FeedMaster nodes, the load balancer can point to the JCC nodes, like https://jcc-node1.example.com:8081 and https://jcc-node2.example.com:8081. A JCC node can process only Triggered Task requests. Make sure you update the load balancer field value in the Snaplex settings with the load balancer URL.

• You should configure the load balancer to run health checks on the Snaplex node on the /healthz URL. Any other response code besides 200 indicates a health check failure.

• The load balancer should perform SSL offloading/termination so that the certificate and cipher management can be done on the load balancer without updating the Snaplex nodes. The connection between the client and the load balancer is over HTTPS with your signed certificate. The connection between the load balancer and the Snaplex nodes are also over HTTPS with the default SnapLogic generated certificate.

• You must set the HTTP request timeout to a value of 900 or higher to allow for long-running requests. This timeout setting is different from the keep-alive timeouts that are used for connection management, like the following examples:
  

  • The proxy_read_timeout for Nginx.

  • The ProxyTimeout for Apache.

  • The idle timeout for AWS ELB.The following image from the AWS UI shows a sample health check configuration for the AWS ELB.

...

...