Page Comparison

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.

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 does 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 does not require a restart and are applied immediately.

Info

title	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.

Note
You should always configure your Snaplex instances using the slpropz file because you do not have to edit the slpropz files manually and changes to the Snaplex done through Manager are applied automatically to all nodes in that Snaplex, making configuration issues, which may prevent the Snaplex from starting, automatically reverted.

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.

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.

...

Versions Compared

Old Version 27

New Version 28

Key