Dispatcher Phoenix is Konica Minolta’s solution for helping businesses save time by automating document image processing, printing, and routing tasks via customisable workflows. It provides busy offices with the convenience and flexibility they need helping increase productivity.
Load balancing Dispatcher Phoenix ensures the application is always available when needed with stable, optimal performance. The ability to isolate servers also reduces risk when performing inevitable upgrades and maintenance tasks – without interrupting end users.
Loadbalancer.org specializes in providing application delivery controllers (ADC) and load balancing solutions to the Print & Workflow Management sector. In addition to load balancing Phoenix, Loadbalancer.org also provides solutions for Konica Minolta’s Dispatcher Paragon product, see the Application page for further details.
The following diagram illustrates how the load balancer is deployed with multiple Dispatcher Phoenix servers.
For a Dispatcher Phoenix deployment, the preferred and default load balancer configuration uses Layer 4 DR Mode (Direct Routing, aka DSR / Direct Server Return). This is a very high performance solution that requires little change to your existing infrastructure. It is necessary to solve “the ARP problem” on the real print servers. This is a straightforward process, and is detailed in our deployment guide, below.
It is also possible to load balance a Dispatcher Phoenix deployment using Layer 7 SNAT Mode. This mode might be preferable if making changes to the real print servers is not possible, although some Windows Registry keys need to be added. Due to the increased amount of information at layer 7, performance is not as fast as at layer 4. Also note that load balanced connections at layer 7 are not source IP transparent, which is not usually an issue when load balancing print servers but should still be considered.