Default model

The default model has a one-to-many relationship between a logical destination and two or more actual destinations. It also lets you submit jobs directly to properly configured actual destinations. (In this way, the default model is similar to Figure 3. Desktop destination configuration model, but it requires you to create and manage fewer objects.) To support direct submission to actual destinations, the default model requires the actual destination to be associated with a logical destination. A job submitted to an actual destination is rerouted to the associated logical destination. At the logical destination, the job derives its job and document defaults. The job is then routed through the associated queue and back to the actual destination.

InfoPrint Manager uses this destination configuration model by default. (A single queue and a single logical destination are created automatically when you install InfoPrint Manager. ) You must configure the actual destinations to enable direct submission.

Default destination configuration model

Job A (submitted to an actual destination) prints on that actual destination. Job B (submitted to the logical destination) prints on the first actual destination that can support it.
Default destination configuration model.

This is a very flexible model that lets you enjoy the benefits of printer pooling, while retaining complete control over where certain jobs print.