In this Page
| Table of Contents | ||||
|---|---|---|---|---|
|
...
| Snaplex Type | Indicates if it is a standard Snaplex. | |||||||
|---|---|---|---|---|---|---|---|---|
| Name | The name of your Snaplex. Rename your Snaplex to provide a better description of the type or location. The name must not exceed 100 characters.
| |||||||
| Location | Indicates whether the Snaplex is in the cloud or on the ground. | |||||||
| 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:
| |||||||
| Version | The version of the Snaplex. Update the version of your Snaplex by setting the Version in Manager. This manual update initiates a rolling restart of the nodes in the Snaplex. Each node is put offline with no new pipelines being sent to the node. The node waits a maximum of 15 minutes for currently running pipelines to finish and then restart itself with the new version of the Snaplex binaries. This process is repeated for each node. The Dashboard shows the updated nodes to be running with the new version. Consider the following three designations when selecting the Snaplex version:
| |||||||
Minimum node per Snaplex | This option makes sure that the application master keeps a certain number of nodes alive even when there is no activity in the Snaplex (useful for Pipeline validation through Designer). Minimum number is 1. | |||||||
| Email address for notifications | Enter the email addresses for notification if one of the Snaplex nodes does not respond for fifteen minutes. | |||||||
| 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 Channel 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 for the load balancer for Triggered Task execution requests. | |||||||
Ultra load balancer | The URL for the FeedMaster load balancer for Ultra Pipeline execution requests. This is available only to those Orgs subscribed to Ultra Pipeline Tasks. |
...
| Level | The logging level that log messages must meet to be captured in the main log file. Select one of the following options:
| |||||
|---|---|---|---|---|---|---|
| Log file size | The maximum log file size, given as a number with a unit. For example, 300 50 MB for 50 megabytes. | |||||
| Main backup count | The number of backup log files to keep for the main log (jcc.json). | |||||
| Error backup count | The number of backup log files to keep for the error log (jcc_error.json). | |||||
| Access backup count | The number of backup log files to keep for the access log (jcc_access.json). |
...
| Maximum slots | The maximum number of slots available on each node in a Snaplex. Each Snap in a Pipeline will consume a slot, so Pipelines will only be executed on nodes where the number of slots currently in use is below this threshold. Otherwise, they will fail or be placed in the Queued state, 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 on the Monitoring Snaplex Health dashboard. A restart is not required with a change to this setting, which can be set to a user-specified value. Default value: 4000 | ||||||
|---|---|---|---|---|---|---|---|
| Reserved slots % | The percentage of slots to reserve on a node for pipelines executed through the Designer tab. A restart is not required with a change to this setting. Default value: 15
| ||||||
| Maximum memory % | The threshold at which no more pipelines will be assigned to a node. A restart is not required with a change to this setting. 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.Choose where the Snaplex node will accept HTTP network connections from. Options include:
| ||||||
| HTTP port | Groundplex only.The HTTP port the Snaplex node will listen on for connections. Default Values: 8090 for a JCC node and 8091 for a FeedMaster. | ||||||
| HTTPS port | Groundplex only.The HTTPS port the Snaplex node will listen 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. Enter the maximum wait time before restarting a node or click Forever for an infinite wait time. Default: 15 minutes Recommended. No greater than 60 minutes.
| ||||||
| Snaplex node types: Hostname/Server type pairs | Groundplex only.Specify the type of service a Snaplex node should provide. Applicable in Ultra-enabled environments. | ||||||
Global properties: | Groundplex only.Internal configuration options. Do not edit these values without contacting SnapLogic Customer Support. |
...