Ricoh InfoPrint Pro C900AFP AIX Planning Guide - Page 33

Pool destination configuration model, Logical, Destination 1, Job/Document, Defaults, Queue 1, Actual

Page 33 highlights

Pool destination configuration model Like the default destination configuration model, the pool destination configuration model has a one-to-many relationship between a logical destination and two or more actual destinations. The pool destination configuration model, as shown in Figure 4, has a one-to-many relationship between a logical destination and two or more actual destinations. Logical Destination 1 Job/Document Defaults Queue 1 Actual Destination 1 Actual Destination 2 Actual Destination 3 Figure 4. Pool destination configuration model This model is very effective when you have output devices that you want to group together based on things such as location, capability, speed, and capacity. You might also want to group them based on who uses them or who manages the output they generate. For example, all jobs sent to a specific group of printers come from the department that generates monthly statements for your customers. The jobs use the same set of job- and document-attribute defaults, including the form that they print on and the overlay they require. The printer operators responsible for the printers direct all of the output to a mail room for distribution. The pool model is also very beneficial in workload balancing. Note: You can submit a job directly to an actual destination with the Pool destination configuration model, but you won't achieve a pooling effect; the job will only be scheduled to the actual destination you submitted it to. Funnel destination configuration model The funnel destination configuration model has a many-to-one relationship between two or more logical destinations and one actual destination. Figure 5 on page 18 shows the funnel configuration. Chapter 2. Planning for configuration 17

  • 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

Pool destination configuration model
Like the default destination configuration model, the pool destination configuration
model has a one-to-many relationship between a logical destination and two or
more actual destinations.
The pool destination configuration model, as shown in Figure 4, has a one-to-many
relationship between a logical destination and two or more actual destinations.
This model is very effective when you have output devices that you want to group
together based on things such as location, capability, speed, and capacity. You
might also want to group them based on who uses them or who manages the
output they generate. For example, all jobs sent to a specific group of printers
come from the department that generates monthly statements for your customers.
The jobs use the same set of job- and document-attribute defaults, including the
form that they print on and the overlay they require. The printer operators
responsible for the printers direct all of the output to a mail room for distribution.
The pool model is also very beneficial in workload balancing.
Note:
You can submit a job directly to an actual destination with the Pool
destination configuration model, but you won’t achieve a pooling effect; the job
will only be scheduled to the actual destination you submitted it to.
Funnel destination configuration model
The funnel destination configuration model has a many-to-one relationship
between two or more logical destinations and one actual destination. Figure 5 on
page 18 shows the funnel configuration.
Logical
Destination 1
Job/Document
Defaults
Queue 1
Actual
Destination 1
Actual
Destination 2
Actual
Destination 3
Figure 4. Pool destination configuration model
Chapter 2. Planning for configuration
17