In this article
...
| Snaplex Type | Specify whether the Snaplex you want to create is a standard Snaplex. Default value: Snaplex | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Name | The name for the Snaplex. The name must not exceed 100 characters.
Default value: No default value. | ||||||||
| Location | Specify whether the Snaplex must be created in the cloud or on premises. Select from the following options:
Default value: sidekick | ||||||||
| Environment | Enter the value used to configure the Snaplex nodes. Alphanumeric characters and the following special characters are allowed: Example: Dev-10 Default value: No default value. 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:
Note |
| |||||||
| 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 | Lists the email addresses for notification if one of the Snaplex nodes does not respond for fifteen minutes. Example: testuser@snaplogic.com Default value: No default value. | ||||||||
| Slack Channel for notifications | Enter the Slack channels, separated by commas, for notification if one of the Snaplex nodes does not respond for fifteen minutes. Example: dev Default value: None | ||||||||
| Slack user for notifications | Enter the Slack recipients, separated by commas, for notification if one of the Snaplex nodes does not respond for fifteen minutes. Example: testuser Default value: None | ||||||||
| Load balancer | The URL of the load balancer for Triggered Task execution requests. Default value: No default value. Example: https://snaplexlb.mydomain.com | ||||||||
Ultra load balancer | The URL of the FeedMaster load balancer for Ultra Pipeline execution requests.
Default value: No default value. 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.
If you use the slpropz file as your Snaplex configuration, then:
- After a Snaplex node is started with the slpropz configuration, subsequent configuration updates are applied automatically.
- Changing the Snaplex properties in Manager causes each Snaplex node to download the updated slpropz and do a rolling restart with no downtime on Snaplex instances with more than one node.
- Some configuration changes, such as an update to the logging properties do not require a restart and are applied immediately.
- Some configuration properties like the Environment cannot be changed without doing manual updates for the slpropz files on the Snaplex nodes.
Older Installations
If you have an older Snaplex installation and its configuration is defined in the global.properties file, then the Environment value must match the jcc.environment value In the JCC global.properties file. To migrate your Snaplex configuration to the slpropz mechanism, see Migrating Older Snaplex Nodes.
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.
For Snaplexes that have feedmasters, the load balancer should point to the feedmaster nodes. The "Ultra load balancer" property should be updated to point to the load balancer URL. This will ensure that all tasks details will point to this load balancer. This includes ultra and triggered tasks.
For Snaplexes that do not have feedmasters, the load balancer should point to the JCC nodes. The "Load balancer" property should be updated to point to the JCC load balancer URL. The triggered tasks details page will point to this load balancer.
The load balancer is recommended to be configured with HTTPS enabled. If the load balancer URL is configured with HTTP instead of HTTPS, then the task details page will point to the load balancer for the HTTP URLs only. The HTTPS URLs will point to the snaplex nodes rather than pointing to the load balancer.
Check Groundplex Requirements#LoadBalancerGuidelines for more details about the load balancer configuration guidelines.
Logging Settings
Use the Create Snaplex > Logging Settings popup to configure logs associated with the Snaplex that you want to create.
...
| 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. |
...