Pipelining Integration Guide (On Prem)

Last Updated: Dec 17, 2014 01:32PM PST

Summary: on-prem This article explains how to set initial data from other applications and save service pipelines for use with Pipette Analysis.

Covered Topics

Clicking a link will scroll the page to the relevant section.

Developing Services and Outputs

The methods for developing services and outputs are fully covered in the Pipette Analysis Service Development Guide.

Setting Initial Data from Other Applications

To set an initial data store containing data from another application, pass the name of a user scoped Pipeline Pilot cache on the URL with an initialdataid parameter:


You can give this initial data store a name with an initialdataname parameter:


To automatically clean up the cache after 24 hours, start the cache name with "pipettetmp", ideally combined with a GUID. See the PilotScript function CreateGUID(). To simplify saving these caches, a Pipette Cache Writer component is provided.


Saving Pipelines

As you build services pipelines, these services and their settings will get serialized to the URL. This means you can bookmark the current URL to return to the pipeline.

Only service settings that are modified from their defaults are stored in the URL.

If the amount of data exceeds that which can be stored in the URL, no service details will be appended to the URL and an incomplete pipeline serialization will not be saved.

This serialized URL string is LZW-compressed, then base-64 and URL-encoded.

Templated services pipelines can be saved through the user interface. These are not subject to the URL length restriction described above.

Shared templates can only be edited by users with the Pipette Analysis/EditSharedTemplate permission. These templates are accessed via the Add Service dialog.


Pipette Analysis Service Development Guide

seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found