1.2 iPrint Component Overview

OES iPrint consists of three main components: the Print Manager, the Driver Store, and the iPrint Client. Other supporting components include the Apache Web Server, iManager, and eDirectory.

Figure 1-1 OES iPrint Component Overview

1.2.1 Print Manager

The Print Manager, which is an object in the eDirectory tree as well as software that runs on an OES server, provides a platform for Printer Agents on the server. As print jobs are submitted to the Print Manager, the print job is forwarded to a printer when the printer is ready.

A single Print Manager can handle print jobs for multiple printers. Depending on your network configuration (for example, remote locations), you can create additional Print Managers on other servers, but only one Print Manager can exist on any one server. The Print Manager user access control allows authorized users to print.

Figure 1-2 Workflow through a Print Manager

Printer Agent: The Printer Agent is an entry in the Print Manager database that represents the physical printer. When you create a printer, a Printer Agent is created in the Print Manager’s database and a Printer object is added to eDirectory. The Printer Agent manages the processing of print jobs; answers queries from network clients about a print job or attributes of a printer; and provides SNMP information that is displayed in the Print Manager Health Monitor.

IPP server: The IPP server’s main function is to handle IPP requests from the Web server and deliver the requests to the Print Manager or to the Broker.

iPrint Gateway: The gateway maintains communication with the printers. When a printer is ready, the gateway requests print jobs from the Print Manager for the printer. The print jobs are sent to the printer through LPR and the TCP/IP protocol. The gateway also uses SNMP to query printers to get their status and other printer information.

1.2.2 Driver Store

The Driver Store is an eDirectory object. Only one Driver Store is required on a network; however, depending on your network configuration, you can create additional Driver Stores. The fewer Driver Stores that are running, the better. With more Driver Stores, you need to keep track of which drivers run on which driver store.

The Driver Store is a repository of printer drivers for your print system. When the first user of a printer installs the printer, the Print Manager requests the associated printer driver from the Driver Store, and the Print Manager saves the printer driver to disk for future use. When the same printer is installed by another user, the Print Manager checks to see if there is an updated printer driver in the Driver Store. If an updated driver exists, the Print Manager caches it and subsequent printer installations use the newer drivers. However, printers already installed on workstations with the older driver are not updated. For additional information on the Driver Store, see TID 3281477 on the OpenText Support Site.

1.2.3 iPrint Client

The iPrint Client is available on the following platforms:

Windows iPrint Client

The Windows iPrint Client lets you install iPrint printers and configure iPrint on your workstation. It includes the following components:

  • Print Provider: The iPrint Print Provider communicates directly with the Windows spooler, which takes print jobs from applications and delivers them to a print provider. Upon startup, the iPrint Client ensures that the iPrint Print Provider is the first one in the list of providers. When a print job is intended for an iPrint printer, the iPrint Print Provider delivers the print job to the Print Manager.

  • Browser plug-in: The iPrint Client contains a browser plug-in for Mozilla-based browsers and Internet Explorer. The IE plug-in is an OCX-based plug-in that lets you install printers through your IE browser.

  • Client configuration: Through the iPrint Client configuration screen, you can take advantage of several advanced client features. For more information on each of these features, see the associated documentation. These features include the following:

  • Command line utilities: The iPrint MS-DOS commands let you install iPrint printers without a web browser and capture LPT ports to iPrint printers. These commands are useful when you have legacy applications that require output to an LPT port, or when you want to add printers through a login script.

    For more information, see Section 5.5.8, Implementing iPrint by Using the Command Line.

For more information, including client requirements, see Section 5.1.3, Windows: iPrint Client.

Macintosh iPrint Client

The Macintosh iPrint Client contains a browser plug-in for the Safari web browser that lets you install printers through your web browser. For more information, see Section A.1, iPrint Client Supported Browsers.

The client integrates with CUPS and uses the CUPS local spooler to send print jobs to the Print Manager.

For more information, including client requirements, see Section 5.1.2, Macintosh: iPrint Client.

1.2.4 iManager

You use iManager to create, configure, and manage your iPrint system. For complete management, including, uploading printer drivers and PostScript Printer Description (PPD) files, you must access iManager from a workstation on which the iPrint Client is installed. For more information, about iPrint tasks in iManager, see Section 3.0, Installing and Setting Up OES iPrint on Your Server and Section 10.0, Managing Your Print System. For more information about iManager, see the NetIQ iManager Administration Guide.

1.2.5 Apache Web Server

Apache is the Web server for iPrint. The Web server serves up HTML pages, handles secure (SSL/TLS) and non-secure requests, and utilizes LDAP for authentication.