In this Article
| Table of Contents | ||||
|---|---|---|---|---|
|
Overview
Groundplex deployment comprises many factors for consideration. Most of these considerations are because of IT requirements in your computing environment, but some also depend on Pipeline production and the types of Pipelines you plan to run in production.
| Info |
|---|
Although 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. |
Computing Requirements
The Groundplex must conform to the following minimum specifications:
...
| 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. |
Supported Operating Systems
Groundplexes support the following operating systems:
...
For improved security, the Groundplex machine timestamp is verified to check if it is synchronized with the time stamp on the SnapLogic Cloud. Running a time service on the Groundplex node ensures that the timestamp is always kept synchronized.
For Linux, refer to Basic NTP Configuration for more details on setting up a NTP server.
For Windows, refer to Windows Time Service Technical Reference for more information.
A 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 time stamps, making it more difficult to debug issues.
Network Guidelines and Requirements
The following network guidelines and requirements apply to Groundplex deployments:
Network throughput
Network firewall
Network Throughput Guidelines
Groundplexes require connectivity to the SnapLogic Integration Cloud, and also connectivity to the cloud applications which may be used in your Tasks and Pipelines.
...
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:
...
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.
Network Guidelines for Snap Usage
In the SnapLogic Platform, the Snaps actually communicate to and from the application endpoints. The protocols and ports required for this communication are mostly determined by the endpoints themselves, and not by SnapLogic. Cloud and SaaS applications commonly communicate using HTTPS, although older applications and non-cloud or SaaS applications might have their own requirements.
...
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.
FeedMaster Node Ports
For Ultra Pipelines, the FeedMaster node listens on the following two ports:
...
The machine hosting the FeedMaster nodes needs to have those ports open on the local firewall, and the other Groundplex nodes need to allow outbound requests to the FeedMaster nodes on those ports.
Groundplex Name and Associated Nodes
Every Snaplex requires a name, for example, ground-dev or ground-prod. In the SnapLogic Designer, you can choose the Snaplex where Pipelines are executed.
...
The Dashboard shows the currently connected nodes for each Snaplex.
Understanding the Distribution of Data Processing across Snaplex Nodes
When a Pipeline or Task is executed, the work is assigned to one of the JCC nodes in the Snaplex. Depending on a number of variables, the distribution of work across JCC nodes is determined by the number of threads in use, the amount of available memory, and the average system load.
| Info |
|---|
To ensure that requests are being shared across JCC nodes, we recommend that you set up a load balancer to distribute the work across JCC nodes in the Snaplex. |
Node Cluster
Starting multiple nodes with the JCC service pointing to the same Snaplex configuration automatically forms a cluster of nodes, if you follow these requirements for nodes in a Snaplex:
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 CPU and memory configurations, as well as access to the same network endpoints.
JCC Node Communication within a Groundplex
We recommend that you set up JCC nodes in a Snaplex in the same network and data center. Communication between JCC nodes in the same Snaplex is required for the following reasons:
...