Ricoh InfoPrint Pro C900AFP AIX Planning Guide - Page 19

Logical destinations, Queues, Actual, Destination 2

Get Ricoh InfoPrint Pro C900AFP PDF manuals and user guides View all Ricoh InfoPrint Pro C900AFP manuals
Add to My Manuals
Save this manual to your list of manuals

Page 19 highlights

Job B Logical Destination 1 Job/Document Defaults Queue 1 Job A Actual Actual Actual Destination 1 Destination 2 Destination 3 Figure 1. InfoPrint Manager print flow. Job B is submitted directly to a logical destination, while Job A is submitted to an actual destination The following sections provide more information about the different kinds of InfoPrint objects and what happens to your print job at each step of the process. Logical destinations Logical destinations are objects in your InfoPrint Manager system that you can submit jobs to. In the simple print model shown in "Basic print flow" on page 2, the InfoPrint Manager environment has one default logical destination. You might want to add more logical destinations to support specific types of jobs and specific groups of job submitters. When you create an additional logical destination, you specify a name for the logical destination and associate it with a specific queue. The logical destination and the queue must reside in the same InfoPrint Manager server. You can specify default job and document attributes for a logical destination, so that all jobs submitted to that logical destination are automatically assigned certain default values. This saves time for the job submitter, and helps make sure that jobs submitted will not fail because of missing resources. If necessary, the submitter can override the default values by explicitly setting the attributes at submission time. Printer pooling (or clustering) is a powerful feature of InfoPrint Manager. Pooling allows jobs to be submitted to a single logical destination and then routed to appropriate physical devices. This feature enables you to distribute your work load evenly among available printing devices and to optimize printer utilization. It prevents bottlenecks where a large number of jobs are queued for a few printers while other equally capable printers sit idle. In short, printer pooling lets you see your output faster, and logical destinations make printer pooling possible. Queues A queue receives jobs from one or more logical destinations and routes jobs to one or more actual destinations. The queue holds a job until an actual destination capable of processing the job becomes available. In the simple print model shown in "Basic print flow" on page 2, the InfoPrint Manager environment has one Chapter 1. Introducing InfoPrint Manager for AIX 3

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
The following sections provide more information about the different kinds of
InfoPrint objects and what happens to your print job at each step of the process.
Logical destinations
Logical destinations are objects in your InfoPrint Manager system that you can
submit jobs to. In the simple print model shown in “Basic print flow” on page 2,
the InfoPrint Manager environment has one default logical destination. You might
want to add more logical destinations to support specific types of jobs and specific
groups of job submitters. When you create an additional logical destination, you
specify a name for the logical destination and associate it with a specific queue.
The logical destination and the queue must reside in the same InfoPrint Manager
server.
You can specify default job and document attributes for a logical destination, so
that all jobs submitted to that logical destination are automatically assigned certain
default values. This saves time for the job submitter, and helps make sure that jobs
submitted will not fail because of missing resources. If necessary, the submitter can
override the default values by explicitly setting the attributes at submission time.
Printer pooling (or clustering) is a powerful feature of InfoPrint Manager. Pooling
allows jobs to be submitted to a single logical destination and then routed to
appropriate physical devices. This feature enables you to distribute your work load
evenly among available printing devices and to optimize printer utilization. It
prevents bottlenecks where a large number of jobs are queued for a few printers
while other equally capable printers sit idle. In short, printer pooling lets you see
your output faster, and logical destinations make printer pooling possible.
Queues
A queue receives jobs from one or more logical destinations and routes jobs to one
or more actual destinations. The queue holds a job until an actual destination
capable of processing the job becomes available. In the simple print model shown
in “Basic print flow” on page 2, the InfoPrint Manager environment has one
Actual
Destination 2
Actual
Destination 1
Actual
Destination 3
Queue 1
Job/Document
Defaults
Logical
Destination 1
Job B
Job A
Figure 1. InfoPrint Manager print flow. Job B is submitted directly to a logical destination, while Job A is submitted to
an actual destination
Chapter 1. Introducing InfoPrint Manager for AIX
3