Snaplogic Triggered Task using an OnPremises URL through Load Balanced Groundplex Nodes
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. e.g., https://GP-Node1:<port>/api/1/rest/feed/<RELATIVE_PATH_TO_TASK>/ 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. e.g., https://GP-LB:<PORT>/api/1/rest/feed/<RELATIVE_PATH_TO_TASK>/ 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.
Semantic URL Example
Hi, I would like to know how to correctly pass data via Semantic URL (as a Triggered Task via URL)? Here is what I did: Edit Pipeline Properties: I created an exampleId variable, if I wanted to pass a value of 1 to the exampleId variable: https://elastic.snaplogic.com:443/api/1/rest/path/to/my/project/pipelineName/exampleId/1 What I have working is: https://elastic.snaplogic.com:443/api/1/rest/path/to/my/project/pipelineName/?exampleId=1Triggered task - don't wait for API response
I have a pipeline that is acting as a “driver” pipeline to kick off other pipelines. I would like to kick off the children pipelines using a triggered task and a REST API call in the parent pipeline. I can get this to work, but I’m noticing that the REST API snap in the parent pipeline is waiting for the child pipeline to finish before moving on. I don’t want want it to wait. I just want it to make the REST API call and move on. How can I accomplish this?