In this article
Table of Contents | ||||
---|---|---|---|---|
|
Overview
Snaplex is a data processing engine used for Pipeline execution. A Snaplex contains multiple nodes and can be a Cloudplex or a Groundplex.
Prerequisites
Note |
---|
|
- To create a Snaplex, navigate to the target project in SnapLogic Manager, do either of the following actions:
- Click and from the dropdown list select Snaplex
OR - Click the Snaplex tab in the page that displays the assets for that Project.
The Create Snaplex dialog displays.
- Click and from the dropdown list select Snaplex
- Click each tab to configure the settings for the Snaplex.
- Click Create.
Info | ||
---|---|---|
| ||
SnapLogic supports the Slack messaging app within the SnapLogic platform communications, enabling you as an Org admin to add Slack channels and recipients for your SnapLogic communications. Learn more about adding Slack communications to your Org, SnapLogic Notifications through Slack. |
Configuring the Snaplex Settings
The Create Snaplex dialog contains the following tabs:
- Settings
- Logging
- Node Properties
- Node Proxies (enabled only for Groundplex nodes).
Settings Tab
Snaplex type | Select the Snaplex you want to create from the list. Default Value: Snaplex | ||
---|---|---|---|
Name | Specify a unique name for the Snaplex. The name must not exceed 100 characters.
Default Value: None | ||
Location | Select the location where the Snaplex must be created. The available options are:
Default Value: Sidekick | ||
Environment | Specify the value to configure the Snaplex nodes. Alphanumeric characters and the following special characters are allowed: Default Value: None
| ||
Version | Specify the version of the SnapLogic Platform on which you want the Snaplex to run.
Default value: Default | ||
Minimum nodes per Snaplex | The minimum number of nodes that must be kept alive even when there is no activity in the Snaplex. This property ensures that when a Pipeline that runs on the Snaplex is validated, at least one node is available to perform the validation. Minimum value: 1 Default Value: 1 | ||
Email address for notifications | List the email addresses for notification if one of the Snaplex nodes does not respond for fifteen minutes. Example: testuser@snaplogic.com Default Value: N/A | ||
Slack Channel for notifications | Specify the name of Slack channels (separated by commas) to notify if one of the Snaplex nodes does not respond in fifteen minutes. Default Value: None | ||
Slack user for notifications | Enter the Slack recipients (separated by commas) to notify if one of the Snaplex nodes does not respond for fifteen minutes. Default Value: N/A | ||
Load balancer | Specify the URL for the load balancer for Triggered Task execution requests. The load balancer URL has to be fully qualified, including the protocol.
Default Value: None | ||
Ultra load balancer | The URL of the FeedMaster load balancer for Ultra Pipeline execution requests.
Default Value: None Example: https://ultralb.mydomain.com |
Snaplex Configuration changes
Snaplex nodes are typically configured using a slpropz
configuration file, located in the $SL_ROOT/etc folder
.
...
You should always configure your Snaplex instances using the slpropz file because you do not have to edit the configuration files manually. Changes to the Snaplex done through Manager are applied automatically to all nodes in that Snaplex.
Load Balancer Settings
For Snaplex triggered pipeline and for Ultra API calls, a load balancer needs to be configured. SnapLogic will provision the load balancer for Cloudplexes when the Ultra feature is enabled. For Groundplexes, the customer has to provision the load balancer. After the load balancer is provisioned, the load balancer URL needs to be configured in the Snaplex properties. This will ensure that task details show the load balancer URLs rather than pointing to the Snaplex nodes.
...
Maximum slots | Each Snap in a Pipeline consumes a slot; so Pipelines can only be executed on nodes where the number of slots in use is below this threshold. Otherwise, they will fail or queued, depending on how they were executed. The number of slots in use corresponds to the number of active threads on a node, which can be viewed in the Snaplex Health dashboard. Default Value: 4000 A heuristic to use is that 2000 slots can be allocated per 8GB of RAM available on each Snaplex node. So for nodes with 16GB of RAM, use 4000 as the slot count. Reserved slots are used when a Pipeline or validation is executed manually from SnapLogic Designer. If no slots are reserved, then these interactive Pipeline executions—Pipeline executions run from Designer for testing or validation purposes—can be blocked by long running executions. You can adjust this setting based on your experience if the default value is not optimal. To reserve more slots for interactive sessions, set your value lower. If the Snaplex is not being used for interactive Pipeline building, set this value higher. | ||
---|---|---|---|
Reserved slot % | The percentage of slots that you want to reserve on a node for Pipelines executed through the Designer tab. Pipelines executed using Tasks or the ForEach Snap will not have access to these slots.
Default value: 15 | ||
Maximum memory % | The memory threshold at–and above–which no more Pipelines can be assigned to a node.
Default value: 85 | ||
Heap max size | Groundplex only. The maximum JVM heap size. Default value: auto (meaning that SnapLogic will automatically set the max heap size based on the available machine memory). | ||
HTTP Interface | Groundplex only. Specify the location from which the Snaplex node can accept HTTP network connections. The following options are available:
Default Value: Localhost only (127.0.0.1) | ||
HTTP Port | Groundplex only. The HTTP port on which the Snaplex node listens for connections. Default Values: 8090 for a JCC node and 8091 for a FeedMaster. | ||
HTTPS Port | Groundplex only. The HTTPS port on which the Snaplex node listens on for connections. Default Values: 8081 for a JCC node and 8084 for a FeedMaster. | ||
Restart Max Wait Time | The maximum wait time before restarting a node. Default Value: 15 minutes | ||
Global Properties (Key/Value pairs) | Groundplex only. Internal configuration options. Do not edit these values without contacting SnapLogic Customer Support. Default Value: No default value. |
...