...
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 Self-managed Snaplex configuration has an Environment variable associated with it,
Your nodes are associated with a Grounplex 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 configured for the Snaplexprovided in the Create Snaplex dialog. You can change this variable in the Update Snaplex dialog.
The host name of the system used by a Groundplex can not have 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 the following folder:
Linux:
/opt/snaplogic/run/logWindows:
...
c:\opt\snaplogic\run\log
...
The Dashboard shows the currently connected nodes for each Snaplex.
...
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 JCC nodes in a Snaplex.
A Ground Triggered Task (invoked from a Groundplex) can be executed on a neighboring JCC node because of load-balancing, in which case, the Pipeline prepare request, and the bodies of the request and response, are transferred between nodes.
...