Overview
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 on. The Snaplex configuration has an environment 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 you’ve configured for the Snaplex.
The hostname of the system used by a Groundplex can not use an underscore (_) in its name as per DNS standards. Avoid special characters as well.
After the Snaplex service is started on a node, the service connects to the SnapLogic Cloud service. Runtime logs from the Snaplex are written to the /opt/snaplogic/run/log (or c:\opt\snaplogic\run\log) directory. The Dashboard shows the nodes that are currently connected for each Snaplex.
Best Practices for Setting Up JCC Node Intercommunication within a Groundplex
We recommend that you set up JCC nodes in a Snaplex within the same network and data center. Communication between JCC nodes in the same Snaplex is required for the following reasons:
The Pipeline Execute Snap communicates directly with neighboring JCC nodes in a Snaplex to start child Pipeline executions and send documents between parent and child Pipelines.
The data displayed in Data Preview is written to and read from neighboring JCC nodes in the Snaplex.
The requests and responses made in Ultra Pipelines are exchanged between a FeedMaster node and all of the JCC nodes in a Snaplex.
A Ground Triggered Task (invoked from a Groundplex) can be executed on a neighboring JCC node due to load-balancing—in which case, the prepare request and the bodies of the request and response are transferred between nodes.
Therefore, any extra latency or network hops between neighboring JCC nodes can introduce performance and reliability problems.
Snaplex Node Configuration
Snaplex nodes are typically configured using a slpropz configuration file, located in the $SL_ROOT/etc folder.
...
In this Article
| Table of Contents |
|---|
Overview
Groundplex deployment comprises many factors for consideration. Most of these considerations are due to 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 |
|---|
While Groundplex and Snaplex refer to the same thing, this article uses Snaplex in general when referring to the SnapLogic Manager, and Groundplex in the context of the computing resources underlying it. |
Name
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.
The hostname of the system used by a Snaplex can not use an underscore (_) in its name as per DNS standards. Avoid special characters as well.
After the Snaplex service is started on a node, the service connects to the SnapLogic Cloud service. Runtime logs from the Snaplex are written to the /opt/snaplogic/run/log (or c:\opt\snaplogic\run\log) directory. The Dashboard shows the nodes that are currently connected for each Snaplex.
Snaplex Node Configuration
Snaplex nodes are typically configured using a slpropz configuration file, located in the $SL_ROOT/etc folder.
If you use the slpropz file as your Snaplex configuration, then:
...
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:
...
in the etc/global.properties by adding it to the Update Snaplex dialog, Node Properties tab, Global properties table.
Best Practices for Setting Up JCC Node Intercommunication within a Groundplex
We recommend that you set up JCC nodes in a Snaplex within the same network and data center. Communication between JCC nodes in the same Snaplex is required for the following reasons:
The Pipeline Execute Snap communicates directly with neighboring JCC nodes in a Snaplex to start child Pipeline executions and send documents between parent and child Pipelines.
The data displayed in Data Preview is written to and read from neighboring JCC nodes in the Snaplex.
The requests and responses made in Ultra Pipelines are exchanged between a FeedMaster node and all of the JCC nodes in a Snaplex.
A Ground Triggered Task (invoked from a Groundplex) can be executed on a neighboring JCC node due to load-balancing—in which case, the prepare request and the bodies of the request and response are transferred between nodes.
Therefore, any extra latency or network hops between neighboring JCC nodes can introduce performance and reliability problems.
Load Balancer Guidelines
...