Queues are print-in channels for acquiring SafePages.
After a tap on the button in the main menu this panel is shown. See Section 4.2, “Menu”.
All non-deleted queues are listed alphabetically by default. A different selection and sorting can be entered: see Figure 4.50, “Admin Web App: Queue - Select and Sort”.
Press the edit a new queue.button to create and
The list can be traversed by tapping one of the buttons at the pager at the top or bottom of the page.
An entry is displayed for each queue, with identifying data and some usage statistics. From top to bottom:
The queue's trust or status (at the top right corner).
The URL Path of the queue. The path is relative to the /printers URL base.
An inline Line-Graph showing the day pagometers of the printed pages over the last 30 days.
The full IPPS URL variant of the queue.
SavaPage takes the first IPv4 address
of the first network interface on the server
platform as URL host. You can overrule this
behavior by setting a fixed IPv4 address or DNS
name in configuration item
Optionally, the allowed client IPv4 and/or IPv6 addresses as a CIDR Set.
The period in which activity was accumulated on the pagometer.
The pagometer of the queue including the number of jobs and bytes printed.
Tap the Section 4.7.2, “Edit Queue”button to change or delete the queue. See
Due to Admin Privileges certain buttons might not be visible.
Queues can be selected by entering the containing text (fragment) of their URL Path Name.
Select the queue's Trust and (Deleted) Status. The button will select both option values.
The list can be sortedor on URL Path Name.
Tap the button to (re)display the list.
A tap on the button resets the selection and sort fields to their default values.
The URL Path is editable for non-reserved queues. Renaming the URL path name will permanently overwrite the old name in all related job history records with the new name.
In response to an IPP Get-Printer-Attributes request the “printer-name” is returned as “SavaPage-urlpath”. So, in this example the IPP printer-name will be “SavaPage-public”.
Enter IPv4 and/or IPv6 address ranges as a CIDR Set at IP addresses allowed to restrict access to the queue based on requesting IP address. If the field is empty all requesting IP addresses from private networks are allowed to print to the queue. See Section 11.5.2, “HTTP XFF Header Settings”.
Tick thecheckbox to disable access to the queue for all users.
Tick the Section 4.11.12, “Backups”.checkbox to delete the Queue. This will be a logical delete as long as related job history is present. Any logical deleted Queue will be physically deleted from the database when no related job history is present anymore. This situation will automatically occur when you enabled automatic backup in combination with the delete of old document logs. See
Press thebutton to commit the changes and return to the Queue List.
Thebutton brings you back to the Queue List without changing anything.
IPP printing from public IP addresses is denied by default. You can override this behavior by setting specific public IP address ranges at IP addresses allowed.
ipp.routing.enable configuration property is
enabled (see table below), the following section appears in the Edit Queue dialog:
Select the option to enable IPP Routing for this Queue, and optionally enter an IPP key/value map in
JSON format to override printer defaults. In this example
media-source is assigned value
IPP Routing Queues are marked with a small printer icon in the Queue List.
Enable IPP Routing:
Table 4.4. Configuration Properties for IPP Routing
See Section 4.11.14, “Config Editor” on how to set these items.
IPP Routing Plug-in instances are called on an IPP Routing event, just before the PDF is send to the Proxy Printer. These plug-ins edit the PDF, for example by adding a header, footer and QR code image.
Alice logs into a computer at the Reception.
The computer has fixed IP address 192.168.1.50
Alice prints the “Sales Report” document to
The PostScript content is received by SavaPage and converted to PDF.
SavaPage notices that ...
/tray1 is configured for IPP
The requester's IP address 192.168.1.50 is linked to Terminal “Reception”.
Terminal “Reception” defines a Custom Proxy Print to the Single Printer Target “HP-Reception”.
SavaPage decides to print the PDF to Proxy Printer “HP-Reception”.
SavaPage notices that an IPP Routing Plug-in instance is present. Therefore, it calls the plug-in with the print job parameters (User id "Alice", Client IP address 192.168.1.50, CUPS printer name “HP-Reception”, Print Job Name “Sales Report”, date/time of the print) together with the PDF to be printed.
The IPP Routing Plug-in calls a RESTful service of a third-party QR code provider, passes the print job parameters, obtains the QR code in return, and draws an image of the QR-code on the PDF to be printed.
SavaPage prints the PDF as edited by the IPP Routing
Plug-in to Proxy Printer “HP-Reception” using the
IPP Routing Options of
Alice collects the printed “Sales Report” document from the “HP-Reception” printer next to her desk.
Dedicated queues are reserved and pre-installed for: