Running an On-premise Pipeline from a URL
The On-premises Snaplex URL refers to the Groundplex machine from which you send the request. Although the URL options are not tied to Snaplex type, these URLs depend on the user's ability to access those networks. For example, the Cloud URL is available to use from any computer with Internet access, whereas the On-premises and Override Alternative URLs require network access to the Groundplex or to a load balancer.
...
When a Triggered Task is invoked through an On-premise Snaplex or Override Alternative URL, the Task is cached for subsequent executions. The cached Tasks are then used on subsequent triggers of the URL, reducing task Task execution latency. Triggered tasks Tasks expire from the cache after an hour.
...
A Triggered Task can run on any of the Groundplex nodes. Because of internal load-balancing between Snaplex nodes for Triggered Tasks, the node in the multi-node Snaplex designated in the On-premise Snaplex URLs might not be the node that executes the Pipeline associated with that Task. Therefore, you need to configure the Groundplex nodes to accept requests from the other nodes so that data can be streamed back to the client.
You can also determine if Snaplex nodes are not communicating by clicking Dashboard > Health, selecting the Snaplex, and viewing the Alerts for each node. If there are communication issues, an alert such as Neighbor connectivity alert might appear.
Configure Triggered Tasks for High Availability with
...
Alternative URLs
Two additional configurable URLs (Local override URL and Local override Secure Secure Alternative URL and Unsecured Alternative URL) appear on the Task Details page. The Override Alternative URLs differ from the On-premises Snaplex URLs in that you can use them to trigger a task Task to run on any Snaplex node, whereas the On-premises Snaplex URL always runs on the Snaplex node that was specified when the Task was created.
If a Triggered Task is assigned to Snaplex A, then it always runs on that Snaplex if triggered with the On-premise Snaplex URL. Therefore, even if triggered on a node on Snaplex B, the Task still runs on Snaplex A. However, if the Override Alternative URL is used, then the Task runs on Snaplex A if triggered on Snaplex A and Snaplex B if triggered on Snaplex B.
For example, if a Task is configured to run on Snaplex A, then it can be forced to run on Snaplex B by substituting the hostname and port of a JCC node or FeedMaster in Snaplex B, in place of the one configured in the Override Alternative URL.
The Override Alternative URL was introduced for users interested in setting up their Tasks to run in High Availability configurations. The Override Alternative URL triggers a Pipeline to run on any Snaplex, regardless of what is defined in the Task. Unlike the On-premises Snaplex URL, which always runs on the Snaplex defined in the Task, you are responsible for defining a High Availability architecture, and it is commonly done using a load balancer or the network's DNS.
...
On the same screen, you can review task Task status to determine if you need to run a Triggered Task on another Snaplex. Furthermore, clicking on the task Task detail displays a window with Pipeline statistics, parameters, and information such as path, node, and the user who ran the Pipeline.
...