...
The Groundplex must conform to the following minimum specifications:
Nodes (Min/Rec) | Minimum: 1 Recommended: 2 or more nodes | SnapLogic Project and Enterprise platform package nodes can be configured in the following sizes:
We recommend two nodes for high availability. For requirements about clustering nodes, refer to Node Cluster. All nodes within a Snaplex must be of the same size. |
|---|---|---|
RAM (Min) | Minimum: 8 GB | Depending on the size, number, and design of Pipelines, more RAM is required to maintain an acceptable level of performance. |
CPU (Min) | Minimum: 2 core | All Snaps execute in parallel in their own threads: the more cores that are available to the Snaplex, the more performant the system. |
Disk (Min/Rec) | Minimum: 80 GB Recommended: 100 GB | Local disk space is required for logging and for any Snap that uses the local disk for temporary storage (for example, Sort and Join Snaps). For details, refer to Temporary Folder. SnapLogic does not have restrictions on the disk size of your Groundplex nodes. |
| Info |
|---|
Memory (RAM) is used by the Pipelines to execute. Some Snaps, such as Sort Snaps, which accumulate many documents, consume more memory; the amount of memory used is influenced by the volume and size of the documents being processed. For an optimum sizing analysis based on your requirements, contact your SnapLogic Sales Engineer. |
...
To optimize performance, we recommend the following network throughput guidelines:
Guideline | Minimum | Recommended |
|---|---|---|
Network In (Min/Rec) | 10 MB/second | 15 MB/second+ |
Network Out (Min/Rec) | 5 MB/second | 10MB/second+ |
Network Firewall Requirements
To communicate with the SnapLogic Control Plane, Groundplexes use a combination of HTTP/HTTPS requests and WebSockets communication over the TLS (SSL) tunnel. For this combination to operate effectively, you must configure the firewall to allow the following network communication requirements:
Component | Required | Consequence |
|---|---|---|
HTTP outbound Port 443 | Yes | Does not function |
HTTP HEAD | Desired | Without HEAD support, a full GET request requires more time and bandwidth |
WebSockets (WSS protocol) | Yes | Does not function |
JCC node: 8090 (HTTP), 8081 (HTTPS) | Yes |
Needs to be available for communication between the nodes in a Snaplex. |
Feedmaster: 8090 (HTTP), 8084 (HTTPS), 8089 (Message queue) |
The nodes of a Snaplex need to communicate among themselves, so it is important that each node can resolve each other's host names. This requirement is crucial when you are making local calls into the Snaplex nodes for the execution of Pipelines instead of initiating it through the SnapLogic Platform. The Pipelines are load-balanced by SnapLogic with Tasks passed to the target node.
Communication between the customer-managed Groundplex and the SnapLogic-managed S3 bucket is over HTTPS with TLS enforced by default. The AWS-provided S3 URL also uses an HTTPS connection with TLS enforced by default. If direct access from the Groundplex to the SnapLogic AWS S3 bucket is blocked, then the connection to the AWS S3 bucket communication falls back to a connection through the SnapLogic Control Plane that still uses TLS 1.2.
...
For example, the following table shows some of these requirements:
Application | Protocol | Default Port |
|---|---|---|
Netezza | TCP | 5480 |
Oracle | TCP | 1521 |
RedShift | TCP | 5439 |
Salesforce | HTTPS | 443 |
Each of these application connections might allow the use of a proxy for the network connection, but it is a configuration option of the application’s connection—not one applied by SnapLogic.
...
The nodes need to communicate with each other on the following ports: 8081, 8084, and 8090.
The nodes should have a reliable, low-latency network connection between them.
The nodes should be homogeneous in that they should have similar the same CPU and memory configurations, as well as access to the same network endpoints.
All JCC nodes should be the same size. All FeedMaster nodes should be the same size for load balancing. Worker and FeedMaster nodes can be different sizes.
JCC Node Communication Requirements
...