This article describes how a triggered task is invoked in the SnapLogic Elastic Integration
Platform using an OnPremise URL through load balanced Groundplex nodes.
Assume that your organization has a SnapLogic Groundplex provisioned with 3 nodes. When an OnPremise URL is exposed for a triggered task, it will automatically suggest the hostname of one of the nodes that belongs to the Groundplex.
To provide redundancy across all nodes in the Groundplex when a triggered task is invoked, a load balancer can be placed in front of the Groundplex nodes. When a load balancer is setup and configured, Snaplogic will use the load balancer in the auto-generated OnPremise URL.
The following diagram describes the flow of network requests made when remotely executing a triggered task using a load balancer OnPremise URL.
- A remote client invokes the triggered task using the OnPremise URL that points to the load balancer (e.g., GP-LB).
- The load balancer forwards the request to an active groundplex node. GP-Node1 is selected for the purpose of this example.
- The groundplex node that receives the triggered task request asks the Control Plane on which node the task should be executed.
- The Control Plane forwards the request to an active groundplex node. GP-Node2 is selected for the purpose of this example.
- The triggered task now prepares to be executed on GP-Node2. An HTTPS connection is created between GPNode-1 and GP-Node2 to enable data to be streamed between the nodes.
- The data is read/write from/to the end points.
- The response message is sent though GP-Node1 then GP-LB (load balancer) back to the caller.