...
| Info |
|---|
While Groundplex and Snaplex refer to the same thing, this article uses Snaplex in general when referring to the type of Asset in SnapLogic Manager, and Groundplex in the context of the computing resources underlying it. |
...
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, see Node Cluster. All nodes within a Snaplex must be of the same size. |
|---|---|---|
RAM (Min) | Minimum: 8GB | Depending on the size, number, and nature 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: 40GB Recommended: 100GB | 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, see Temporary Folder. SnapLogic does not in anyway restrict the disk size of your Groundplex nodes. |
| Info |
|---|
Memory (RAM) is used by the Pipelines to execute. Some Snaps, like 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. |
Supported Operating Systems
The SnapLogic on-premises Snaplex is supported on Groundplexes support the following operating systems:
CentOS (or Red Hat) Linux 6.3 or newer.
Debian and Ubuntu Linux.
Windows Server 2008 64-bit, Windows Server 2012, and Windows Server 2016 with a minimum of 8GB RAM.
You can also deploy a Groundplex:
On a Docker container
In a Kubernetes Environment
For improved security, the Groundplex machine timestamp is verified to check if it is in sync with the timestamp on the SnapLogic Cloud. Running a time service on the Groundplex node ensures that the timestamp is always kept in sync.
For Linux, see Basic NTP Configuration for more details on setting up a NTP server.
For Windows, see Windows Time Service Technical Reference for more information.
Large clock skew can also affect communication between the FeedMaster and the JCC nodes. The Date.now() expression language function might be different between Snaplex nodes, and Internal log messages might have skewed timestamps, making it more difficult to debug issues.
Network Requirements
Network Throughput Guidelines
...
The nodes of a Snaplex need to communicate among themselves, so it is important that they can each resolve each other's hostnames. This is required when you are making local calls into the Snaplex nodes for the execution of Pipelines rather than going 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 via the SnapLogic Control Plane that still uses TLS 1.2.
...
Each of these application connections may 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.
...
8084—The FeedMaster's HTTPS port. Requests for the pipelines are sent here as well as some internal requests from the other Groundplex nodes.
8089—The FeedMaster's embedded ActiveMQ broker SSL port. The other Groundplex nodes connects connect to this port to send/receive messages.
...
Every Snaplex requires a name, for example, ground-dev or ground-prod. In the SnapLogic Designer, you can choose on which Snaplex Pipelines are executed. The Snaplex configuration also has an Environment variable associated with it, for example, dev or prod. When you configure the nodes for the Snaplex, you must set the jcc.environment to the Environment value that you have configured for the Snaplex.
...