On this Page
Ultra Pipeline Tasks require consideration and preparation of your network depending on the purpose of the Ultra Pipeline. The following deployment architectures cover the most common scenarios for setting up your environment to run Pipelines in Ultra mode.
One component present in most configurations is the FeedMaster, which brokers the queues between the execution nodes and Clients. The FeedMaster receives HTTP requests and turns them into documents and sends them to nodes for processing. The response from the node sends it to the FeedMaster, which in turn returns it as a response to incoming requests.
Headless Ultra Pipelines do not require a FeedMaster, so setting up this Snaplex is simpler than other configurations.
Use this configuration if you already have a data source that provides a listener-type of interfaces, such as JMS or file poller.
The following are the Listener Snaps that can be used in the headless Ultra pipelines:
|
This configuration allows customers to build a low latency REST interface for communicating with any type of endpoint. It provides low latency and reliability as compared to a Triggered Task, which is dependent on the control plane.
The FeedMaster uses the following ports:
The machine hosting the FeedMaster must have those ports available on the local firewall. |
The following diagram provides an overview of the standard network architecture required for Ultra Pipeline, including the communication between the various components with a focus on the network ports.
The following diagram provides an overview of the Disaster Recovery architecture for Ultra Pipelines.
Configuration on DNS Server
Deployment of Tasks
Configuration Guidelines for a Load Balancer