Page Comparison

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.

If you rename a Snaplex, then you must perform the following actions:

• Do a rolling restart on all the nodes in the Snaplex.

• Update any Pipe Execute Snaps that reference the old Snaplex name with the new name.

Uneditable. Indicates how the Snaplex is managed:

• Managed by SnapLogic: cloud

• Self-managed: sidekick

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

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.

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:

• Recommended. Indicates that this distribution is the version you should use.

• Restricted Distribution. Indicates that this version has a configuration intended for specific customers only.

• Deprecated. Indicates that this version is being phased out and should not be selected.

When you choose not to update your Snaplex manually and wait for the Automatic Update instead, you receive notifications until the Snaplex upgrade occurs. You can configure  your Snaplexes within an Org to update automatically in Manager when a new version is available.

Enter the email addresses for notification if one of the Snaplex nodes does not respond for fifteen minutes.

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

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

The URL for the load balancer for Triggered Task execution requests. The load balancer URL has to be fully qualified, including the protocol. 
When you save the Load balancer URLs in the Snaplex settings, these details are used for Snaplex Trigger URL.

Example: https://snaplexlb.mydomain.com

The URL for the FeedMaster load balancer for Ultra Pipeline execution requests.

This is available only to those Orgs subscribed to Ultra Pipeline Tasks.
Example: https://ultralb.mydomain.com