Ricoh InfoPrint Pro C900AFP AIX Planning Guide - Page 35

Recommended distributed configuration model, InfoPrint Manager Administration GUI

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 35 highlights

Recommended distributed configuration model To manage your print environment efficiently in a distributed environment (as shown in Figure 7), we recommend organizing your destinations using the hourglass configuration model and using multiple queues and default jobs to control the work flow through your InfoPrint Manager for AIX servers. Define queues based upon operators, rather than based upon the number of devices defined in your installation. Whether your installation has one operator for every ten printers at your site or an operator managing all the printers on a particular floor, grouping printers by queue makes management of all printers and print jobs much easier because one person can monitor a single queue. Having one person monitor a single queue is highly efficient. An operator can use the InfoPrint Manager Administration GUI to view a particular queue. Because InfoPrint uses queue authorization to manage the security settings on print jobs, an operator has a much easier job overseeing this support without having to switch from one queue to another. You can create default jobs and associate them with different logical destinations to make sure that the queue schedules these jobs on the correct actual destinations. For example, the initial-value-job associated with LogDest1 can default actual-destination-requested to ActDest1, so that jobs submitted to LogDest1 are scheduled to ActDest1. Since actual-destinationrequested is a multiple-valued attribute, you can also specify more than one actual destination on the initial value job's actual-destination-requested attribute and let other job and document attributes (such as document-format) determine which actual destination is selected. Log Dest 1 Log Dest 2 Log Dest 3 Log Dest 4 Log Dest 5 Log Dest 6 Log Dest 7 Log Dest 8 Log Dest 9 Log Dest 10 Log Dest 11 Log Dest 12 Queue1 Queue2 Queue3 Queue4 Act Dest 1 Act Dest 2 Act Dest 3 Act Dest 4 Act Dest 5 Act Dest 6 Act Dest 7 Act Dest 8 Act Dest 9 Act Dest 10 Act Dest 11 Act Dest 12 Figure 7. Distributed configuration model. With this model, you can have different actual destinations associated with different logical destinations through the job and document defaults you specify. Chapter 2. Planning for configuration 19

  • 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
Recommended distributed configuration model
To manage your print environment efficiently in a distributed environment (as
shown in Figure 7), we recommend organizing your destinations using the
hourglass configuration model and using multiple queues and default jobs to
control the work flow through your InfoPrint Manager for AIX servers. Define
queues based upon operators, rather than based upon the number of devices
defined in your installation. Whether your installation has one operator for every
ten printers at your site or an operator managing all the printers on a particular
floor, grouping printers by queue makes management of all printers and print jobs
much easier because one person can monitor a single queue.
Having one person monitor a single queue is highly efficient. An operator can use
the
InfoPrint Manager Administration GUI
to view a particular queue. Because
InfoPrint uses queue authorization to manage the security settings on print jobs, an
operator has a much easier job overseeing this support without having to switch
from one queue to another. You can create default jobs and associate them with
different logical destinations to make sure that the queue schedules these jobs on
the correct actual destinations. For example, the initial-value-job associated with
LogDest1 can default
actual-destination-requested
to ActDest1, so that jobs
submitted to LogDest1 are scheduled to ActDest1. Since
actual-destination-
requested
is a multiple-valued attribute, you can also specify more than one actual
destination on the initial value job’s
actual-destination-requested
attribute and let
other job and document attributes (such as
document-format
) determine which
actual destination is selected.
Queue1
Queue3
Queue2
Queue4
Act
Dest
2
Act
Dest
8
Act
Dest
5
Act
Dest
11
Act
Dest
3
Act
Dest
9
Act
Dest
6
Act
Dest
12
Log
Dest
1
Log
Dest
4
Log
Dest
7
Log
Dest
10
Log
Dest
2
Log
Dest
5
Log
Dest
8
Log
Dest
11
Log
Dest
3
Log
Dest
6
Log
Dest
9
Log
Dest
12
Act
Dest
1
Act
Dest
7
Act
Dest
4
Act
Dest
10
Figure 7. Distributed configuration model.
With this model, you can have different actual destinations associated with
different logical destinations through the job and document defaults you specify.
Chapter 2. Planning for configuration
19