Ricoh InfoPrint Pro C900AFP Planning Guide - Page 31

Planning for configuration, Understanding destination configuration models

Page 31 highlights

Chapter 2. Planning for configuration This chapter describes destination configuration models that might be important to you as you design your InfoPrint Manager environment. Understanding destination configuration models Destination configuration models show the relationships among logical destinations, job- and document-attribute defaults, queues, and actual destinations. A default InfoPrint Manager destination configuration has a one-to-one relationship between a logical destination and an actual destination, and provides minimal job- and document-attribute default settings. As you customize your InfoPrint Manager environment to support your printing needs, you might want to consider a more advanced destination configuration model. Note: In multiple InfoPrint Manager server environments, the logical destination and the queue that it sends jobs to must reside in the same InfoPrint Manager server. The actual destination, however, can reside in a different InfoPrint Manager server, unless you want to submit jobs directly to the actual destination. For direct submission, the actual destination must reside in the same server as the logical destination and queue. The 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 the desktop model described below, 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. © Copyright InfoPrint Solutions Company 2000, 2009 15

  • 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

Chapter 2. Planning for configuration
This chapter describes destination configuration models that might be important to
you as you design your InfoPrint Manager environment.
Understanding destination configuration models
Destination configuration models show the relationships among logical
destinations, job- and document-attribute defaults, queues, and actual destinations.
A default InfoPrint Manager destination configuration has a one-to-one
relationship between a logical destination and an actual destination, and provides
minimal job- and document-attribute default settings. As you customize your
InfoPrint Manager environment to support your printing needs, you might want to
consider a more advanced destination configuration model.
Note:
In multiple InfoPrint Manager server environments, the logical destination
and the queue that it sends jobs to must reside in the same InfoPrint Manager
server. The actual destination, however, can reside in a different InfoPrint Manager
server, unless you want to submit jobs directly to the actual destination. For direct
submission, the actual destination must reside in the same server as the logical
destination and queue.
The 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 the desktop model described below, 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.
© Copyright InfoPrint Solutions Company 2000, 2009
15