Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.

Note

We recommend you use a descriptive name for your Snaplex, so that you can identify it easily.

Default value: No default value.

Location

Specify whether the Snaplex must be created in the cloud or on premises. Select from the following options:

  • Cloud: Indicates that you want to create the Snaplex in the cloud.
  • Sidekick: Indicates that you want to create a Groundplex (on premises.)

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.

Note

The environment value cannot be changed if there are nodes running in the Snaplex. The Snaplex nodes have to be stopped first before the environment value is changed. The config file has to be downloaded to each node and the nodes restarted for the environment value change to take effect.


Version

Specify the version of the SnapLogic Platform on which you want the Snaplex to run.

Note

By default, all new Snaplexes are configured to work with the latest version of the SnapLogic platform. To update your Snaplex version, click Version and, from the drop-down list displayed, select the SnapLogic Platform version (such as mrc216) that you want to use with the Snaplex. Once you save the Snaplex, a rolling restart of the nodes in the Snaplex is initiated. One by one, each node in the Snaplex is put offline, and no new pipelines are sent to the node. The node waits for a maximum of 15 minutes for currently running pipelines to finish. It then restarts itself with the specified version of the Snaplex binaries. Once these restarts are done, the Dashboard shows the updated nodes to be running with the specified version.

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.

Note

This property is available only to Orgs that have subscribed to Ultra Pipeline Tasks.

Default value: No default value.

Example: https://ultralb.mydomain.com

Snaplex Configuration changes

...

For Snaplexes that do not have feedmasters, the load balancer should point to the JCC nodes. The "Load 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.

...

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.

Note

Changes made to this setting do not require a restart.

Default value: 15

Maximum memory %

The memory threshold at–and above–which no more Pipelines can be assigned to a node.

Note

Changes made to this setting do not require a restart.

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:

  • Localhost only (127.0.0.1)
  • Any interface (0.0.0.0)

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.

...