The Advanced Configuration section covers server-level settings and architecture options that go beyond the day-to-day web-console configuration. These topics are intended for system administrators who need to change ports, publish driverless print endpoints, deploy print nodes at remote sites, or design a highly-available multi-server cluster.
In This Section
|
Page |
Description |
|---|---|
|
Change the IIS binding so the OptimiDoc web console and API listen on a non-default port, and update everything (device agents, printing nodes, OAuth callbacks) that refers back to the server. |
|
|
Install a driverless IPP/IPPS printer on Windows, macOS, Linux and ChromeOS clients so users can submit jobs to OptimiDoc using the operating system's built-in IPP support — no vendor driver required. |
|
|
Deploy an OptimiDoc Printing Node (OPN) — a lightweight, database-free print service installed near your printers that receives LPD/IPP jobs locally and hands them to the central server. |
|
|
Reference for OptimiDoc high availability: multiple active server nodes on one shared database, the master role, configuration convergence, shared spooler, and how failover works. |
When to Use Advanced Configuration
Most OptimiDoc deployments run well on the default settings. Reach for these topics when:
-
The default HTTPS port (443) conflicts with another application on the server.
-
You need driverless printing from a mixed-OS or BYOD estate (IPP).
-
Remote sites would benefit from a local print entry point rather than sending jobs across the WAN (a printing node).
-
Your organisation requires high availability or load balancing across multiple OptimiDoc server nodes.
A Note on the Two Kinds of Node
Two of the pages here involve "nodes", and they are not the same thing:
-
A printing node is a small standalone service that provides a local LPD/IPP entry point and forwards jobs to the central server. It does not host the console or touch the database. See Print Nodes Configuration.
-
A server node is a full OptimiDoc installation that shares the database and participates in the highly-available cluster. See Failover Architecture.
Both are listed together under Diagnostics > Cluster Nodes, distinguished by their type (PrintingNode or Server).