Page Comparison

You can configure which Snaplex a Pipeline, Task, API/Proxy will use in one of the following ways:

• With a Pipeline open in Designer, you can select from the Snaplex drop-down menu a Snaplex instance on which the Pipeline should run.

• When you configure a Scheduled or Triggered Task, you can select the Snaplex to run the Pipeline.

• When using the Pipeline Execute Snap,

  • The Pipeline Execute Snap has a Snaplex

   property

  •  field that specifies

  where

  • the child

  Pipeline is executed. When using a Pipeline Execute Snap, if you

  • Pipeline’s Snaplex. leave the

  property blank or use

  • field blank.

  • As an alternative, use the pipe.plexPath expression

  ,

  • to ensure that the child Pipeline

  is executed

  • runs on the same node as the parent.

  When running a parent and child Pipeline on the same node, data is not transferred over a network, which improves the performance of the Pipeline execution.
  When using the Pipeline Execute Snap,

  • if you specify a different Snaplex to run a child Pipeline, then the input documents and Pipeline parameters are passed

  (

  • through the

  control plane

  • Control Plane using encrypted transport

  )

  • to a node in the designated Snaplex.

• To set a dedicated Snaplex for a project, an Org admin can move a Snaplex from the Shared project to any other project. Only In Manager and Designer, only those Pipelines within the new project have access to that Snaplex. However, regardless of the Project containing the Snaplex, you can still run Pipelines on it as long as you have access.

• The parameter runtime_path_id allows users to specify the Snaplex for OAuth2 operations in the Snap. This availability ensures that the refresh token is sent to the nodes in the given Snaplex.