Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Minor edits

...

  • One unconnected input view and one or more unconnected output views: A FeedMaster must also be in the Snaplex for this to work. This is different from triggered tasks Triggered Tasks (one input and one output).
  • No unconnected views: A FeedMaster is not required to be in the Snaplex in this case. This scenario is expected to be used if the data source is a Snap like along the lines of a JMS Consumer.

Low-latency Feed (Request and Response) 

...

Guidelines for Ultra Pipeline Designs

Ultra Pipelines tools are similar to web service requests and conform to an HTTP response architecture. Consider these guidelines when designing you design an Ultra PipelinesPipeline.

Input View Type

An unconnected input view type must be either binary or document:

  • If binary, the HTTP headers are in the binary document's header.
  • If a document, the headers from the original HTTP request are in the root of the document, and the body of the request is in the content field.
    For example, you can reference the the User-Agent HTTP header in the input document as $['user-agent'].

...

  • If the view type is a document: 
    • The output document is JSON-encoded and sent back to the client as the response body.
    • To customize the response header and HTTP response code:
      • Map the response body to the $content field of the output.
      • Map the custom header fields to the root($) in the output.
      • Map the custom HTTP response code to the $status field of the output.
    • The other fields in the output document are treated as HTTP response headers to send back to the client.
    • If a content field is not present, the entire document is JSON-encoded and used as the response body to be sent back to the client.
  • If the view type is binary data, the binary file's header is sent back to the client as HTTP response headers. The body of the binary file is directly streamed back to the client.
  • SnapLogic expects exactly one output document for every input.
  • If the output is not sent, then the original HTTP request sent to the FeedMaster hangs, eventually reaching a timeout.
  • If more than one output document is generated, then SnapLogic only sends the first one back as the response to the original HTTP request. This behavior is different from a Triggered Task, where all of the documents sent to the unlinked output are sent back in the response.
  • Error views are implicitly added to all Snaps when the Pipeline is executed in Ultra mode, regardless of how the Snaps are configured.

...