When considering the compatibility of iPrint with respect to a specific printer, the overall goal is to ensure that:
The following guidelines reflect these overall goals.
iPrint Guideline #1Administration
The printer can be created, configured, and managed using iManager and commandline iPrint management tools. This implies that:
- The printer driver(s) can be uploaded to the iPrint Driver Store (for OES Linux).
- The printer driver(s) can be uploaded to the iPrint Broker (for OES NetWare).
- The printer can be added to the iPrint framework and made available for client installation via the server's iPrint web page.
- The appropriate driver can be assigned to the printer.
- The printer's status (including all supported printer functions) are correctly reflected by the iManager printer management and status pages.
iPrint Guideline #2Usability
Once the printer has been properly configured for use with iPrint, endusers can install the printer (and associated driver) and print to the printer using the iPrint interface. This implies that:
- The printer can be installed on any supported client by accessing the server's iPrint web page.
- The printer correctly prints bitmap and PDF files submitted from the client platform(s).
- The printer correctly prints files from wordprocessing applications on the client platform(s).
- The printer's status is correctly and completely reflected by the iPrint Client on the client platform.
iPrint Guideline #3Bidirectional capabilities
For bidirectional capable printers (on Windows), it will be necessary to validate that the communications take place between the client and the device by ensuring that the device settings, properties, and defaults show appropriately to the enduser in the printer folder and associated property pages. Typically this communication reflects device configuration information like trays, memory, disk, and other 'installed/configured' items of the printer into the printer folder.
If you find in your testing that iPrint installed printers have issues with properly displaying this information, it may be necessary to enhance the printer driver to support this ability with the iPrint client (as many vendors have already done). This change is minimal in nature and typically requires that the driver obtain the physical address of the printer from a registry location that has been set by the iPrint client. The following should be considered:
- The installed printer communicates via SNMP or other protocol with the physical printer.
- The installed printer shows property pages and device settings as obtained from the physical device.
- The installed printer correctly honors those settings when submitting a print job.
Note: Printer vendors bear the ultimate responsibility for ensuring that their devices are compatible with iPrint. This is because vendors have the full suite of devices and drivers with which to test their product with iPrint. Novell allows participation in the Novell OES Ready program based on vendors' assurances that they have tested their products in iPrint environments using their own tests or the suggested test procedures in Appendix A. The Novell OES Ready printer vendor and Novell will take all reasonable steps to address any compatibility issues.