Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP Distributed Print Service Administration Guide: HP 9000 Computers > Chapter 3 Planning Your HPDPS Configuration

Selecting Logical Configuration Models

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

A logical configuration model shows the relationships among logical printers, initial-value-job and initial-value-document objects, queues, and physical printers. You might want to configure all of the printers that you plan to administer with HPDPS at the same time. However, the more typical approach might be to at first configure just some of them under HPDPS , and then slowly bring more of them under HPDPS control. This approach lets you gradually become familiar with the capabilities and features of HPDPS and minimizes the initial configuration effort. This section describes four configuration models that you might consider for your HPDPS printing system.

The Desktop Configuration Model

A desktop configuration model has a one-to-one relationship between logical printers and physical printers. This model represents the way you typically manage and use a workstation printer. The types of jobs that your users can print with this configuration model are directly controlled by the capabilities of the physical printer.

Figure 3-1 Desktop Configuration Model

Desktop Configuration Model

The advantages and disadvantages of the desktop configuration model are:

Advantages:

  • Matches a traditional workstation printer configuration for an individual or for a small group.

  • Users have no uncertainty as to where their jobs will print.

  • Allows you to specify different defaulting for each physical printer.

  • Provides good security and control of printing activities.

Disadvantages:

  • No printer workload balancing.

  • You must create and manage more HPDPS objects; greater complexity.

  • All jobs sent to a logical printer must have similar characteristics. Based on the job, HPDPS might reject it, requiring your users to submit their jobs to a different logical printer.

The desktop configuration model is easy to understand because of the one-to-one relationship between a logical and physical printer. However, if workload balancing and ease of management are important considerations within a larger print environment, you might want to implement one of the other configuration models.

The Printer Pool Configuration Model

A printer pool configuration model has a one-to-many relationship between a logical printer and its associated physical printers. The primary consideration for a printer pool configuration is whether you have printer devices that make sense to group together. For example, the printer pool configuration is appropriate for printer devices that are located near one another, such as in a print room. Printing occurs at the same location, providing a central point where users pick up their jobs or from where you can distribute jobs. You can also group printer devices together based on other considerations:

  • printers with similar capabilities, such as a group of high-speed production printers.

  • printers that support a particular user group.

  • printers that support similar job characteristics, such as duplexed or rotated printing.

Figure 3-2 Printer Pool Configuration Model

Printer Pool Configuration Model

The advantages and disadvantages of the printer pool configuration model are:

Advantages:

  • Simplicity; you may have fewer HPDPS objects to create and manage as compared to the desktop model.

  • Allows HPDPS to balance your printer workload.

  • Convenient for printer devices that are in close proximity to one another.

  • Convenient for printer devices with similar functions and capabilities.

Disadvantages:

  • Defaults must be the same for all physical printers. If the printers do not have similar capabilities and features, you have very few options for job and document default values.

  • Users do not know where their jobs will print until they receive notification that the jobs have printed.

  • HPDPS does much of the routing of jobs to the printers. However, if your users require a specific printer device for their jobs, they must specify a physical printer with their print request.

The greatest benefit of the printer pool configuration model is in balancing your printing workload. The greatest drawback is that your users do not know which of the printers in the pool will print their job. You can solve this problem by only pooling printers with locations in common, by telling users how to request a specific physical printer, or by using a common job delivery method. For example, you can have printer operators deliver jobs to a central location.

The Funnel Configuration Model

A funnel configuration model has a many-to-one relationship between logical printers and a physical printer. This is a flexible configuration model that provides you with the ability to more closely control types of jobs and access to logical printers. Also, the funnel configuration solves the problem of users not knowing where their jobs will print.

Figure 3-3 Funnel Configuration Model

Funnel Configuration Model

The advantages and disadvantages of the funnel configuration model are:

Advantages:

  • Users know exactly where their jobs will print.

  • Allows you to specify different defaulting for each logical printer. Your users can submit a variety of job types.

  • Allows you to control the access to both the physical printer and its features.

Disadvantages:

  • There is no printer workload balancing.

  • Complexity; you must create and manage more HPDPS objects as compared to the desktop configuration model.

  • Limited by the capability of the physical printer. Based on the job, HPDPS might reject it causing your users to submit the job to a logical printer outside of the funnel configuration model.

The funnel configuration model shares with the desktop model the advantage of letting your users know exactly where their jobs will print. The added advantage is the flexibility of multiple logical printers with different sets of default values for jobs. For example, one logical printer might default attributes for double-sided printing jobs and another logical printer might default attributes for single-sided jobs.

The Hourglass Configuration Model

The hourglass configuration model has a many-to-many relationship between logical printers and physical printers. This model combines the printer workload balancing benefits of the printer pool model with the flexible job and document defaulting benefits provided by the funnel model. Figure 3-4 “Hourglass Configuration Model ” shows the hourglass configuration model.

Figure 3-4 Hourglass Configuration Model

Hourglass Configuration Model

The advantages and disadvantages of the hourglass configuration model are:

Advantages:

  • Allows HPDPS to balance your printer workload.

  • Convenient for printer devices that are in close proximity to one another.

  • Convenient for printer devices with similar functions and capabilities.

  • Allows you to specify different defaulting for each logical printer.

  • Provides good security and control of the printing activities in your print environment.

Disadvantages:

  • Complexity; you must create and manage more HPDPS objects as compared to the desktop configuration model.

  • Users do not know where their jobs will print until they receive notification that the jobs have printed.

The hourglass configuration model is the most flexible HPDPS configuration. The control you have of the print environment balances the complexity of the configuration.

Once you understand the four configuration models, you can use them as building blocks to plan your logical configuration. A complex configuration is unlikely to be exactly like one of the configurations above. Rather, it will most likely combine some or all of these building blocks to meet your varied print environment needs.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2000 Hewlett-Packard Development Company, L.P.