Overview

To ensure maximum up-time for enterprise-level deployments, Dispatcher Phoenix offers important features for the enterprise, including:

  • Failover - A failover server that is used if the primary server goes down ensures maximum up-time. When a failure occurs on one server in a cluster, resources are redirected and the workflow is redistributed to another server in the cluster, which has been licensed as a failover server. All failover servers can function as a primary for 30 days, after which the failover acting as primary will stop functioning (if a licensed primary server is unavailable). If a primary server becomes permanently offline and the failover server needs to become the permanent primary server, a manual license transfer is necessary to move the primary license to the failover server.

  • Load balancing - For a large deployment of devices, load balancing is optimal for distributing requests to servers. With Dispatcher Phoenix, multiple primaries can be joined together for automatic load balancing in which case jobs move from one primary to another based on backload and a user-specified threshold.

  • OCR offloading - To speed processing time, intensive processing tasks can be offloaded to other servers. Dispatcher Phoenix can be set up to offload MFP Connectivity, Mobile Connectivity, Web Connectivity, and Workflow Processing.

  • Workflow Sharing - With the fine-grain sharing control feature, specific users or groups of users can be assigned workflows.

  • Workflow Control - Admins can run, stop, and pause workflows without needing Dispatcher Phoenix installed on your system.

  • Dashboard - Graphical online Dashboard provides quick snapshot on server/user activity.

These features are available via the Dispatcher Phoenix Web application.

Glossary of Terms

CLUSTER - A group of two or more replicated servers (also known as “nodes”) that are deployed to increase the availability, reliability, and/or performance of the group over that provided by a single server. Once joined together in a cluster, the nodes remain in constant communication.

  • Failover Clusters - A cluster designed to provide failover services (if a failure occurs on the primary member of the cluster, the primary server’s resources will automatically restart on another server that is also a member of the cluster).

  • Load balancing Clusters - A cluster designed to distribute the workload to several servers that form the cluster (also known as a server “farm”).

FAILOVER - The process of moving resources from one node to another in the case of failure. Using an Active/Passive configuration, a passive node remains in standby mode, waiting for the active node to fail. If the primary node becomes unavailable because of failure or maintenance, the passive node immediately takes control of the cluster resources and services.

HEARTBEAT - A network “packet” sent between nodes in the cluster to confirm that they are still online.

LOAD BALANCING - Distributes the processing and traffic evenly across all servers in a cluster.

NODE - A server that is part of a cluster.

  • Active Node - The cluster server that currently owns cluster group resources and responds to network requests made to those services.
  • Passive Node - The cluster server that does not currently own cluster group resources but is available if the active node fails over.

Requirements

DP Web is supported on all HTML5 supported browsers, including:

  • Chrome

  • Firefox

  • Internet Explorer 10+

  • Microsoft Edge

  • Safari for Mac

On this Page: