SnapLogic Best Practices:Tips and Tricks in 30 Minutes

Praneal NarayanJason Slater

2

Agenda

Today’s Topic: Event Driven Pipelines

Pipeline Parameters

Pipeline End Patterns

Creating a Triggered Pipeline via Tasks

Triggering a Pipeline

When Would I…?

Gotcha’s

Testing  

3

Before We Get Started…..

Documentation

Download the following:– Snaplex

– JSDK

– Snap Packs

– Mac, Linux and Windows Installers

Community Board and Ideas

Don’t forget to use our Developer Community

http://developer.snaplogic.com

4

Pipeline Parameters

Parameters– Default is no parameters

– Add them under pipeline properties

Parameters are strings

Default value is also useful for testing

5

Some Typical Pipeline End Patterns

End open to produce data

Beginning open to consume data

– Control data types

– (binary, xml, default is JSON)

Neither end open

6

Creating a Triggered Task for a Pipeline

Manager >> Project >> Tasks >> +– Select Pipeline (what)

– Select Snaplex (where)

– Select “Triggered”

– Specify default value(s) for parameters

Event-Driven REST endpoint(s) for a pipeline (URL)– Groundplex: proxied cloud + on-premise URL

– Cloudplex: cloud URL

7

Triggering a Pipeline

Triggered via REST GET/POST Basic Authentication

URL Parameters (tip: URL encode your parameters)

Default payload is JSON; binary, XML support as well

Single input or output view necessary

8

When Would I…?

Examples, i.e. “When would I…?” SFDC -> SAP, event-based pipeline; triggered from SFDC,

pipeline does the heavy lifting

Expose data from behind firewall (groundplex) and consume it in the cloud without opening hole in firewall

Modernize; SOAP/etc. - expose legacy services as modern RESTful endpoints

9

Gotchas and Testing

If pipeline parameters change, re-create the task

Use Manager/Tasks to test in your browser, or use a browser plugin like POSTMan to test

10

Connecting with the SnapLogic Team

@SnapLogic

Facebook/SnapLogic

developer.snaplogic.com

www.snaplogic.com/techtalk