Page Comparison

...

Enterprise job schedulers that execute long-running Triggered Task Pipelines can report timeout or lost client connection errors. To help solve this issue, we provide the snaplogic_exec.sh script. It can execute on a any server that has network access to call the Triggered Task URL.

...

• A user or service account with Read & Execute read and execute access for the project that contains the Triggered Task.

• The URL for the Triggered Task, including any Pipeline parameters and their values.

• Read and execute permissions on the node(s) that will run the Triggered Task.

• For use on Windows nodesservers, a Cygwin shell with curl.

Workflow

...

Install the script on any server where the Scheduler has access to run the script, it and configure it with your SnapLogic credentials:

1. Download snaplogic_exec.zip.

2. Extract the compressed file and save the snaplogic_exec.sh script to the appropriate location.
   For example, use /usr/local/bin on Linux machines and %systemroot%\System32\Repl\Imports\Scripts on Windows.

3. From the directory containing the script, invoke snaplogic_exec.sh --config in a terminal window. For example, on Windows:
   

   

4. Enter your the SnapLogic user name and password.

...

1. In Snaplogic Designer, open the Pipeline that you want the script to execute.

2. Add a Mapper Snap to the canvas.

3. In the Settings tab, enter Map snaplogic_exec.sh return in the Label field.

4. In the Mapping table, add the Expression,pipe.ruuid with the Target path ruuid:
   

   

5. Select the Views tab.

6. Click - (minus) to remove the input view.

7. Leave the default output view, output0, as is, with Type document:
   

   

8. Save and close the Mapper Snap.

9. The Pipeline should look similar to the following (before validation):

   

...

Using the snaplogic_exec.sh script should enable you to execute long-running Triggered Tasks with from an enterprise scheduler without encountering causing timeout or lost connection errors.

...