...
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 Guidelines and Requirements
The following requirements are for network guidelines and requirements apply to Groundplex deployments:
Network throughput
Network
...
firewall
Network Throughput Guidelines
You should consider that a Groundplex requires Groundplexes require connectivity to the SnapLogic Integration Cloud when running, as well as connectivity to the Cloud applications which may be used in the processes/Pipelines created and run in your solution. your Tasks and Pipelines.
To optimize performance, we recommend the following network throughput guidelines:
...
To communicate with the SnapLogic Integration Cloud, SnapLogic On-premises Snaplex uses Groundplexes use 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 to allow the following network communication requirements:
...
In the SnapLogic Platform, the Snaps tactually actually communicate to and from the applicationsapplication endpoints. The protocols and ports required for application this communication are mostly determined by the endpoint applications endpoints themselves, and not by SnapLogic. It is common for Cloud/ Cloud and SaaS applications to commonly communicate using HTTPS, although older applications and non-cloud /or SaaS applications might have their own requirements.
...
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.
FeedMaster Node Ports
The 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.
Name
Every Snaplex requires a name, for example, ground-dev or ground-prod. In the SnapLogic Designer, you can choose 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.
...
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 memory available, 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, as long as you follow these requirements for nodes in a Snaplex:
...