...
iIn this Article
| Table of Contents | ||||
|---|---|---|---|---|
|
...
CentOS (or Red Hat) Linux 6.3 or newer.
Debian and Ubuntu Linux.
Windows Server 2016/2019/2022 with a minimum of 8 GB RAM.
...
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 the 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.
To successfully implement the Zero Trust policy on the Kubernetes in any environment, use the following S3 URLs.
snaplogic.com is required for all users.
snaplogic-prod-sldb.s3.amazonaws.com and s3.amazonaws.com access is required for file operations that use
sldbprotocol (For example, FileReader / FileWriter Snaps that are configured to usesldbprotocol).
Learn more about Snaplex network set upsetup.
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.
...
Your nodes are associated with a Grounplex Groundplex through the Environment variable: for example, dev or prod. When you configure the nodes for your Groundplex, you must set the jcc.environment to the Environment value that you provided in the Create Snaplex dialog. You can change this variable in the Update Snaplex dialog.
...
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 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 of different sizes.
Node Diagnostics
Snaplex Diagnostics helps you verify your Snaplex host environment and troubleshoot any issues. Each Snaplex node is a JCC instance running on a host, and the node diagnostic test highlights the hardware and thread limits requirements. It checks for minimum hardware requirements such as RAM and disk storage. The details of the test are listed in the table below. For more information on how to view the node details panel, refer to https://docs.snaplogic.com/monitor/node-details-panel.html
Diagnostic test | Recommended value | Examples of current value displayed in the diagnostic test |
Nodes have insufficient swap space | If the maximum value is not present, the system displays the value of 50% of the RAM configured or 8GB, whichever is greater. | If the value is not as per the recommended value the current value is displayed in red. |
Max Slots | If there is no minimum value, then the recommended value is calculated as follows: RAM configured or 8GB) * 2000 (max value) rounded to the nearest 500. | Example: If the maximum value is 3840, the current value displayed is 4000 |
Thread limit | Minimum value = 65000 | Displays the thread limit in red if the value is below the recommended value. Example: 4000 |
Max file descriptors | If there is no maximum value and the minimum value is 65000, then the recommended value should be 65000. | Example: 65535 |
Max jvm heap | The minimum and the recommended value is calculated as follows: Minimum value = 12GiB Recommended value = 12GiB | Example: 12.44 GiB |
RAM configured | Minimum value = 4GiB Recommended value = 4 GiB | Example: 2.73% |
RAM available | More than 15 minute period per day where memory utilization is > 75% or average memory utilization is > 60% | Example: 2.78% |
Disk storage configured | Minimum value: 40GiB Recommended value: 100GiB | Example: 39.98 GiB |
JCC Node Communication Requirements
...
Any extra latency or network hops between neighboring JCC nodes can introduce performance and reliability problems.