Deploy tasks from on-premises networks

The Tasks Details page displays all available URLs to trigger a pipeline execution. In addition to a Cloud URL, two sets of Secured (HTTPS) and Unsecured (HTTP) URLs are available for triggering the pipeline to run on an on-premises network:
  • Snaplex
  • Alternate
The Alternate URL refers to the Groundplex machine (a self-managed Snaplex) to which you send the request.

Although the URL options are not tied to Snaplex type, these URLs depend on the ability to access those networks. For example, the Cloud URL is available to use from any computer with internet access. When used, the API call is processed through the SnapLogic control plan.

Calling a Task with a Groundplex node.

The Snaplex and Alternative URLs require network access to the Groundplex or to a load balancer. By default, the Groundplex machine only accepts HTTP requests from the Loopback interface (127.0.0.1). To allow access from other machines, you must change the HTTP interface of the Groundplex configuration to listen on any IP address (0.0.0.0). This may also require additional network changes, such as opening up a firewall, so consult your network administrator for guidance.

Two Secure Snaplex URLs and Unsecured Snaplex URLs on the Task Details page offer flexibility. The Alternate URL always runs on the Snaplex node defined in the Task, which you can see in the endpoint path. The segment begins with the hostname or port.

The Snaplex URL was introduced for users interested in setting up their Tasks to run in high availability configurations. The Snaplex URLs differ from the Alternate URLs in that you can use them to trigger a task to run on any Groundplex node, using a load balancer or the network's DNS to specify which node to run the task.

When a Triggered Task is invoked through a Snaplex or Alternative URL, the task is cached for subsequent executions. The cached tasks are then used on subsequent triggers of the URL, reducing execution latency. Triggered Tasks expire from the cache after 4 days (96 hours).

Additional setup for multiple Groundplex nodes

A Triggered Task can run on any of the nodes in your Groundplex. Because of internal load-balancing between nodes for Triggered Tasks, the node designated in the Snaplex URLs might not be the node that executes the pipeline associated with that Task. Configure the Snaplex nodes to accept requests from the other nodes so that data can be streamed back to the client.

You can also determine if Groundplex nodes are not communicating by clicking Dashboard > Health , selecting the Snaplex, and viewing the Alerts for each node. If communication issues exist, an alert such as Neighbor connectivity alert might appear.

High availability example with Snaplex URLs

The Snaplex URL triggers a pipeline to run on any Snaplex node. You can force it to run on Node B by substituting the hostname and port of a JCC node or FeedMaster. This should be done in place of the one configured in the Snaplex URL - note the /run/task/ segment included in the endpoint path.

For example, using Node A and Node B as designators, a Triggered Task assigned to Node A can run on Node B when triggered with the Snaplex URL using the your load balancer's URL in place of the FeedMaster Node B.