CUPS DSS
If your input data formats (for example, PostScript, PDF, and PCL) are the same as the formats accepted by your printer (you neither need nor desire that data to be transformed), then driving your printer with a CUPS DSS is a good choice. An InfoPrint Manager CUPS DSS can drive any printer that a CUPS printer can drive by using the CUPS-provided backends: ipp, ipps, lpd, socket, etc. By using one of the InfoPrint Manager enhanced CUPS backends (pioinfo or piorpdm for Ricoh printers), the CUPS DSS also supports accurate job completion and job accounting. Before using one of these backends, you must install the driver files for your printer.
The hardest part of creating a CUPS DSS is figuring out what the destination-command should be. So if you want to use the InfoPrint Manager enhanced CUPS backend (pioinfo or piorpdm) to obtain accurate job completion and job accounting information, you just need to know the port number to use for your printer.
The CUPS DSS destination command for the InfoPrint Manager enhanced backends can be one of these:
pioinfo://ip-address:[port-number] piorpdm://ip-address:[port-number]
where ip-address is the IP address of the printer you want to use and port is the TCP/IP port that printer uses for both PCL and PostScript print jobs. If the
port is not specified, it defaults to 9100 for pioinfo. On HP, InfoPrint, and Ricoh printers, the port is most often 9100.
If your printer driver supports printing PDF, select the PDF value in the Formats allowed list to print PDF documents on your actual destination representing that printer.
If your printer supports printing PDF natively and you want to send the data directly to the printer without any CUPS processing or filtering then your destination command should use the raw option:
pioinfo://ip-address[:port-number] raw piorpdm://ip-address[:port-number] raw
By using one of the CUPS backends the CUPS DSS provides the same support as the CUPS printing system, such as encryption and other security features over the Internet Printing protocol (IPP). Refer to the CUPS documentation for more details about CUPS, the CUPS backends, and the CUPS implementation of IPP.
The CUPS DSS destination command for the CUPS backends can be one of these:
ipps://ip-address:443/ipp/print socket://ip-address lpd://ip-address/queue